Harold, I don't quite understand why you would need to do that. You can
simply use relative urls without any problem. Can you explain a test case
where this is happening?
-Mohamed Mansour
On Wed, Dec 30, 2009 at 7:04 AM, Harold Chan <cmkgr...@gmail.com> wrote:
> the purpose of this is to prevent hardcoding the extension ID which is
> different in unpacked and packed mode
>
> On Dec 30, 7:55 pm, Harold Chan <cmkgr...@gmail.com> wrote:
> > finally, I have come up with a solution.
> >
> > What I did is that
> > 1. not to include the CSS files in manifest.json
> > 2. in a js file that is included in content script, do the following
> > things:
> >
> > add var htmlElement = document.createElement("link");
> > add attrubutes rel="stylesheets", type="text/css",
> > href=chrome.extension.getURL("RELATIVE CSS FILE PATH") in htmlElement
> > add htmlElement to the head of the document
> >
> > by doing this, relative path can be used in the CSS files.
>
> --
>
> 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<chromium-extensions%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/chromium-extensions?hl=en.
>
>
>
--
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.
