Skip to content

fix(fluent-editor): Fix click issues with rich text components in Edge browser #3655

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 1 commit into
base: dev
Choose a base branch
from

Conversation

chenxi-20
Copy link
Collaborator

@chenxi-20 chenxi-20 commented Aug 19, 2025

PR

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

  • Bug Fixes
    • Fullscreen toggle now reliably responds to clicks on the on-screen control (mouse/touch), improving usability.
    • Escape key behavior for exiting fullscreen remains consistent, ensuring parity across keyboard and mouse interactions.
    • No changes to user-facing settings or configuration; behavior is more consistent without altering workflows.

Copy link

coderabbitai bot commented Aug 19, 2025

Walkthrough

The keyDownHandler in packages/renderless/src/fluent-editor/index.ts now conditionally handles click events to toggle fullscreen, in addition to existing Escape key handling. No function signatures or public APIs changed.

Changes

Cohort / File(s) Summary
Fullscreen toggle input handling
packages/renderless/src/fluent-editor/index.ts
Converted trailing else to else if (e.type === 'click') to process click events for fullscreen toggle alongside Escape key logic; no exported API changes.

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant FullscreenButton
  participant Editor
  participant Handler as keyDownHandler

  User->>FullscreenButton: Click
  FullscreenButton->>Handler: Event(type="click")
  Handler->>Editor: Toggle fullscreen

  User->>Editor: Keydown (Escape)
  Editor->>Handler: Event(key="Escape")
  Handler->>Editor: Toggle fullscreen (if currently fullscreen)
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I thump my paws—click!—the screen grows wide,
A tap, a key, we slip to fullscreen’s tide.
Escape to burrow back, snug and neat,
Two paths, one tunnel, tidy and sweet.
In code’s soft clover, I hop with delight,
Toggling the moon to brighten the night.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/fluent-editor-bug-20250819

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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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 Aug 19, 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: 0

🧹 Nitpick comments (1)
packages/renderless/src/fluent-editor/index.ts (1)

140-146: Harden Escape detection (deprecated keyCode) and keep click handling — cross-browser fix

Good call scoping the non-keyboard path to clicks. To make Escape handling reliable in Edge and modern browsers (where keyCode is deprecated and can be 0/undefined), detect Escape via event.key first and fall back to keyCode.

Proposed change:

-    if (e.keyCode) {
-      if (e.keyCode === 27 && state.isFullscreen) {
-        state.isFullscreen = !state.isFullscreen
-      }
-    } else if (e.type === 'click') {
-      state.isFullscreen = !state.isFullscreen
-    }
+    if (e.type === 'keydown') {
+      const isEscape =
+        (typeof (e as any).key === 'string' && (e as any).key === 'Escape') ||
+        (e as any).keyCode === 27
+      if (isEscape && state.isFullscreen) {
+        state.isFullscreen = !state.isFullscreen
+      }
+    } else if (e.type === 'click') {
+      state.isFullscreen = !state.isFullscreen
+    }

Suggested quick validation:

  • Chrome/Firefox/Edge: Enter fullscreen via the toolbar button (click), then press Escape to exit. Ensure no toggle occurs on other keys.
  • Edge specifically: Verify Escape works even if keyCode is not set, thanks to event.key === 'Escape'.
📜 Review details

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

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 4366672 and 1b0026e.

📒 Files selected for processing (1)
  • packages/renderless/src/fluent-editor/index.ts (1 hunks)

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.

1 participant