I'll be meeting with various WPT stakeholders at the Web Engines
Hackfest next week. Do we have any thoughts or concerns about the future
of WPT as a platform to drive Servo's web compatibility and testing web
features across all browsers? Are there any web platform features that
are still hard to test that we should be talking about? Are there any
concerns about the quality of tests, or feature sets that Servo does not
support that we should discuss rewriting in existing tests?
On my list right now:
* PRs can merge upstream that fail the lint without being detected; this
breaks our nightly syncing
(https://github.com/servo/servo/pull/21814#issuecomment-424737163 and
https://github.com/web-platform-tests/wpt/issues/13222).
* Unnecessary use of the named window getter in tests, which Servo does
not support and is more complex than it sounds
* Reduce code patterns in tests that lead to TIMEOUT rather than ERROR
when a feature is unsupported
Please let me know if there is anything I'm missing!
Cheers,
Josh
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo