-
@tmcw @pfrazee @odbol Wow, good find. That’s surprising behavior (to me at least) that you unearthed there. I’ll have a very close look tomorrow. I’d give this bug a solid 10/10 to be honest. (Thanks, @RReverser, for looping me in.)Permalink On twitter.com
❤️ 2 Favorites Mood +13 🙂
-
@tmcw @pfrazee @odbol @RReverser As promised looked into this. I've created a reduced reproduction case (heady-flame-editor.glitch.me/) that I've also linked in a Chromium bug (bugs.chromium.org/p/chromium/issues/detail?id=1287459)—where I'm not sure if it's a bug indeed or just unintuitive. For now the article's fixed via github.com/GoogleChrome/web.dev/pull/7173.On twitter.com
-
@tmcw @pfrazee @odbol @RReverser Quick update here: It's not a bug, just a gotcha. The great @jaffathecake has summarized the situation in his bug comments: crbug.com/1287459#c1. (I have updated the documentation fix PR accordingly: github.com/GoogleChrome/web.dev/pull/7173.)Permalink On twitter.com