Confirmed users, Bureaucrats and Sysops emeriti
1,217
edits
Electrolysis/Short-Term Goals: Difference between revisions
new goals
(new goals) |
|||
| Line 1: | Line 1: | ||
= Current Goals = | |||
== Get Firefox Starting Up == | == Get Firefox Starting Up == | ||
| Line 7: | Line 9: | ||
Status: patches posted, see [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipe his status report] | Status: patches posted, see [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipe his status report] | ||
== Dynamic | == Deploy Dynamic Analysis to mozilla-central == | ||
Followup to the initial dynamic analaysis goal: clean up the patch that is written, write some simple testcases to ensure correct behavior, and land the analysis to mozilla-central debug builds (off by default). | |||
Owner: Drew Willcoxon | |||
Goal date: 14-July | |||
== Make basic Firefox navigation use the Message Manager == | |||
In order to make the dynamic analysis useful for estimating Firefox frontend work, we need basic page navigation to not produce any warnings. This means that current uses of web progress listeners in the Firefox frontend should be ported to the message manager. | |||
Owner: Felipe Gomes | |||
Goal date: 21-July | |||
== Connect the chrome/content accessibility tree on Windows == | |||
Implement the basic a11y plan on Windows with a hidden HWND and a connected cross-process a11y tree. | |||
Owner: | Owner: Alexander Surkov | ||
Goal date: | Goal date: 21-July | ||
== Static Analysis of Chrome/Content Interaction == | == Static Analysis of Chrome/Content Interaction == | ||
| Line 40: | Line 41: | ||
Goal date: 23-June | Goal date: 23-June | ||
Status: incomplete, in trouble | |||
=== Subgoal 2: Analyze and produce reports on one bad pattern === | === Subgoal 2: Analyze and produce reports on one bad pattern === | ||
Goal date: 7-July | Goal date: 7-July | ||
== Extension Usage Metrics == | == Extension Usage Metrics == | ||
| Line 57: | Line 52: | ||
Owner: blizzard?/jorge? | Owner: blizzard?/jorge? | ||
Goal Date: 7-July | Goal Date: 7-July | ||
| Line 79: | Line 67: | ||
Owner: Ted Mielczarek | Owner: Ted Mielczarek | ||
Goal Date: TBD | Goal Date: TBD | ||
= Completed Goals = | |||
== Dynamic Instrumentation for Chrome/Content Interaction == | |||
We want to identify: | |||
* non message-manager scripts | |||
* which touch a "content object" | |||
* or implement nsIWebProgressListener | |||
Definitions: | |||
Non message-manager script is any chrome script that isn't run through nsIChromeFrameMessageManager.loadFrameScript. | |||
Content objects are at least the following: | |||
* Any DOM object (window, document, or node) | |||
* Docshell or docshell derivative | |||
* nsIWebProgress | |||
* nsIDOMWindowUtils | |||
Owner: Drew Willcoxon | |||
Goal date: 30-June | |||
Status: DONE (patch and initial analysis complete) | |||
== Identify Work Items for Multiple Content Processes == | |||
We have identified multiple content processes as a requirement for desktop Firefox. Identify and find owners for the work required for multiple content processes. | |||
Owner: Benjamin Smedberg | |||
Goal Date: 23-June | |||
Status: DONE (feature bugs filed... memory analysis will be later) | |||
== Accessibility Engineering Plan == | |||
Identify whether the accessibility tree will need to be mirrored, or whether accessibility tools can work directly with trees in content processes. | |||
Owner: David Bolter | |||
Goal Date: 7-July | |||
Status: DONE (posted to mozilla.dev.planning) | |||