1612329 - (add-plaintext-editor-tests) [meta] Create tests for editor usage in Thunderbird, particularly for "plaintext mail"

Status: NEW

(MailNews Core :: Composition, task)

Description

[Jorg K (CEST = GMT+2)]

Further reading in bug 1393140 comment #44 and above.

These tests need to go into M-C so it breaks there first ;-)

Masayuki-san has a spreadsheet that shows test coverage for the editor API (or lack thereof).

Comment 1

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Currently, we have API tests under editor/libeditor/tests as test_<interface_name>_<member_name>.html. They assume existing behavior does not have any bugs. I.e., created for keeping traditional behavior. So, when you add new API test, please use this format. And also, if some behavior in the existing tests are not suitable for Thunderbird requirements, file bugs for each thing and cc me. I'll take a look when I have spare time.

Comment 2

[Wayne Mery (:wsmwk)]

Masayuki-san has a spreadsheet that shows test coverage for the editor API (or lack thereof).

Do you still have the spreadsheet?

Comment 3

[Wayne Mery (:wsmwk)]

Magnus, do we have a strategic direction for editor that correlates to this issue?

bug 1393140 comment 43 is certainly interesting.

Comment 4

[Magnus Melin [:mkmelin]]

Apart from adjusting code when it's been needed, we have worked on using less non-standard functions for editing (bug 1655014 and it's predecessors). That way Thunderbird can also serve as a good test case for editing on the web.

I think the doc is here: https://docs.google.com/spreadsheets/d/19hj6utJC08rRlkGkqOj5hLY5Gi6jRACdXqOQVJPzk8o/edit#gid=0

Comment 5

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Yes, that is, but it does not include the spellchecker APIs.