Setting chrome://*/* in the content script "matches" section of the manifest results in the error:
Invalid value for "content_scripts[0].matches[0]". Is there another channel by which I can inject code on chrome:// pages? This is the use case: the extension I'm developing provides tab and page navigation keyboard shortcuts, and its content script runs on all webpages. However, it does not run on chrome:// pages because of the above restriction. If you are using my extension to switch tabs via the keyboard, once you switch to Chrome's New Tab page, your shortcuts will cease to work. According to this bug, it seems like content scripts may have been allowed to execute on chrome:// pages at one point in time: http://code.google.com/p/chromium/issues/detail?id=12410 If anyone has more details behind the rationale for restricting access to chrome:// pages, that would be very informative. If this is not possible today, I'd be happy to file an improvement ticket for it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
