1147504 - 'ev' popup in devtools inspector experiences rendering glitches when scrolling inner content

Status: NEW

(Core :: Graphics, defect, P3)

Description

[Jim Mathies [:jimm]]

STR:

1) load test case, it's a test html file from a test I'm working. It will appear blank in the browser.
2) open the inspector
3) you should see some anon html:divs inserted into content, and on these there are these little 'ev' buttons related to event listeners.
4) click on one of the 'ev' buttons, and scroll the content in the popup

result: tearing and streaking of rendered content

Comment 1

[Jim Mathies [:jimm]]

Attachment: plugin_hidden_to_visible.html

Comment 2

[Jim Mathies [:jimm]]

Attachment: jimm dell t5810 support.txt

Comment 3

[Jim Mathies [:jimm]]

Attachment: screenshot.png

Comment 4

[Jeff Muizelaar [:jrmuizel]]

Can you reproduce this on other machines?

Comment 5

[Jim Mathies [:jimm]]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #4)
> Can you reproduce this on other machines?

Heavily on my Win8 Surface Pro 2 on Google's homepage. Just look for a big block of script in one of the event handler popups and scroll. I see colorful streaks across the entire popup window that dance and display and then go away every time I scroll. :)

Comment 6

[Jim Mathies [:jimm]]

This is without e10s as well.

Comment 7

[Jeff Muizelaar [:jrmuizel]]

Is this a regression?

Comment 8

[Jim Mathies [:jimm]]

I'm sorry, I don't have time to go regression hunting. Lets get some help from QA. Juan, can you help us get softvision involved here?

Comment 9

[[SV Manager] Florin Mezei, QA (:FlorinMezei)]

I was able to easily reproduce the issue on Windows 7 x64, using the latest Nightly 40 build, and the following scenario:
1. Open Firefox and go to https://www.google.ro.
2. Press F12 (or Ctrl+Shift+I) to open the Developer Toolbox.
3. Select the "Inspector" tab.
4. You should see a small gray "ev" button at the end of the first line (the html tag).
5. Click on it and look for a line that says "keydown" and click on it. -> you should get a scrollable content pop up.
6. Scroll up/down using the mouse scroll or the vertical scroll bar.

Results: you should see the tearing and streaking of content.

Looking for a regression range, I see this issue appeared at the moment we started displaying the "ev" button in July 21st 2014. Note that if you try the Nightly build from that date you will notice some black flickering that hides the tearing and streaking most of the time.

Regression window data:
Last good revision: 0894d2cdb16d (2014-07-20)
First bad revision: 5b64c42742cd (2014-07-21)
Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0894d2cdb16d&tochange=5b64c42742cd

Comment 10

[Jim Mathies [:jimm]]

Thanks Juan and thank you Florin for the detail report. Would you mind spot checking aurora, beta, and release and updating the bug flag? Sounds like this in everything.

Comment 11

[Jeff Muizelaar [:jrmuizel]]

Florin, There's a lot in that range is it possible to get a narrower regression window using inbound builds or manual building?

Comment 12

[[SV Manager] Florin Mezei, QA (:FlorinMezei)]

(In reply to Jim Mathies [:jimm] from comment #10)
> Thanks Juan and thank you Florin for the detail report. Would you mind spot
> checking aurora, beta, and release and updating the bug flag? Sounds like
> this in everything.

This is indeed in everything Jim. I updated the status flags.

(In reply to Jeff Muizelaar [:jrmuizel] from comment #11)
> Florin, There's a lot in that range is it possible to get a narrower
> regression window using inbound builds or manual building?

Since there are no more inbound builds from July 2014 this would require manual building which is extremely time consuming so I would rather not do that unless this is deemed a very high priority issue. We have very limited resources and a lot to deal with, especially with new features in Firefox 38.

However, given that this issue appeared at the same time with the "ev" buttons I would say that there are only 2 possibilities here:
1. The issue was introduced by the introduction of the "ev" button itself, so we should just look where that got in
2. The issue itself has been there before the introduction of the "ev" button, but in this case it is hidden and we cannot get the correct regression window with these steps

Comment 13

[setname4g]

[Tracking Requested - why for this release]: