Re: Next year in web-platform-tests

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

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: Intent to implement: individaul transform

(cc'ing the dev-developer-tools list, please keep responses to dev-platform) Very happy to see this being implemented. I would like to point out that this does have some DevTools impact that we might want to align with the target release for this. There's a (sort of hidden) feature in DevTools

Re: Intent to implement: individaul transform

On 12/15/2017 08:51 AM, Ku(顧思捷)CJ wrote: > Summary: > The translate, rotate, and scale properties allow authors to specify > simple transforms independently, in a way that maps to typical user > interface usage, rather than having to remember the order in transform that > keeps the actions of

Next year in web-platform-tests

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 benefit we have two long term objectives for the

Re: Intent to implement: individaul transform

There have been a series of attacks[0] that allow SOP bypasses by applying non-constant-time transforms to cross-domain resources and using timing attacks to infer the contents. I'm not sure to what extent we have been tracking our exposure to these attacks over the years, but it's something I'm

This year in web-platform-tests

I thought that people might be interested in a retrospective on the progress with web-platform-tests in the last year. 2017 has seen big advance in the adoption of web-platform-tests by the wider browser community, and has brought considerable improvements to the associated tooling and

Re: Next year in web-platform-tests

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

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

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: Intent to implement: individaul transform

Behind a preference(about:flags - enable individual transforms) On Sat, Dec 16, 2017 at 12:10 AM, Emilio Cobos Álvarez wrote: > > > On 12/15/2017 08:51 AM, Ku(顧思捷)CJ wrote: > > Summary: > > The translate, rotate, and scale properties allow authors to specify > > simple

Re: Next year in web-platform-tests

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

Re: Next year in web-platform-tests

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