Skip to content

Conversation

@shenjunjian
Copy link
Collaborator

@shenjunjian shenjunjian commented Mar 28, 2025

PR

日历视图组件, 让鼠标可以移入tooltip

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our Commit Message Guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • Refactor
    • Streamlined the calendar view’s tooltip behavior for a more responsive experience.
    • Tooltips now appear almost immediately on hover and dismiss more smoothly with controlled timing.
    • Consistent improvements have been applied across both mobile and desktop views for enhanced usability.

@coderabbitai
Copy link

coderabbitai bot commented Mar 28, 2025

Walkthrough

This PR refines the tooltip management within the calendar view components. The changes adjust the mouse event handlers by modifying their logic and parameters. Specifically, the tooltip now shows immediately upon a mouseenter event with a scheduled call after a 20ms delay and employs a controlled closing mechanism on mouseleave by calling setExpectedState(false) and debounceClose(). Additionally, the state property eventTipVisible has been removed and the tooltip’s reactive binding has been eliminated from the Vue templates.

Changes

File(s) Change Summary
packages/renderless/.../calendar-view/index.ts Revised handleMouseenter to remove tooltip hiding logic and schedule tooltip.show() with a 20ms timeout; updated handleMouseleave to destructure vm, calling setExpectedState(false) and debounceClose().
packages/renderless/.../calendar-view/vue.ts Removed the eventTipVisible property from the state in initState and updated the handleMouseleave method to receive vm instead of state.
packages/vue/.../mobile-first.vue
packages/vue/.../pc.vue
In both Vue components, removed the v-model binding and :manual attribute from <tiny-tooltip>, with pc.vue also including minor formatting adjustments in class bindings.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant C as Calendar Component
    participant T as Tooltip

    U->>C: Mouse Enter
    C->>T: Set tooltip content
    C->>T: Schedule tooltip.show() (20ms delay)
    T-->>C: Tooltip displayed

    U->>C: Mouse Leave
    C->>T: Call setExpectedState(false)
    C->>T: Trigger debounceClose()
    T-->>C: Tooltip hidden
Loading

Possibly related PRs

Suggested labels

bug

Suggested reviewers

  • zzcr

Poem

I'm a bunny coder, hopping through the code,
With tooltips now quick to bloom and unload,
Mouse enters light up the view with a spark,
Mouse leaves bring calm and quell the dark,
I nibble on changes with a joyful bound,
Rabbit-approved fixes in every round!

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/renderless/src/calendar-view/index.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

packages/vue/src/calendar-view/src/mobile-first.vue

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

packages/vue/src/calendar-view/src/pc.vue

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

  • 1 others
✨ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

@github-actions github-actions bot added the bug Something isn't working label Mar 28, 2025
@petercat-assistant
Copy link

Walkthrough

This PR addresses an issue in the calendar view component where the tooltip could not be hovered over with the mouse. The changes involve modifying the tooltip handling logic to ensure it can be interacted with using the mouse.

Changes

Files Summary
index.ts, vue.ts Updated tooltip handling logic to allow mouse interaction by removing manual visibility control and using tooltip methods for showing and hiding.
mobile-first.vue, pc.vue Removed v-model binding for tooltip visibility and adjusted tooltip attributes for better mouse interaction.

state.eventTipContent = val
state.eventTipVisible = true
setTimeout(tooltip.updatePopper, 20)
setTimeout(tooltip.show(), 20)

Choose a reason for hiding this comment

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

Using setTimeout(tooltip.show(), 20) might cause unexpected behavior because tooltip.show() is executed immediately, and setTimeout will receive its return value, not the function itself. Consider passing the function reference: setTimeout(() => tooltip.show(), 20). This ensures tooltip.show() is called after the delay.

@github-actions
Copy link

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide

@shenjunjian shenjunjian changed the title fix(calendar-view): fix popper cant mouse enter fix(calendar-view): [calendar-view] fix popper cant mouse enter Mar 28, 2025
Copy link

@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: 3

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between db24997 and c491177.

📒 Files selected for processing (4)
  • packages/renderless/src/calendar-view/index.ts (1 hunks)
  • packages/renderless/src/calendar-view/vue.ts (1 hunks)
  • packages/vue/src/calendar-view/src/mobile-first.vue (1 hunks)
  • packages/vue/src/calendar-view/src/pc.vue (2 hunks)
🧰 Additional context used
🧬 Code Definitions (1)
packages/renderless/src/calendar-view/vue.ts (1)
packages/renderless/src/calendar-view/index.ts (1)
  • handleMouseleave (65-71)
🔇 Additional comments (3)
packages/renderless/src/calendar-view/vue.ts (1)

289-289: Enhanced mouseout handling by using ViewModel reference instead of state.

Good change to update the handleMouseleave function parameter from state to vm. This change aligns with the implementation in index.ts where the function needs direct access to the tooltip reference through vm.$refs.tooltip.

packages/vue/src/calendar-view/src/pc.vue (1)

61-62: Simple indentation improvement.

Minor formatting change that improves readability of the conditional expression.

packages/renderless/src/calendar-view/index.ts (1)

62-62: Improved tooltip display with slight delay.

Adding the timeout ensures the tooltip appears consistently after a brief delay (20ms), which improves the interaction flow and maintains a smooth user experience.

effect="light"
placement="right"
>
<tiny-tooltip ref="tooltip" popper-class="absolute max-w-[theme(spacing.80)]" effect="light" placement="right">
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Improved tooltip interaction by removing visibility binding and manual control.

The removal of v-model="state.eventTipVisible" and :manual="true" attributes from the tooltip component allows for smoother user interaction with tooltip content. This change enables users to directly move their mouse onto the tooltip without it disappearing.

effect="light"
placement="right"
>
<tiny-tooltip ref="tooltip" popper-class="tiny-calendar-view-tooltip" effect="light" placement="right">
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Improved tooltip interaction by removing visibility binding and manual control.

The removal of v-model="state.eventTipVisible" and :manual="true" attributes from the tooltip component is consistent with the changes in mobile-first.vue and allows users to move their mouse onto the tooltip without it disappearing.

Comment on lines +66 to 71
({ vm }) =>
() => {
state.eventTipVisible = false
const tooltip = vm.$refs.tooltip
tooltip.setExpectedState(false)
tooltip.debounceClose()
}
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fixed tooltip hover issue with improved close mechanism.

This is the core of the fix. By changing the mouse leave handler to:

  1. Access tooltip directly via vm.$refs.tooltip
  2. Set expected state to false with setExpectedState(false)
  3. Use debounceClose() to delay closing

This allows users to move their mouse from the event item onto the tooltip before it closes, fixing the "popper cant mouse enter" issue.

@zzcr zzcr merged commit 6fee367 into dev Mar 28, 2025
13 of 16 checks passed
@kagol kagol deleted the shen/fix-calender-tooltip-enter branch April 14, 2025 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants