New issue
Advanced search Search tips

Issue 622242 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

consider not running the rendering pipeline for display:none iframes

Project Member Reported by ojan@chromium.org, Jun 22 2016

Issue description

It's not clear if this is web compatible, but conceptually, it doesn't make sense to be running requestAnimationFrame inside display:none iframes.

WebKit tried this for both display:none and 0x0 iframes and had to revert. I'm hoping it was the 0x0 that was the problem, not the display:none. http://jsbin.com/jolatibebe/1/edit?html,output

IMO, we should consider doing this for display:none and see if it breaks that page.
 

Comment 1 by ojan@chromium.org, Jun 22 2016

Status: Untriaged (was: Unconfirmed)
Whoops. http://jsbin.com/jolatibebe/1/edit?html,output is my test case for this. 

http://trac.webkit.org/changeset/186195 is the webkit revert patch with the link to the page that breaks.
Status: WontFix (was: Untriaged)
So turns out we accidentally shipped this and it caused  bug 680925 . I think we can conclude that this change isn't web compatible.

Sign in to add a comment