-
Notifications
You must be signed in to change notification settings - Fork 12.2k
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
The new X button doesn't close the website #1876
Comments
STOP |
got this issue too, here's hoping it gets resolved soon! 🙏 |
It's always a delight to visit this repo |
it's a new feature |
I got fed up waiting for a fix so I made a userscript that patches this as a temporary workaround. I haven't been able to test it thoroughly but hopefully someone finds it useful |
twitter has official become unusable with these bugs… |
Try |
extremely concerning |
Twitter is one big bug these days No solving that one |
Can confirm this bug also for Firefox ESR 115 on Debian GNU/Linux 12 |
Knew this rebrand was going to screw everything over. |
Any news about this? I had to shut down my computer in order to leave the site. |
I also have the same bug on Chromium 115 since days. |
Out of scope |
Works on my machine |
Looking into it! |
Same bug here https://X.com Environment |
Same bug here |
Tested, proven workaround: never visit that dumpster fire of a website again. Delete the app too. |
Can reproduce, on Firefox for Android and Firefox for Fedora Linux and OpenSUSE Tumbleweed. |
can confirm for Firefox 115.0.2-1 on Arch Linux x86_64 |
Also I would like to add that the X logo in the top left is a different font from the official logo |
My two cents: maybe someone deployed by mistake the native X.org client app. Would definitely join |
Can confirm this issue occurs on both OpenBSD and Windows XP 😭 |
Well, we are not handing your machine to all other users tho |
If the |
Ewww eMacs |
Elon: LTGM |
Tweets in GitHub issues is new level |
document.querySelector("X").on('click', chrome.closeCurrentTab()) Type in your console. |
Can confirm this is a problem. Does happen on Firefox 112 as well. I did some investigating and it looks like on some clients it redirects to the home screen and on others it goes right to the top depending on the platform. I think we should consider this could be a problem with the Web Environment Integrity API not being implemented properly as it might think that the browser is not capable of closing the tab thus crashing and restarting the React app back to "/". Twitter Devs should consider checking their setup of it here https://github.com/RupertBenWiser/Web-Environment-Integrity and make sure it's all setup properly. As the technology is new it might accidentally class the browser wrong so you should ideally be using navigator.* as a fallback. |
Please make sure you update your browser to the latest version, which is Safari XVI. |
lgtm, pls fix it |
Oh yeah... the TeX |
same bug exists on Chrome115 |
This bug is spreading further, not only on browsers but now also on the android app. In addition, the "close button" moved to the center of the app header bar, making the UI experience even worse as users are more forced to close this app immediately. |
|
You should make the fallback message look like this instead: https://yewtu.be/watch?v=p7HzFXoZQ4k |
There is a patch for it !!!@grumpycoderpt @CleoMenezesJr there is some news for you :D |
Quick fix
|
If you close this issue, it will become more powerful (and self-referential) than you can possibly imagine |
this issue should be pinned for visibility actually. most users have problems with that X button and can find workarounds in here |
This one works better : |
today, i just clicked on the X for real trying to go back to the previous page for real |
@fanfare: we're all here because we clicked on the X for real, please treat this issue with the proper respect and seriousness that it deserves. |
my accidentally clicking the X a moment ago is technically a separate issue from the OP (i was trying to go "back" after opening a tweet -- confusing the functionality of the "X" with the functionality of the site's "left" arrow [1] -- and not trying to "close the website" (this confusion likely stems from other sides having "X" buttons to dismiss the current active page and go back, e.g. USA Today [2])). I doubt this separate confusion warrants a new issue, however, I would be happy to open one or even several more new issues on the topic if necessary. separately, i have done some reflection and agree that my using the phrase "for real" was dismissive and insensitive, and for that i offer my deepest apologies... |
I think that this is definitely confusing and should be addressed immediately. The functionality of the “X” should be noticeably different from the site’s left arrow to prevent confusion.
… On Aug 9, 2023, at 12:22, fanfare ***@***.***> wrote:
@fanfare <https://github.com/fanfare>: we're all here because we clicked on the X for real, please treat this issue with the proper respect and seriousness that it deserves.
my accidentally clicking the X a moment ago is technically a separate issue from the OP (i was trying to go "back" after opening a tweet -- confusing the functionality of the "X" with the functionality of the site's "left" arrow [1] -- and not trying to "close the website" (this confusion likely stems from other sides having "X" buttons to dismiss the current active page and go back, e.g. USA Today [2])). I doubt this separate confusion warrants a new issue, however, I would be happy to open one or even several more new issues on the topic if necessary.
separately, i have done some reflection and agree that my using the phrase "for real" was dismissive and insensitive, and for that i offer my deepest apologies...
<https://camo.githubusercontent.com/c304856a7ff5a9c6d3c8a350692a265fad0d8f811ffee47916d47cc6bf974f6d/68747470733a2f2f692e6a6f6c6c6f2e6f72672f4447594b7932656f2e706e67>
<https://camo.githubusercontent.com/7ee2d0374b1489a3427825dac92d88afcfad6dc92f433bf042f4a997a4e324d2/68747470733a2f2f692e6a6f6c6c6f2e6f72672f73585a6d366d69332e706e67>
—
Reply to this email directly, view it on GitHub <#1876 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUA6DVADB2RLQCKEFPU2ACLXUL7APANCNFSM6AAAAAA2VYC5DI>.
You are receiving this because you commented.
|
Calling this retarded and hostile toward users would do a whole lot more good than interpreting it as a joke. But alas. I'm having correspondence with twitter users right now, so you probably checked out at the third word of this comment and got your pitchforks ready out of fear of punishment for not punishing the usage of that term. Alas, alas. |
X Twitters overflow-github |
can confirm on grub/gnu/linux/systemd/lenovo/intel/nixos/x86_64/gpl/nix/nvidia/zsh/ext4/sddm/wayland/kde/qt5/ using the Firefox browser (version 120.0.1 (64-bit)) (Mozilla Firefox for NixOS) (nixos - 1.0) (Firefox is designed by Mozilla, a global community working together to keep the Web open, public and accesible to all.) (Want to help? Make a donation or get involved) |
The problem can be reproduced on my Mac(M1 series, 256GB + 16GB). |
Nice, but could you reproduce the issue? |
No, I cannot reproduce it anymore since I blocked that entire embarrassment of a website from my life and I can only feel pity for those who for whatever reason have to keep using it. |
This has to be the one of the funniest issues in all github hahah |
Describe the bug
So a new close button popup today on the website and it doesn't work, instead of closing the website it redirects the user to the homepage.
I know it is not regarding the algorithm but this place seemed appropriated to report a bug issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The tab should close, as good UX teach us.
Environment
Windows Chrome latest version, also Mac OS and iOS 14 Safari.
The text was updated successfully, but these errors were encountered: