-
Notifications
You must be signed in to change notification settings - Fork 238
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
StackOverflow code appearing issue #1819
Comments
Hey! Thanks for the detailed report here! We've remotely disabled the changes on Stack Exchange so that it's not causing an issue. We're going to roll out a fix for this soon. Thanks! |
@jonathanKingston For completeness's sake, Stack Exchange Q&A sites are also hosted on the domains Can those sites please be added to the list? |
@gparyani I came here to add that this issue still exists on |
@jthornton-0 It was worked around for Super User and the other four sites earlier this week, per the above code change. |
I am still seeing this issue on Stack Overflow. I have version 2023.4.11 of this extension installed. |
@codeguru42 this should now be fixed, sorry I forgot to turn the fix back on via the config when removing the mitigations for Chrome. 🤦🏻 |
Description
When using certain websites like StackExchange (Tex.SE, Meta.SE, SO.SE), the application is causing a box of code to appear when clicking on the global inbox like so:
Those lines of code should not appear and it is apparently a bug on DuckDuckGo's side (the StackOverflow answer here and the answer to my Meta StackExchange question here explain in further detail that I cannot claim experience with).
Steps to Reproduce
Expected behavior:
For there to be no code and for inbox to open without taking vertical space from the screen.
Actual behavior:
The bug causes lines of code to appear due to this answer by
Kaiido:
Versions
Additional Information
The linked answers seem to diagnose the issues. I cannot replicate the issue on other sites but as StackOverflow and co are widely used and so is your application it may be significant.
I will also say that is a very new issue, I cannot recall this from a few days ago but the user in the StackOverflow Meta question reported it 7/8 days ago.
The text was updated successfully, but these errors were encountered: