I want to add my extension options menu in system tray icon of Google chrome. I searched it a lot but not found even a hint. Here I saw one extension added it.
Could anyone help to explain that. I even have look into source code of that extension but didn't found answer. So finally here.
This item appears if the following conditions are met:
The extension requests "background" permission.
Chrome settings allow "Continue running background apps when Google Chrome is closed".
This menu item is mostly a reminder "what extensions/apps are keeping Chrome runtime running in backround". If no extensions meet the above critera, the Chrome icon doesn't appear at all.
If clicked, it has a fixed behavior that you can't change:
If the extension has an options page defined, it's opened in a new tab, even if it's the new-style options page that should be embedded in chrome://extensions. That last point is certainly a bug.
If the extension has no options page defined, it opens chrome://extensions/ in a new tab.
Related
On Skype, someone sends me website link... I click those and Chrome opens up showing the page.
Is there an event/hook/listener for chrome extension to show that the link was clicked on Skype?
In other words, find out which program made the chrome open from a Chrome extension.
Checked a bit around but couldn't find anything.
Thank you
No. That information isn't recorded anywhere. And it isn't a Chrome extension. It's just one process launching another process.
I want to debug code at the same time as I see what is being sent on the network tab without having to go back and forth between the Network tab and Sources tab. Is there a way to do this as of chrome Version 52.0.2743.82 or Version 54.0.2810.2 canary?
I know that it is possible to log http request in the console which can be visible with other tabs open but I want the actuall networks tab if possible..
Thank you in advance
This is now possible in Chrome 87. Right click Network in the menu and select "Move to bottom"
and it will do this
You can view 'Quick source' while viewing the Network panel (or the other main panels) at the same. This will allow you to view the source and add breakpoints.
However, it's not possible to step through code using the debugging in the split view. Chrome will automatically switch to the Sources tab if you use the shortcuts.
It's also not possible to have an extension running a separate instance of the debugger as the Chrome Debugging Protocol doesn't allow simultaneous clients to be connected.
I will open up a discussion with other Chromium contributors into the feasibility of sharing the debugging controls in the split view. I don't know whether it will or can be done easily. I suspect it's a fair amount of work.
If you would like to set up the split view, as it's useful anyway, go to overflow menu on the right side and select 'More Tools' and then select 'Show console'. This makes sure the panel loads below the main one.
On the left side of the panel that shows, click the overflow menu and select 'Quick source'.
You will now see a small Sources panel.
Since I was referred here from this question, I'll answer here.
In my scenario I need to be able to work on two different source files (under DevTools->Sources) simultaneously, for instance an html and a css file.
My workaround was to work on two separate tabs.
Right click one of them and click 'Open in new tab'.
When the new tab is open press F12 to open DevTools, and dock the two editors side by side (Focus on one and pressing ⊞+→ then leftwards on the other one).
Result:
I have the Chrome Apps and Extensions developer tool installed to debug my Chrome Extension. However, to debug the popup script running in the popup window, you have to perform the following steps:
Refresh the Chrome Extension on the Extensions page
Right click the icon next to the url bar
Select "Inspect Popup"
Set breakpoints
The real annoying part about this is the popup window has to be re-opened every time a change happens. Debugging background scripts I don't have as much of a problem with, because the background script debug page stays open after you refresh the chrome extension. But for popup scripts, the popup window along with the popup debug page keeps closing and it becomes a really tedious, repetitive task to re-open it when debugging a lot. Is there no other way to more easily start debugging Chrome Extensions popup scripts?
As i understood you have a pop up while tapping the icon in the URL bar
In order to debug you can use weinre remote debugger ,Which may solve your problem
apache weinre
When I open Google Chrome's developer tools, I do not get the scripts tab. I have done this on two computers, one running Windows 7 and the other Windows Server 2008 R2. Can you please tell me what I need to do to get the Scripts tab back. Many thanks!
Screenshot of what you are seeing? Scripts are under 'Sources' now
There is no scripts tab in the Chrome debugger any more. You can view the javascript under the Resources tab (though I don't find it all that useful in the Resources tab).
You can view and set breakpoints in your scripts under the Sources tab. Go to the Sources tab now, click on the right facing arrow at upper left (right below Elements) and then find the script you are looking for. Click on it there and it will create a tab with just that script in it. You can then set a breakpoint.
How can I see javascript error when loading chrome extensions? I've tried using developer tools but I don't see any errors there. Also if I use console.log, I don't see any output in the console.
Anyone have any ideas?
http://code.google.com/chrome/extensions/tut_debugging.html
Go to the Extensions page (chrome://extensions), and make sure Developer mode is still enabled. The Extensions page doesn't need to be open for the following to work. The browser remembers the setting, even when the page isn't shown.
Right-click the extension's icon and choose the Inspect popup menu item. The popup appears, and a Developer Tools window like the following should display the code for popup.html.
The above answer doesn't work anymore. Sadly the Inspect Popup menu item has been removed from Chrome.
But this answer works:
Debug popup.html of a Chrome Extension?
(More precisely: the second comment of the first answer on the above page helps).