[w3c/editing] Valid text element declaration for rich text editing caret accessibility (Issue #481)

jabcreations created an issue (w3c/editing#481)

I'm the developer of the JAB Creations web platform which has a rich text editor called the Rich Editor. I use very minimal HTML and like most web developers and designers dislike pixels and spacing added by visual formatting by line break in structural HTML (e.g. header, menu, footer, main, etc)  to be annoying. In my Rich Editor I disallow text to be added to what I consider non-text elements. Yes, I know many people love putting text in structural elements like div elements however the context and semantics are lost.

I think it would be valuable for websites with rich text editing to have the ability to define (on their own terms for those who just have to have div text) an array of what they consider valid text elements. This would help greatly improve keyboard caret accessibility with the browsers knowing which elements may and absolutely should not move the keyboard caret to while navigating via Tab or arrow keys in example. That way the HTML generated would be vastly more consistent between rendering engines. 

An exhaustive example from my platform's JavaScript elements_array_text() function:

```
<div contenteditable="true" validtextelements="a,abbr,acronym,area,bdi,bdo,cite,code,data,datalist,dd,del,dfn,dt,em,ins,kbd,label,li,map,mark,p,pre,q,rb,rbc,rp,rt,rtc,ruby,s,sam,small,span,strong,style,sub,sup,textarea,time,td,th,tt,u,var">
<p></p>
</div>
```

This should please everyone since there will be someone somewhere that insists on putting text in divs; they can just add whatever elements to the comma delimited array.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/481
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/481@github.com>