Bug description
On the Show User page, the expand/contract icons are not displayed for the “User info”, “Personal Info” and “Audit Info” sections.
Screenshots/recordings
Superset version
4.0.2
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [X] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [X] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
The expand/contract icons in Apache Superset are implemented using the AntdCollapse
component from the antd
library. The icons are styled with conditional logic that includes properties like animateArrows
and expandIconPosition
[1]. If these icons are not displaying, it could be due to a styling issue or a missing dependency related to these properties.
Here are a few things you might want to check:
-
Dependencies: Ensure that the
antd
library is correctly installed and up to date, as it provides theCollapse
component used for these icons. -
CSS/Styling: Verify that the CSS styles are correctly applied. The icons rely on specific styles for rotation and animation, which might not be applied if there are CSS conflicts or missing styles.
-
JavaScript Console: Check the browser's JavaScript console for any errors that might indicate why the icons are not rendering.
-
Component Props: Ensure that the props like
animateArrows
andexpandIconPosition
are set correctly in the component implementation.
If these checks do not resolve the issue, it might require a deeper dive into the specific implementation details of the 'Show User' page to identify any discrepancies.
To continue talking to Dosu, mention @dosu.
Comment From: sfirke
A very minor bug but yes I see this in Superset 4.0.2 as well, in both Chrome and Firefox.
Comment From: rusackas
PRs welcome for this... but really this needs to be converted to a React view, so supporting the FAB view isn't likely to get much love.
Comment From: rusackas
Looks like the PR attempting to fix this got closed for some reason. If anyone is interested in taking this up, that'd be great, but otherwise it might be closed as "not planned" soon, since we want to revamp this view to React anyway.