51–60 of 164 posts
Super excited about better codec spread. What do they mean by volume control, though? We've been able to control the volume of HTML5 video/audio for a while now. Edit: here's a comparison of the audio UI between versions: https://mediacru.sh/2528762308f7 , looks butt-ugly imo
Eagerly waiting to ditch Chrome & its forced notifications. Perhaps with Australis (Firefox 29), the UI would be at par. Edit : Chrome feels subtle, lighter & perceptually faster (specifically : tabs, scrollbars). Although after updating Firefox today, I can notice that there's improvement in Firefox.
One major (okay maybe not that major but an important factor in my decision) issue for me with Australis is the separate boxes for URLs and search. Every other browser merged them and I don't know of any reason to keep them separate - is there one?
What I like about Firefox (versus Chrome specifically) is that the AwesomeBar gives much better suggestions from your history, doing full-text searches in titles - within Chrome I can rarely find something in my history without opening the history view and seriously, most searches that I do are for things that I've already seen and it saves a lot of roundtrips to Google (hint, hint), plus searching for things you can barely remember on Google, which you end up doing in Chrome, is like searching for the metaphorical needle in a haystack.
Plus, as others said, I like it when the browser cares about my privacy. On Android on the other hand there's only a single bar due to a lack of space, but it asks you if you want to activate Google's search suggestions.
Earlier quoted context omitted.
It's admittedly a corner case, but I've searched phrases that contain URLs and have had them get treated as a URL rather than search phrase in Chrome. In that case, I just drop to google.com and issue the search from there.
If you prefix your query with a ? it will be sent to your default search provider instead.
Eagerly waiting to ditch Chrome & its forced notifications. Perhaps with Australis (Firefox 29), the UI would be at par. Edit : Chrome feels subtle, lighter & perceptually faster (specifically : tabs, scrollbars). Although after updating Firefox today, I can notice that there's improvement in Firefox.
One major (okay maybe not that major but an important factor in my decision) issue for me with Australis is the separate boxes for URLs and search. Every other browser merged them and I don't know of any reason to keep them separate - is there one?
Is VP9 supported by all WebM-supporting browsers now? (i.e. is it feasible to completely drop VP8 and use VP9 instead?)
Earlier quoted context omitted.
It's admittedly a corner case, but I've searched phrases that contain URLs and have had them get treated as a URL rather than search phrase in Chrome. In that case, I just drop to google.com and issue the search from there.
ctrl-k works as "go to search box" in both browsers. For Chrome, that means focussing on the address bar and presetting it to "? ".
Firefox should allow you to type "45/3" in the address bar and be taken to Google with the calculation.
It does, when you prepend "google " in front of "45/3", which is in my opinion the best solution (I don't want to route all my URLs through google).
Super excited about better codec spread. What do they mean by volume control, though? We've been able to control the volume of HTML5 video/audio for a while now. Edit: here's a comparison of the audio UI between versions: https://mediacru.sh/2528762308f7 , looks butt-ugly imo
The relnote is presumably talking about https://bugzilla.mozilla.org/show_bug.cgi?id=649490
Earlier quoted context omitted.
In regards to rendering performance, we have this internal app that's pushing a lot of points into timeline charts rendered with HighCharts. When all the datapoints are rendered, Chrome has a lot of latency but is still usable, whereas Firefox chokes. I see that in Australis it's much improved, but still less usable than Chrome. This is awkward since in general I find Firefox's performance to be on par with Chrome, s…
I've found Chrome's graphics performance in general to be better than Firefox's, specifically with regards to canvas and SVG. Not sure the reason, but my guess is just lack of optimization.