-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#3274: Updated table layout post-fixer and upcast converters to properly fix empty rows. #6762
Conversation
I think that this fix is too late in the whole progress. We must always have valid model and all algorithms that operates on model expects that and must create valid table. We have post-fixers for cases that general algorithms on the model could produce invalid table. In most of the cases it is due to collaboration changes. This might happen when applying colliding changes from an external editor. The most obvious case is: user A insert row user B inserts column. Such changes should only be the reason to fix improper model structure. The table upcast converters should work with invalid HTML - just because not everybody reads the specs and can create something invalid. We will not fix them all and let the table blow-up :man_shrugging: . But in cases that an invalid HTML breaks the editor should be addressed there. In other words we should create valid model from an invalid input during upcast conversion if feasible. I think that the provided change is not in line with a valid table model and will yield table model error:
I think that we should remove empty row from the model or not allow it to land it in the model in the first place. The fixer for rowspan attributes should cover cases where all cells occupies slots of another row. So that could be another issue. ps.: I like the idea of "slot" - I didn't probably noticed that before and maybe it would be a better to use this term for "spanned" cells. |
I've forgot about this tool: https://validator.w3.org/nu/#textarea. Example set of errors: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As above :point_up: .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :+1: I'd change one thing - to be discussed on F2F before pushing.
Suggested merge commit message (convention)
Fix (table): Table layout post-fixer and upcast converters should properly handle empty rows . Closes #3274.
Additional information