[WebIDL] スタイル編集

IDL 用のスタイルを他の仕様と共通化

Author: triple-underscore

WebIDL-JS-ja.html

@@ -6,32 +6,20 @@
 
 <style>
 
-:root {
-	--code-color: light-dark( hsl(12 100% 33%), hsl(12 100% 73%) );
-	--idl-color: light-dark( hsl(231 100% 23%), hsl(231 100% 83%) );
-	--idl-bg-color: light-dark( hsl(204 80% 95%), hsl(204 80% 13%) );
-}
-
-code {
-	color: var(--code-color);
-}
-
 /* 拡張d属性 */
 .xattr {
 	font-family: monospace0, monospace;
 	color: var(--text-color-1);
 }
 
-/* IDL, JavaScript 型／値 */
+/* IDL */
 
 .idltype,
 .idlmember,
 .idlvalue {
-	font-family: monospace0, monospace;
-	color: var(--idl-color);
 }
 
-/* JavaScript */
+/* JS */
 .js-property,
 .js-error {
 	color: var(--js-color);
@@ -42,16 +30,6 @@
 	text-decoration: underline;
 }
 
-	/* コードブロック */
-pre {
-	margin: 0.5em 0 0.5em 0.5em;
-	padding: 0.5em 1em;
-}
-
-pre.webidl {
-	background: var(--idl-bg-color);
-}
-
 /* 引用例 */
 blockquote {
 	border: dashed thin var(--N-color);
@@ -4132,7 +4110,7 @@ <h5 title="Creating a sequence from an iterable">3.2.21.1. 可反復から連列
 The following interface defines an attribute of a sequence type as well as an operation with an argument of a sequence type.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Canvas {
 
@@ -5829,7 +5807,7 @@ <h5 title="Examples">3.2.24.2. 例</h5>
 delay is an operation that returns a promise that will be fulfilled in a number of milliseconds. It illustrates how simply you can resolve a promise, with one line of prose.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 interface I {
   Promise&lt;undefined&gt; delay(unrestricted double ms);
 };
@@ -5914,7 +5892,7 @@ <h5 title="Examples">3.2.24.2. 例</h5>
 The validatedDelay operation is much like the delay function, except it will validate its arguments. This shows how to use rejected promises to signal immediate failure before even starting any asynchronous operations.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 interface I {
   Promise&lt;undefined&gt; validatedDelay(unrestricted double ms);
 };
@@ -6006,7 +5984,7 @@ <h5 title="Examples">3.2.24.2. 例</h5>
 addDelay is an operation that adds an extra number of milliseconds of delay between promise settling and the returned promise settling.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 interface I {
   Promise&lt;any&gt; addDelay(Promise&lt;any&gt; promise, unrestricted double ms);
 };
@@ -6148,7 +6126,7 @@ <h5 title="Examples">3.2.24.2. 例</h5>
 environment.ready is an attribute that signals when some part of some environment, e.g. a DOM document, becomes "ready". It illustrates how to encode environmental asynchronicity.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 interface Environment {
   readonly attribute Promise&lt;undefined&gt; ready;
 };
@@ -6270,7 +6248,7 @@ <h5 title="Examples">3.2.24.2. 例</h5>
 addBookmark is an operation that requests that the user add the current web page as a bookmark. It’s drawn from some iterative design work and illustrates a more real-world scenario of appealing to environmental asynchrony, as well as immediate rejections.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 interface I {
   Promise&lt;undefined&gt; addBookmark();
 };
@@ -6394,7 +6372,7 @@ <h5 title="Examples">3.2.24.2. 例</h5>
 Several places in [SERVICE-WORKERS] use get a promise to wait for all. batchRequest illustrates a simplified version of one of their uses. It takes as input a sequence of URLs, and returns a promise for a sequence of Response objects created by fetching the corresponding URL. If any of the fetches fail, it will return a promise rejected with that failure.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 interface I {
   Promise&lt;sequence&lt;Response&gt;&gt; batchRequest(sequence&lt;USVString&gt; urls);
 };
@@ -8158,7 +8136,7 @@ <h4>3.3.2. `AllowShared^x</h4>
 The following IDL fragment demonstrates the possible combinations of the [AllowResizable] and [AllowShared] extended attribute:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface ExampleBufferFeature {
   undefined writeInto(ArrayBufferView %dest);
@@ -8275,7 +8253,7 @@ <h4>3.3.3. `Clamp^x</h4>
 In the following IDL fragment, two operations are declared that take three octet arguments; one uses the [Clamp] extended attribute on all three arguments, while the other does not:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface GraphicsContext {
   undefined setColor(octet %red, octet %green, octet %blue);
@@ -8548,7 +8526,7 @@ <h4>3.3.5. `Default^x</h4>
 As an example, the [Default] extended attribute is suitable for use on toJSON regular operations:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Animal {
   attribute DOMString name;
@@ -8684,7 +8662,7 @@ <h4>3.3.6. `EnforceRange^x</h4>
 In the following IDL fragment, two operations are declared that take three octet arguments; one uses the [EnforceRange] extended attribute on all three arguments, while the other does not:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface GraphicsContext {
   undefined setColor(octet %red, octet %green, octet %blue);
@@ -9400,7 +9378,7 @@ <h4>3.3.7. `Exposed^x</h4>
 The following IDL fragment shows how that might be achieved:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window, Global=Window]
 interface Window {
   /* ... */
@@ -9748,7 +9726,7 @@ <h4>3.3.8. `Global^x</h4>
 The Window interface exposes frames as properties on the Window object. Since the Window object also serves as the JavaScript global object, variable declarations or assignments to the named properties will result in them being replaced by the new value. Variable declarations for attributes will not create a property that replaces the existing one.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window, Global=Window]
 interface Window {
   getter object【！any】 (DOMString %name);
@@ -9886,7 +9864,7 @@ <h4>3.3.9. `NewObject^x</h4>
 As an example, this extended attribute is suitable for use on the createElement() operation on the Document interface, since a new object is always returned when it is called. [DOM]
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Document : Node {
   [NewObject] Element createElement(DOMString %localName);
@@ -10022,7 +10000,7 @@ <h4>3.3.10. `PutForwards^x</h4>
 The following IDL fragment defines interfaces for names and people. The [PutForwards] extended attribute is used on the name attribute of the Person interface to indicate that assignments to that attribute result in assignments to the full attribute of the Person object:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Name {
   attribute DOMString full;
@@ -10135,7 +10113,7 @@ <h4>3.3.11. `Replaceable^x</h4>
 The following IDL fragment defines an interface with an operation that increments a counter, and an attribute that exposes the counter’s value, which is initially 0:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Counter {
   [Replaceable] readonly attribute unsigned long value;
@@ -10251,7 +10229,7 @@ <h4>3.3.12. `SameObject^x</h4>
 As an example, this extended attribute is suitable for use on the implementation attribute on the Document interface since the same object is always returned for a given Document object. [DOM]
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Document : Node {
   [SameObject] readonly attribute DOMImplementation implementation;
@@ -10375,7 +10353,7 @@ <h4>3.3.13. `SecureContext^x</h4>
 The following IDL fragment defines an interface with one operation that is executable from all contexts, and two which are executable only from secure contexts.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface ExampleFeature {
   /* <span class="comment">
@@ -10520,7 +10498,7 @@ <h4>3.3.14. `Unscopable^x</h4>
 For example, with the following IDL:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Thing {
   undefined f();
@@ -10678,7 +10656,7 @@ <h4>3.4.1. `LegacyFactoryFunction^x</h4>
 The following IDL defines an interface that uses the [LegacyFactoryFunction] extended attribute.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window,
  LegacyFactoryFunction=Audio(DOMString %src)]
 interface HTMLAudioElement : HTMLMediaElement {
@@ -10797,7 +10775,7 @@ <h4>3.4.2. `LegacyLenientSetter^x</h4>
 The following IDL fragment defines an interface that uses the [LegacyLenientSetter] extended attribute.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Example {
   [LegacyLenientSetter] readonly attribute DOMString x;
@@ -10890,7 +10868,7 @@ <h4>3.4.3. `LegacyLenientThis^x</h4>
 The following IDL fragment defines an interface that uses the [LegacyLenientThis] extended attribute.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Example {
   [LegacyLenientThis] attribute DOMString x;
@@ -11007,7 +10985,7 @@ <h4>3.4.4. `LegacyNamespace^x</h4>
 The following IDL fragment defines a namespace and an interface which uses [LegacyNamespace] to be defined inside of it.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]【！＊原文抜け】
 namespace Foo { };
 
@@ -11083,7 +11061,7 @@ <h4>3.4.5. `LegacyNoInterfaceObject^x</h4>
 The following IDL fragment defines two interfaces, one whose interface object is exposed on the JavaScript global object, and one whose isn’t:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Storage {
   undefined addEntry(unsigned long %key, any %value);
@@ -11185,7 +11163,7 @@ <h4>3.4.6. `LegacyNullToEmptyString^x</h4>
 The following IDL fragment defines an interface that has one attribute whose type has the extended attribute, and one operation whose argument’s type has the extended attribute:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Dog {
   attribute DOMString name;
@@ -11319,7 +11297,7 @@ <h4>3.4.7. `LegacyOverrideBuiltIns^x</h4>
 The following IDL fragment defines two interfaces, one that has a named property getter and one that does not.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface StringMap {
   readonly attribute unsigned long length;
@@ -11447,7 +11425,7 @@ <h4>3.4.8. `LegacyTreatNonObjectAsNull^x</h4>
 The following IDL fragment defines an interface that has one attribute whose type is a [LegacyTreatNonObjectAsNull]-annotated callback function and another whose type is a callback function without the extended attribute:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 callback OccurrenceHandler = undefined (DOMString %details);
 
 [LegacyTreatNonObjectAsNull]
@@ -11655,7 +11633,7 @@ <h4>3.4.10. `LegacyUnforgeable^x</h4>
 For example, the following is disallowed:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface A1 {
 [LegacyUnforgeable] readonly attribute DOMString x;
@@ -11704,7 +11682,7 @@ <h4>3.4.10. `LegacyUnforgeable^x</h4>
 The following IDL fragment defines an interface that has two attributes, one of which is designated as [LegacyUnforgeable]:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface System {
   [LegacyUnforgeable] readonly attribute DOMString username;
@@ -11847,7 +11825,7 @@ <h4>3.4.11. `LegacyWindowAlias^x</h4>
 The following IDL defines an interface that uses the [LegacyWindowAlias] extended attribute.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window,
  LegacyWindowAlias=WebKitCSSMatrix]
 interface DOMMatrix : DOMMatrixReadOnly {
@@ -13697,7 +13675,7 @@ <h4 title="Interface prototype object">3.7.3. ~ifc原型~obj</h4>
 The interface prototype object of an interface that is defined with the [LegacyNoInterfaceObject] extended attribute will be accessible. For example, with the following IDL:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window,
  LegacyNoInterfaceObject]
 interface Foo {
@@ -15379,7 +15357,7 @@ <h6 title="Default toJSON operation">3.7.7.1.1. 既定の~toJSON演算</h6>
 Only regular attributes of interfaces that declare a toJSON operation with a [Default] extended attribute are included, even if an inherited interface declares such a toJSON operation. For example, consider the following IDL fragment:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface A {
   [Default] object toJSON();
@@ -15438,7 +15416,7 @@ <h6 title="Default toJSON operation">3.7.7.1.1. 既定の~toJSON演算</h6>
 A toJSON operation can also be declared on an interface mixin (or partial interface) and is equivalent to declaring it on the original interface. For example, consider the following IDL fragment:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface D {
   attribute DOMString d;
@@ -22370,7 +22348,7 @@ <h4 title="Creating and throwing exceptions">3.14.3. 例外の作成-法と投
 The above algorithms restrict objects representing exceptions propagating out of a function object to be ones that are associated with the realm of that function object (i.e., the current realm at the time the function executes). For example, consider the IDL:
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface MathUtils {
   /* <span class="comment">
@@ -22451,7 +22429,7 @@ <h4 title="Handling exceptions">3.14.4. 例外の取扱い</h4>
 The following IDL fragment defines two interfaces and an exception. The valueOf attribute on ExceptionThrower is defined to throw an exception whenever an attempt is made to get its value.
 </p>
 
-<pre class="webidl">
+<pre class="idl">
 [Exposed=Window]
 interface Dahut {
   attribute DOMString type;