[perma] comm/mail/components/extensions/test/browser/browser_ext_compose_begin.js | plainText content is correct - Got "\n", expected ""
Categories
(Thunderbird :: Add-Ons: Extensions API, defect, P5)
Tracking
(thunderbird_esr78 unaffected)
| Tracking | Status | |
|---|---|---|
| thunderbird_esr78 | --- | unaffected |
People
(Reporter: intermittent-bug-filer, Assigned: masayuki)
References
(Regression)
Details
(Keywords: intermittent-failure)
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Filed by: mkmelin [at] iki.fi
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=341401452&repo=comm-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/YinoVyLqQAKy-RNZjEejmg/runs/0/artifacts/public/logs/live_backing.log
|
||
Comment 1•4 years ago
|
||
This is from https://hg.mozilla.org/mozilla-central/rev/9d28dcb2d4d46cc2c400ffdc61d8d4b2cbd4a99b - bug 1540037
So editor.outputToString("text/plain", Ci.nsIDocumentEncoder.OutputRaw) of an initial editor (in paragraph mode) is now "\n" instead of empty. Unclear to me if it's expected or not?
|
Assignee | |
Comment 2•4 years ago
|
||
It's obviously a regression of it. I'll take a look.
|
|
Assignee | |
Comment 3•4 years ago
|
||
It stopped using ComputeValueFromTextNodeAndBRElement for HTMLEditor case.
However, ComputeValueFromTextNodeAndBRElement handles the case that there is
only padding <br> element for empty editor even if the instance is
HTMLEditor.
So, this patch makes it handle this special case by itself before checking
whether the instance is TextEditor.
|
||
Comment 5•4 years ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
Description
•