Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/b64d0a8c04db08eaa81502868a5802d660030842 (Keyboard-accessible scroll containers (with tabIndex = 0)).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

ClusterFuzz has detected this issue as fixed in range 610212:610219.

Detailed report: https://clusterfuzz.com/testcase?key=6249431298736128

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  blink::IntRect::UniteEvenIfEmpty
  blink::Element::BoundsInViewport
  blink::WebElement::BoundsInViewport
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=608008:608015
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=610212:610219

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6249431298736128

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6249431298736128 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Not fixed, only hid. KeyboardFocusableScrollers got disabled yesterday.

We will re-enable it for M73.

This overflow was already found and closed as WontFix in  Issue 890480 .