-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
missing class attributes on wrapper functions #50
base: master
Are you sure you want to change the base?
Conversation
…nd_yarn/acorn-5.7.4 Bump acorn from 5.7.3 to 5.7.4
88cbe38
to
a553672
Compare
That's strange. Never realised that it behaves like that. But this seems to me like a bug in the server side rendering. |
@maoberlehner can you share your thoughts on why you think this component will be obsolete with Vue 3? I'm deciding whether I should aggressively optimize my Nuxt.js app with this component or hold off on that. I can't seem to find any info on lazy hydration being planned for Vue 3. |
See https://twitter.com/youyuxi/status/1265684355420225537 for example. |
Very cool, thank you! 👍 |
this happens only when using the wrapper functions for hydration and not by using a tag.
e.g. you have a
<CustomComponentA class="xyz" />
and CustomComponentA has
<div class="blub"></div>
as template.Currently only "xyz" is applied while the component is not hydrated, with this regular class merging is happening and the final result class is "xyz blub".
I've added a test for this scenario.
Without the patch following scenarios happen:
SSR (correct):

before hydration (wrong, this also causes some flickering):

after hydration (correct again):

with this patch missing classes (missing in vnode, but are available in $el) are applied to the loading component.
@maoberlehner please let me know what you think of this issue.
thanks
simon