If you make the image path relative to the CSS file you should be fine. On Dec 29, 2009, at 10:34 , Harold Chan wrote:
> thanks all > > sounds that hard code is still the best solution for my problem > > On Dec 29, 6:21 am, Brian Kennish <bkenn...@chromium.org> wrote: >> On Sun, Dec 27, 2009 at 6:01 PM, Harold Chan <cmkgr...@gmail.com> wrote: >>> If I specify image paths in CSS files that is included by content >>> script, how to specify the file path that point to the chrome >>> extention? >> >>> I have tried hardcoding it like chrome-extension://<ID>/path, but it >>> seems that it is not a good solution as it may change in some cases. >> >> Hey Harold, if you're publishing this extension in the gallery, you >> shouldn't have to worry about the ID changing. After you do your >> initial upload, the ID will remain fixed. >> >> Otherwise, if you're still in development mode and expect the ID to >> change, then you can set the relevant CSS property with JavaScript >> (e.g., using your element's "style" object and, of course, >> "chrome.extension.getURL"). > > -- > > You received this message because you are subscribed to the Google Groups > "Chromium-extensions" group. > To post to this group, send email to chromium-extensi...@googlegroups.com. > To unsubscribe from this group, send email to > chromium-extensions+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > > -- Mark Wubben http://supercollider.dk -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
