51–60 of 256 posts
Earlier quoted context omitted.
Adding multi-process to a large project that was not designed for multi-process is an astronomical amount of work. And Firefox's approach has advantages over Chrome's, so they're not simply playing catch-up.
Even Internet Explorer has been multi-process since IE8. All other browsers do it, except Firefox.
Earlier quoted context omitted.
Session restore in Firefox has been lazy for a long time now (the tab only loads when you activate it). It doesn't take longer than loading a single page. How often do tabs crash for you? That's the real issue if you ask me. I'm on Nightly (with Electrolysis!) and the last crash was over 2 months ago.
I have a crash probably every day. Usual culprit is Flash.
I recently switched back to Firefox from Chrome. They have done a nice job in speeding it up. My Chrome seems like more of a bottleneck than my internet connection.
I really wish there were a way to more easily identify if the problem is an addon or inherent to Firefox.
Earlier quoted context omitted.
speaking of zooming, and if any Moz devs are watching, please finally fix radio and checkbox control zooming. it's been 7.5 years . https://bugzilla.mozilla.org/show_bug.cgi?id=400364
What? You don't like the challenge of trying to click on a micron wide checkbox on your new 4k laptop screen? That's half the fun, I say.
Yay! Time for another firefox rant. I love the idea of firefox and I used to love it a lot. But not now. I keep trying it and always go back to chrome. It crashes. A lot. Like, at least once a day I have to ctrl+alt+del and restart it on my laptop. It freezes and the window stops responding, it doesn't even paint. In the inspector, the DOM breadcrumb area scrolls and moves around. It's like the blink tag, only worse.…
I'm not sure why you're being downvoted so much. I assume the usual FOSS fanboyism that rules HN. I used Chrome, IE11, and Firefox all day. FF is the only one that locks up and crashes on me. Its so rare in the other browsers I'm shocked when it happens in FF. I run almost no extensions and I think my copy at work has zero extensions and I don't even have flash installed, so the idea that it must be a plugin problem…
I know for a fact that Mozilla leadership does prioritize crashes and resource usage (in fact, this is one reason for all of the work on the process separation feature called Electrolysis), but of course they will prioritize crashes that affect lots of users. For various reasons, it could be that your crashes are different from those. (I'll assume that you're on the most recent version of Firefox already.)
Meanwhile, in firefox 39a (current nightly), a reader view (readability/printfriendly) http://imgur.com/DONqb30
Why's that added to the main program, though? I mean, there's extensions that do the same thing, right? (I'm sure others have made similar remarks about other features that were added over time that were originally in extensions)
I recently switched back to Firefox from Chrome. They have done a nice job in speeding it up. My Chrome seems like more of a bottleneck than my internet connection.
my concern with firefox, at least on the mac, I tend to find video play back just stops whereas I can take the same video to Safari and have zero issues. I really wish there were a way to more easily identify if the problem is an addon or inherent to Firefox.
Earlier quoted context omitted.
Understood, but I'm speaking from the viewpoint of a user, here. It's a massive annoyance for a crashed tab to annihilate the other 49. (And the session restore being activated is generally grounds for a smoke break, because your system will be tied up for a while...)
Session restore in Firefox has been lazy for a long time now (the tab only loads when you activate it). It doesn't take longer than loading a single page. How often do tabs crash for you? That's the real issue if you ask me. I'm on Nightly (with Electrolysis!) and the last crash was over 2 months ago.
Yeah, because it only loads a single page. It doesn't actually restore anything. Sometimes the pages it restores aren't even the live version but a cached one, I have no idea when or why it does that. It's absolutely infuriating.