Skip to content
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

Colspan has no effect PageModule when using Fluid rendering #53

Closed
YKWeyer opened this issue Oct 16, 2023 · 2 comments · May be fixed by #54
Closed

Colspan has no effect PageModule when using Fluid rendering #53

YKWeyer opened this issue Oct 16, 2023 · 2 comments · May be fixed by #54

Comments

@YKWeyer
Copy link

YKWeyer commented Oct 16, 2023

When using fluidBasedPageModule on TYPO3 v11, the colCount / colspan keys has no effect on the rendering in the Page module. All columns will automatically be adjusted based on their content.

It seems to be caused by the lack of a <colgroup> tag inside the grids <table>

@Cybercraft-GmbH
Copy link
Collaborator

colspan has nothing to do with adjusted widths of table cells or their respective ration to each other. It just determines the way table cells overlap each other.

Since a fixed maximum width of a cell will break the rendering of nested Gridelements at a certain point, this behaviour most likely won't change in the near future. Even colgroup tags could only determine a minimum width, but would not help to fix that problem completely, since a maximum width again would break nested structures.

@YKWeyer
Copy link
Author

YKWeyer commented Oct 16, 2023

Since a fixed maximum width of a cell will break the rendering of nested Gridelements at a certain point, this behaviour most likely won't change in the near future

I am very sorry for the lack of clarity, but it is not a feature request but a bug report.

This is something that used to work, and that probably still works when the fluid rendering is disabled, since it still is part of the DrawItem::renderGridLayoutTable logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants