I think in this case, a picture will be worth a thousand words. I really have no idea why this is happening, but the error is in my code, and nothing I have tried will allow me to see. Nothing is blackboxed. Nothing is filtered out. The things that look greyed out like they are disabled, are disabled. I cannot edit them. Unchecking "Group Similar" has no effect.
You can see where I point to the red lines, it looks like they are indicative a hidden error message here.
I am using Version 65.0.3325.181 (Official Build) (64-bit). Did I do this somehow? Is this a bug maybe? Any insight would be appreciated.
go to console and press f1 to go to setting. At the end of page you get link to restore setting and reload.
Related
When I click on a line to set a break point, the break point line gets highlighted, then the break point highlight disappears.
Other than that, Firefox developer debug has been working fine.
This might help people in the future without having to modify any js file:
Have you clicked the Deactivate breakpoints button? Pressing this will toggle breakpoints on/off.
If the icon is in blue, it means the breakpoints will be de-activated.
Note: I have noticed that in some sessions the toggle is activated although not blue, a refresh of the page solved this.
This just happened to me in Firefox 60.3.0. The tip about removing the Mozilla folder led me to a better solution, which is to edit the prefs.js file in the Mozilla profile folder. (In my system this was in C:\Users\xxx\AppData\Roaming\Mozilla\Firefox\Profiles\xxx.default)
I deleted all of the lines in prefs.js that began with
user_pref("devtools.
e.g.
user_pref("devtools.toolsidebar-height.inspector", 350);
user_pref("devtools.toolsidebar-width.inspector", 350);
This fixed the problem while preserving all my bookmarks, saved passwords, etc. The lines in prefs.js were recreated when I next ran the debugger.
I my case I have mistakenly enabled 'Blackbox source' on a file (in right click menu). When I disabled it then the breakponts works again.
I just encountered the same problem - Firefox Quantum 60 on Ubuntu.
Solution for me was to delete the ~/.mozilla folder for my account. Lost all my bookmarks, history, settings, etc., but can now set breakpoints again.
In my case it was 2 check-boxes to check:
I ran into this problem, or a variant of it as well. For me, it was because webpack was defaulting to setting devtool to "eval". This broke stopping at breakpoints in Firefox for me. Changing that setting to "source-map" resolved the issue, though I suspect most other non-eval options would work fine as well.
I noticed this because I looked in the generated JS file and noticed everything was put into eval() calls.
Also, check the console for errors. I've experienced this issue (can't set a breakpoint) when there is an error elsewhere in the page..
I just stumbled across a similar problem. In my case, it was the eye on the lower left of the debugger window.
The breakpoint vanishes after clicking the eye:
Update:
And another way to blackbox a source:
Sublime Linter suddenly isn't displaying the nice ui highlighting it used to. It also isn't displaying lint messages in the bottom left of sublime. This may have happened after a recent windows update, but i wasn't paying close enough attention to be sure exactly when it occurred. I've followed the troubleshooting section on the documentation, and verified jshint is working in the command line. I've also switched to debug mode but I see no Linter errors in the console. I've also tried switching to manual lint mode, but the "Lint This View" option is grayed out. Not sure what to do at this point. Any suggestions?
You mention that you recently updated your copy of Windows, so it's possible that the Environment Variable for node(and other variables) have been removed or erased, I suggest you check that first.
I'm not really sure how to best word this, but let's say I'm on a web page and when I click a certain button, something undesirable happens. Like a whole bunch of content disappears. Is there a way in the Firefox debugging tools where I can insert a watch on that button so when I click it, the debugger will pause the JS execution and show me exactly where in the code it's executing the stuff I don't want?
(note: obviously this is code I did not write, otherwise I'd know where to look to fix the problem)
Yes, in the debugger there is an events pane, and you can break when a specific event is triggered. The documentation is here:
https://developer.mozilla.org/en-US/docs/Tools/Debugger#events-pane
Firefox has a good built-in profiler - you can click the start profile, and click it again to end, and see what parts of the code are running the most.
This is really helpful in finding performance problems too.
I need to debug some JavaScript an' I use Chrome dev tools. I'm a newby in JavaScript (just started to learn a couple of days ago), an' at work I could set breakpoints via the Resources pane. But at home for some reason I can't do this: after the click no breakpoint appeares.
I have Chrome version: 26.0.1410.64 m.
What could be the case?
clicking on the De-Obfuscate Source button (i.e. {}) solved this issue for me.
I'm a fool! haha! breakpoints are set in the Source pane )))
It's been a while, but in version 33.0.1750.146, but my problem was that I was on the Sources pane (I'd call this a tab; it's one of the items at the very top of the window), but I was on the Content scripts tab (on the left hand side). I needed to switch to the Sources tab.
To be clear, there are two sets of Sources tabs; one is within the other.
UPDATE 2016-01-07: Now I'm on 47.0.2526.106. The only thing that worked for me today was to close DevTools and re-open. It was a little finicky. It worked once, then stopped, and I had to close the DevTools and re-open again. I saw #johntrepreneur's answer about closing the browser, but unfortunately I have too many tabs open on too many workspaces, so that's too much of a pain, so I didn't try that, although I have to assume that would work.
Other solutions didn't work for me. Had to close and restart browser to be able to set breakpoints again.
This also happens when there is a JS error in your code.
Some sort of weird built in function in windows 10 i think because I did press a few buttons by accident. Some of my keys even stopped working in certain areas of visual studio. F.e the letter "c" stopped working in the find window.
Mine did this and no solution worked, i pressed alt, windows key and function key a few times and my problem went away.
Fixed as follows: For me, the issue stems from having set up Chrome to interact with operating system files. If you set this up, then the fact is evident from a green dot by the file name. At some point, I could not set a breakpoint in a recently edited file. I fixed this by disconnecting the interaction, as follows: When viewing "sources", above the code, there were some file names listed. Clicking the [x] to make the particular filename go away gave a caution message; I proceeded without saving. After that, I was able to set breakpoints for that file.
I also had this problem. However, once I closed the popup message in my browser, suddenly all my breakpoints that I set in that time appeared. Mental note: Don't set breakpoints while your app is showing a popup.
I couldn't find any direct fix for this problem.
It seems that chrome keeps settings of your site stored somewhere whatever you do to clean it. (I tried removing the folder from workspace, closing et reopening chrome etc... and nothing worked).
A workaround is to change your site's url to make chrome consider it a new site
I have been using JustCode(latest ver) for about 2 months now, and have started just turning it off most of the time.
The final straw was today when I wasted about an hour trying to find out why I was getting an error(along the lines of no overload with those parameters) when I was sure the code was correct. Finally I turned JC off and the error went away.
Why does it wrongly report errors?
Why does it sometimes disable keys like backspace in a normal code block?
Why does it sometimes color the code in an ASPX page like it is commented out(all green), when it is not(after disabling it VS colors it correctly).
There are lots of other niggly problems like if my mouse is over the word im typing intellisense will not come up etc.
So am I using it wrong or something? It really does look like a promising product from the features videos etc on their site - so I hope the problem is with me :)
Sorry to hear you had such problems with JustCode. I suppose you used the Q2 version that was released in July. Some of the problems that you describe – hiding the intellisense, blocking some keys – are problems that others have also reported and were fixed in the Service Pack that was recently released. Please, go ahead and download the latest version. It has other fixes as well than could solve other niggly problems that you may have.
In case you find yourself wondering why some error is showing while you are sure your code is correct – Visual Studio successfully builds the project – try refreshing the code analysis (in JustCode menu choose – Refresh Code Analysis). That may clear the errors. If the error shows even after that – then position the cursor onto the error and hit Alt + Enter (or choose Fix… from JustCode menu). At the bottom of the popup menu you will find Report Good Code Red. This will send over a report for the issue to the team and they’ll contact you with more information on the problem. If you are irritated from the error you can choose Ignore This Error / Warning from the same popup menu.
One thing that you can always count on is accurate and prompt response from the team. If you have any problems or suggestions – please, go ahead and write a support ticket or forum post in Telerik’s web site.
Hope this helps.