Live data from Hacker News

Firefox 76

mozilla.org

161–170 of 274 posts

Re: Firefox 76

#161
post #127
post #84

Earlier quoted context omitted.

They are not OS-native, but they use OS theming information.

Right. Browsers can't use the OS control implementations, because the demands of DOM/CSS simply can't be handled by those native implementations. But Firefox is trying to emulate the look and feel of the OS controls, using native theme drawing APIs when possible. It is very hard to get 100% right, which is why no browser does.

> Browsers can't use the OS control implementations, because the demands of DOM/CSS simply can't be handled by those native implementations. [...] It is very hard to get 100% right, which is why no browser does.

This is not correct. In instances where CSS doesn't affect the styling of the control, the browser can use native controls. As far as I know, every browser _except_ Firefox does this. For example, elements in Chrome and Safari are native elements (albeit Win32 versions in the former on Windows).

Re: Firefox 76

#162
post #102

There are 2 things I miss from switching to FF: Right click on a picture -> search google for image Right click -> Translate page Everything else seems smooth enough.

I really miss being able to search youtube quickly by opening a new tab, typing `you`, and hitting tab to query inline.

Re: Firefox 76

#164
post #79

Earlier quoted context omitted.

> The underlying problem is Windows suggesting Windows 98 styled buttons I'm almost positive that Firefox doesn't use OS-native controls; they've specifically styled their controls to look the way they do, so yes, this is a Firefox problem, not a Windows problem.

Really? The reason I assumed otherwise is that, the buttons on Mac look like Mac buttons to me. And furthermore, the buttons on my Mavericks Mac (pre Apple's flat redesign) look different than the ones on my High Sierra Mac.

Safari on windows were showing osx-styled default buttons, so I think safari also implement their own UI controls, not using system's ui elements.

Re: Firefox 76

#165

Earlier quoted context omitted.

In the last update (75) I had this bizarre problem that any amazon.co.uk links in my history weren't showing up in the "most used links" that the url bar is usually populated with if you click the down arrow (or in this update where the down arrow used to be) I have a browser profile that is used almost exclusively for amazon content as well. The most visited links in that profile are amazon.co.uk and prime video but…

Wow that's sad. Firefox's URL bar completion behaviour was one of its biggest advantages over Chrome. I wonder what the logic behind changing it is, and if it will lose that edge.

Well, not strictly the completion - it's the behaviour when you click on the urlbar before typing anything.

Normally (in my setup) it shows a list of "most visited" urls.

The new behaviour is to still show this list but omit any amazon.co.uk (and maybe other, I have no idea) urls.

Completion works as expected as far as I know.

Re: Firefox 76

#166

Earlier quoted context omitted.

In the last update (75) I had this bizarre problem that any amazon.co.uk links in my history weren't showing up in the "most used links" that the url bar is usually populated with if you click the down arrow (or in this update where the down arrow used to be) I have a browser profile that is used almost exclusively for amazon content as well. The most visited links in that profile are amazon.co.uk and prime video but…

File a bug.

I probably should, but I'd half expect to be told that this is intended behaviour due to some "clever" feature that knows better than I do how I want to use my browser.

Re: Firefox 76

#167

i just want to say, Firefox is seriously fast now, while Chrome continues to get slower [1]. my 10M datapoint uPlot benchmark runs in half the time, for both pure js (fake data gen) and canvas workloads (chart rendering). check out the console in [2]. however, i'm still waiting for the performance assessment in devtools to improve so i can get an easy summary as i can in Chrome. also, better default form input stylin…

Would love to see how Safari handles your benchmark! I find it pretty fast, but maybe that's just bias because it treats my battery nice.

I ran three trials of each on a min spec 2019 MacBook Pro 16". All numbers are ms rounded to the nearest integer, all browsers are latest stable. I also loaded the page with dev tools closed since that affected times.

Browser: (trial 1 prep, trial 1 chart), (trial 2 prep, trial 2 chart), (trial 3 prep, trial 3 chart)

Chrome: (649, 347), (638, 343), (618, 358)

Firefox: (353, 307), (358, 307), (361, 308)

Safari: (281, 264), (287, 258), (309, 262)

Re: Firefox 76

#168
post #162
post #102

There are 2 things I miss from switching to FF: Right click on a picture -> search google for image Right click -> Translate page Everything else seems smooth enough.

I really miss being able to search youtube quickly by opening a new tab, typing `you`, and hitting tab to query inline.

You can do better than that, you can add custom search engines for most search bars on the web, triggered by key words.

Just go to Youtube.com, right click the search box and click the "add keyword" menu item. Then choose a keyword you want to use to trigger a Youtube search (I use yt) and confirm.

After that you can search Youtube from anywhere by just typing "yt cute kittens" in the address bar and hitting enter.

Re: Firefox 76

#169
post #127

Earlier quoted context omitted.

Right. Browsers can't use the OS control implementations, because the demands of DOM/CSS simply can't be handled by those native implementations. But Firefox is trying to emulate the look and feel of the OS controls, using native theme drawing APIs when possible. It is very hard to get 100% right, which is why no browser does.

Huh. I wonder if that applies even to Safari on Mac and iOS, given how integrated Apple likes to be with their UI controls.

Some of them are native, if you don't style them.

Re: Firefox 76

#170

Earlier quoted context omitted.

Really? The reason I assumed otherwise is that, the buttons on Mac look like Mac buttons to me. And furthermore, the buttons on my Mavericks Mac (pre Apple's flat redesign) look different than the ones on my High Sierra Mac.

Safari on windows were showing osx-styled default buttons, so I think safari also implement their own UI controls, not using system's ui elements.

Safari buttons on macOS are native unless you style them in a way that causes their font or size to change.
Post reply on HN