Chrome 77 Breaking Drag and Drop Events • Hacker News Board

Re: Chrome 77 Breaking Drag and Drop Events

#171

Post by repolfx » Fri, Oct 11, 2019, 5:44 PM UTC

forgottenpass wrote: post #130

stefan_ wrote: 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.

That's the trend these days. Tomorrow everyone on Hacker News and Twitter will go back to chiding IT departments that want the ability to test software changes before they get deployed, or have the ability to roll back.

In fairness, when was the last time you read a story like this one?

Chrome updates constantly and regresses nearly never. It's actually impressive how rarely this happens given the complexity of HTML. Slow IT departments delaying useful upgrades is an everyday occurrence though.

Re: Chrome 77 Breaking Drag and Drop Events

#172

Post by eitland » Fri, Oct 11, 2019, 6:13 PM UTC

Insanity wrote: post #70

eitland wrote: post #69

Earlier quoted context omitted.

In the "Windows only" case it is kind of reasonable: supporting another platform takes work. When they are blocking other browsers explicitly despite the fact that the other platforms work that is a whole different level.

Well browsers with a different engine do work differently. By the way, I do disagree with this strategy. Just saying it is not necessarily something illegal.

Problem was in this case it seems the product works fine across different engines, they just decided it was ok to block a competing product to limit comsumer choices and generally make the web a worse place ;-)

Of course it doesn't have to be that black and white but they certainly makes it easy to dislike them at the moment.

Re: Chrome 77 Breaking Drag and Drop Events

#173

Post by eitland » Fri, Oct 11, 2019, 6:15 PM UTC

favadi wrote: post #71

eitland wrote: post #54

Earlier quoted context omitted.

How comes nobody has sued them over that yet?!!

Which rule they violated?

Abuse of dominant market position in one market (search) to push into other markets (browsers).

Re: Chrome 77 Breaking Drag and Drop Events

#174

Post by Marsymars » Fri, Oct 11, 2019, 6:49 PM UTC

The_rationalist wrote: post #36

js8 wrote: post #4

It seems like drag-and-drop is out of fashion. I think big reason is that it really cannot be done well on touch-screen devices and touchpads. I don't really complain, because I have always found d&d rather impractical (and it's also terrible for accessibility); unfortunately, there are some applications that still rely on it a lot. (As an aside, what bothers me more that the right-click menu goes out of fashion. Tha…

How to move cards on a Kanban (say Trello) without drag and drop?

My preference would be something like arrow keys move the card selection, while holding ctrl + arrow keys moves the selected card.

Re: Chrome 77 Breaking Drag and Drop Events

#175

Post by magicalist » Fri, Oct 11, 2019, 6:53 PM UTC

eitland wrote: post #173

favadi wrote: post #71

Earlier quoted context omitted.

Which rule they violated?

Abuse of dominant market position in one market (search) to push into other markets (browsers).

Skype is a Microsoft product, though?

Re: Chrome 77 Breaking Drag and Drop Events

#176

Post by cpeterso » Fri, Oct 11, 2019, 7:06 PM UTC

commoner wrote: post #44

crazysim wrote: post #24

Earlier quoted context omitted.

At this rate, how long until Firefox does a "Like Chrome" in its UA?

Mozilla is developing an add-on called Go Faster that uses WebCompat data to adjust settings in Firefox for compatibility on poorly tested sites. https://github.com/mozilla/webcompat-addon https://wiki.mozilla.org/Compatibility/Go_Faster_Addon/Overr... https://webcompat.com/

Firefox already ships some UA overrides. You can see the list of active overrides (with links to bug reports explaining each) in Firefox's about:compat page.

Re: Chrome 77 Breaking Drag and Drop Events

#177

Post by throwaway_bad » Fri, Oct 11, 2019, 7:23 PM UTC

stefan_ wrote: post #169

Waterluvian wrote: post #11

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 synchronizati…

> Chances are if you are calling getImageData regularly, you are doing something wrong and inefficient.

I would love to see stats on the use cases. Personally I have never used canvas other than to getImageData in a loop!

If I only needed to draw primitives, SVG is often a better choice.

If I needed something GPU accelerated, I would switch to webgl and write shaders.

So the only thing left 2D canvas is good for is to get the pixel data to do image processing on (e.g., flood fill connected components, color histograms, etc).

Re: Chrome 77 Breaking Drag and Drop Events

#178

Post by onion2k » Fri, Oct 11, 2019, 7:30 PM UTC

mcintyre1994 wrote: post #137

onion2k wrote: post #29

Earlier quoted context omitted.

... and this, reader, is why we have end-to-end testing.

Probably more a case of me never having tried than anything else because I'm sure someone will have solved it, but end-to-end testing of drag and drop sounds pretty hard.

It isn't. Jest and Puppeteer are my current choice, and it's really just a matter of sending mousedown, mousemove, and mouseup events to the browser and checking the expected behaviour is right.

It makes a huge difference to how long you send testing manually.

Re: Chrome 77 Breaking Drag and Drop Events

#179

Post by bwat49 » Fri, Oct 11, 2019, 8:00 PM UTC

ChristianBundy wrote: post #154

senorjazz wrote: post #118

Earlier quoted context omitted.

> Bundling Pocket Why is that a problem? I never got the furore over it. When it appeared, I removed the icon and just went about my business. Annoying yes, but certainly not "shady". From what I understood / stand it was a mozilla app they included with the browser, not that different to how firefox comes with a bookmarks app.

It should be mentioned that it also adds articles to your new tab page, which is possible to remove but not easy for most people.

> it also adds articles to your new tab page, which is possible to remove but not easy for most people

It's two clicks.

Re: Chrome 77 Breaking Drag and Drop Events

#180

Post by BowBun » Fri, Oct 11, 2019, 8:17 PM UTC

jdnenej wrote: post #55

dmix wrote: post #8

Earlier quoted context omitted.

Agreed, it's a much harder problem to get right than it looks on the surface "sure I can add drag & drop easily!". Like a lot of things in software...

You can add drag and drop quite easily if you use a library for it.

To add to sibling's point, many drag-drop libraries work great on a bare demo website with nothing else to worry about.

Once you start trying to add it to your frontend with other complex features already there, you're back having to reason about the core of drag-and-drop and essentially solving it yourself to parse the library's code. In my experience I've had to modify library code to handle my requirements most of the time because it did not play well in a complex environment.