It might be useful to have an "os integration" component, or a set of components ("os integration: windows", ...) for things like registering file types, registering url schemes (bug 70264), adding a tray icon for new mail, etc. Right now those bugs are scattered throughout various components.
blake, law, sairuh, would this be useful? as part of the XPApps cleanup maybe (bug 68621)?
i've filed bug 77237 as a request to have a File Handling component. sounds like this one would overlap with 77237. what preference do folx have? if people favor the description in this one, i'd actually change the name "OS Integration" to something else, as it sounds a bit too vague to me.
Asa: Did anything happen here? I'm trying to track down some OS integration bugs, but I can't find any sure way of listing all of them, since we seem to have no appropriate component.
ian, no, nothing happened here. anyone on the cc: care to comment? do you want this? will one of you own it? I'm sure that some set of bugs in XP apps could comfortably fit in this bucket. So do we need one for Browser and one for MailNews too? sspitzer, putterman, do you think this would be useful for MaiNews?
If it would make it easier for other people to look for things than I'm not against having a Mailnews version of this, though I don't think it's necessary because I don't think we have too many bugs on this right now for mail. Right now they probably are all under Mail Window Frontend.
I'd like a set of components, one for each major platform (win/mac/unix). I'll own the windows one (but I don't want the other platforms).
was just chatting with Asa over irc about this... what do people think of just making this part of the "file handling" component i've proposed in bug 77237? i admit, i don't have a strong idea as to how many bugs have already been filed re: OS integration, so i'm not sure how much "unecessary" bug-bloat this would cause in a file handling component. if people would rather have os integration as a separate component[s]: i'm not sure i should be the default qa contact for all three components [win32, unix, mac]. lisa & other qa ppl, any ideas who'd be able to cover those test areas [or, who's already testing them]? i might be able to cover unix and mac, but prolly not win32...
Some of the bugs that would land under "os integration" would fit under "file handling," but not all. For example, somebody is going to ask that choosing "Configure..." when right-clicking on Mozilla in the WinXP Start Menu open Mozilla's pref window, rather than IE's Internet Options. That's not going to be a "file handling" bug.
There's no clear request here. For a new component I need a name, a description which explains by example what bugs are appropriate, a volunteer to own the component, and a volunteer to QA the component. WONTFIX. Please reopen if you can provide the above. Thanks.
fwiw, Chimera: OS Integration email@example.com firstname.lastname@example.org For issues with integrating Chimera with Mac OS X. For example: Services. How about, Description: For issues integrating with the OS. Including associating files and protocols with Mozilla and setting Mozilla as the default application. proposed Owner: Law, QA: Sairuh At some point (perhaps now), I'd imagine the Owner and QA would diverge.
law, se: do you want this?
i think i need to pass on this one, sorry. as it stands now, for win32 and mac os integration issues, we have two QA on those --email@example.com for win32 and firstname.lastname@example.org for mac os. (linux is up in the air, alas.) i'm not sure who'd be the "default" developers for those --bill has done win32 in the past, but i don't know who'd be the one nowadays for mac os or linux...
Ok, so what I'm hearing is that there isn't really a big demand for this. Please do not hesitate to file a new bug if this changes.
I'm going to mark this "verified" as "won't fix" at this time.