I tested this on multiple sites and I have the same problem everywhere. When I refresh the site in Chrome with developer tools open, the site stops and its stuck on loading. In developer tools opens the tab Sources with bundle.js file code and I get and error in console:
Cannot read property 'dataset' of null
Why is this error occurring and how can I resolve this? I tried to restart my computer but its not working. Disabling JavaScript in Chrome is not an option. I have Chrome Version 52.0.2743.116.
Related
I once came across an SO answer that gave a Chrome URL to navigate to, that had a button to "enable" JS console logging. After enabling the logging, that tab would show the console logs of other Chrome tabs.
I know this answer seems like a duplicate, but I'm having a lot of trouble finding how to do that again. It was super convenient since it gave the console logs on any Chrome browser without needing a USB connected.
Any ideas? I know I came across it in an SO question about iOS debugging.
Found it! So, it's actually a Chrome on iOS only feature.
URL: chrome://inspect
That URL won't show anything on Chrome for Android, which tripped me up. But, on iOS it shows a "Start Logging" button.
Answer from: https://stackoverflow.com/a/55433616/2096769
I have some weird thing going on in my machine. When loading a specific website at work and opening the Chrome devtools, the website's tab gets frozen, Chrome task manager shows > 100% CPU usage and all is frozen and unusable.
I’ve tried the following, none worked:
Disabled all extensions
Cleared cookies
Restarted Chrome
When loading the same URL with devtools in Incognito mode, all is splendidly working and smooth as butter.
What can be the problem here? I'm using Chrome version 79.0.3945.130, which is currently the latest
I am trying to add the "add to Homescreen" prompt function to my website. Now I've read the google developer articles and I have everything set up.
Now, If I try to manually add my page to the homescreen with the button "Add to homecreen" in the Chrome devtools > Application > Manifest , nothing is happening. A few times the console showed an error, but after fixing it nothing happens. I don't get the Add to shelf banner, but I don't get an error displayed in the console. Lighthouse doesn't show any error either. In fact, lighthouse shows a score of 92 in pwa.
Is this now meaning that everything is working? Is there an other debug function I've overseen?
Edit: If I press the button and than reload the page, after I press reload and the page is acctually loaded, the console displays:
Site cannot be installed: the page has requested the banner prompt be cancelled
I was having this same issue: Chrome Dev Tools Add to Homescreen was not working on ANY PWA. After days struggling trying to figure out where the problem was I finally found that Chrome main menu has an option to install the app, and that option is working fine. So you don't need to use Chrome Dev Tools option.
If you are testing in localhost, try http://localhost instead of 127.0.0.1.
I don't know why, but I have the same issue when using 127.0.0.1.
After changing to localhost, it works correctly.
Hi I was using selenium chrome drivers as interactive service to open some websites. It was working fine. Suddenly found that the session is not loading correctly and showing black page. Found following error:
chrome automation extension has crashed. click this balloon to reload the extension
Found that with chrome browser version was updated to v51 and selenium-chromedriver 2.21 is compatible with v50.
Downgraded chrome browser to v50. Now it is working fine.
I am experiencing an issue with opening a Microsoft Office Document, using IT Hit WebDAV AJAX library, in latest Chrome 39.0. running on Windows OS. It is a sporadic issue that occurs only in Chrome, and it happens when one opens a document multiple times. Word instance won't start, the page freezes and browser becomes unresponsive, and Chrome suggests killing the page. The only solution is restarting the browser, which solves the issue.
I have tried opening a document in Chrome on Mac OS X, and it is working fine. So are Mozilla and Safari on all operating systems. It seems to be a Chrome + Windows issue only.
Has anyone experienced this issue and is there a fix?
The Microsoft Office plug-in that opens the document displays a warning popup "Some files can harm your computer.", which is a modeless dialog:
If you quickly click on a link that opens the document more than one time the dialog will hide behind the main web browser window. As a result the web browser window is blocked.
You need to switch to that dialog and confirm or reject document opening, otherwise after some time Chrome will ask you if to kill the page or wait.
Note that there is no way to avoid that dialog, this is a built-in MS Office functionality as far as I know.
Chrome will only work good with ITHitWebDAV if the user has got Office 2013 or superior.
Google is blocking all Java applets and NPAPIs now, so good luck with that. I just detect the browser of the user that wants to edit a document, and if it's chrome, I warn him to change to another browser like Firefox with a modal, and that's all.
Very poor support between Chrome and ITHitWebDAV, and no much you can do about it.