I can't find a way to search a string in all .js and .css files on Firefox Developer Edition 56.0b4.
I found a way, but it was before versions 52. I wonder why they removed this feature?
Thanks for help.
While not listed on MDN Dev Tools Search page, Firefox Developer (Quantum) 58 once again includes the ability to search ALL files. I was missing this and almost defected to Chrome, but the tool set is way less intuitive.
From the debugger panel Mac the key shortcut is CMD-SHIFT-F.
The new debugger front end, aka debugger.html, did not have this feature until relatively recently.
For Firefox 56, if you really need this feature, you can try going back to the old debugger. The old debugger is not as nice in many ways; but it does have this feature. The old debugger can be selected via a pref in about:config.
I believe project search is available in the new debugger front end in Firefox 57.
The preference to go back to the old debugger is devtools.debugger.new-debugger-frontend
Related
I'm building an extension for Firefox.
I've checked the javascripts and they work well.
I've tried to make all the modules of the extensions right. But every time I try to install the plug-in into my firefox it says "Impossible to Install.. the component is damaged".
I'm looking for an "extension debugger" that can find the error that makes my add-on not working. Any advise?
I was looking for a link to Firefox background page debugging.
I found this link to Firefox debugging.
It says to follow these steps:
open Firefox
enter "about:debugging" in the URL bar
check the box labelled "Enable add-on debugging"
click the "Debug" button next to your extension
click "OK" in the warning dialog.
I don't think there is a dedicated debugger for that. Look at this article, maybe it can help: http://blogger.ziesemer.com/2007/10/javascript-debugging-in-firefox.html
Regards, Hiawatha
There are some debuggers for Firefox extensions, inparticular Venkman and Chromebug (which only works reliably with Firefox v5).
These will be able to break (pause code execution and launch debugger) when an exception occurs but don't usually help when you've got packaging problems, which are often caused by
Bad manifests - look though Mozilla's packaging documentation, in particular the format of manifests.
Errors in XML - validate all XML files (such as install.rdf).
Referenced files that are missing (e.g. a DTD referenced in the XML that is missing)
With the lack of tools, the best option is often to compare your extension's manifests and directory structure against a known good extension (e.g. an example Hello World extension, or an earlier version of your extension) as something as simple as a wrong entity in a DTD file can cause the error you are seeing.
Is this is a classic extension or the more recent bootstrapped type?
I would recommend to check the text encoding of install.rdf, chrome.manifest and bootstrap.js. Anything else than ANSI would be a cause of troubles.
In Visual Studio 2010 and earlier, the Find in Files feature remembered your selection for the "Look in" option.
In 2012, the option sometimes gets reset to "Current Document", making it only search in a single file. This can be annoying, particularly when you don't notice it's done it.
Is there any way I can force this setting to stick with what I want it to be (generally "Entire Solution")?
As an example of the problem, highlight a few lines of text in a source file and bring up the Find in Files box. It will have changed the "Look In" setting to "Selection". Close it, deselect the text and do Find in Files again. The setting will have silently reverted to "Current Document". Doing this in 2010 and earlier doesn't change the setting.
There's another description of the problem here.
I find that its intermittent (but more often that not) and that its a potential bug. For me it resets to "All Open Documents" which could be far more disastrous.
Do you have any plugins installed as I was thinking of raising this as an issue with vs if its not a 3rd party tool affecting it?
I have the following installed:
Resharper 7.1
Teamcity
Ankh
Entity Framework Power Tools Beta 2
Ghost Doc
Microsoft Web Developer Tools
NestIn
NuGet
Spell Chekcer
SQL Server Compact Toolbox
VS Extensions for Windows Library JavaScript
I guess we should rule out some of these first?
Anyone else find this who has no extensions installed?
Try if the SmartFind extension helps in your case. I wrote it because I had a similar problem.
http://visualstudiogallery.msdn.microsoft.com/015611c4-b357-4672-8977-f3ec92f0b808
Source is here: https://github.com/laktak/vs-smartfind
What worked for me is under keyboard customization i made it so Ctrl-Shift-F maps to Edit.SwitchtoFindInFiles instead of the default (Edit.FindInFiles). I did also install the SmartFind extension (mentioned above in this tread) but by itself it didn't seem to fix it. I'm not sure if it's the combination of the two that fixed it in my case. Also note that this applies to VS2012 so YMMV.
I always use ctrl + f to search in document and ctrl + shift + f to search the entire solution.
Might not be an answer to your question, but it should solve your problem.
I am unable to debug at al in Chrome. I set it as my default broswer but when I try to debug, I see Connecting to 127.0.0.1:7930 in the Debugger window, but nothing happens (Chrome doesn't popup or anything). I have no idea how to trouble shoot this....any ideas?
If you are not familiar with, and believe me its worth checking out...another alternative is to use the Chrome developer Tools Built into the browser
You can debug javascript (add breakpoints and step into over, view variables), edit css and see your modifications in real time and save changes back to your file system. It also has a revision history for changes you make and you can revert back to any version! You can use use these Chrome developer tools in conjunction with the free Netbeans IDE where you can create your HTML, CSS & Javascript which has excellent code hinting / completion with Jquery support. You also add plugins to add more functionality.
Well I could not figure out how the heck to get Webstorm to debug with Chrome and their support is extremely limited. So as a workaround and what may be better because its free , is use Eclipse with Chrome Developer tools.
You are able to debug all the JavaScript files on your server and set breakpoints. I haven't stepped through while debugging, but this seems very promising. You could use Eclipse as well for the development of your corresponding HTML and css files or use in conjunction with Netbeans which is also free. Very straightforward if you are familiar with Eclipse already:
Eclipse with Chrome Developer Tools
For a couple of days I had noticed that the "script" tab of firebug had not been working. I ignored it because I wasn't working with javascript at the time.
Then the day came I was going to need that script panel, which still wasn't working, so I decided to reinstall firebug.
And now, when it's installed, it's just plain gone. No icon that I can see, neither on the bottom bar nor the top bar. No mention of it in the tool menu. The only evidence it's installed is an entry in the extensions list and a file in the extensions folder.
I've tried googling but have not fond anything that sounds like my issue.
I'm using firefox 6 on Windows XP.
For some reason, Firebug changed it's toolbar button (and removed the old one) from the old bug to a blue default cursor over a width, short box. Right-click on a toolbar, select Customize, and look for the icon next to the bug at the large picture of Firebug at top of this page:
http://getfirebug.com/html
This is the button you're looking for (download the raw file to view):
http://code.google.com/p/fbug/source/browse/branches/firebug1.9/skin/classic/inspect.png
You might try checking if it's profile-specific to start:
http://support.mozilla.com/en-US/kb/Managing-profiles
Try disabling any other extensions you have installed?
Debugging asp.net websites/web projects in visual studio.net 2005 with Firefox is loads slower
than using IE.
I've read something somewhere that there is a way of fixing this but i can't for the life of me find it again.
Does anyone know what i'm on about and can point me in the right direction please?
Cheers
John
edit
sorry rob i haven't explained myself very well(again). I prefer Firefox for debugging (firebug etc)
hitting F5 when debugging with IE the browser launches really quickly and clicking around my web application is almost instant and when a breakpont is hit i get to my code straight away with no delays.
hitting F5 when debugging with FireFox the browser launches really slowly (ok i have plugins that slow FF loading) but clicking around my web application is really really slow and when a breakpoint is hit it takes ages to break into code.
i swear i've read something somewhere that there is a setting in Firefox (about:config maybe?) that when changed to some magic setting sorts all this out.
bingo. found the article i read before.
i just changed my network.dns.ipv4OnlyDomains property in about:config to localhost. restarted firefox and now firefox performs the same as IE when debugging asp.net with visual studio (2005).
hope this helps anyone else that has the same problem.
"Alternative solution". Do the following in Firefox
about:config in the address bar
set network.dns.disableIPv6 to true.
Are you serious? One of the main reasons I stick to Firefox is because its so much nicer to develop with..
The live source update is awesome (view source > change code > rebuild > F5 in source)...
What is actually "slow".. I mean, the some browsers tend to be slower at rendering, but I dont see how it affects your debug time? As soon as the request is made, and your breakpoint is hit in the code, it stops?
For quick debugging try this..
Add Debugger.Break() into your code at an appropriate place.
Browse to the page in firefox (via localhost) if on local dev machine? and the Visual Studio Just in Time debugger should pop up.. select the currently open instance of Visual Studio and you can step into the code where every you want without having to start from the beginning or jumping to cursor.
-- Lee