Closed Bug 404294 Opened 12 years ago Closed 12 years ago

Remove some stray chrome://communicator/skin/s

Categories

(MailNews Core :: Composition, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: philor, Assigned: philor)

References

Details

Attachments

(1 file)

Attached patch Fix v.1Splinter Review
No sense in making Thunderbird grovel around to load chrome://global/skin/ through an @import for these, when that's all anything, including SeaMonkey, actually needs.
Attachment #289266 - Flags: superreview?(neil)
Attachment #289266 - Flags: review?(neil)
Comment on attachment 289266 [details] [diff] [review]
Fix v.1

>Index: mailnews/compose/resources/content/MsgAttachPage.xul
Thunderbird doesn't use this - it's a copy of openLocation.xul that I made so that we could autocomplete from history. (Originally I wanted to reuse openLocation.xul but it was too tied in to editor and tabbed browser.)

> <window class="dialog" id="customHeaders"
Eww, this hasn't been changed to a <dialog> yet?
Might as well file a separate bug and fix both at the same time.

>Index: mailnews/import/resources/content/fieldMapImport.xul
Suite currently needs this for the up and down arrows...
Attachment #289266 - Flags: superreview?(neil)
Attachment #289266 - Flags: review?(neil)
Attachment #289266 - Flags: review-
But... but... if I file a separate bug to fix the one file that I wasn't stupidly fixing something non-broken in, then that means this one is invalid!
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Well if you're that concerned about your bugzilla karma then we can fix the CSS in the custom headers window here and convert it to a dialog separately ;-)
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.