I can confirm, it hasn't been removed. I don't have a deadline for removal either. It's been in place for years, and it feels like it can remain in the current state (enabled by the user) for a few months more, while we ship other features and work on higher-priority technical debt. If something changes, such as SCAYT publishing ads that go beyond self-promotion, we may have to act quickly, so I'm glad we started the discussion. It may become a blocking issue when we start on other work, such as a strict Content Security Policy.
I've opened bug 1351022 to track the feature change.
On Tuesday, March 21, 2017 at 2:53:23 PM UTC-5, Eric Shepherd wrote:
> No, SCAYT remains in place. Some of the improvements to its configuration went live, but after deciding to remove it eventually, we have done nothing further.
> I believe we do have consensus about switching to the built-in spell checker, although there’s an issue with the fact that this requires a weird key-click thing to get at the browser’s engine. Ideally we’d figure out how to either make CKEditor use the standard context menu, or add access to the built-in spell checker to the CKEditor context menu widget.
> > On Mar 21, 2017, at 3:03 PM, Janet Swisher wrote:
> > Has anything changed as a result of this discussion? I came across a mention of SCAYT in the meta-docs, and I'm not sure whether to delete the mention yet.