Includes important security fixes for vuln's disclosed at Pwn2Own, like this arbitrary heap write from JS:
https://www.mozilla.org/security/announce/2014/mfsa2014-31.h...
Firefox 28 Release Notes
71–80 of 164 posts
Re: Firefox 28 Release Notes
#72Firefox 29 hits the beta, that means MacOs users get tabs in title line, finally!
That makes me wiling to try Firefox again, since amongst the Safari/Chrome/Firefox it was the browser that consumed most vertical space, which is an issue on mobile (less than 15") laptops - at least for me.
Give it a try .. it looks great in OS X native full screen mode.
Re: Firefox 28 Release Notes
#73Earlier quoted context omitted.
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?
There is, yes. You have three somewhat simple options for the search/url thing: 1) Have a single box, do not offer search suggestions. 2) Have a single box, offer search suggestions for the stuff users type in it. 3) Have separate boxes; offer search suggestions for the stuff typed in the search box but not the stuff typed in the url box. #2 involves sending everything the user types in the url bar to the search sugg…
Another option is to prefix searches. If I type "google " then start offering search suggestions. Chrome even has this, and a nice UX for it. It just unfortunately also has unprefixed searching.
Re: Firefox 28 Release Notes
#74Earlier quoted context omitted.
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?
There is, yes. You have three somewhat simple options for the search/url thing: 1) Have a single box, do not offer search suggestions. 2) Have a single box, offer search suggestions for the stuff users type in it. 3) Have separate boxes; offer search suggestions for the stuff typed in the search box but not the stuff typed in the url box. #2 involves sending everything the user types in the url bar to the search sugg…
>only offering search suggestions if the string typed so far doesn't look like a URL
How would this work? Lets say I wanted to search for Wikipedia, perhaps because I know there's news about it. How would Firefox know I was going to type "Wikipedia" and not "Wikipedia.com"?
Re: Firefox 28 Release Notes
#75Why Firefox removes spdy/2 support? They don't want to support spdy/2 servers? Why? PS: I'm not expert on servers :)
It got discontinued, and Chrome dropped it as well. Both support the newer SPDY/3.1 https://en.wikipedia.org/wiki/SPDY#Protocol_versions https://bugzilla.mozilla.org/show_bug.cgi?id=912550 https://code.google.com/p/chromium/issues/detail?id=303957
While all browsers support http 1.0 websites almost three decades later.
Spdy really shows how fast people are willing to put immature technology in production as long as Google claims it better. Amazing.
What's even wise is the attitude towards abandoning published protocols and contracts. This is not how a lasting and stable internet was built.
This clearly shows why spdy can't be a candidate for http 2.0
Re: Firefox 28 Release Notes
#76Earlier quoted context omitted.
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?
This is to protect user privacy as explained by a Mozilla dev: https://news.ycombinator.com/item?id=6756582 Otherwise every keystroke you made would be sent to Google.
Uhm it could just search when hitting enter. No need to autosuggest.
Re: Firefox 28 Release Notes
#779007199254740992 running in "random" mode with 0ms delay is still way faster in Chromium 32 than in Firefox 28. http://www.csie.ntu.edu.tw/~b01902112/9007199254740992/
Hmm. I see about the same thing with Chrome 35 dev and Firefox (28 or nightly) on Mac here, performance wise.
Re: Firefox 28 Release Notes
#78Earlier quoted context omitted.
There is, yes. You have three somewhat simple options for the search/url thing: 1) Have a single box, do not offer search suggestions. 2) Have a single box, offer search suggestions for the stuff users type in it. 3) Have separate boxes; offer search suggestions for the stuff typed in the search box but not the stuff typed in the url box. #2 involves sending everything the user types in the url bar to the search sugg…
>only offering search suggestions if the string typed so far doesn't look like a URL How would this work? Lets say I wanted to search for Wikipedia, perhaps because I know there's news about it. How would Firefox know I was going to type "Wikipedia" and not "Wikipedia.com"?
Yes, it's things like that that make this approach complicated and failure-prone. Which is why Firefox is not doing it.
Re: Firefox 28 Release Notes
#799007199254740992 running in "random" mode with 0ms delay is still way faster in Chromium 32 than in Firefox 28. http://www.csie.ntu.edu.tw/~b01902112/9007199254740992/
Same there (try 10000 sites, click "Benchmark"): http://www.raymondhill.net/voronoi/rhill-voronoi-demo1.html The difference has narrowed though, FF used to be much, much slower than chromium.
I can definitely see a difference on this one, yes, about 30%. A question. Does "rendering not included" mean not including painting times, or not including the canvas API call times either? My profiler is showing a bunch of fill(), rect(), stroke(), moveTo() calls dominating the wall-clock time, but I'm not sure whether those are what's being measured here or not.
Re: Firefox 28 Release Notes
#80Earlier quoted context omitted.
This is to protect user privacy as explained by a Mozilla dev: https://news.ycombinator.com/item?id=6756582 Otherwise every keystroke you made would be sent to Google.
Uhm it could just search when hitting enter. No need to autosuggest.
This already work.
Remove the separate search bar and you are ready to go.