Yes, this is a known issue. I've created a bug that you can track if you're interested:
http://code.google.com/p/chromium/issues/detail?id=11547 - a On Wed, May 6, 2009 at 11:37 AM, jack <js2...@gmail.com> wrote: > > The phenomenon is quite simple: the addon code may not be loaded > (quite random) for the first loaded page (i.e., your homepage when you > first launch Chrome). > > I don't know how to attach a file, but here are the steps to duplicate > it: > > 1. Just follow any standard way to create a new extension: > > http://dev.chromium.org/developers/design-documents/extensions/howto > > 2. Use the following code: > > -------------------------------------------------------------------------------------------------- > Manifest.json: > > { > "format_version": 1, > "id": "08C0AD5C3A6811DEB0A1DEB556D8959301234567", > "version": "1.0", > "name": "Test", > "description": "Test", > "content_scripts": [ > { > "matches": ["http://*/*", "https://*/*"], > "js": ["test.js"] > } > ] > } > > > test.js: > > document.title = "test title"; > document.addEventListener("click", function(){alert('Here I > come...');}, false); > > ------------------------------------------- > > > As you can see, it is quite simple: it changes the page title, and > alert every time you click your mouse. But when you launch your > chrome, it is not loaded in the specified homepage (e.g., www.google.com). > Only after you navigate out from the page and go to the second page > (e.g., news.google.com) will the addon take effect. > > > Any ideas about this? Or did I do sth. wrong? > > Thanks. > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---