Live data from Hacker News

Chrome 77 Breaking Drag and Drop Events

bugs.chromium.org

81–90 of 194 posts

Re: Chrome 77 Breaking Drag and Drop Events

#81

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.

Is there a such plug-in?

You can do it in chrome dev tools. Just pick which one or put a custom one in.

Re: Chrome 77 Breaking Drag and Drop Events

#82
post #66
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…

Given that Chrome ended Opera, and is effectively ending IE/Edge, people really need to take pause and appreciate and be thankful that Firefox is still around. I think the "shady shit" Mozilla has pulled lately are death rattles. I certainly don't expect it to be around in another 5-10 years. Firefox's tiny market share is all that stands between all the W3C and WHATG publications going from "standards" to "what Chro…

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.

Re: Chrome 77 Breaking Drag and Drop Events

#83
> "I wish the reporter could elaborate more on whether there are live websites broken due to this or is it a project under development so we can measure the impact more."

(Quoted a comment from the thread on https://bugs.chromium.org/p/chromium/issues/detail?id=100574...)

Wasn't this specific version of Chrome rolling out to production users world-wide? Clearly there was a subset of users that was impacted by this (otherwise, a report wouldn't have been made in the first place). Not sure why they're asking the reporter about the state of their specific project?... :\

Re: Chrome 77 Breaking Drag and Drop Events

#84
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…

I switched back to Firefox from Chrome with the introduction of Firefox Quantum after years of failed attempts at switching back prior to that. Firefox really is first class again. I echo your suggestion to give it a try again.

Re: Chrome 77 Breaking Drag and Drop Events

#87
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…

Firefox could be a lot better with usability issues, too. They will agree on something being an issue and then let the ticket sit there for months and years, even if it's something that's easy to fix and should be prioritized.

If it's such an easy fix, then fix it.

If it's a js/css/html/xul-only fix (and chances are good it is, when it's a usability issue, as the frontend/UI code js on a high level), then you do not even have to really build Firefox but can use artifacts mode[1], which takes a few minutes for the initial build and only a few seconds for subsequent builds.

Then find a reviewer. I usually look at the recent activity of files I touch (or related files, or related bugs), find functional changes and just add whoever reviewed those most recent changes. Even easier when it's regressions, then you can see who reviewed the regressed changeset and who wrote it and CC them as well.

If the person(s) you picked do not want to review it or cannot review it, they will tell you, and usually suggest who else to ask. If this doesn't work, then you can always ask/nag on IRC.

[1] https://developer.mozilla.org/en-US/docs/Mozilla/Developer_g...

Re: Chrome 77 Breaking Drag and Drop Events

#88

Earlier quoted context omitted.

"should be prioritized" is a very subjective statement. Out of every 100 tickets, there is 50 people who believe theirs is the most important one. And we have over 200k tickets total (not all are bugs, many are resolved, but the scale is massive). If you think a bug is easy to fix, pleasez consider providing a patch.

I find it hard to believe you don't know that casually contributing to Firefox is ridiculously hard. The build system is borderline insane, building takes hours, and most importantly people who can approve your changes clearly have more important things to do and regularly fail to answer. I have tried contributing a couple of times. Thank you, no more.

Compared to other software of similar complexity I think standing up a Firefox build is actually pretty reasonable. The bootstrap instructions are not complicated (https://developer.mozilla.org/en-US/docs/Mozilla/Developer_g...) and the build takes about an hour on my laptop. Chrome is certainly a lot harder and takes significantly longer (if you lack access to Google's internal build farm). Likewise the Linux kernel is also tricky and slow to build the first time.

Re: Chrome 77 Breaking Drag and Drop Events

#89
post #88

Earlier quoted context omitted.

I find it hard to believe you don't know that casually contributing to Firefox is ridiculously hard. The build system is borderline insane, building takes hours, and most importantly people who can approve your changes clearly have more important things to do and regularly fail to answer. I have tried contributing a couple of times. Thank you, no more.

Compared to other software of similar complexity I think standing up a Firefox build is actually pretty reasonable. The bootstrap instructions are not complicated ( https://developer.mozilla.org/en-US/docs/Mozilla/Developer_g... ) and the build takes about an hour on my laptop. Chrome is certainly a lot harder and takes significantly longer (if you lack access to Google's internal build farm). Likewise the Linux kern…

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

Re: Chrome 77 Breaking Drag and Drop Events

#90
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…

> 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?
Post reply on HN