SSR error -- extra attributes from the server: tabindex
See original GitHub issueWhen developing with Gatsby using the DEV_SSR flag, the following warning shows in the browser console:
react_devtools_backend.js:4026 Warning: Extra attributes from the server: tabindex
at video
at media-controller
at eval (webpack-internal:///./node_modules/media-chrome/dist/react/index.js:78:74)
I think this sort of error occurs when there’s a mismatch between what is server-side rendered vs. what is rendered in the browser after React hydration. If there’s a need for a basic github repo with Gatsby demonstrating the issue just let me know, since this isn’t reproducible in codepen.
This is with media-chrome@0.15.1
.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Warning: Extra attributes from the server: style #22388 - GitHub
So my question is how to find that particular error. I've clicked on all those links in the console message, but I'm unable...
Read more >Warning: Extra attributes from the server: disabled
When I compile it and run via SSR setup, I see this error in browser console: Warning: Extra attributes from the server: disabled....
Read more >Server-Side Rendering Optimization - Spartacus Documentation
Server -Side Rendering optimization allows you to fine tune your SSR setup, and gives you more ways to resolve potential issues related to...
Read more >next/link | Next.js
Enable client-side transitions between routes with the built-in Link component.
Read more >NG0100: Expression has changed after it was checked - Angular
This error commonly occurs when you've added template expressions or have begun to implement lifecycle hooks like ngAfterViewInit or ngOnChanges . It is...
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
I’ve created a repo to reproduce the issue: https://github.com/ShaunDychko/demo-mediachrome-ssr-error
To reproduce
npm run develop
http://localhost:8000
While the error shows in the browser console, I was not able to demonstrate that React has to re-render.
thanks for providing an example to reproduce.
appears there is also a special property
suppressHydrationWarning
that can be set totrue
to hide the warnings https://reactjs.org/docs/dom-elements.html#suppresshydrationwarning