Summary: | Web Inspector: Canvas Tab: canvas card selection not restored on page reload | ||
---|---|---|---|
Product: | WebKit | Reporter: | BJ Burg <bburg> |
Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED CONFIGURATION CHANGED | ||
Severity: | Normal | CC: | hi, inspector-bugzilla-changes, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://acko.net | ||
Bug Depends on: | |||
Bug Blocks: | 175485 |
Description
BJ Burg
2017-11-06 15:21:31 PST
Do we have a reliable method of "identifying" canvas contexts? As an example, <http://acko.net> uses additional canvases for feature detection. These canvases are sometimes GC'd before I can see them in the UI (leaving 1 canvas showing). If I select this canvas and refresh, and on the next load the other canvases are not GC'd as fast, which canvas should be selected? Should it be by index (meaning the first canvas is selected, regardless of what it is), or should we go by DOM path (but then what about double/triple buffer canvases)? I agree that we should have some selection restoration, but I am not sure how to go about it for some of these edge cases. Admittedly, most pages do only have 1 or 2 canvases ¯\_(ツ)_/¯ Canvases are no longer selectable in the Overview. |