Re: [webkit-dev] What to do about scroll anchoring?

And, to be clear, we _can_ fix these compat issues, some way or another. One thought is to limit the amount of scroll adjustments without user scrolling or stuff like that, which would prevent the "you get stuck on the page". Making anchoring opt-in rather than opt-out is another option, but

[webkit-dev] WinCairo EWS

The WinCairo EWS bot has been in pretty sad shape for a while, providing no useful information and lots of false negatives. Could someone please fix it or remove it? See https://ews-build.webkit.org/#/builders/12/builds/5501 for an

Re: [webkit-dev] WinCairo EWS

It provides every bit as much useful information as any other EWS bot when it’s not running into that specific issue (`patch` failure). :) Intermittent or not, it does seem like this is happening with shocking frequency lately. I have no idea what causes it, but I hope we can quickly find a

Re: [webkit-dev] WinCairo EWS

Do you think adding a build step before svn-apply which deletes “ C:\Users\ContainerAdministrator\AppData\Local\Temp” would help? Thanks Aakash > On Sep 27, 2019, at 1:34 PM, ross.kirsl...@sony.com wrote: > >  > It provides every bit as much useful information as any other EWS bot when >

Re: [webkit-dev] Planned EWS improvements

Thank You everyone (who responded) for the feedback. I will prioritize the features some of you mentioned, especially adding a way to retry the patch. Thanks Aakash > On Sep 27, 2019, at 9:27 AM, Konstantin Tokarev wrote: > > > > 27.09.2019, 08:15, "Simon Fraser" : >>> On Sep 27, 2019, at

[webkit-dev] What to do about scroll anchoring?

Hi, (cc'ing webkit-dev@ and blink-dev@ in case they have feedback or opinions, as WebKit is the only engine which does not implement scroll anchoring, though I don't know if they plan to, and Blink is the only other engine that does implement it. Please reply to dev-platform@ though.) TLDR:

[webkit-dev] ios-wk2 EWS in a bad state because of flaky tests

Hi All, Last week we updated the iOS bots from iOS 12 to iOS 13. Since then we have been noticing a lot of flaky tests. Because of that ios-wk2 queue has been in a bad state. Most of the time, it is unable to determine if the test failures were introduced by the patch or were pre-existing, and