Re: Next Year in web-platform-tests - 2018/19 Edition

2018-12-12 Thread Nils Ohlmeier
> On 7Dec, 2018, at 07:45, James Graham wrote: > > I would also very much like to hear about remaining pain points and reasons > that developers choose to write browser-specific tests for web-platform > features. Those are issues we need to prioritize fixing. Without going too much into the

Re: Next year in web-platform-tests

2017-12-16 Thread Ben Kelly
I know you aware, but just mentioning for the list: We need WPT coverage on Android to fully rely on it as our primary test suite. Particularly while Android's config deviates so far from desktop. On Dec 15, 2017 10:40 AM, "James Graham" wrote: > Following the summary

Re: Next year in web-platform-tests

2017-12-15 Thread Emilio Cobos Álvarez
On 12/16/2017 04:57 AM, L. David Baron wrote: > On Friday 2017-12-15 16:00 -0600, Andrew McCreight wrote: >> For me, a blocker to only having WPT is leak checking, both in terms of >> XPCOM leak checking and LeakSanitizer. (The latter is probably going to >> automatically work if you run them in

Re: Next year in web-platform-tests

2017-12-15 Thread L. David Baron
On Friday 2017-12-15 16:00 -0600, Andrew McCreight wrote: > For me, a blocker to only having WPT is leak checking, both in terms of > XPCOM leak checking and LeakSanitizer. (The latter is probably going to > automatically work if you run them in ASan, but it would be good to check.) > I know

Re: Next year in web-platform-tests

2017-12-15 Thread Kartikaya Gupta
On Fri, Dec 15, 2017 at 4:59 PM, Andreas Tolfsen wrote: > I would be interested to hear more about what primitives for user > input emulation are required. Touch input emulation would also be good. There are some CSS properties like touch-action which require emulating user touch

Re: Next year in web-platform-tests

2017-12-15 Thread Andrew McCreight
On Fri, Dec 15, 2017 at 9:38 AM, James Graham wrote: > Following the summary of what we achieved in wpt in the last year, I'd > like to solicit input from the gecko community to inform the > priorities of various pieces of wpt work for the next year. > > In order to

Re: Next year in web-platform-tests

2017-12-15 Thread Andreas Tolfsen
Also sprach smaug: > On 12/15/2017 05:38 PM, James Graham wrote: >> In particular it would help to hear about things that you would >> consider blockers to removing tests from non-wpt suites that are >> duplicated in wpt (assuming exact duplication), and limitations >> either in the capabilities

Re: Next year in web-platform-tests

2017-12-15 Thread David Burns
On 15 December 2017 at 21:29, smaug wrote: > > Not being able to send (DOM) events which mimic user input prevents > converting > many event handling tests to wpt. > Not sure if WebDriver could easily do some of this, or should browsers > have some testing mode which exposes >

Re: Next year in web-platform-tests

2017-12-15 Thread smaug
Great work on wpt! On 12/15/2017 05:38 PM, James Graham wrote: Following the summary of what we achieved in wpt in the last year, I'd like to solicit input from the gecko community to inform the priorities of various pieces of wpt work for the next year. In order to maximise the compatibility