Bug 274700

Summary:

Korean Composition Events Not Triggered on macOS and iOS Safari

Product:

WebKit

Reporter:

Hyungu Kang <gusrn1423>

Component:

HTML Editing

Assignee:

Nobody <webkit-unassigned>

Status:

NEW

Severity:

Normal

CC:

ap, karlcow, webkit-bug-importer, wenson_hsieh

Priority:

Keywords:

InRadar

Version:

Safari 17

Hardware:

All

OS:

iOS 17

Attachments:

Description	Flags
Compares Japanese and Korean input events	none
Chrome-Safari-comparison	none

Hyungu Kang

Reported 2024-05-24 19:39:28 PDT

Created attachment 471509 [details] Compares Japanese and Korean input events Test Environment: • macOS: Version 14.4.1 • Safari: Version 17.4.1 (19618.1.15.11.14) • iPhone: iOS 17.4.1 • Safari: Version 17.4.1 Mobile/15E148 Safari/604.1 Description: - When inputting Korean text, the `compositionstart`, `compositionupdate`, and `compositionend` events are not being triggered as expected. - This issue does not occur with other compositional languages like Japanese. Steps to Reproduce: - Open a text input field in Safari on macOS or iOS. - Switch the keyboard input to Korean. - Type any Korean text using the keyboard. - Observe the sequence of events. Expected Result: - For both Korean and Japanese, the sequence of events should include `compositionstart`, `compositionupdate`, and `compositionend` as text is composed and finalized. Actual Result: - Korean: The sequence of events does not include `compositionstart`, `compositionupdate`, and `compositionend`. - Japanese: The expected composition events (`compositionstart`, `compositionupdate`, `compositionend`) are triggered correctly. Additional Information: - Testing on macOS, you can easily add and switch between different language inputs via Settings > Keyboard > Input Sources. - This bug significantly affects web applications relying on composition events for processing Korean input. Please investigate and address this inconsistency to improve the user experience for Korean language input in Safari on macOS and iOS.

Attachments
Compares Japanese and Korean input events (33.59 KB, image/png) 2024-05-24 19:39 PDT, Hyungu Kang	no flags	Details
Chrome-Safari-comparison (1.16 MB, image/png) 2024-05-27 21:28 PDT, Hyungu Kang	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Alexey Proskuryakov

Comment 1 2024-05-27 10:24:12 PDT

I think that this is expected behavior, given how system Korean input methods work. They do not create an inline input session, so naturally there are no composition events.

Hyungu Kang

Comment 2 2024-05-27 21:28:42 PDT

Created attachment 471524 [details] Chrome-Safari-comparison

Hyungu Kang

Comment 3 2024-05-27 21:31:39 PDT

I am attaching images of the test results for the same input in both Chrome and Safari. https://bug-274700-attachments.webkit.org/attachment.cgi?id=471524 The tests were conducted on the following site: https://w3c.github.io/uievents/tools/key-event-viewer.html

Radar WebKit Bug Importer

Comment 4 2024-05-31 19:40:16 PDT

<rdar://problem/129094152>

Note You need to log in before you can comment on or make changes to this bug.