Well, obviously, it is a bug, but - as a workaround, you can search for
"text_color" in your files.

But, could it be in the manifest.json?

☆PhistucK


On Fri, Dec 11, 2009 at 12:25, hassenbentanf...@gmail.com <
hassenbentanf...@gmail.com> wrote:

> Hi,
>  When debugging a script or when an error occurs, a few elements are
> missing
>
> 1) The error message (stack) is cut.
> "TypeError: Cannot read property 'text_color' of undefined at optVal
> (chrome-extension://dfpiadka…"
> *I don't see where I can read the details.*
>
> 2) It does not mention which script and MOST IMPORTANTLY which line
> (for extensions). It seems to work fine for regular files.
>
> Example:
> TypeError
> arguments: Array
> message: "Cannot read property 'text_color' of undefined"
> stack: "TypeError: Cannot read property 'text_color' of undefined at
> optVal (chrome-extension://dfpiadka…"
> type: "non_object_property_load"
>
>
> 3) The need to constantly reload the extension is quite annoying. Is
> there a way for chrome to just read my latest changes while I'm
> developing the extension.
>
> Thanks for your help.
>
> --
>
> 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.


Reply via email to