Closed
Bug 1348151
Opened 7 years ago
Closed 6 years ago
Community testing for new LWT
Categories
(WebExtensions :: Themes, enhancement, P5)
WebExtensions
Themes
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: amyt, Unassigned)
References
Details
(Whiteboard: triaged)
One acceptance criterion for QA team is community testing to ensure LWT authors transition successfully to new themes. Amy, Caitlin, and Krupa to come up with the plan.
|
Reporter | |
Updated•7 years ago
|
Blocks: themingapi
|
|
Reporter | |
Updated•7 years ago
|
No longer blocks: themingapi
|
|
Reporter | |
Comment 1•7 years ago
|
||
Need to see flow from UX before we can design the tests. Caitlin to find out when to expect them.
|
|
Reporter | |
Updated•7 years ago
|
No longer blocks: themingapi
|
||
Updated•7 years ago
|
Priority: -- → P5
|
||
Updated•6 years ago
|
Component: WebExtensions: Frontend → WebExtensions: Themes
|
||
Comment 2•6 years ago
|
||
I don't think this is still relevant, LWT and WE themes are rendered using the same underlying system. And any conversion from LWT to new themes will be done on AMO's side.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
|
||
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•