Closed Bug 730691 Opened 9 years ago Closed 9 years ago

Bump Venkman compatibility for SeaMonkey 2.10 / Firefox 13.0 / Thunderbird 13.0

Categories

(Other Applications Graveyard :: Venkman JS Debugger, defect)

defect
Not set
normal

Tracking

(seamonkey2.9 verified, seamonkey2.10 verified)

VERIFIED FIXED
mozilla13
Tracking Status
seamonkey2.9 --- verified
seamonkey2.10 --- verified

People

(Reporter: InvisibleSmiley, Assigned: InvisibleSmiley)

References

Details

Attachments

(1 file)

+++ This bug was initially created as a clone of Bug #702155 +++

Unfortunately we missed bumping the last two times.

The compatibility for SeaMonkey should be changed to 2.10.* and for Firefox and Thunderbird to 13.0.*. This is needed in order to allow users to disable compatible-by-default, and to stop a Toolkit test to succeed which checks the compatibility of all bundled add-ons (only an issue with SeaMonkey, obviously).
Attachment #600783 - Flags: review?(gijskruitbosch+bugs)
Target Milestone: --- → mozilla13
I am less and less sure these kinds of blanket bumpings are the right thing to do. How well does Venkman actually still work on trunk? Are people there still relying on it?
(In reply to Gijs Kruitbosch from comment #1)
> I am less and less sure these kinds of blanket bumpings are the right thing
> to do.

Not the bump is blanket, the rs is (or should be, IMHO, to help get updates like this one done ASAP). IOW, if Venkman doesn't work with trunk, we're not going to bump maxVersions.

> How well does Venkman actually still work on trunk?

AFAIK, there are minor issues (e.g. bug 459996), but otherwise I think it's fine.

This statement is only really true for Venkman trunk, though; AMO needs to be updated. Cf. bug 418426 comment 43.

> Are people there still relying on it?

Well, I wouldn't know what else to use for debugging chrome. Chromebug is pretty much dead. For debugging web content, Firebug is the better choice (works with both FF and SM, too).
Comment on attachment 600783 [details] [diff] [review]
patch [Checkin: Comment 4]

That pretty much confirms what I thought, although I'd call it more than mild breakage... in any case, thank you for laying it out. Ideally, someone fixes Vnk to use JSD2 when it is done, and/or creates a new chrome debugger... at this point, not yet sure which would be easier, and it's outside the scope of this bug.

rs=me for now, thanks for the work on this one!
Attachment #600783 - Flags: review?(gijskruitbosch+bugs) → review+
Comment on attachment 600783 [details] [diff] [review]
patch [Checkin: Comment 4]

http://hg.mozilla.org/venkman/rev/65ad515ebba6
Attachment #600783 - Attachment description: patch → patch [Checkin: Comment 4]
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1330654046.1330660646.11577.gz
Linux comm-central-trunk debug test mochitest-other on 2012/03/01 18:07:26
{
TEST-PASS | chrome://mochitests/content/browser/suite/browser/test/browser_bug728651.js | JavaScript Debugger 0.9.88.2 should be compatible
}

V.Fixed
Status: RESOLVED → VERIFIED
Depends on: SM2.7
No longer blocks: 732749
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.