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/+/52d55d36c78e4772e0e3499409dc6f6dcabde00e (Make InsertText command not to split SPAN element containing TAB character).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Lower to Pri-3 since it is caused by unusual HTML, e.g. nth-last-of-type with display: inline-flexbox

Testcase 4517094841647104 is a top crash on ClusterFuzz for windows platform. Please prioritize fixing this crash.

Marking this crash as a Beta release blocker.

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

Per C#4 this seems to be caused by unusual HTML but as per CF this is top crash on ClusterFuzz for windows platform.

yosin@: Could you please review the blocker label added in C#5 and remove if this should not be blocking at all.

Cc'ing yosin@ for review of the blocker label.

Remove RB label per #c4, since this bug doesn't affect real world usage.

ClusterFuzz has detected this issue as fixed in range 510178:510722.

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

Fuzzer: miaubiz_css_fuzzer
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x00000024
Crash State:
  blink::IsTabHTMLSpanElement
  blink::EditingStyle::Init
  blink::EditingStyle::Create
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=506675:506699
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=510178:510722

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

Additional requirements: Requires Gestures

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 4517094841647104 is verified as fixed, so closing issue as verified.

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