Questions re: user experience

[osnr]

Questions re: user experience

[osnr]

Yeah. I'll think about how to document that better. I sort of feel like we should have... like... an autogenerated tree / table of contents / listing of all the synthetic files that says what they do, what side effects they have (some pull up the debugger warning, some are slow), etc.

if this is inside the extension, maybe it also has config so you can toggle them off without modifying the source code (although I do want people to feel comfortable modifying the source code, too)

[osnr]

interesting. I think only stuff in the debugger/ subfolder should actually require the debugger and trigger the warning. (i.e. not title.txt, url.txt, etc).

it's possible that something in your userspace is reaching into debugger/ (to stat files or whatever) and triggering the debugger (and once it's on, it tends to stay on).

I think if you just delete that whole block I linked, the debugger won't be invoked anymore? (it is already disabled in Firefox, which doesn't have the chrome.debugger API)

[beaugunderson]

oh interesting! documenting that it shouldn't normally happen would help here, and I think in my case maybe it's Spotlight indexing or something that's enumerating all of the files?

or maybe the initial grep or **/*.txt enumerated all the debugger-specific files and the debugger remained on for all tabs