Some tests calls internals.settings.setEnableCompositingForFixedPosition() in the onload handler, which may be too late because the compositing requirements may have been computed. This causes the tests flaky or failure to test the expected behavior.
Created attachment 178043 [details] Patch
Alternately, can we make that call re-evaluate compositing requirements? We normally do that whenever style changes.
(In reply to comment #2) > Alternately, can we make that call re-evaluate compositing requirements? We normally do that whenever style changes. I'm afraid there might be still other places in the code not expecting change of the settings.
Comment on attachment 178043 [details] Patch Clearing flags on attachment: 178043 Committed r136885: <http://trac.webkit.org/changeset/136885>
All reviewed patches have been landed. Closing bug.