Closed Bug 378620 Opened 14 years ago Closed 9 years ago
Figure out tooltip whitespace stripping behavior for Firefox 3
I know some people (Steuard being one of them) have strong opinions about what we should be doing with regard to whitespace stripping. This bug will hopefully be a good place to discuss pros/cons of each approach and ultimately decide whether we want to keep the block of code at http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/browser/base/content/browser.js&rev=1.778&mark=2690-2696#2690, without resorting to baseless advocacy. Here is the list of pros/cons that I know of for our current behavior (strip out whitespace): Pros: - In accordance with HTML spec (not sure how relevant this really is) - Better behavior in some cases where markup includes unintentional whitespace - No change in behavior if we ever fix bug 322270 (other than for whitespace entities) Cons: - Doesn't match behavior of either SeaMonkey or IE - Doesn't gives authors a way to explicitly add line breaks (at least not until bug 322270 is fixed) I might be forgetting something here, but I think those are the salient points. Thoughts?
The discussion in bug 358452 is probably also relevant.
Summary: Figure out whitespace stripping behavior for for Firefox 3 → Figure out tooltip whitespace stripping behavior for for Firefox 3
Summary: Figure out tooltip whitespace stripping behavior for for Firefox 3 → Figure out tooltip whitespace stripping behavior for Firefox 3
Will bug 322270 be fixed for 1.9? If so, maybe we don't need to have this confusing discussion.
I don't think it will be fixed for Firefox 3, which is why I filed this bug. I'm not sure that it's ever going to be "fixed", since it might lead to incompatibilities with the web. You're right that if it is, our decision here would be simpler :)
Not blocking on this, though if we can come up with a good answer we should do this.
Flags: blocking-firefox3? → blocking-firefox3-
As discussed in bug 322270 over a year ago, HTML5 seems to have made this issue moot. It seems clear that this bug should be closed, but I'm not entirely sure what the resolution should be. (WONTFIX? FIXED? WORKSFORME?) Hopefully someone more knowledgeable than I am will decide; otherwise the next time I think of it I'll take my best guess and close it myself.
We fixed bug 358452 in Firefox 12. This bug isn't useful anymore!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.