I'm looking at Bug 28174 as one which I and my employer intend to fix. The catch is no one's said exactly how to do so.
As I see it, there are several things we need to do for this bug:
Of these, I know I can do #3. #1 requires C code, and I'll try to partner with one of my coworkers on this. We'll probably need some help, at least in determining where the code goes in the source tree under xpinstall. #4 is a matter of debate, and your comments here would be useful. #2 is something we will need help on; I don't think anyone here knows how to do that. It might be as simple as a XPCOM service from C, but I don't know.
My concern for the moment is just to get the checkboxes part of comment 23 working. We'll deal with other issues later.
I'll update this blog entry based on your comments. So please offer useful feedback, particularly technical details.
UPDATE: Guys, having opinions on the way you want it to appear is all well and good. But I need technical expertise on how to make it work. Any takers?
This bug has had a high level of interest for me for quite some time. Unfortunately, it has stagnated for an equally long time...
The idea is simple: we should somehow keep a reference to the original document (not letting the XSLT transformation obliterate it) and all the descendant nodes.
I really don't know where to begin looking for ways to fix this one. Getting the original document without XSLT transformations applied would be a boon for web developers.
This bug is an evil Firefox 1.0 blocker. I can't figure out what's going on in the source code (nsDownloadManager.cpp, possibly nsExternalAppHandlerService.cpp) well enough to start working on a patch.
helpwanted: I don't know yet if this is a Windows-only bug or if it affects other platforms. I also don't know where in the code this is taking a turn for the worse. I need help determining these issues, so that a patch can be developed.
In this case, the bug is blocking me from releasing another nice little feature for this blog.
Please don't comment to this blog entry about whatever you discover. File your comments in the bug.
The "Featured Bug for Research" column is a new one for this blog, basically asking people to help me out on bugs that interest me and are not necessarily trivial to figure out. I'll use it primarily for issues where I'm just stuck.
UPDATE: Well, this blog entry got some attention. Within a few hours of me noting it here, a number of developers leaped on it, pointed out the basic flaw in the code, created a patch (porting another patch that already applied to Mozilla trunk), r+sr'd, and checked it in. We're waiting on the patch to finish baking on tbox and grab a nightly to test. Prospects are good.
UPDATE 2: Penalty flag on the kicker, offsides. We're still showing this bug as of a nightly grabbed from Tinderbox, internal timestamp 2004092506.
FINAL UPDATE: Ladies and gentlemen, this bug has been fixed. I apologize for retracting the entry, but due to its security-sensitive status, I felt I had to retract it momentarily.