Ticket #6600 (closed enhancement: fixed)

Opened 7 months ago

Last modified 6 hours ago

[patch][ccla] dijit._editor/RichText has a programmatic and declarative way to disable spell checking in FireFox

Reported by: jaredj Owned by: liucougar
Priority: normal Milestone: 1.3
Component: Editor Version: 1.1.0
Severity: normal Keywords:
Cc:

Description (last modified by jaredj) (diff)

Request: dijit._editor/RichText has a programmatic and declarative way to disable spell checking in FireFox?.

I've been working with some people in my office that encountered a scenario where it would be extremely helpful if the editor and RichText? widgets had a way to programmatically and declaratively disable firefox's spell check feature. An example scenario is if the editor is being used to view and edit source code. Function names and the like will definitely be flagged as misspelled. The disable is simply setting the attribute spellcheck="false" on the body of the iFrame returned by _getIframeDocTxt().

This can be easily exposed as a widget instantiation parameter and declarative parameter, but I'm not sure it can be toggled on and off easily programmatically once it has been created (I haven't dug that far into it).

A patch with the prelim code needed for disabling spell check in RichText? as well as a test case for it will be coming shortly.

Attachments

Change History

Changed 7 months ago by jaredj

  • description modified (diff)

Changed 7 months ago by jaredj

Changed 5 months ago by peller

  • summary changed from Request: dijit._editor/RichText has a programmatic and declarative way to disable spell checking in FireFox to [patch][ccla] dijit._editor/RichText has a programmatic and declarative way to disable spell checking in FireFox

Changed 5 months ago by bill

  • milestone set to tbd

mark all (open) tickets w/blank milestones to be "tbd"; their milestones need to be set to a version number or to "future"

Changed 3 months ago by bill

  • milestone changed from tbd to 1.3

Changed 13 days ago by bill

  • milestone changed from 1.3 to 1.4

Note that safari doesn't have a way to do this yet, see https://bugs.webkit.org/show_bug.cgi?id=14552.

Changed 6 hours ago by peller

  • status changed from new to closed
  • resolution set to fixed
  • milestone changed from 1.4 to 1.3

Fixed in [16008]

Note: See TracTickets for help on using tickets.