-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[Details Block] The space key doesn't work (Firefox) #49679
Comments
@gyurmey2 Firefox Version: 111.0.1 (64-bit) f4b24416bed753812c0eb9857b798a01.mp4 |
I think this is a problem unique to Firefox. If I give the Here is the code I used to test: <!DOCTYPE html>
<html lang="ja">
<head>
<meta charset="UTF-8">
<title>Document</title>
</head>
<body>
<details>
<summary><div contenteditable>Editable Details Summary</div></summary>
<p>Details Content</p>
</details>
<script>
document.querySelector('summary').addEventListener('click', function(event) {
console.log( 'clicked!' );
});
</script>
</body>
</html> |
I can reproduce this and I have tried to use different combinations of "KeyUp" instead of "onClick" for the prevent, but I have been unable to solve it. |
Here's the bug report for firefox - https://bugzilla.mozilla.org/show_bug.cgi?id=1822860. It has been triaged and accepted which is good. I'm not sure if we can add any workarounds to RichText, or if we should just wait for the firefox bug to be resolved. It seems like it's being considered a normal priority, but I left a comment asking why that is and if there's a workaround. |
There's a suggestion for a workaround from a Firefox maintainer:
The latter sounds like a good option 👍 |
I am trying to fix in #50540. |
Description
The space key doesn't work when entering text in the "Details Summary" field. This only happens in Firefox browsers.
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
Environment info
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: