-
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
Rich text: run input rules after composition end #33416
Conversation
a1f8ac0
to
5a29414
Compare
5a29414
to
e17f5af
Compare
Size Change: +35 B (0%) Total Size: 1.07 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wonderful.
@@ -451,4 +451,19 @@ describe( 'RichText', () => { | |||
await page.keyboard.press( 'ArrowLeft' ); | |||
expect( await page.$( blockToolbarSelector ) ).toBe( null ); | |||
} ); | |||
|
|||
it( 'should run input rules after composition end', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recommend adding a comment here about Puppeteer's lack of support for composition events and a link to puppeteer/puppeteer#4981, so that we can track it and as justification for the fact that this isn't a user-centred test.
Works for me, thanks for the fix. |
Description
Fixes #33004.
Introduced by #31752 (thanks @mcsf).
Input rules used to run after
compositionend
, but that's no longer the case.It's not possible to make an e2e test for this because Puppeteer doesn't have any APIs around it. I filed a request in the past: puppeteer/puppeteer#4981.
How has this been tested?
Change to a keyboard with
`
as a dead key and try to wrap text in it to wrap it in a code element.Screenshots
Types of changes
Checklist:
*.native.js
files for terms that need renaming or removal).