Closed
Bug 690153
Opened 13 years ago
Closed 13 years ago
Bump DOM Inspector compatibility for SeaMonkey 2.7 / Firefox 10.0 / Thunderbird 10.0
Categories
(Other Applications :: DOM Inspector, defect)
Other Applications
DOM Inspector
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla10
People
(Reporter: iannbugzilla, Assigned: iannbugzilla)
References
Details
Attachments
(1 file)
2.24 KB,
patch
|
iannbugzilla
:
review+
|
Details | Diff | Splinter Review |
With the latest merge the compatibility for SeaMonkey / Firefox / Thunderbird should be bumped.
rs=sdwilsh
Attachment #563237 -
Flags: review+
Comment on attachment 563237 [details] [diff] [review]
Inspector version bump [Checked in: Comment 2]
http://hg.mozilla.org/dom-inspector/rev/75b1039b2015
Attachment #563237 -
Attachment description: Inspector version bump → Inspector version bump [Checked in: Comment 1]
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla10
Comment on attachment 563237 [details] [diff] [review]
Inspector version bump [Checked in: Comment 2]
Backout of wrong patch:
http://hg.mozilla.org/dom-inspector/rev/95e92281f0ef
Checkin of correct patch
http://hg.mozilla.org/dom-inspector/rev/ae1e610e755f
Attachment #563237 -
Attachment description: Inspector version bump [Checked in: Comment 1] → Inspector version bump [Checked in: Comment 2]
Comment 3•13 years ago
|
||
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.7.2/contrib/seamonkey-2.7.2.en-US.linux-x86_64.tar.bz2 (mirrored over ftp.uni-erlangen.de "Friedrich-Alexander Universität Erlangen-Nürnberg")
No .txt file available to tell us build ID and m-c / c-c changesets without launching the build
Looking into ./seamonkey/distribution/extensions/inspector@mozilla.org.xpi::install.rdf
minVersion maxVersion
Firefox 3.0a1 11.0a1
Thunderbird 3.0a1pre 11.0a1
SeaMonkey 2.0a1pre 2.8a1
Obviously at least one further version upgrade has been applied but without undoing the fix for this bug. VERIFIED.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•