News for hackers. Stuff that matters.

A comment on JavaScript performance, WebAssembly, and Shared Memory in Microsoft Edge. Parent comment

Re:JavaScript performance, WebAssembly, and Shared Memory in... by pcwalton on Thursday April 20, 2017 @04:53PM (#14160759)
> In our current code base we have more workarounds for FF bugs than any other browser, and some of them are pretty nasty. e.g. monkey patching `getComputedStyle` to get around this: https://bugzilla.mozilla.org/show_bug.cgi?id=548397

In that case, Blink and WebKit are changing to Firefox (and Edge)'s behavior, because it makes more sense. https://github.com/whatwg/html/issues/1813

[ Parent | on HN ]
Re:JavaScript performance, WebAssembly, and Shared Memory in... by mbell on Thursday April 20, 2017 @11:31PM (#14162907)
> In that case, Blink and WebKit are changing to Firefox (and Edge)'s behavior

The problem in FF isn't that they don't perform layout in the hidden iframe, it's that `getComputedStyle` returns `null`, which happens to be a side effect of not performing layout in Gecko.

If you read through the various related issues in your link I think you'll find that they are moving to standardize on not performing layout in hidden iframes, but `getComputedStyle` returning `null` is still a bug that Gecko intends to fix.

[ Parent | on HN ]