Live data from Hacker News

Firefox 76

mozilla.org

111–120 of 274 posts

Re: Firefox 76

#111

> The shadow around the address bar field is reduced in width when a new tab is opened; I mean, at least they're trying, I guess. Still seems to me like lipstick on a pig. I'm still trying to figure out what UX problem the expanding bar was intended to address.

> I'm still trying to figure out what UX problem the expanding bar was intended to address.

Possibly the same as removing navigation arrows from the context menu if text is selected, i.e. to annoy long time Firefox users like me?

Certain features should be compile time options, default off and then we could make a UX-designer edition with all the crazy stuff just line we have developer edition.

Then I and everyone else could continue you use the old ux that actually worked very well ;-)

Re: Firefox 76

#112

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.

there's an artificial 500ms delay in there between fake data gen and chart drawing so it's easier for me to isolate the two in the perf timeline :)

> Would love to see how Safari handles your benchmark!

i don't have access to a Mac, so you won't get this from me!

Re: Firefox 76

#113

Earlier quoted context omitted.

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.

there's an artificial 500ms delay in there between fake data gen and chart drawing so it's easier for me to isolate the two in the perf timeline :) > Would love to see how Safari handles your benchmark! i don't have access to a Mac, so you won't get this from me!

Fair enough! Thanks anyway, though.

Re: Firefox 76

#114

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…

It seems that it's faster on every website I use except Gmail, Google Voice, and Youtube. I wonder whether Google is using some sort of Chrome-specific javascript to make those sites run faster in their own browser?

I'm not sure if this is still the case, but Youtube used to use WebComponents v0 which has to be emulated in JS in non-Webkit browsers, since only Google ever implemented v0, while everyone else agreed it required a bit more work, and other engines run v1 instead, which is not compatible.

Re: Firefox 76

#115

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…

It seems that it's faster on every website I use except Gmail, Google Voice, and Youtube. I wonder whether Google is using some sort of Chrome-specific javascript to make those sites run faster in their own browser?

It doesn't exactly need to be Chrome-specific; every browser/JS engine will have slightly different performance on different workloads, so Google just has to lean heavily on things that are golden-path for Chrome. They could even do this accidentally/nonmaliciously just by mostly testing on Chrome and not testing performance on other browsers.

Re: Firefox 76

#116

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…

It seems that it's faster on every website I use except Gmail, Google Voice, and Youtube. I wonder whether Google is using some sort of Chrome-specific javascript to make those sites run faster in their own browser?

I can corroborate this. YouTube especially.

Does anyone have any hard numbers to validate this? Or are we just random outliers?

Re: Firefox 76

#117

Earlier quoted context omitted.

Reddit was pretty annoyed too. I actually did a little real-life poll ( I admittedly might care about minute details too much!), and everyone was either indifferent or negative. Indifference was more common, but, is that really a good outcome? > Firefox simply wanted it to be more obvious that the address bar is in focus the moment you open a new tab. Is that it? Because I'm still trying to figure this out! I'm just…

Indifference shouldn't be surprising for a minute detail. I didn't even know about the feature until I saw this thread (clicking address bar expands it), since I normally immediately start typing once I open a new tab. I'd even argue that indifference should be the goal when making design changes; make subtle changes over time instead of the complete overhauls that are common today.

I totally agree, but only if there's also either (A) some people who actually like the change or (B) the change is addressing a specific UX problem.

If everyone is indifferent, why did you change anything?

Re: Firefox 76

#118

Earlier quoted context omitted.

It seems that it's faster on every website I use except Gmail, Google Voice, and Youtube. I wonder whether Google is using some sort of Chrome-specific javascript to make those sites run faster in their own browser?

I'm not sure if this is still the case, but Youtube used to use WebComponents v0 which has to be emulated in JS in non-Webkit browsers, since only Google ever implemented v0, while everyone else agreed it required a bit more work, and other engines run v1 instead, which is not compatible.

Youtube was updated to the v1 quite some time ago with a fresh Polymer version

>Polymer.version

3.4.0

Polymer uses v1 WCs since Polymer v2

Re: Firefox 76

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

I think it's an imitation. They're not stock UI elements. For example, on my Mojave system, if I just make an HTML button, I can see it doesn't respect the systemwide dark setting, the highlight color looks slightly darker than a normal light-theme button and it doesn't invert the text color when highlighted.

Re: Firefox 76

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

Search By Image: https://addons.mozilla.org/en-US/android/addon/search_by_ima...

Translate Now: https://addons.mozilla.org/en-US/android/addon/translate-now...

Post reply on HN