In trying to debug a content script, I found that a content script in another extension was erroring out, causing my content script to not fire. With a lot of extensions using http://* for their content scripts, I can imagine this sort of thing happening regularly
Are there anything I can do to keep this from happening? Anything on the extension roadmap to keep this from happening? -- 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.
