Open grumpycoderpt opened 1 year ago
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 :q!
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 This repository covers the recommendation algorithm, not the client UI
Works on my machine
Looking into it!
Same bug here https://X.com
Environment Firefox 115.0.2 on Windows 10.
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 xeyes
and xsnow
in the ultimate app package.
Can confirm this issue occurs on both OpenBSD and Windows XP 😭
Works on my machine
Well, we are not handing your machine to all other users tho
I'm having the opposite problem of OP — for the last couple days, my Twitter tabs have had two close buttons. Is it possible that it's related to the same bug?
I've attached a screenshot it case it might be helpful to the developers.
having the same problem on chrome:
If the :q!
, as suggested by @abuseofnotation doesn't work, you can try the Emacs way: C-x C-c
If the
:q!
, as suggested by @abuseofnotation doesn't work, you can try the Emacs way:C-x C-c
Ewww eMacs
I see what the confusion might be. It's a delayed reaction, could take six months, could take a year or two. But this website will close.
I think it's a latency issue. have you tried moving closer to the datacenter?
Why still not fixed, geez these programmers getting lazier everyday
had to consult stackoverflow, but apparently you can type :qa to get out of it, however not well documented
Any news about this? I had to shut down my computer in order to leave the site.
Didn't work for me. After I turned it back on, the website opened again with the same problem.
UPD: Reinstalling the browser solved it.
UPD 2: Now I have to reinstall the browser every time to close twitter. I think I'll avoid visiting it until they fix this issue.
This critical bug is still not resolved? Is this project dead?
can confirm for Firefox (latest), Opera (latest), Brave (latest), Chromium (latest) and BadWolf (latest) on Linux. can also confirm for Firefox (latest) and Chrome (latest) on android. if anyone wants to test lynx or other terminal browsers, be my guest
Wake up babe, a new competitor to unable to exit vim memes just dropped
Elon: LTGM
𝕏
Now that’s a retro meme
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.
Environment Windows Chrome latest version, also Mac OS and iOS 14 Safari.
Please make sure you update your browser to the latest version, which is Safari XVI.
lgtm, pls fix it
The problem spread to iOS. When I click on the "x" in the upper right corner of my device, a weird, twitter-like app opens!
Oh yeah... the TeX $\mathbb{X}$
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.
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.
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.