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

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

It crashes during VisibleSelection adjustment.

yoichio: Could you take a look?

It is from combination of document.execCommand("selectall") and
document.designMode = "on".
User impact might be low.

ClusterFuzz has detected this issue as fixed in range 560941:560959.

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_cfi_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  chrome
  blink::Node::MayContainLegacyNodeTreeWhereDistributionShouldBeSupported
  blink::Node::UpdateDistributionInternal
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=559420:559432
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=560941:560959

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

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

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