32
edits
Project Fission/DocShell Tree Replace: Difference between revisions
Jump to navigation
Jump to search
Project Fission/DocShell Tree Replace (view source)
Revision as of 19:34, 20 November 2019
, 20 November 2019Added summary of categories.
(Added link to overall bug tree view.) |
(Added summary of categories.) |
||
| Line 33: | Line 33: | ||
== Usages of nsIDocShellTreeItem == | == Usages of nsIDocShellTreeItem == | ||
The uses of nsIDocShellTreeItem are broadly categorized by the kind of use. The categories are: | |||
1. simple - uses which can be fixed by porting the tree traversal directly to the BrowsingContext tree instead of the DocShell tree. | |||
2. sync-state - uses which require moving some existing state within a process-internal structure (e.g. Document, DocShell, Window, etc.) and moving it into a cross-process replicated structure like BrowsingContext, TabContext, or WindowContext. | |||
3. hard - uses that will require some form of IPC or architectural change to fix | |||
4. rename - helper functions which need to be re-named to reflect their in-process-only semantics, and their uses audited. | |||
5. validate - existing uses which are likely consistent with Fission requirements, but must be verified and closed. These may involve some small cosmetic changes to code. | |||
[https://bugzilla.mozilla.org/showdependencytree.cgi?id=1467214&hide_resolved=1|Tree Overview of All Relevant Bugs] | [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1467214&hide_resolved=1|Tree Overview of All Relevant Bugs] | ||