Some chrome extension doesn't work on chromium.
This for example: http://code.google.com/chrome/extensions/samples.html#5d81304a17cf7ac2887484f730fbd2b01e51e166
How can I get it to work on chromium ?
I can successfully load it (Chromium 18.0.1025.151, Ubuntu 11.10).
I only encountered one problem, when I literally dragged the code to nano: Some newlines were truncated, causing code to be commented. Check whether you correctly copy-pasted the code.
When the extension loads, but "nothing happens", check the console for errors. The console for the background page can be opened by following these steps.
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 am running Node.js on localhost:3001 and unintentionally wrote some code with an infinite while loop. This locked up Chrome to the point where the only resolution was to kill the browser. Since then, I found the problem in my code using Firefox, and fixed the code, but even after restarting Chrome, it will not load my page. I even changed the port that the server runs on, and the cache is disabled with developer tools open - Chrome simply refuses to load the page. I see a single request to the server for the page, but in Chrome it just registers as Pending.
Has Chrome maybe flagged this page as suspect, somehow? How do I get it to play again? I would at least expect Chrome to offer some opportunity to kill a tight loop - like Firefox does - but I've yet to see it. Is there some setting I can tweak? I'm on version 74.0.3729.169 (Official Build) (64-bit), although now that I opened the About page, I see that it is updating Chrome, so maybe that will fix it.
UPDATE: It didn't fix it, but it works in Incognito mode. ???!!!
UPDATE: Disabling all of my extensions also didn't fix it!
I found a setting in Chrome: "Continue to run background apps when Chrome is closed"
I turned that off, and now it works again.
I have made a webpage using Polymer. The webpage doesn't open on Google Chrome (both Windows and Android). When I try to open the page, Chrome shows "He's Dead, Jim!" message on Windows and "Aw, Snap!" message on Android. I have reset the settings and reinstalled Chrome but the problem still continues. Can anyone tell me how to solve this problem or the reason behind it?
https://www.googledrive.com/host/0B2Zii8voDW6QcGduNnl1cFBReXc/fold/
maybe you can check if there is any error in your page, which stop polymer initialization:
https://www.polymer-project.org/docs/polymer/debugging.html#unregistered-element-bookmarklet
Btw, did you try the official demo page with your browsers? If they work, then it's your code problem.
Chrome console tells you what line in the parsed file JavaScript syntax errors are located. Every once in a while, when I click on the link to take me to see the actual code of where the error is, I get a blank screen in the console. If I open up the same page inside Firefox with Firebug, I can see the error code without any issues.
Is this a known error in Chrome? If so, are there any ways to remedy it?
Here is an official list of known issues with Google Chrome. It doesn't seem like that is one of the known issues. I would try again and see if it happens again.
it is a problem of "same origin policy" on local file, i have tried that
C:\somewhere some folder\chrome.exe" --allow-file-access-from-files
don't work, now i am working javascript on localhost(web server) ...my situation is ridiculous, it make the "iframe loading" and xmlhttprequest(which not work for local files) have no difference for scripting.
Does chromium just the same function as chrome except "--allow-file-access-from-files" works? if not , writing code for ie,chrome,chromium just create one more issue but solve one.
--allow-file-access-from-files works for me on Chromium under Ubuntu. However, you have to close Chromium completely before this, because otherwise it will just open a tab in the existing Chromium process (which was presumably not started with that option).
Otherwise, this is just bug 40787.