Which suggests a timing issue. Somebody is capturing the DOM before all the lazy-loaded stuff is added into the page. Then the offsets are captured from the fully-customized page and applied to the pre-customized cahced page.
Given the extremely dynamic nature of Discourse pages I’d expect this bug to manifest all over Discourse. Unless somehow there’s a narrow window of circumstances where the cached un-customized DOM isn’t updated and most sites happily (but only by luck) miss that small window.
@AHunter3 , it might be working properly for you, but your screenshots don’t show it. When I right-click, what I see looks correct. But when you hit ‘Look Up “expected”’, does it give you the definition of “expected”, or the definition of some other string?
The shadow DOM isn’t just the regular DOM though, but like… a portal into a mirror universe where Cthlulu is an enslaved web developer writing CSS inside one HTML tag for all eternity… or something like that.
Just about everything these days is lazy loaded and it’s usually fine, but most things don’t need to talk to the OS APIs the way “Look up” does. The shadow DOM is like another layer of sandboxing inside a custom HTML tag… not surprised it’s buggy.
Interesting. Maybe it only affects some versions of macOS? The developers would probably appreciate that info, if you cared. That bug has been around for a couple years and they don’t seem to be in any rush to fix it.
I tried everything to get this to fail, including that codeopen.io demo site, in Safari and Chrome, with adblocker disabled, and I couldn’t reproduce the buggy behavior.
