My questions is regarding the startup order of the two events chrome.runtime.onInstalled and chrome.runtime.onStartup when Chrome was updated and restarted. Does onInstalled fire when Chrome is updated and before getting restarted, or after Chrome is restarted but after onStartup
onInstalled is fired when the extension is first installed, when the extension is updated to a new version, and when Chrome is updated to a new version.
onStartup is fired when Chrome is starting up.
Related
When I press F12 in IE11 (v.11.1016.18362.0) to open developer tools first time it shows an exception with text
Check dependency list! Syncronous require cannot resolve module
'serviceHub'. This is the first mention of this module!) [3040]
iexplore.exe.
Sometimes if I need to debug JS, it shows that error window about 5-10 times and I close it one after one...
I tried:
Removed and install again IE11 in windows components
Replaced files in C:\Windows\System32\F12\
Installed all Windows updates
Disabled all extensions and helpers in IE settings.
What else can I try?
When I tried to debug it, I see an exception in with text
"There was no method handler registered for the
'getTranslatedLocation' method."
But I have no plugins in IE enabled anymore.
The solution was just to set checkboxes "Disable debugging (Internet Explorer)" and "Disable debugging (others)" in IE11 settings.
I have developed a chrome extension that i have tested successfully in two different computers (Linux and Windows systems) with Chrome version 76.0. The first line of this extension is a console.log("test") which is obviously showing in the developer console every time i start chrome. The problem I face now is that when testing the extension in a MAC computer (which should not make a difference?) with Chrome 76.0, it is installed successfully but it never starts. Not a single log is shown (yes, i checked that logs are being shown) and it is not working at all. No error are shown in the console and no errors in the extension settings tab. I have no idea what is going on here.
I have msi which installs extension using windows registry as described here https://developer.chrome.com/apps/external_extensions#registry. It works fine as extension is hosted on CWS. After extension is installed, notification popup is shown to enable/remove extension.
I have created upgraded msi which contains updated nativeapp as well as new extension. When I run new msi old extension entry is removed from registry and new extension entry is added into the registry ( both extension have different ids ). At that time some times, Notification popup is not shown for newly added extension. New Extension is installed however, it is disabled and old extension is removed.
I event tried to restart chrome but extension notification popup is not displyed as it looks like newly added extension is blacklisted.
Is there any way so that user can be prompted with popup to enable/remove extension in this case?
I play with CDP and Puppeteer libraries with Node.js. I want to capture keyboard event within browser window (not window or document objects at webpage context) context - so when I am in Chromium DevTools (runned by Puppeteer) and press i.e Ctrl + E combination (which fires Performance test in Timeline tab) I would like to capture this event.
I managed to do that with RobotJS library, but it does not support the latest Node version (v8.7), so after updating Node I cannot even install it. I found iohook lib, but it does not support latest Node neither as well as Windows (which I use).
CDP and Puppeeteer libs AFAIK supports only events within webpage context only.
I also tried Node native module readline, which however captures keyboard events in console, but not in browser window.
Is there any way to capture/listen to keyboard events in Chrome/Chromium browser window via Node.js?
iohook at this moment support Node.js 8+ but still don't have prebuilt versions for windows.
You can try use windows fork of iohook
Or you can compile original iohook in your windows machine
I've recently upgraded my player to v. 0.8.8. I'm now no longer able to see my code changes when I do a right-click "Reload Application"
When looking at the "Network" tab in the inspector - I'm seeing that my javascript assets are pulling from cache. Also: in version 0.8.5 of the player, there was an option in the inspector settings to disable cache. This option is no longer available in version 0.8.8.
Long story short: there is no way to disable cache in the new 0.8.8 player and thus any changes to code in development require a complete restart of the application. In 0.8.5, righ-click and then "refresh" were enough.
I'm on Windows 7 x64
Spotify 0.8.5 inspector:
Spotify 0.8.8 inspector:
How can I refresh my assets without quitting out of the application in the 0.8.8 player?
The disabling Javascript caching option will be reintroduced in a later version of the Spotify client. Unfortunately, at this point in time I can't tell you in which version or when it will be released.