Chrome isn't doing this; ChromeDriver 2 is. ChromeDriver 2 and the DevTools windows both compete for the same automation channel, and ChromeDriver automatically closes the DevTools window in order for it to work. See https://sites.google.com/a/chromium.org/chromedriver/help/devtools-window-keeps-closing for more info Also see the related issue: https://code.google.com/p/chromedriver/issues/detail?id=483

The weird thing is that instead of the tab being labeled MyJavascriptFile.js it reads VM or some other number. This is because you are accessing your script through localhost, and therefore running into security policies. If you host your file at an IP or domain name, you'll be able to debug normally again.

I am having the same problem with unchecked styles. I found a slightly easier way of saving the unchecked styles. Just uncheck the style, add another temporary style to your rule and then delete the temporary style. Chrome will document the changes and you will be able to save your unchecked (commented out) style with the "Save-as..." feature in the "Sources" tab. This is not ideal, but it saves you the hassle of unchecking and modifying a style, doing a "Save-as..." and then going back and changing the modified sytle back to the way it was. I will definitely bring this up in the Chrome support forum.

No, this is not possible directly. You have to have DevTools open for it to log requests. There is a work-around though: This is similar to https://code.google.com/p/chromium/issues/detail?id=178918 - use remote debugging locally (https://developers.google.com/chrome-developer-tools/docs/debugger-protocol#remote).

Here is the code of the page <div id="speedbump"> <span class="internal"><p>The page you are going to on usbank.com is not optimized for viewing on a mobile device.</p></span> <div class="continue">Continue</div> <div class="cancel">Cancel</div> </div> They are using a confirm dialog, but the HTML is right there. People don't believe me... so here is a picture, take a look now :D

To disable the source maps for one file: You can filter out the messages for the .map files by right clicking them in the console (Not the link) Selecting Filter > Hide messages from ... You can also disabled either CSS or JavaScript source maps globally from the Developer Tools settings. To disable the source maps globally: Click the cog icon in the bottom right of the Developer Tools Locate the 2nd and 3rd options on the right under Sources Untick Enable JS source maps Untick Enable CSS source maps

What you tried to execute is a JavaScript pseudo-scheme. Note the javascript: part at the beginning. Doesn't it sound familiar with other schemes like http:, https:, ftp:? It would be executed in the URL, not in the Console. In other words, you use JavaScript pseudo-scheme to execute a piece of JavaScript code, in the address bar of the browser. To execute it in Console, you have to do two things: Remove javascript: scheme Because it's supposed to be executed in the URL, it's URL encoded. You have to decode it first. See that %7B? It represents {. Console won't recognize it, till it's decoded to the original character.

I agree you would probably need a plugin. You can however create a view-source link (though no line numbers): <a href="view-source:http://stackoverflow.com/questions/18660106">view source</a>

Yes, there is a way to force an elements state using chrome devtools; if you look on the right side you should see an icon that looks like the cursor with a broken box behind it on the 'styles' tab. When you click on it, it will have a dropdown menu that will allow you to toggle the selected code's hover, active, focus and visited pseudo-classes.

On the bottom of the devtools window, to the left of the error and warning icons, there should be a set of console output filter buttons. See below for a description of the filter options. Note the funnel button to the left of the "All" button. You must check the type of output you want in the funnel-menu. The funnel menu is active for all filter-button options. So if you select the "Logs" button but have "Logging" unchecked in the funnel-menu, there will be no logging output. Both funnel-menu and filter-buttons can be multi-selected. Ctrl-click, Windows, or Cmd-click, OSX, to select multiple filter-buttons. From the docs All—Shows all console output. Errors—Only show output from console.error() Warnings—Only show output from console.warn() Logs—Only show output from console

I think you want: window.myVariable But, I recommend you read up on coffee scripts handling of scope. SO reference

The code you show is minified, that's why it's only one line and not readable nor directly debbugable. But you have a small button { } at the bottom left of the screen you show (the fifth from the left), it lets you beautify the code. Click on it. You can put breakpoints in this beautified code in a much precise way.

You can never 'trust' input from your users. Whatever you do. With developer tools you can easily add HTML into a website and post the values to the server. You could even edit the POST itself and add whatever data you want. Security and checks need to be done server-side. You can simply use your jQuery show/hide and do the validation server-side.

I'm the creator of Restangular. So, when you're doing a getList, Restangular expects to get an Array as the response. In your case, when you're getting a list and the path is availableCourses, you're returning a string (the title) which has properties. So you're creating a "special" string with properties, it's not really common, nor compatible with Restangular. If you want to get the list of all available courses, you need to return an array as the new response. So, what's the exact response from the server when you do the getList? If you giv eme that, I'll be able to help you easier on how to create this response extarctor. Also take a look to this MongoLab example :), maybe It'll help you. http://plnkr.co/edit/d6yDka?p=preview Bests!

After a careful review of the W3C standards surrounding this issue, it seems clear that this is a browser bug (albeit not a serious one). The discrepancy exists because the non-AJAX method being used was presumably chosen to be more "friendly" and maintain consistency between the code and the presentation, whereas the AJAX method is more respectful of the true W3C specification. Such is the result of any collaborative development effort. For those who are hoping to avoid any such inconsistencies, I recommend you use the following syntax: $('#some-id').prop('checked', true); // Preferred method for checking a box or radio button ... instead of: /* DON'T USE THIS CODE! $('#some-id').attr('checked', 'checked'); // Deprecated method for checking a box or radio button IF YOU DO, IT'S ON YO

In previous versions of IE and in all other modern browsers you can't tell if the Developer Tools or Web Inspector are open. I assume the same is for IE10. You can check if the browser supports console logging by using: if ('console' in window) { if ('log' in console) { console.log('This will work.'); } } IE8 and below may not support console logging, so it's wise to check if they do before logging to the console in your code.

If you hit F12 and only see File, Find, Disable, View, Images, Cache, Tools, Validate, Browser Mode my guess is that the console is minimized. Try Ctrl + M or clicking on the restore window button located to the right of the Browser Mode display. Hope that gets you going.

Javascript runs on the client, and many browsers allow you to change javascripts, not just the variable values, but also inserting or deleting lines etc... For this reason, you should always sanitize incoming data on the server side, even if it is coming from your own website.. In general, you should only consider javascript as a means to improve the UI and user's experience, but never as a means to validate, secure pages or do important business logic. There are some handy functions included in PHP for handling variable validation

Changes made in the IE10 developer tools don't persist beyond the current browser session. Based on the symptoms described, you have the site configured to run in Compatibility View, which is a browser setting. Untick the "Broken document" icon in the Address bar, or click Tools > Compatibility View settings and remove the site.

I don't know of any way to follow the requests across pop-ups, as each window has its own Web Inspector, however you can use Fiddler to inspect HTTPS requests. It will MITM, and subsequently throw a certificate error, which should allow you to inspect all requests in the order that they happened.

You're probably filtering out your CSS warnings. They're filtered by default. Click the filter and check:

Unfortunately I can confirm your suspicions, there is no 'Always refresh from server' feature in F12 tools in IE 11 preview as far as I can tell. There is clear browser cache button you mentioned which does nothing. Currently the only way to get fresh content from the server is to refresh IE11 with Ctrl+F5 keys combination. IE 11 is still in preview, so let's hope MS will at least fix clear browser cache button before official release.

Which version of Safari are you using? I am using its 6.0.4th version. Well even I could not find the option to add watch expressions but at the bottom of the debugging window there is one more down arrow icon near continue script execution icon. Clicking on the icon you will get one console and you can see the value of the expressions you are interested in. Hope this helps you a bit.

Whilst not ideal I would have to suggest using firebug lite. https://getfirebug.com/firebuglite It will at least give you half decent tools to view these kind of things.

You are referring to a wizard that helps you build your initial application. It creates a generic icon and labels it ic_launcher.png and places it in each of your drawable folders. If you want to change your icon just name your file "ic_launcher" and size it according to Google's standards and place it in each drawable directory. There is also a final file ic_launcher-web.png in the root of your project that you must replace as well. If you want to use a generator to make your icon you can use the Android Studio Launcher Icon tool here. Just create it and follow my above steps for setting it up. Finally a note from Google on proper icon sizes:

Not exactly an answer, but I tend to keep a http://jsbeautifier.org/ window open for such things. Get cursor in field, Ctrl+A, Ctrl+C, go to beautifier window, Ctrl+A, Ctrl+V, click "Beautify Javascript or Html"... the whole keysequence + mouse movements is not immediate, but it is pretty quick. You could also use Fiddler2 and add a JSON formatter if your company would allow installation of that.

It's specifically for developer purposes. They can monitor the handset's "behind-the-scenes" activity down to every bit. You can use this to monitor how your app or other apps are working with your device. You can see how much CPU they are using, the layouts in the UI and much much more. See this guide.

This is kind of hacky, but might be able to get the job done. $filesBefore = get_included_files(); //after get_template_part( 'content', get_post_format() ); $files = array_diff($fileBefore, get_included_files()); echo '<pre>' . $files . '</pre>'; This should show you the difference between the files that had been included before the line you mentioned and then afterwards.

The problem is here: Matcher object = OBJECT_NAME_PATTERN.matcher(line.trim()); String objectName = object.group(1); You created the matcher, but you didn't tell it to actually do its work on the string. As a result, even if there was a match you'd have no groups available. You need to call one of the matching methods (.find(), .lookingAt() or .matches(), but all three will be equivalent for you since your regexes are anchored both at the beginning and end of input), and then collect the groups. Example (.find()): Matcher object = OBJECT_NAME_PATTERN.matcher(line.trim()); object.find(); // or you could have an if statement here String objectName = object.group(1);

In chrome developer tools you can put break points in your viewmodels and step through the code. Also, durandal logs your viewmodel objects that have been composed to the console.log so you can see the state at which they were bound to a view. Here is another way which is just making use of the mechanics of requirejs to get a reference to your viewmodel object programmatically. Just type something like this into your chrome console: require(['durandal/pluggins/router','yourViewModel'], function (router, vm) { // here you can do whatever you want now to your router or vm. vm.someproperty('changed'); router.activateRoute('page2'); }); You can even make a global reference to the objects you want to change by doing this in the console: require(['durandal/pluggins/router','yo

There's no way to hide the console window entirely, but all output from it should be tee'd to Output window, so you can use that if you don't like the console. There's also a Debug Interactive window (Debug -> Windows -> Python Debug Interactive) that you may find of help, if what you want specifically is being able to stop at breakpoints and then work with variables etc in a REPL environment. Once enabled, this window will provide you a live REPL of the debugged process, and when you're stopped anywhere, you can interact with it. Like Output window, it does not suppress the regular console window, but it mirrors its output.

This is actually the REAL code behind instantiating $ Take a look at the github source jQuery.fn = jQuery.prototype = { // The current version of jQuery being used jquery: core_version, constructor: jQuery, init: function( selector, context, rootjQuery ) { var match, elem; ..... and then at line 263 // Give the init function the jQuery prototype for later instantiation jQuery.fn.init.prototype = jQuery.fn; Since you are using the minified version, this gets turned into what you see.

$ is a function, just like any other function function sum(value1, value2) { return value1 + value2; } it is called like var result = sum(2, 4); Therefor, selecting a element using jQuery would look like this: var result = $("a");

The obvious solution is to use Console. It gives you much more tools than simple console.log: Formatting (console.log("%cThis will be formatted with large, blue text", "color: blue; font-size: x-large");) Measuring time (console.time("Array initialize"); longRunningOperation(); console.timeEnd("Array initialize");) Grouping (console.group("Authenticating user '%s'", user); authentication(); console.groupEnd();) Marking events on the timeline (console.timeStamp("Adding result");) This should be more than enough to create readable log of custom events. See the official docs for more tips on using the Console.

This is due to the Ad-block or some plugin you are using with the chrome. Disabling the ad-block/plugin which blocks the requests will fix your issue. It blocks all the requests and so it is pending. Try to fix this way and share the status.

Overriding the UA doesn't make a browser behave like another browser. It just changes the value of the User-Agent header sent to the server and to any JavaScript code that checks navigator.userAgent.

This is a fairly broad question that potentially has many solutions depending on your exact needs, scenario and skillset. Also, it's always best to post an attempt at the problem to get a better response. One solution would be to simply hide (display: none;) a sticky div that is attached to the bottom of the window. To show/hide you can use js and either a button/link or try something like http://plugins.jquery.com/project/hotkeys if you want to activate it with a keyboard shortcut.

If some element is inserted to your DOM and you want to find code responsible for adding it then I suggest using more appropriate tool than debugger;. Check out "subtree modifications":

Ug coffeescript. That aside, anytime you're memory leak hunting with jquery on the page you need to disable the jquery dom cache. In my brief playing with the example site you've linked to, I'm pretty sure some of the detached nodes I'm seeing are in that cache. $.expr.cacheLength = 1; This is very poorly documented, but should help you hunt down where your actual leaks are coming from.

So are you asking if you can use jQuery to prevent people from running additional javascript/jQuery from the browser console? No, you cannot do this, the console is built into the browser for developers to test and experiment with by running additional javascript after/while javascript on the page is running. Same thing goes for other browsers as well.