Warning: Extra attributes from the server: data-lt-installed #41816
Replies: 19 comments 35 replies
-
|
I was getting something like this ( |
Beta Was this translation helpful? Give feedback.
-
|
it was Grammarly for me 🤦 |
Beta Was this translation helpful? Give feedback.
-
|
Grammarly for me too🤯. Thanks @oscartbeaumont . |
Beta Was this translation helpful? Give feedback.
-
|
Yes to me. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
It worked for me too! I think in my case was LanguageTool causing the warning, it makes sense because both are grammar extensions, maybe both uses some same dependencies. |
Beta Was this translation helpful? Give feedback.
-
|
same issue cuz of grammarly |
Beta Was this translation helpful? Give feedback.
-
|
For development, it's better to have everything disabled, even AdBlock, how did you find out about LanguageTool? Very clever if you ask me, I would have never thought of it. |
Beta Was this translation helpful? Give feedback.
-
|
it was Grammarly |
Beta Was this translation helpful? Give feedback.
-
|
I have not been able to solve it in any way, I uninstalled all the extensions and still I get the error, what is it due to?
|
Beta Was this translation helpful? Give feedback.
-
|
This way I have my layout in the root |
Beta Was this translation helpful? Give feedback.
-
|
how did you manage that? |
Beta Was this translation helpful? Give feedback.
-
|
Had same error, but once I disabled Grammar extension, it disappears. |
Beta Was this translation helpful? Give feedback.
-
|
The culprit was Grammarly on mine. Switched "This can read and change site data" -> When you click the extension |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, i disabled it and the error disappeared |
Beta Was this translation helpful? Give feedback.
-
|
yes it truly work when I also remove Grammarly extension from the browser |
Beta Was this translation helpful? Give feedback.
-
|
Hi @itsezc 👋🏻 Does this cause any harm besides the warning? Asking because I would rather not uninstall LanguageTool. |
Beta Was this translation helpful? Give feedback.
-
|
Just a warning, never run into anything more serious. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. Just ran into same error. Will ignore as I just need it for a demo |
Beta Was this translation helpful? Give feedback.
-
|
Just ran into this as well. Confirming that disabling Grammarly resolves the warning. I'm curious what is going on here though ... |
Beta Was this translation helpful? Give feedback.
-
|
I've run into this problem with a few of my extensions. Grammarly, 1Password and even Seems like it's not really a big problem though, but I would like to get rid of it without losing the functionality of any of my tools (I obviously don't want myself or others to be trained to ignore errors in the console). |
Beta Was this translation helpful? Give feedback.
-
|
FYI, apparently you can disable warnings if you know what's causing them by doing the following |
Beta Was this translation helpful? Give feedback.
-
|
I don't want to delete Grammarly, if it's the main reason, actually
|
Beta Was this translation helpful? Give feedback.
-
|
Nothing is working for me |
Beta Was this translation helpful? Give feedback.
-
|
Thanks this fixed it |
Beta Was this translation helpful? Give feedback.
-
|
Thanks |
Beta Was this translation helpful? Give feedback.
-
|
This fixes it thanks |
Beta Was this translation helpful? Give feedback.
-
|
This fixes it thanks |
Beta Was this translation helpful? Give feedback.
-
|
Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Disabling Grammarly worked for me too. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Apparently there are a few extensions that might be causing this. For me, I had to run my browser in private mode. (I had some extensions configured to run even in private, so I had to turn this option off on Firefox). |
Beta Was this translation helpful? Give feedback.
-
|
I disabled Grammarly extension and it worked for me |
Beta Was this translation helpful? Give feedback.
-
|
Stop
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks rakibulinux |
Beta Was this translation helpful? Give feedback.
-
|
Chrome has released a new feature to disable extensions for specific URLs which is great, since this warning seems to just be a development environment issue. Simply put chrome://flags/#extensions-menu-access-control into your Chrome browser to enable this flag, then you can toggle off your extensions for the http://localhost:3000 URL! No need for the suppressHydrationWarning={true} prop mentioned above. |
Beta Was this translation helpful? Give feedback.
-
|
Can you give more informations on how to do it please? What should we do here?
|
Beta Was this translation helpful? Give feedback.
-
|
Cool 😎 |
Beta Was this translation helpful? Give feedback.
-
|
Change the "Extensions Menu Access Control" setting to "Enabled", then relaunch Chrome. You'll see a new option in the toolbar that allows you to block extensions on a per-site basis. |
Beta Was this translation helpful? Give feedback.
-
|
thank you, It looks like it's not working very well, it's buggy for me but maybe over time they will fix it |
Beta Was this translation helpful? Give feedback.
-
|
Disabling Grammarly worked for me too. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
PT: EN: In my case, it happened because of LanguageTool, ColorZilla and Grammarly. After I deactivated it, it worked. |
Beta Was this translation helpful? Give feedback.
-
Disabling Liner worked for me. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Work for me, Disable the extension and enable it again and the warning will be removed |
Beta Was this translation helpful? Give feedback.
-
|
Nice troll from extensions, same issue |
Beta Was this translation helpful? Give feedback.
-
|
So as pointed out in the previous comments above extensions similar to Grammarly, and ColorZilla can be the culprit. In my case I had the two. These extensions passing extra attributes with your code when it is executed on the browser trying to interact with the UI, this creates a mismatch between what was rendered on the server and what is rendered on the client. While disabling these extension can solve the problem an
export default RootLayout({ children }) { |
Beta Was this translation helpful? Give feedback.
and others
-
For anyone running into this warning on Next 13 (on Firefox):
You have to disable / uninstall the LanguageTool extension, disabling it for the site won't be enough.
Beta Was this translation helpful? Give feedback.
All reactions