3 ms·
Read in another HN comment just the other day that the slowness was because they used some obsolete only-in-chrome shadow DOM API which "polyfilled" on all othe
by lostmyoldone 8y ago
Read in another HN comment just the other day that the slowness was because they used some obsolete only-in-chrome shadow DOM API which "polyfilled" on all other browser, which if true sounds exactly like pulling a Microsoft.
I haven't verified it myself and I couldn't find a reference with a quick search, so while it sounds plausible, it would be great to havd a credible source to refer to.
- tumetab1 8y agoSome kind of reference https://news.ycombinator.com/item?id=18053935 https://news.ycombinator.com/item?id=18053935
- the_duke 8y agoThis is not necessarily malicious though. Probably some in-house framework they use that happens to use this old browser API. And they haven't gotten around to fixing it. Of course it's also reasonable that nobody is pushing a fix up because it works fine on Chrome and that's what Google wants us to use.