This would avoid bugs like issue 596105.

Very much opposed to Chrome changing system configuration. 

This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue.
The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

+shrike@ — but tentatively WontFixing, too. It looks like Chrome includes an option to use Google for spelling suggestions, and that seems like a good solution for anyone who's not satisfied with macOS's built-in spelling dictionaries.

FWIW - server-side spelling might be unpalatable to users who don't want to transmit their entire typing to a server-side process.

But even if we accept the above solution, it doesn't help - you cannot switch to a language that macOS currently doesn't support. Tentatively reopening, unless macOS team decides that restricting to system languages is OK. (I'd think that's the right decision, but I'd like that to be an *explicit* decision with awareness there's no fallback)

Hi groby@,

I agree with your reasoning in c#5 and c#2. Given that we don't want to support downloading dictionaries into ~/Library/Spelling, and that we don't want to say Google spelling is the answer, are there any other options? Or is this a wontfix because we are out of options?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

ellyjones@ what do you think re: c#6?

Mac TL: WontFix. We will not support this.