994250 - Investigate how Web Audio Editor works with caching

Status: RESOLVED WONTFIX

(DevTools Graveyard :: Web Audio Editor, defect)

Description

[Jordan Santell [:jsantell] [@jsantell]]

Make sure the WAE works with bfcache

Comment 1

[Jordan Santell [:jsantell] [@jsantell]]

Was working previously, now when the WAE starts and finds the AudioContext, after reloading, the tool will not restart unless closing/reopening the dev tools panel.

Comment 2

[Jordan Santell [:jsantell] [@jsantell]]

Disregard comment #1, that is now fixed.

Caching situation can be recreated by navigating to a page with a context. Go back, then forward again, and the tool waits for "waiting for AudioContext to be created", which makes sense since we don't have the initial creation event as the page is popped from bfcache. If there's not much overhead to store the AudioNodeActors during a bfcache, then we can recreate it, but worry that it might be a lot of information on complicated pages, and would be better to just prompt for a refresh in the tool.

Any thoughts Victor, as you did this for the shader editor? Some complicated audio usages have 50-100 audio nodes.

Comment 3

[Victor Porof [:vporof][:vp]]

The Shader Editor stores everything (i.e. programs) until the inner window owning them is destroyed. Sounds like the Audio Editor should either do the same, or try to retrieve all audio nodes when navigating to a page in the bfcache (which seems hard).

Comment 4

[Patrick Brosset <:pbro>]

Mass-closing inactive (2 years+) bugs on unmaintained devtools components.