-
Notifications
You must be signed in to change notification settings - Fork 207
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
Optimize responsive tables #1509
Comments
@dev7ch As far as i can see, we should keep the table="table-responsive" and optimize this class instead of adding something new. this way developers does not have to find some misc luya bs4 features somewhere.
|
the bs4
|
|
explanation: if we have a This can be only done with a wrapper as a far i can see. |
@TheMaaarc so we should take care of this problem, maybe we can only use this wrapping div for the CRUD table? |
@TheMaaarc Please add this table-responsive wrapper informations to the docks. |
If everything is OK we can close this issue. |
@dev7ch @TheMaaarc keep the issue open for a while so we can test the changes and see if some unexpected behaviors appear. |
👍 |
What steps will reproduce the problem?
In Luya Admin navigate to News > Categories and open e.g. Chrome inspect element toolbar
this happens on a 15" screen (macbook), if page width is less then 1280px
What is the expected result?
What do you get instead? (A Screenshot can help us a lot!)
This comes from the bs4 css class
table-responsive
usually its haves an effect under breakpoint sm ( less then 768px )In compiled luya css we have
Why do we have this up to 1280px @luyadev/coredev ? is bootstrap overwritten for this case?
Suggested Solution
We should wrap tables into a div like:
and add a styling like:
This would give us a much more suitable control to responsive tables.
If it tables would be wrapped we could use the style
display: inline-table
fortable
to fix this issue.The table wrapper could be also applied via js, just instead of add it manually in every html files.
Additional infos
The text was updated successfully, but these errors were encountered: