All users were logged out of Bugzilla on October 13th, 2018

Simplify venkman-overlay for Thunderbird

RESOLVED FIXED in mozilla10

Status

RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: iann_bugzilla, Assigned: iann_bugzilla)

Tracking

Trunk
mozilla10

SeaMonkey Tracking Flags

(seamonkey2.7 fixed)

Details

(Whiteboard: [qa?])

Attachments

(1 attachment)

(Assignee)

Description

7 years ago
Created attachment 563379 [details] [diff] [review]
Split venkman-overlay [Checked in: Comment 2]

At the moment there is a single venkman-overlay.xul but due to duplication of IDs, have to remove the TB menuitem using javascript.
This patch:
* Moves the TB part of the overlay to a separate file.
* Only overlays TB with the new file.
* Stops overlaying TB with the old file.
* Drops the javascript removal of the TB menuitem.
Attachment #563379 - Flags: review?(gijskruitbosch+bugs)

Comment 1

7 years ago
Comment on attachment 563379 [details] [diff] [review]
Split venkman-overlay [Checked in: Comment 2]

r=me
Attachment #563379 - Flags: review?(gijskruitbosch+bugs) → review+
(Assignee)

Comment 2

7 years ago
Comment on attachment 563379 [details] [diff] [review]
Split venkman-overlay [Checked in: Comment 2]

http://hg.mozilla.org/venkman/rev/7fce081822d4
Attachment #563379 - Attachment description: Split venkman-overlay → Split venkman-overlay [Checked in: Comment 2]
(Assignee)

Updated

7 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
status-firefox10: --- → fixed
status-seamonkey2.7: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla10
Is this something that can be verified in Firefox 10 or is it Thunderbird-only?
Whiteboard: [qa?]
(Assignee)

Comment 4

7 years ago
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #3)
> Is this something that can be verified in Firefox 10 or is it
> Thunderbird-only?

There should be no visible difference, so hard to verify. I've removed the status-firefox10 flag as apparently I shouldn't have set that.
status-firefox10: fixed → ---
You need to log in before you can comment on or make changes to this bug.