Live data from Hacker News

Firefox 28 Release Notes

mozilla.org

131–140 of 164 posts

Re: Firefox 28 Release Notes

#131
post #87

Earlier quoted context omitted.

You can turn autosuggest off

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

Assign keywords to different search engines.

This lets you do queries like such:

Type "g hello" into the url bar - googles "hello"

wa integral from 0 to 1 of ln(x^4)dx - can be set to wolframalpha

w France - my wikipedia one

Re: Firefox 28 Release Notes

#132

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. Hopeful…

"The fact that FF runs in a single process seems to be a major security issue since the web views are not sandboxed."

Only to people who don't really understand security. This whole "multi process" "sandboxed" meme started by chrome guys has really got out of hand.

Re: Firefox 28 Release Notes

#133
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.

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?

I have custom search plugins for work stuff that are absolute lifesavers when combined with the following addons:

Context Search (adds a context menu dropdown when you right click highlighted text; think plaintext words you search in trouble ticket type stuff) https://addons.mozilla.org/en-US/firefox/addon/context-searc...

Add To Search Bar (adds an option to search-engine-ify any submit text box) https://addons.mozilla.org/en-US/firefox/addon/add-to-search... (might as well mention https://addons.mozilla.org/en-US/firefox/addon/organize-sear...)

Bonus productivity favorite: https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...

So yeah, you'll pry Firefox away from my cold dead hands.

Re: Firefox 28 Release Notes

#135
post #123
post #80

Earlier quoted context omitted.

This already work. Remove the separate search bar and you are ready to go.

If you remove the bar and press Ctrl+k you are taken to google in the current tab... not cool

But why would you press Ctrl+K if you've removed the search bar?

Re: Firefox 28 Release Notes

#137

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

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

This is why it surprised me that, as I understand it, the Firefox OS homescreen search bar seems to take exactly the opposite approach: every keystroke is sent to some obscure for-profit private company in Israel. Do you know what's up with that?

Re: Firefox 28 Release Notes

#138
post #115

Earlier quoted context omitted.

Er, I thought I was agreeing with you. What do you think I'm arguing? To be clear, I view these two statements as grounded in the same logic, although perhaps one is more strongly worded than the other: Yours - "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." Mine - "I think it's a fair assessment that supporting experime…

Let me rephrase then: Don't even bother building nginx 1.4 with spdy support or configuring it since no one can use it. From May 2013 until now there was a benefit to end-users. There no longer is. If you want to provide the speed benefits of spdy to users, you now need to run unstable nginx or mod_spdy.

Right. I think the point is that you shouldn't be relying on experimental standards for one's web architecture unless you recognize its experimental status.

Re: Firefox 28 Release Notes

#139

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. Hopeful…

> The fact that FF runs in a single process seems to be a major security issue since the web views are not sandboxed.

Running content in multiple processes, by itself, doesn't help security at all. It does help stability, since if one process crashes the rest of the browser need not; that's particularly important if running plugins like Flash, which crash in a stiff breeze. But if untrusted content manages to exploit a separate browser process that doesn't have any additional sandboxing applied, there's nothing standing between it and the rest of your system.

Additional security, however, comes from then applying sandboxing features to those separate processes, following the principle of least privilege.

Re: Firefox 28 Release Notes

#140
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…

The 'mainline' branch of nginx which supports spdy/3 is not considered unstable and can be used in production. Source: http://forum.nginx.org/read.php?2,221377,221390#msg-221390

Except when a security patch comes out and the API changed between security releases and you have to potentially update configuration and fix third-party modules.
Post reply on HN