Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 28 Release Notes

mozilla.org

Post reply on HN
Print view View original

91–100 of 164 posts

Re: Firefox 28 Release Notes

#91

Post by nnethercote »

bad_user wrote: post #22
reidrac wrote: post #6

Well, there's also stuff that you can't see in the "release notes". I found that Firefox 27 had huge speed improvements in canvas 2D compared to Firefox 26, at least in Linux without hardware accelerated canvas. I couldn't find anything related to that in 27's release notes, sooo (still happy though!).

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…

Internal apps are hard for Firefox devs to debug, but I've had success in the past debugging problems in internal apps by using a test account where the developers have emailed the login details to me privately.

If you are able to provide such a test account, please file a bug at https://bugzilla.mozilla.org/enter_bug.cgi; use "Core :: General" in the "find product" box; and don't worry too much about most of the fields, the title and description are the most important; and also add ":njn" to the "CC" field. Say something like "I can provide login details privately".

If you can do that, I'll try to find the right person to address it.

Re: Firefox 28 Release Notes

#92

Post by hobohacker »

wbond wrote: post #49

Interesting to see that now the current stable versions of Chrome and Firefox have dropped spdy/2, which is the only version of spdy supported by the current stable version of nginx. And nginx is the server used by more than 90% of hosts supporting spdy[1]. I presume this means it is mostly a Google/Twitter/Cloudflare thing for now since they seem to all be running spdy/3.1 in production. [1] http://w3techs.com/techn…

Speaking as a Chromium SPDY & HTTP/2 developer, we are very much focused on standardization. SPDY is an experimental protocol meant to drive the standards process, not become a de facto standard itself. Therefore, it's critical for us to kill off old SPDY versions.

For more discussion on this topic, please refer to these discussion threads: https://groups.google.com/forum/#!topic/spdy-dev/_uvxTJkeCP0 https://groups.google.com/forum/#!topic/spdy-dev/XDudMZSq3e4

And note that your reference is slightly misleading (I don't think you intended this). It's true, the vast majority of hosts supporting SPDY are running nginx. In practice though, the vast majority of these hosts are Cloudflare or WordPress.com hosted sites. Both run newer versions of nginx with SPDY/3.1 support.

Re: Firefox 28 Release Notes

#93

Post by marcosdumay »

rch wrote: post #35
tedmielczarek wrote: post #29

Earlier quoted context omitted.

If your search bar is your URL bar, then all your keystrokes (even when typing URLs) go to your search provider to provide autocomplete of search results. In Firefox you can type URLs without having them sent to a third-party. We think this is important. (You can get autocomplete search results by typing in the search bar.)

You could handle this with configuration, as others have. Edit: judging from the other comments, maybe you have already.

No, you can not.

If you don't have a separated search bar, your only options are enabling or disabling autocomplete. There is no option of using autocomplete just when you want it.

Also, the local autocomplete of the address bar is great. Count me as another one that does not want to miss it.

Re: Firefox 28 Release Notes

#94

Post by marcosdumay »

ajanuary wrote: post #73
bzbarsky wrote: post #65

Earlier 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…

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.

We can also make it bash compatible, and have all the GNU tools available at the address bar... (find www.wikipedia.com --title GNU)... But I don't think most people will be able to use it.

Re: Firefox 28 Release Notes

#95

Post by rch »

enscr wrote: post #20

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.

The first thing I look for in a browser is a way to switch through tabs in last-used order. If doesn't work out of the box, then I personally don't have a reason to investigate further. If this was a checkbox feature in Chrome (or Firefox, whichever's first), I'd probably never try anything else.

Re: Firefox 28 Release Notes

#96

Post by gorhill »

bzbarsky wrote: post #77
davidgerard wrote: post #9

9007199254740992 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.

I am pretty sure he was joking. But there are cases though where the speed does matter. Cool d3 animations for example.

Re: Firefox 28 Release Notes

#97

Post by wbond »

hobohacker wrote: post #92
wbond wrote: post #49

Interesting to see that now the current stable versions of Chrome and Firefox have dropped spdy/2, which is the only version of spdy supported by the current stable version of nginx. And nginx is the server used by more than 90% of hosts supporting spdy[1]. I presume this means it is mostly a Google/Twitter/Cloudflare thing for now since they seem to all be running spdy/3.1 in production. [1] http://w3techs.com/techn…

Speaking as a Chromium SPDY & HTTP/2 developer, we are very much focused on standardization. SPDY is an experimental protocol meant to drive the standards process, not become a de facto standard itself. Therefore, it's critical for us to kill off old SPDY versions. For more discussion on this topic, please refer to these discussion threads: https://groups.google.com/forum/#!topic/spdy-dev/_uvxTJkeCP0 https://groups.g…

Right, so my point stands that it is interesting that current stable browsers don't support current stable web servers. So unless someone has the resources to test and deploy unstable web servers, it effectively means you shouldn't bother with spdy at this point.

Re: Firefox 28 Release Notes

#98

Post by work_account_2 »

ams6110 wrote: post #87
brymaster wrote: post #38

Earlier 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.

You can turn autosuggest off

And you can install Omnibar or Instantfox if you want a combined address bar and search bar.

Re: Firefox 28 Release Notes

#99

Post by hobohacker »

wbond wrote: post #97
hobohacker wrote: post #92

Earlier quoted context omitted.

Speaking as a Chromium SPDY & HTTP/2 developer, we are very much focused on standardization. SPDY is an experimental protocol meant to drive the standards process, not become a de facto standard itself. Therefore, it's critical for us to kill off old SPDY versions. For more discussion on this topic, please refer to these discussion threads: https://groups.google.com/forum/#!topic/spdy-dev/_uvxTJkeCP0 https://groups.g…

Right, so my point stands that it is interesting that current stable browsers don't support current stable web servers. So unless someone has the resources to test and deploy unstable web servers, it effectively means you shouldn't bother with spdy at this point.

I think it's a fair assessment that supporting experimental technologies requires more engineering resources. Everyone has to do the cost/benefit analysis themselves.

Re: Firefox 28 Release Notes

#100

Post by mrinterweb »

From what I can tell about the exploits found at Pwn2Own, there were a total of 4 critical. Looks like FF28 addresses all 4. That was a very quick turnaround.

The fact that FF runs in a single process seems to be a major security issue since the web views are not sandboxed. I know Mozilla is working on their multiprocess project Electrolysis https://wiki.mozilla.org/Electrolysis that is experimental in FF 30. Hopefully, this project will help harden FF security.

Post reply on HN