hmm...I understand the motivation and I think you're right, but it works 60% okay on Windows thanks to Windows transparent API using "@" prefix in the font name, and I know at least a few sites are already using it. I've got a request to ignore "@" when I provided my private build for test purpose because his site is using the feature with "@" today. How bad is it to keep the current behavior? I'm fine to disable text-orientation because it's not working at all, but feels better if we can leave writing-mode enabled for reasons above. Or maybe you want to disable by reading this because we don't want sites to rely on half-baked features?

As is, we're breaking the feature detection and doing a disservice to the Web :(

Yeah, right, but we've been leaving this for more than a year, and the patch is in the review queue, so I hope we can land it within a month or so. Along with by being closer to users who wish to keep the half-baked feature, I'm leaning towards not to disable writing modes. That's my opinion, but I'm fine to follow to whatever decisions you guys make. Is this already discussed and agreed, or are you just pinging for opinions?

Marked LayoutTest bugs, bugs with Chromium IDs, and some others as WontFix. Test failure bugs still are trackable via TestExpectations or disabled unit tests.