Simon Fraser
Simon Fraser
No, all the content is already loaded when the test runs. Various things affect the level of noise in the results; these can be inspected if you run from `developer.html`...
This needs rebasing.
Marked "non-trivial" since the changes touch test code.
There's a PR for this at https://github.com/WebKit/WebKit/pull/11560
> Please note this improvement is currently disabled for mac platforms. Could you explain why?
@mattwoodrow
Could we add a unit test for the old scoring algorithm, and then this PR should modify that test. I'd also like to see an independent implementation of the scoring...
> "Whenever a browser is running in full screen mode, it is RECOMMENDED that the browser compositor synchronizes to the frame rate frequency of the dominant / element, to unlock...
Something similar could be useful for other replaced elements like `` and ``/``. For example, you might want to apply `dynamic-range-limit` to the image content, but not its CSS backgrounds...
I guess so; maybe we need a way to address replaced element "primary" content if that's something we can define.