Skip to content

Fix: Prevent select extension when hovering Ask AI button during mouse drag #1304

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

dnp314
Copy link

@dnp314 dnp314 commented Jul 15, 2025

Summary

Fixes a bug where, while selecting text and hovering over the Ask AI button (with the mouse button still held down), the browser would incorrectly extend the text selection to include extra content below the selection.
This PR disables pointer events on the Ask AI button while the mouse is pressed, preventing the browser from expanding the selection during drag.

List of files changed and why

  • docs/md_v2/assets/style.css
    • Added .no-pointer class to disable pointer events on the Ask AI button while selecting.
  • docs/md_v2/assets/selection_ask_ai.js
    • Updated mouse event handlers to add/remove the .no-pointer class on the Ask AI button during selection drag.

How Has This Been Tested?

  • Manually tested by selecting text, dragging over the Ask AI button, and confirming the selection is no longer extended.
  • Verified that after releasing the mouse button, the Ask AI button can be clicked as expected.
  • Tested in Chrome .

https://github.com/user-attachments/assets/b3cde6e4-9ede-4a3e-8622-b6768417af95

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added/updated unit tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes (or N/A if no tests)

Summary by CodeRabbit

  • New Features

    • Improved the interactivity of the Ask AI button by toggling pointer events during mouse and touch interactions for a smoother user experience.
  • Style

    • Added a CSS rule to disable pointer events on the Ask AI button when needed, enhancing its responsiveness.

Copy link
Contributor

coderabbitai bot commented Jul 15, 2025

Walkthrough

The changes update the behavior and styling of the "Ask AI" selection button by toggling a 'no-pointer' CSS class during mouse and touch interactions. JavaScript event listeners now add or remove this class on pointer events, while a new CSS rule disables pointer events for the button when the class is present.

Changes

File(s) Change Summary
docs/md_v2/assets/selection_ask_ai.js Updated mouseup/touchend and mousedown/touchstart event listeners to toggle the 'no-pointer' class on the Ask AI button.
docs/md_v2/assets/styles.css Added CSS rule to disable pointer events for .ask-ai-selection-button.no-pointer.
mkdocs.yml Added a newline at the end of the file with no functional changes.

Poem

A button awaits with pointer so sly,
Now toggled by code as events pass by.
With 'no-pointer' it sits, untouchable, still—
Then springs back to life with a click or a will.
Such is the dance of the Ask AI crew,
Where style meets logic, and interactivity too!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e185cba and de0d617.

📒 Files selected for processing (2)
  • docs/md_v2/assets/selection_ask_ai.js (2 hunks)
  • mkdocs.yml (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • mkdocs.yml
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/md_v2/assets/selection_ask_ai.js
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs/md_v2/assets/selection_ask_ai.js (1)

167-167: Consider adding consistent touch event handling.

The mousedown handler adds the no-pointer class, but the corresponding touchstart handler (line 174) doesn't. This could lead to inconsistent behavior between mouse and touch interactions on mobile devices.

Consider adding the same class manipulation to the touchstart handler for consistency:

 document.addEventListener('touchstart', (event) => {
+    if (askAiButton) askAiButton.classList.add('no-pointer');
     // Same for touch events, but only hide if not on the button
     if (askAiButton && event.target !== askAiButton) {
         hideButton();
     }
 });

And ensure the touchend handler also removes the class:

-document.addEventListener('touchend', handleSelectionEvent);
+document.addEventListener('touchend', (event) => {
+    if (askAiButton) askAiButton.classList.remove('no-pointer');
+    handleSelectionEvent(event);
+});
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bde1bba and e185cba.

📒 Files selected for processing (2)
  • docs/md_v2/assets/selection_ask_ai.js (2 hunks)
  • docs/md_v2/assets/styles.css (1 hunks)
🔇 Additional comments (2)
docs/md_v2/assets/styles.css (1)

264-266: Clean CSS implementation for disabling pointer events.

The CSS rule correctly disables pointer events on the Ask AI button when the no-pointer class is applied. The selector specificity and !important declaration ensure this takes precedence during drag operations.

docs/md_v2/assets/selection_ask_ai.js (1)

147-150: Proper cleanup of pointer events on mouseup.

The implementation correctly removes the no-pointer class before processing the selection event, ensuring the button remains interactive after the drag operation completes.

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.

1 participant