Closed
Bug 1722780
Opened 3 years ago
Closed 3 years ago
Add the foundations for the content overlay and child/parent communication
Categories
(Firefox :: Screenshots, task)
Firefox
Screenshots
Tracking
()
RESOLVED
DUPLICATE
of bug 1736429
People
(Reporter: sfoster, Assigned: sfoster)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
In order to start migrating the extension code, we need a way to overlay the content document and communicate user choices and interaction on that layer up to the parent process where the screenshot will be finalized.
Assignee | ||
Updated•3 years ago
|
Assignee: nobody → sfoster
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•3 years ago
|
||
- The child window actor creates a AnonymousContentOverlay instance to manager the anonymous-content overlay
- The overlay sits on top of the page to be screenshot, and blocks pointer events
- It gets inserted into the document's canvasFrame anonymous content container
- As anonymous content, we have to treat it a little differently/carefully....
Status:
- This is a first pass. While we'll iterate and incrementally migrate the extension functionality while pref'd off, I'd like to make sure the architecture and approach are sound at a high level.
- Clicks on the full/visible page buttons will send a message up the parent
- The parent calls the appropriate method on ScreenshotsUtils, and sends a message back to the child to close the overlay.
- There's the beginning of some CSS for the overlay, but while we can load e.g. common.css, we currently need a :-moz-native-anonymous prefix on all selectors so it doesnt help much
Assignee | ||
Comment 2•3 years ago
|
||
This got broken out into individual bugs, but the initial, most important piece was bug 1736429.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
Updated•3 years ago
|
Attachment #9233585 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•