Thanks PhistucK,
Adding "debugger;" totally worked. The console launches and you have
access to the isolated world the content script runs in. Once all
"debugger" breakpoints are passed over, the console returns
automatically to the webpage's world, and the content scripts world is
no longer accessible.
Either way, that vastly simplifies the content script debugging.
Thanks!
-Adam
On Feb 17, 9:46 am, PhistucK <
phist...@gmail.com> wrote:
> Not really, as far as I try...
> You can add a "debugger;" to your code, which will become a breakpoint that
> will be triggered (if reached) and use the Scripts panel to debug.
> It may give you more information and let you debug within the world of the
> content script, I am not sure.
>
> Example -
>
> var a = "";
> a++;
> debugger; // This will create a breakpoint.
> function bla()
> {
> return;}
>
> a = bla();
>
> ☆*PhistucK*
>
>
>
>
>
>
>
> On Thu, Feb 17, 2011 at 16:33, Adam <
ldsfutbolpla...@gmail.com> wrote:
> > Is this possible? I have found no way to actually interact with a
> > content Script, other than reloading the extension and either passing
> > messages to it from background.html or bubbling events to it from the
> > page.
>
> > Is there anyway to interact with the variables and functions in a
> > content script from the console?
>
> > --
> > 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...@chromium.org.
> > To unsubscribe from this group, send email to
> >
chromium-extensions+unsubscr...@chromium.org.