Open Bug 991048 Opened 11 years ago Updated 3 years ago

Let the composer always render in no-quirks mode. Ignore the DOCTYPE. Implement Gaia behavior.

Categories

(Thunderbird :: Message Compose Window, defect)

24 Branch
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: xn--mlform-iua, Unassigned)

References

(Blocks 1 open bug)

Details

Bug #335499 proposes to always render e-mail in no-quirks mode - in contrast to today, where Thunderbird always renders in quirks mode, regardless of DOCTYPE. A proposed fix for Bug #335499 is add the html DOCTYPE <!DOCTYPE html>. Gaia already implement this behavior. (Gaia renders in no-quirks even if DOCTYPE is lacking.) My assumption is that Gaia simply ignores the DOCTYPE, falling back to non-quirks. (By contrast, Thunderbird today ignores the DOCTYPE but falls back to quirks.) The Gaia behavior is in tune with e.g. Gmail, which always renders messages in no-quirks. Email, being a kind of "temporary" or short lived medium, is a context where we do no give much weight to the fact that always rendering e-mail in no-quirks mode would cause some old, "legacy messages" to not render as intended. Besides, we *are* already in a situation where some messages will render in quirks in some readers, while in standards in other readers. Today’s composer behavior is an obstacle to fixing Bug #335499, since, as of today, if the composer renders in no-quirks, the message display would render in quirks. Therefore both needs to be fixed in tandem. The best fix would be to simply make the email medium be one where omission of (conforming) DOCTYPE does *not* trigger quirks-mode and let this rule also affect the composer.
Blocks: 335499
Blocks: 991053
Filed bug against HTML5 require no-quirks mode for HTML mail regardless of DOCTYPE: https://www.w3.org/Bugs/Public/show_bug.cgi?id=25234
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.