Closed Bug 239394 Opened 21 years ago Closed 20 years ago

nsIMIMEInfo should use interCaps for functions and attributes

Categories

(Core Graveyard :: File Handling, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla1.8alpha1

People

(Reporter: Biesinger, Assigned: Biesinger)

References

()

Details

Attachments

(1 file)

nsIMIMEInfo should use interCaps like all other interfaces.
Attached patch patch (deleted) — Splinter Review
Comment on attachment 147986 [details] [diff] [review] patch bz, this should be a simple review... but if you don't have time or if if you don't want to do reviews or something, I can ask darin for r+sr instead
Attachment #147986 - Flags: superreview?(darin)
Attachment #147986 - Flags: review?(bzbarsky)
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.8alpha
Comment on attachment 147986 [details] [diff] [review] patch r=bzbarsky, assuming you didn't miss any callers. ;) I love how we have 3 identical copies of everything...
Attachment #147986 - Flags: review?(bzbarsky) → review+
(In reply to comment #3) > (From update of attachment 147986 [details] [diff] [review]) > r=bzbarsky, assuming you didn't miss any callers. ;) I do hope I got all of them :) I really hate how JS makes it impossible to do this kind of checking at compiletime...
Comment on attachment 147986 [details] [diff] [review] patch sr=darin I wonder how many third-party extensions this is going to break :-(
Attachment #147986 - Flags: superreview?(darin) → superreview+
well, we'll need to break them anyway on the road to libxul (by which point we should have this frozen, imo).
Agreed. This interface is definitely something we should try to freeze for libxul if not for 1.8 =)
before freezing this, we should decide something about the other dependencies of bug 162116; especially the one about non-ascii extensions. it may be sufficient to use AUTF8String for the extension attributes here... (interface-wise) I'll send an announcement of this change to newsgroups and mozillazine forums... hopefully that'll suffice we should have some process to announce such changes, methinks...
checked in.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
looks like the browser/ part needs relanding
Keywords: aviary-landing
the toolkit/ part too, for that matter
biesi: send mail to ben goodger?? or are you going to take care of re-landing it?
darin: my impression was that someone would go through the bugs with the aviary-landing keyword and check those in again...
ok, makes sense.
Relanding relevant parts of patch following aviary branch landing One difference: - var desc = mimeInfo.Description; + var desc = mimeInfo.description; instead of - aFilePicker.appendFilter(mimeInfo.Description, extString); + aFilePicker.appendFilter(mimeInfo.description, extString);
Keywords: aviary-landing
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: