31–40 of 175 posts
Chrome was years behind Firefox, too: https://code.google.com/p/chromium/issues/detail?id=143 - from at least 2008 thorough 2012 there was no proper color management in Chrome, while Firefox had it. This was a deal-breaker for some users. Eventually Chrome copied what Firefox had for many years. It goes both ways.
> no proper color management in Chrome Can you elaborate on this? I'm relatively new at it, but I write code for a color science company so I'm curious as to what you mean. Edit: I'm also reading halfcamerageek 's URL: http://cameratico.com/guides/web-browser-color-management-gu...
The correct behavior would be to interpret all page elements and untagged images as being in the sRGB color space. This is what the W3C recommends and Firefox follows.
Chrome was years behind Firefox, too: https://code.google.com/p/chromium/issues/detail?id=143 - from at least 2008 thorough 2012 there was no proper color management in Chrome, while Firefox had it. This was a deal-breaker for some users. Eventually Chrome copied what Firefox had for many years. It goes both ways.
Now, as the author pointed out, Firefox seems to be unable to keep up in some key areas.
I began using Firefox a long time ago (when it was called Phoenix) but switched to Chrome. A couple months ago I switched back to Firefox because Chrome lost my open tab session in some cases (hard crashes when loading the old session), due to privacy issues and because it often triggered long swaps (locking the process) when dealing with lots of tabs (I usually have like 50-60 tabs open in several windows). Also bec…
It's the really small things that annoy me about Firefox. For example, in gmail, when writing an email, I can't hit cmd+right arrow to go to the end of a line. And because links are set to open in a new window, I can't cmd+click them to open them in the background.
Ctrl-click also seems to work (on Linux).
"No Multi-Process Architecture" This is a feature, and I like it. The rest is just flamebait.
I don't know if the author is trying to make Mozilla prioritize his desired features, but the years-behind metric doesn't sound very friendly, or used-centered for the matter.
"No Multi-Process Architecture" This is a feature, and I like it. The rest is just flamebait.
Also: Firefox seems to discourage you from messing with cookies. For example: I can't select cookies by TLD. I have to painstakingly go through the list, clicking each host and clicking "Remove". Compare the cooking management functionality with the next tab over, password management. There you can filter the list as you want. So it is possible.
Earlier quoted context omitted.
Seriously? Can't there be one discussion on here that isn't about Snowden or Prism?
So long at people get karma for lazy low-content references to whatever cause everyone is swept up in they won't stop posting them.
According to Snowden's leaked Prism slides, Google was brought into the NSA fold on the 14th of January 2009. So Firefox is well over 4 years behind Chrome in that respect as well. Get your act together, Mozilla!
Seriously? Can't there be one discussion on here that isn't about Snowden or Prism?
It's also important to note that there is a divide between OSS Chromium and Chrome.
I started using Firefox again and everything works except for some reason, I cannot login to Twitter. After entering the details, and clicking the Login button, I'm redirected back to the login page. I can view tweets just fine (without being logged in).