Closed
Bug 1486520
Opened 7 years ago
Closed 6 years ago
[Translate.Next] Add support for Fluent
Categories
(Webtools Graveyard :: Pontoon, enhancement, P2)
Webtools Graveyard
Pontoon
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1554705
People
(Reporter: adrian, Unassigned)
References
Details
This is a meta-bug that will be, in time, replaced by a myriad of smaller bugs about implementing Fluent support to the new Translate App.
|
Reporter | |
Updated•7 years ago
|
Priority: P3 → P1
|
|
Reporter | |
Comment 1•7 years ago
|
||
Notes from our October work week:
- we want to use Translate.Next as an opportunity to test various features and changes around the Fluent editor. First one of those would be to ship only an advanced text editor (like Ace or CodeMirror) for all Fluent content, and no rich editor.
- that means we can "ship" Translate.Next earlier, without blocking on the Fluent rich editor implementation (making this bug a P4). By "ship" I mean show it to real users in the production website, with the current UI as a backup in case something goes wrong (or they don't like our tests).
- that also implies that we get more metrics about usage of Translate.Next (and the current UI) so that we can drive decisions based on data.
Priority: P1 → P4
|
|
Reporter | |
Updated•7 years ago
|
Priority: P4 → P2
|
|
Reporter | |
Updated•7 years ago
|
Assignee: adrian → nobody
|
||
Comment 2•6 years ago
|
||
Closing on behalf of bug 1554705.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
|
||
Updated•4 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•