Eyedropper may fail under certain Content-Security-Policy settings
Categories
(DevTools :: Inspector, defect, P2)
Tracking
(firefox-esr91 wontfix, firefox90 wontfix, firefox91 wontfix, firefox92 wontfix, firefox95 wontfix, firefox96 wontfix, firefox97 verified)
People
(Reporter: mdavids, Assigned: jdescottes)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36
Steps to reproduce:
- Go to https://example.nl (literally)
- Start eyedropper
Actual results:
- Eyedropper appear, but is broken
- Console log shows a CSP-issue:
Content Security Policy: The page’s settings blocked the loading of a resource at data:image/png;base64,iVBORw0KGgoAAAANSU… (“img-src”).
Expected results:
Functional eyedropper.
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Reproduced on all the latest Firefox versions (Release 90, Beta 91.0b1 and Nightly 92.0a1) on MacOS 10.15.
Thanks for reporting this issue!
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 4•3 years ago
|
||
The issue is that the codepath we added to support remote frames relies on loading an image in the content process which fails if the page uses CSPs.
We either need a way to create an ImageData from a base64 URL without using an intermediary Image
load. Or we need to send the data over using a different format.
Updated•3 years ago
|
Assignee | ||
Comment 5•3 years ago
|
||
We can probably just send over the imageData instead of converting to a base64 here.
Assignee | ||
Comment 6•3 years ago
|
||
Use ImageData instead of base64 URL.
Updated•3 years ago
|
Comment 7•3 years ago
|
||
Set release status flags based on info from the regressing bug 1568831
Updated•3 years ago
|
Comment 9•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Comment 10•3 years ago
|
||
I've reproduced this bug using STR from comment 0, on an affected Nightly build 92.0a1 (20210713214232).
The issue is verified as fixed on latest Beta 97.0b8, across platforms: Win 10 x64, macOS 11, Ubuntu 18.04 x64.
Description
•