Firefox 41-50 is well and truly fucked
-
@anonymous234 said in Firefox 41-50 is well and truly fucked:
@CreatedToDislikeThis I like Vivaldi. It has vertical tabs and tab stacking. Why can't other browsers copy at least that?
Lynx does that, if you stack your Putty windows right.
-
-
@Lorne-Kates said in Firefox 41-50 is well and truly fucked:
free-after-use bug, which gives R/W access to memory
When will dumbarse software developers learn to stop writing programs in C?
Oh, never? Well, shit.
-
Most of Firefox is written in C++, so obviously it's twice as good as C.
Filed under: I still every time I thnk about the name C Plus Plus.
-
@Lorne-Kates said in Firefox 41-50 is well and truly fucked:
@anonymous234 said in Firefox 41-50 is well and truly fucked:
Yeah good thing Firefox 22 only has 25 critical vulnerabilities eh?
:noscript.txt:
-
@sloosecannon said in Firefox 41-50 is well and truly fucked:
It's a good thing none of those vulnerabilities can be executed without JavaScript. Because man, that would suck
via a CANVAS element, a mozTextStyle attribute and an onresize event
I don't know if I've ever even seen a CANVAS I wonder if Adblock / noscript takes them out by default?
Anyways, it doesn't matter, since it requires all three. CANVAS, with a mozTextSize, and a resize event to fire.
Which requires Javascript.
:noscript.pdf:
-
@Lorne-Kates said in Firefox 41-50 is well and truly fucked:
@sloosecannon said in Firefox 41-50 is well and truly fucked:
It's a good thing none of those vulnerabilities can be executed without JavaScript. Because man, that would suck
via a CANVAS element, a mozTextStyle attribute and an onresize event
I don't know if I've ever even seen a CANVAS I wonder if Adblock / noscript takes them out by default?
Anyways, it doesn't matter, since it requires all three. CANVAS, with a mozTextSize, and a resize event to fire.
Which requires Javascript.
:noscript.pdf:
Yeah I picked a bad one (misread and as or)
The link now is just a crafted document though, so that's JS-free
-
@sloosecannon Or this, which is literally caused by a large document...
-
@anonymous234 said in Firefox 41-50 is well and truly fucked:
tab stacking
Yep, that feature is absolutely essential. When the old Opera was discontinued and replaced with one that could not stack tabs, I was really angry.
-
think i will move over to edge
-
@Helix said in Firefox 41-50 is well and truly fucked:
think i will move over to edge
Be careful you don't fall off
-
@Helix I use Edge, with Opera for sites that don't work properly on it. I'm such a maverick
-
@Helix said in Firefox 41-50 is well and truly fucked:
think i will move over to edge
-
@anonymous234 said in Firefox 41-50 is well and truly fucked:
@CreatedToDislikeThis I like Vivaldi. It has vertical tabs and tab stacking. Why can't other browsers copy at least that?
Because, we need full width pages, so we can restrict the content to the middle 50%, because more than 80 characters per line is confusing to the millennials.
But, seriously, I would be concerned that shaving the width would create chaos with "responsive" design.
-
I just had to restart Firefox twice because the first time I clicked on "Restart to update" it had only updated to 50.0.1. What good is silent background updating if it doesn't even update all the way?
-
@hungrier Why doesn't it use dynamically linked libraries to update while running?
-
@sloosecannon said in Firefox 41-50 is well and truly fucked:
@sloosecannon Or this, which is literally caused by a large document...
Which requires loading a huge page (initial reports were using an infiniscroll hack on Reddit, with inline images, and going 17+ pages).
The Bugzilla thread shows the difficulty of trying to repro-- it isn't reliable.
And then it creates a race condition, which is extremely difficult to control and get anything useful out of.
Also also it seems to only be for x86 Windows 7 , and not x64. So I'm good.
-
@xaade said in Firefox 41-50 is well and truly fucked:
I would be concerned that shaving the width would create chaos with "responsive" design.
Uh, isn't the point of responsive design that it works regardless of the width? Like, that's literally the reason it exists...
-
By the way, to get a newer version, one can use FireFox developer edition.
-
@sloosecannon said in Firefox 41-50 is well and truly fucked:
@xaade said in Firefox 41-50 is well and truly fucked:
I would be concerned that shaving the width would create chaos with "responsive" design.
Uh, isn't the point of responsive design that it works regardless of the width? Like, that's literally the reason it exists...
Yeah.... about that....
Programmers expect you to be at 1080, or at phone width.
If you're anywhere between, god knows what layout you're going to get, and what bugs it will have, since no one tests at every width.
-
@sloosecannon said in Firefox 41-50 is well and truly fucked:
Uh, isn't the point of responsive design that it works regardless of the width?
You're using an example of software that doesn't do that :P
@xaade said in Firefox 41-50 is well and truly fucked:
If you're anywhere between, god knows what layout you're going to get, and what bugs it will have, since no one tests at every width.
I do.
Well, not every width imaginable, but I at least test around every Bootstrap 3 breakpoint, and any I add myself. Also, I don't go hiding features on mobile (though some decorative images do get hidden on small screens).
-
@xaade said in Firefox 41-50 is well and truly fucked:
Programmers expect you to be at 1080, or at phone width.
*Some programmers. Or *most programmers. Not all.
@xaade said in Firefox 41-50 is well and truly fucked:
since no one tests at every width.
I do as well. I test at L, M, and S.
@RaceProUK said in Firefox 41-50 is well and truly fucked:
@sloosecannon said in Firefox 41-50 is well and truly fucked:
Uh, isn't the point of responsive design that it works regardless of the width?
You're using an example of software that doesn't do that :P
@xaade said in Firefox 41-50 is well and truly fucked:
If you're anywhere between, god knows what layout you're going to get, and what bugs it will have, since no one tests at every width.
I do.
Well, not every width imaginable, but I at least test around every Bootstrap 3 breakpoint, and any I add myself. Also, I don't go hiding features on mobile (though some decorative images do get hidden on small screens).
Yeah, hiding features on mobile is, again, not responsive design.
I mean, a lot of "responsive" sites do it. looks at nodebb.
But it's not.
-
@sloosecannon said in Firefox 41-50 is well and truly fucked:
Yeah, hiding features on mobile is, again, not responsive design.
I love how some websites just put a stub in for their site at phone width.
Literally no content, and maybe 3 or 4 links if you're lucky.
Then they direct you to an app that still has only 10% of the functionality of their full site.
-
@xaade said in Firefox 41-50 is well and truly fucked:
@sloosecannon said in Firefox 41-50 is well and truly fucked:
Yeah, hiding features on mobile is, again, not responsive design.
I love how some websites just put a stub in for their site at phone width.
Literally no content, and maybe 3 or 4 links if you're lucky.
That's the #1 best way to make me never visit your site again you idiotic moron
-
@Adynathos said in Firefox 41-50 is well and truly fucked:
FireFox developer edition.
It shouldn't surprise me that the forum that invented the term "discoursistent" has trouble spelling both Firefox and WordPress.
-
@ben_lubar I don't have an f key. I do have a F key though.
-
@asdf said in Firefox 41-50 is well and truly fucked:
@anonymous234 said in Firefox 41-50 is well and truly fucked:
tab stacking
Yep, that feature is absolutely essential. When the old Opera was discontinued and replaced with one that could not stack tabs, I was really angry.
Did you break things?
-
@Helix said in Firefox 41-50 is well and truly fucked:
think i will move over to edge
Make sure you don't get cut.
-
@ben_lubar there's also laziness attached, at least in my case when typing Wordpress :P
-
@kt_ said in Firefox 41-50 is well and truly fucked:
Did you break things?
You mean, apart from our forum software? ;)
-
@xaade
Like Linkedin then
-
@xaade said in Firefox 41-50 is well and truly fucked:
because more than 80 characters per line is confusing to the millennials.
Go to http://motherfuckingwebsite.com on a 1080 display with your browser on full screen and tell me how readable that shit is
-
@bb36e said in Firefox 41-50 is well and truly fucked:
Go to http://motherfuckingwebsite.com on a 1080 display with your browser on full screen and tell me how readable that shit is
http://bettermotherfuckingwebsite.com says:
Looking at an LCD screen is strainful enough. Don't make me read a line of text that's 200 fucking characters long. Keep it to a nice 60-80 and users might actually read more than one sentence of your worthless dribble.
-
@bb36e said in Firefox 41-50 is well and truly fucked:
I would, but the work URL filter blocks that as "Pornography" XD
-
@Zecc said in Firefox 41-50 is well and truly fucked:
says:
Exactly, there's a reason for limiting the width, it's not because of 'millennial hipster web designers'
-
@Zecc said in Firefox 41-50 is well and truly fucked:
@bb36e said in Firefox 41-50 is well and truly fucked:
Go to http://motherfuckingwebsite.com on a 1080 display with your browser on full screen and tell me how readable that shit is
Looking at an LCD screen is strainful enough. Don't make me read a line of text that's 200 fucking characters long. Keep it to a nice 60-80 and users might actually read more than one sentence of your worthless dribble.
Either one works.
Maybe that's because I'm different.
I can read a line that is whatever amount of characters long, but I rather prefer double spacing. What makes me lose my train of thought isn't losing what I read at the beginning of the line, but losing which line I'm looking at.
-
@xaade said in Firefox 41-50 is well and truly fucked:
I can read a line that is whatever amount of characters long,
Sure, that's easy. The problem is finding the start of the next line. Or skimming without losing half the content.
-
@xaade said in Firefox 41-50 is well and truly fucked:
What makes me lose my train of thought isn't losing what I read at the beginning of the line, but losing which line I'm looking at.
And this.
-
@Zecc said in Firefox 41-50 is well and truly fucked:
@xaade said in Firefox 41-50 is well and truly fucked:
I can read a line that is whatever amount of characters long,
Sure, that's easy. The problem is finding the start of the next line. Or skimming without losing half the content.
Not a problem if you double space.
-
@Yamikuronue said in Firefox 41-50 is well and truly fucked:
@El_Heffe Yeah, but it seems like Created is looking for a sweet spot: as good at rendering as Chrome, but much more customizable
-
@Helix said in Firefox 41-50 is well and truly fucked:
think i will move over to edge
Call me when it starts reliably and doesn't just instaquit when opening it at random.
-
@aliceif said in Firefox 41-50 is well and truly fucked:
@Yamikuronue said in Firefox 41-50 is well and truly fucked:
@El_Heffe Yeah, but it seems like Created is looking for a sweet spot: as good at rendering as Chrome, but much more customizable
WTF What font is it failing to fallback from?!
font-family: "ヒラギノ角ゴ Pro W3", "Hiragino Kaku Gothic Pro", "メイリオ", Meiryo, Osaka, "MS Pゴシック", "MS PGothic", "Helvetica Neueue",Helvetica,Arial,sans-serif;
Ended in
MS PGothic
. why...
-
@aliceif said in Firefox 41-50 is well and truly fucked:
Call me when it starts reliably and doesn't just instaquit when opening it at random.
I can't login in to my 401K with it. But that's not Edge's fault.
-
@Tsaukpaetra said in Firefox 41-50 is well and truly fucked:
font-family: "ヒラギノ角ゴ Pro W3"
Great, first Drumpf pisses of China by taking that phone call, and already they've taken over the Internet.
-
Good news everyone! A new version of Firefox is out and you can upgrade to it right away to get this critical update.
Also, it may fuck up your personalized settings.
http://www.ghacks.net/2016/12/05/beware-firefox-updates-may-reset-preferences/
Godfuckit, Mozilla.
-
@Yamikuronue said in Firefox 41-50 is well and truly fucked:
@El_Heffe Yeah, but it seems like Created is looking for a sweet spot: as good at rendering as Chrome, but much more customizable
I thought that's something we'll be getting.
Then I actually saw Opera 15.
Fucks.
Meanwhile... Vivaldi?
-
That's what I get for replying before reading everything...
@anonymous234 said in Firefox 41-50 is well and truly fucked:
I like Vivaldi. It has vertical tabs and tab stacking. Why can't other browsers copy at least that?
That's exactly what Opera WAS. Then they fucked it up. And now Vivaldi is trying to bring it back.
The problem being, they're using Electron framework...
-
@Onyx said in Firefox 41-50 is well and truly fucked:
I thought that's something we'll be getting.
https://www.youtube.com/watch?v=9ntPxdWAWq8#t=1m20s&end=1m36s
-
@aliceif said in Firefox 41-50 is well and truly fucked:
Call me when it starts reliably and doesn't just instaquit when opening it at random
I've never had those problems, so... now?
Edge is a bit crap in a lot of ways, but I haven't seen any of the serious problems some other people talk about
-
My brain is insisting on reading the title of this thread as
Firefox -11 is well and truly fucked
and i keep thinking:
1) I want to use that sort of version numbering scheme for something
2) THAT'S NOT HOW MATH WORKS ACCALIA!