When migrating a Plone page using DraftJS to Slate (via DraftJS -> HTML -> Slate) we do not want to lose table block settings.
So I propose respecting the table settings by evaluating its classes when converting a HTML to a Slate table.
To avoid applying this behavior to "usual" HTML tables (and messing up the default settings for those cases) I propose only to apply this behavior to tables having the classes ui table .
When migrating a Plone page using DraftJS to Slate (via DraftJS -> HTML -> Slate) we do not want to lose table block settings.
So I propose respecting the table settings by evaluating its classes when converting a HTML to a Slate table. To avoid applying this behavior to "usual" HTML tables (and messing up the default settings for those cases) I propose only to apply this behavior to tables having the classes
ui table
.