179346 2017-11-06 15:21:31 -0800 Web Inspector: Canvas Tab: canvas card selection not restored on page reload 2018-08-28 11:46:22 -0700 1 1 1 Unclassified WebKit Web Inspector WebKit Nightly Build All All RESOLVED CONFIGURATION CHANGED http://acko.net InRadar P2 Normal --- 175485 1 bburg webkit-unassigned hi inspector-bugzilla-changes webkit-bug-importer oldest_to_newest 1368805 0 bburg 2017-11-06 15:21:31 -0800 Steps to reproduce: 0. Load acko.net, see three canvas cards in Canvas Tab 1. Make card selection 2. Reload page => Selection is lost, despite canvases being recreated within the cookie restoration last chance timeout 1368806 1 webkit-bug-importer 2017-11-06 15:21:53 -0800 <rdar://problem/35375222> 1368824 2 hi 2017-11-06 16:06:38 -0800 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 ¯\_(ツ)_/¯ 1454473 3 hi 2018-08-28 11:46:22 -0700 Canvases are no longer selectable in the Overview.