3 ms·
But none that describe the cause of the bug, right?
by pjtr 11y ago
But none that describe the cause of the bug, right?
- digitalzombie 11y agoWell, the person who reported the bug comment in depth details of what it does from his point of view on that link. So yes? ctrl+f to find user "fukusa" and you'll find that one of his/her comment goes into depth.
- fukusa 11y agoThanks, also have a look at: https://news.ycombinator.com/item?id=10047010 https://news.ycombinator.com/item?id=10047010
- pjtr 11y agoThanks, that's closer to what I was looking for. I'm still a bit unclear on what exactly the root cause of the bug is. A flawed plugin API (PlayPreview), flawed usage of that API, a bug in the implementation of that API, a combination of these or something else. From your link it looks like the plugin now does not use the API anymore, but the API still exists. But the API implementation seems to have required fixes as well. [1] [2] [1] https://github.com/mozilla/gecko-dev/commit/2e67509c8a3cefe8c0cdf74922f02c340543b17f https://github.com/mozilla/gecko-dev/commit/2e67509c8a3cefe8... [2] https://github.com/mozilla/gecko-dev/commit/8b7f7bde8f21bd71d85f40a5b5fbf9c9b0e05528 https://github.com/mozilla/gecko-dev/commit/8b7f7bde8f21bd71...