zhangqd / chromiumembedded

Automatically exported from code.google.com/p/chromiumembedded
0 stars 1 forks source link

1916 branch: Not receiving paint updates with off-screen rendering #1260

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Load up CEFClient with the env variable "--off-screen-rendering-enabled"
2. open the attached "test.html"
3. click on the "Tab 2" button and wait 6 seconds (alternate the buttons to 
repeat)
4. Perceive the transitions as they occur

What is the expected output? What do you see instead?
expected: In windowed mode (and in chromium and other browsers), the "new" tab 
fades in to the right, then switches places with the old tab.

What do you see:In CEFClient it instead does not appear to do anything for 4 
seconds and then the new tab pops into existence for the "left" transition

What version of the product are you using? On what operating system?
Occurs in cef_binary_3.1916.1662_macosx32 and cef_binary_3.1921.1656_macosx32

Please provide any additional information below.
If you change the "top" setting in the ".tabbed.selected" selector in the 
internal CSS, even by a single pixel, you will see that the transition works 
correctly. (presumably since there is then a top transition at the same time as 
the opacity transition, it "avoids" the problem) 
I would guess that this is because the animation occurs correctly in the 
background, but that CEF is failing to request a paint, so if paints are 
requested for other reasons, the problem disappears.

Further evidence for this theory is that resizing continually during the 4 
seconds when it *should* be transitioning also avoids the problem.

Apologies if this is a dupe, but i found no relevant issues under "transition" 
or "opacity".

Original issue reported on code.google.com by finnBry...@gmail.com on 28 Apr 2014 at 6:41

Attachments:

GoogleCodeExporter commented 9 years ago
Just saw Issue 1257, I guess this is related to that. This issue doesn't occur 
in Branch 1650, so I'll stick with that build for now.

Original comment by fbry...@feralinteractive.com on 30 Apr 2014 at 5:59

GoogleCodeExporter commented 9 years ago
Issue 1322 has been merged into this issue.

Original comment by magreenb...@gmail.com on 2 Jul 2014 at 11:14

GoogleCodeExporter commented 9 years ago

Original comment by magreenb...@gmail.com on 2 Jul 2014 at 11:16

GoogleCodeExporter commented 9 years ago

Original comment by magreenb...@gmail.com on 2 Jul 2014 at 11:26

GoogleCodeExporter commented 9 years ago

Original comment by magreenb...@gmail.com on 23 Oct 2014 at 5:36

GoogleCodeExporter commented 9 years ago
This appears to be fixed in 2062+.

Original comment by magreenb...@gmail.com on 23 Oct 2014 at 5:54