Problem with console source in google chrome browser - javascript

I have faced a problem for a long time in the chrome browser, the point is that when I open the console in the chrome browser and open the "Sources" item, my project folder is not displayed now in more detail
I am developing a React application and I often need to insert debuggers to check something when I run the application in the Microsoft Edge browser everything works well.
Please now pay attention to what is happening in the google chrome browser
What could be the problem?

Related

Chrome DevTools for Node.js not loading source maps

I am working on a node.js API. We use typescript and I use Chrome dev tools for debuging. In the last day when I started the chrome node inspector it could not load my resource maps. I tried making a small mock project and it happened for that one too.
The warning it gives is DevTools failed to load source map: Could not load content for file://<path_to_source_map>: No setting registered: network.enable-unc-loading. I have the latest version of chrome 105 and I am on macOS 12.5.1.
I was thinking it might have something with mac permission but when I take the link to the file file://<path_to_source_map> and open it in browser it can open my file and I can add the file trough workspaces but it cannot link them even if I do it manually. I do not know if it is a chrome setting or what.
Any ideas ?
I've found this setting:
But this setting is not available in the Dev Tools console for Remote Targets so it didn't fix the issue.

Google chrome screen content freezes

We have an old web application (javascript jquery + css) that it is displayed in a lot of displays (google chrome browser), randomly (we do not know the casuistry) the browser active tab content freezes. We can open a new browser window and it woks normally.
The javascript does changes to the DOM and we can see them in developer console, but the content does not change.
We also tried to override the DOM through the browser console with same effect.
We tried to do a location.reload() and we saw in the console that browser downloads all (javascript, css files etc..) but the screen continues unaltered.
The software version we are using:
Browser: Google chrome 44 (same version in another installations and we never experimented this issue before)
OS: Linux Centos 7.2
Graphin card Drivers: Nvidia different versions.
Different configurations tried (not solving the problem):
- GPU enabled
- GPU disabled
Currently we are trying this actions to see if solves the issue (we do not have results yet )
- Update Google Chrome to latest version
- Update Nidivia drivers` to latest version
Any idea about why is this happening?
Any help would be appreciated.
Thanks you all very much.

Google Chrome Push Notifications not working if the browser is closed?

It is written here that the push notifications will work even if the browser is closed, but I tested it and it is not the case. I receive push-notifications only if the browser is open (doesnt matter if the particular webpage is open or not).
I tested this on chrome for Desktop & chrome for Android (after updating to latest version).
my question is :- For push notifications to work should the browser be open?
Note:- I used this for testing.
According to Can I Use, Chrome and Firefox desktop browsers require the browser to be running for receiving push notifications; mobile browsers typically don't.
Open Settings (in chrome)
Do the following:
> advanced
> system >
"continue running background apps when chrome is closed"
>enable
On desktop, browsers need a process running. For example on Mac OS X the browser can have no window open but if you look at the dock, the light underneath icon can be glowing (meaning it has a process running). In the scenario you should receive push messages.
If the browser was completely quit, then push messages won't get through.
The same applies to windows and Linux.
On android you should be receiving the messages regardless of whether the browser is open or not. This is in part (as far as I know) to the fact that android manages it's connection to the push service rather than the browser, so it'll receive messages whenever possible.
The messages should (eventually) get through even if they are sent while the browser is closed, or the device is offline, etc. (And this works for me using https://gauntface.github.io/simple-push-demo/ and other tests.)
I've worked on demo to provide push notifications on Google Chrome and Firefox. Demo -> https://twitter.com/d_danailov/status/1163824171480166400
If someone has a question could ping me on twitter.
The public URL: https://push-notifications-ddanailov.firebaseapp.com/
Repo: https://github.com/dimitardanailov/push-notifications
On desktop the browser needs to be running since that is the process that receives the push messages. Some extensions, like hangouts force the browser to keep running even when the last tab is closed so for users with one such extension installed push will work all the time.
On Android, the browser does not need to be running since the entity in charge of receiving the messages is baked into Google Play Services.
The Chrome team is working on the desktop issue in https://bugs.chromium.org/p/chromium/issues/detail?id=402456
It is possible to write Chrome extension where background script can run if Chrome is allowed to run in the background (configurable in settings). It can also use GCM.
EDIT:
For service worker to run in the background even if no tab or window is opened there must be at least one Chrome extension with background permissions installed and Chrome must be allowed to run apps in background. Tested on Linux.
Yes, the other users are right and there is no way to receive them on Windows if the browser is closed unless the browser is running in the background, which some Chrome Apps and Extensions can force. I ran into this recently and found this extension, which I believe may help. It keeps the browser running in the background even if the windows are closed but does not do anything besides that (it is open source and presumably the version uploaded to the Chrome Store matches that version)
https://chrome.google.com/webstore/detail/lightning-reopen/ahphokgmcecbjeipkfkamcdmemghkaph

Bad performance in chrome running this site

This is my first website , it running good in IE but bad at Google Chrome
especially when zoom in and out
http://robovics.com/e-dec_Admin/project.html?id=0&name=Project1
how i can know why?
If there any performance analyzer tool to check the problem
So, conveniently enough there are developer tools built into Chrome (as well as every other major browser) that let you profile, debug, or inspect the performance or source code of a webpage. To open the console CTLR+SHIFT+I (Windows) or CMD+OPT+I (Mac). Now you'll see a console at the bottom of the webpage go to the Network tab at the top of it and refresh the page; it will tell you how long its taking Chrome to load the resources for your website. For even more insight check out this link. I hope that helps.

Remote debugging javascript on iPad from a Windows machine possible?

I have an iPad with iOS 6.1 connected to a windows 8 machine. I would like to be able to debug some javascript code running on the iPad.
The safari on iPad has a web inspect option that needs the iPad to be connected by wire to computer and then can be accessed in Safari for desktop's develop menu. I installed Safari 5 for Windows but don't see the iPad detected in the develop menu.
Any other ideas ?
The Firefox Tools Adaptor allows one to use Firefox DevTools for Safari on iOS.
https://github.com/mozilla/valence#debugging-safari-firefox-and-other-webviews-on-ios
For remote debuggin I use Weinre.
Weinre has almost everything you need, but lacks a JavaScript debugger.
It has a WebInspector for DOM manipulations, network traffic, timeline, resources and a console.
Checkout this project on GitHub: weinre-remote-debug to setup weinre locally.
Another option described on this page is jsconsole.com. By appending a <script> tag to your page (or running a bookmarklet on your device) you get access to a JS console.
To start, go to jsconsole.com and run :listen in the prompt. This will give you a unique session ID and a script tag that you insert into your mobile web page.
Now, any console output that your mobile page generates will be streamed to the console open in your desktop web browser, including any errors!
It is certainly no replacement for a full web inspector, but it can get you out of trouble when you don’t have access to a Mac.
Source: https://blog.idrsolutions.com/2015/02/remote-debugging-ios-safari-on-os-x-windows-and-linux/

Categories

Resources