Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Nylas Email Component Rendering Issues / Performance #171

Closed
PranavSathy opened this issue Nov 4, 2021 · 5 comments · Fixed by #179
Closed

[BUG] Nylas Email Component Rendering Issues / Performance #171

PranavSathy opened this issue Nov 4, 2021 · 5 comments · Fixed by #179

Comments

@PranavSathy
Copy link
Contributor

Describe the bug
Leveraging the Email component for any thread results in a huge whitespace between messages.

To Reproduce
Send emails back and forth through Outlook Web , open the thread in Nylas Email component. There will be jumbled text and large white spaces.

Expected behavior
It renders cleanly, without large whitespace and without affecting parent container CSS.

Version:
1.0.13

Additional context
See video below:

https://drive.google.com/file/d/12aGtAaeER9ZioCQ3cOEHwNdvmiIkBJdF/view?usp=sharing

@PranavSathy
Copy link
Contributor Author

Just curious if there is an ETA here and #172? Both are blocking our ability to integrate this component successfully.

@ozsivanov
Copy link
Contributor

Hi @PranavSathy, I'm taking a look at both of these today. Would you be able to put together a minimal reproducible example for #172 ? I'm not able to reproduce it with vanilla JS + HTML, so it looks like it might be related to an interaction between our components and React.

@PranavSathy
Copy link
Contributor Author

Thanks Oliver, unfortunately we don't have the bandwidth to roll a minimal reproducible at the moment :( [swamped on other things]. Recommendation would be a simple NextJS boilerplate application and render a hard coded Nylas email to see if it can be repro'ed.

I can see if the team can put together a repro earlier next week otherwise.

@ozsivanov
Copy link
Contributor

@PranavSathy I pushed v1.0.14 with fixes for both issues included. Please re-open if you're still running into these bugs.

@PranavSathy
Copy link
Contributor Author

@ozsivanov Awesome, thanks for these fixes. Had a minute to test out 1.0.14 on my Feature branch, looks like both of the issues mentioned here and in #172 were fixed. I noticed one last issue, which I will now as a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants