DOM mismatch when using mq-layout
See original GitHub issuenuxt.config.js:
mq: {
defaultBreakpoint: 'md',
breakpoints: {
sm: 640,
md: 1250,
lg: Infinity
}
},
using in a component.vue:
<mq-layout mq="sm">content for sm breakpoint</mq-layout>
Then i get an error:
If i change defaultBreakpoint
to sm
then it works, but if i use <mq-layout mq="md">content for md breakpoint</mq-layout>
then i get DOM mismatch error again.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Layout mismatch between development & build in Gatsby
The problem is that the render is correct in gatsby develop, But when I gatsby build, the second item of the airtable data...
Read more >DOM diff and component stack in SSR hydrate mismatch ...
Renders DOM diff and component stack showing visually the location where the hydration failed. Example warning with a diff (see the fixtures/ssr and...
Read more >Debugging and fixing hydration issues - somewhat abstract
To exclude a component that needs layout effects from the server-rendered HTML, render it conditionally with showChild && <Child /> and ...
Read more >react-hydration-error
An example of this is using window in a component's rendering. Another example: Invalid HTML may cause hydration mismatch such as div inside...
Read more >Understand and solve hydration errors in Vue.js
If the server and client of the DOM have states that differ at the time of hydration, nodes may be missing or added,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
With pleasure.
Is this issue related to #56? If so, I can close that one off too.
Good luck with your project!
Guess, it was my own issues, i restarted IDE and errors are gone, thanks for your time.