Open Bug 1429097 Opened 6 years ago Updated 10 months ago

Pause execution when Canvas Permission Prompt is displayed

Categories

(Core :: Graphics: Canvas2D, enhancement, P3)

enhancement

Tracking

()

Tracking Status
firefox59 --- affected

People

(Reporter: tjr, Unassigned)

References

Details

(Whiteboard: [fingerprinting][gfx-noted][fp-triaged])

From talking with :luke, it seems like it would be possible to pause JS execution when the Canvas Permission Prompt is displayed, using the same sort of ugly waitloop we use for synchronous XHR and alert().

This would require the user to respond to the permission prompt (instead of ignoring it) before execution of the page can resume.  Maaaybe we don't want to do that (because it would freeze the page to some extent) - but I'm opening this bug to consider it and get the note down.

We should not do this before Bug 1376865 otherwise we will block execution of page loads.
Priority: -- → P3
Whiteboard: [fingerprinting] → [fingerprinting][gfx-noted]
Whiteboard: [fingerprinting][gfx-noted] → [fingerprinting][gfx-noted][fp-triaged]
This seems like a very interesting idea, because it blocks the image extraction attempt rather than ignoring the first attempt. Maybe we could introduce async versions of the image extraction APIs at the same time to give web authors an option to use a non-blocking version.
Whiteboard: [fingerprinting][gfx-noted][fp-triaged] → [fingerprinting][gfx-noted]
Whiteboard: [fingerprinting][gfx-noted] → [fingerprinting][gfx-noted][fp-triaged]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.