Live data from Hacker News

Chrome 77 Breaking Drag and Drop Events

bugs.chromium.org

161–170 of 194 posts

Re: Chrome 77 Breaking Drag and Drop Events

#161
post #153

Earlier quoted context omitted.

Your complaint is about a Web Extension Experiment that they're currently testing and not a feature they have shipped in the browser. It seems like this isn't shady at all, but rather they're testing something and soliciting feedback. You provided some and they responded that they plan to write a blog post about it. So what's shady here? That the process is working?

My understanding is that this is how it's being rolled out, eventually to 100% of users: https://blog.mozilla.org/futurereleases/2019/09/06/whats-nex...

I still don't think its shady. Mozilla have publicly stated that its possible to change the DOH provider, and furthermore they have clearly laid out their requirements for Cloudflare to participate in this experiment. This seems like a good compromise in order to force other providers to start encrypting dns requests.

Re: Chrome 77 Breaking Drag and Drop Events

#162
post #9

I switched to Firefox after they stopped caring about usability issues (like right clicking without releasing left mouse button deselects the text since v fifty-something on windows), the difficulties they created for ad blockers, the account integration fiasco, and so on. I know this particular bug seems to be an edge case that may happen with every browser, but when you are using Chrome, you should know that if an…

Subjectively, most of the performance regressions I've had have been in Firefox, sadly. They had an issue that absolutely torpedoed flexbox performance for quite some time, for example. It has since been resolved, but it's still the leading cause of performance complaints I see from my users.

Re: Chrome 77 Breaking Drag and Drop Events

#163
post #93

Earlier quoted context omitted.

Why would they ever do an IE6? They don't want to cripple the web as an application platform as MS did but move as much things as possible onto it.

"Doing an IE6" for Google would be quite different from what Microsoft did, who wanted the desktop to stay relevant. For Google the web is just an advertisement platform. If/When Firefix is gone, they will hold all the cards. "Doing an IE6" might mean removing support for ad-blockers. Or making Google DNS mandatory. Or have everything you do on the web be phoned to Google, to improve your advertising experience. Assu…

> the web is just an advertisement platform

And a key UI target for a huge chunk of their applications and services, including search.

If "web browsing" doesn't work in Chrome, that's kind of a big deal for Google.

Re: Chrome 77 Breaking Drag and Drop Events

#164
post #115

Earlier quoted context omitted.

> I think the "shady shit" Mozilla has pulled lately are death rattles. Would you mind briefly elaborating on this? I wasn't aware that Mozilla had done anything apart from behave well.

How about enabling DNS-over-HTTPS, which routes your entire browsing history to a third party, based on selections labelled "OK, Got It" and "Disable Protection": https://github.com/mozilla/doh-rollout/issues/125 Don't get me wrong, DoH is great if you have a shady ISP. But it should be opt-in, not opt-out, since those of us who don't have shady ISPs don't want all our DNS queries centralized in the same place, to be…

"OK, Got It" and "Disable Protection" is pretty accurate.

It's inconvenient, but it turns out the "open, anonymous" web has huge trust issues that bad actors use to exploit and attack the unknowing. Some of that is most readily solved by nudging users to trusted third-parties.

You can have issue with whether that third party should be trusted, but the larger issue is that the user has to trust some third party for DNS to work at all, and most don't even think twice about that question.

> since those of us who don't have shady ISPs don't want all our DNS queries centralized

If you don't hae a shady ISP, disable protection. You're already protected by your ISP not being shady, right? ;) The average user has no idea if they should trust their ISP's DNS.

Re: Chrome 77 Breaking Drag and Drop Events

#165
post #77

After the Chromium removed chrome://net-internals/, the browser is not worth it anymore.

Wow, why on earth did they do this!? Are they trying to hobble devs working with their browser?

There's a good breakdown of the decision here [https://bugs.chromium.org/p/chromium/issues/detail?id=892453].

The short version is that the value to devs was offset by the cost borne by every user (those components were in the binary even if they were never used, and they pulled in libraries that weren't used by anything else) and the increased attack surface of having that tool in place.

Re: Chrome 77 Breaking Drag and Drop Events

#166

How is that even possible that bugs like that made it to production? They do not write tests or something?

The combinatorics of browser features described by the standards are not unit-testable in the scale of human lifetimes.

That having been said, if they didn't have a test for this situation before, I assume they do now. ;)

Re: Chrome 77 Breaking Drag and Drop Events

#167

Why does anybody still use Chrome? Really, Google is a criminal data theft organization. Why not just take all of your browsing data and publish it online, skip the middle man?

It's real convenient to have all my browser preferences follow me when I boot up my browser on another computer.

Re: Chrome 77 Breaking Drag and Drop Events

#168

Earlier quoted context omitted.

> I'd still humbly suggest everyone to give Firefox a try. I usually suggest die-hard Chrome users use a plugin to spoof their user agent so product managers and developers are more likely to tread non-Chrome as a first-class browser.

I guess it's better than nothing but 1.) it will cause pages (especially some Google properties) to deliver unoptimised versions meant for the real Firefox (or more generally non-Chrome browsers), and 2.) don't sophisticated websites and apps anyway ignore user-agent string and directly probe through JS?

As they should...but often don't (see unoptimized versions to your own comment).

Re: Chrome 77 Breaking Drag and Drop Events

#169

I've been dealing with a massive performance regression in the canvas API. The frustrating bit is that they were well aware of the cost and made the change anyways. They didn't seem to stop and consider what effect it might have on major libraries and applications. https://bugs.chromium.org/p/chromium/issues/detail?id=100184...

No, you are just not understanding the tradeoff. They fixed some canvas not being accelerated when they should have been. This means they can be hardware composited, drawn to and need to only exist once as a GPU texture. This is a massive win for performance and power consumption.

Here is what is not efficient, ever: getting a GPU texture into a raster format CPU accessible buffer. At best this requires synchronization and a full memory copy into a new buffer, but it can easily be much much more expensive because GPUs, and mobile GPUs basically never, store textures in raster formats. So now you need a full copy and a bunch of extra SIMD to convert it from the GPU preferred format into raster format for your getImageData call.

And all this for what is essentially a trap API! Chances are if you are calling getImageData regularly, you are doing something wrong and inefficient.

Re: Chrome 77 Breaking Drag and Drop Events

#170
post #98

Love the random comments in the bug tracker. "We have an enterprise-level software affected, what is the ETA?" Lots of folks just figuring out web apps don't run in a metaspherical happy place or "the cloud", no, they run on fucking Chrome and you are not paying for it.

The problem is, they should be running in browsers that support standards, and then if one browser doesn't work you just use another one.

The monoculture is more of a problem here than having browser-hosted UIs to enterprise software.

Post reply on HN