- From: drwez <notifications@github.com>
- Date: Tue, 11 Jul 2023 09:08:02 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/uievents/issues/346/1631101854@github.com>
> > (1) typing emoji or other non-BMP characters (2) using a browser with broken charCode for non-BMP and (3) into a web-site that is actively processing keypress.charCode to receive characters. > > Yes, that applies to a lot of situations. It is very common for websites to use event listeners to monitor comment textboxes. For example, Twitter monitors the textbox so it can update the "maximum characters allowed". That's true, but that can (and often is) done using events & fields other than `keypress` and `charCode`. > > it sounds like the single-surrogate DOMStrings are being treated as a complete Unicode code-point, somewhere in rust-dominator > > Incorrect, it is not a dominator bug, it is 100% a browser bug. This was already well established. That bug report is what lead hsivonen to file bug reports against the browsers, which then lead to this spec bug. Yes, I don't think there is any debate that some browsers are currently implementing `input` incorrectly - resolving that for Chromium is tracked at crbug.com/1450498. That's a separate issue from `keypress`, though. > I am well aware of what is going on. Likewise. :) > > and appears to be on Windows, not macOS > > Yes, which is exactly what this bug is about: Chrome and Firefox on Windows are incorrectly generating 2 events when they should generate 1 event. Safari correctly generates 1 event. Again, this bug is specifically about the legacy `keypress` event, and the `charCode` field, for which the web platform spec is non-normative. Historically two `keypress` events have, in the past, in various implementations, been emitted for non-BMP characters - so it can't be said that emitting only one is more (or less) correct. :) -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/346#issuecomment-1631101854 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents/issues/346/1631101854@github.com>
Received on Tuesday, 11 July 2023 16:08:08 UTC