[meta] DevTools HTML experiment fails to load in Servo

[jryans]

The DevTools team has been working on an experimental HTML version of the Firefox DevTools UI in the joewalker/devtools.html repo. This is not something we plan to use anywhere directly, it's just an experiment to learn from for future deXULification. In any event, we thought it would be good to see how far Servo is from being able to load it. @bgrins has been working in the servo-client branch to tweak things as necessary to get something loading in Servo.

If you wish to try the experiment locally, I would suggest using Firefox as the DevTools server, and only testing the client UI in Servo to focus on this issue only. The repo's README.md explains how to get started and start a server in Firefox. So, the only modification from the README instructions would be to open the actual UI at http://localhost:8081/client/framework/toolbox-wrapper.html in Servo instead.

We'll use this issue to track the various individual issues as we find them:

P1

• contentWindow null in frames Ensure that grandchild same-origin iframes are added to the children … #8978
• Range.getBoundingClientRect is not defined inside CodeMirror frames [devtools.html] Range.getBoundingClientRect support #8982

P2

• window.focus is undefined window.focus/blur support #8981

@bgrins @jdm @Ms2ger @larsbergstrom

[jdm]

This particular iframe problem is fixed by #8978, allowing us to progress to the next set of errors :)

[bgrins]

Cool! The next set of errors I'm seeing:

• this._markupFrame.contentWindow.focus is not a function
• getBoundingClientRect not defined inside of codemirror
• 'let' is used in codemirror/addon/search/search.js (I've just pushed a fix for that in the servo-client branch)

[bgrins]

Should we expect contentWindow.focus() to work on an iframe? I can comment that bit out if it's not yet implemented

[jdm]

We don't implement Window.focus() yet.

[paulrouget]

@bgrins @jryans I recommend you to file one issue per bug. You can probably use this bug as a meta bug. See how we do for browser.html: browserhtml/browserhtml#562

[jryans]

Okay, I've created a task list in this issue to use for tracking. Each new problem should be filed separately as it comes up, and we can use the task list to track overall progress.

[paulrouget]

For the record, i think opening the devtools should be implemented at the runtime level: #7379 (comment)

See Electron's code:

• https://github.com/atom/electron/blob/afa8f8b1664b1ff49e68254ba7c1fae1b728bf0a/atom/browser/api/atom_api_web_contents.h#L79
• https://github.com/atom/electron/blob/02e0c169a22e4f94bda88581d1ece73e498499e0/docs/api/web-contents.md#webcontentsopendevtoolsoptions

[highfive]

cc @fitzgen