Did I miss the thread about the new Firefox redesign?
-
@mott555 said:
The new Firefox interferes with my AMD drivers somehow.
Other people (including me) report visual corruption of the entire program and certain websites with AMD cards.
-
@LoremIpsumDolorSitAmet said:
Also, I like Morb's new sig that makes me agree with them.
It's the only way he could get anyone to agree with him. A bit sad, really.
I also like how Firefox now has a fucking POWER BUTTON on the "hamburger" menu. Because really, the title bar close button is just so 2010s.
-
@Zylon said:
It's the only way he could get anyone to agree with him. A bit sad, really.
Daww, is Zywon gonna cwy?
-
@Zylon said:
I also like how Firefox now has a fucking POWER BUTTON on the "hamburger" menu. Because really, the title bar close button is just so 2010s.
Power button? So does it turn off the power on the 1920x1080 HD widescreen DESKTOP MONITOR that this desktop web browser is running on?
Goddamn fucking Mozilla.
-
@dhromed said:
@mott555 said:
About a year ago Firefox changed something that caused rendering problems but it could be fixed by going into <font face="courier new,courier">about:config</font> and setting <font face="courier new,courier">gfx.content.azure.enabled = False</font>. It wouldn't suprise me if there was some new regression that brought back the problem.The new Firefox interferes with my AMD drivers somehow.
Other people (including me) report visual corruption of the entire program and certain websites with AMD cards.
-
You mean this bug?
I can't even tell if it's already fixed, will be fixed in FF30 or whatever...
-
@Strolskon said:
They have a fix that appears to work. The fix will not be included in 30; it will be in 31. At least that's what I get from the last few comments.You mean this bug?
https://bugzilla.mozilla.org/show_bug.cgi?id=812695
I can't even tell if it's already fixed, will be fixed in FF30 or whatever...
-
@HardwareGeek said:
@Strolskon said:
I was right. It's a regression. After fixing the original bug, they made some new changes that exposed more problems with certain older AMD drivers. There's an about:config setting that can be used as a workaround and they claim to have a fix that's just been put into the code for the nightly builds, and may show up in FF 31. Of course the the bad news is you have to use the new Assholio version of FF to get the fix. Or use a FF fork like Palemoon which never implemented the problem code in the first place.You mean this bug?
They have a fix that appears to work. The fix will not be included in 30; it will be in 31. At least that's what I get from the last few comments.https://bugzilla.mozilla.org/show_bug.cgi?id=812695
I can't even tell if it's already fixed, will be fixed in FF30 or whatever...
-
@morbiuswilters said:
Daww, is Zywon gonna cwy?
Have you started speaking Welsh now? Pining for the sheep, are you?
-
@dkf said:
@morbiuswilters said:
Daww, is Zywon gonna cwy?
Have you started speaking Welsh now? Pining for the sheep, are you?Is Zyoon gonna cooi??!
-
@Zylon said:
I also like how Firefox now has a fucking POWER BUTTON on the "hamburger" menu. Because really, the title bar close button is just so 2010s.
That's retarded. And completely irrelevant. I've never used the hamburger button in EVER. I wouldn't even have realized this button exists if I hadn't checked just now. I still use the menu and I don't intend to change that.
Also, the new "Australis" changes didn't really bring anything that annoyed me, much unlike the previous (28 - 3.6) GUI redesigns.
-
@El_Heffe said:
I hope my AMD drivers aren't old. I have a Radeon R9 280X.@HardwareGeek said:
@Strolskon said:
I was right. It's a regression. After fixing the original bug, they made some new changes that exposed more problems with certain older AMD drivers. There's an about:config setting that can be used as a workaround and they claim to have a fix that's just been put into the code for the nightly builds, and may show up in FF 31. Of course the the bad news is you have to use the new Assholio version of FF to get the fix. Or use a FF fork like Palemoon which never implemented the problem code in the first place.You mean this bug?
They have a fix that appears to work. The fix will not be included in 30; it will be in 31. At least that's what I get from the last few comments.https://bugzilla.mozilla.org/show_bug.cgi?id=812695
I can't even tell if it's already fixed, will be fixed in FF30 or whatever...
-
@mott555 said:
I have a Radeon R9 280X.
Slightly jelly. But my HD 6850 is holding up nicely, even if I've had it for a while.
-
@mikeTheLiar said:
@mott555 said:
I have a Radeon R9 280X.
Slightly jelly. But my HD 6850 is holding up nicely, even if I've had it for a while.I've been meaning to upgrade my rig for a while now, but every time I look at the roadmap and see something better a little further down the horizon.
I was going to upgrade to Maxwell first quarter of this year, but there were problems with the 20nm fab.
-
@joe.edwards said:
I've been meaning to upgrade my rig for a while now, but every time I look at the roadmap and see something better a little further down the horizon.
There always is something better coming along; it's the fundamentally deflationary nature of this industry. Stuff keeps getting cheaper, for real (or what you get for your money gets better; they're approximately equivalent in economic terms). Sometimes you've got to stop worrying about what may come in the future and buy something for now; it'll be rapidly obsolete anyway.
-
And necroing this too because I'm pissed off.
-
Guest said in Did I miss the thread about the new Firefox redesign?:
@fire2k said:
I'll still try a blakeyrant.
Has a good beat and is easy to dance to. I give it an 83.And the 2013 Ironic Lack Of Self Awareness Award goes to:
Anything posted to the Internet lasts forever.
Unless it's an image more than 6 months old. Because fuck permanent URLs or hosting.
Filed under: Or a Microsoft KB article
-
@GreyWolf1 said in Did I miss the thread about the new Firefox redesign?:
Thanks for the warning, everybody. So I just tuned off attomatic updating in Firefox options. I will never allow the Atlantis update.
That was posted Tuesday, November 12, 2013 11:22:29 PM
Close enough to June 25, 2013 that maaaaaaaaaaaaybe I'm not the only one.
-
Also, if the migration from Dickwhores to NoWorkingBB had preserved "last read" markers, when I clicked on this topic I would have ended up at the necroing post-- rather than the start of the thread, which gave me the opportunity to re-read some of it and make some sweet FF22 jokes.
-
@Lorne-Kates said in Did I miss the thread about the new Firefox redesign?:
Also, if the migration from Dickwhores to NoWorkingBB had preserved "last read" markers, when I clicked on this topic I would have ended up at the necroing post-- rather than the start of the thread, which gave me the opportunity to re-read some of it and make some sweet FF22 jokes.
I'm seriously considering treating this sort of thing as if the highlighted word is merely a strange and incorrect spelling of "necrotic"...
-
@Lorne-Kates said in Did I miss the thread about the new Firefox redesign?:
make some sweet FF22 jokes
ENOTFOUND
-
@Lorne-Kates said in Did I miss the thread about the new Firefox redesign?:
Guest said in Did I miss the thread about the new Firefox redesign?:
And the 2013 Ironic Lack Of Self Awareness Award goes to:
Anything posted to the Internet lasts forever.
Unless it's an image more than 6 months old. Because fuck permanent URLs or hosting.
You're just mad because you can't see the pictures in this other post:
Guest said in Did I miss the thread about the new Firefox redesign?:@flabdablet said:
Horsepenis
-
For those of you pining for something a bit less bloated and shiny, there's a fork of Firefox called Pale Moon ( palemoon.org ). Back when I used Firefox, it typically took at least a minute to load when switching to X after the computer spent all night in the virtual console. With Pale Moon, it's never taken more than a second. And that's on a modern computer- one with a 3GHz Pentium 4 and 2GB of memory.
Here's a screenshot: https://u21i.imgup.net/pale36ce.png
Edit: WTF, this was a general reply, not one to a specific person.
-
@hw3patch said in Did I miss the thread about the new Firefox redesign?:
And that's on a modern computer- one with a 3GHz Pentium 4 and 2GB of memory.
Weird, NodeBB showed this to me as a recent post
-
@wharrgarbl
It is:I meant to post in the other thread. More seriously, my definition of modern may be a bit lax. 32-bit computers ought to be enough for anybody!
-
@hw3patch said in Did I miss the thread about the new Firefox redesign?:
Pale Moon
is it supposed to not support javascript?
more seriously though, I need tab trees -- do you know if palemoon has an addon for them?
-
is it supposed to not support javascript?
Ha, it's just that I fully enable NoScript 99% of the time.
more seriously though, I need tab trees -- do you know if palemoon has an addon for them?
That's one of the things I like: From the FAQ: Addons designed for Firefox <= 24 are fully compatible (or at least supposed to be). I don't use tab trees myself, but it didn't choke when I started to install Tab Tree, but backed out at the last second.
-
@hw3patch said in Did I miss the thread about the new Firefox redesign?:
there's a fork of Firefox called Pale Moon ( palemoon.org )
I've been using it since a few months after the meddling in a Firefox update broke my Vimperator keybindings.
So far I like Pale Moon because it doesn't try to be over-ambitious and it's a "vote with your feet" approach (analytics should at least see a drop in "Firefox usage" as Firefox v22 is by definition Firefox)
Keep in mind though that addon support is sketchy. Most if not all addons need to be modified to work, and Firefox addon developers are just a slight bit more likely to quit or fully rewrite their addon to the SDK du jour (pardon my French) rather than support an "obscure" browser.
So if you want an addon then it'll likely need to be modified by a Pale Moon supporter, and that little project might then suffer from the open source "it fixes my problem, pull requests welcome" support model.
-
@barfoo1 Cupcakes are definitively worse than cookies. Unless you get the really expensive gourmet ones, which are an entire class unto themselves. But as far as garden-variety cupcakes go, I'd take a muffin or a cookie any day.