You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When clicking the action kebabs on our tables (such as domain request and member), their accordion content should be right aligned rather than left aligned.
Acceptance criteria
Our kebab style is adjusted such that they are right aligned rather than left aligned.
For the domain request table, the accordion content is not "cut off" due to overflow-x styles.
Edge cases like the kebab display under the last record on the table are accounted for, or the "expand" dropdown for the member table.
Apply these changes to any case where we have kebabs in a table
Additional context
While setting the content style to "right: auto" will work for the member table, it is worth noting that this is not the case for the domain request table. Due to differences in how overflow-x is defined, this will cause the content to get "cut off" as it expands into the table directly. This will need to be accounted for - see the linked slack thread for more context on this.
Change the behavior of the overflow above a certain breakpoint and set the kebob positioning to whatever we want. Will only work on larger screens. If that does not work, dynamically add/remove the responsive table wrapper class based on screen size. Either way, we'd be creating 2 different layout schemes for these tables, plus reconciling one of these with the member table so we have some consistency. Might be tricky and warrants its own ticket.
zandercymatics
changed the title
Table action kebabs: open to the right rather than the left
Action kebabs for tables: open to the right rather than the left
Jan 16, 2025
Issue description
When clicking the action kebabs on our tables (such as domain request and member), their accordion content should be right aligned rather than left aligned.
Acceptance criteria
Additional context
While setting the content style to "right: auto" will work for the member table, it is worth noting that this is not the case for the domain request table. Due to differences in how overflow-x is defined, this will cause the content to get "cut off" as it expands into the table directly. This will need to be accounted for - see the linked slack thread for more context on this.
Current display:
Desired display:
See this thread for more context
Links to other issues
Implementation notes:
Change the behavior of the overflow above a certain breakpoint and set the kebob positioning to whatever we want. Will only work on larger screens. If that does not work, dynamically add/remove the responsive table wrapper class based on screen size. Either way, we'd be creating 2 different layout schemes for these tables, plus reconciling one of these with the member table so we have some consistency. Might be tricky and warrants its own ticket.
The text was updated successfully, but these errors were encountered: