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

fix: Clicking in the body of a Markdown component does not put it into edit mode #32384

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

notHuman9504
Copy link

@notHuman9504 notHuman9504 commented Feb 26, 2025

fixes: #32252

Solved Issue of not able to switch to edit mode when clicking on div.

@dosubot dosubot bot added dashboard:editmode Related to te Dashboard edit mode dashboard:markdown Related to the markdown component of the Dashboard labels Feb 26, 2025
Copy link

@korbit-ai korbit-ai bot left a comment

Choose a reason for hiding this comment

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

Review by Korbit AI

Korbit automatically attempts to detect when you fix issues in new commits.
Category Issue Fix Detected
Functionality Incorrect Event Propagation Logic ▹ view
Performance Redundant State Update in Click Handler ▹ view
Files scanned
File Path Reviewed
superset-frontend/src/dashboard/components/menu/WithPopoverMenu.tsx
superset-frontend/src/dashboard/components/gridComponents/Markdown.jsx

Explore our documentation to understand the languages and file types we support and the files we ignore.

Need a new review? Comment /korbit-review on this PR and I'll review your latest changes.

Korbit Guide: Usage and Customization

Interacting with Korbit

  • You can manually ask Korbit to review your PR using the /korbit-review command in a comment at the root of your PR.
  • You can ask Korbit to generate a new PR description using the /korbit-generate-pr-description command in any comment on your PR.
  • Too many Korbit comments? I can resolve all my comment threads if you use the /korbit-resolve command in any comment on your PR.
  • Chat with Korbit on issues we post by tagging @korbit-ai in your reply.
  • Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.

Customizing Korbit

  • Check out our docs on how you can make Korbit work best for you and your team.
  • Customize Korbit for your organization through the Korbit Console.

Current Korbit Configuration

General Settings
Setting Value
Review Schedule Automatic excluding drafts
Max Issue Count 10
Automatic PR Descriptions
Issue Categories
Category Enabled
Documentation
Logging
Error Handling
Readability
Design
Performance
Security
Functionality

Feedback and Support

Note

Korbit Pro is free for open source projects 🎉

Looking to add Korbit to your team? Get started with a free 2 week trial here

Comment on lines +164 to +166
if (shouldFocusComponent) {
event.stopPropagation();
}
Copy link

Choose a reason for hiding this comment

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

Incorrect Event Propagation Logic category Functionality

Tell me more
What is the issue?

The event.stopPropagation() is called when shouldFocusComponent is true, which contradicts the comment 'Allow the event to propagate to the Markdown component' and the intended behavior.

Why this matters

This will prevent the click event from reaching the Markdown component when we actually want it to be editable, potentially breaking the main feature this PR aims to implement.

Suggested change ∙ Feature Preview

The event.stopPropagation() should be removed or the logic should be inverted depending on the exact desired behavior. If we want to allow propagation to Markdown, simply remove these lines:

if (shouldFocusComponent) {
    event.stopPropagation();
}

Report a problem with this comment

💬 Chat with Korbit by mentioning @korbit-ai.

Comment on lines +391 to +396
onClick={() => {
if (editMode) {
this.handleChangeFocus(true);
this.handleChangeEditorMode('edit');
}
}}
Copy link

Choose a reason for hiding this comment

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

Redundant State Update in Click Handler category Performance

Tell me more
What is the issue?

Redundant call to handleChangeEditorMode('edit') since handleChangeFocus(true) already triggers edit mode

Why this matters

The redundant call creates unnecessary state updates and could potentially cause race conditions or unexpected behavior in the component's state management

Suggested change ∙ Feature Preview

Remove the redundant call to handleChangeEditorMode and only use handleChangeFocus:

onClick={() => {
  if (editMode) {
    this.handleChangeFocus(true);
  }
}}

Report a problem with this comment

💬 Chat with Korbit by mentioning @korbit-ai.

@notHuman9504
Copy link
Author

@rusackas , @sfirke test this one.

@sadpandajoe sadpandajoe changed the title Fix issue #32252: Clicking in the body of a Markdown component does n… fix: Clicking in the body of a Markdown component does not put it into edit mode Feb 26, 2025
@sadpandajoe sadpandajoe requested a review from rusackas February 26, 2025 18:27
@notHuman9504
Copy link
Author

notHuman9504 commented Feb 26, 2025

@rusackas , @sfirke Its done can you check it?

@sfirke
Copy link
Member

sfirke commented Feb 26, 2025

I see it's passing CI, excellent! I don't know enough front end to review but hopefully @rusackas can take a look or tag another reviewer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dashboard:editmode Related to te Dashboard edit mode dashboard:markdown Related to the markdown component of the Dashboard size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clicking in the body of a Markdown component does not put it into edit mode.
2 participants