TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Chrome 77 Breaking Drag and Drop Events

219 点作者 ardenpm超过 5 年前

22 条评论

sgentle超过 5 年前
If I&#x27;m reading the issue thread correctly, it seems that a big revision of the hit testing code was being field trialled (ie enabled for 1% of stable users) and a fix to that code in Chrome 77 caused a bug for the other 99%. Unfortunately, this new bug was only discovered partway through version 77&#x27;s rollout.<p>So now there&#x27;s a bit of a pinch: revert the fix (and break it for the 1%), or leave it (break it for the 99%). Presumably, you could disable the field trial AND revert the fix at the same time, but that wasn&#x27;t considered. I&#x27;m not sure why, but my guess would be that it&#x27;s a pain in the butt to coordinate both rollout systems.<p>Obviously the right answer is to make a new fix that doesn&#x27;t break things for any users, but fixes take time and the release was already halfway rolled out. I think that&#x27;s where the discussion about impact came from, and the initial assessment was that it wouldn&#x27;t break much stuff, so the fix was bumped to the next release (Chrome 78).<p>However, after lots of people jumped on the issue tracker to say it did, in fact, break a bunch of stuff, Chrome 77 was re-released (&quot;respun&quot;) with the new fix included.<p>So, broadly speaking, I think the decisions here made sense under the assumption that it was a small-impact issue. My main criticism would be that there must be a more effective way to estimate impact than waiting for people to complain in the bug tracker.<p>One approach would be some kind of reverse integration testing system. ie, if you have a critical app or library that depends on Chrome, there should be some way of submitting your tests so that the Chrome team can estimate the impact of changes and find out more easily if they&#x27;ll break anything unexpected.<p>Rust does this with a system called Crater: <a href="https:&#x2F;&#x2F;rust-lang.github.io&#x2F;rustc-guide&#x2F;tests&#x2F;intro.html#crater" rel="nofollow">https:&#x2F;&#x2F;rust-lang.github.io&#x2F;rustc-guide&#x2F;tests&#x2F;intro.html#cra...</a><p>And apparently Yocto has something similar: <a href="https:&#x2F;&#x2F;lwn.net&#x2F;Articles&#x2F;788626&#x2F;" rel="nofollow">https:&#x2F;&#x2F;lwn.net&#x2F;Articles&#x2F;788626&#x2F;</a>
评论 #21224320 未加载
ardenpm超过 5 年前
Spent half the morning trying to work out why drag and drop events were not working properly in code that was working fine and deployed for nearly a year. Finally tracked it down to this obscure bug in Chrome 77 which re-orders drag and drop events but only when your page is inside an iframe that is hosted on a different domain. Looking at the report it looks like this has broken a lot of peoples applications and likely a lot more that haven&#x27;t yet worked out this is the reason. Looks like a fix is coming in 78 fortunately.
评论 #21221638 未加载
评论 #21222866 未加载
评论 #21222535 未加载
egeozcan超过 5 年前
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.<p>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 issue doesn&#x27;t affect Google, it will likely be deprioritized a lot.<p>I&#x27;m not a self-acclaimed internet freedom fighter, I&#x27;m actually very pragmatic, and I&#x27;d still humbly suggest everyone to give Firefox a try.
评论 #21222631 未加载
评论 #21221845 未加载
评论 #21223013 未加载
评论 #21223201 未加载
评论 #21222363 未加载
评论 #21222754 未加载
评论 #21221950 未加载
评论 #21221787 未加载
评论 #21222162 未加载
评论 #21221821 未加载
评论 #21226052 未加载
评论 #21226204 未加载
评论 #21222324 未加载
评论 #21222167 未加载
评论 #21223646 未加载
评论 #21222279 未加载
评论 #21223907 未加载
stefan_超过 5 年前
Love the random comments in the bug tracker. &quot;We have an enterprise-level software affected, what is the ETA?&quot;<p>Lots of folks just figuring out web apps don&#x27;t run in a metaspherical happy place or &quot;the cloud&quot;, no, they run on fucking Chrome and you are not paying for it.
评论 #21226484 未加载
评论 #21224640 未加载
yreg超过 5 年前
I find the tone the maintainers used when talking to reporters interesting.<p>&gt;[Do you have a] live website or is it a project under development? […] We will fix the issue for 78 if that is alright with you.<p>or<p>&gt;Are they going to upgrade to 77? Enterprise customers usually only upgrade if things are alright.<p>As if the reporter&#x27;s apps were more special than the thousands of other websites that it broke.<p>And I don&#x27;t mean this in a negative way, I&#x27;m just surprised.
评论 #21223127 未加载
wazoox超过 5 年前
Funny, my company has been developing an application that suddenly behaved bizarrely in Chrome 76 (some divs were constantly jumping up and down the page, augh). We pulled our hair on this problem for a week, then suddenly Chrome 77 corrected that... But apparently it&#x27;s broken elsewhere?
Waterluvian超过 5 年前
I&#x27;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&#x27;t seem to stop and consider what effect it might have on major libraries and applications.<p><a href="https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=1001845" rel="nofollow">https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=100184...</a>
评论 #21226369 未加载
评论 #21228510 未加载
评论 #21222040 未加载
评论 #21222859 未加载
cuddlecake超过 5 年前
Just realized that I never use the drag and drop I implemented in my application.<p>Wonder if it actually still works.
评论 #21222066 未加载
greggman2超过 5 年前
While we&#x27;re on Chrome bugs am I the only person in the world running into this bug in Chrome that makes it DOS the entire machine? You can repo on an NVidia MacBook Pro. Go to stackoverflow, try to make a new code snippet it (click the snippet button in the toolbar), then try typing in the snippet (hold a letter key and watch it repeat). You should notice some bug related to drop shadows ends up DOSing the GPU and the entire system runs slow. The bug has existed since around June. They claim to be trying to fix it, or rather ship the fix that already exists but needs testing, but I&#x27;m just surprised I seem to be the only person who runs into the issue. (The subset of people who write snippets on stackoverflow on an NVidia MacBook Pro). No idea what other sites are affected. If more sites are affected that would raise the priority for fixing. If most people are not affected then it&#x27;s reasonable it&#x27;s not a high priority.
newnewpdro超过 5 年前
I had to fire up Epiphany recently just to do drag-n-drop graphics assets management in the Steam app admin page.<p>Both Firefox and Chromium were broken, when I contacted Steam&#x27;s support they said I am the only person having problems.<p>When I dug into the failure a bit in Firefox the object coming with the event was always NULL, and searches turned up a bunch of results from web devs struggling with the same problem in various ways.<p>I&#x27;m glad Epiphany worked, so I could promptly forget it all and get on with my life. Presumably it&#x27;s still broken for steam app devs however. It escapes me why Valve doesn&#x27;t have a simple file browser button fallback for when this crap doesn&#x27;t work.
tiglionabbit超过 5 年前
The way Chrome displayed flexbox stuff permanently changed at some point after version 70, breaking an app of mine that had been working fine for years.
uasm超过 5 年前
&gt; &quot;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.&quot;<p>(Quoted a comment from the thread on <a href="https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=1005747" rel="nofollow">https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=100574...</a>)<p>Wasn&#x27;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&#x27;t have been made in the first place). Not sure why they&#x27;re asking the reporter about the state of their specific project?... :\
williamstein超过 5 年前
For the last few weeks, Chrome 77 breaks very badly when there are more than 255 failed websocket attempts: <a href="https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=1006243" rel="nofollow">https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=100624...</a> Even refreshing the page doesn&#x27;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&#x27;ve also been getting reports of this other websocket connection issue breaking SPA&#x27;s.
muststopmyths超过 5 年前
I have a very old Macbook that I keep around for occasional use. The latest version of Chrome has a serious performance problem with it. Every click on a web site brings up the spinning cursor and there are several seconds of latency. Safari on the same computer has no such problem, so it&#x27;s not the age of the machine.<p>I reported the issue, after navigating several-second UI lag, but not holding my breath for them to fix something on an old OS&#x2F;hardware.<p>It seems like every release of a Google product(the ones that I use anyway, gmail, Chrome, Voice) brings some downside&#x2F;regression.<p>Can anyone recommend script blockers for Safari ? It was the main reason to use Chrome for me.
js8超过 5 年前
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&#x27;t really complain, because I have always found d&amp;d rather impractical (and it&#x27;s also terrible for accessibility); unfortunately, there are some applications that still rely on it a lot.<p>(As an aside, what bothers me more that the right-click menu goes out of fashion. That I feel is a bigger usability problem.)
评论 #21221651 未加载
评论 #21222044 未加载
评论 #21223683 未加载
评论 #21224319 未加载
评论 #21222132 未加载
评论 #21221830 未加载
shadowgovt超过 5 年前
It looks like they were able to back-port the fix for this into Chrome 77. Hopefully, the issue won&#x27;t stay live too long.
dmix超过 5 年前
Chrome Canary is currently 79.0. The mainline version is 77.<p>Edit: I wasn&#x27;t able to reproduce in either, didn&#x27;t dig into why
评论 #21221812 未加载
bibinou超过 5 年前
fixed in 77.0.3865.120
est超过 5 年前
After the Chromium removed chrome:&#x2F;&#x2F;net-internals&#x2F;, the browser is not worth it anymore.
评论 #21223128 未加载
asdf12346超过 5 年前
How is that even possible that bugs like that made it to production?<p>They do not write tests or something?
评论 #21226319 未加载
oldmanthrowit超过 5 年前
Why does anybody still use Chrome? Really, Google is a criminal data theft organization.<p>Why not just take all of your browsing data and publish it online, skip the middle man?
评论 #21226327 未加载
safeplanet-fesa超过 5 年前
Jokes on them, I still use Chromium 67 from chromium.woolyss.com. It&#x27;s the last version before WebRTC became unremovable. Now it&#x27;s impossible to download this version, only the new ones. Woolyss should have kept it, like they keep Chromium 49, the last version before Chromium stopped running on XP and Vista. And I understand the risks of running an obsolete version, but it&#x27;s a trade-off. For some time I was thinking of updating it, but then Google came up with lots of anti-consumer browser-crippling features.
评论 #21223275 未加载