Earlier quoted context omitted.
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.
dude! :D
Firefox 28 Release Notes
121–130 of 164 posts
Re: Firefox 28 Release Notes
#122Re: Firefox 28 Release Notes
#123Re: Firefox 28 Release Notes
#124Re: Firefox 28 Release Notes
#125Earlier quoted context omitted.
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.
Can you explain why you want window manager features in your browser? If you use windows-in-a-virtual-desktop instead of tabs-in-a-window, they're LRU by default on pretty much every OS.
Because I rarely dedicate a virtual desktop to Firefox alone, and I enjoy the flexibility of a deeper hierarchy (virtual desktops - windows - tabs). Everyone has their own needs and usage patterns. Are you also opposed to file browser and terminal window tabs?
Re: Firefox 28 Release Notes
#126Earlier 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.
Thanks glad to see an explanation and a good one too.
Re: Firefox 28 Release Notes
#127Firefox should allow you to type "45/3" in the address bar and be taken to Google with the calculation.
If you type "45/3=" into the search bar and it will return the result without having to load the google page.
Re: Firefox 28 Release Notes
#128Eagerly 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 the omnibar add on and have Firefox (nightly actually) configured so that searches in the bar first look at bookmarks and the history. If nothing shows up there, then it searches DuckDuckGo, and if I don't see anything there, I fall back to Google.
Re: Firefox 28 Release Notes
#129Earlier quoted context omitted.
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.
Can you explain why you want window manager features in your browser? If you use windows-in-a-virtual-desktop instead of tabs-in-a-window, they're LRU by default on pretty much every OS.
Unfortunately I cannot really justify my interest in philosophical or design-oriented terms. I had simply gotten used to the tab switching behavior in Opera, and have missed that behavior a great deal since having to switch (for reasons that should be obvious).
Re: Firefox 28 Release Notes
#130Earlier quoted context omitted.
Anyone have a good breakdown of the differences in these benchmarks? i.e. Why does Chrome dramatically lead the(ir) Octane benchmark?
Because Octane was written by Google. So it's either: -representative of things Google knows it's faster at -representative of things Google thinks should be fast and prioritizes... and is thus faster. or a little of column A little of column b in a feedback loop.
Octane is the continuation of V8 benchmark (and contains all of the V8 benchmark tests) — V8 (the JS engine) was specifically designed to provide good performance on those tests (this is why V8 had a generational GC from launch, for example; though somewhat amusing last I checked Carakan (Opera/Presto's last JS engine) was quickest at splay, primarily a GC benchmark, despite having a very naïve GC!). The tests new in Octane don't display such a clear disparity, as V8 wasn't designed for them.