Closed Bug 515108 Opened 17 years ago Closed 17 years ago

Error "Metadata.xul cannot be found" when extensions want to access the removed properties dialog on trunk [e.g. imagebar]

Categories

(Firefox :: Extension Compatibility, defect)

defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: danialhorton, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [caused by extension])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.3a1pre) Gecko/20090907 Minefield/3.7a1pre GTB5 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.3a1pre) Gecko/20090907 Minefield/3.7a1pre GTB5 (.NET CLR 3.5.30729) Firefox can't find the file at jar:file:///C:/Program Files/Mozilla/Minefield/chrome/browser.jar!/content/browser/metaData.xul. Reproducible: Always Steps to Reproduce: 1. Right click a page, image or link Actual Results: Properties menu item does not appear in the list. Expected Results: Properties menu item should appear in the list. Extensions such as imagebar displays a info button which brings up the image properties, this is where the i noticed the following error message Firefox can't find the file at jar:file:///C:/Program Files/Mozilla/Minefield/chrome/browser.jar!/content/browser/metaData.xul.
The properties dialog has been removed by bug 513147. The add-on authors have to update their extensions.
Blocks: 513147
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Component: Menus → Extension Compatibility
Keywords: regression
OS: Windows XP → All
QA Contact: menus → extension.compatibility
Hardware: x86 → All
Resolution: --- → INVALID
Summary: Metadata.xul missing from Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.3a1pre) Gecko/20090907 Minefield/3.7a1pre GTB5 (.NET CLR 3.5.30729) ID:20090907051047 → Error "Metadata.xul cannot be found" when extensions want to access the removed properties dialog on trunk [e.g. imagebar]
Version: unspecified → Trunk
Status: RESOLVED → VERIFIED
Whiteboard: [caused by extension]
You need to log in before you can comment on or make changes to this bug.