Skip to content

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 21, 2024

Backport of #6394 to release/9.0

Fixes #6393

/cc @JamesNK

Customer Impact

Expand/collapse buttons on the trace details page don't update the data grid. Clicking on the expand/collapse does nothing. Users are unable to hide data they don't want to see.

Testing

Manual testing

expand-collapse

Risk

Low

Regression?

Yes, this worked in 8.2. A FluentUI update during 9.0 changed how data grid updates are handled and this situation wasn't updated to make it work.

Microsoft Reviewers: Open in CodeFlow

@drewnoakes
Copy link
Member

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@joperezr
Copy link
Member

Visible bug on high traffic page + regression. Approved.

@joperezr
Copy link
Member

@JamesNK Any automation that can be added to catch this in the future? Perhaps in form of a playwright test? Particularly curious as this is depending on fluent controls that can get updated without us noticing these breaks.

@joperezr
Copy link
Member

(The above question doesn't block this PR so I'm merging anyway)

@joperezr joperezr merged commit f356f2d into release/9.0 Oct 21, 2024
8 checks passed
@joperezr joperezr deleted the backport/pr-6394-to-release/9.0 branch October 21, 2024 21:05
@JamesNK
Copy link
Member

JamesNK commented Oct 21, 2024

@JamesNK Any automation that can be added to catch this in the future? Perhaps in form of a playwright test? Particularly curious as this is depending on fluent controls that can get updated without us noticing these breaks.

Yeah, a playwright test could probably have caught this. The downside is it's pretty difficult to write a test for this, and full coverage is a lot of tests.

@github-actions github-actions bot locked and limited conversation to collaborators Nov 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants