4 ms·
It's hard to define it as an nVidia bug or a browser bug. You may say it's an nVidia bug because it only happens on nVidia; but then you can also say it's a "Wi
by fireattack 8y ago
It's hard to define it as an nVidia bug or a browser bug. You may say it's an nVidia bug because it only happens on nVidia; but then you can also say it's a "Win 7 bug" because it only happens on Win7.
Anyway, as a fact: it works fine in IE and Chrome (after they fixed it). So at very least, it is fixable on browser's end.
It also works fine in any video player you can think of.
Also, from what I can see, neither Chromium dev nor Firefox dev claim it's an "nVidia bug". Chromium dev just went ahead and fixed it. Firefox dev said they're not going to fix it because (from previous ticket [1]) "We don't intend to add new features such as this code is only used on Windows 7." Which IMHO makes no sense because when this bug firstly appeared, it was 3-4 years ago; and Win 7 is still one of the most used OS and is in the supported OS list of Firefox.
[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1161349#c46 https://bugzilla.mozilla.org/show_bug.cgi?id=1161349#c46
- Yoric 8y agoIt's a problem of resources. There are simply not enough devs to do everything. So Mozilla needs to prioritize bugs and features aggressively.