Hacker News Reader

Comment by torben-friis | Hacker News Reader

I just wish they finally fixed the bug that makes it unusable for me and thousands of other users using macbooks with resolution set to "more space"... I can't count how many people in my office I've had to help after their macbook randomly starts heating and turning fans to max power, it's always that they started using firefox.

I've been checking the tickets associated with the issue (mainly [this one](https://bugzilla.mozilla.org/show_bug.cgi?id=1404042) ) and there doesn't seem to be any significant advance, nor it seems the people in charge are aware of how prevalent and deal breaking this bug is :(

View on HN

yeah, I also noticed this and this is the one reason I wont be switching to Firefox on my macbook. On other PCs I’ve been using firefox for a long time now.

It's not just that. Exporting Passwords from Chrome to FF is impossible in macOS. Not a day goes by that I don't have to enter my password for a website. Thus, switching to FF actually means re-entering tens of passwords manually (given that you do remember the passwords, otherwise you'll have to go to Passwords Manager in Chrome and see the saved passwords).

Might it be worth using a password manager instead, like 1Password, or KeePass and its variants?

Maybe, but the problem of exporting passwords from Chrome still exists.

Sorry to be completely off topic here as HN does not support private messages or replies to old threads.

A long shot but you may be able to save us countless hours of effort. Over at the OpenJ9 project we're trying to get z/OS testing for our JDK and one of the dependencies is the XML::Parse perl library which depends on libexpat. In [1] you mentioned you worked on porting this to work with EBCDIC. Did you ever succeed? If so are your changes available in open source anywhere?

[1] https://news.ycombinator.com/item?id=14084875

Oh god! That's why my battery life is better since switching back to the standard resolution. What an awful bug.

Indeed.

In my experience the bug is usually overlooked because people won't notice that they only have performance issues when the browser is open - for most people, the browser is always running nowadays.

I wonder if this bug also applies to using the "Looks like 1280x800" option on a MBP with a 2560x1600 screen (this is what I use). The default is "Looks like 1440x900".

It doesn't, or it's at least better.

Reply on news.ycombinator.com