181–190 of 236 posts
My issues with Firefox 1) Signing into Chrome is easier and more intuitive then syncing with a code. Also having your extensions is nice. 2) The Inspect element and console are easier to use in Chrome. (Copy as HTML, etc) 3) I seem to have to click on a YouTube video twice for it to pause in Firefox. 4) Typing search queries in chrome is easier. For example in Firefox, you can't just type define: word to search Googl…
I find it irritating that Mozilla now herds its Firefox users toward the Stub installer, and not the full offline-install redistributable binary. The actual download itself is available on the "Systems & Languages" page: > https://www.mozilla.org/en-US/firefox/all/ This kind of download is important, when you want to try out a new release, without committing yourself to it. For example, let's say you want to load it…
Earlier quoted context omitted.
I don't understand how you can be unhappy about the performance of the few last versions of Firefox. It is now quite savy in memory (especially in comparison with Chrome) and handles everything I throw at it without noticeable janks.
Well it's certainly better. But, as some one who has to run Selenium at work a fair bit (it makes me so sad), I can tell you that Aurora is quite savvy and the memory use never really got out of hand but FF24 still crashes after running a fairly long suite.
Earlier quoted context omitted.
We love contributors :) https://developer.mozilla.org/en-US/docs/introduction
This is great! Thanks :) Anyone know of any other open source projects that one can contribute to?
Although lately I haven't worked in anything, would like to hear about more great opensource projects.
Earlier quoted context omitted.
More info on this?
I think they are referring to this change: https://blog.mozilla.org/nnethercote/2013/10/01/memshrink-pr... Images that aren't visible aren't decoded as they are downloaded, or something like that. It reduces peak memory usage on image-heavy pages. It should be coming in Firefox 26.
Earlier quoted context omitted.
They honestly had to though. their aggressive stance on plugins risked losing them significant market share in the Java-heavier parts of the world. They couldn't let a few rogue cowboy-developers with an agenda and complete user disconnect overnight just ruin what Mozilla have spent decades building up.
Anyone is still using Java in the Browser?
for better or worse some places java is the one sanctioned way to sign into online banks and sign official documents online.
Having your browser constantly telling you that you can't do that anymore, completely out of the blue, tends to cause dramatic reduction in browser usage in those areas.
How did firefox get development stagnate so badly? We have more workarounds and polyfills for dealing with firefox than we do for dealing with IE now, it is ridiculous.
Wow, on my MacBook Pro Retina, Firefox is now faster than Chrome. It's noticeable during any graphics update, scrolling pages in particular. I wonder if this is because Firefox has been optimized, or whether Chrome has simply stagnated. I suspect it's the latter; when I got the Retina MBP I immediately noticed that graphics performance was laggy compared to what I was used to on my previous (slower but non-Retina) MB…
Wow, on my MacBook Pro Retina, Firefox is now faster than Chrome. It's noticeable during any graphics update, scrolling pages in particular. I wonder if this is because Firefox has been optimized, or whether Chrome has simply stagnated. I suspect it's the latter; when I got the Retina MBP I immediately noticed that graphics performance was laggy compared to what I was used to on my previous (slower but non-Retina) MB…
Earlier quoted context omitted.
I agree in principle. But I've got to get stuff done in the real world. I don't have an extra week to read the 22,554 words of JUST the video/audio spec in HTML5, and try to figure out not just how all the browser versions differ from each other, but also how they differ from the spec: http://www.w3.org/TR/2011/WD-html5-20110113/video.html Sometimes user-agent sniffing is the only remotely sane thing you can do. Blam…
I'm cheerfully assuming that you're using distilled documentation and not the literal spec. If there is, say, conflicting documentation from Mozilla and Google, then we certainly have a bigger problem.
So that's the whole point. People who go on about "feature detection" and "follow the spec", and think it's that simple, really don't seem to understand what's actually going on.
[1] https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaEl...