Closed Bug 1070225 Opened 10 years ago Closed 6 years ago

Fix navigation regression for the canvas editor

Categories

(DevTools Graveyard :: Canvas Debugger, defect, P3)

Product:
DevTools Graveyard
Component:
Canvas Debugger
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: jsantell, Unassigned)

Details

Apply fix from web audio editor to canvas editor from bug 1066450, introduced via bug 1053805.
Assignee: nobody → jsantell
Status: NEW → ASSIGNED
I'm not seeing this issue for the canvas debugger. Anytime an attempt to load a new context (so navigating away, and coming back) fails for the web audio editor, reloading works fine though. Do you know how to recreate the canvas debugger issues you've seen?
Flags: needinfo?(vporof)
Here's my STR, although it takes a few attempts to reproduce this: 1. Make sure the toolbox is closed 2. Go to a page that works (properly) with the canvas debugger 3. Open the canvas debugger 4. Cmd+Shift+Reload (via keyboard) 5. Quickly close the toolbox (Cmd+Shift+I) 6. Open the canvas debugger (Cmd+Shift+I) 7. Cmd+Shift+Reload (via keyboard) 8. Click the stopwatch button The canvas debugger gets stuck and clicking the stopwatch button yields an error. Pastebin: https://pastebin.mozilla.org/6595534
Flags: needinfo?(vporof)
Assignee: jsantell → nobody
Bulk changing the status, as there is no assignee anymore. Sebastian
Status: ASSIGNED → NEW
Priority: -- → P3
Product: Firefox → DevTools
The code behind DevTools:Canvas Debugger has gone away. Closing this bug as INVALID
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
Product: DevTools → DevTools Graveyard
You need to log in before you can comment on or make changes to this bug.