Ignore the TAO check for cross origin images for LCP
Categories
(Core :: DOM: Performance APIs, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox141 | --- | fixed |
People
(Reporter: sefeng211, Assigned: sefeng211)
References
Details
Attachments
(1 file)
There was an update to LCP spec such that the renderTime is no longer
protected by Timing-Allow-Origin due to it's easy to side channel attack
it and it isn't needed for CORS protected images.
The solution was to coarsen the timestamp by 4ms (this is what Chrome did).
To do something similar in Firefox, we don't need to coarsen the
timestamp because we already reduce more precisions. We just need to
always expose this.
Spec discussion: https://github.com/w3c/largest-contentful-paint/issues/111
This patch won't fix any test, instead, it'll make multiple-redirects-TAO.html starts to depend on PaintTimingMixin
| Assignee | ||
Comment 1•1 year ago
|
||
There was an update to LCP spec such that the renderTime is no longer
protected by Timing-Allow-Origin due to it's easy to side channel attack
it and it isn't needed for CORS protected images.
The solution was to coarsen the timestamp by 4ms (this is what Chrome did).
To do something similar in Firefox, we don't need to coarsen the
timestamp because we already reduce more precisions. We just need to
always expose this.
Spec discussion: https://github.com/w3c/largest-contentful-paint/issues/111
Updated•1 year ago
|
Comment 3•1 year ago
|
||
| bugherder | ||
Backed out for causing wpt failures
| Assignee | ||
Comment 6•1 year ago
|
||
Ah right, we fixed bug 1963464, so more tests are passing.
Comment 7•1 year ago
|
||
Backout got merged in central: https://hg.mozilla.org/mozilla-central/rev/6e45200ba360194bb2bc2a158bd312ba768a4548
Comment 9•1 year ago
|
||
| bugherder | ||
Updated•1 year ago
|
Description
•