details要素summary要素a element to define a commandbutton element to define a commandinput element to define a commandoption element to define a commandaccesskey attribute
on a legend element to define a commandaccesskey
attribute to define a command on other elementsdialog要素details要素Support: detailsChrome for Android 69+Chrome 12+iOS Safari 6.0+UC Browser for Android 11.8+Firefox 49+IE NoneSafari 6+Edge NoneOpera 15+Samsung Internet 4+Android Browser 4+
Source: caniuse.com
summary要素に続くフローコンテンツ。open — detailsが可視かどうか[Exposed =Window ,
HTMLConstructor ]
interface HTMLDetailsElement : HTMLElement {
[CEReactions ] attribute boolean open ;
};details要素は、ユーザーが追加情報やコントロールを得ることができるディスクロージャーウィジェットを表す。
details要素は、脚注には適さない。脚注をマークアップする方法の詳細については、脚注のセクションを参照のこと。
要素の子である最初のsummary要素がもしあれば、detailsの要約または凡例を表す。If there is no child summary element, the user agent should provide its own legend (e.g. "Details").
要素のコンテンツの残り部分は、追加情報やコントロールを表す。
openコンテンツ属性は、真偽属性である。存在する場合、この属性は要約と追加情報の両方がユーザーに表示されることを示す。属性が存在しない場合、要約のみが表示されるようになる。
When the element is created, if the attribute is absent, the additional information should be hidden; if the attribute is present, that information should be shown. Subsequently, if the attribute is removed, then the information should be hidden; if the attribute is added, the information should be shown.
The user agent should allow the user to request that the additional information be shown or
hidden. To honor a request for the details to be shown, the user agent must set the open attribute on the element to the empty string. To honor a
request for the information to be hidden, the user agent must remove the open attribute from the element.
This ability to request that additional information be shown or hidden
may simply be the activation behavior of the appropriate
summary element, in the case such an element exists. However, if no such element
exists, user agents can still provide this ability through some other user interface
affordance.
Whenever the open attribute is added to or removed from
a details element, the user agent must queue a task that runs the
following steps, which are known as the details notification task steps, for this
details element:
If another task has been queued to run the details notification task steps for this
details element, then return.
When the open attribute is toggled
several times in succession, these steps essentially get coalesced so that only one event is
fired.
Fire an event named toggle at the details element.
このタスクのためのタスクソースは、DOM操作タスクソースである。
open IDL属性は、openコンテンツ属性を反映しなければならない。
次の例は、details要素が進捗報告書で技術的な詳細を非表示にするために使用される様子を示す。
< section class = "progress window" >
< h1 > Copying "Really Achieving Your Childhood Dreams"</ h1 >
< details >
< summary > Copying... < progress max = "375505392" value = "97543282" ></ progress > 25%</ summary >
< dl >
< dt > Transfer rate:</ dt > < dd > 452KB/s</ dd >
< dt > Local filename:</ dt > < dd > /home/rpausch/raycd.m4v</ dd >
< dt > Remote filename:</ dt > < dd > /var/www/lectures/raycd.m4v</ dd >
< dt > Duration:</ dt > < dd > 01:16:27</ dd >
< dt > Color profile:</ dt > < dd > SD (6-1-6)</ dd >
< dt > Dimensions:</ dt > < dd > 320×240</ dd >
</ dl >
</ details >
</ section > 以下は、details要素がデフォルトで一部のコントロールを非表示にするために使用できる様子を示す：
< details >
< summary >< label for = fn > Name & Extension:</ label ></ summary >
< p >< input type = text id = fn name = fn value = "Pillar Magazine.pdf" >
< p >< label >< input type = checkbox name = ext checked > Hide extension</ label >
</ details > これは、ユーザーがそれぞれを開くことができる機能とともに、見出しの小さなセットにフィールドのセットを折りたたむことができるよう、リスト内の他のdetailsとともにこれを使用できる。
これらの例において、要約はコントロールが変更できるものをまとめたものであり、理想に満たない実際値ではない。
ユーザーがコントロールを操作するために自動的にopen属性が追加および削除されるので、この属性の状態に基づく異なる、この属性CSSで要素に使用できる。Here, a style sheet is used to animate the color of the summary when the element is opened or closed:
< style >
details > summary { transition : color 1 s ; color : black ; }
details [ open ] > summary { color : red ; }
</ style >
< details >
< summary > Automated Status: Operational</ summary >
< p > Velocity: 12m/s</ p >
< p > Direction: North</ p >
</ details > summary要素details要素の最初の子として。HTMLElementを使用する。summary要素は、もしあれば、summary要素の親details要素に属する残りの内容のキャプションまたは凡例を表す。
The activation behavior of summary elements is to run the following
steps:
If this summary element has no parent node, then return.
Let parent be this summary element's parent node.
If parent is not a details element, then return.
If parent's first summary element child is not this
summary element, then return.
If the open attribute is present on
parent, then remove it.
Otherwise, set parent's
open attribute to the empty string.
This will then run the details notification task steps.
コマンドは、メニュー項目、ボタン、リンクの背後に抽象化したものである。一度コマンドが定義されると、インターフェイスの他の部分は、Disabled状態のようなファセットを共有するために単一の機能へ多くのアクセスポイントを許可し、同じコマンドを参照できる。
コマンドは、次のファセットを持つように定義される：
ユーザーエージェントは、次の条件に一致するコマンドを公開してもよい：
ユーザーエージェントは、ユーザーにこれらのキーを通知するための方法として、アクセスキーを持つコマンドのために特にこれを行うことが推奨される。
たとえば、そのようなコマンドは、ユーザーエージェントのメニューバーにリストされるかもしれない。
a element to define a commandAn a element with an href attribute defines a command.
The Label of the command is the string given by the
element's textContent IDL attribute.
The Access Key of the command is the element's assigned access key, if any.
The of the command is true (hidden) if the element has a attribute, and false otherwise.
The Disabled State facet of the command is true if the element or one of its ancestors is inert, and false otherwise.
The Action of the command is to fire a click event at the element.
button element to define a commandA button element always defines a
command.
The Label, Access Key, , and Action facets of the command are determined as for a elements (see the previous section).
The Disabled State of the command is true if the element or one of its ancestors is inert, or if the element's disabled state is set, and false otherwise.
input element to define a commandAn input element whose type attribute is in
one of the Submit Button, Reset Button, Image
Button, Button, Radio Button, or Checkbox states defines a
command.
The Label of the command is determined as follows:
If the type attribute is in one of the
Submit Button, Reset Button, Image
Button, or Button states, then the
Label is the string given by the
value attribute, if any, and a UA-dependent,
locale-dependent value that the UA uses to label the button itself if the attribute is
absent.
Otherwise, if the element is a labeled control, then the
Label is the string given by the
textContent of the first label element in tree order
whose labeled control is the element in question. (In DOM terms, this is the
string given by element.labels[0].textContent.)
Otherwise, if the value attribute is present, then
the Label is the value of that attribute.
Otherwise, the Label is the empty string.
The Access Key of the command is the element's assigned access key, if any.
The of the command is true (hidden) if the element has a attribute, and false otherwise.
The Disabled State of the command is true if the element or one of its ancestors is inert, or if the element's disabled state is set, and false otherwise.
The Action of the command is to fire a click event at the element.
option element to define a commandAn option element with an ancestor select element and either no value attribute or a value
attribute that is not the empty string defines a command.
The Label of the command is the value of the
option element's label attribute, if there is
one, or else the value of option element's textContent IDL attribute,
with ASCII whitespace stripped and
collapsed.
The Access Key of the command is the element's assigned access key, if any.
The of the command is true (hidden) if the element has a attribute, and false otherwise.
The Disabled State of the command is true if
the element is disabled, or if its nearest ancestor
select element is disabled, or if it or one
of its ancestors is inert, and false otherwise.
If the option's nearest ancestor select element has a multiple attribute, the Action of the command is to toggle the option element. Otherwise, the Action is to pick the option element.
accesskey attribute
on a legend element to define a commandA legend element defines a command if all of
the following are true:
It has an assigned access key.
It is a child of a fieldset element.
Its parent has a descendant that defines a command
that is neither a label element nor a legend element. This element,
if it exists, is the legend element's accesskey
delegatee.
The Label of the command is the string given by the
element's textContent IDL attribute.
The Access Key of the command is the element's assigned access key.
The , Disabled State, and Action facets of the command are the same as the respective
facets of the legend element's accesskey delegatee.
In this example, the legend element specifies an accesskey, which, when activated, will delegate to the
input element inside the legend element.
< fieldset >
< legend accesskey = p >
< label > I want < input name = pizza type = number step = 1 value = 1 min = 0 >
pizza(s) with these toppings</ label >
</ legend >
< label >< input name = pizza-cheese type = checkbox checked > Cheese</ label >
< label >< input name = pizza-ham type = checkbox checked > Ham</ label >
< label >< input name = pizza-pineapple type = checkbox > Pineapple</ label >
</ fieldset > accesskey
attribute to define a command on other elementsAn element that has an assigned access key defines a command.
If one of the earlier sections that define elements that define commands define that this element defines a command, then that section applies to this element, and this section does not. Otherwise, this section applies to that element.
The Label of the command depends on the element. If
the element is a labeled control, the textContent of the first
label element in tree order whose labeled control is the
element in question is the Label (in DOM terms, this is
the string given by element.labels[0].textContent). Otherwise,
the Label is the textContent of the element
itself.
The Access Key of the command is the element's assigned access key.
The of the command is true (hidden) if the element has a attribute, and false otherwise.
The Disabled State of the command is true if the element or one of its ancestors is inert, and false otherwise.
The Action of the command is to run the following steps:
click event at the element.dialog要素Support: dialogChrome for Android 69+Chrome 37+iOS Safari NoneUC Browser for Android 11.8+Firefox NoneIE NoneOpera Mini NoneSafari NoneEdge NoneOpera 24+Samsung Internet 4+Android Browser 67+
Source: caniuse.com
open — ダイアログボックスが見えるかどうか[Exposed =Window ,
HTMLConstructor ]
interface HTMLDialogElement : HTMLElement {
[CEReactions ] attribute boolean open ;
attribute DOMString returnValue ;
[CEReactions ] void show ();
[CEReactions ] void showModal ();
[CEReactions ] void close (optional DOMString returnValue );
};dialog要素は、たとえばダイアログボックス、インスペクタ、またはウィンドウなどのタスクを実行するために、ユーザーが操作するアプリケーションの一部を表す。
open属性は、真偽属性である。指定される場合、dialog要素はアクティブであり、ユーザーが操作できることを示す。
A dialog element without an open attribute specified should not be shown to the user. この要件は、スタイルレイヤーを通して間接的に実装されてもよい。For example, user agents that support the suggested default rendering implement this requirement using the CSS rules described in the rendering section.
open属性を削除すると、通常ダイアログが非表示になる。しかし、そのようにすると、いくつかの奇妙な追加の結果となる：
closeイベントは発火しない。
The close() method, and any user-agent provided cancelation interface, will no longer be able
to close the dialog.
If the dialog was shown using its showModal()
method, the Document will still be blocked.
これらの理由から、open属性を手動で削除しない方が一般的には良い方法である。代わりに、ダイアログを閉じるためにclose()メソッドを使用する、または非表示にするために属性を使用する。
tabindex属性は、dialog要素で指定されてはならない。
show()dialog要素を表示する。
showModal()dialog要素を表示し、一番上のモーダルダイアログにする。
この方法は、autofocus属性を履行する。
close( [ result ] )dialog要素を閉じる。
引数が与えられた場合、戻り値を提供する。
returnValue [ = result ]dialogの戻り値を返す。
戻り値を更新する設定が可能である。
When the show() method is invoked, the user
agent must run the following steps:
If the element already has an open attribute, then
return.
Add an open attribute to the dialog
element, whose value is the empty string.
Set the dialog to the normal alignment mode.
Run the dialog focusing steps for the dialog element.
When the showModal() method is invoked,
the user agent must run the following steps:
Let subject be the dialog element on which the method was
invoked.
If subject already has an open
attribute, then throw an "InvalidStateError" DOMException.
If subject is not connected, then throw an
"InvalidStateError" DOMException.
Add an open attribute to subject, whose value is the empty string.
Set the dialog to the centered alignment mode.
Let subject's node document be blocked by the modal dialog subject.
If subject's node document's top layer does not already contain subject, then add subject to subject's node document's top layer.
Run the dialog focusing steps for subject.
The dialog focusing steps for a dialog element subject are as follows:
If subject is inert, return.
Let control be the first descendant element of subject, in tree
order, that is not inert and has the autofocus attribute specified.
If there isn't one, then let control be the first non-inert descendant element of subject, in tree order.
If there isn't one of those either, then let control be subject.
Run the focusing steps for control.
If at any time a dialog element is removed from a Document, then if that dialog is in that
Document's top layer, it must be removed from it.
When the close() method is invoked, the user
agent must close the dialog that the method was invoked on. If the method was invoked
with an argument, that argument must be used as the return value; otherwise, there is no return
value.
When a dialog element subject is to be closed, optionally with a return value result, the user agent
must run the following steps:
If subject does not have an open
attribute, then return.
Remove subject's open
attribute.
If the argument result was provided, then set the returnValue attribute to the value of result.
Queue a task to fire an event named
close at subject.
The returnValue IDL attribute, on
getting, must return the last value to which it was set. On setting, it must be set to the new
value. When the element is created, it must be set to the empty string.
Canceling dialogs: When Document is
blocked by a modal dialog dialog, user agents may provide a user interface
that, upon activation, queues a task to run these steps:
Let close be the result of firing an
event named cancel at dialog, with the cancelable attribute initialized to true.
If close is true and dialog has an open attribute, then close the dialog with no
return value.
An example of such a UI mechanism would be the user pressing the "Escape" key.
A dialog element is in one of two modes: normal alignment or
centered alignment. When a dialog element is created, it must be placed in
the normal alignment mode. In this mode, normal CSS requirements apply to the
element. The centered alignment mode is only used for dialog elements
that are in the top layer. [FULLSCREEN] [CSS]
When an element subject is placed in centered alignment mode, and when it is in that mode and has new rendering boxes created, the user agent must set up the element such that its static position of the edge that corresponds to subject's parent's block-start edge, for the purposes of calculating the used value of the appropriate box offset property ('top', 'right', 'bottom', or 'left'), is the value that would place the element's margin edge on the side that corresponds to subject's parent's block-start side as far from the same-side edge of the viewport as the element's opposing side margin edge from that same-side edge of the viewport, if the element's dimension ('width' or 'height') in subject's parent's block flow direction is less than the same-axis dimension of the viewport, and otherwise is the value that would place the element's margin edge on the side that corresponds to subject's parent's block-start side at the same-side edge of the viewport.
If there is a dialog element with centered alignment and that is
being rendered when its browsing context changes viewport
dimensions (as measured in CSS pixels), or when this
dialog element's parent changes block flow direction, then the user
agent must recreate the element's boxes, recalculating its edge that corresponds to this
dialog element's parent's block-start edge as in the previous
paragraph.
This static position of a dialog element's edge with centered
alignment must remain the element's static position of that edge until its boxes are
recreated. (The element's static position is only used in calculating the used value
of the appropriate box offset property ('top', 'right',
'bottom', or 'left') in certain situations; it's not used, for instance,
to position the element if its 'position' property is set to
'static'.)
User agents in visual interactive media should allow the user to pan the viewport
to access all parts of a dialog element's border box, even if the
element is larger than the viewport and the viewport would otherwise not
have a scroll mechanism (e.g. because the viewport's 'overflow' property
is set to ).
open IDL属性は、openコンテンツ属性を反映しなければならない。
このダイアログボックスは、いくつかの小さなプリントを持つ。strong要素は、より重要な部分にユーザーの注意を引くために使用される。
< dialog >
< h1 > Add to Wallet</ h1 >
< p >< strong >< label for = amt > How many gold coins do you want to add to your wallet?</ label ></ strong ></ p >
< p >< input id = amt name = amt type = number min = 0 step = 0.01 value = 100 ></ p >
< p >< small > You add coins at your own risk.</ small ></ p >
< p >< label >< input name = round type = checkbox > Only add perfectly round coins </ label ></ p >
< p >< input type = button onclick = "submit()" value = "Add Coins" ></ p >
</ dialog >