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

The Column Resize Selection Area Is Too Narrow On The Markdown Dashboard Widget #19838

Closed
3 tasks done
cccs-Dustin opened this issue Apr 25, 2022 · 1 comment
Closed
3 tasks done
Labels
#bug Bug report

Comments

@cccs-Dustin
Copy link
Contributor

cccs-Dustin commented Apr 25, 2022

Within the edit mode of a dashboard, hovering over the far right edge of the Markdown widget only shows the “move” cursor, not the “resize” cursor. This is inconsistent with the other types of charts, as for the rest of them, the "resize" cursor appears when one hovers over the far right edge.

The screenshot below is what you see when you try to adjust the width of a Markdown widget (you see the "move" cursor and not the "resize" cursor).
Very Small Column Resize Selection Area

How to reproduce the bug

  1. Go to a dashboard which contains a Markdown widget, or add a Markdown widget to a new or existing dashboard.
  2. Select the "Edit dashboard" button (pencil icon in the top right of the page).
  3. Try to adjust the width of the markdown widget.
  4. You will notice that it is not easy to get the "resize" cursor to appear.

Expected results

When you go to adjust the width of the Markdown widget, the "resize" cursor should appear and thus allow you to make the widget larger or smaller.

Actual results

When you try to find the area that gives you the "resize" cursor, it does not seem to exist, or it is so small that it takes a while to get your cursor lined up with it.

Screenshots

Please see the main summary for a screenshot

Environment

(please complete the following information):

  • browser type and version: Google Chrome (Version 100.0.4896.127)
  • superset version: Master
  • python version: Python 3.8.10
  • node.js version: v16.9.1
  • any feature flags active: N/A

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Also, since discovering this bug, I have created a fix for it on my local fork. I will create a corresponding PR that fixes this bug (and link it to this issue).

@cccs-Dustin
Copy link
Contributor Author

cccs-Dustin commented May 5, 2022

Closing this issue as the associated PR which fixes the bug has been merged into master. That PR can be found here: #19839

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

1 participant