Although browser spellcheck works on many commonly used fields (title, etc.), it does not work in the content field of the notes sub-records in resource records. This leads to frequent typos, particularly since inexperienced users expect that the spellcheck works in all fields.
Closing this since is a more holistic description of the desired functionality.
, should we resurrect this ticket and couch it specifically for enabling browser-provided spell check for these fields?
At the October 6, 2020 meeting of Dev/Pri this ticket was approved for implementation, but it was noted that adding this functionality must avoid breaking the wrap in tag and autocomplete tag functions.