- From: <bugzilla@jessica.w3.org>
- Date: Mon, 01 Aug 2011 21:25:42 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13504
Charles Pritchard <chuck@jumis.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chuck@jumis.com
--- Comment #1 from Charles Pritchard <chuck@jumis.com> 2011-08-01 21:25:41 UTC ---
(In reply to comment #0)
> HTML5 should define a standardized mechanism for marking up phrases flagged by
> a spelling checker or the like, so that content scripts or assistive technology
> could react to them intelligently.
This issue was also brought up in relation to canvas-based rich text editing
and other custom IMEs. [ http://www.w3.org/Bugs/Public/show_bug.cgi?id=11238 ]
These mechanisms are already in place when native components are used, though
they are not exposed to the scripting environment due to security concerns. A
malicious script might be able to identify custom dictionary entries and
otherwise fingerprint the client machine based on the identification of
mis-spellings.
As for custom widgets: ARIA supports marking of invalid spelling and grammar
ranges.
http://www.w3.org/TR/wai-aria/states_and_properties#aria-invalid
That handles our DOM commitments regardless of the visual presentation.
Hironori Bono has been working on IME proposals for awhile, and has been
testing, within WebKit, spell checking as managed by the scripting environment.
He proposed several new interfaces including window.spellCheckController and
SpellcheckRange.
https://lists.webkit.org/pipermail/webkit-dev/2011-June/017242.html
http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/0545.html
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 1 August 2011 21:25:43 UTC