Acy Watson
Acy Watson
> Though with such an API you could just generate \ nesting yourself by responding to the appropriate edit events. The problem is that the the HTML spec itself doesn't...
I'm going to leave this one open for the moment, because I actually think that reducing the out-of-the-box footprint of Lexical JSON is a goal worth pursuing and potentially do-able....
> The congruence between the `exportJSON` output and the state managed by lexical seems to be consistent and effective. > > It is possible to efficiently access the nodes and...
Note the failing UTs
> 🚢🚢🚢 
Can you help me out by pasting in here the HTML that MS Word puts on the clipboard? The issue is going to be that they're not using semantic HTML.
I've been looking at re-working our nested lists logic, partially to fix this problem. One issue is that, AFAICT, it's impossible to get browsers to render a list with an...
> What is the change you plan to make (and why)? Forbid a li from indenting more than one level from her parent? **Selected quotes from my comment above:** With...
> The more I think about lists and indents, the more convinced I am that `ul` and `ol` were an HTML error from the start. In my opinion, the standard...
> I would think that valid HTML/semantics would be a high priority to ensure accessibility, compatibility and consistent behavior across browsers. It is, which is exactly why this whole thing...