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: Slash command menu bad positioning in Web Version #709

Merged
merged 1 commit into from
Feb 18, 2024
Merged

fix: Slash command menu bad positioning in Web Version #709

merged 1 commit into from
Feb 18, 2024

Conversation

dagyu
Copy link
Contributor

@dagyu dagyu commented Feb 8, 2024

Description:

While developing with AppFlowy editor, I encountered the following bug in the web version. I have integrated the AppFlowy editor into my app as shown in the image. On the left side, the editor is positioned between a sidebar and a header. This placement causes a displacement of the command menu. The slippage occurs because the menu is inserted relative to its container, rather than being positioned absolutely within the web page.

Screenshot 2024-02-08 at 16 04 57

Expected Behavior:

The command menu should be positioned correctly without any slippage, even when the editor is placed between a sidebar and a header.

Fix:

To resolve this issue, I modified Overlay.of(context) to Overlay.of(context, rootOverlay: true). Additionally, this fix also addresses issue #545.

Please review and consider implementing this fix in the next release. Let me know if you need any further clarification or information. Thank you!

@CLAassistant
Copy link

CLAassistant commented Feb 8, 2024

CLA assistant check
All committers have signed the CLA.

@dagyu dagyu changed the title [BUG FIX] Slash Command Menu bad positioning in Web Version fix: Slash Command Menu bad positioning in Web Version Feb 8, 2024
@dagyu dagyu changed the title fix: Slash Command Menu bad positioning in Web Version fix: Slash command menu bad positioning in Web Version Feb 8, 2024
Copy link

codecov bot commented Feb 18, 2024

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (63844fd) 75.54% compared to head (7d7a081) 75.54%.
Report is 3 commits behind head on main.

Files Patch % Lines
...onent/table_block_component/table_action_menu.dart 0.00% 2 Missing ⚠️
...editor/toolbar/desktop/items/color/color_menu.dart 0.00% 1 Missing ⚠️
...bile_floating_toolbar/mobile_floating_toolbar.dart 0.00% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #709   +/-   ##
=======================================
  Coverage   75.54%   75.54%           
=======================================
  Files         297      297           
  Lines       13707    13707           
=======================================
  Hits        10355    10355           
  Misses       3352     3352           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@LucasXu0
Copy link
Collaborator

@dagyu Thanks for your contribution. LGTM.

@LucasXu0 LucasXu0 merged commit 763459b into AppFlowy-IO:main Feb 18, 2024
9 of 11 checks passed
q200892907 added a commit to q200892907/appflowy-editor that referenced this pull request Feb 19, 2024
* main:
  chore: upgrade flutter version to 3.19.0 (AppFlowy-IO#719)
  fix: the positioning of the slash command menu in the web version (AppFlowy-IO#709)
  fix: unable to export image block in markdown format (AppFlowy-IO#713)
  feat: debounce on word count service (AppFlowy-IO#711)
  feat: on demand word count without listening (AppFlowy-IO#710)
  feat: support selection counters (AppFlowy-IO#706)
  feat: word counter service (AppFlowy-IO#705)
  chore: bump version 2.3.2
  chore: update Chinese i18n (AppFlowy-IO#698)
  fix: fix checkbox not work as expected in html module. (AppFlowy-IO#700)
  chore: revert ime changes (AppFlowy-IO#701)
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.

None yet

3 participants