Apparently it was fixed upstream by Google?

Not sure how long it will take to get resolved but that thread seems reassuring even if there isn't a direct source that it was fixed.

AnssiH 3 days ago | parent | next [-]

It is not fixed.

In the thread you linked to people are confusing a typo correction ("mas fixed" => "was fixed") as a claim about this new issue being fixed.

The one that was fixed is this similar old issue from years ago: https://issuetracker.google.com/issues/172048751

	▲	jchw 2 days ago \| parent [-]
		Oh, that's unfortunate, very confusing thread.

Still haven't. Currently, most of the devs aren't aware of this underlying issue!