I'm building a rich-text-editor component in vue using lexical and taking a lot of inspiration from the lexical-playground that is using the react plugins and trying to convert them where needed.

I stumbled upon a bug in my implementation when creating lists, styling and formatting was not applied and got that fixed using the code from "registerList".

One thing that still differs from my component and the lexical playground is that in the playground <li> elements has applied inline-styles (an example where this is needed is to get different sizes on list bullets or different colors etc.). I've searched best I could in the lexical repo but cant seem to find where in the code this is happening...

I think I could solve this with a custom styled ListItemNode but I would much rather dont have to do that.

Anyone that knows how this is done in the playground?

I'm building a rich-text-editor component in vue using lexical and taking a lot of inspiration from the lexical-playground that is using the react plugins and trying to convert them where needed.

I stumbled upon a bug in my implementation when creating lists, styling and formatting was not applied and got that fixed using the code from "registerList".

One thing that still differs from my component and the lexical playground is that in the playground <li> elements has applied inline-styles (an example where this is needed is to get different sizes on list bullets or different colors etc.). I've searched best I could in the lexical repo but cant seem to find where in the code this is happening...

I think I could solve this with a custom styled ListItemNode but I would much rather dont have to do that.

Anyone that knows how this is done in the playground?

• javascript
• vue.js
• lexicaljs

Share Improve this question Follow asked Mar 3 at 7:59 VatchiVatchi 1344 bronze badges 1

• can you share playground? – Utsav Sheta Commented Mar 4 at 5:10

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

Lexical recently published new versions after I installed the version I was using (0.25.0), in 0.26.0+ they seem to have fixed this issue so no extra code needed for me.