@@ -3,18 +3,8 @@ Group: WHATWG
3
3
H1: Web IDL
4
4
Shortname: webidl
5
5
Text Macro: TWITTER webidl
6
- Abstract: This document defines an interface definition language, Web IDL,
7
- Abstract: that can be used to describe interfaces that are intended to be
8
- Abstract: implemented in web browsers. Web IDL is an IDL variant with a number
9
- Abstract: of features that allow the behavior of common script objects in
10
- Abstract: the web platform to be specified more readily. How interfaces
11
- Abstract: described with Web IDL correspond to constructs within ECMAScript
12
- Abstract: execution environments is also detailed in this document.
13
- Abstract: It is expected that this document acts
14
- Abstract: as a guide to implementors of already-published specifications,
15
- Abstract: and that newly published specifications reference this
16
- Abstract: document to ensure conforming implementations of interfaces
17
- Abstract: are interoperable.
6
+ Abstract: This standard defines an interface definition language, Web IDL, that can be used to describe interfaces that
7
+ Abstract: are intended to be implemented in web browsers.
18
8
Translation: ja https://triple-underscore.github.io/WebIDL-ja.html
19
9
Complain About: accidental-2119 no
20
10
</pre>
@@ -377,28 +367,17 @@ urlPrefix: https://tc39.es/proposal-resizablearraybuffer/; spec: RESIZABLE-BUFFE
377
367
378
368
<i>This section is informative.</i>
379
369
380
- Technical reports published by the W3C that include programming
381
- language interfaces have typically been described using the
382
- Object Management Group’s Interface Definition Language (IDL)
383
- [[OMGIDL]]. The IDL provides a means to
384
- describe these interfaces in a language independent manner. Usually,
385
- additional language binding appendices are included in such
386
- documents which detail how the interfaces described with the IDL
387
- correspond to constructs in the given language.
388
-
389
- However, the bindings in these specifications for the language most
390
- commonly used on the web, ECMAScript, are consistently specified with
391
- low enough precision as to result in interoperability issues. In
392
- addition, each specification must describe the same basic information,
393
- such as DOM interfaces described in IDL corresponding to properties
394
- on the ECMAScript global object, or the {{unsigned long}} IDL type mapping to the Number
395
- type in ECMAScript.
396
-
397
- This specification defines an IDL language similar to OMG IDL
398
- for use by specifications that define interfaces for Web APIs. A number of extensions are
399
- given to the IDL to support common functionality that previously must
400
- have been written in prose. In addition, precise language bindings
401
- for the ECMAScript language are given.
370
+ This standard defines an interface definition language, Web IDL, that can be used to describe
371
+ interfaces that are intended to be implemented in web browsers. Web IDL is an IDL variant with a
372
+ number of features that allow the behavior of common script objects in the web platform to be
373
+ specified more readily. How interfaces described with Web IDL correspond to constructs within
374
+ ECMAScript execution environments is also detailed here.
375
+
376
+ Concretely, Web IDL provides a syntax for specifying the surface APIs of web platform objects, as
377
+ well as ECMAScript bindings that detail how those APIs manifest as ECMAScript constructs. This
378
+ ensures common tasks, such as installing global properties, processing numeric inputs, or exposing
379
+ iteration behavior, remain uniform across web platform specifications: such specifications describe
380
+ their interfaces using Web IDL, and then use prose to specify API-specific details.
402
381
403
382
404
383
<h2 id="idl">Interface definition language</h2>
@@ -6042,12 +6021,6 @@ The {{DOMString}} type corresponds to
6042
6021
the set of all possible sequences of [=code units=].
6043
6022
Such sequences are commonly interpreted as UTF-16 encoded strings [[!RFC2781]]
6044
6023
although this is not required.
6045
- While {{DOMString}} is defined to be
6046
- an OMG IDL boxed [=sequence type|sequence=]<{{unsigned short}}> valuetype
6047
- in [[DOM-LEVEL-3-CORE/core#ID-C74D1578|DOM Level 3 Core §The DOMString Type]],
6048
- this document defines {{DOMString}} to be an intrinsic type
6049
- so as to avoid special casing that sequence type
6050
- in various situations where a string is required.
6051
6024
6052
6025
Note: Note also that <emu-val>null</emu-val>
6053
6026
is not a value of type {{DOMString}}.
0 commit comments