On 4/13/12 10:49 AM, Tanvi Vyas wrote:
One thought I had was requiring that the very first time a user uses a developer tool, the user needs to go to Tools->WebDeveloper->Selected Devtool. After that, keyboard shortcuts would work for all devtools. The developer wouldn't have to do anything else to enable the tools and there would be no additional warnings.
Some sort of interstitial warning roughly like this is where I'd start thinking from. EG, when you first open the webconsole, a click-thru-able warning about staying away unless you know what you're doing. Same basic take as we already have with about:config.
[Obvious next refinement: only do this when you're about to execute JS for the first time.]
I also see this as an issue for people who uninstall/reinstall firefox, or for developers who get a new computer, install firefox, and wonder why their keyboard shortcuts aren't working. This is bad user experience since its not clear to the user what's going on.
I don't think that's a deal-breaker, it's a one-time mild annoyance at worst. Make it a flag (pref) handled by Sync, and when you use Sync to pull in your existing stuff it's a non-issue.
Justin _______________________________________________ dev-security mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security
