Beginning on October 25th, 2016, Persona will no longer be an option for authentication on BMO. For more details see Persona Deprecated.
Last Comment Bug 707108 - text within <!--[if !mso]> <![endif]--> tags not displayed
: text within <!--[if !mso]> <![endif]--> tags not displayed
Status: RESOLVED INVALID
:
Product: Core
Classification: Components
Component: HTML: Parser (show other bugs)
: 8 Branch
: x86_64 Windows 7
: -- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
: Andrew Overholt [:overholt]
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-12-02 02:24 PST by Andrea Janna
Modified: 2012-07-16 04:41 PDT (History)
4 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
message.html (3.09 KB, text/plain)
2011-12-02 02:24 PST, Andrea Janna
no flags Details

Description Andrea Janna 2011-12-02 02:24:51 PST
Created attachment 578526 [details]
message.html

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111104165243

Steps to reproduce:

I'm receiving emails using Thunderbird 8.0.



Actual results:

Sometimes when I receive answers to emails I sent, I can see only quoted "original message" but I cannot see actual reply that sender wrote. The same message is correctly displayed by Outlook 2003.
If I save the message as HTML from Thunderbird and open the file in Firefox 8.0 there is the same issue: I can see only quoted "original message" but I cannot see actual reply that sender wrote. If I open the same file in Internet Explorer version 8 or 9 I can see the full message, like using Outlook.
Please find attached "message.html", which is an edited version of the original message and which triggers the issue in Thunderbird / Firefox.

This issue is triggered by <!--[if !mso]> tag that Outlook and Outlook Express programs sometimes add when replying to my emails. Please note that this tag is added only sometimes: I can get from the same sender, which uses always the same Outlook version, some emails without this tag and other emails with it.

I got this issue from senders which use Outlook (X-Mailer: Microsoft Office Outlook 11, X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157) and also from senders which use Outlook Express (X-Mailer: Microsoft Outlook Express 6.00.2900.5931, X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157).
All senders are from far east countries like Corea, China and Taiwan.



Expected results:

Thunderbird should display the full message like Outlook does.
Comment 1 Henri Sivonen (:hsivonen) (not reading bugmail or doing reviews until 2016-10-27) 2011-12-02 05:32:50 PST
According to the HTML specification <!--[if !mso]>foo<![endif]--> is a single HTML comment (whose value is "[if !mso]>foo<![endif]"). Comment nodes aren't displayed. Thus, Thunderbird is behaving spec-wise correctly for text/html messages.

My first reaction was to WONTFIX this, but I realize there might be a need to interop with the Microsoft products that do a bad, bad thing.

However, before adding non-standard behaviors to the HTML parser, I'd like to understand how often the problem occurs, whether we can get Microsoft to fix it at their end and whether the outgoing HTML Thunderbird sends can be tweaked so that this behavior isn't triggered in Outlook or Outlook Express when replying.
Comment 2 Henri Sivonen (:hsivonen) (not reading bugmail or doing reviews until 2016-10-27) 2011-12-02 05:35:28 PST
How do non-Outlook, non-Thunderbird email clients that support text/html message bodies (e.g. Apple's and Opera's email clients, Gmail, etc.) behave when receiving messages like these?
Comment 3 drhowarddrfine 2011-12-02 05:52:44 PST
Adding non-standard behavior in a Mozilla product to fix a Microsoft bug really rubs me raw.
Comment 4 j.j. 2011-12-02 08:47:24 PST
And this isn't a regression from the old parser
Comment 5 j.j. 2012-07-16 01:21:02 PDT
This bug is just invalid.

Note You need to log in before you can comment on or make changes to this bug.