Closed
Bug 799018
Opened 12 years ago
Closed 8 years ago
Incorrect painting when following review link on Amazon.com
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jesup, Unassigned)
References
Details
(Keywords: steps-wanted, Whiteboard: [platform-rel-Amazon][platform-rel-AmazonShopping])
Attachments
(2 files)
Clicked on "read full review: link on right bar, header line of review is wrong. ('before' image). Hitting screenshot caused a window to pop up on top, which captured the error but caused a redraw that erased it. See 'after' image.
Reporter | ||
Comment 1•12 years ago
|
||
Reporter | ||
Comment 2•12 years ago
|
||
Note: I think (given the final image) I scrolled down one click with the mousewheel as or maybe just after the page loaded. When I tried to re-create I believe I saw it again for a fraction, but I probably had already clicked on more on the mousewheel. Final URL: http://www.amazon.com/Samurai-Trilogy-Criterion-Collection-Blu-ray/product-reviews/B007N5YJZM/ref=cm_cr_dp_synop?ie=UTF8&showViewpoints=0&sortBy=bySubmissionDateDescending#R2XE3QQP8XHM9P URL coming from: http://www.amazon.com/Samurai-Trilogy-Criterion-Collection-Blu-ray/dp/B007N5YJZM/ref=pd_ys_sf_s_2644980011_a1_6_p URL clicked on: (above, this is the text, right "mini-reviews" column): 2.0 out of 5 stars Brilliant films, stupidly remastered Having waited faithfully for years for a good HD and Blu-Ray remastering of these wonderful films, I was delighted to
Updated•12 years ago
|
tracking-firefox18:
--- → ?
I can't reproduce on linux-x64/basic or win7/d3d10, but I'm not sure I'm doing it right.
Keywords: qawanted,
steps-wanted
Reporter | ||
Comment 4•12 years ago
|
||
I produced this on Linux64 (F15). However, I was unable to easily reproduce it; it appeared to be timing-related. I think I saw flashes of the problem in intermediate paints, but then it got overwritten by later reflows/draws.
Comment 5•12 years ago
|
||
Leaving this nominated to see if QA is able to reproduce it . Will not track for release if QA cannot reproduce or until we hear more users facing this issue
Comment 6•12 years ago
|
||
Juan - please try to reproduce on a couple of different configurations. If you have a hard time reproducing, please set tracking-firefox18 to ? and we'll re-evaluate.
Comment 7•12 years ago
|
||
I haven't been able to reproduce this on VMs using Fedora 17. I've cc'd Kevin who often uses Fedora as his working OS. I'm also going to ask our Softvision team to take a crack at it.
Randell, can you please provide a copy of the Graphics section of about:support so QA can come close to reproducing the circumstances of this bug? I'm unable to reproduce this on a local instance of Crunchbang Linux (based on Debian 6) running on a Lenovo X230 with Intel graphics.
Comment 9•12 years ago
|
||
I'm not able to reproduce on 19.0a1 (2012-11-06) and 18.0a2 (2012-11-06) on Fedora 17 x64.
Reporter | ||
Comment 10•12 years ago
|
||
As I mentioned, I was unable to reproduce it immediately; it seemed to be timing related. Linux Fedora 15 Quadro 600/PCI/SSE2 4.1.0 NVIDIA 280.13 GPU accelerated windows: 0/1 Basic
Comment 11•12 years ago
|
||
Paul can you retest with an environment similar to Randell's? That is, Fedora 15 with an NVidia card? Randell, in turn can you please try using a more recent graphics driver? http://www.nvidia.com/object/linux-display-amd64-304.64-driver.html It might also be worth noting which Desktop Environment you are using. Fedora 15 was the first release to use Gnome 3 which could be quite buggy if it's not been as maintained as the version on Fedora 17.
Comment 12•12 years ago
|
||
To supplement comment 11, I searched Fedora's package db and found that Fedora 15 uses Gnome 3.0.1 while Fedora 17 uses Gnome 3.4.1. I'm not saying this is not a Firefox bug, but I'd like to eliminate as many variables as possible.
Reporter | ||
Comment 13•12 years ago
|
||
Correct, Gnome 3.0.x. I'll note that I run m-c builds almost exclusively on this machine, and this was a clearly new behavior shortly after DLBI re-landed (along with some other bugs, most of which were not repeatable). I'll also note I run a LOT of tabs (~900-950). This has the side-effect of slowing down a bunch of operations, and may change the timings of incremental reflows, exposing bugs that might not be seen if the page loads/reflows faster. I really doubt this one will be easily repeatable, if at all, even if it hasn't been fixed since.
Comment 14•12 years ago
|
||
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #11) > Paul can you retest with an environment similar to Randell's? That is, > Fedora 15 with an NVidia card? Sure, but it will take me couple of days, I have to set up the environment first. I'll come back with the results.
Comment 15•12 years ago
|
||
(In reply to Paul Silaghi [QA] from comment #14) > Sure, but it will take me couple of days, I have to set up the environment > first. I'll come back with the results. That's fine, thanks Paul.
Comment 16•12 years ago
|
||
From what Randell mentions in comment #13 it looks like the conditions under which this happens may not be too common. I run lots of tabs on Mac and Windows and I haven't seen this problem (I use Amazon quite a bit). I also haven't seen this problem on a Ubuntu 12.04 LTS machine where I also run usually more than 20 tabs including Amazon. We'll wait for Paul to report back, but I think we should not track for 18.
Comment 17•12 years ago
|
||
I'm still not able to reproduce on 19.0a1 (2012-11-08) and 18.0a2 (2012-11-08) on Fedora 15 x64 with Nvidia GeForce 210.
Comment 18•12 years ago
|
||
Thanks for trying, Paul. I'm not sure what more we can do.
Keywords: qawanted
Comment 20•12 years ago
|
||
Please take a look on bug 810608
Comment 21•12 years ago
|
||
Untracking for 19 based on lack of reproducibility and seemingly low effect on users.
Updated•8 years ago
|
platform-rel: --- → ?
Whiteboard: [platform-rel-Amazon][platform-rel-AmazonShopping]
Reporter | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•