Open
Bug 634573
Opened 14 years ago
Updated 11 months ago
Print warning in error console when file described in chrome.manifest is not found
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
UNCONFIRMED
People
(Reporter: borisov.gleb, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.102 Safari/534.13
Build Identifier: 4.0b9pre (build from head on 2011-02-14)
For example:
interfaces component/someIface.xpt
I've typed component instead of components and have a lot of fun with debugging it :)
It would be great if we would warn on this cases for: interfaces, component, overlay, manifest, binary-component directives
Reproducible: Always
Steps to Reproduce:
Write chrome.manifest with files does not exists (eg. interfaces directive)
Actual Results:
Nothing happens. Interface is not registered, no warning or error in console.
Expected Results:
Error or warning appears in error console. Interface still not registered.
Reporter | ||
Comment 1•14 years ago
|
||
I think (I'm not experienced Mozilla developer, just diving in) that it's possible to print message to error console from nsComponentManagerImpl.
For example: nsComponentManagerImpl::ManifestXPT (interfaces directive processor) use NS_WARNING to produce error if stream is not available. In this point we could put warning in error console.
Updated•2 years ago
|
Severity: minor → S4
In Chrome extensions, you can use the chrome.manifest file to specify the resources and components your extension uses. To print a warning in the error console when a file https://therummyapk.com/junglee-rummy-apk-free-download/ described in the chrome.manifest is not found, you can follow these steps:
You need to log in
before you can comment on or make changes to this bug.
Description
•