Closed
Bug 305046
Opened 19 years ago
Closed 19 years ago
DOM Inspector and Reporter are not compatible with Deer Park 1.0+
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: tracy, Unassigned)
Details
(Keywords: regression)
Seen on Windows DP 2005-08-17-12-mozilla1.8 -Perform a custom install and ensure DOM Inspector and Website Reporter are checked for installation. -Launch DP, go to Tools | Extensions Tested results: DOM Inspector and Reporter are greyed out and red labels as: Disabled - not compatible with Deer Park 1.0+ DOM Inspector and Reporter are not listed their expected menu slots Expected results: DOM Inspector and Reporter enabled and available for use from their menu slots. just a guess, but Windows build was quite late today. Perhaps the checkin for bug 304476 at 10:17 08/17 is to blame?
Reporter | ||
Updated•19 years ago
|
Flags: blocking1.8b4?
Summary: DOM Inspector and Reporter are not compatible → DOM Inspector and Reporter are not compatible with Deer Park 1.0+
Comment 1•19 years ago
|
||
I wasn't able to reproduce with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050817 Firefox/1.0+ ID:2005081721
Comment 2•19 years ago
|
||
I can confirm problems with Inspector, Reporter AND Talkback. I use Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20050817 Firefox/1.6a1 and all three extensions show in the EM the following message: "... will be installed when Deer Park is restarted". But nothing happens if Deer Park is restarted. Alle three extensions are not usable.
Comment 3•19 years ago
|
||
On *trunk* this is 304874. On *branch* this may be related to https://bugzilla.mozilla.org/show_bug.cgi?id=304476#c5
Comment 4•19 years ago
|
||
With a debug trunk build both the Thunderbird and Firefox targetApplication minVersion and maxVersion were set correctly. With a tbox trunk build the Thunderbird targetApplication minVersion and maxVersion were empty for Reporter and DOMi. There is no error handling for this so it killed the EM and since it did it during an install restarting does not fix it. We could add additional error handling all over the EM code for invalid values but I would expect there to be at least a slight perf impact and these types of errors should only be seen by extension developers.
Reporter | ||
Comment 5•19 years ago
|
||
DOM Inspector and Website Reporter are enabled and working with builds from 0818. In particular Windows 2005-08-18-08-mozilla1.8 Marking WFM :
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Updated•19 years ago
|
Flags: blocking1.8b4?
Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•