google-chrome-devtools

How to bring up mobile keyboard in chrome dev tools?

早过忘川 提交于 2019-11-29 06:37:11
I'm trying to test which keyboard type comes up by default for certain inputs on iOS and Android. Is there a way to bring up the on screen keyboard in Chrome devtools phone simulator? So far I have tested the iOS version of my website by running the xcode simulator and pointing to my website but it would be really convenient to use devtools. Thanks! You can view the standard keyboard for the Nexus 5X device for the portrait or landscape view: However, you can't interact with it, nor does it change based on the context it is called from. I found by inspecting DevTools that it is simply an image

Chrome Dev Tools is it possible to keep open even after window closes?

吃可爱长大的小学妹 提交于 2019-11-29 06:33:26
问题 I need to see the network traffic for a particular site of which I have no control. The problem is that the site at one point triggers a pop-up which automatically closes when a particular upload event is completed. The HTTP requests I need to see, are only triggered at the moment of close which is when the upload completes. As soon as the window closes, so does the Dev Tools window. Is there any way to force it to stay open? What about IE and Firefox? Other tools that are not browser

Does Chrome retain each object's constructor?

谁说胖子不能爱 提交于 2019-11-29 06:17:05
问题 In Chrome's JavaScript console: > function create(proto) { function Created() {} Created.prototype = proto return new Created } undefined > cc = create() Created {} > cc Created {} Created is a function private to the create function; after create completes, there are no (known to me) references to Created . Yet Chrome can show the function's name at any time, starting from the object created by it. Chrome didn't achieve this by following the "naïve" approach: > cc.constructor function Object

How do I get the screen size to show when Chrome console is open?

杀马特。学长 韩版系。学妹 提交于 2019-11-29 06:10:44
问题 I just upgraded to the latest version of Chrome (49.0.2623.87). I'm noticing a slight feature missing. If I was inspecting a page with the console open and I resized the browser, in the upper-right hand corner Chrome used to have a small indicator of what the browser viewport size was. That's now gone. How do I get it back? 回答1: Known bug, already fixed: https://bugs.chromium.org/p/chromium/issues/detail?id=582421 It should land in M50. If you need it sooner then it is currently in Canary

Chrome 73: Can no longer debug NodeJS with Dedicated DevTools for Node

纵饮孤独 提交于 2019-11-29 05:28:53
I've just upgraded my Chrome to 73.0.3683.75 (Linux) and now cannot get my dedicated Node debugger to actually debug a running instance. Even though I can see the "Debugger attached" message in the console: $ node --inspect-brk hello.js Debugger listening on ws://127.0.0.1:9229/864a1c18-5e45-49ab-843c-77a22841ffff For help, see: https://nodejs.org/en/docs/inspector Debugger attached. the debugger window does not show any signs of debugging a target: Anyone has an idea if this is broken in Chrome 73 or if I'm doing something wrong? Thanks! Yes, it's a bug with v73. I am also seeing it https:/

What is the System objects in chrome javascript memory profiler

徘徊边缘 提交于 2019-11-29 05:10:31
问题 I'm profiling javascript application using Chrome dev tools. I see that the only memory area that grows is System objects total. I wonder how could I understand what causes such behavior as there are no details in the tool showing which system objects got leaked. I've taken a look at app allocation, but it doesn't change much over time ... When I'm using timeline feature heap grows over 500mb 回答1: According to the JSHeapSnapshot.js implementation in Chromium, as mentioned in a comment by

Console.log not working at all

旧巷老猫 提交于 2019-11-29 05:02:11
问题 A bunch of code isn't working and I'm trying to identify where the problem lies but console.log() isn't logging any results in Chrome Dev tools, am I doing it correctly? $(window).scroll(function() { $('section').each(function(){ var id='#'+$(this).attr('id'), off=$(id).offset().top, hei=$(id).height(), winscroll=$(window).scrollTop(), dif=hei+off-($(window).height()); if (winscroll >= off && winscroll<=dif) { console.log('first broken'); $(id+' .sticky').removeClass('abs').addClass('fix'); }

How to know in which file that defined a js global var in chrome console?

左心房为你撑大大i 提交于 2019-11-29 04:59:19
问题 How to find out which file and line a variable was defined in using google chrome console? For example, the variable Native (from MooTools) has been defined in global scope. I want to know in which file that defined this variable using google chrome console. 回答1: Using chrome : Open the Web Inspector Show the console and check if the var you're searching for exists (ex : Native Enter ) Click on the Resources panel Enter Native= , var Native or Native = in the top right search field You've got

How do you use chrome.tabs.getCurrent to get the page object in a Chrome extension?

主宰稳场 提交于 2019-11-29 04:54:35
问题 The code is meant to output the current tab object for the page the user is viewing to the console but it just outputs undefined. It's run from within a browser action page. chrome.tabs.getCurrent( function(tab){ console.log(tab); } ); I've looked at the documentation and as far as I can tell the code seems to match what it says. 回答1: Try: chrome.tabs.getSelected(null, function(tab){ console.log(tab); }); 回答2: The method getSelected() has been deprecated since Google Chrome 16 (but many

Chrome not showing OPTIONS requests in Network tab

旧街凉风 提交于 2019-11-29 04:47:12
My web client application is setting HTTP POST requests via fetch API. I see that OPTIONS preflight requests are sent via debugging proxy (Charles Proxy), but they are not displayed in Google Chrome Developer Tools\Network tab. I don't have any filters setup on the network tab. I remember OPTIONS requests being visible there, but not anymore. How do I bring them back? You'll need to go to: chrome://flags/#out-of-blink-cors, disable the flag, and restart Chrome. This is an expected behavior change according to: https://bugs.chromium.org/p/chromium/issues/detail?id=995740#c1 I originally came