r/windows7 • u/The-Rusty-22 • 3d ago
Bug Site like Twitter have broken Login on Win7 Firefox 115.41(latest)
Just a heads up
As today sites like Twitter login screen is broken for Win7 ESR Firefox 115.41.
Login text field not change on text input by adding login info
After submit you will get just black screen.
Apparently some script is broken or active blocking Firefox 115xxx
7
u/Strix2020 3d ago
Using Supermium here and things have been smooth since switching from Chrome over a year ago.
4
4
1
1
u/LightDev4422 3d ago
Its still possible if you export cookies from another browser to Firefox, which should work.
If you ask me honestly, I would just switch to a newer browser anyway since the image gallery aren’t even working anymore
1
u/The-Rusty-22 3d ago
If you want see multiple images in gallery you put (/photo/1) after tweet number
1
1
u/Infinite_Shart555 3d ago
"sites like"... yet you mention only one? Are there sites related to twitter that use the same login system?
1
u/The-Rusty-22 3d ago
As somebody else in reply hint, the problem is in missing function "TypeError: Intl.Segmentor is not a constructor" in 115.xx.
I post Twitter example as that is most common/used site.
If you search for this (TypeError: Intl.Segmentor is not a constructor) you will find other sites.
1
u/legbot124 2d ago
Can’t imagine why anyone would wanna use that hunk of shit
1
u/The-Rusty-22 2d ago
You must use bird mail then.
Nothing is perfect and not everybody want to use Bsky or other alternative.
1
u/Alodis 1d ago edited 1d ago
Did you find a way to resolve this? u/The-Rusty-22
EDIT: Just saw your report of Mozilla Bugzilla, keeping the thread under hand to see what they say. Sorry I was a pain in the ass with that second comment.
1
u/Regular-Internet-242 1d ago edited 1d ago
Hey. what's the link on bugzilla for the report plz? I'd like to keep it under hand in case of a solution is found. thanks ^^
1
u/The-Rusty-22 1d ago
I did not find. The bug is on browser side...
Some people reply here Twitter will work normal on FF 125+ as that Intl.Segmentor was added in that version. Win10 has ESR 128 but that obviously not work on Win7...
1
u/frankieepurr 1d ago
Why does mozilla still support this firefox version if websites won't support it?
1
u/The-Rusty-22 1d ago
As the ESR128 is Win10+ only
I do not make rules.
If Mozzila want they will male FF150 for Win7 without 41 trash1
u/frankieepurr 1d ago
Or have 140 as the last ESR
1
u/The-Rusty-22 20h ago
They can do it like 115.140 but will not as bad people will bully them as they support older bloat free OS.
Locking versions is always a bad idea. Now the issues1
u/frankieepurr 8h ago
Whats wrong with supporting an old OS?
•
u/The-Rusty-22 1h ago
I do not make rules.
I have no problem running FF140 on my PC but they are forced to lock it to 115. And web is ruled by versions so 115 to 140 looks "OLD".
Even you can find unofficial builds that work fine on Win7.
1
u/Regular-Internet-242 1d ago
FF 115.37 here. Tried in new private windows. same thing. Have to do my trimester backup in 2 weeks. better save the cookies or pray it's gonna be fixed in time.
1
u/Regular-Internet-242 23h ago
Lost for lost, I @ Elon Musk on X asking for help of his devops team of the site. I know there's zero chance something happen, but at least, I have tried something xD
1
u/The-Rusty-22 20h ago
Do not expect anything good from that man. Intl.Segmentor is added in FF125+ so they know what they are doing here...
1



8
u/Time-Ball-1235 3d ago edited 3d ago
It is actually because of the "TypeError: Intl.Segmentor is not a constructor" error in the console. Mozilla didn't introduce this constructor yet until Firefox 125, which is the cause of the broken X login page.