Bug 190197 – REGRESSION(r236719): this revision caused 39 layout test failures that tested for scrolling, a bug was also not present in the commit or change log. (Requested by Truitt on #webkit).

• Component: New Bugs
• Status: RESOLVED FIXED

[WebKit Commit Bot]

https://trac.webkit.org/changeset/236719 broke the build:
this revision caused 39 layout test failures that tested for scrolling, a bug was also not present in the commit or change log. (Requested by Truitt on #webkit).

This is an automatic bug report generated by webkitbot. If this bug
report was created because of a flaky test, please file a bug for the flaky
test (if we don't already have one on file) and dup this bug against that bug
so that we can track how often these flaky tests fail.

[WebKit Commit Bot]

Created attachment 351383 [details]
ROLLOUT of r236719

Any committer can land this patch automatically by marking it commit-queue+.  The commit-queue will build and test the patch before landing to ensure that the rollout will be successful.  This process takes approximately 15 minutes.

If you would like to land the rollout faster, you can use the following command:

  webkit-patch land-attachment ATTACHMENT_ID

where ATTACHMENT_ID is the ID of this attachment.

[WebKit Commit Bot]

Comment on attachment 351383 [details]
ROLLOUT of r236719

Clearing flags on attachment: 351383

Committed r236741: <https://trac.webkit.org/changeset/236741>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

[Radar WebKit Bug Importer]

<rdar://problem/44937228>

[Michael Catanzaro]

Ah, I see the problem: frameView.addScrollableArea and frameView.removeScrollableArea have side effects. Thanks for the speedy rollout.

Note that we don't require bugs for trivial build fixes (in this case, -Wunused-variable).

[Alexey Proskuryakov]

Correct, we don’t require a bug for every commit. Mentioning that in a rollback bug seems useful anyway:

1. Maybe there was a bug, just not mentioned in ChangeLog. Not knowing about it means that the person who rolled back the change could not reopen the original. 

2. It makes it more clear that some context could have been lost (maybe there was an IRC discussion that not everyone saw).

[Michael Catanzaro]

Fixed properly in bug #190200