Revision as of 17:10, 16 December 2020

About

DevTools support for cross-site iframes with Fission is in progress and this page summarizes the current state.

The DevTools team is listening in in the #devtools:mozilla.org room on Mozilla's Matrix server.

Instructions for enabling Fission for DevTools:

In about:config, set the "fission.autostart"
Restart the browser

You can file DevTools Fission related bug in Bugzilla, here.

See detailed testing results (gdoc)

Fission Compatibility

Known issues are split into two milestones (M2 and M3).

M2 Q4 2020
M3 Q1 2021

Panels

Summary of known issues related to DevTools panels.

Accessibility

The Accessibility panel should be fully compatible with Fission.

Application

M3 Service Workers coming from remote frames are not displayed (bug 1473257).

Performance

M3 New Fission compatible Performance panel will be enabled (by default) at the end of October (bug 1668218).

Inspector

M3 Advanced features related to highlighting elements in the page. This includes support for highlighting grid elements, shapes defined using CSS clip-path property, highlighting fonts, geometry editor for absolute positioned elements within relative positioned elements and inspecting CSS animations (bug 1568827)
M3 Search within the Inspector panel doesn't included remote iframes (bug 1568880)
M3 Eydropper (a button in the Inspector's panel toolbar ) used to grab a color from the page (bug 1568831)

Console

The Console panel should be fully compatible with Fission.

Network

M3 Proper support for JS Context Switching (bug 1594726, bug 1594728)

Debugger

M3 Debugging of service workers should work as expected
M3 Special breakpoints set for: DOM mutation, XHR, various DOM events, Logpoints and Watchpoints should work as expected.
M3 When there are several frames from various origins, sources will be missing for some of the origins in the source pane (bug 1659969)
M3 Search across all processes (bug 1577878)
M3 Debugger doesn't work properly if page loads two remote iframes from the same domain (bug 1503499, bug 1678741)

Style Editor

The Style Editor panel should be fully compatible with Fission

Storage

M3 Show all data coming from remote frames: Cookies, Session & Local storage, Extension storage, IndexDB and Cache data (bug 1644192)

Memory

M3 Memory usage of remote frames is not displayed.

DOM

M3 Objects coming from remote frames are not displayed.

Miscellaneous Features

Summary of known issues related to independent features.

Screenshot

M3 Screenshot doesn't work with remote frames (bug 1568833)

Service Workers

M3 Support for Service Workers is not not compatible with Fission.

@@ Line 50: / Line 50: @@
 * <span style="background-color: #ff9900; color: white;>M3</span> Debugging of service workers should work as expected
 * <span style="background-color: #ff9900; color: white;>M3</span> Special breakpoints set for: DOM mutation, XHR, various DOM events, Logpoints and Watchpoints should work as expected.
+* <span style="background-color: #ff9900; color: white;>M3</span> When there are several frames from various origins, sources will be missing for some of the origins in the source pane ([https://bugzilla.mozilla.org/show_bug.cgi?id=1659969 bug 1659969])
+* <span style="background-color: #ff9900; color: white;>M3</span> Search across all processes ([https://bugzilla.mozilla.org/show_bug.cgi?id=1577878 bug 1577878])
+* <span style="background-color: #ff9900; color: white;>M3</span> Debugger doesn't work properly if page loads two remote iframes from the same domain ([https://bugzilla.mozilla.org/show_bug.cgi?id=1503499 bug 1503499], [https://bugzilla.mozilla.org/show_bug.cgi?id=1678741 bug 1678741])
 === Style Editor ===

DevTools/Fission: Difference between revisions