Re: [dev-servo] Servo testing as part of PhD dissertation

> In addition to feeling less novel, QuickChecking JS > APIs doesn't feel quite as useful for Servo testing (based on the > assumption that Servo will be re-using *Monkey). Most of the JS APIs are part of the DOM and not the built in objects. These are implemented in the browser itself, not in

[dev-servo] Upgrading HTTP requests to WebSocket with rust-websockets.

I am currently writing a prototype of a debugger server for Servo that works with the Chrome Debugging Protocol: https://github.com/ejpbruel/servo/tree/acceptor The Chrome Debugging Protocol works by first sending a HTTP request to http://localhost:/json (where is the remote debugging port).

Re: [dev-servo] Servo testing as part of PhD dissertation

Thanks for all the feedback. I've collected the responses and replied inline. > Jack Moffitt wrote: > A sort of subtask of this which would be extremely useful is taking > a known rendering problem and producing a minimal reproduction of > it. For example, many issues are discovered in existing