+Ketaki

Without a milestone label, releaseblock-beta has no meaning.

Also 9202.18.0 has already rolled out to beta, so the genie is already out of the bottle here.

This is specific to Chrome OS.

Yes, please add the right milestone so that we can track these kind of issues timely.

vsuley@ This is already fixed adn the fix is in the build for todays qualification. Please validate

As per Katherine cyan should work.Other devices still need to explore.

could not repro with the M57 beta candidate 9202.28.0

[Auto-generated comment by a script] We noticed that this issue is targeted for M-57; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-57 label, otherwise remove Merge-TBD label. Thanks.