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 adding ccs based on suspected regression changelists:

Replace calls of deprecated functions FirstPositionInOrBeforeNode by iceman@yandex-team.ru - https://chromium.googlesource.com/chromium/src/+/988b43d3c131f73b07db7186b8a01de7be568076

Remove deprecated versions of {First,Last}PositionInOrBeforeNode() by iceman@yandex-team.ru - https://chromium.googlesource.com/chromium/src/+/3accfc0b420fd982759568435f2683061b883d0f

Update ICU to version 60.1 + local patches by jshin@chromium.org - https://chromium.googlesource.com/chromium/src/+/befb16634bb440cf5442979ad262832b4cebd43e

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

Lower to P2 due to the unusual HTML that will be normally rejected by HTML parser:

A slightly cleaner test case:

<caption>
foo
<meta></meta>
<a contenteditable="true">
<svg viewbox="10 0 65 10" writing-mode="tb"></svg>
<basefont></basefont>
</a>
</caption>
<script>
var basefont = document.createElement('basefont'); 
document.querySelector('meta').appendChild(basefont); 
var sel = window.getSelection(); 
sel.collapse(basefont); 
sel.modify("move","right","word"); 
</script>

ClusterFuzz has detected this issue as fixed in range 545385:545392.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::EditingIgnoresContent
  blink::PositionTemplate<blink::EditingAlgorithm<blink::NodeTraversal> >::FirstPo
  blink::DirectionOfEnclosingBlockOf
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=514498:517702
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=545385:545392

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

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

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