| Main Process (pid 89180) | |
| Explicit Allocations | |
| 1.05 MB (100.0%) -- explicit | |
| ├──0.98 MB (93.50%) -- images | |
| │ ├──0.84 MB (80.26%) -- chrome/vector/used/progress=18f | |
| │ │ ├──0.06 MB (05.55%) -- image(5x7, chrome://devtools/skin/images/breadcrumbs-divider.svg) | |
| │ │ │ ├──0.05 MB (05.15%) ── source | |
| │ │ │ └──0.00 MB (00.41%) ++ locked/types=2000/surface(5x7) | |
| │ │ ├──0.05 MB (05.00%) -- image(16x16, chrome://devtools/skin/images/close-3-pane.svg) |
| { | |
| "devtools_tests": [ | |
| { | |
| "test": "devtools/client/memory/test/xpcshell/test_individuals_05.js", | |
| "averageRuntime": 174.97391418277104, | |
| "runs": 3193 | |
| }, | |
| { | |
| "test": "devtools/client/debugger/test/mochitest/browser_dbg-sourcemapped-scopes.js", | |
| "averageRuntime": 174.76304804804806, |
./mach wpt-update /Users/jdescottes/Development/wpt-update/
After downloading the relevant wpt-report.json files from try. Always try to take a variety of platforms (eg 1 linux 1 android, or more generally one which fails for specific conditions and a successful one).
| Bug 1687954 - Pause on JS exceptions doesn't work properly in Fission (8) | |
| Bug 1687963 - Debugger should properly break on debugger; keyword in remote frame (8) | |
| Bug 1665020 - DevTools Toolbox broken when navigating cross origin (20) | |
| Bug 1568880 - Make the inspector's search field work with remote targets (8) | |
| Bug 1681698 - Bootstrap thread actor as soon as we start registering breakpoints via the Watcher actor (20) | |
| Total: 64 points | |
| Why did I prioritize this way: | |
| I did not include the storage bugs, because this is already broken today, and not Fission related. | |
| Also did not include most of the server-side resource support. Unless there is a huge feature broken with fission because of that I don't think it will have any user impact. |
| const { RootMessageHandlerRegistry } = ChromeUtils.import( | |
| "chrome://remote/content/shared/messagehandler/RootMessageHandlerRegistry.jsm" | |
| ); | |
| const { RootMessageHandler } = ChromeUtils.import( | |
| "chrome://remote/content/shared/messagehandler/RootMessageHandler.jsm" | |
| ); | |
| const { WindowGlobalMessageHandler } = ChromeUtils.import( | |
| "chrome://remote/content/shared/messagehandler/WindowGlobalMessageHandler.jsm" | |
| ); |
| const moduleLayout = { | |
| root: { | |
| windowglobal: {}, | |
| contentprocess: { | |
| worker: {}, | |
| }, | |
| }, | |
| }; |
| function getPageNumber() { | |
| const previous = document.querySelector("[aria-label='Previous']"); | |
| return previous.closest("[aria-label*='Page']").getAttribute("aria-label").replace("Page ", "") * 1; | |
| } | |
| (async () => { | |
| while (getPageNumber() > 1) { | |
| document.querySelectorAll("[data-testid*='summary'].form-check-input").forEach(e => e.click()) | |
| await new Promise(r => setTimeout(r, 3000)); | |
| document.querySelectorAll('.btn-secondary [data-icon="check"]').forEach(e => e.parentNode.click()) |
People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
Two suggestions below to slightly rephrase some paragraphs in the code example:
-> "This was already helpful to perform some setup logic, or to expose functions that could be called from script.evaluate or script.callFunction commands later on. However there was no way to properly handle dynamic situations, like monitoring DOM mutations and notify the client about the details."