Good day,
Every time I open the console in brave and the debugging mode is on, and my screen is over lay with stop pause debug thing.
Does anybody know how exactly to turn it off and get back to normal console ?
Maybe you figured it out by now.
But, in case you didn't, here is a solution.
Open Developer Tools in Brave
Open Sources Tab
And make sure "Pause on Exceptions" is disabled.
Check the image
Related
If I close a browser running a web application, it is desirable that the debugging session dies. After all, this equals to closing a windows application. However, if I stop debugging and the browser has more than one tabs (as often is the case), all of them will close - definitely not what I intended. Not using this option means I continuously forget the debugger running and clicking the stop button is just extra work.
Is there an add-on to Visual Studio or any other trick that allows to do only the first: stop debugger when window is closed?
Who thought it would be a good idea to put two options behind a single checkbox? This is a double-edged sword at its sharpest!
It's not exactly what you want. But, it might be a workaround. If you enable JavaScript debugging in Tools->Options->Debugging and then you Debug->Detach All. The browser should stay open and debugging should stop... Now it would mean that the application is still running, which might not be desirable.
It's a great suggestion to make this an option. I'd encourage you to open a suggestion on developer community.
Tools Options:
Detach:
I have a script that I'm trying to debug, but the debugger immediately closes itself when it hits an error and dismisses the error message. I could manually open the log and wait for it to load every time I hit a stop, but that wastes a lot of time when it could just pop up on my screen. I figure it has to be an easy fix and I probably did something stupid, but one gets pretty tired of Google's shit when you've read blog headlines such as "THE 6 DEADLY SINS OF GOOGLE APPS SCRIPT ADD-ON DEVELOPMENT" for the 50th time in as many search queries. Anyways, rant over.
When I hit debug, the debugger will run, a white tray pops up at the bottom of my screen and stays empty. When it hits an error, it will flash the error message across the top of the window and immediately close/dismiss that error as well the tray that popped up. The tray looks like the one in the image below, except completely empty.
Has anyone else had this issue and know why it might be happening? Also, can anyone tell me if there is a Matlab-style workspace explorer that displays each user-defined variable and what kind of data it holds? I would find that extremely helpful in debugging. That, and a live in-window console/log.
This is a known issue. Star(on the top left) the issue to let Google know that you're affected and for the issue to be prioritised. Some of the features you requested is already in development
New IDE features Monaco for cutting edge code editing, streaming logs, reliable debugging and Material design. Seamless integration into the G Suite Developer Hub lets users design, develop, deploy and manage their projects all in one place.
In the meantime, You can use clasp in your local IDE.
Related question:
V8 engine no longer breaks on errors
My job is working on a website using Forefox, that website will promt a pop-up every 1 minute to give me a code. When the pop-up window appears, it'll display on top of all other windows and steals the focus. It's so annoying.
When i'm writing Word/Excel it causes mistyping, and that pop-up will minimize some full-screen application like Video Player/Games.
I've tried:
-Set working windows always on top - when i work with 5-10 programs a time it will be more annoyed.
-Change dom.disable_window_flip and browser.tabs.loadDivertedInBackground - NOT working.
I'm not sure if this problem come from Firefox or Windows's default setting for a new window pop-up.
Could anyone give me a solution for this case?
Thanks in advance
Does anyone know of a browser that has a screen reader friendly debugging console? I have a friend whose a blind programmer and it drives her nuts that she can't easily "see" the console log errors.
This drives me nuts also. Unfortunately, the best solution for now is IE 10. This is awful what they did to IE 11 but I hope to convince them to make this more accessible.
And yes, I'm working with JAWS, so it might be different for NVDA, Window Eyes or Supernova.
I personally use Firebug for Firefox. After installing it, in the Web Developer menu of the tools menu, go into Firebug, Options, then turn on the accessibility enhancements. Some bits aren't perfect, but the console window at least is. It has a list of log rows that can be navigated with the up/down arrows and then a bit for typing in your own js commands. To get to the Firebug window when you open it with F12, use F6. Also works for getting out of it too.
Hope this works for your friend as well as its worked for me.
I use Visual Studio 2008. I haven't seen this behavior before and, as far as I know, I didn't change anything in the options.
When I press Start debugging all the possibly windows (watch 1 - 4), data sources, properties, registers (to be honest I have not even ever seen these windows before) appear in front of the code window and stay there after I stop the debugger.
Anyone has an idea what could be causing this ? (I am using CodeRush and Refactor for quite a while now)
When I close and restart visual studio all the windows are where they should be.
PS: Previously I have seen normal switching from normal to debug mode and back with some repositioning changes. That is the way it used to work. Now it is not. It has suddenly gone mad and when going to the debug mode it sometimes shows all possible IDE windows and sometimes not. When it does it no longer returns to the previous state. I cannot find this in the options anywhere.
Visual Studio remembers 2 sets of window layouts, normal mode and debugging mode. My solution is to arrange my normal windows exactly like I want them, then start debugging an application and once again arrange all of the windows the way I want, usually making it as similar to my normal layout as possible, then stopping the debugger and doing a File Exit so that VS saves my settings.
After doing that, it recalls my 2 different layouts each time.
I'm experiencing the same thing - whenever the debugger is running, switching focus back to the IDE immediately caused the debug panel to expand.
I ended up just pinning the debug panel so that it always appears when debugging, and just changing its height as needed.
To add to palehorse, another tip is Full Screen mode.