Mozilla/5.0 (Windows NT 5.1; rv:10.0.6) Gecko/20100101 Firefox/10.0.6 On Amazon, a black square is displayed when hovering the mouse over the items. This issues is reproducible on Firefox 10.0.6 ESR. Steps to reproduce: 1. Navigate to http://amzn.to/M3hP9a 2. Hover the mouse over any item. Expected results: The items are properly displayed without any flickers or black squares. Actual results: A black square is displayed when hovering the mouse over the item. Please see the video: http://screencast.com/t/eViMVd7Lo
similar to bug 763467 / bug 702099 Can you reproduce without hardware acceleration (-> safemode) ? Do you get the same result with Firefox13 on the same system ? The testcase is wfm with Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/16.0 Firefox/16.0 SeaMonkey/2.13a1 Build identifier: 20120714003024
In reply to Matthias Versen (Matti) from comment #1) > Can you reproduce without hardware acceleration (-> safemode) ? Without the hardware acceleration I can not reproduce the issue. But the issue is reproducible for me on clean profiles. > Do you get the same result with Firefox13 on the same system ? The issue is not reproducible on Firefox 13.0.1, Firefox 14.0.1 on the latest Nightly or on Aurora. Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0.1 Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1 Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Firefox/17.0 Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120716 Firefox/15.0a2 The issue is only reproducible on the ESR branch: Mozilla/5.0 (Windows NT 5.1; rv:10.0.5) Gecko/20100101 Firefox/10.0.5 Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
We are taking only security fixes on the ESR branch, right ? This is also no regression between 2 ESR branch versions and I don't think that this gets fixed on ESR. Fixing this means that you have to find the checkin that fixed this issue and backport it to the ESR branch.
Component: General → Graphics
Product: Firefox → Core
2 years ago
platform-rel: --- → ?
platform-rel: ? → ---
You need to log in before you can comment on or make changes to this bug.