Re:JavaScript performance, WebAssembly, and Shared Memory in...
by bzbarsky on Thursday April 20, 2017 @11:42PM
(#14162953)
> point is it shouldn't take nine years to fix an app-breaking bug
It depends on priorities, obviously. That bug was fixed in various cases that were most-commonly hit (e.g. translate-only transforms) much earlier than now. Fixing it in the scale case more or less required completely rewriting how <select> is implemented, and there was always other stuff that needed to get done that was a bigger problem in practice.
I'm not saying this is good, obviously; it would be great if there were more people working on Gecko bugs and triage were not so critical. But there weren't and it was. I'm sorry that it's caused you problems; I'll see if I can get some progress to happen on the option label thing.
> Could you specify some issues you ran into on Chrome that affected user space this directly
Note that all these bugs were filed in the WebKit bug system for a while before I went and refiled them in the Blink bug system after Blink forked off from WebKit. So they are much older than the dates you see on those reports.
It depends on priorities, obviously. That bug was fixed in various cases that were most-commonly hit (e.g. translate-only transforms) much earlier than now. Fixing it in the scale case more or less required completely rewriting how <select> is implemented, and there was always other stuff that needed to get done that was a bigger problem in practice.
I'm not saying this is good, obviously; it would be great if there were more people working on Gecko bugs and triage were not so critical. But there weren't and it was. I'm sorry that it's caused you problems; I'll see if I can get some progress to happen on the option label thing.
> Could you specify some issues you ran into on Chrome that affected user space this directly
Off the top of my head, https://bugs.chromium.org/p/chromium/issues/detail?id=352144 is a pretty glaring CSS layout bug. Is that direct enough?
Or how about https://bugs.chromium.org/p/chromium/issues/detail?id=269500 which has been around forever (it existed in WebKit long before Chrome was even announced)?
Or https://bugs.chromium.org/p/chromium/issues/detail?id=353580
Or https://bugs.chromium.org/p/chromium/issues/detail?id=286672
Note that all these bugs were filed in the WebKit bug system for a while before I went and refiled them in the Blink bug system after Blink forked off from WebKit. So they are much older than the dates you see on those reports.