#devtools tells me that we can hide files from debugging by clicking on an eyeball icon. All well and good, but perhaps the devtools should have some way of making that persistent between sessions. I need help figuring out where to store that persistence info, as prefs might not be the right answer. Bug 872980 talks about limiting prefs to 4kb in the long run... then again, how big do file URL's get? Hiding whole branches would be great too. (Say, if I don't want to debug browser files, but I do want to see my own chrome files at work.) Finally, what would the UI be like for this? I need some help with that.
setting this to assigned. File URLs can get pretty big, but we should probably key off of domain or some subset of the full URL. You could use indexedDB or filestorage to stash your settings. For UI, I'd suggest adding a checkbox in the Options panel with words to the effect of: "Persist Blackboxed Files Across Sessions" in the Debugger section or similar. Add to that a "Clear Site Prefs" button and you should be done. I doubt we need to provide an editor to enter/edit URLs.
Status: NEW → ASSIGNED
Priority: -- → P3
Summary: Skipping over certain files by default should be configurable, persistent → black boxing sources should be optionally persistent
Assignee: ajvincent → nobody
Status: ASSIGNED → NEW
Assuming that by 'persistent between sessions' you meant: 'between closing and reopening the debugger'. I've tried it out, but as far as I can tell, blackboxing is already persistent between sessions. Resolving this as WORKSFORME. Feel free to reopen if I somehow misinterpreted the intent of this bug.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.