You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<conversation with colleague> Me: if you mean if something is a spelling error and a grammar error then I think that's something we've never encountered before Colleague: Clearly you haven't my wrting.
</conversation with colleague>
Guess he has a point. Hence the question in the summary. Maybe aria-invalid should be a token list.
The text was updated successfully, but these errors were encountered:
-1
I don't think it needs to be a token list, and that will complicate things.
For a single misspelled word, there isn't enough info to mark it as a grammar error, since it's unknown what word was intended anyway.
The case for having both can be done as:
<span aria-invalid="grammar">Here is mine bad <span aria-invalid="spelling">santence<span>.</span>
If the editor in question is really smart it can recognize the bad grammar despite the misspelling, but the bad grammar is going to include the smaller node.
And just in case people want to argue with me, we could do this if we really had to: <span aria-invalid="grammar"><span aria-invalid="spelling">Yucks</span></span>.
The type of
aria-invalid
is currently a token.<conversation with colleague>
Me: if you mean if something is a spelling error and a grammar error then I think that's something we've never encountered before
Colleague: Clearly you haven't my wrting.
</conversation with colleague>
Guess he has a point. Hence the question in the summary. Maybe
aria-invalid
should be a token list.The text was updated successfully, but these errors were encountered: