Closed
Bug 1055291
Opened 12 years ago
Closed 12 years ago
[B2G][Email] HTML code is parsed in Email subject line
Categories
(Firefox OS Graveyard :: Gaia::E-Mail, defect)
Tracking
(b2g-v2.0 affected, b2g-v2.1 affected)
RESOLVED
INVALID
People
(Reporter: bzumwalt, Unassigned)
Details
(Whiteboard: [2.1-flame-test-run-1])
Attachments
(2 files)
Description:
If user receives email with HTML code in the subject line, the HTML code is parsed into a string that is visible in both message list view and email view. For subject line to be parsed, user may have to manually sync.
Strings tried include:
<meta http-equiv="refresh" content="0;http://cnn.com";>, <iframe src="http://www.google.com"/>, and <button> This button should not be created </button>
Repro Steps:
1) Update a Flame device to BuildID: 20140818040201
2) Launch email app
3) Set up new email account (Hotmail or Gmail)
4) From a different device/account send new email to device with the subject line set to "
<meta http-equiv="refresh" content="0;http://cnn.com";>"
5) Manually sync email account on device
Actual:
HTML code is parsed as string in email subject line.
Expected:
HTML code is not parsed in email subject line.
Environmental Variables:
Device: Flame 2.1 Master (319mb)
BuildID: 20140818040201
Gaia: aa8aace12d65956dd9525da5dac66e0d3b28597f
Gecko: 0aaa2d3d15cc
Version: 34.0a1 (2.1 Master)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Notes:
Repro frequency: 3/3, 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/4370/
See attached: screenshot & logcat
| Reporter | ||
Comment 1•12 years ago
|
||
| Reporter | ||
Comment 2•12 years ago
|
||
Issue DOES occur on Flame 2.1 (512mb), Buri 2.1, Flame 2.0 (319mb), Buri 2.0
Environmental Variables:
Device: Flame 2.1 Master (512mb)
BuildID: 20140818040201
Gaia: aa8aace12d65956dd9525da5dac66e0d3b28597f
Gecko: 0aaa2d3d15cc
Version: 34.0a1 (2.1 Master)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Device: Buri 2.1 Master
BuildID: 20140818073016
Gaia: ba1992f2addc5a84afc2eab426f222a6bf2962ba
Gecko: bf27e27c994d
Version: 34.0a1 (2.1 Master)
Firmware: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Device: Flame 2.0 (319mb)
BuildID: 20140818000201
Gaia: fb2dd31abed2803eb7ad67eb4c52abb48de1e0f7
Gecko: 09f7a7184c71
Version: 32.0 (2.0)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Device: Buri 2.0
Build ID: 20140818063008
Gaia: 640ce38ca03f1e26a4524ff4215b8b3f7731e2f0
Gecko: 692c93509dc9
Version: 32.0 (2.0)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Actual result: HTML code is parsed as string in email subject line.
Comment 3•12 years ago
|
||
I think this moztrap case is a bit confused. Subjects are always text/plain. Anything you type in them will be displayed verbatim. If you type something that looks like HTML, the recipient will see something that looks like HTML. (Unless there is a serious/dangerous bug in the client and they assign the value to innerHTML. Or unless the email client has decided to proactively sanitize the weird probably-html stuff.)
We already have extensive automated back-end tests related to the HTML sanitizer and snippet generation and quite strict hygiene about use of innerHTML, so I don't think anyone is benefitting from the existence of this moztrap case.
Let's please delete/removeinvalidate the moztrap case; whatever it takes! :)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Comment 4•12 years ago
|
||
Disabled test case based upon comment 3.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → in-moztrap-
You need to log in
before you can comment on or make changes to this bug.
Description
•