Re: [w3c/selection-api] Selection.modify() taking optional strings doesn't make sense to me (Issue #346) from Anne van Kesteren on 2025-03-03 (public-webapps-github@w3.org from March 2025)

From: Anne van Kesteren <notifications@github.com>
Date: Mon, 03 Mar 2025 03:44:13 -0800
To: w3c/selection-api <selection-api@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/selection-api/issues/346/2694100075@github.com>

annevk left a comment (w3c/selection-api#346)

WebKit used to not validate the number of arguments. I suspect this originates from that era.

It also seems like unusual behavior to have ASCII case-insensitive matching for arguments. That makes me a bit less inclined to try and fix it up. Clarifying it and maybe adding a console warning seems reasonable though.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/346#issuecomment-2694100075
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/selection-api/issues/346/2694100075@github.com>

Received on Monday, 3 March 2025 11:44:17 UTC