Chrome 77 Breaking Drag and Drop Events • Hacker News Board

Re: Chrome 77 Breaking Drag and Drop Events

#131

Post by Guidii » Fri, Oct 11, 2019, 2:30 PM UTC

egeozcan wrote: post #113

hu3 wrote: post #108

Earlier quoted context omitted.

And this is why I take rants against Google and MS with a grain of salt. Top voted comment couldn't bother to read bug report. I often see inconvenient truths buried in downvotes meanwhile misinformation that apeases a vocal minority gets catapulted to the top.

I've read the report. I knew about the merge. This issue has been postponed until developers started reacting aggressively, so breaking all drag and drop in iframes was nearly okay until a new version was published. When the issue is affecting users, it gets worse: The small number of them who could navigate their way into creating a chromium bug report will be waved away. I'm also not a comment, I'm a person. Thank…

The reported issue was addressed within 21 days.

I'm not sure that this issue illustrates the case you're trying to make here.

Re: Chrome 77 Breaking Drag and Drop Events

#132

Post by williamstein » Fri, Oct 11, 2019, 2:33 PM UTC

For the last few weeks, Chrome 77 breaks very badly when there are more than 255 failed websocket attempts: https://bugs.chromium.org/p/chromium/issues/detail?id=100624... Even refreshing the page doesn't workaround the problem (you have to open a new tab). This has been causing a lot of trouble for long running single page applications that use websockets. Fortunately, a fix is being rolled out right now for Chrome. We've also been getting reports of this other websocket connection issue breaking SPA's.

Re: Chrome 77 Breaking Drag and Drop Events

#133

Post by egeozcan » Fri, Oct 11, 2019, 2:39 PM UTC

Guidii wrote: post #131

egeozcan wrote: post #113

Earlier quoted context omitted.

I've read the report. I knew about the merge. This issue has been postponed until developers started reacting aggressively, so breaking all drag and drop in iframes was nearly okay until a new version was published. When the issue is affecting users, it gets worse: The small number of them who could navigate their way into creating a chromium bug report will be waved away. I'm also not a comment, I'm a person. Thank…

The reported issue was addressed within 21 days. I'm not sure that this issue illustrates the case you're trying to make here.

I respectfully disagree: Try to explain your users that they won't get drag and drop for 21 days. This would have been worse if there weren't passionate people aggressively following it.

A Google account integration issue would always be more important than web pages being broken in many subtle ways. This wasn't the case when they didn't hold the browser monopoly.

Re: Chrome 77 Breaking Drag and Drop Events

#134

Post by lultimouomo » Fri, Oct 11, 2019, 2:41 PM UTC

hvis wrote: post #121

lultimouomo wrote: post #89

Earlier quoted context omitted.

I have found contributing to the linux kernel a significantly more pleasant experience than contributing to Firefox. I have no trouble believing that contributing to Chrome is even harder, but then again I didn't hear someone from Google saying "If you think a bug is easy to fix, pleasez consider providing a patch."

> then again I didn't hear someone from Google saying ... Is that a good thing?

I mean, Google doesn't even pretend to be open to community contributions. Pretty much every choice they make is tailored to googlers only, just look at their build systems. They're upfront about it which I think prevents me from complaining about how hard is to contribute.

I'll take Mozilla over Google every day, but if Mozilla presents itself as open to community, it also lends itself to criticism that Google avoids altogether.

Re: Chrome 77 Breaking Drag and Drop Events

#135

Post by [deleted] » Fri, Oct 11, 2019, 2:47 PM UTC

dpifke wrote: post #115

rkangel wrote: post #104

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…

[deleted]

Re: Chrome 77 Breaking Drag and Drop Events

#136

Post by dangerface » Fri, Oct 11, 2019, 2:50 PM UTC

dpifke wrote: post #115

rkangel wrote: post #104

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…

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

If you live in the US or EU your ISP logs dns queries and sells them on [0] encryption is the only solution.

[0] https://www.ispreview.co.uk/index.php/2019/04/big-uk-broadba...

Re: Chrome 77 Breaking Drag and Drop Events

#137

Post by mcintyre1994 » Fri, Oct 11, 2019, 2:53 PM UTC

onion2k wrote: post #29

cuddlecake wrote: post #18

Just realized that I never use the drag and drop I implemented in my application. Wonder if it actually still works.

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

Re: Chrome 77 Breaking Drag and Drop Events

#138

Post by kragen » Fri, Oct 11, 2019, 2:53 PM UTC

senorjazz wrote: post #118

SmellyGeekBoy wrote: post #107

Earlier quoted context omitted.

Bundling Pocket, resetting default search provider back to Google on updates. Just a couple off the top of my head. I'm a long-time Firefox user, FWIW.

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

Originally it was a proprietary program from a for-profit company. That's why people got upset.

Re: Chrome 77 Breaking Drag and Drop Events

#139

Post by dmix » Fri, Oct 11, 2019, 2:54 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.

That’s exactly what you think going in...that’s the point I’m making.

No one is hand rolling drag and drop these days.

There’s a lot of complexity implementing drag and drop both visually and binding stuff to events. It’s messy and finicky. Unless your usecase is very simple.

Re: Chrome 77 Breaking Drag and Drop Events

#140

Post by cptskippy » Fri, Oct 11, 2019, 2:57 PM UTC

dpifke wrote: post #115

rkangel wrote: post #104

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…

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?