Closed nbriz closed 1 year ago
thought through this a bit, but turns out to be a lot more trouble than it's worth... seems simple enough at first, but when u consider the different "evaluation context" issues (they'd have to switch from "top" to "netnet.studio" + we'd have to explain what that is... etc) it becomes a bit of a rabbit whole
Friendly error messages should also suggest that the user open their dev console for more info so they get used to doing that.
F12
seems to be the most universal shortcut for dev tools (but opens the most previously opened tab, which might not be the Console), there are specific shorctuts to open up the Console... but these vary from browser2browser && platform2platform (could use Averigua to check && then dynamically display shorctut key?)