mdn / sprints

Archived: MDN Web Docs issues are tracked in the content repository.
https://github.com/mdn/content
Creative Commons Zero v1.0 Universal
150 stars 142 forks source link

Firefox 63 WebExt DDNs #372

Closed chrisdavidmills closed 6 years ago

chrisdavidmills commented 6 years ago

User story

As an extensions developer, I want to learn about the new WebExtension/Browser Extension features in Firefox 63, so I can use them in my own projects.

Acceptance criteria

    • [x] All DDNs complete.
    • [ ] Reviews request from engineers for all documentation work.

Tasks

Items for Irene

  1. (Moved to a separate Issue, #503) Implement theme experiments [2 points]

(smaller items, total 3.5 points)

Items for Will

(smaller items, total 3.5 points)

irenesmith commented 6 years ago

New tab colors was much simpler than it appeared. I only had to update browser compatibility since the properties are already defined as a result of Chrome support for them.

Example added as well.

irenesmith commented 6 years ago

Asked about this one: #1470516 as I'm not sure that it needs anything but a release notes comment because none of the existing documentation says anything about localized strings.

irenesmith commented 6 years ago

Remaining DDNs:

1347207 should be done today. 1418602 asked what changes there are to document here. It isn't clear from reading the bug whether theme creators have to define something in particular to have this work. 1280370 should be done this afternoon. 1396684 This one may not be done until tomorrow (Friday) morning. 1369209 Another one that may not be done until tomorrow (Friday) morning.

irenesmith commented 6 years ago

1369209 - Some of the information in the bug description implies that the management.install method only applies to lightweight themes. It doesn't seem to make sense to document it if LWT is going away.

irenesmith commented 6 years ago

1347207 - Removing this one from the issue as it is more extensive than a DDN. I will discuss the subject of experimental themes with the team and determine how ready it is for release, then come up with a plan to document it fully.