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(richtext-lexical): z-index issues #4570

Merged
merged 1 commit into from
Dec 20, 2023

Conversation

AlessioGr
Copy link
Member

@AlessioGr AlessioGr commented Dec 20, 2023

Description

  1. Slash menu of first editor is hidden behind second editor content
    Screenshot 2023-12-20 at 14 58 35@2x

  2. Same issue for a Select field inside of a block

  • I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

  • Chore (non-breaking change which does not add functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Change to the templates directory (does not affect core functionality)
  • Change to the examples directory (does not affect core functionality)
  • This change requires a documentation update

Checklist:

  • I have added tests that prove my fix is effective or that my feature works
  • Existing test suite passes locally with my changes
  • I have made corresponding changes to the documentation

@AlessioGr AlessioGr added the plugin: richtext-lexical @payloadcms/richtext-lexical label Dec 20, 2023
@AlessioGr AlessioGr merged commit 8015e99 into main Dec 20, 2023
28 of 29 checks passed
@AlessioGr AlessioGr deleted the fix/richtext-lexical-z-index-issues branch December 20, 2023 14:10
AlessioGr added a commit that referenced this pull request Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plugin: richtext-lexical @payloadcms/richtext-lexical
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant