New issue
Advanced search Search tips

Issue 578155 link

Starred by 12 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Mac: Zero-Width-Space (ZWSP) chars are erroneously inserted into text editor of Outlook Web App

Reported by luke.ham...@gmail.com, Jan 15 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36

Steps to reproduce the problem:
1. Log in to Outlook Web App using Chrome

2. Compose new mail.

3. Click into the Message Body area.

4. Type the word "foo" and hit Enter

5. Now press <CMD-A> (select all) and hit <DEL> to delete all content.

6. Type "bar"

7. Now right click and inspect the "bar" element.  You will see that there is a Zero Width Space (&#8203;) right after the first <p> element. This will remain there and get transposed to a '?' character when the plaintext version of the email is sent out.

Versions tested:

Chrome (Mac) 47.0.2526.111 (64-bit)
Firefox (Mac) 43.0.4
IE 11.0.10240.16603 (Windows 10)

Server side Microsoft Exchange / Outlook Web App (OWA)
Exchange 2013 v15.0.1130.7 (CU10)
Exchange 2016 v15.1.225.42

What is the expected behavior?
There should be no extra &#8203; character inserted at the beginning of the MicrosoftOWAEditorRegion div.  This can be seen in the inspector.

What went wrong?
A ZWSP Zero Width Space is inserted at the front of the "MicrosoftOWAEditorRegion" div. This causes plaintext emails to be sent with a leading '?' character which looks like it was a careless typo.

Did this work before? No 

Chrome version: 47.0.2526.111  Channel: stable
OS Version: OS X 10.11.2
Flash Version: Shockwave Flash 20.0 r0

Have also tested Chrome Canary v49 - same problem.

Have done the same test with Firefox 43, Internet Explorer 11 and they do not exhibit this bug, they work as expected.

I am attaching a ZIP with 3 screenshots inside showing the inspector from Chrome/Firefox/IE and that Chrome was the only browser where the ZWSP was added.

It seems that a bug was filed on this 2 years ago but never fixed.
https://code.google.com/p/chromium/issues/detail?id=350352

Also see here for a thread on Microsoft's forum about this issue
https://social.technet.microsoft.com/Forums/exchange/en-US/585e8701-8282-41eb-b66f-618f41c74a50/owa-message-mangling-in-chrome
 
Chrome-ZWSP-issue.zip
570 KB Download
 Issue 350352  has been merged into this issue.
Labels: -Cr-Blink Cr-Blink-Editing OS-Windows
Status: Untriaged
If it helps, we can provide login credentials to a "live" OWA server to make it easier for testing/repro.

Comment 4 by yosin@chromium.org, Jan 21 2016

Labels: Needs-Feedback
Status: Unconfirmed
Summary: NEED_FREE_BACK: Zero-Width-Space (ZWSP) chars are erroneously inserted into text editor of Outlook Web App (was: Zero-Width-Space (ZWSP) chars are erroneously inserted into text editor of Outlook Web App)
I search chromium code repostory for "200B" and "8023", but editing code doesn't use them. It seems Outlook Web App dose something special for Chrome.

How about Safari on Mac?
Just tested Safari for Mac v9.0.2 (11601.3.9) and it does not exhibit this problem.
So far I am only seeing it on Chrome.
Updated to
Chrome Mac v48.0.2564.82 (64-bit)
Outlook Web App from Exchange 2013 CU11 [15.0 Build 1156.6]

Bug with ZWSP still exists

Comment 7 by yosin@chromium.org, Feb 19 2016

Status: Available (was: Unconfirmed)
Summary: Mac: Zero-Width-Space (ZWSP) chars are erroneously inserted into text editor of Outlook Web App (was: NEED_FREE_BACK: Zero-Width-Space (ZWSP) chars are erroneously inserted into text editor of Outlook Web App)
Project Member

Comment 8 by sheriffbot@chromium.org, Feb 20 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue.
The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 9 by yosin@chromium.org, Feb 21 2017

Status: Available (was: Untriaged)

Comment 10 by cseg...@gmail.com, Jun 26 2017

The issue still exists on the latest Chrome version, under windows. 
Labels: Pri-3
Project Member

Comment 12 by sheriffbot@chromium.org, Oct 5

Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)
I can confirm that this issue is still exists on Chrome version 69.0.3497.100 (Official Build) (64-bit). 
Maybe has some connection with the canned responses or the automatic signature. I mostly face this problem when I delete or modify my signature included automatically. I only use Chrome on Windows. 

As a workaround, I have created a Chrome extension using InboxSDK to remove U200b characters from the body of the message. 
E.g.:

        // Subscribe to the presending event of the compose view
        composeView.on('presending', function (event) {
            var origHtml = composeView.getHTMLContent();
            var modifiedHtml = origHtml.replace(/\u200B/g, '');
            composeView.setBodyHTML(modifiedHtml);

        });


FYI, if anybody is interested, here is my git repo for the extension:
https://github.com/csegyud/Hudgi-s-Gmail-Fixer-Chrome-Extension

Sign in to add a comment