- From: Anne van Kesteren <notifications@github.com>
- Date: Thu, 04 Apr 2024 06:51:16 -0700
- To: whatwg/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/webidl/pull/1392/review/1979986937@github.com>
@annevk commented on this pull request. > @@ -11056,6 +11091,21 @@ allowed. The security check takes the following three inputs: Note: The HTML Standard defines how a security check is performed. [[!HTML]] +Certain algorithms are defined to +<dfn id="dfn-validate-the-string-in-context" export>validate the string in context</dfn> on a given +value. This check is used to determine whether a given value +is appropriate for its {{StringContext}}. This validation takes the following four inputs: + +1. the [=platform object=] on + which the operation invocation or attribute access is being done, +1. the value to validate, +1. the {{StringContext}} [=identifier=], and +1. the [=identifier=] of the operation or attribute. + +The algorithm returns an ECMAScript value, or [=JavaScript/throws=] a <l spec=ecmascript>{{TypeError}}</l>. + +Note: The HTML Standard defines how the validation is performed. [[!HTML]] If you don't expect the code path to be used then you need to use Assert. But given @petervanderbeken's comments I'm starting to wonder if having this as an extended attribute is a good after all. I guess I'm back at https://github.com/whatwg/webidl/pull/841#issuecomment-590988522 where I wonder if we should put most of the complexity in the specification algorithms. cc @domenic @koto -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/webidl/pull/1392#discussion_r1551733549 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/webidl/pull/1392/review/1979986937@github.com>
Received on Thursday, 4 April 2024 13:51:19 UTC