RESOLVED INVALID105055
REGRESSION: painting issues in haaretz.co.il 
https://bugs.webkit.org/show_bug.cgi?id=105055
Summary REGRESSION: painting issues in haaretz.co.il
Yair Yogev
Reported 2012-12-14 14:26:17 PST
Steps to reproduce the problem: 1. Enter http://www.haaretz.co.il/magazine/theword/1.1884919 2. Scroll down beneath the article to the comments part 3. Click on one of comment titles (it's the bolded text left to the number of the comment) 4. In case it happen to look OK so far, try clicking it again to collapse the comment. When expanding: The comments don't expand, or expand cropped, or expand showing only the ad floating weirdly. When collapsing: The comments tend to leave part of their grayish "expanded state" background behind. If you select that part of the page and then deselect it, the issue is "fixed" and you can see how the page was supposed to look. Reproduced with Chromium under Windows 7, apparently started with WebKit roll 137323:137425 in http://crrev.com/172605 So the relevant WebKit changelog is at http://trac.webkit.org/log/?action=stop_on_copy&mode=stop_on_copy&rev=137425&stop_rev=137324&limit=200&verbose=on Also related: Between the article and the comments there is a form to add new comments. just above that a few images and text can appear with suggestions to related articles. I noticed that when it appears, it can have painting issues too- the images appear with a duplicate of the new comments form surrounding it. selection+deselection "fixes" that too. Tracked in Chromium bugtracker as http://crbug.com/166198
Attachments
Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2012-12-18 10:35:30 PST
I cannot reproduce with r138025 on Mac (using Safari).
Alexey Proskuryakov
Comment 2 2012-12-18 10:36:36 PST
I wonder if this has anything to do with bug 105073.
Yair Yogev
Comment 3 2012-12-22 23:36:35 PST
The bug is more obvious to notice if when you click a comment instead of a reply to a comment. Reproducible using Chrome Canary 26.0.1368.0 with WebKit 138366
Yair Yogev
Comment 4 2013-01-06 01:44:12 PST
In chrome, it does not reproduce when using " --disable-accelerated-compositing"
alan
Comment 5 2013-07-26 01:52:22 PDT
It seems to be working for me. At least I can't see any odd rendering artifacts. Could you attach a screenshot of the broken behaviour?
Yair Yogev
Comment 6 2013-07-26 09:00:35 PDT
I can't at the moment too, but i think it was probably a Chrome specific issue anyway (so it longer has a place here). Thanks
Note You need to log in before you can comment on or make changes to this bug.