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

Mesa fix layout #1298

Merged
merged 2 commits into from
Dec 9, 2024
Merged

Mesa fix layout #1298

merged 2 commits into from
Dec 9, 2024

Conversation

dmfalke
Copy link
Member

@dmfalke dmfalke commented Dec 9, 2024

This PR addresses some recently introduced layout issues with Mesa table, specifically when rows are either selectable or expandable.

With the relatively recently position: sticky css value, we can dramatically simplify the html and remove a decent amount of runtime javascript.

These changes impact all uses of Mesa table:

  • Dataset and study pages
  • Strategy results
  • Record page tables
  • EDA categorical filters
  • TreeTable (ortho group record's protein table)

Seeing as this is an urgent fix (the bug is on production), I would appreciate a quick review. I'm happy to go over changes in more detail, after this is merged.

@dmfalke dmfalke merged commit 467eb3b into main Dec 9, 2024
1 check passed
@dmfalke dmfalke deleted the mesa-fix-layout branch December 9, 2024 22:36
const { columns } = this.props;
const hasSelectionColumn = this.hasSelectionColumn();
const { contentTable, getInnerCellWidth } = this;
this.setState({ dynamicWidths: null }, () => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused as to where this.state.dynamicWidths is ever accessed?

This seems to be more about setting this.widthCache.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching. That was an oversight. I meant to purge all occurrences of dynamicWidths. Will fix in a follow-up.

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 this pull request may close these issues.

3 participants