Abstract概要
This specification evolves HTML and its related APIs to ease the
authoring of Web-based applications. Additions include context
menus, a direct-mode graphics canvas, a full duplex client-server
communication channel, more semantics, audio and video, various
features for offline Web applications, sandboxed iframes, and scoped
styling. Heavy emphasis is placed on keeping the language backwards
compatible with existing legacy user agents and on keeping user
agents backwards compatible with existing legacy documents.この仕様書は、 Web ベースのアプリケーションの制作の簡単化のために
HTML やそれに関係する API を拡張します。
新たに文脈メニュー、直接モード図形画布、全二重クライアント鯖型通信路、
更なる意味、音声や動画、オフライン Web アプリケーションのための各種機能、
砂箱化 iframe、範囲指定スタイル付けなどの機能を追加します。
また、既存の旧来の利用者エージェントに対する言語の後方互換性を維持し、
既存の旧来の文書に対する利用者エージェントの後方互換性を維持することに特に留意しています。
Status of this documentこの文書の状態
This is a work in progress! This document is
changing on a daily if not hourly basis in response to comments and
as a general part of its development process. Comments are very
welcome, please send them to whatwg@whatwg.org. Thank
you.この文書は作業中です!
この文書は、コメントへの対応や通常の開発の過程として、
毎時毎分とは言い過ぎですが毎日のペースで変更されています。
コメントは非常に歓迎していますので、
whatwg@whatwg.org
へお送りください。よろしくお願いします。
The current focus is in responding to the outstanding
feedback. (There is a chart showing
current progress.)現在の焦点は未解決のフィードバックへの対応です。
(現在の進捗を示したグラフもあります。)
Implementors should be aware that this specification is not
stable. Implementors who are not taking part in the
discussions are likely to find the specification changing out from
under them in incompatible ways. Vendors interested in
implementing this specification before it eventually reaches the
call for implementations should join the WHATWG mailing list and take part in the
discussions.実装者は、この仕様書が安定していないことに注意するべきです。
実装者は議論に参加しておかないと、
仕様がその実装とは非互換に変更されてしまうかもしれません。
この仕様書がいずれ実装呼び掛けの段階に達するのよりも前にこの仕様を実装したい販売者は、
WHATWG メイリング・リストに参加し、
議論に加わるべきです。
This specification is also being produced by the W3C HTML WG. The two
specifications are identical from the table of contents onwards.この仕様書は W3C HTML WG
によっても出版されています。2つの仕様書の目次以降は同一です。
This specification is intended to replace (be the new version of)
what was previously the HTML4, XHTML 1.x, and DOM2 HTML
specifications.この仕様書は、従来 HTML4、XHTML 1.x、DOM2 HTML
の仕様書にあったものを置き換える (その新しい版となる)
ことを意図しています。
Stability安定性
Different parts of this specification are at different levels of
maturity.この仕様書の各部分はそれぞれ異なる成熟度にあります。
Some of the more major known issues are marked
like this. There are many other issues that have been raised as
well; the issues given in this document are not the only known
issues! Also, firing of events needs to be unified (right now some
bubble, some don't, they all use different text to fire events,
etc).
Table of contents目次
1 Introduction
1.1 Background
1.2 Audience
1.3 Scope
1.4 History
1.5 Relationships to other specifications
1.5.1 Relationship to HTML 4.01 and DOM2 HTML
1.5.2 Relationship to XHTML 1.x
1.5.3 Relationship to XHTML2 and XForms
1.5.4 Relationship to Flash, Silverlight, XUL
and similar proprietary languages
1.6 HTML vs XHTML
1.7 Structure of this specification
1.7.1 How to read this specification
1.7.2 Typographic conventions
2 Common infrastructure
2.1 Terminology
2.1.1 XML
2.1.2 DOM trees
2.1.3 Scripting
2.1.4 Plugins
2.1.5 Character encodings
2.2 Conformance requirements
2.2.1 Dependencies
2.2.2 Features defined in other specifications
2.2.3 Common conformance requirements for APIs exposed to
JavaScript
2.3 Case-sensitivity and string comparison
2.4 Common microsyntaxes
2.4.1 Common parser idioms
2.4.2 Boolean attributes
2.4.3 Numbers
2.4.3.1 Unsigned integers
2.4.3.2 Signed integers
2.4.3.3 Real numbers
2.4.3.4 Ratios
2.4.3.5 Percentages and dimensions
2.4.3.6 Lists of integers
2.4.4 Dates and times
2.4.4.1 Months
2.4.4.2 Dates
2.4.4.3 Times
2.4.4.4 Local dates and times
2.4.4.5 Global dates and times
2.4.4.6 Weeks
2.4.4.7 Vaguer moments in time
2.4.5 Colors
2.4.6 Space-separated tokens
2.4.7 Comma-separated tokens
2.4.8 Keywords and enumerated attributes
2.4.9 References
2.5 URLs
2.5.1 Terminology
2.5.2 Parsing URLs
2.5.3 Resolving URLs
2.5.4 Dynamic changes to base URLs
2.5.5 Interfaces for URL manipulation
2.6 Fetching resources
2.6.1 Protocol concepts
2.6.2 Encrypted HTTP and related security concerns
2.7 Determining the type of a resource
2.7.1 Content-Type metadata
2.7.2 Content-Type sniffing: Web pages
2.7.3 Content-Type sniffing: text or binary
2.7.4 Content-Type sniffing: unknown type
2.7.5 Content-Type sniffing: image
2.7.6 Content-Type sniffing: feed or HTML
2.8 Common DOM interfaces
2.8.1 Reflecting content attributes in DOM attributes
2.8.2 Collections
2.8.2.1 HTMLCollection
2.8.2.2 HTMLFormControlsCollection
2.8.2.3 HTMLOptionsCollection
2.8.3 DOMTokenList
2.8.4 DOMStringMap
2.8.5 DOM feature strings
2.8.6 Exceptions
3 Semantics and structure of HTML documents
3.1 Introduction
3.2 Documents
3.2.1 Documents in the DOM
3.2.2 Security
3.2.3 Resource metadata management
3.2.4 DOM tree accessors
3.3 Elements
3.3.1 Semantics
3.3.2 Elements in the DOM
3.3.3 Global attributes
3.3.3.1 The id attribute
3.3.3.2 The title attribute
3.3.3.3 The lang and xml:lang
attributes
3.3.3.4 The xml:base
attribute (XML only)
3.3.3.5 The dir attribute
3.3.3.6 The class attribute
3.3.3.7 The style attribute
3.3.3.8 Embedding custom non-visible data
3.4 Content models
3.4.1 Kinds of content
3.4.1.1 Metadata content
3.4.1.2 Flow content
3.4.1.3 Sectioning content
3.4.1.4 Heading content
3.4.1.5 Phrasing content
3.4.1.6 Embedded content
3.4.1.7 Interactive content
3.4.2 Transparent content models
3.5 Paragraphs
3.6 APIs in HTML documents
3.7 Dynamic markup insertion
3.7.1 Controlling the input stream
3.7.2 Dynamic markup insertion in HTML
3.7.3 Dynamic markup insertion in XML
4 The elements of HTML
4.1 The root element
4.1.1 The html element
4.2 Document metadata
4.2.1 The head element
4.2.2 The title element
4.2.3 The base element
4.2.4 The link element
4.2.5 The meta element
4.2.5.1 Standard metadata names
4.2.5.2 Other metadata names
4.2.5.3 Pragma directives
4.2.5.4 Specifying the document's character encoding
4.2.6 The style element
4.2.7 Styling
4.3 Scripting
4.3.1 The script element
4.3.1.1 Scripting languages
4.3.2 The noscript element
4.3.3 The eventsource element
4.4 Sections
4.4.1 The body element
4.4.2 The section element
4.4.3 The nav element
4.4.4 The article element
4.4.5 The aside element
4.4.6 The h1, h2,
h3, h4,
h5, and h6
elements
4.4.7 The header element
4.4.8 The footer element
4.4.9 The address element
4.4.10 Headings and sections
4.4.10.1 Creating an outline
4.4.10.2 Distinguishing site-wide headings from page headings
4.5 Grouping content
4.5.1 The p element
4.5.2 The hr element
4.5.3 The br element
4.5.4 The pre element
4.5.5 The dialog element
4.5.6 The blockquote element
4.5.7 The ol element
4.5.8 The ul element
4.5.9 The li element
4.5.10 The dl element
4.5.11 The dt element
4.5.12 The dd element
4.6 Text-level semantics
4.6.1 The a element
4.6.2 The q element
4.6.3 The cite element
4.6.4 The em element
4.6.5 The strong element
4.6.6 The small element
4.6.7 The mark element
4.6.8 The dfn element
4.6.9 The abbr element
4.6.10 The time element
4.6.11 The progress element
4.6.12 The meter element
4.6.13 The code element
4.6.14 The var element
4.6.15 The samp element
4.6.16 The kbd element
4.6.17 The sub and sup elements
4.6.18 The span element
4.6.19 The i element
4.6.20 The b element
4.6.21 The bdo element
4.6.22 The ruby element
4.6.23 The rt element
4.6.24 The rp element
4.6.25 Usage summary
4.6.26 Footnotes
4.7 Edits
4.7.1 The ins element
4.7.2 The del element
4.7.3 Attributes common to ins and del elements
4.7.4 Edits and paragraphs
4.7.5 Edits and lists
4.8 Embedded content
4.8.1 The figure element
4.8.2 The img element
4.8.2.1 Requirements for providing text to act as an alternative for images
4.8.2.1.1 A link or button containing nothing but the image
4.8.2.1.2 A phrase or paragraph with an alternative graphical representation: charts, diagrams, graphs, maps, illustrations
4.8.2.1.3 A short phrase or label with an alternative graphical representation: icons, logos
4.8.2.1.4 Text that has been rendered to a graphic for typographical effect
4.8.2.1.5 A graphical representation of some of the surrounding text
4.8.2.1.6 A purely decorative image that doesn't add any information
4.8.2.1.7 A group of images that form a single larger picture with no links
4.8.2.1.8 A group of images that form a single larger picture with links
4.8.2.1.9 A key part of the content
4.8.2.1.10 An image not intended for the user
4.8.2.1.11 An image in an e-mail or document intended for a specific person who is known to be able to view images
4.8.2.1.12 General guidelines
4.8.2.1.13 Guidance for markup generators
4.8.3 The iframe element
4.8.4 The embed element
4.8.5 The object element
4.8.6 The param element
4.8.7 The video element
4.8.7.1 Video and audio codecs for video elements
4.8.8 The audio element
4.8.8.1 Audio codecs for audio elements
4.8.9 The source element
4.8.10 Media elements
4.8.10.1 Error codes
4.8.10.2 Location of the media resource
4.8.10.3 Media types
4.8.10.4 Network states
4.8.10.5 Loading the media resource
4.8.10.6 Offsets into the media resource
4.8.10.7 The ready states
4.8.10.8 Cue ranges
4.8.10.9 Playing the media resource
4.8.10.10 Seeking
4.8.10.11 User interface
4.8.10.12 Time ranges
4.8.10.13 Event summary
4.8.10.14 Security and privacy considerations
4.8.11 The canvas element
4.8.11.1 The 2D context
4.8.11.1.1 The canvas state
4.8.11.1.2 Transformations
4.8.11.1.3 Compositing
4.8.11.1.4 Colors and styles
4.8.11.1.5 Line styles
4.8.11.1.6 Shadows
4.8.11.1.7 Simple shapes (rectangles)
4.8.11.1.8 Complex shapes (paths)
4.8.11.1.9 Text
4.8.11.1.10 Images
4.8.11.1.11 Pixel manipulation
4.8.11.1.12 Drawing model
4.8.11.2 Color spaces and color correction
4.8.11.3 Security with canvas elements
4.8.12 The map element
4.8.13 The area element
4.8.14 Image maps
4.8.14.1 Authoring
4.8.14.2 Processing model
4.8.15 MathML
4.8.16 SVG
4.8.17 Dimension attributes
4.9 Tabular data
4.9.1 Introduction
4.9.2 The table element
4.9.3 The caption element
4.9.4 The colgroup element
4.9.5 The col element
4.9.6 The tbody element
4.9.7 The thead element
4.9.8 The tfoot element
4.9.9 The tr element
4.9.10 The td element
4.9.11 The th element
4.9.12 Attributes common to td and th elements
4.9.13 Processing model
4.9.13.1 Forming a table
4.9.13.2 Forming relationships between data cells and header cells
4.10 Forms
4.10.1 The form element
4.10.2 The fieldset element
4.10.3 The label element
4.10.4 The input element
4.10.4.1 States of the type attribute
4.10.4.1.1 Hidden state
4.10.4.1.2 Text state and Search state
4.10.4.1.3 URL state
4.10.4.1.4 E-mail state
4.10.4.1.5 Password state
4.10.4.1.6 Date and Time state
4.10.4.1.7 Date state
4.10.4.1.8 Month state
4.10.4.1.9 Week state
4.10.4.1.10 Time state
4.10.4.1.11 Local Date and Time state
4.10.4.1.12 Number state
4.10.4.1.13 Range state
4.10.4.1.14 Color state
4.10.4.1.15 Checkbox state
4.10.4.1.16 Radio Button state
4.10.4.1.17 File Upload state
4.10.4.1.18 Submit Button state
4.10.4.1.19 Image Button state
4.10.4.1.20 Reset Button state
4.10.4.1.21 Button state
4.10.4.2 Common input element attributes
4.10.4.2.1 The autocomplete attribute
4.10.4.2.2 The list attribute
4.10.4.2.3 The readonly attribute
4.10.4.2.4 The size attribute
4.10.4.2.5 The required attribute
4.10.4.2.6 The multiple attribute
4.10.4.2.7 The maxlength attribute
4.10.4.2.8 The pattern attribute
4.10.4.2.9 The min and max attributes
4.10.4.2.10 The step attribute
4.10.4.2.11 The placeholder attribute
4.10.4.3 Common input element APIs
4.10.4.4 Common event behaviors
4.10.5 The button element
4.10.6 The select element
4.10.7 The datalist element
4.10.8 The optgroup element
4.10.9 The option element
4.10.10 The textarea element
4.10.11 The output element
4.10.12 Association of controls and forms
4.10.13 Attributes common to form controls
4.10.13.1 Naming form controls
4.10.13.2 Enabling and disabling form controls
4.10.13.3 A form control's value
4.10.13.4 Autofocusing a form control
4.10.13.5 Limiting user input length
4.10.13.6 Form submission
4.10.14 Constraints
4.10.14.1 Definitions
4.10.14.2 Constraint validation
4.10.14.3 The constraint validation API
4.10.14.4 Security
4.10.15 Form submission
4.10.15.1 Implicit submission
4.10.15.2 Form submission algorithm
4.10.15.3 URL-encoded form data
4.10.15.4 Multipart form data
4.10.15.5 Plain text form data
4.10.16 Resetting a form
4.10.17 Event dispatch
4.11 Interactive elements
4.11.1 The details element
4.11.2 The datagrid element
4.11.2.1 The datagrid data model
4.11.2.2 How rows are identified
4.11.2.3 The data provider interface
4.11.2.4 The default data provider
4.11.2.4.1 Common default data
provider method definitions for cells
4.11.2.5 Populating the datagrid element
4.11.2.6 Updating the datagrid
4.11.2.7 Requirements for interactive user agents
4.11.2.8 The selection
4.11.2.9 Columns and captions
4.11.3 The command element
4.11.4 The bb element
4.11.4.1 Browser button types
4.11.4.1.1 The make application state
4.11.5 The menu element
4.11.5.1 Introduction
4.11.5.2 Building menus and tool bars
4.11.5.3 Context menus
4.11.5.4 Toolbars
4.11.6 Commands
4.11.6.1 Using the a element to define a command
4.11.6.2 Using the button element to define a command
4.11.6.3 Using the input element to define a command
4.11.6.4 Using the option element to define a command
4.11.6.5 Using the command element to define
a command
4.11.6.6 Using the bb element to define a command
4.12 Miscellaneous elements
4.12.1 The legend element
4.12.2 The div element
5 Web browsers
5.1 Browsing contexts
5.1.1 Nested browsing contexts
5.1.1.1 Navigating nested browsing contexts in the DOM
5.1.2 Auxiliary browsing contexts
5.1.2.1 Navigating auxiliary browsing contexts in the DOM
5.1.3 Secondary browsing contexts
5.1.4 Security
5.1.5 Groupings of browsing contexts
5.1.6 Browsing context names
5.2 The default view
5.2.1 Security
5.2.2 APIs for creating and navigating browsing contexts by name
5.2.3 Accessing other browsing contexts
5.3 Origin
5.3.1 Relaxing the same-origin restriction
5.4 Scripting
5.4.1 Script execution contexts
5.4.2 Event loops
5.4.2.1 Generic task sources
5.4.3 The javascript: protocol
5.4.4 Events
5.4.4.1 Event handler attributes
5.4.4.2 Event firing
5.4.4.3 Events and the Window object
5.4.4.4 Runtime script errors
5.5 User prompts
5.5.1 Simple dialogs
5.5.2 Printing
5.5.3 Dialogs implemented using separate documents
5.5.4 Notifications
5.6 System state and capabilities
5.6.1 Client identification
5.6.2 Custom protocol and content handlers
5.6.2.1 Security and privacy
5.6.2.2 Sample user interface
5.7 Offline Web applications
5.7.1 Introduction
5.7.2 Application caches
5.7.3 The cache manifest syntax
5.7.3.1 A sample manifest
5.7.3.2 Writing cache manifests
5.7.3.3 Parsing cache manifests
5.7.4 Updating an application cache
5.7.5 Processing model
5.7.5.1 Changes to the networking model
5.7.6 Application cache API
5.7.7 Browser state
5.8 Session history and navigation
5.8.1 The session history of browsing contexts
5.8.2 The History interface
5.8.3 Activating state object entries
5.8.4 The Location interface
5.8.4.1 Security
5.8.5 Implementation notes for session history
5.9 Browsing the Web
5.9.1 Navigating across documents
5.9.2 Page load processing model for HTML files
5.9.3 Page load processing model for XML files
5.9.4 Page load processing model for text files
5.9.5 Page load processing model for images
5.9.6 Page load processing model for content that uses plugins
5.9.7 Page load processing model for inline content that doesn't have a DOM
5.9.8 Navigating to a fragment identifier
5.9.9 History traversal
5.9.10 Closing a browsing context
5.10 Structured client-side storage
5.10.1 Storing name/value pairs
5.10.1.1 Introduction
5.10.1.2 The Storage interface
5.10.1.3 The sessionStorage attribute
5.10.1.4 The localStorage attribute
5.10.1.5 The storage event
5.10.1.5.1 Event definition
5.10.1.6 Threads
5.10.2 Database storage
5.10.2.1 Introduction
5.10.2.2 Databases
5.10.2.3 Executing SQL statements
5.10.2.4 Database query results
5.10.2.5 Errors
5.10.2.6 Processing model
5.10.3 Disk space
5.10.4 Privacy
5.10.4.1 User tracking
5.10.4.2 Cookie resurrection
5.10.5 Security
5.10.5.1 DNS spoofing attacks
5.10.5.2 Cross-directory attacks
5.10.5.3 Implementation risks
5.10.5.4 SQL and user agents
5.10.5.5 SQL injection
5.11 Links
5.11.1 Hyperlink elements
5.11.2 Following hyperlinks
5.11.2.1 Hyperlink auditing
5.11.3 Link types
5.11.3.1 Link type "alternate"
5.11.3.2 Link type "archives"
5.11.3.3 Link type "author"
5.11.3.4 Link type "bookmark"
5.11.3.5 Link type "external"
5.11.3.6 Link type "feed"
5.11.3.7 Link type "help"
5.11.3.8 Link type "icon"
5.11.3.9 Link type "license"
5.11.3.10 Link type "nofollow"
5.11.3.11 Link type "noreferrer"
5.11.3.12 Link type "pingback"
5.11.3.13 Link type "prefetch"
5.11.3.14 Link type "search"
5.11.3.15 Link type "stylesheet"
5.11.3.16 Link type "sidebar"
5.11.3.17 Link type "tag"
5.11.3.18 Hierarchical link types
5.11.3.18.1 Link type "index"
5.11.3.18.2 Link type "up"
5.11.3.19 Sequential link types
5.11.3.19.1 Link type "first"
5.11.3.19.2 Link type "last"
5.11.3.19.3 Link type "next"
5.11.3.19.4 Link type "prev"
5.11.3.20 Other link types
6 User Interaction
6.1 Introduction
6.2 The hidden attribute
6.3 Activation
6.4 Scrolling elements into view
6.5 Focus
6.5.1 Sequential focus navigation
6.5.2 Focus management
6.5.3 Document-level focus APIs
6.5.4 Element-level focus APIs
6.6 The text selection APIs
6.6.1 APIs for the browsing context selection
6.6.2 APIs for the text field selections
6.7 The contenteditable attribute
6.7.1 User editing actions
6.7.2 Making entire documents editable
6.8 Drag and drop
6.8.1 Introduction
6.8.2 The DragEvent and DataTransfer interfaces
6.8.3 Events fired during a drag-and-drop action
6.8.4 Drag-and-drop processing model
6.8.4.1 When the drag-and-drop operation starts or ends in another
document
6.8.4.2 When the drag-and-drop operation starts or ends in another
application
6.8.5 The draggable attribute
6.8.6 Copy and paste
6.8.6.1 Copy to clipboard
6.8.6.2 Cut to clipboard
6.8.6.3 Paste from clipboard
6.8.6.4 Paste from selection
6.8.7 Security risks in the drag-and-drop model
6.9 Undo history
6.9.1 The UndoManager interface
6.9.2 Undo: moving back in the undo transaction history
6.9.3 Redo: moving forward in the undo transaction history
6.9.4 The UndoManagerEvent interface and the undo and redo events
6.9.5 Implementation notes
6.10 Command APIs
7 Communication
7.1 Event definitions
7.2 Server-sent events
7.2.1 The RemoteEventTarget interface
7.2.2 Connecting to an event stream
7.2.3 Parsing an event stream
7.2.4 Interpreting an event stream
7.2.5 Notes
7.3 Web sockets
7.3.1 Introduction
7.3.2 The WebSocket interface
7.3.3 WebSocket Events
7.3.4 The Web Socket protocol
7.3.4.1 Client-side requirements
7.3.4.1.1 Handshake
7.3.4.1.2 Data framing
7.3.4.2 Server-side requirements
7.3.4.2.1 Minimal handshake
7.3.4.2.2 Handshake details
7.3.4.2.3 Data framing
7.3.4.3 Closing the connection
7.4 Cross-document messaging
7.4.1 Introduction
7.4.2 Security
7.4.2.1 Authors
7.4.2.2 User agents
7.4.3 Posting text
7.4.4 Posting message ports
7.4.5 Posting structured data
7.5 Channel messaging
7.5.1 Introduction
7.5.2 Message channels
7.5.3 Message ports
7.5.3.1 Ports and browsing contexts
7.5.3.2 Ports and garbage collection
8 The HTML syntax
8.1 Writing HTML documents
8.1.1 The DOCTYPE
8.1.2 Elements
8.1.2.1 Start tags
8.1.2.2 End tags
8.1.2.3 Attributes
8.1.2.4 Optional tags
8.1.2.5 Restrictions on content models
8.1.2.6 Restrictions on the contents of CDATA and RCDATA elements
8.1.3 Text
8.1.3.1 Newlines
8.1.4 Character references
8.1.5 CDATA sections
8.1.6 Comments
8.2 Parsing HTML documents
8.2.1 Overview of the parsing model
8.2.2 The input stream
8.2.2.1 Determining the character encoding
8.2.2.2 Character encoding requirements
8.2.2.3 Preprocessing the input stream
8.2.2.4 Changing the encoding while parsing
8.2.3 Parse state
8.2.3.1 The insertion mode
8.2.3.2 The stack of open elements
8.2.3.3 The list of active formatting elements
8.2.3.4 The element pointers
8.2.3.5 The scripting state
8.2.4 Tokenization
8.2.4.1 Data state
8.2.4.2 Character reference data state
8.2.4.3 Tag open state
8.2.4.4 Close tag open state
8.2.4.5 Tag name state
8.2.4.6 Before attribute name state
8.2.4.7 Attribute name state
8.2.4.8 After attribute name state
8.2.4.9 Before attribute value state
8.2.4.10 Attribute value (double-quoted) state
8.2.4.11 Attribute value (single-quoted) state
8.2.4.12 Attribute value (unquoted) state
8.2.4.13 Character reference in attribute value state
8.2.4.14 After attribute value (quoted) state
8.2.4.15 Self-closing start tag state
8.2.4.16 Bogus comment state
8.2.4.17 Markup declaration open state
8.2.4.18 Comment start state
8.2.4.19 Comment start dash state
8.2.4.20 Comment state
8.2.4.21 Comment end dash state
8.2.4.22 Comment end state
8.2.4.23 DOCTYPE state
8.2.4.24 Before DOCTYPE name state
8.2.4.25 DOCTYPE name state
8.2.4.26 After DOCTYPE name state
8.2.4.27 Before DOCTYPE public identifier state
8.2.4.28 DOCTYPE public identifier (double-quoted) state
8.2.4.29 DOCTYPE public identifier (single-quoted) state
8.2.4.30 After DOCTYPE public identifier state
8.2.4.31 Before DOCTYPE system identifier state
8.2.4.32 DOCTYPE system identifier (double-quoted) state
8.2.4.33 DOCTYPE system identifier (single-quoted) state
8.2.4.34 After DOCTYPE system identifier state
8.2.4.35 Bogus DOCTYPE state
8.2.4.36 CDATA section state
8.2.4.37 Tokenizing character references
8.2.5 Tree construction
8.2.5.1 Creating and inserting elements
8.2.5.2 Closing elements that have implied end tags
8.2.5.3 Foster parenting
8.2.5.4 The "initial" insertion mode
8.2.5.5 The "before html" insertion mode
8.2.5.6 The "before head" insertion mode
8.2.5.7 The "in head" insertion mode
8.2.5.8 The "in head noscript" insertion mode
8.2.5.9 The "after head" insertion mode
8.2.5.10 The "in body" insertion mode
8.2.5.11 The "in CDATA/RCDATA" insertion mode
8.2.5.12 The "in table" insertion mode
8.2.5.13 The "in caption" insertion mode
8.2.5.14 The "in column group" insertion mode
8.2.5.15 The "in table body" insertion mode
8.2.5.16 The "in row" insertion mode
8.2.5.17 The "in cell" insertion mode
8.2.5.18 The "in select" insertion mode
8.2.5.19 The "in select in table" insertion mode
8.2.5.20 The "in foreign content" insertion mode
8.2.5.21 The "after body" insertion mode
8.2.5.22 The "in frameset" insertion mode
8.2.5.23 The "after frameset" insertion mode
8.2.5.24 The "after after body" insertion mode
8.2.5.25 The "after after frameset" insertion mode
8.2.6 The end
8.2.7 Coercing an HTML DOM into an infoset
8.3 Namespaces
8.4 Serializing HTML fragments
8.5 Parsing HTML fragments
8.6 Named character references
9 Rendering
9.1 Rendering and menus/toolbars
9.1.1 The 'icon' property
10 Obsolete features
10.1 Obsolete elements
10.1.1 The body element
10.1.2 The applet element
10.2 Conformance checkers
11 Things that you can't do with this specification because
they are better handled using other technologies that are further
described herein
11.1 Localization
11.2 Declarative 2D vector graphics and animation
11.3 Declarative 3D scenes
11.4 Timers
11.5 Rendering and the DOM
Index
References
Acknowledgements
1 Introduction1 はじめに
1.1 Background1.1 背景
This section is non-normative.この節は規定の一部ではありません。
The World Wide Web's markup language has always been HTML. HTML
was primarily designed as a language for semantically describing
scientific documents, although its general design and adaptations
over the years has enabled it to be used to describe a number of
other types of documents.World Wide Web のマーク付け言語は、いつもずっと HTML でした。
HTML は主に意味的に記述された科学的な文書のための言語として設計されましたが、
一般性を持った設計になっていたことと長年にわたる適応化が行われたことから、
それ以外の様々な種類の文書の記述にも使えるようになりました。
The main area that has not been adequately addressed by HTML is a
vague subject referred to as Web Applications. This specification
attempts to rectify this, while at the same time updating the HTML
specifications to address issues raised in the past few years.HTML がこれまで十分に取り扱わなかった分野としては、主に、Web アプリケーションと大まかに括られる分野が挙げられます。
この仕様書は、この状況を是正しようと試みると共に、
過去数年間に取り上げられた問題を解決するべく、 HTML 仕様書を更新するものです。
1.2 Audience
This section is non-normative.この節は規定の一部ではありません。
This specification is intended for authors of documents and
scripts that use the features defined in this specificaton, and
implementors of tools that are intended to conform to this
specification, and individuals wishing to establish the correctness
of documents or implementations with respect to the requirements of
this specification.
This document is probably not suited to readers who do not
already have at least a passing familiarity with Web technologies,
as in places it sacrifices clarity for precision, and brevity for
completeness. More approachable tutorials and authoring guides can
provide a gentler introduction to the topic.
In particular, readers should be familiar with the basics of DOM
Core and DOM Events before reading this specification. An
understanding of WebIDL, HTTP, XML, Unicode, character encodings,
JavaScript, and CSS will be helpful in places but is not
essential.
1.3 Scope1.3 適用範囲
This section is non-normative.この節は規定の一部ではありません。
This specification is limited to providing a semantic-level
markup language and associated semantic-level scripting APIs for
authoring accessible pages on the Web ranging from static documents
to dynamic applications.この仕様書は、静的な文書から動的なアプリケーションまで、 Web
のアクセス性の高い頁を著述するための、
意味レベルのマーク付け言語とそれに関連付けられた意味レベルのスクリプト API
を提供することに限定されています。
The scope of this specification does not include providing
mechanisms for media-specific customization of presentation
(although default rendering rules for Web browsers are included at
the end of this specification, and several mechanisms for hooking
into CSS are provided as part of the language).この仕様書の適用範囲には、提示の媒体特有のカスタム化のための機構の提供は含みません
(ただし、 Web ブラウザの既定のレンダリング規則がこの仕様書の最後に含まれており、
CSS に引っ掛けるための仕組みもいくつか言語の一部として提供します)。
The scope of this specification does not include documenting
every HTML or DOM feature supported by Web browsers. Browsers
support many features that are considered to be very bad for
accessibility or that are otherwise inappropriate. For example, the
blink element is clearly presentational and authors
wishing to cause text to blink should instead use CSS.この仕様書の適用範囲には、 Web ブラウザで提供されるすべての HTML や DOM
の機能の文書化は含みません。ブラウザは、アクセス可能性的に非常に悪いか、
その他の理由で不適切と考えられる機能に多く対応しています。例えば、
blink 要素は明らかに提示的であり、
著者は文章を点滅させたい時には代わりに CSS を使うべきです。
The scope of this specification is not to describe an entire
operating system. In particular, hardware configuration software,
image manipulation tools, and applications that users would be
expected to use with high-end workstations on a daily basis are out
of scope. In terms of applications, this specification is targeted
specifically at applications that would be expected to be used by
users on an occasional basis, or regularly but from disparate
locations, with low CPU requirements. For instance online purchasing
systems, searching systems, games (especially multiplayer online
games), public telephone books or address books, communications
software (e-mail clients, instant messaging clients, discussion
software), document editing software, etc.この仕様書の適用範囲には、オペレーティング・システム全体を記述することは含みません。
特に、ハードウェア設定ソフトウェア、画像操作ツール、高級ワークステーションでの日常用途向けアプリケーションは適用範囲外です。
この仕様書は、アプリケーションに関しては、時たま利用するか、日常的ながらも様々な場所から利用するような、
しかも CPU に対する要求の低いアプリケーションを特に対象としています。
例えば、オンライン購入システム、検索システム、ゲーム (特に多プレイヤー・オンライン・ゲーム)、
公衆電話帳・住所録、通信ソフトウェア (電子メイル・クライアント、
即席メッセージ・クライアント、議論ソフトウェア)、
文書編集ソフトウェアなどです。
For sophisticated cross-platform applications, there already
exist several proprietary solutions (such as Mozilla's XUL, Adobe's
Flash, or Microsoft's Silverlight). These solutions are evolving
faster than any standards process could follow, and the requirements
are evolving even faster. These systems are also significantly more
complicated to specify, and are orders of magnitude more difficult
to achieve interoperability with, than the solutions described in
this document. Platform-specific solutions for such sophisticated
applications (for example the Mac OS X Core APIs) are even further
ahead.洗練された多環境対応アプリケーションについては、独占的な解決策が既にいくつか存在します
(Mozilla の XUL、 Adobe の Flash、 Microsoft の Silverlight など)。
これらの解決策は標準化過程よりも速く進化しており、
要求も更に速いスピードで高まっています。これらのシステムは、
この文書で説明している解決策よりも甚だ複雑で規定しがたく、
相互運用性の達成も桁違いに難しいものです。
洗練されたアプリケーションのための環境特有の解決策 (例えば Mac OS X 中核 API)
は更にそれ以上です。
1.4 History1.4 歴史
This section is non-normative.この節は規定の一部ではありません。
Work on HTML5 originally started in late 2003, as a proof of
concept to show that it was possible to extend HTML4's forms to
provide many of the features that XForms 1.0 introduced, without
requiring browsers to implement rendering engines that were
incompatible with existing HTML Web pages. At this early stage,
while the draft was already publicly available, and input was
already being solicited from all sources, the specification was only
under Opera Software's copyright.元々 HTML5 に関する作業は2003年の暮れに、 XForms 1.0 が導入した機能の多くは既存の HTML Web
頁と非互換なレンダリング・エンジンをブラウザに実装させずとも HTML4
のフォームの拡張によって提供できることの実証としてはじまりました。
この早い段階の作業は、原案は既に公開されていましたし、意見は既にあらゆる方面から募られていましたが、
仕様書は Opera Software の著作権のもとにのみ置かれていました。
In early 2004, some of the principles that underly this effort,
as well as an early draft proposal covering just forms-related
features, were presented to the W3C jointly by Mozilla and Opera at
a workshop discussing the future of Web Applications on the Web. The
proposal was rejected on the grounds that the proposal conflicted
with the previously chosen direction for the Web's evolution.2004年のはじめ、この作業の根底にある原理の一部やフォーム関連の機能のみを扱った早期の原案提案を
Mozilla と Opera が共同で W3C に対して Web における Web アプリケーションの将来を議論する会議において示しました。
この提案は以前選ばれた Webの発展の方向と矛盾しているとの理由で却下されました。
Shortly thereafter, Apple, Mozilla, and Opera jointly announced
their intent to continue working on the effort. A public mailing
list was created, and the drafts were moved to the WHATWG site. The
copyright was subsequently amended to be jointly owned by all three
vendors, and to allow reuse of the specifications.そのすぐ後、 Apple と Mozilla と Opera はこの作業を継続する意思を共同で発表しました。
公開のメイリング・リストが作成され、原案は WHATWG サイトに移されました。
それ以後著作権はこれら3販売者が共同で所有し、仕様書の再利用を認めるように改定されました。
In 2006, the W3C expressed interest in the specification, and
created a working group chartered to work with the WHATWG on the
development of the HTML5 specifications. The working group opened in
2007. Apple, Mozilla, and Opera allowed the W3C to publish the
specifications under the W3C copyright, while keeping versions with
the less restrictive license on the WHATWG site.2006年には、 W3C はこの仕様書に対する興味を示し、 HTML5 仕様書の開発を WHATWG
と共に行うことを憲章に含めた作業部会を作成しました。作業部会は2007年に開始しました。
Apple と Mozilla と Opera は W3C が仕様書を W3C の著作権のもとで出版することを認めつつ、
WHATWG サイトでより制限のゆるいライセンスの版を提供し続けています。
Since then, both groups have been working together.それ以後、両部会は共同で作業を続けています。
1.5 Relationships to other specifications1.5 他の仕様書との関係
1.5.1 Relationship to HTML 4.01 and DOM2 HTML1.5.1 HTML 4.01 や DOM2 HTML との関係
This section is non-normative.この節は規定の一部ではありません。
This specification represents a new version of HTML4, along with
a new version of the associated DOM2 HTML API. Migration from HTML4
to the format and APIs described in this specification should in
most cases be straightforward, as care has been taken to ensure that
backwards-compatibility is retained. [HTML4] [DOM2HTML]この仕様書は HTML4 の新しい版であり、それに対応する DOM2 HTML API
の新しい版です。この仕様書は後方互換性を残すことに注意を払っていますので、
ほとんどの場合、 HTML4 からこの仕様書で説明する書式や API
への移行は簡単なはずです。[HTML4] [DOM2HTML]
1.5.2 Relationship to XHTML 1.x1.5.2 XHTML 1.x との関係
This section is non-normative.この節は規定の一部ではありません。
This specification is intended to replace XHTML 1.0 as the
normative definition of the XML serialization of the HTML
vocabulary. [XHTML10]この仕様書は、 HTML 語彙の XML 直列化の規定的定義としての XHTML 1.0
を置き換えることを意図しています。 [XHTML10]
While this specification updates the semantics and requirements
of the vocabulary defined by XHTML Modularization 1.1 and used by
XHTML 1.1, it does not attempt to provide a replacement for the
modularization scheme defined and used by those (and other)
specifications, and therefore cannot be considered a complete
replacement for them. [XHTMLMOD] [XHTML11]この仕様書は XHTML モジュール化 1.1 で定義され XHTML 1.1
で使われている語彙の意味と要件を更新することを意図していますが、
これらの仕様書 (やその他の仕様書) で定義され使用されているモジュール化手法の置き換えを提供しようとはしていませんので、
これらの完全なる置き換えとはいえません。 [XHTMLMOD] [XHTML11]
Thus, authors and implementors who do not need such a
modularization scheme can consider this specification a replacement
for XHTML 1.x, but those who do need such a mechanism are encouraged
to continue using the XHTML 1.1 line of specifications.従って、当該モジュール化手法が必要ない著者や実装者にとってはこの仕様書を
XHTML 1.x を置き換えるものと考えることができますが、それが必要な人は
XHTML 1.1 系列の仕様書を使い続けることをお勧めします。
This section is non-normative.この節は規定の一部ではありません。
XHTML2 defines a new vocabulary with features for hyperlinks,
multimedia content, annotating document edits, rich metadata,
declarative interactive forms, and describing the semantics of human
literary works such as poems and scientific papers. [XHTML2]XHTML2 はハイパーリンクや多媒体の内容、文書の編集の注釈付け、豊富なメタデータ、
宣言的な対話的フォーム、詩や科学的論文などの人文学的著作物の意味の記述のための機能を持った新しい語彙を定義しています。
[XHTML2]
XForms similarly defines a new vocabulary with features for
complex data entry, such as tax forms or insurance forms.同様に、 XForms は納税申告書や保険書類のような複雑なデータ入力のための機能を持った新しい語彙を定義しています。
However, XHTML2 and XForms lack features to express the semantics
of many of the non-document types of content often seen on the
Web. For instance, they are not well-suited for marking up forum
sites, auction sites, search engines, online shops, mapping
applications, e-mail applications, word processors, real-time
strategy games, and the like.しかし、 XHTML2 と XForms は、 Web でよく見られる、文書以外の種類の内容の多くの意味を表現する機能に欠けています。
例えば、 XHTML2 や XForms は掲示板サイト、オークション・サイト、検索円陣、
オンライン商店、地図アプリケーション、電子メイル・アプリケーション、
ワープロ、実時間戦略ゲーム、等々のマーク付けにはあまり適していません。
This specification aims to extend HTML so that it is
also suitable in these contexts.この仕様書は、 HTML を拡張し、これらの文脈でも適切なものとなることを目指します。
XHTML2, XForms, and this specification all use different
namespaces and therefore can all be implemented in the same XML
processor.XHTML2、XForms、そしてこの仕様はすべて異なる名前空間を用いていますから、
同じ XML 処理器ですべてを実装することができます。
1.5.4 Relationship to Flash, Silverlight, XUL
and similar proprietary languages1.5.4 Flash、Silverlight、XUL、
その他同様の独占言語との関係
This section is non-normative.この節は規定の一部ではありません。
This specification is independent of the various proprietary
application languages that various vendors provide, but is intended
to address many of the same problems.この仕様書は様々な販売者が提供する様々な独占的アプリケーション言語とは独立したものですが、
解決しようとする問題には共通するものも多くあります。
In contrast with proprietary languages, this specification is
intended to define an openly-produced, vendor-neutral language, to
be implemented in a broad range of competing products, across a wide
range of platforms and devices. This enables developers to write
applications that are not limited to one vendor's implementation or
language. Furthermore, while writing applications that target
vendor-specific platforms necessarily introduces a cost that
application developers and their customers or users will face if
they are forced to switch (or desire to switch) to another vendor's
platform, using an openly-produced and vendor neutral language means
that application authors can switch vendors with little to no
cost.この仕様書は独占言語とは異なり、開放的に生産された販売者に中立な言語を定義すること、
様々な環境と装置において競合する製品間にも広く実装されることを意図しています。
それによって開発者は特定の販売者の実装や言語に制限されないアプリケーションを書くことができます。
更に、特定の販売者固有の環境を対象とするアプリケーションを書くと顧客・利用者が他の販売者の環境に切り替えなければならなくなった場合 (や切り替えたい場合) に必然的に対価を求めることになってしまいますが、開放的に生産された販売者に対して中立な言語を使うことでアプリケーションの著者はほとんど対価なしに販売者を切り替えることができます。
1.6 HTML vs XHTML1.6 HTML 対 XHTML
This section is non-normative.この節は規定の一部ではありません。
This specification defines an abstract language for describing
documents and applications, and some APIs for interacting with
in-memory representations of resources that use this language.この仕様書は、文書とアプリケーションを記述するための抽象言語と、
その言語を用いた資源の記憶装置内表現と対話する API をいくつか定義します。
The in-memory representation is known as "DOM5 HTML", or "the
DOM" for short.記憶装置内表現は「DOM5 HTML」、あるいは略して「DOM」と呼ばれます。
There are various concrete syntaxes that can be used to transmit
resources that use this abstract language, two of which are defined
in this specification.この抽象言語を用いた資源を転送するために使用できる具象構文はいろいろありますが、
この仕様書ではそのうちの2つを定義します。
The first such concrete syntax is "HTML5". This is the format
recommended for most authors. It is compatible with all legacy Web
browsers. If a document is transmitted with the MIME type text/html, then it will be processed as an "HTML5"
document by Web browsers.1つ目の具象構文は「HTML5」です。これは、ほとんどの著者に推奨する書式です。
この具象構文はすべての遺物 Web ブラウザと互換性があります。
文書が MIME 型 text/html で転送される場合、 Web ブラウザはこれを「HTML5」
として処理します。
The second concrete syntax uses XML, and is known as
"XHTML5". When a document is transmitted with an XML MIME type, such
as application/xhtml+xml, then it is processed
by an XML processor by Web browsers, and treated as an "XHTML5"
document. Authors are reminded that the processing for XML and HTML
differs; in particular, even minor syntax errors will prevent an XML
document from being rendered fully, whereas they would be ignored in
the "HTML5" syntax.2つ目の具象構文は XML を使い、「XHTML5」と呼ばれます。文書が XML MIME 型、例えば application/xhtml+xml で転送される時には、 Web
ブラウザは XML 処理器によりこれを処理し、「XHTML5」文書として扱います。
著者は、 XML と HTML の処理が異なることに注意する必要があります。
特に、 XML 文書は小さな構文誤りによってさえ完全には表示されなくなってしまいます。
一方の「HTML5」構文では小さな誤りは無視されます。
The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all
represent the same content. For example, namespaces cannot be
represented using "HTML5", but they are supported in "DOM5 HTML" and
"XHTML5". Similarly, documents that use the noscript
feature can be represented using "HTML5", but cannot be represented
with "XHTML5" and "DOM5 HTML". Comments that contain the string
"-->" can be represented in "DOM5 HTML" but
not in "HTML5" and "XHTML5". And so forth.「DOM5 HTML」、「HTML5」、「XHTML5」の各表現は、
すべてが同じ内容を表現できるわけではありません。例えば、
名前空間は「HTML5」では表現できませんが、「DOM5 HTML」と「XHTML5」
は対応しています。同様に、 noscript 機能を用いた文書は「HTML5」
を使って表現できますが、「XHTML5」や「DOM5 HTML」では表現できません。
文字列「-->」を含む注釈は「DOM5 HTML」
では表現できますが、「HTML5」や「XHTML5」では表現できません。
他にもあります。
1.7 Structure of this specification1.7 この仕様書の構造
This section is non-normative.この節は規定の一部ではありません。
This specification is divided into the following major
sections:この仕様書は次の大きな章で構成されています。
- Common Infrastructure共通基盤
- The conformance classes, algorithms, definitions, and the
common underpinnings of the rest of the specification.適合性級、算法、定義、仕様書の残りの部分の共通の土台です。
- The DOMDOM
- Documents are built from elements. These elements form a tree
using the DOM. This section defines the features of this DOM, as
well as introducing the features common to all elements, and the
concepts used in defining elements.文書は要素により構築されます。要素は DOM を使って木を形成します。
この章は DOM の機能を定義すると共に、
すべての要素に共通な機能と要素を定義するために用いる概念を導入します。
- Elements要素
- Each element has a predefined meaning, which is explained in
this section. User agent requirements for how to handle each
element are also given, along with rules for authors on how to use
the element.各要素はあらかじめ定義された意味を持っており、それをこの章で説明します。
各要素をどう取り扱うかに関する利用者エージェント要件や、
著者が要素をどう使うかの規則も与えます。
- Web BrowsersWeb ブラウザ
- HTML documents do not exist in a vacuum — this section
defines many of the features that affect environments that deal
with multiple pages, links between pages, and running scripts.HTML 文書は単独で存在するのではありません。この章は、
複数の頁や頁間のリンクやスクリプトの実行を処理する、
環境に影響する機能の多くを定義します。
- User Interaction利用者対話
- HTML documents can provide a number of mechanisms for users to
interact with and modify content, which are described in this
section.HTML 文書は利用者と対話したり利用者が内容を編集したりするための数々の仕組みを提供でき、
この章ではそれについて説明します。
- The Communication APIs通信 API
- Applications written in HTML often require mechanisms to
communicate with remote servers, as well as communicating with
other applications from different domains running on the same
client.HTML で書かれたアプリケーションでは、よく遠隔鯖と通信したり、
同じクライアント上で図指している異なるドメインの他のアプリケーションと通信する仕組みが必要になります。
- The Language Syntax言語構文
- All of these features would be for naught if they couldn't be
represented in a serialized form and sent to other people, and so
this section defines the syntax of HTML, along with rules for how
to parse HTML.これらの機能はすべて、直列化された形式で表現して他の人に送ることができなければ、
意味がありません。この章では、 HTML の構文と、 HTML の構文解析の方法に関する規則を定義します。
There are also a couple of appendices, defining rendering rules for Web browsers and listing
areas that are out of scope for this
specification.この仕様書には、 Web ブラウザのレンダリング規則を定義する附属書やこの仕様書の適用範囲外の分野を列挙する附属書もあります。
1.7.1 How to read this specification1.7.1 この仕様書の読み方
This specification should be read like all other specifications.
First, it should be read cover-to-cover, multiple times. Then, it
should be read backwards at least once. Then it should be read by
picking random sections from the contents list and following all the
cross-references.この仕様書は、他のすべての仕様書と同じように読むべきです。
まず、最初から最後まで、何回も読むべきです。
次に、最低1回は後ろから読むべきです。
その次に、目次から無作為に節を選び、すべての相互参照をたどりながら読むべきです。
1.7.2 Typographic conventions1.7.2 活字的規約
This is a definition, requirement, or explanation.これは定義や要件や説明です。
This is a note.これは注意書きです。
This is an example.これは例です。
This is an open issue.これは未解決の問題です。
This is a warning.これは警告です。
The defining instance of a term is marked up like this. Uses of that term are marked up like
this or like this.用語の定義を行う実現値はこのようにマーク付けされます。この用語を使う場合は、このように、あるいはこのようにマーク付けされます。
The defining instance of an element, attribute, or API is marked
up like this. References to
that element, attribute, or API are marked up like this.要素、属性、API を定義する実現値は、
このようにマーク付けされます。
この要素、属性、API への参照はこのようにマーク付けされます。
Other code fragments are marked up like
this.その他の符号素片は、このようにマーク付けされます。
Variables are marked up like this.変数はこのようにマーク付けされます。
interface Example {
// this is an IDL definition
};interface 例 {
// これは IDL 定義です。
};
2 Common infrastructure2 共通基盤
2.1 Terminology2.1 用語
This specification refers to both HTML and XML attributes and DOM
attributes, often in the same context. When it is not clear which is
being referred to, they are referred to as content
attributes for HTML and XML attributes, and DOM
attributes for those from the DOM. Similarly, the term
"properties" is used for both ECMAScript object properties and CSS
properties. When these are ambiguous they are qualified as object
properties and CSS properties respectively.この仕様書では、よく、同じ文脈で HTML や XML の属性と DOM の属性の両方に言及します。
いずれの属性を指しているのかが明確でない場合には、
HTML や XML の属性を内容属性、
DOM の属性を DOM 属性と呼びます。
同様に、用語「特性」は ECMAScript のオブジェクト特性と CSS の特性の両方に使います。
いずれを指すか曖昧な場合には、それぞれオブジェクト特性や CSS 特性のように修飾して使います。
The term HTML documents is sometimes used in
contrast with XML documents to specifically mean
documents that were parsed using an HTML parser (as
opposed to using an XML parser or created purely through the
DOM).用語 HTML 文書は時々
XML 文書と対比させて使いますが、
(XML 構文解析器を使って構文解析されたものや純粋に DOM を使って作られたものに対して)
HTML 構文解析器を使って構文解析された文書を意味します。
Generally, when the specification states that a feature applies
to HTML or XHTML, it also includes the other. When a feature
specifically only applies to one of the two languages, it is called
out by explicitly stating that it does not apply to the other
format, as in "for HTML, ... (this does not apply to XHTML)".一般に、この仕様書が HTML か XHTML に適用される機能を述べる時には、
他方についても含んでいます。ある機能がこの2つの言語のうちのいずれかにのみに特に適用される時は、
それがわかるように、他方の書式には適用されないことを明記します。
This specification uses the term document to
refer to any use of HTML, ranging from short static documents to
long essays or reports with rich multimedia, as well as to
fully-fledged interactive applications.この仕様は、短く静的な文書から長くて豊富な多媒体を用いた随筆や報告書まで、
あるいは一丁前の対話的なアプリケーションなど、 HTML のあらゆる用法をも含めて、
用語文書を使って表します。
For simplicity, terms such as shown, displayed,
and visible might sometimes be used when referring to the
way a document is rendered to the user. These terms are not meant to
imply a visual medium; they must be considered to apply to other
media in equivalent ways.簡単のため、文書が利用者に対してレンダリングされる方法に言及する際に示す、表示する、可視であるといった用語を使うことがあります。
これらの語を使っていても、視覚的な媒体を仮定しているわけではありません。
他の媒体に対しても等価な方法で適用されると解釈しなければなりません。
Some of the algorithms in this specification, for historical
reasons, require the user agent to pause until some
condition has been met. While a user agent is paused, it must ensure
that no scripts execute (e.g. no event handlers, no timers,
etc). User agents should remain responsive to user input while
paused, however, albeit without letting the user interact with Web
pages where that would involve invoking any script.この仕様書にある算法のうちのいくつかは、歴史的な理由により、何らかの条件が満たされるまでの間、
利用者エージェントが一時停止することを要求しています。
利用者エージェントは、一時停止している間、スクリプト (事象取扱器やタイマーなど)
が実行されないようにしなければなりません。
しかし、一時停止中利用者エージェントは、
スクリプトの呼び出しに関わってくるような Web 頁との対話を利用者にさせないでおきながらも、
利用者の入力に応答的であり続けるべきです。
2.1.1 XML
To ease migration from HTML to XHTML, UAs
conforming to this specification will place elements in HTML in the
http://www.w3.org/1999/xhtml namespace, at least for
the purposes of the DOM and CSS. The term "elements in the HTML
namespace", or "HTML elements" for short, when used
in this specification, thus refers to both HTML and XHTML
elements.HTML から XHTML への移行を簡単にするために、
この仕様書に適合する利用者エージェントは、
少なくても DOM と CSS に関しては、 HTML の要素を
http://www.w3.org/1999/xhtml
名前空間に置きます。
この仕様書では、用語「HTML 名前空間の要素」、
略して「HTML 要素」は、
HTML と XHTML の両方の要素を指します。
Unless otherwise stated, all elements defined or mentioned in
this specification are in the
http://www.w3.org/1999/xhtml namespace, and all
attributes defined or mentioned in this specification have no
namespace (they are in the per-element partition).特に断らない場合、
この仕様書で定義または言及するすべての要素は
http://www.w3.org/1999/xhtml 名前空間にあり、
この仕様書で定義または言及するすべての属性は名前空間を持ちません
(要素毎区画にあります)。
When an XML name, such as an attribute or element name, is
referred to in the form prefix:localName, as in xml:id or
svg:rect, it refers to a name with the local name localName and the namespace given by the prefix, as
defined by the following table:XML の名前 (属性名や要素名など) を prefix:localName の形表す場合 (例えば xml:id や
svg:rect) には、局所名が localName であり、
名前空間は接頭辞によって次の表で定義する通りであるような名前を表します。
xmlhttp://www.w3.org/XML/1998/namespacehtmlhttp://www.w3.org/1999/xhtmlsvghttp://www.w3.org/2000/svg
Attribute names are said to be XML-compatible if they
match the Name production defined in XML, they contain no
U+003A COLON (:) characters, and their first three characters are
not an ASCII case-insensitive match for the string
"xml". [XML]属性名が XML 互換であるとは、 XML で定義されている Name 生成規則に一致し、 U+003A
COLON (:) 文字を含まず、最初の3文字が ASCII 大文字・小文字不区別で文字列「xml」に一致しないことをいいます。 [XML]
2.1.2 DOM trees2.1.2 DOM 木
The term root element, when not explicitly qualified
as referring to the document's root element, means the furthest
ancestor element node of whatever node is being discussed, or the
node itself if it has no ancestors. When the node is a part of the
document, then that is indeed the document's root element; however,
if the node is not currently part of the document tree, the root
element will be an orphaned node.用語根要素は、
文書の根要素と明示的に修飾していない時は、
当該節点の最遠の祖先要素節点か、祖先を持たない場合にはその節点自体を意味します。
節点が文書の一部である時には、これは文書の根要素となります。
しかし、節点がその時点で文書木の一部でない場合は、
根要素は孤児節点となります。
The Document of a Node (such as an
element) is the Document that the Node's
ownerDocument DOM attribute returns.Node (要素など) の Document とは、
当該 Node の ownerDocument DOM
属性が返す Document です。
An element is said to have been inserted into a document when its root
element changes and is now the document's root
element. If a Node is in a Document
then that Document is always the Node's
Document, and the Node's ownerDocument DOM attribute thus always returns that
Document.要素は、その根要素が変化し、
根要素が文書の根要素となった時、
文書に挿入されたといいます。
The term tree order means a pre-order, depth-first
traversal of DOM nodes involved (through the parentNode/childNodes
relationship).用語木順は、関係 DOM 節点の (parentNode/childNodes 関係を通じた)
行きがけ順幅優先探索を表します。
When it is stated that some element or attribute is ignored, or treated as some other value, or
handled as if it was something else, this refers only to the
processing of the node after it is in the DOM. A user agent must not
mutate the DOM in such situations.要素や属性が無視される、他の値であるとして扱う、
何か他のものであるかのように扱うと述べられている時は、その節点が DOM
に入った後の処理についてのみ言及しています。利用者エージェントは、そのような状況で DOM
を変異させてはなりません。
The term text node refers to any Text
node, including CDATASection nodes; specifically, any
Node with node type TEXT_NODE (3)
or CDATA_SECTION_NODE (4). [DOM3CORE]用語テキスト節点は、任意の
Text 節点を指し、 CDATASection 節点を含みます。
厳密には、節点型が TEXT_NODE (3) か CDATA_SECTION_NODE
(4) の任意の Node を指します。
[DOM3CORE]
2.1.3 Scripting2.1.3 スクリプティング
The construction "a Foo object", where
Foo is actually an interface, is sometimes used instead
of the more accurate "an object implementing the interface
Foo".「Foo オブジェクト」という構文 (Foo
は実際には界面) を時々使いますが、より正確な「界面 Foo
を実装しているオブジェクト」の代わりに用いています。
A DOM attribute is said to be getting when its value is
being retrieved (e.g. by author script), and is said to be
setting when a new value is assigned to it.DOM 属性は、その値が (例えば著者のスクリプトによって) 取り出される時に取得時であるといい、
新たな値が割り当てられる時に設定時であるといいます。
If a DOM object is said to be live, then that means
that any attributes returning that object must always return the
same object (not a new object each time), and the attributes and
methods on that object must operate on the actual underlying data,
not a snapshot of the data.DOM オブジェクトが生きているという場合、
そのオブジェクトを返す属性は常に同じオブジェクトを返さなければならない
(毎回新しいオブジェクトを返すのではなく) 上に、
そのオブジェクトの属性やメソッドがそのオブジェクトの裏にある実際のデータのスナップ写真ではなく、
データそのものに対して操作されなければならないことを意味します。
The terms fire and dispatch are used
interchangeably in the context of events, as in the DOM Events
specifications. [DOM3EVENTS]用語発火・発送は、事象についての文脈では、
DOM 事象仕様書にある通りに、交換可能なものとして用います。 [DOM3EVENTS]
2.1.4 Plugins2.1.4 プラグイン
The term plugin is used to mean any content handler,
typically a third-party content handler, for Web content types that
are not supported by the user agent natively, or for content types
that do not expose a DOM, that supports rendering the content as
part of the user agent's interface.用語プラグインは、任意の内容取扱器を意味して使います。
典型的には利用者エージェントが生で対応していない Web
内容型のためや DOM を晒さない内容型のための、第3者による内容取扱器で、
利用者エージェントの界面の一部として内容をレンダリングすることに対応しているものです。
One example of a plugin would be a PDF viewer
that is instantiated in a browsing context when the
user navigates to a PDF file. This would count as a plugin
regardless of whether the party that implemented the PDF viewer
component was the same as that which implemented the user agent
itself. However, a PDF viewer application that launches separate
from the user agent (as opposed to using the same interface) is not
a plugin by this definition.プラグインの一例は、利用者が PDF ファイルに操縦した時に閲覧文脈中に実現値化される PDF 表示器です。この場合、PDF 表示器部品が利用者エージェント自体と同じ者により実装されたかどうかを問わず、
プラグインと考えます。しかし、 PDF 表示器アプリケーションが利用者エージェントとは
(同じ界面を使わずに) 別に起動する場合には、この定義ではプラグインではありません。
This specification does not define a mechanism for
interacting with plugins, as it is expected to be user-agent- and
platform-specific. Some UAs might opt to support a plugin mechanism
such as the Netscape Plugin API; others might use remote content
converters or have built-in support for certain types. [NPAPI]この仕様書は、プラグインと対話する仕組みを定義しません。そのような仕組みは利用者エージェントや環境に依存すると思われるからです。
ある利用者エージェントは Netscape プラグイン API のようなプラグインの仕組みに対応したいかもしれません。
他の利用者エージェントは遠隔内容変換器を使ったり、ある型については組み込みで対応したりするかもしれません。
Browsers should take extreme care when
interacting with external content intended for plugins. When third-party software is run with
the same privileges as the user agent itself, vulnerabilities in the
third-party software become as dangerous as those in the user
agent.ブラウザは、プラグインを想定した外部の内容と対話する時に特に十分な注意を払うべきです。
第3者ソフトウェアが利用者エージェント自体と同じ特権で走る時は、
第3者ソフトウェアの脆弱性が利用者エージェントの脆弱性と同じくらい危険となります。
2.1.5 Character encodings2.1.5 文字符号化
An ASCII-compatible character encoding is one that is
a superset of US-ASCII (specifically, ANSI_X3.4-1968) for bytes in
the set 0x09, 0x0A, 0x0C, 0x0D, 0x20 - 0x22, 0x26, 0x27, 0x2C -
0x3F, 0x41 - 0x5A, and 0x61 - 0x7A.
All diagrams, examples, and notes in this specification are
non-normative, as are all sections explicitly marked non-normative.
Everything else in this specification is normative.この仕様書のすべての図、例示、注意書き、ならびに規定の一部ではないと明記したすべての節は、
規定の一部ではありません。
この仕様書のそれ以外の部分はすべて規定の一部です。
The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in the normative parts of this document are to be
interpreted as described in RFC2119. For readability, these words do
not appear in all uppercase letters in this specification. [RFC2119]この文書の規定の部分にあるキーワード「しなければなりません」、
「してはなりません」、
「必須です」、「するべきです」、
「するべきではありません」、
「推奨します」、「して構いません」、
「任意です」は、 RFC 2119 で説明されているように解釈します。
この仕様書の原文では、
可読性の観点から、
これらの語の原語のすべて大文字による表記は行っていません。
[RFC2119]
Requirements phrased in the imperative as part of algorithms
(such as "strip any leading space characters" or "return false and
abort these steps") are to be interpreted with the meaning of the
key word ("must", "should", "may", etc) used in introducing the
algorithm.算法の一部として動作の指示の形で (原文では命令形で) 記述された要件
(例えば「先頭の間隔文字をすべて除去します」や「偽を返し、これらの段階を停止します」)
は、算法を紹介するに当たって使われたキーワード (しなければなりません、
するべきです、して構いませんなど) の意味により解釈します。
This specification describes the conformance criteria for user
agents (relevant to implementors) and documents (relevant to
authors and authoring tool implementors).この仕様書は、利用者エージェントに対する適合性基準 (実装者に関係するもの)
と文書に対する適合性基準 (著者や著述ツール実装者に関係するもの) を説明します。
There is no implied relationship between document
conformance requirements and implementation conformance
requirements. User agents are not free to handle non-conformant
documents as they please; the processing model described in this
specification applies to implementations regardless of the
conformity of the input documents.文書適合性要件と実装適合性要件の間には暗示的な関係もありません。
利用者エージェントは不適合の文書を好きなように取り扱ってよいわけではありません。
入力文書の適合性の如何を問わず、この仕様書で説明する処理モデルが適用されます。
User agents fall into several (overlapping) categories with
different conformance requirements.利用者エージェントは異なった適合性要件を持つ複数の (重なり合った) 範疇に分類できます。
- Web browsers and other interactive user agentsWeb ブラウザその他の対話的利用者エージェント
-
Web browsers that support XHTML must process
elements and attributes from the HTML namespace found
in XML documents as described in this specification,
so that users can interact with them, unless the semantics of
those elements have been overridden by other specifications.XHTML に対応する Web ブラウザは、
XML 文書中に見える HTML
名前空間の要素や属性をこの仕様書で説明するように処理することにより、
利用者がそれらと対話できるようにしなければなりません。ただし、
それらの要素の意味が他の仕様書により上書きされている場合を除きます。
A conforming XHTML processor would, upon
finding an XHTML script element in an XML document,
execute the script contained in that element. However, if the
element is found within an XSLT transformation sheet (assuming the
UA also supports XSLT), then the processor would instead treat the
script element as an opaque element that forms part
of the transform.適合 XHTML 処理器は、 XML 文書中で XHTML script
要素を見つけた際に、その要素に含まれるスクリプトを実行することになります。しかし、
その要素が XSLT 変形シート中に見える場合には (利用者エージェントが XSLT
にも対応しているとすると)、処理器は通常の処理の代わりに script 要素を変形の一部を形成する不透明な要素として扱うことになります。
Web browsers that support HTML must
process documents labeled as text/html as described
in this specification, so that users can interact with them.HTML に対応する Web
ブラウザは、 text/html と札付けされた文書をこの仕様書で説明するように処理することにより、
利用者がそれらと対話できるようにしなければなりません。
- Non-interactive presentation user agents非対話的提示利用者エージェント
-
User agents that process HTML and XHTML documents purely to
render non-interactive versions of them must comply to the same
conformance criteria as Web browsers, except that they are exempt
from requirements regarding user interaction.HTML 文書と XHTML 文書を純粋にその非対話的な版をレンダリングするために処理する利用者エージェントは、
利用者との対話に関する要件を除き、 Web ブラウザと同じ基準に従わなければなりません。
Typical examples of non-interactive presentation
user agents are printers (static UAs) and overhead displays
(dynamic UAs). It is expected that most static non-interactive
presentation user agents will also opt to lack scripting support.非対話的提示利用者エージェントの典型的な例は印刷機 (静的利用者エージェント)
や頭上表示機 (動的利用者エージェント) です。ほとんどの静的非対話的提示利用者エージェントはスクリプティング対応を欠くことをも選ぶと思われます。
A non-interactive but dynamic presentation UA
would still execute scripts, allowing forms to be dynamically
submitted, and so forth. However, since the concept of "focus" is
irrelevant when the user cannot interact with the document, the UA
would not need to support any of the focus-related DOM APIs.それでも、非対話的ながら動的な提示の利用者エージェントはスクリプトを実行し、
フォームを動的に提出することを許すなどすることでしょう。しかし、
利用者が文書に対話できない時には「焦点」の概念は無関係となるので、
利用者エージェントは焦点に関係する DOM API のいずれにも対応する必要がありません。
- User agents with no scripting supportスクリプティングに対応しない利用者エージェント
-
Implementations that do not support scripting (or which have
their scripting features disabled entirely) are exempt from
supporting the events and DOM interfaces mentioned in this
specification. For the parts of this specification that are
defined in terms of an events model or in terms of the DOM, such
user agents must still act as if events and the DOM were
supported.スクリプティングに対応しない (またはスクリプティング機能が完全に無効化されている)
実装は、この仕様書で言及している事象や DOM 界面への対応を免除されます。
この仕様書で事象モデルや DOM を用いて定義されている部分に関しては、
この種の利用者エージェントもやはり事象や DOM に対応しているかのように動作しなければなりません。
Scripting can form an integral part of an
application. Web browsers that do not support scripting, or that
have scripting disabled, might be unable to fully convey the
author's intent.スクリプティングはアプリケーションの不可分の部分を形成することがあります。
スクリプティングに対応しない、またはスクリプティングを無効化された利用者エージェントは、
著者の意図を完全に伝えることができないかもしれません。
- Conformance checkers適合性検査器
-
Conformance checkers must verify that a document conforms to
the applicable conformance criteria described in this
specification. Automated conformance checkers are exempt from
detecting errors that require interpretation of the author's
intent (for example, while a document is non-conforming if the
content of a blockquote element is not a quote,
conformance checkers running without the input of human judgement
do not have to check that blockquote elements only
contain quoted material).適合性検査器は、文書がこの仕様書中で説明する適用可能な適合性基準に適合するかを検証しなければなりません。
自動化された適合性検査器については、著者の意図の解釈が必要な誤りの検出を免除します
(例えば、 blockquote 要素の内容が引用ではない文書は不適合ですが、
人間の判断の入力なしで走っている適合性検査器は
blockquote
要素が引用されたものだけを含むかを検査しなくてかまいません)。
Conformance checkers must check that the input document
conforms when parsed without a browsing context
(meaning that no scripts are run, and that the parser's
scripting flag is disabled), and should also check
that the input document conforms when parsed with a browsing
context in which scripts execute, and that the scripts
never cause non-conforming states to occur other than transiently
during script execution itself. (This is only a "SHOULD" and not a
"MUST" requirement because it has been proven to be impossible. [HALTINGPROBLEM])適合性検査器は、閲覧文脈なしの時に (つまりスクリプトが走らず、
構文解析器のスクリプティング旗が無効化された状態で)
入力文書が適合するかを検査しなければならず、スクリプトを実行する閲覧文脈中で構文解析する時に入力文書が適合するか、
スクリプトが決して不適合状態を引き起こさないか (スクリプト自体の実行中の過渡状態を除きます。)
も検査するべきです。 (これは不可能であると証明されているので、
「するべき」要件であり、「しなければならない」要件ではありません。 [HALTINGPROBLEM])
The term "HTML5 validator" can be used to refer to a
conformance checker that itself conforms to the applicable
requirements of this specification.用語「HTML5 妥当性検査器」は、それ自体がこの仕様書の適用可能な要件に適合する適合性検査器を指して使うことができます。
XML DTDs cannot express all the conformance requirements of
this specification. Therefore, a validating XML processor and a
DTD cannot constitute a conformance checker. Also, since neither
of the two authoring formats defined in this specification are
applications of SGML, a validating SGML system cannot constitute
a conformance checker either.XML DTD はこの仕様書のすべての適合性要件を表現することができません。
従って、妥当性を検証する XML 処理器 と DTD は適合性検査器が適合性検査器を構成することはできません。
また、この仕様書が定義する2つの著述書式のどちらも SGML の応用ではありませんから、
妥当性を検証する SGML システムが適合性検査器を構成することはできません。
To put it another way, there are three types of conformance
criteria:別の言い方をすると、適合性基準には次の3種類があります。
Criteria that can be expressed in a DTD.DTD で表現できる基準
Criteria that cannot be expressed by a DTD, but can still be
checked by a machine.DTD で表現できないが、それでも機械で検査できる基準
Criteria that can only be checked by a human.人間だけが検査できる基準
A conformance checker must check for the first two. A simple
DTD-based validator only checks for the first class of errors and
is therefore not a conforming conformance checker according to
this specification.適合性検査器ははじめの2つを検査しなければなりません。
単純な DTD を基にした妥当性検証器は1つ目の級の誤りしか検査しませんから、
この仕様書による適合妥当性検証器ではありません。
- Data mining toolsデータ・マイニング・ツール
-
Applications and tools that process HTML and XHTML documents
for reasons other than to either render the documents or check
them for conformance should act in accordance to the semantics of
the documents that they process.文書のレンダリングや適合性の検査以外の理由で HTML 文書や XHTML
文書を処理するアプリケーションやツールは、その処理する文書の意味に従って作用するべきです。
A tool that generates document outlines but increases the nesting
level for each paragraph and does not increase the nesting level
for each section would not be conforming.文書の輪郭を生成するツールで、
入れ子の水準を段落毎に増加させ、章節毎には増加させないものは、
適合しません。
- Authoring tools and markup generators著述ツールとマーク付け生成器
-
Authoring tools and markup generators must generate conforming
documents. Conformance criteria that apply to authors also apply
to authoring tools, where appropriate.著述ツールとマーク付け生成器は、適合文書を生成しなければなりません。
著者に適用される適合性基準は著述ツールにも適当なら適用されます。
Authoring tools are exempt from the strict requirements of
using elements only for their specified purpose, but only to the
extent that authoring tools are not yet able to determine author
intent.著述ツールは要素をその指定された目的のみに用いるという厳密な要件を免除されますが、
これは著述ツールがまだ著者の意図を判断することができない範囲内に限ります。
For example, it is not conforming to use an
address element for arbitrary contact information;
that element can only be used for marking up contact information
for the author of the document or section. However, since an
authoring tool is likely unable to determine the difference, an
authoring tool is exempt from that requirement.例えば、 address 要素を任意の連絡先情報に使うことは適合しません。
この要素は文書や章節の著者の連絡先情報のマーク付けにのみ使うことができます。
しかし、著述ツールはこの違いを判断できないでしょうから、
著述ツールはこの要件を免除されます。
In terms of conformance checking, an editor is
therefore required to output documents that conform to the same
extent that a conformance checker will verify.このため、適合性検査に関しては、編集器は適合性検査器が検証できるのと同程度に適合する文書を出力されることが要求されます。
When an authoring tool is used to edit a non-conforming
document, it may preserve the conformance errors in sections of
the document that were not edited during the editing session
(i.e. an editing tool is allowed to round-trip erroneous
content). However, an authoring tool must not claim that the
output is conformant if errors have been so preserved.著述ツールを不適合の文書を編集するために用いる時には、
その編集セッションで編集しなかった文書中の部分の適合性誤りを保持して構いません
(つまり、編集ツールは誤った内容を往復することが認められます)。しかし、
著述ツールは誤りが保持される場合に出力が適合していると主張してはなりません。
Authoring tools are expected to come in two broad varieties:
tools that work from structure or semantic data, and tools that
work on a What-You-See-Is-What-You-Get media-specific editing
basis (WYSIWYG).著述ツールは2つに大きく分けられると思われます。1つは構造・意味的なデータに対して働くもので、
もう1つは見たままな感じの媒体指定の編集 (WYSIWYG) に基づき働くものです。
The former is the preferred mechanism for tools that author
HTML, since the structure in the source information can be used to
make informed choices regarding which HTML elements and attributes
are most appropriate.前者は原始構造中の構造を HTML のどの要素や属性が最も適切かに関して十分な選択を行うために使うことができるので、
HTML を著述するツールにはより好ましい仕組みです。
However, WYSIWYG tools are legitimate. WYSIWYG tools should use
elements they know are appropriate, and should not use elements
that they do not know to be appropriate. This might in certain
extreme cases mean limiting the use of flow elements to just a few
elements, like div, b, i,
and span and making liberal use of the style attribute.しかし、 WYSIWYG ツールは合法です。 WYSIWYG ツールは適切であると知っている要素を使うべきで、
適切ではないと知っている要素を使うべきではありません。
これは、極端な場合に、使用する流れ要素を div、
b、
i、span のような少数の要素に制限し、 style
属性を使いまくるようにすることを意味するかもしれません。
All authoring tools, whether WYSIWYG or not, should make a best
effort attempt at enabling users to create well-structured,
semantically rich, media-independent content.すべての著述ツールは、 WYSIWYG か否かに関わらず、
よく構造化され、意味的に豊かな、媒体非依存の内容を利用者が作成できるようにするため、
最大限の努力を行うべきです。
Some conformance requirements are phrased as requirements on
elements, attributes, methods or objects. Such requirements fall
into two categories: those describing content model restrictions,
and those describing implementation behavior. The former category
of requirements are requirements on documents and authoring
tools. The second category are requirements on user agents.いくつかの適合性要件は属性やメソッドやオブジェクトの要件として説明されています。
そのような要件は、2つの範疇に分類されます。1つは内容モデルの制限を説明するもので、
もう1つは実装の動作を説明するものです。前者の範疇の要件は文書や著述ツールの要件です。
後者の範疇は利用者エージェントの要件です。
Conformance requirements phrased as algorithms or specific steps
may be implemented in any manner, so long as the end result is
equivalent. (In particular, the algorithms defined in this
specification are intended to be easy to follow, and not intended to
be performant.)算法や特定の段階として説明されている適合性要件は、
最終的な結果が等価である限り、任意の方法で実装して構いません。
(特に、この仕様書で定義されている算法は追うのを簡単にしており、
高性能であることを目指してはいません。)
User agents may impose
implementation-specific limits on otherwise unconstrained inputs,
e.g. to prevent denial of service attacks, to guard against running
out of memory, or to work around platform-specific limitations.利用者エージェントは、サービス拒否攻撃を防ぐため、
記憶容量を使い尽くすことを防ぐため、
あるいは環境特有の制限に対応するためなどの目的で、
別段の制約のない入力に対して実装特有の制限を設けて構いません。
For compatibility with existing content and prior specifications,
this specification describes two authoring formats: one based on XML
(referred to as XHTML5), and
one using a custom format inspired by SGML
(referred to as HTML5). Implementations may
support only one of these two formats, although supporting both is
encouraged.既存の内容や以前の仕様書との互換性のため、この仕様書は2つの著述書式を説明します。
1つは XML に基づくもので (XHTML5
と呼びます)、もう1つは SGML に着想を得たカスタム書式を使うもの (HTML5 と呼びます) です。実装者はこれら2つの書式の1つだけに対応して構いませんが、
両方に対応することをおすすめします。
XHTML documents (XML
documents using elements from the HTML
namespace) that use the new features described in this
specification and that are served over the wire (e.g. by HTTP) must
be sent using an XML MIME type such as application/xml
or application/xhtml+xml and must not be served as
text/html. [RFC3023]XHTML 文書 (XML 文書で、 HTML 名前空間の要素を用いるもの) であって、
この仕様書が説明する新しい機能を使い、
ネットワークを通じて (例えば HTTP で) 供給されるものは、
application/xml や application/xhtml+xml
のような XML MIME 型を使って送られなければならず、
text/html として供給されてはなりません。 [RFC3023]
Such XML documents may contain a DOCTYPE if desired,
but this is not required to conform to this specification.そのような XML 文書は、望ましければ DOCTYPE
を含んで構いませんが、この仕様書に適合するために必要なわけではありません。
According to the XML specification, XML processors
are not guaranteed to process the external DTD subset referenced in
the DOCTYPE. This means, for example, that using entity references
for characters in XHTML documents is unsafe (except for <, >, &, " and
').XML 仕様書によれば、 XML 処理器が DOCTYPE 中で参照されている外部 DTD
部分集合を処理することは保証されていません。これは、例えば XHTML 文書中で文字を参照するために実体参照を使うことは (<、
>、&、"、 ' を除き)
安全ではないことを意味しています。
HTML
documents, if they are served over the wire (e.g. by HTTP)
must be labeled with the text/html MIME type.HTML 文書は、ネットワークを通じて (例えば
HTTP で) 供給される場合、 text/html MIME 型と札付けされなければなりません。
The language in this specification assumes
that the user agent expands all entity references, and therefore
does not include entity reference nodes in the DOM. If user agents
do include entity reference nodes in the DOM, then user agents must
handle them as if they were fully expanded when implementing this
specification. For example, if a requirement talks about an
element's child text nodes, then any text nodes that are children of
an entity reference that is a child of that element would be used as
well. Entity references to unknown entities must be treated as if
they contained just an empty text node for the purposes of the
algorithms defined in this specification.この仕様書の言語は、利用者エージェントがすべての実体参照を展開し、
従って DOM 中には実体参照節点が含まれないことを仮定しています。
利用者エージェントが DOM 中に実体参照節点を含めるという場合には、
利用者エージェントはこの仕様書を実装する時には実体参照節点が完全に展開されているかのように取り扱わなければなりません。
例えば、ある要件が要素の子供テキスト節点について反している場合には、
その要素の子供の実体参照の子供であるテキスト節点も同じように使われることになります。
未知の実体に対する実体参照は、この仕様書で定義する算法に関しては、
単に空のテキスト節点を含むかのように扱わなければなりません。
2.2.1 Dependencies2.2.1 依存性
This specification relies on several other underlying
specifications.この仕様書は、他のいくつかの下位の仕様書に依存しています。
- XML
-
Implementations that support XHTML5 must support some version
of XML, as well as its corresponding namespaces specification,
because XHTML5 uses an XML serialization with namespaces. [XML] [XMLNAMES]XHTML5 に対応する実装は、 XML のいずれかの版と、
それに対応する名前空間仕様書に対応しなければなりません。
XHTML5 は名前空間を用いた XML 直列化を使います。
[XML]
[XMLNAMES]
- DOM
-
The Document Object Model (DOM) is a representation — a
model — of a document and its content. The DOM is not just
an API; the conformance criteria of HTML implementations are
defined, in this specification, in terms of operations on the DOM.
[DOM3CORE]文書オブジェクト・モデル (DOM) は、文書とその内容の表現 (モデル) です。
DOM は単なる API ではなく、この仕様書では HTML 実装の適合性基準を
DOM 上の操作として定義しています。 [DOM3CORE]
Implementations must support some version of DOM Core and DOM
Events, because this specification is defined in terms of the DOM,
and some of the features are defined as extensions to the DOM Core
interfaces. [DOM3CORE] [DOM3EVENTS]実装は、 DOM 中核と DOM 事象のそれぞれのいずれかの版に対応しなければなりません。
この仕様書は DOM を使って定義を行っていますし、この仕様書で定義するいくつかの機能は DOM
中核界面に対する拡張となっています。 [DOM3CORE] [DOM3EVENTS]
- ECMAScript
-
Implementations that use ECMAScript to implement the APIs
defined in this specification must implement them in a manner
consistent with the ECMAScript Bindings defined in the Web IDL
specification, as this specification uses that specification's
terminology. [WebIDL]この仕様書で定義する API を実装するために ECMAScript を使用する実装は、
Web IDL 仕様書で定義されている ECMAScript 束縛と整合的な方法で実装しなければなりません。
この仕様書は Web IDL 仕様書の用語法を使っているからです。 [WebIDL]
- Media Queries媒体照会
-
Implementations must support some version of the Media Queries
language. [MQ]実装は、媒体照会言語のいずれかの版を実装しなければなりません。
[MQ]
This specification does not require support of any particular
network transport protocols, style sheet language, scripting
language, or any of the DOM and WebAPI specifications beyond those
described above. However, the language described by this
specification is biased towards CSS as the styling language,
ECMAScript as the scripting language, and HTTP as the network
protocol, and several features assume that those languages and
protocols are in use.この仕様書は、特定のネットワーク輸送プロトコル、スタイル・シート言語、
スクリプティング言語の仕様書への対応を要求しませんし、
ここまでに述べた内容以上には DOM や WebAPI の仕様書への対応も要求しません。
しかし、この仕様書で説明する言語は、
スタイル付け言語として CSS、スクリプティング言語として ECMAScript、
ネットワーク・プロトコルとして HTTP に偏向しており、
いくつかの機能はこれらの言語やプロトコルが使われることを想定しています。
This specification might have certain additional
requirements on character encodings, image formats, audio formats,
and video formats in the respective sections.この仕様書は、文字符号化、画像書式、音声書式、動画書式に関して、
それぞれに関する節で追加の要件を示すかもしれません。
2.2.2 Features defined in other specifications
this section will be removed at some point
Some elements are defined in terms of their DOM
textContent attribute. This is an attribute
defined on the Node interface in DOM3 Core. [DOM3CORE]
The interface DOMTimeStamp is defined in
DOM3 Core. [DOM3CORE]
The rules for handling alternative
style sheets are defined in the CSS object model specification. [CSSOM]
See http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.html?content-type=text/html;%20charset=utf-8
This section will eventually be removed in favour of WebIDL.
A lot of arrays/lists/collections
in this spec assume zero-based indexes but use the term "indexth" liberally. We should define those to be
zero-based and be clearer about this.
Unless otherwise specified, if a DOM attribute that is a floating
point number type (float) is assigned an
Infinity or Not-a-Number value, a NOT_SUPPORTED_ERR exception must be
raised.
Unless otherwise specified, if a method with an argument that is a
floating point number type (float) is passed
an Infinity or Not-a-Number value, a NOT_SUPPORTED_ERR exception must be
raised.
Unless otherwise specified, if a method is passed fewer
arguments than is defined for that method in its IDL definition,
a NOT_SUPPORTED_ERR exception must be
raised.
Unless otherwise specified, if a method is passed more arguments than
is defined for that method in its IDL definition, the excess
arguments must be ignored.
2.3 Case-sensitivity and string comparison2.3 大文字・小文字と文字列の比較
This specification defines several comparison operators for
strings.この仕様書は文字列に対する比較演算子をいくつか定義します。
Comparing two strings in a case-sensitive manner means
comparing them exactly, codepoint for codepoint.2つの文字列を大文字・小文字を区別する方法で比較するとは、
両者を正確に、符号位置それぞれについて比較することを意味します。
Comparing two strings in a ASCII case-insensitive
manner means comparing them exactly, codepoint for codepoint, except
that the characters in the range U+0041 .. U+005A (i.e. LATIN
CAPITAL LETTER A to LATIN CAPITAL LETTER Z) and the corresponding
characters in the range U+0061 .. U+007A (i.e. LATIN SMALL LETTER A
to LATIN SMALL LETTER Z) are considered to also match.2つの文字列を ASCII 大文字・小文字を区別しない方法で比較するとは、
両者を正確に、符号位置それぞれについて比較しますが、範囲 U+0041 ～ U+005A (つまり
LATIN CAPITAL LETTER A から LATIN CAPITAL LETTER Z) の文字と範囲 U+0061 ～
U+007A (つまり LATIN SMALL LETTER A から LATIN SMALL LETTER Z)
の対応する文字も一致するものと考えることを意味します。
Comparing two strings in a compatibility caseless
manner means using the Unicode compatibility caseless match
operation to compare the two strings. [UNICODECASE]2つの文字列を大文字・小文字互換性不区別な方法で比較するとは、
2つの文字列の比較に Unicode 大文字・小文字互換性不区別演算を使うことを意味します。 [UNICODECASE]
Converting a string to
uppercase means replacing all characters in the range U+0061
.. U+007A (i.e. LATIN SMALL LETTER A to LATIN SMALL LETTER Z) with
the corresponding characters in the range U+0041 .. U+005A
(i.e. LATIN CAPITAL LETTER A to LATIN CAPITAL LETTER Z).文字列を大文字に変換するとは、
範囲 U+0061 ～
U+007A (つまり LATIN SMALL LETTER A から LATIN SMALL LETTER Z)
の文字をすべて範囲 U+0041 ～ U+005A (つまり
LATIN CAPITAL LETTER A から LATIN CAPITAL LETTER Z) の対応する文字に置き換えることを意味します。
Converting a string to
lowercase means replacing all characters in the range U+0041
.. U+005A (i.e. LATIN CAPITAL LETTER A to LATIN CAPITAL LETTER Z)
with the corresponding characters in the range U+0061 .. U+007A
(i.e. LATIN SMALL LETTER A to LATIN SMALL LETTER Z).文字列を小文字に変換するとは、範囲 U+0041 ～ U+005A (つまり
LATIN CAPITAL LETTER A から LATIN CAPITAL LETTER Z)
の文字をすべて範囲 U+0061 ～
U+007A (つまり LATIN SMALL LETTER A から LATIN SMALL LETTER Z)
の対応する文字に置き換えることを意味します。
A string pattern is a prefix match
for a string s when pattern
is not longer than s and truncating s to pattern's length leaves the
two strings as matches of each other.文字列 pattern が文字列 s
の接頭辞一致であるのは、
pattern が s より長くなく、
s を pattern の長さに短縮すると両文字列が互いに一致する時です。
2.4 Common microsyntaxes2.4 共通マイクロ構文
There are various places in HTML that accept particular data
types, such as dates or numbers. This section describes what the
conformance criteria for content in those formats is, and how to
parse them.HTML 中のいろいろな場所で、日付や数値のような特定のデータ型を使うことができます。
この節では、そのような書式の内容の適合基準は何か、
どう構文解析するかを説明します。
Need to go through the whole spec and make sure
all the attribute values are clearly defined either in terms of
microsyntaxes or in terms of other specs, or as "Text" or some
such.仕様書全体について、すべての属性値がマイクロ構文を使ってか他の仕様書を使ってか「文章」などとして定義されるようにする必要があります。
2.4.1 Common parser idioms2.4.1 構文解析器共通慣用句
The space characters, for the
purposes of this specification, are U+0020 SPACE, U+0009 CHARACTER
TABULATION (tab), U+000A LINE FEED (LF), U+000C FORM FEED (FF), and
U+000D CARRIAGE RETURN (CR).間隔文字は、
この仕様書においては、 U+0020 SPACE, U+0009 CHARACTER
TABULATION (tab)、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、 U+000D
CARRIAGE RETURN (CR) です。
The White_Space characters are
those that have the Unicode property "White_Space". [UNICODE]White_Space 文字は、
Unicode 特性「White_Space」を持つ文字です。 [UNICODE]
Some of the micro-parsers described below follow the pattern of
having an input variable that holds the string
being parsed, and having a position variable
pointing at the next character to parse in input.これ以降で説明するマイクロ構文解析器のいくつかは、構文解析される文字列を保持する
input 変数を持ち、 input
中で次に構文解析する文字を指す position
変数を持つというパターンに従っています。
For parsers based on this pattern, a step that requires the user
agent to collect a sequence of characters means that the
following algorithm must be run, with characters
being the set of characters that can be collected:このパターンに従う構文解析器において、利用者エージェントが文字列を集めることを要求している段階は、
次の算法を、 characters
が収集できる文字の集合であるとして実行しなければならないことを意味しています。
Let input and position be the same variables as those of the same
name in the algorithm that invoked these steps.input と position
を、これらの段階を呼び出した算法中の同名の変数と同じものとします。
Let result be the empty string.result を空文字列とします。
While position doesn't point past the
end of input and the character at position is one of the characters, append that character to the end of result and advance position to
the next character in input.position が input の終わりの更に先を指しておらず、 position
の文字が characters のうちの1つである間、
その文字を result の終わりに追加し、 position を input の次の文字に進めます。
Return result.result を返します。
The step skip whitespace means that the user agent
must collect a sequence of characters that are space characters. The step skip
White_Space characters means that the user agent must
collect a sequence of characters that are
White_Space characters. In both cases, the collected
characters are not used. [UNICODE]段階空白を飛ばすは、
利用者エージェントが空白文字であるような文字の列を収集しなければならないことを意味します。
段階 White_Space 文字を飛ばすは、
利用者エージェントが
White_Space
文字であるような文字の列を収集しなければならないことを意味します。
いずれの場合も、収集した文字は使いません。 [UNICODE]
When a user agent is to strip line breaks from a
string, the user agent must remove any U+000A LINE FEED (LF) and
U+000D CARRIAGE RETURN (CR) characters from that string.利用者エージェントが文字列から改行を除去する場合、
当該文字列から U+000A LINE FEED (LF) 文字と
U+000D CARRIAGE RETURN (CR) 文字を削除しなければなりません。
The codepoint length of a string is the number of
Unicode codepoints in that string.文字列の符号位置長は、当該文字列中の Unicode
符号位置の数です。
2.4.2 Boolean attributes2.4.2 ブール型属性
A number of attributes in HTML5 are boolean attributes. The presence of a boolean
attribute on an element represents the true value, and the absence
of the attribute represents the false value.HTML5 の数々の属性はブール型属性です。要素にブール型属性が存在すると真の値を表し、
存在しないと偽の値を表します。
If the attribute is present, its value must either be the empty
string or a value that is an ASCII case-insensitive
match for the attribute's canonical name, with no leading or
trailing whitespace.属性が存在する場合、その値は空文字列か、または
ASCII 大文字・小文字不区別で属性の正準名と一致するような
(先頭にも末尾にも空白がない) 値のいずれかでなければなりません。
2.4.3 Numbers2.4.3 数値
2.4.3.1 Unsigned integers2.4.3.1 符号無し整数
A string is a valid non-negative integer if it
consists of one of more characters in the range U+0030 DIGIT ZERO
(0) to U+0039 DIGIT NINE (9).文字列は、範囲 U+0030 DIGIT ZERO (0) ～ U+0039 DIGIT NINE (9)
の文字1文字以上で構成される場合、妥当な非負整数です。
The rules for parsing non-negative integers are as
given in the following algorithm. When invoked, the steps must be
followed in the order given, aborting at the first step that returns
a value. This algorithm will either return zero, a positive integer,
or an error. Leading spaces are ignored. Trailing spaces and indeed
any trailing garbage characters are ignored.非負整数を構文解析する規則は次の算法で与えられるものです。
この算法が呼び出された時には、与えられた順に段階に従い、
値を返す最初の段階で中断しなければなりません。
この算法は零か正整数か誤りを返します。
先頭の間隔は無視されます。末尾の空白、というかごみ文字列はすべて無視されます。
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Let value have the value 0.value を値 0 にします。
Skip whitespace. 空白を読み飛ばします。
If position is past the end of input, return an error.position が input の終わりを過ぎていれば、誤りを返します。
If the next character is not one of U+0030 DIGIT ZERO (0)
.. U+0039 DIGIT NINE (9), then return an error.次の文字が U+0030 DIGIT ZERO (0) 〜 U+0039
DIGIT NINE (9) のうちの1つでない場合、誤りを返します。
-
If the next character is one of U+0030 DIGIT ZERO (0) .. U+0039
DIGIT NINE (9):次の文字が U+0030 DIGIT ZERO (0) 〜 U+0039
DIGIT NINE (9) のうちの1つである場合:
Multiply value by ten.value を10倍します。
Add the value of the current character (0..9) to value.現在の文字の値 (0〜9) を value に加えます。
Advance position to the next
character.position を次の文字に進めます。
If position is not past the end of input, return to the top of step 7 in the overall
algorithm (that's the step within which these substeps find
themselves).position が input の終わりを過ぎていなければ、
算法全体の段階 7 (これらの部分段階自体が含まれている段階) の先頭に返ります。
Return value.value を返します。
2.4.3.2 Signed integers2.4.3.2 符号付き整数
A string is a valid integer if it consists of one of
more characters in the range U+0030 DIGIT ZERO (0) to U+0039 DIGIT
NINE (9), optionally prefixed with a U+002D HYPHEN-MINUS ("-")
character.文字列は、範囲 U+0030 DIGIT ZERO (0) ～ U+0039 DIGIT NINE
(9) の文字1文字以上で構成され、任意選択で接頭辞として U+002D HYPHEN-MINUS ("-")
文字がある場合、妥当な整数です。
The rules for parsing integers are similar to the
rules for non-negative integers, and are as given in the following
algorithm. When invoked, the steps must be followed in the order
given, aborting at the first step that returns a value. This
algorithm will either return an integer or an error. Leading spaces
are ignored. Trailing spaces and trailing garbage characters are
ignored.整数を構文解析する規則は、非負整数用の規則と似ており、
次の算法により与えられます。これらの段階は、呼び出された場合、
与えられた順序に従い実行し、初めて値を返す段階で停止しなければなりません。
この算法は整数か誤りのいずれかを返します。先頭の間隔は無視されます。
末尾の間隔や末尾のごみ文字は無視されます。
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Let value have the value 0.value を値 0 にします。
Let sign have the value
"positive".sign を、「正」という値を持つようにします。
Skip whitespace. 空白を読み飛ばします。
If position is past the end of input, return an error.position が input の終わりを過ぎていれば、誤りを返します。
-
If the character indicated by position (the
first character) is a U+002D HYPHEN-MINUS ("-") character:position が示す文字 (最初の文字)
が U+002D HYPHEN-MINUS ("-") 文字である場合、
Let sign be "negative".sign を「負」とします。
Advance position to the next
character.position を次の文字に進めます。
If position is past the end of input, return an error.position が input の終わりを過ぎていれば、誤りを返します。
If the next character is not one of U+0030 DIGIT ZERO (0)
.. U+0039 DIGIT NINE (9), then return an error.次の文字が U+0030 DIGIT ZERO (0) 〜 U+0039
DIGIT NINE (9) のうちの1つでない場合、誤りを返します。
-
If the next character is one of U+0030 DIGIT ZERO (0) .. U+0039
DIGIT NINE (9):次の文字が U+0030 DIGIT ZERO (0) 〜 U+0039
DIGIT NINE (9) のうちの1つである場合:
Multiply value by ten.value を10倍します。
Add the value of the current character (0..9) to value.現在の文字の値 (0〜9) を value に加えます。
Advance position to the next
character.position を次の文字に進めます。
If position is not past the end of input, return to the top of step 9 in the overall
algorithm (that's the step within which these substeps find
themselves).position が input の終わりを過ぎていなければ、
算法全体の段階 9 (これらの部分段階自体が含まれている段階) の先頭に返ります。
If sign is "positive", return value, otherwise return 0-value.sign が「正」の場合、 value を返します。そうでない場合、
0-value を返します。
2.4.3.3 Real numbers2.4.3.3 実数
A string is a valid floating point number if it
consists of:文字列は、それが次のものから構成される場合、妥当な浮動小数点数です。
Optionally, a U+002D HYPHEN-MINUS ("-") character.U+002D HYPHEN-MINUS ("-") 文字 (任意選択)。
A series of one or more characters in the range U+0030 DIGIT
ZERO (0) to U+0039 DIGIT NINE (9).範囲 U+0030 DIGIT
ZERO (0) ～ U+0039 DIGIT NINE (9) の文字1文字以上の列。
Optionally:
任意選択で、
A single U+002E FULL STOP (".") character.単一の U+002E FULL STOP (".") 文字。
A series of one or more characters in the range U+0030 DIGIT
ZERO (0) to U+0039 DIGIT NINE (9).範囲 U+0030 DIGIT
ZERO (0) ～ U+0039 DIGIT NINE (9) の文字1文字以上の列。
Optionally:
任意選択で、
Either a U+0065 LATIN SMALL LETTER E character or a U+0045
LATIN CAPITAL LETTER E character.U+0065 LATIN SMALL LETTER E 文字か、 U+0045
LATIN CAPITAL LETTER E 文字のいずれか。
Optionally, a U+002D HYPHEN-MINUS ("-") character.U+002D HYPHEN-MINUS ("-") 文字 (任意選択)。
A series of characters in the range U+0030 DIGIT ZERO (0) to
U+0039 DIGIT NINE (9).範囲 U+0030 DIGIT ZERO (0) ～
U+0039 DIGIT NINE (9) の文字の列。
The rules for parsing floating point number values are
as given in the following algorithm. As with the previous
algorithms, when this one is invoked, the steps must be followed in
the order given, aborting at the first step that returns
something. This algorithm will either return a number or an
error. Leading spaces are ignored. Trailing spaces and garbage
characters are ignored.浮動小数点値を構文解析する規則は次の算法により与えられます。
前の算法と同様に、この算法が呼び出された時には、各段階に順に従い、何かを返した最初の段階で停止しなければなりません。
この算法は数か誤りを返します。先頭の間隔は無視します。
末尾の間隔やごみ文字は無視します。
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Let value have the value 1.value を、値 1 にします。
Let divisor have the value 1.divisor を、値 1 にします。
Let exponent have the value 1.exponent を、値 1 にします。
Skip whitespace. 空白を読み飛ばします。
If position is past the end of input, return an error.position が input の終わりを過ぎていれば、誤りを返します。
-
If the character indicated by position is a
U+002D HYPHEN-MINUS ("-") character:position で示される文字が
U+002D HYPHEN-MINUS ("-") の場合、
Change value and divisor to −1.value と divisor
を −1 に変えます。
Advance position to the next
character.position を次の文字に進めます。
If position is past the end of input, return an error.position が input の終わりを過ぎていれば、誤りを返します。
If the character indicated by position
is not one of U+0030 DIGIT ZERO (0) .. U+0039 DIGIT NINE (9), then
return an error.position
で示される文字が U+0030 DIGIT ZERO (0) ~ U+0039 DIGIT NINE (9)
のいずれかでない場合、誤りを返します。
Collect a sequence of characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9), and interpret the
resulting sequence as a base-ten integer. Multiply value by that integer.範囲 U+0030 DIGIT ZERO (0) ~ U+0039 DIGIT NINE (9)
の文字の列を集め、
得られた列を十進整数として解釈します。value にその整数を掛けます。
If position is past the end of input, return value.position が input
の終わりを超えている場合、 value を返します。
If the character indicated by position
is a U+002E FULL STOP ("."), run these substeps:position
が示す文字が U+002E FULL STOP (".")
の場合、次の部分算法を走らせます。
Advance position to the next
character.position を次の文字に進めます。
If position is past the end of input, or if the character indicated by position is not one of U+0030 DIGIT ZERO (0)
.. U+0039 DIGIT NINE (9), then return value.
Fraction loop: Multiply divisor
by ten.
Add the value of the current character interpreted as a
base-ten digit (0..9) divided by divisor, to
value.
Advance position to the next
character.position を次の文字に進めます。
If position is past the end of input, then return value.
If the character indicated by position
is one of U+0030 DIGIT ZERO (0) .. U+0039 DIGIT NINE (9), return
to the step labeled fraction loop in these
substeps.
If the character indicated by position
is a U+0065 LATIN SMALL LETTER E character or a U+0045 LATIN
CAPITAL LETTER E character, run these substeps:
Advance position to the next
character.position を次の文字に進めます。
If position is past the end of input, then return value.
-
If the character indicated by position is
a U+002D HYPHEN-MINUS ("-") character:position で示される文字が
U+002D HYPHEN-MINUS ("-") の場合、
Change exponent to −1.
Advance position to the next
character.position を次の文字に進めます。
If position is past the end of input, then return value.
If the character indicated by position
is not one of U+0030 DIGIT ZERO (0) .. U+0039 DIGIT NINE (9),
then return value.
Collect a sequence of characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9), and interpret the
resulting sequence as a base-ten integer. Multiply exponent by that integer.
Multiply value by ten raised to the
exponentth power.
Return value.value を返します。
2.4.3.4 Ratios2.4.3.4 比率
The algorithms described in this section are used by
the progress and meter elements.この節で説明する算法は、 progress 要素と
meter 要素で使います。
A valid denominator punctuation character is one of
the characters from the table below. There is a value
associated with each denominator punctuation character, as
shown in the table below.妥当な分母句読点文字は、
次の表の文字のいずれかです。次の表に示すように、各分母句読点文字には関連付けられた値があります。
| Denominator Punctuation Character分母句読点文字 |
Value値 |
|---|
| U+0025 PERCENT SIGN |
% |
100 |
| U+066A ARABIC PERCENT SIGN |
٪ |
100 |
| U+FE6A SMALL PERCENT SIGN |
﹪ |
100 |
| U+FF05 FULLWIDTH PERCENT SIGN |
％ |
100 |
| U+2030 PER MILLE SIGN |
‰ |
1000 |
| U+2031 PER TEN THOUSAND SIGN |
‱ |
10000 |
The steps for finding one or two numbers of a ratio in a
string are as follows:文字列中の比率の1つか2つの数字を探す段階は、次の通りです。
If the string is empty, then return nothing and abort these
steps.文字列が空である場合、何も返さず、これらの段階を停止します。
Find a number in the string according to the
algorithm below, starting at the start of the string.後述の算法に従い、文字列のはじめから開始して数を探します。
If the sub-algorithm in step 2 returned nothing or returned an
error condition, return nothing and abort these steps.段階 2 の部分算法が何も返さなかったか、誤り条件を返した場合には、
何も返さず、これらの段階を停止します。
Set number1 to the number returned by the
sub-algorithm in step 2.number1 を、段階 2 の部分算法が返した数とします。
Starting with the character immediately after the last one
examined by the sub-algorithm in step 2, skip all
White_Space characters in the string (this might match
zero characters).
If there are still further characters in the string, and the
next character in the string is a valid denominator
punctuation character, set denominator
to that character.文字列中に更に文字がまだある場合で、文字列中の次の文字が妥当な分母句読点文字である場合には、
denominator をその文字に設定します。
If the string contains any other characters in the range U+0030
DIGIT ZERO to U+0039 DIGIT NINE, but denominator was
given a value in the step 6, return nothing and abort these
steps.文字列が範囲 U+0030 DIGIT
ZERO ～ U+0039 DIGIT NINE の文字をまだ他に含んでいる場合で、
段階 6 で denominator に値が与えられた場合には、
何も返さず、これらの段階を停止します。
Otherwise, if denominator was given a value
in step 6, return number1 and denominator and abort these steps.そうでない場合、 denominator が段階 6
で値を与えられた場合には、 number1 と denominator を返し、これらの段階を停止します。
Find a number in the string again, starting
immediately after the last character that was examined by the
sub-algorithm in step 2.文字列中を更に数を探しますが、
段階 2 の部分算法で調べた最後の文字の直後からはじめます。
If the sub-algorithm in step 9 returned nothing or an error
condition, return number1 and abort these
steps.
Set number2 to the number returned by the
sub-algorithm in step 9.number2 を、段階 9 の部分算法が返した数とします。
Starting with the character immediately after the last one
examined by the sub-algorithm in step 9, skip all
White_Space characters in the string (this might match
zero characters).
If there are still further characters in the string, and the
next character in the string is a valid denominator
punctuation character, return nothing and abort these
steps.文字列中に更に文字がまだある場合で、文字列中の次の文字が妥当な分母句読点文字である場合、
何も返さず、これらの段階を停止します。
If the string contains any other characters in the range U+0030
DIGIT ZERO to U+0039 DIGIT NINE, return nothing and abort these
steps.文字列が範囲 U+0030 DIGIT
ZERO ～ U+0039 DIGIT NINE の文字をまだ他に含んでいる場合、
何も返さず、これらの段階を停止します。
Otherwise, return number1 and
number2.そうでない場合、 number1 と number2 を返します。
The algorithm to find a number is as follows. It is
given a string and a starting position, and returns either nothing,
a number, or an error condition.数を探すための算法は次の通りです。
この算法は、文字列と開始位置を与えられ、
何も返さないか、数を返すか、誤り条件を返すかのいずれかです。
Starting at the given starting position, ignore all characters
in the given string until the first character that is either a
U+002E FULL STOP or one of the ten characters in the range U+0030
DIGIT ZERO to U+0039 DIGIT NINE.与えられた開始位置からはじめ、 U+002E FULL STOP か、範囲 U+0030 DIGIT ZERO ～ U+0039
DIGIT NINE の10文字のいずれかであるような最初の文字まで、
その文字列中のすべての文字を無視します。
If there are no such characters, return nothing and abort these
steps.そのような文字がない場合には、何も返さず、これらの段階を停止します。
Starting with the character matched in step 1, collect all the
consecutive characters that are either a U+002E FULL STOP or one of
the ten characters in the range U+0030 DIGIT ZERO to U+0039 DIGIT
NINE, and assign this string of one or more characters to
string.段階 1 で一致した文字からはじめ、 U+002E FULL STOP か、範囲 U+0030 DIGIT ZERO ～
U+0039 DIGIT NINE の10文字のいずれかであるような連続した文字群をすべて集め、
この1文字以上の文字からなる文字列を string に代入します。
If string consists of just a single U+002E
FULL STOP character or if it contains more than one U+002E FULL
STOP character then return an error condition and abort these
steps.string が単一の U+002E FULL
STOP 文字のみで構成される場合や、複数の U+002E FULL
STOP 文字を含む場合は、誤り状態を返し、
これらの段階を停止します。
Parse string according to the rules
for parsing floating point number values, to obtain number. This step cannot fail (string is guaranteed to be a valid floating
point number).string を浮動小数点数値を構文解析する規則により構文解析し、
number を得ます。この段階は失敗しません (string は妥当な浮動小数点数であることが保証されています)。
Return number.number を返します。
2.4.3.5 Percentages and dimensions2.4.3.5 百分率と寸法
valid positive non-zero integers
rules for parsing dimension values (only used by
height/width on img, embed, object — lengths in css pixels or
percentages)
2.4.3.6 Lists of integers2.4.3.6 整数のリスト
A valid list of integers is a number of valid integers separated by U+002C
COMMA characters, with no other characters (e.g. no space characters). In addition, there
might be restrictions on the number of integers that can be given,
or on the range of values allowed.妥当な整数の並びは、 U+002C COMMA
文字で分離された数々の妥当な整数であって、
他の文字を含まない (例えば間隔文字を含まない) ものです。
加えて、与えられる整数の数や認められる値の範囲に制限が設けられることがあります。
The rules for parsing a list of integers are as
follows:整数のリストを構文解析する規則は次の通りです。
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Let numbers be an initially empty list
of integers. This list will be the result of this
algorithm.numbers を、初期状態として、空の整数のリストとします。
このリストは、この算法の結果となります。
If there is a character in the string input at position position, and
it is either a U+0020 SPACE, U+002C COMMA, or U+003B SEMICOLON
character, then advance position to the next
character in input, or to beyond the end of the
string if there are no more characters.文字列 input の位置 position
に文字があり、これが U+0020 SPACE、U+002C COMMA、 U+003B SEMICOLON
のいずれかの文字であれば、 position を input 中の次の文字に進めるか、それ以上文字がないのであれば文字列の終わりを過ぎたとします。
If position points to beyond the end of
input, return numbers and
abort.position が input の終わりを過ぎた先を指していれば、
numbers を返し、停止します。
If the character in the string input at
position position is a U+0020 SPACE, U+002C
COMMA, or U+003B SEMICOLON character, then return to step 4.文字列 input の位置 position
が U+0020 SPACE、U+002C COMMA、U+003B
SEMICOLON のいずれかの文字であれば、段階 4 に戻ります。
Let negated be false.negated を、偽とします。
Let value be 0.value を、0 とします。
Let started be false. This variable is
set to true when the parser sees a number or a "-" character.started を、偽とします。この変数は、
構文解析器が数か「-」文字を見たときに真に設定されます。
Let got number be false. This variable
is set to true when the parser sees a number.got number を偽とします。この変数は構文解析器が数を見たときに真に設定されます。
Let finished be false. This variable is
set to true to switch parser into a mode where it ignores
characters until the next separator.finished を偽とします。この変数は構文解析器が次の分離子まで文字を無視するモードに切り替わったとき真に設定されます。
Let bogus be false.bogus を、偽とします。
Parser: If the character in the string input at position position
is:構文解析器: 文字列 input 位置 position
の文字が、
- A U+002D HYPHEN-MINUS characterU+002D HYPHEN-MINUS 文字の場合
-
Follow these substeps:次の部分段階に従います。
If got number is true, let finished be true.got number が真である場合、 finished を真とします。
If finished is true, skip to the next
step in the overall set of steps.finished が真であれる場合、全体の段階の集合のうちの次の段階に飛びます。
If started is true, let negated be false.started が真である場合、 negated を偽とします。
Otherwise, if started is false and if bogus is false, let negated
be true.そうでない場合、started が偽であり、 bogus が偽である場合、 negated
を真とします。
Let started be true.started を、真とします。
- A character in the range U+0030 DIGIT ZERO .. U+0039 DIGIT
NINE範囲 U+0030 DIGIT ZERO ～ U+0039 DIGIT NINE の文字の場合
-
Follow these substeps:次の部分段階に従います。
If finished is true, skip to the next
step in the overall set of steps.finished が真であれる場合、全体の段階の集合のうちの次の段階に飛びます。
Multiply value by ten.value を10倍します。
Add the value of the digit, interpreted in base ten, to
value.数字を十進数で解釈した場合の値を value に加えます。
Let started be true.started を、真とします。
Let got number be true.got number を、真とします。
- A U+0020 SPACE characterU+0020 SPACE 文字の場合
- A U+002C COMMA characterU+002C COMMA 文字の場合
- A U+003B SEMICOLON characterU+003B SEMICOLON 文字の場合
-
Follow these substeps:次の部分段階に従います。
If got number is false, return the numbers list and abort. This happens if an entry
in the list has no digits, as in "1,2,x,4".got number が偽の場合、 numbers リストを返し、停止します。
これは、「1,2,x,4」のようにリスト中の項目が数字を持たない場合に起こります。
If negated is true, then negate value.negated が真の場合、 value を負にします。
Append value to the numbers list.value を numbers リストの末尾に追加します。
Jump to step 4 in the overall set of steps.全体の段階の集合のうちの段階 4 に飛びます。
- A U+002E FULL STOP characterU+002E FULL STOP 文字の場合
-
Follow these substeps:次の部分段階に従います。
If got number is true, let finished be true.got number が真である場合、 finished を真とします。
If finished is true, skip to the next
step in the overall set of steps.finished が真であれる場合、全体の段階の集合のうちの次の段階に飛びます。
Let negated be false.negated を、偽とします。
- Any other characterその他の文字の場合
-
Follow these substeps:次の部分段階に従います。
If finished is true, skip to the next
step in the overall set of steps.finished が真であれる場合、全体の段階の集合のうちの次の段階に飛びます。
Let negated be false.negated を、偽とします。
Let bogus be true.bogus を、真とします。
If started is true, then return the
numbers list, and abort. (The value in value is not appended to the list first; it is
dropped.)started が真の場合、 numbers リストを返し、停止します。
(value の値はリストに最初に追加されてはいません。
捨てられます。)
Advance position to the next character
in input, or to beyond the end of the string if
there are no more characters.position を input 中の次の文字に進めるか、それ以上文字がないのであれば文字列の終わりを過ぎたとします。
If position points to a character (and
not to beyond the end of input), jump to the
big Parser step above.position が文字を指す場合 (で
input の終わりを過ぎていない場合)、
先の大段階構文解析器に飛びます。
If negated is true, then negate value.negated が真の場合、 value を負にします。
If got number is true, then append value to the numbers list.got number が真の場合、 value を numbers
リストの最後に追加します。
Return the numbers list and
abort.numbers リストを返し、停止します。
2.4.4 Dates and times2.4.4 日付と時刻
In the algorithms below, the number of days in month month of year year is:
31 if month is 1, 3, 5, 7, 8, 10, or
12; 30 if month is 4, 6, 9, or 11;
29 if month is 2 and year is a number divisible by 400, or if year is a number divisible by 4 but not by 100; and
28 otherwise. This takes into account leap years in the
Gregorian calendar. [GREGORIAN]
The digits in the date
and time syntaxes defined in this section must be characters in the
range U+0030 DIGIT ZERO to U+0039 DIGIT NINE, used to express
numbers in base ten.
2.4.4.1 Months
A month consists of a specific
proleptic Gregorian date with no timezone information and no date
information beyond a year and a month. [GREGORIAN]
A string is a valid month string representing a year
year and month month if it
consists of the following components in the given order:
Four or more digits, representing year, where year > 0
A U+002D HYPHEN-MINUS character (-)
Two digits,
representing the month month, in the range
0 ≤ month ≤ 12
The rules to parse a month string are as follows. This
will either return a year and month, or nothing. If at any point the
algorithm says that it "fails", this means that it is aborted at
that point and returns nothing.
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Parse a month component to obtain year and month. If this returns
nothing, then fail.
If position is not beyond the
end of input, then fail.
Return year and month.year and month を返します。
The rules to parse a month component, given an input string and a position, are
as follows. This will either return a year and a month, or
nothing. If at any point the algorithm says that it "fails", this
means that it is aborted at that point and returns nothing.
Collect a sequence of characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not at least four characters long, then
fail. Otherwise, interpret the resulting sequence as a base-ten
integer. Let that number be the year.
If year is not a number greater than
zero, then fail.
If position is beyond the end of input or if the character at position is not a U+002D HYPHEN-MINUS character,
then fail. Otherwise, move position forwards
one character.position が input の終わりを過ぎている場合や position の位置の文字が U+002D HYPHEN-MINUS 文字でない場合、
失敗です。そうでない場合、 position を1文字先へ進めます。
Collect a sequence of characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
interpret the resulting sequence as a base-ten integer. Let that
number be the month.範囲 U+0030 DIGIT ZERO (0) ～ U+0039 DIGIT NINE (9) の文字の列を集めます。
集めた列が丁度2文字の長さでない場合、失敗です。
そうでない場合、得られた列を十進整数として解釈します。
この数を month とします。
If month is not a number in the range
1 ≤ month ≤ 12, then
fail.month が範囲 1 ≤ month ≤ 12
の数でない場合、失敗します。
Return year and month.year and month を返します。
2.4.4.2 Dates2.4.4.2 日付
A date consists of a specific
proleptic Gregorian date with no timezone information, consisting of
a year, a month, and a day. [GREGORIAN]
A string is a valid date string representing a year
year, month month, and day
day if it consists of the following components
in the given order:
A valid month string, representing year and month
A U+002D HYPHEN-MINUS character (-)
Two digits,
representing day, in the range
0 ≤ day ≤ maxday where maxday is the number of days
in the month month and year year
The rules to parse a date string are as follows. This
will either return a date, or nothing. If at any point the algorithm
says that it "fails", this means that it is aborted at that point
and returns nothing.
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Parse a date component to obtain year, month, and day. If this returns nothing, then fail.
If position is not beyond the
end of input, then fail.
Let date be the date with year year, month month, and day day.
Return date.date を返します。
The rules to parse a date component, given an input string and a position, are
as follows. This will either return a year, a month, and a day, or
nothing. If at any point the algorithm says that it "fails", this
means that it is aborted at that point and returns nothing.
Parse a month component to obtain year and month. If this returns
nothing, then fail.
Let maxday be the number of days
in month month of year year.
If position is beyond the end of input or if the character at position is not a U+002D HYPHEN-MINUS character,
then fail. Otherwise, move position forwards
one character.position が input の終わりを過ぎている場合や position の位置の文字が U+002D HYPHEN-MINUS 文字でない場合、
失敗です。そうでない場合、 position を1文字先へ進めます。
Collect a sequence of characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
interpret the resulting sequence as a base-ten integer. Let that
number be the day.範囲 U+0030 DIGIT ZERO (0) ～ U+0039 DIGIT NINE (9) の文字の列を集めます。
集めた列が丁度2文字の長さでない場合、失敗です。
そうでない場合、得られた列を十進整数として解釈します。
この数を day とします。
If day is not a number in the range
1 ≤ month ≤ maxday, then fail.day が範囲 1 ≤ month ≤ maxday の数でない場合、失敗します。
Return year, month,
and day.year, month, and day を返します。
2.4.4.3 Times
A time consists of a specific
time with no timezone information, consisting of an hour, a minute,
a second, and a fraction of a second.
A string is a valid time string representing an hour
hour, a minute minute, and a
second second if it consists of the following
components in the given order:
Two digits,
representing hour, in the range
0 ≤ hour ≤ 23
A U+003A COLON character (:)
Two digits,
representing minute
Optionally (required if second is
non-zero):
A U+003A COLON character (:)
Two digits,
representing the integer part of second, in
the range 0 ≤ s ≤ 59
Optionally (required if second is not an
integer):
A 002E FULL STOP character (.)
One or more digits, representing the
fractional part of second
The second component cannot be
60 or 61; leap seconds cannot be represented.
The rules to parse a time string are as follows. This
will either return a time, or nothing. If at any point the algorithm
says that it "fails", this means that it is aborted at that point
and returns nothing.
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Parse a time component to obtain hour, minute, and second. If this returns nothing, then fail.
If position is not beyond the
end of input, then fail.
Let time be the time with hour hour, minute minute, and second
second.
Return time.time を返します。
The rules to parse a time component, given an input string and a position, are
as follows. This will either return an hour, a minute, and a second,
or nothing. If at any point the algorithm says that it "fails", this
means that it is aborted at that point and returns nothing.
Collect a sequence of characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
interpret the resulting sequence as a base-ten integer. Let that
number be the hour.範囲 U+0030 DIGIT ZERO (0) ～ U+0039 DIGIT NINE (9) の文字の列を集めます。
集めた列が丁度2文字の長さでない場合、失敗です。
そうでない場合、得られた列を十進整数として解釈します。
この数を hour とします。
If hour is not a number in the range
0 ≤ hour ≤ 23, then
fail.hour が範囲 0 ≤ hour ≤ 23
の数でない場合、失敗します。
If position is beyond the end of input or if the character at position is not a U+003A COLON character, then
fail. Otherwise, move position forwards one
character.position が input の終わりを過ぎている場合、
または position の文字が U+003A COLON
文字でない場合、失敗します。
そうでない場合、 position を1文字先へ進めます。
Collect a sequence of characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
interpret the resulting sequence as a base-ten integer. Let that
number be the minute.範囲 U+0030 DIGIT ZERO (0) ～ U+0039 DIGIT NINE (9) の文字の列を集めます。
集めた列が丁度2文字の長さでない場合、失敗です。
そうでない場合、得られた列を十進整数として解釈します。
この数を minute とします。
If minute is not a number in the range
0 ≤ minute ≤ 59, then
fail.minute が範囲
0 ≤ minute ≤ 59
の数でない場合、失敗します。
Let second be a string with the value
"0".second を、値「0」の文字列とします。
-
If position is not beyond the end of
input and the character at position is a U+003A COLON, then run these
substeps:
Advance position to the next character
in input.position を input 中の次の文字へ進めます。
If position is beyond the end of input, or at the last character in input, or if the next two characters in
input starting at position are not two characters both in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9), then
fail.position が input の終わりを過ぎている場合や、 input の最後の文字の位置にある場合や、 input 中の position
から始まる次の2つの文字が共に範囲 U+0030 DIGIT ZERO (0) ～ U+0039 DIGIT
NINE (9) の文字2つではない場合、失敗します。
Collect a sequence of characters that are
either characters in the range U+0030 DIGIT ZERO (0) to U+0039
DIGIT NINE (9) or U+002E FULL STOP characters. If the collected
sequence has more than one U+002E FULL STOP characters, or if the
last character in the sequence is a U+002E FULL STOP character,
then fail. Otherwise, let the collected string be second instead of its previous value.
Interpret second as a base-ten number
(possibly with a fractional part). Let second
be that number instead of the string version.
If second is not a number in the range
0 ≤ second < 60, then
fail.
Return hour, minute,
and second.hour, minute, and second を返します。
2.4.4.4 Local dates and times
A local date and time
consists of a specific proleptic Gregorian date, consisting of a
year, a month, and a day, and a time, consisting of an hour, a
minute, a second, and a fraction of a second, but expressed without
a time zone. [GREGORIAN]
A string is a valid local date and time string
representing a date and time if it consists of the following
components in the given order:
A valid date string representing the date.
A U+0054 LATIN CAPITAL LETTER T character.
A valid time string representing the time.
The rules to parse a local date and time string are as
follows. This will either return a date and time, or nothing. If at
any point the algorithm says that it "fails", this means that it is
aborted at that point and returns nothing.
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Parse a date component to obtain year, month, and day. If this returns nothing, then fail.
If position is beyond the end of input or if the character at position is not a U+0054 LATIN CAPITAL LETTER T
character then fail. Otherwise, move position
forwards one character.
Parse a time component to obtain hour, minute, and second. If this returns nothing, then fail.
If position is not beyond the
end of input, then fail.
Let date be the date with year year, month month, and day day.
Let time be the time with hour hour, minute minute, and second
second.
Return date and time.date and time を返します。
2.4.4.5 Global dates and times
A global date and time
consists of a specific proleptic Gregorian date, consisting of a
year, a month, and a day, and a time, consisting of an hour, a
minute, a second, and a fraction of a second, expressed with a time
zone, consisting of a number of hours and minutes. [GREGORIAN]
A string is a valid global date and time string
representing a date, time, and a timezone offset if it consists of
the following components in the given order:
A valid date string representing the date
A U+0054 LATIN CAPITAL LETTER T character
A valid time string representing the time
Either:
This format allows for time zone offsets from -23:59
to +23:59. In practice, however, the range of actual time zones is
-12:00 to +14:00, and the minutes component of actual time zones is
always either 00, 30, or 45.
The following are some examples of dates written as valid global date and
time strings.
- "
0037-12-13T00:00Z"「0037-12-13T00:00Z」
- Midnight UTC on the birthday of Nero (the Roman Emperor).ネロ (ローマ皇帝) の誕生日の UTC における真夜中
- "
1979-10-14T12:00:00.001-04:00"「1979-10-14T12:00:00.001-04:00」
- One millisecond after noon on October 14th 1979, in the time
zone in use on the east coast of North America during daylight
saving time.北米大陸東海岸の夏時刻適用中における1979年10月14日の正午の1ミリ秒後
- "
8592-01-01T02:09+02:09"「8592-01-01T02:09+02:09」
- Midnight UTC on the 1st of January, 8592. The time zone
associated with that time is two hours and nine minutes ahead of
UTC, which is not a real time zone currently, but is nonetheless
allowed.
Several things are notable about these dates:これらの日付に関して、いくつか注意点があります。
Years with fewer than four digits have to be
zero-padded. The date "37-12-13" would not be a valid date.4桁に満たない年は零埋めする必要があります。「37-12-13」
は妥当な日付ではありません。
To unambiguously identify a moment in time prior to the
introduction of the Gregorian calendar, the date has to be first
converted to the Gregorian calendar from the calendar in use at
the time (e.g. from the Julian calendar). The date of Nero's birth
is the 15th of December 37, in the Julian Calendar, which is the
13th of December 37 in the proleptic Gregorian Calendar.
The time and timezone components are not optional.時刻や時間帯の部品は省略可能ではありません。
Dates before the year zero can't be represented as a datetime
in this version of HTML.
Time zones differ based on daylight savings time.時間帯は夏時刻制によって異なります。
The rules to parse a global date and time string are
as follows. This will either return a time in UTC, with associated
timezone information for round tripping or display purposes, or
nothing. If at any point the algorithm says that it "fails", this
means that it is aborted at that point and returns nothing.
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Parse a date component to obtain year, month, and day. If this returns nothing, then fail.
If position is beyond the end of input or if the character at position is not a U+0054 LATIN CAPITAL LETTER T
character then fail. Otherwise, move position
forwards one character.
Parse a time component to obtain hour, minute, and second. If this returns nothing, then fail.
If position is beyond the end of input, then fail.position が input の終わりを過ぎている場合、失敗します。
Parse a timezone component to obtain timezonehours and timezoneminutes. If this returns
nothing, then fail.
If position is not beyond the
end of input, then fail.
Let time be the moment in time at year
year, month month, day day, hours hour, minute minute, second second,
subtracting timezonehours
hours and timezoneminutes
minutes. That moment in time is a moment in the UTC
timezone.
Let timezone be timezonehours hours and timezoneminutes minutes from
UTC.
Return time and timezone.time と timezone を返します。
The rules to parse a timezone component, given an input string and a position, are
as follows. This will either return timezone hours and timezone
minutes, or nothing. If at any point the algorithm says that it
"fails", this means that it is aborted at that point and returns
nothing.
-
If the character at position is a U+005A
LATIN CAPITAL LETTER Z, then:
Let timezonehours
be 0.
Let timezoneminutes be 0.
Advance position to the next character
in input.position を input 中の次の文字へ進めます。
Otherwise, if the character at position is
either a U+002B PLUS SIGN ("+") or a U+002D HYPHEN-MINUS ("-"),
then:
If the character at position is a
U+002B PLUS SIGN ("+"), let sign be
"positive". Otherwise, it's a U+002D HYPHEN-MINUS ("-"); let sign be "negative".
Advance position to the next character
in input.position を input 中の次の文字へ進めます。
Collect a sequence of characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then
fail. Otherwise, interpret the resulting sequence as a base-ten
integer. Let that number be the timezonehours.範囲 U+0030 DIGIT ZERO (0) ～ U+0039 DIGIT NINE (9) の文字の列を集めます。
集めた列が丁度2文字の長さでない場合、失敗です。
そうでない場合、得られた列を十進整数として解釈します。
この数を timezonehours とします。
If timezonehours is
not a number in the range 0 ≤ timezonehours ≤ 23, then fail.
If sign is "negative", then negate timezonehours.
If position is beyond the end of input or if the character at position is not a U+003A COLON character, then
fail. Otherwise, move position forwards one
character.position が input の終わりを過ぎている場合、
または position の文字が U+003A COLON
文字でない場合、失敗します。
そうでない場合、 position を1文字先へ進めます。
Collect a sequence of characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then
fail. Otherwise, interpret the resulting sequence as a base-ten
integer. Let that number be the timezoneminutes.範囲 U+0030 DIGIT ZERO (0) ～ U+0039 DIGIT NINE (9) の文字の列を集めます。
集めた列が丁度2文字の長さでない場合、失敗です。
そうでない場合、得られた列を十進整数として解釈します。
この数を timezoneminutes とします。
If timezoneminutes is
not a number in the range 0 ≤ timezoneminutes ≤ 59, then fail.
If sign is "negative", then negate timezoneminutes.
Return timezonehours
and timezoneminutes.timezonehours and timezoneminutes を返します。
2.4.4.6 Weeks
A week consists of a week-year
number and a week number representing a seven day period. Each
week-year in this calendaring system has either 52 weeks or 53
weeks, as defined below. A week is a seven-day period. The week
starting on the Gregorian date Monday December 29th 1969
(1969-12-29) is defined as week number 1 in week-year
1970. Consecutive weeks are numbered sequentially. The week before
the number 1 week in a week-year is the last week in the previous
week-year, and vice versa. [GREGORIAN]
A week-year with a number year that
corresponds to a year year in the proleptic
Gregorian calendar that has a Thursday as its first day (January
1st), and a week-year year where year is a number divisible by 400, or a number
divisible by 4 but not by 100, has 53 weeks. All other week-years
have 52 weeks.
The week number of the last day of a week-year with 53
weeks is 53; the week number of the last day of a week-year with 52
weeks is 52.
The week-year number of a particular day can be
different than the number of the year that contains that day in the
proleptic Gregorian calendar. The first week in a week-year year is the week that contains the first Thursday of
the Gregorian year year.
A string is a valid week string representing a
week-year year and week week
if it consists of the following components in the given order:
Four or more digits, representing year, where year > 0
A U+002D HYPHEN-MINUS character (-)
A U+0057 LATIN CAPITAL LETTER W character
Two digits,
representing the week week, in the range
1 ≤ week ≤ maxweek, where maxweek is the
week number of the last day of week-year year
The rules to parse a week string are as follows. This
will either return a week-year number and week number, or
nothing. If at any point the algorithm says that it "fails", this
means that it is aborted at that point and returns nothing.
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Collect a sequence of characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not at least four characters long, then
fail. Otherwise, interpret the resulting sequence as a base-ten
integer. Let that number be the year.
If year is not a number greater than
zero, then fail.
If position is beyond the end of input or if the character at position is not a U+002D HYPHEN-MINUS character,
then fail. Otherwise, move position forwards
one character.position が input の終わりを過ぎている場合や position の位置の文字が U+002D HYPHEN-MINUS 文字でない場合、
失敗です。そうでない場合、 position を1文字先へ進めます。
If position is beyond the end of input or if the character at position is not a U+0057 LATIN CAPITAL LETTER W
character, then fail. Otherwise, move position
forwards one character.
Collect a sequence of characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
interpret the resulting sequence as a base-ten integer. Let that
number be the week.
Let maxweek be the week number of
the last day of year year.
If week is not a number in the range
1 ≤ week ≤ maxweek, then fail.
If position is not beyond the
end of input, then fail.
Return the week-year number year and the
week number week.
2.4.4.7 Vaguer moments in time2.4.4.7 より曖昧な時刻
A date or time string consists of either a date, a time, or a global date and time.
A string is a valid date or time string if it is also
one of the following:
A string is a valid date or time string in content if
it consists of zero or more White_Space characters,
followed by a valid date or time string, followed by
zero or more further White_Space characters.
The rules to parse a date or time string are as
follows. The algorithm is invoked with a flag indicating if the
in attribute variant or the in content variant is to
be used. The algorithm will either return a date, a time, a global date and time, or nothing. If
at any point the algorithm says that it "fails", this means that it
is aborted at that point and returns nothing.
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
For the in content variant: skip White_Space
characters.
Set start position to the same position
as position.
Set the date present and time present flags to true.
Parse a date component to obtain year, month, and day. If this fails, then set the date
present flag to false.
-
If date present is true, and position is not beyond the end of input, and the character at position is a U+0054 LATIN CAPITAL LETTER T
character, then advance position to the next
character in input.
Otherwise, if date present is true, and
either position is beyond the end of input or the character at position is not a U+0054 LATIN CAPITAL LETTER T
character, then set time present to false.
Otherwise, if date present is false, set
position back to the same position as start position.
If the time present flag is true, then
parse a time component to obtain hour, minute, and second. If this returns nothing, then set the time present flag to false.
If both the date present and time present flags are false, then fail.
If the time present flag is true, but
position is beyond the end of input, then fail.
If the date present and time present flags are both true, parse a
timezone component to obtain timezonehours and timezoneminutes. If this returns nothing, then
fail.
For the in content variant: skip White_Space
characters.
If position is not beyond the
end of input, then fail.
-
If the date present flag is true and the
time present flag is false, then let date be the date with year year, month month, and day day, and return date.
Otherwise, if the time present flag is true
and the date present flag is false, then let
time be the time with hour hour, minute minute, and second
second, and return time.
Otherwise, let time be the moment in time
at year year, month month,
day day, hours hour,
minute minute, second second, subtracting timezonehours hours and timezoneminutes minutes, that moment in time being a
moment in the UTC timezone; let timezone be
timezonehours hours and
timezoneminutes minutes
from UTC; and return time and timezone.
2.4.5 Colors
A simple color consists of three 8-bit numbers in the
range 0..255, representing the red, green, and blue components of
the color respectively, in the sRGB color space. [SRGB]
A string is a valid simple color if it is exactly
seven characters long, and the first character is a U+0023 NUMBER
SIGN (#) character, and the remaining six characters are all in the
range U+0030 DIGIT ZERO (0) .. U+0039 DIGIT NINE (9), U+0041 LATIN
CAPITAL LETTER A .. U+0046 LATIN CAPITAL LETTER F, U+0061 LATIN
SMALL LETTER A .. U+0066 LATIN SMALL LETTER F, with the first two
digits representing the red component, the middle two digits
representing the green component, and the last two digits
representing the blue component, in hexadecimal.
A string is a valid lowercase simple color if it is a
valid simple color and doesn't use any characters in
the range U+0041 LATIN CAPITAL LETTER A .. U+0046 LATIN CAPITAL
LETTER F.
The rules for parsing simple color values are as given
in the following algorithm. When invoked, the steps must be followed
in the order given, aborting at the first step that returns a
value. This algorithm will either return a simple color
or an error.
Let input be the string being
parsed.input を、構文解析される文字列とします。
If input is not exactly seven characters
long, then return an error.
If the first character in input is not a
U+0023 NUMBER SIGN (#) character, then return an error.
If the last six characters of input are
not all in the range U+0030 DIGIT ZERO (0) .. U+0039 DIGIT NINE
(9), U+0041 LATIN CAPITAL LETTER A .. U+0046 LATIN CAPITAL LETTER
F, U+0061 LATIN SMALL LETTER A .. U+0066 LATIN SMALL LETTER F, then
return an error.
Let result be a simple
color.
Interpret the second and third characters as a hexadecimal
number and let the result be the red component of result.
Interpret the fourth and fifth characters as a hexadecimal
number and let the result be the green component of result.
Interpret the sixth and seventh characters as a hexadecimal
number and let the result be the blue component of result.
Return result.result を返します。
The rules for serialising simple color values given a
simple color are as given in the following
algorithm:
Let result be a string consisting of a
single U+0023 NUMBER SIGN (#) character.
Convert the red, green, and blue components in turn to
two-digit hexadecimal numbers using the digits U+0030 DIGIT ZERO
(0) .. U+0039 DIGIT NINE (9) and U+0061 LATIN SMALL LETTER A
.. U+0066 LATIN SMALL LETTER F, zero-padding if necessary, and
append these numbers to result, in the order
red, green, blue.
Return result, which will be a
valid lowercase simple color.
The 2D graphics
context has a separate color syntax that also handles
opacity.
Some obsolete legacy attributes parse colors in a
more complicated manner.
2.4.6 Space-separated tokens
A set of space-separated tokens is a set of zero or
more words separated by one or more space characters, where words consist of any
string of one or more characters, none of which are space characters.
A string containing a set of space-separated tokens
may have leading or trailing space
characters.
An unordered set of unique space-separated tokens is a
set of space-separated tokens where none of the words
are duplicated.
An ordered set of unique space-separated tokens is a
set of space-separated tokens where none of the words
are duplicated but where the order of the tokens is meaningful.
Sets of
space-separated tokens sometimes have a defined set of
allowed values. When a set of allowed values is defined, the tokens
must all be from that list of allowed values; other values are
non-conforming. If no such set of allowed values is provided, then
all values are conforming.
When a user agent has to split a string on spaces, it
must use the following algorithm:
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Let tokens be a list of tokens,
initially empty.
Skip whitespace
While position is not past the end of
input:
Collect a sequence of characters that are not
space characters.
Add the string collected in the previous step to tokens.
Skip whitespace
Return tokens.tokens を返します。
When a user agent has to remove a token from a string,
it must use the following algorithm:
Let input be the string being
modified.
Let token be the token being removed. It
will not contain any space
characters.
Let output be the output string,
initially empty.
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
If position is beyond the end of input, set the string being modified to output, and abort these steps.
If the character at position is a
space character:
Append the character at position to
the end of output.
Increment position so it points at the
next character in input.
Return to step 5 in the overall set of steps.段階全体の集合の段階 5 に戻ります。
Otherwise, the character at position is
the first character of a token. Collect a sequence of
characters that are not space
characters, and let that be s.
If s is exactly equal to token, then:
Skip whitespace (in input).
Remove any space
characters currently at the end of output.
If position is not past the end of
input, and output is not
the empty string, append a single U+0020 SPACE character at the
end of output.
Otherwise, append s to the end of output.そうでない場合、 s を output
の末尾に追加します。
Return to step 6 in the overall set of steps.段階全体の集合の段階 6 に戻ります。
This causes any occurrences of the token to be
removed from the string, and any spaces that were surrounding the
token to be collapsed to a single space, except at the start and end
of the string, where such spaces are removed.
2.4.7 Comma-separated tokens2.4.7 注釈分離字句
We should allow whitespace around commas, and
leading/trailing whitespace.
A set of comma-separated tokens is a set of zero or
more tokens each separated from the next by a single U+002C COMMA
character (,), where tokens consist of any
string of zero or more characters, none of which are U+002C COMMA
characters (,).
Sets of
comma-separated tokens sometimes have further restrictions on
what consists a valid token. When such restrictions are defined, the
tokens must all fit within those restrictions; other values are
non-conforming. If no such restrictions are specified, then all
values are conforming.
When a user agent has to split a string on commas, it
must use the following algorithm:
Let input be the string being
parsed.input を、構文解析される文字列とします。
Let position be a pointer into input, initially pointing at the start of the
string.position を input 中の指示子とし、初期位置を文字列の始めとします。
Let tokens be a list of tokens,
initially empty.
Token: If position is past the
end of input, jump to the last step.
Collect a sequence of characters that are not
U+002C COMMA characters (,).
Add the string collected in the previous step (which might
be the empty string) to tokens.
If position is not past the end of input, then the character at position is a U+002C COMMA character (,); advance position past that
character.
Jump back to the step labeled token.
Return tokens.tokens を返します。
2.4.8 Keywords and enumerated attributes2.4.8 キーワードと列挙属性
Some attributes are defined as taking one of a finite set of
keywords. Such attributes are called enumerated attributes. The keywords are each
defined to map to a particular state (several keywords
might map to the same state, in which case some of the keywords are
synonyms of each other; additionally, some of the keywords can be
said to be non-conforming, and are only in the specification for
historical reasons). In addition, two default states can be
given. The first is the invalid value default, the second
is the missing value default.
If an enumerated attribute is specified, the attribute's value
must be an ASCII case-insensitive match for one of the
given keywords that are not said to be non-conforming, with no
leading or trailing whitespace.
When the attribute is specified, if its value is an ASCII
case-insensitively match for one of the given keywords then
that keyword's state is the state that the attribute represents. If
the attribute value matches none of the given keywords, but the
attribute has an invalid value default, then the attribute
represents that state. Otherwise, if the attribute value matches
none of the keywords but there is a missing value default
state defined, then that is the state represented by the
attribute. Otherwise, there is no default, and invalid values must
be ignored.
When the attribute is not specified, if there is a
missing value default state defined, then that is the state
represented by the (missing) attribute. Otherwise, the absence of
the attribute means that there is no state represented.
The empty string can be one of the keywords in some
cases. For example the contenteditable attribute has
two states: true, matching the true
keyword and the empty string, false, matching false and all other keywords (it's the invalid
value default). It could further be thought of as having a
third state inherit, which would be the default when the
attribute is not specified at all (the missing value
default), but for various reasons that isn't the way this
specification actually defines it.
2.4.9 References2.4.9 参照
A valid hash-name reference to an element of type type is a string consisting of a U+0023 NUMBER SIGN
(#) character followed by a string which
exactly matches the value of the name
attribute of an element in the document with type type.型 type の要素への妥当なハッシュ名参照は、 U+0023 NUMBER SIGN
(#) 文字の後に続けて文書中の型 type
の要素の name 属性の値と正確に一致する文字列が続くような文字列です。
The rules for parsing a hash-name reference to an
element of type type are as follows:型 type の要素へのハッシュ名参照を構文解析する規則は次の通りです。
If the string being parsed does not contain a U+0023 NUMBER
SIGN character, or if the first such character in the string is the
last character in the string, then return null and abort these
steps.構文解析する文字列が U+0023 NUMBER
SIGN 文字を含んでいない場合や、文字列中最初の U+0023 NUMBER
SIGN 文字が文字列中の最後の文字の場合、 null を返し、これらの段階を停止します。
Let s be the string from the character
immediately after the first U+0023 NUMBER SIGN character in the
string being parsed up to the end of that string.s を、構文解析する文字列の中の最初の U+0023 NUMBER SIGN
文字の直後の文字から文字列の末尾までの文字列とします。
Return the first element of type type
that has an id or name attribute whose value is a compatibility
caseless match for s.型 type で、
id 属性か
name 属性の値が互換性大文字・小文字不区別で s と一致する最初の要素を返します。
2.5 URLs2.5 URL
This specification defines the term URL, and defines
various algorithms for dealing with URLs, because for historical
reasons the rules defined by the URI and IRI specifications are not
a complete description of what HTML user agents need to implement to
be compatible with Web content.この仕様書は、用語 URL を定義し、 URL
を処理する各種算法を定義します。というのは、歴史的理由により、 URI や IRI
の仕様書で定義されている規則は Web 内容との互換性のために HTML
利用者エージェントが実装する必要があるものの完全な説明となっていないからです。
2.5.1 Terminology2.5.1 用語
A URL is a string used to identify a resource. A URL is always associated with a
Document, either explicitly when the URL is created or
defined; or through a DOM node, in which case the associated
Document is the node's Document; or
through a script, in which case the associated Document
is the script's script document context.URL は資源を識別するために使われる文字列です。URL は常に Document
と関連付けられています。この関連付けは URL が作成されるか定義される時に明示的になされるか、
または DOM 節点を通じてなされる (この場合、関連付けられた Document
は節点の Document です。) か、スクリプトを通じてなされます
(この場合、関連付けられた Document
はスクリプトのスクリプト文書文脈です。)。
A URL is a valid URL if at least one of
the following conditions holds:URL は、次のいずれかの最低1つの条件を満たす場合、妥当な
URL です。
The term "URL" in this specification is used in a
manner distinct from the precise technical meaning it is given in
RFC 3986. Readers familiar with that RFC will find it easier to read
this specification if they pretend the term "URL" as used
herein is really called something else altogether.この仕様書中の用語「URL」は、 RFC 3986 で与えられている正確な技術的な意味と異なった形で使われています。
RFC 3986 に精通した読者にとっては、ここでの用語「URL」が何か全く別の呼ばれ方をしたものであると思った方がこの仕様書を読むのが楽になるでしょう。
2.5.2 Parsing URLs2.5.2 URL の構文解析
To parse a URL url into its
component parts, the user agent must use the following steps:利用者エージェントは、
URL url を構文解析して部品部分を得る際、
次の段階を使わなければなりません。
Strip leading and trailing space characters from url.url から先頭と末尾の間隔文字を除去します。
-
Parse url in the manner defined by RFC
3986, with the following exceptions:url を RFC 3986 で定義された方法で構文解析します。
ただし、次の例外に従います。
Add all characters with codepoints less than or equal to
U+0020 or greater than or equal to U+007F to the
<unreserved> production.符号位置が U+0020 以下の文字や U+007F 以上の文字をすべて <unreserved>
生成規則に追加します。
Add the characters U+0022, U+003C, U+003E, U+005B .. U+005E,
U+0060, and U+007B .. U+007D to the <unreserved>
production.
Add a single U+0025 PERCENT SIGN character as a second
alternative way of matching the <pct-encoded> production,
except when the <pct-encoded> is used in the
<reg-name> production.単一の U+0025 PERCENT SIGN 文字を <pct-encoded>
生成規則に一致する2つ目の方法として追加します。ただし、 <pct-encoded>
が <reg-name> 生成規則で使われる時を除きます。
Add the U+0023 NUMBER SIGN character to the characters
allowed in the <fragment> production.U+0023 NUMBER SIGN 文字を <fragment> 生成規則で認められる文字に追加します。
-
If url doesn't match the
<URI-reference> production, even after the above changes are
made to the ABNF definitions, then parsing the URL fails with an
error. [RFC3986]ABNF 定義に前述の変更を加えた後であっても
url が <URI-reference> 生成規則に一致しない場合は、
URL の構文解析は誤りにより失敗とします。 [RFC3986]
Otherwise, parsing url was successful; the
components of the URL are substrings of url
defined as follows:そうでない場合、 url の構文解析は成功です。 URL
の部品は次の通り定義される url の各部分文字列です。
- <scheme>
The substring matched by the <scheme> production, if any.<scheme> 生成規則に一致する部分文字列 (あれば)。
- <host>
The substring matched by the <host> production, if any.<host> 生成規則に一致する部分文字列 (あれば)。
- <port>
The substring matched by the <port> production, if any.<port> 生成規則に一致する部分文字列 (あれば)。
- <hostport>
If there is a <scheme> component and a <port>
component and the port given by the <port> component is
different than the default port defined for the protocol given by
the <scheme> component, then <hostport> is the
substring that starts with the substring matched by the
<host> production and ends with the substring matched by the
<port> production, and includes the colon in between the
two. Otherwise, it is the same as the <host> component.<scheme> 部品と <port> 部品があり、 <port>
部品により与えられるポートが <scheme> 部品により与えられるプロトコルに対して定義された既定のポートと異なる場合、
<hostport> は <host> 生成規則に一致する部分文字列で始まり、
<port> 生成規則に一致する部分文字列で終わり、両者の間のコロンを含む部分文字列です。
そうでない場合、 <host> 部品と同じです。
- <path>
-
The substring matched by one of the following productions, if
one of them was matched:次の生成規則のいずれかに一致する部分文字列 (いずれかが一致する場合)。
<path-abempty>
<path-absolute>
<path-noscheme>
<path-rootless>
<path-empty>
- <query>
The substring matched by the <query> production, if any.<query> 生成規則に一致する部分文字列 (あれば)。
- <fragment>
The substring matched by the <fragment> production, if any.<fragment> 生成規則に一致する部分文字列 (あれば)。
- <host-specific>
The substring that follows the substring matched
by the <authority> production, or the whole string if the
<authority> production wasn't matched.
2.5.3 Resolving URLs2.5.3 URL の解決
Relative URLs are resolved relative to a base URL. The base
URL of a URL is the absolute URL
obtained as follows:相対 URL は基底 URL に対して相対的に解決されます。 URL の基底 URLは、次のようにして得られる絶対 URL です。
- If the URL to be resolved was passed to an API解決する URL が API に渡された場合
The base URL is the document base URL of the
script's script document context.基底 URL は、そのスクリプトのスクリプト文書文脈の文書基底 URL
です。
- If the URL to be resolved is from the value of a content
attribute解決する URL が内容属性の値に由来する場合
-
The base URL is the base URI of the element that the
attribute is on, as defined by the XML Base specification, with
the base URI of the document entity being defined as the
document base URL of the Document that
owns the element.基底 URL は、 XML 基底仕様書によって定義される、その属性の属する要素の基底 URI
です。ここで、文書実体の基底 URI は、その要素を所有する Document
の文書基底 URL
として定義されます。
For the purposes of the XML Base specification, user agents
must act as if all Document objects represented XML
documents.利用者エージェントは、 XML 基底仕様書の範囲に関しては、すべての
Document オブジェクトが XML 文書を表現するかのように作用しなければなりません。
It is possible for xml:base attributes to be present
even in HTML fragments, as such attributes can be added
dynamically using script. (Such scripts would not be conforming,
however, as xml:base attributes
are not allowed in HTML documents.)xml:base 属性は、 HTML
素片中であっても出現することがあります。なぜなら、スクリプトを作って動的にこの属性を追加することができるからです。
(しかし、 xml:base
属性は HTML 文書中では認められていないので、
そのようなスクリプトは適合しません。)
- If the URL to be resolved was found in an offline application
cache manifest解決する URL がオフライン・アプリケーション・キャッシュ・マニフェスト中に現れた場合
The base URL is the URL of the application
cache manifest.基底 URL は、 アプリケーション・キャッシュ・マニフェストの URL
です。
The document base URL of a Document is
the absolute URL obtained by running these steps:Document の文書基底 URL
は、次の段階を走らせて得られる絶対 URL
です。
If there is no base element that is both a
child of the head element and has an
href attribute, then the
document base URL is the document's
address.
Otherwise, let url be the value of the
href attribute of the first such
element.そうでない場合、 url をそのような最初の要素の href 属性の値とします。
Resolve the url URL, using the document's address
as the base URL (thus, the base href attribute isn't affected by
xml:base attributes).
The document base URL is the result of the
previous step if it was successful; otherwise it is the
document's address.
To resolve a URL to an absolute URL the
user agent must use the following steps. Resolving a URL can result
in an error, in which case the URL is not resolvable.利用者エージェントは、URL を解決して絶対 URL にするために次の段階を使わなければなりません。
URL の解決は誤りに終わるかもしれませんが、その場合 URL は解決可能ではありません。
Let url be the URL being
resolved.url を、解決する URL とします。
Let document be the
Document associated with url.document を、url
と関連付けられている Document
とします。
Let encoding be the character encoding of
document.
If encoding is UTF-16, then change it to
UTF-8.encoding が UTF-16 の場合、これを UTF-8
に変更します。
Let base be the base URL
for url. (This is an absolute
URL.)base を、 url の基底
URL とします。 (これは絶対
URL です。)
Parse url into its component parts.
-
If parsing url resulted in a <host> component, then replace the
matching subtring of url with the string that
results from expanding any sequences of percent-encoded octets in
that component that are valid UTF-8 sequences into Unicode
characters as defined by UTF-8.url の構文解析の結果 <host> 部品が得られた場合、 url
中のそれに一致した部分文字列を、その部品中で百分率符号化されたオクテット列であって妥当な
UTF-8 列である部分を UTF-8 で定義されているようにして Unicode
文字に置き換えた文字列によって置き換えます。
If any percent-encoded octets in that component are not valid
UTF-8 sequences, then return an error and abort these steps.この部品中の百分率符号化されたオクテットが妥当な UTF-8 列でない場合は、
誤りを返し、これらの段階を停止します。
Apply the IDNA ToASCII algorithm to the matching substring,
with both the AllowUnassigned and UseSTD3ASCIIRules flags
set. Replace the matching substring with the result of the ToASCII
algorithm.IDNA ToASCII 算法を、 AllowUnassigned 旗と UseSTD3ASCIIRules
旗の両方を設定した上で、一致した部分文字列に適用します。一致した部分文字列を、
ToASCII 算法の結果により置き換えます。
If ToASCII fails to convert one of the components of the
string, e.g. because it is too long or because it contains invalid
characters, then return an error and abort these steps. [RFC3490]ToASCIIが文字列の部品のいずれかの変換に失敗した場合 (例えば部品が長すぎる場合や非妥当な文字を含む場合)、
誤りを返し、これらの段階を停止します。
[RFC3490]
-
If parsing url resulted in a <path> component, then replace the
matching substring of url with the string that
results from applying the following steps to each character other
than U+0025 PERCENT SIGN (%) that doesn't match the original
<path> production defined in RFC 3986:url の構文解析の結果 <path> 部品が得られた場合、 url
の一致した部分文字列を、 RFC 3986 で定義されている元々の <path>
生成規則に一致しない U+0025 PERCENT
SIGN (%) 以外の文字それぞれに次の段階を適用した結果の文字列により置き換えます。
Encode the character into a sequence of octets as defined by
UTF-8.文字を、 UTF-8 で定義されているようにしてオクテット列に符号化します。
Replace the character with the percent-encoded form of those
octets. [RFC3986]文字を、そのオクテット列の百分率符号化した形で置き換えます。
[RFC3986]
For instance if url was "//example.com/a^b☺c%FFd%z/?e", then the
<path> component's substring
would be "/a^b☺c%FFd%z/" and the two
characters that would have to be escaped would be "^" and "☺". The
result after this step was applied would therefore be that url now had the value "//example.com/a%5Eb%E2%98%BAc%FFd%z/?e".
-
If parsing url resulted in a <query> component, then replace the
matching substring of url with the string that
results from applying the following steps to each character other
than U+0025 PERCENT SIGN (%) that doesn't match the original
<query> production defined in RFC 3986:url の構文解析の結果 <query> 部品が得られた場合、 url
の一致した部分文字列を、 RFC 3986 で定義されている元々の <path>
生成規則に一致しない U+0025 PERCENT
SIGN (%) 以外の文字それぞれに次の段階を適用した結果の文字列により置き換えます。
If the character in question cannot be expressed in the
encoding encoding, then replace it with a
single 0x3F octet (an ASCII question mark) and skip the remaining
substeps for this character.当該文字が符号化 encoding で表現できない場合、
これを単一の 0x3F オクテット (ASCII 疑問符) で置き換え、
この文字についての残りの部分段階を飛ばします。
Encode the character into a sequence of octets as defined by
the encoding encoding.文字を、符号化 encoding で定義されているようにしてオクテット列に符号化します。
Replace the character with the percent-encoded form of those
octets. [RFC3986]文字を、そのオクテット列の百分率符号化した形で置き換えます。
[RFC3986]
Apply the algorithm described in RFC 3986 section 5.2
Relative Resolution, using url as the
potentially relative URI reference (R), and
base as the base URI (Base). [RFC3986]RFC 3986 5.2 節 相対解決で説明されている算法を適用します。ここで、 url
を潜在的相対 URI 参照 (R)、
base を基底 URI (Base)
とします。 [RFC3986]
-
Apply any relevant conformance criteria of RFC 3986 and RFC
3987, returning an error and aborting these steps if
appropriate. [RFC3986] [RFC3987]RFC 3986 と RFC 3987 の関係する適合性基準を適用し、
適切であれば、誤りを返し、これらの段階を停止します。 [RFC3986] [RFC3987]
For instance, if an absolute URI that would be
returned by the above algorithm violates the restrictions specific
to its scheme, e.g. a data: URI using the
"//" server-based naming authority syntax,
then user agents are to treat this as an error instead.
Let result be the target URI (T) returned by the Relative Resolution
algorithm.result を、相対解決算法で返される対象 URI (T) とします。
If result uses a scheme with a
server-based naming authority, replace all U+005C REVERSE SOLIDUS
(\) characters in result with U+002F SOLIDUS
(/) characters.result が鯖型命名局の scheme を使っている場合、 result 中のすべての U+005C REVERSE SOLIDUS (\)
文字を U+002F SOLIDUS (/) 文字に置き換えます。
Return result.result を返します。
A URL is an absolute URL if resolving it results in the same
URL without an error.URL は、これを解決しても誤りとならずに同じ URL
が得られる場合、絶対 URL です。
2.5.4 Dynamic changes to base URLs2.5.4 基底 URL に対する動的な変更
When an xml:base attribute
changes, the attribute's element, and all descendant elements, are
affected by a base URL change.xml:base
属性が変化した時、その属性の要素と、すべての子孫要素は、
基底 URL の変更に影響されます。
When a document's document base URL changes, all
elements in that document are affected by a base URL
change.文書の文書基底 URL が変化した時、
文書中のすべての要素は基底 URL の変更に影響されます。
When an element is moved from one document to another, if the two
documents have different base
URLs, then that element and all its descendants are
affected by a base URL change.要素がある文書から別の文書へと移動された時、
2つの文書が異なる基底 URL を持つ場合、
その要素とすべての子孫は基底 URL の変更に影響されます。
When an element is affected by a base URL change, it
must act as described in the following list:要素が基底 URL の変更に影響される時、
次の並びで説明するように作用しなければなりません。
- If the element is a hyperlink
element要素がハイパーリンク要素である場合
-
If the absolute URL identified by the hyperlink is
being shown to the user, or if any data derived from that URL is
affecting the display, then the href attribute should be reresolved and the UI updated
appropriately.当該ハイパーリンクにより識別される絶対 URL
が利用者に示される場合に、あるいはその URL に由来する何らかのデータが表示に影響する場合に、 href
属性は再解決され、
利用者界面は適切に更新されるべきです。
For example, the CSS :link/:visited
pseudo-classes might have been affected.例えば、 CSS :link/:visited
擬似クラスが影響を受けるかもしれません。
If the hyperlink has a ping attribute and its absolute URL(s) are being shown to the
user, then the ping
attribute's tokens should be reresolved and the UI updated appropriately.ハイパーリンクが ping 属性を持ち、その絶対 URL (群) が利用者に示される場合に、
ping
属性の字句は再解決され、
利用者界面は適切に更新されるべきです。
- If the element is a
blockquote, q,
ins, or del element with a cite attribute要素が blockquote、
q、ins、
del のいずれかの要素であって、 cite 属性を持つ場合
-
If the absolute URL identified by the cite attribute is being shown to the user, or if
any data derived from that URL is affecting the display, then the
URL should be reresolved and the UI updated appropriately.
- Otherwiseそれ以外の場合
-
The element is not directly affected.要素は直接影響されません。
Changing the base URL doesn't affect the image
displayed by img elements, although subsequent
accesses of the src DOM attribute
from script will return a new absolute URL that might
no longer correspond to the image being shown.
2.5.5 Interfaces for URL manipulation2.5.5 URL 操作用界面
An interface that has a complement of URL decomposition
attributes will have seven attributes with the following
definitions:URL 分解属性を持つ界面は、
次の定義による7つの属性を持ちます。
attribute DOMString protocol;
attribute DOMString host;
attribute DOMString hostname;
attribute DOMString port;
attribute DOMString pathname;
attribute DOMString search;
attribute DOMString hash;
The attributes defined to be URL decomposition attributes must
act as described for the attributes with the same corresponding
names in this section.URL 分解属性として定義される属性は、この節の中の同じ対応する名前の属性について説明されているように作用しなければなりません。
In addition, an interface with a complement of URL decomposition
attributes will define an input, which is a URL
that the attributes act on, and a common setter action, which is a
set of steps invoked when any of the attributes' setters are
invoked.
The seven URL decomposition attributes have similar
requirements.7つの URL 分解属性は似た要件を持ちます。
On getting, if the input
fulfills the condition given in the "getter condition" column
corresponding to the attribute in the table below, the user agent
must return the part of the input URL given in the "component"
column, with any prefixes specified in the "prefix" column
appropriately added to the start of the string and any suffixes
specified in the "suffix" column appropriately added to the end of
the string. Otherwise, the attribute must return the empty
string.取得時、利用者エージェントは、
入力が後述の表の該当属性に対応する「取得器条件」の列に与えられた条件を満たす場合、
「部品」の列で与えられる入力 URL
の一部分を、「接頭辞」の列で指定された接頭辞をその文字列のはじめに適切に追加し、
「接尾辞」の列で指定された接尾辞をその文字列の終わりに適切に追加した上で、
返さなければなりません。
そうでない場合、属性は空文字列を返さなければなりません。
On setting, the new value must first be mutated as described by
the "setter preprocessor" column, then mutated by %-escaping any
characters in the new value that are not valid in the relevant
component as given by the "component" column. Then, if the resulting
new value fulfills the condition given in the "setter condition"
column, the user agent must make a new string output by replacing the component of the URL given by
the "component" column in the input URL with the new value;
otherwise, the user agent must let output be
equal to the input. Finally,
the user agent must invoke the common setter action with the
value of output.
When replacing a component in the URL, if the component is part
of an optional group in the URL syntax consisting of a character
followed by the component, the component (including its prefix
character) must be included even if the new value is the empty
string.URL 中の部品を置き換える時、その部品が URL 構文中で1文字の後にその部品が続くような任意選択の群の一部である場合には、
その部品 (と接頭辞文字) は、新しい値が空文字列であっても含めなければなりません。
The previous paragraph applies in particular to the
":" before a <port> component, the "?" before a <query> component, and the "#" before a <fragment> component.
For the purposes of the above definitions, URLs must be parsed
using the URL parsing rules defined
in this specification.
| Attribute
属性 | Component
部品 | Getter Condition
取得器条件 | Prefix
接頭辞 | Suffix
接尾辞 | Setter Preprocessor
設定器前処理器 | Setter Condition
設定器条件 |
|---|
protocol
| <scheme>
| —
| —
| U+003A COLON (":")
| Remove all trailing U+003A COLON (":") characters
末尾のすべての U+003A COLON (":") 文字を削除 | The new value is not the empty string
新しい値は空文字列ではない |
host
| <hostport>
| input is hierarchical and uses a server-based naming authority
入力は階層的で、
鯖型命名局を使っている | —
| —
| —
| —
|
hostname
| <host>
| input is hierarchical and uses a server-based naming authority
入力は階層的で、
鯖型命名局を使っている | —
| —
| Remove all leading U+002F SOLIDUS ("/") characters
先頭のすべての U+002F SOLIDUS ("/") 文字を削除 | —
|
port
| <port>
| input is hierarchical, uses a server-based naming authority, and contained a <port> component (possibly an empty one)
入力は階層的で、
鯖型命名局を使っており、
<port>
部品を (空であったとしても) 含んでいる | —
| —
| Remove any characters in the new value that are not in the range U+0030 DIGIT ZERO .. U+0039 DIGIT NINE.
If the resulting string is empty, set it to a single U+0030 DIGIT ZERO character ('0').
新しい値の中の範囲 U+0030 DIGIT ZERO ～ U+0039 DIGIT NINE 以外の文字をすべて削除。
その結果の文字列が空の場合、単一の U+0030 DIGIT ZERO character ('0'
に設定。 | —
|
pathname
| <path>
| input is hierarchical
入力が階層的 | —
| —
| If it has no leading U+002F SOLIDUS ("/") character, prepend a U+002F SOLIDUS ("/") character to the new value
先頭が U+002F SOLIDUS ("/") 文字ではない場合、
新しい値の前に U+002F SOLIDUS ("/")
文字を追加 | —
|
search
| <query>
| input is hierarchical, and contained a <query> component (possibly an empty one)
入力は階層的で、
<query> 部品を
(空であったとしても) 含んでいる | U+003F QUESTION MARK ("?")
| —
| Remove one leading U+003F QUESTION MARK ("?") character, if any
先頭に U+003F QUESTION MARK ("?")
文字があれば、これを1つ削除 | —
|
hash
| <fragment>
| input contained a <fragment> component (possibly an empty one)
入力は階層的で、 <fragment>
部品を (空であったとしても) 含んでいる | U+0023 NUMBER SIGN ("#")
| —
| Remove one leading U+0023 NUMBER SIGN ("#") character, if any
先頭に U+0023 NUMBER SIGN ("#") 文字があれば、
これを1つ削除 | —
|
The table below demonstrates how the getter condition for search results in different results
depending on the exact original syntax of the URL:次の表は、 search
の取得器条件が元々の URL の正確な構文の違いによってどのように結果が変化するかを示しています。
| Input URL
入力 URL | search value
search 値 | Explanation
説明 |
|---|
http://example.com/
| empty string
空文字列 | No <query> component in input URL.
入力中に <query>
部品がありません。 |
http://example.com/?
| ?
| There is a <query> component, but it is empty. The question mark in the resulting value is the prefix.
<query> 部品がありますが、
空です。結果の値の疑問符は接頭辞です。 |
http://example.com/?test
| ?test
| The <query> component has the value "test".
<query>
部品は値「test」を持ちます。 |
http://example.com/?test#
| ?test
| The (empty) <fragment> component is not part of the <query> component.
(空の) <fragment>
部品は <query>
部品の一部ではありません。
|
2.6 Fetching resources
When a user agent is to fetch a resource, the
following steps must be run:
If the resource is identified by a URL, then
immediately resolve that
URL.
If the resulting absolute URL is
about:blank, then return the empty string
and abort these steps.
Perform the remaining steps asynchronously.
-
If the resource identified by the resulting absolute
URL is already being downloaded for other reasons
(e.g. another invocation of this algorithm), and the resource is
to be obtained using a idempotent action (such as an HTTP GET
or equivalent),
and the user agent is configured such that it is to reuse the data
from the existing download instead of initiating a new one, then
use the results of the existing download instead of starting a new
one.
Otherwise, at a time convenient to the user and the user agent,
download the resource, applying the semantics of the relevant
specifications (e.g. performing an HTTP GET or POST operation, or
reading the file from disk, following redirects, dereferencing javascript: URLs,
etc).
When the resource is available, queue a task
that uses the resource as appropriate. If the resource can be
processed incrementally, as, for instance, with a progressively
interlaced JPEG or an HTML file, multiple tasks may be queued to
process the data as it is downloaded. The task source
for these tasks is the networking task source.
The offline application cache
processing model introduces some changes to the networking model
to handle the returning of cached resources.
The navigation
processing model handles redirects itself, overriding the
redirection handling that would be done by the fetching
algorithm.
Whether the type
sniffing rules apply to the fetched resource depends on the
algorithm that invokes the rules — they are not always
applicable.
2.6.1 Protocol concepts
User agents can implement a variety of transfer protocols, but
this specification mostly defines behavior in terms of HTTP. [HTTP]
The HTTP GET
method is equivalent to the default retrieval action of the
protocol. For example, RETR in FTP. Such actions are idempotent and
safe, in HTTP terms.
The HTTP response
codes are equivalent to statuses in other protocols that have
the same basic meanings. For example, a "file not found" error is
equivalent to a 404 code, a server error is equivalent to a 5xx
code, and so on.
The are equivalent to fields in other protocols that have
the same basic meaning. For example, the the HTTP authentication
headers are equivalent to the authentication aspects of the FTP
protocol.
If there are any specific questions with what should
be considered equivalent to what, let me know, and I'll make it more
explicit for those cases.
Anything in this specification that refers to HTTP also applies
to HTTP-over-TLS, as represented by URLs
representing the https scheme.
User agents should report certificate errors to
the user and must either refuse to download resources sent with
erroneous certificates or must act as if such resources were in fact
served with no encryption.
Not doing so can result in users not noticing man-in-the-middle
attacks.
If a user connects to a server with a self-signed certificate,
the user agent could allow the connection but just act as if there
had been no encryption. If the user agent instead allowed the user
to override the problem and then displayed the page as if it was
fully and safely encrypted, the user could be easily tricked into
accepting man-in-the-middle connections.
If a user connects to a server with full encryption, but the
page then refers to an external resource that has an expired
certificate, then the user agent will act as if the resource was
unavailable, possibly also reporting the problem to the user. If
the user agent instead allowed the resource to be used, then an
attacker could just look for "secure" sites that used resources
from a different host and only apply man-in-the-middle attacks to
that host, for example taking over scripts in the page.
2.7 Determining the type of a resource
It is imperative that the rules in this section
be followed exactly. When a user agent uses different heuristics for
content type detection than the server expects, security problems
can occur. For example, if a server believes that the client will
treat a contributed file as an image (and thus treat it as benign),
but a Web browser believes the content to be HTML (and thus execute
any scripts contained therein), the end user can be exposed to
malicious content, making the user vulnerable to cookie theft
attacks and other cross-site scripting attacks.
2.7.1 Content-Type metadata
What explicit Content-Type
metadata is associated with the resource (the resource's type
information) depends on the protocol that was used to
fetch the resource.
For HTTP resources, only the first Content-Type HTTP header, if
any, contributes any type information; the explicit type of the
resource is then the value of that header, interpreted as described
by the HTTP specifications. If the Content-Type HTTP header is
present but the value of the first such header cannot be interpreted
as described by the HTTP specifications (e.g. because its value
doesn't contain a U+002F SOLIDUS ('/') character), then the resource
has no type information (even if there are multiple Content-Type
HTTP headers and one of the other ones is syntactically correct). [HTTP]
For resources fetched from the file system, user agents should use
platform-specific conventions, e.g. operating system extension/type
mappings.
Extensions must not be used for determining resource types for
resources fetched over HTTP.
For resources fetched over most other protocols, e.g. FTP, there
is no type information.
The , given a string s, is as
follows. It either returns an encoding or nothing.
Find the first seven characters in s
that are an ASCII case-insensitive match for the word
"charset". If no such match is found, return nothing.
Skip any U+0009, U+000A, U+000C, U+000D, or U+0020
characters that immediately follow the word 'charset' (there might
not be any).
If the next character is not a U+003D EQUALS SIGN ('='),
return nothing.
Skip any U+0009, U+000A, U+000C, U+000D, or U+0020
characters that immediately follow the equals sign (there might not
be any).
Process the next character as follows:
- If it is a U+0022 QUOTATION MARK ('"') and there is a later
U+0022 QUOTATION MARK ('"') in s
- If it is a U+0027 APOSTROPHE ("'") and there is a later
U+0027 APOSTROPHE ("'") in s
Return the string between this character and the next
earliest occurrence of this character.
- If it is an unmatched U+0022 QUOTATION MARK ('"')
- If it is an unmatched U+0027 APOSTROPHE ("'")
- If there is no next character
Return nothing.
- Otherwiseそれ以外の場合
Return the string from this character to the first U+0009,
U+000A, U+000C, U+000D, U+0020, or U+003B character or the end of
s, whichever comes first.
The above algorithm is a willful violation of the
HTTP specification. [RFC2616]
2.7.2 Content-Type sniffing: Web pages
The sniffed type of a
resource must be found as follows:
If the user agent is configured to strictly obey
Content-Type headers for this resource, then jump to the last step
in this set of steps.
If the resource was fetched over an HTTP protocol and there
is an HTTP Content-Type header and the value of the first such
header has bytes that exactly match one of the following lines:
| Bytes in Hexadecimal
バイトの十六進数表現 | Textual representation
|
|---|
| 74 65 78 74 2f 70 6c 61 69 6e
| text/plain
|
| 74 65 78 74 2f 70 6c 61 69 6e 3b 20 63 68 61 72 73 65 74 3d 49 53 4f 2d 38 38 35 39 2d 31
| text/plain; charset=ISO-8859-1
|
| 74 65 78 74 2f 70 6c 61 69 6e 3b 20 63 68 61 72 73 65 74 3d 69 73 6f 2d 38 38 35 39 2d 31
| text/plain; charset=iso-8859-1
|
| 74 65 78 74 2f 70 6c 61 69 6e 3b 20 63 68 61 72 73 65 74 3d 55 54 46 2d 38
| text/plain; charset=UTF-8
|
...then jump to the text or binary section below.
Let official type be the type given by
the Content-Type metadata for the
resource, ignoring parameters. If there is no such type, jump to
the unknown type
step below. Comparisons with this type, as defined by MIME
specifications, are done in an ASCII case-insensitive
manner. [RFC2046]
If official type is "unknown/unknown" or
"application/unknown", jump to the unknown type step below.
If official type ends in "+xml", or if
it is either "text/xml" or "application/xml", then the sniffed
type of the resource is official type; return
that and abort these steps.
If official type is an image type
supported by the user agent (e.g. "image/png", "image/gif",
"image/jpeg", etc), then jump to the images section below, passing it the official type.
If official type is "text/html", then
jump to the feed or
HTML section below.
The sniffed type of the resource is official
type.
2.7.3 Content-Type sniffing: text or binary2.7.3 Content-Type 探知: テキストまたはバイナリー
The user agent may wait for 512 or more bytes of the resource
to be available.利用者エージェントは、資源の 512 バイト以上が利用可能となるまで待って構いません。
Let n be the smaller of either 512 or
the number of bytes already available.n を、512 か、既に利用可能なバイト数の小さい方とします。
-
If n is 4 or more, and the first bytes of
the resource match one of the following byte sets:n が 4 以上であり、資源の最初の数バイトが次のバイト集合のいずれかに一致する場合、
| Bytes in Hexadecimal
バイトの十六進数表現 | Description
説明 |
|---|
| FE FF
| UTF-16BE BOM
|
| FF FE
| UTF-16LE BOM
|
| EF BB BF
| UTF-8 BOM
|
...then the sniffed type of the resource is "text/plain". Abort
these steps.資源の探知型は「text/plain」です。これらの段階を停止します。
If none of the first n bytes of the
resource are binary data bytes then the sniffed type
of the resource is "text/plain". Abort these steps.資源の最初の n バイトのいずれもがバイナリー・データ・バイトでない場合、
資源の探知型は「text/plain」です。これらの段階を停止します。
-
If the first bytes of the resource match one of the byte
sequences in the "pattern" column of the table in the unknown type
section below, ignoring any rows whose cell in the "security"
column says "scriptable" (or "n/a"), then the sniffed type of the
resource is the type given in the corresponding cell in the
"sniffed type" column on that row; abort these steps.資源の最初のバイトが、
後の未知型の節の表のうち、
「保安性」の列がのこまが「スクリプト可能」 (か「N/A」) となっている行以外で、
「パターン」の列のバイト列のいずれかと一致する場合、
資源の探知型は、その行の「探知型」の列の対応するこまで与えられた型です。
これらの段階を停止します。
It is critical that this step not ever return a
scriptable type (e.g. text/html), as otherwise that would allow a
privilege escalation attack.この段階でスクリプト可能な型 (例えば text/html) を返さないことは重要であり、
そうしなければ特権昇格攻撃を認めることになってしまいます。
Otherwise, the sniffed type of the resource is
"application/octet-stream".そうでない場合、資源の探知型は「application/octet-stream」です。
Bytes covered by the following ranges are binary data
bytes:次の範囲に含まれるバイトがバイナリー・データ・バイトです。
0x00 - 0x08
0x0B
0x0E - 0x1A
0x1C - 0x1F
2.7.4 Content-Type sniffing: unknown type2.7.4 Content-Type 探知: 未知型
The user agent may wait for 512 or more bytes of the
resource to be available.利用者エージェントは、資源の 512 バイト以上が利用可能となるまで待って構いません。
Let stream length be the smaller of
either 512 or the number of bytes already available.stream length を、 512 と既に利用可能なバイトの数の小さい方とします。
For each row in the table below:後掲の表の各表について、
- If the row has no "WS" bytes:行が「WS」バイトを持たない場合、
-
Let pattern length be the length of the
pattern (number of bytes described by the cell in the second
column of the row).pattern length を、パターンの長さ
(行の2つ目のこまに記述されたバイトの数)
とします。
If stream length is smaller than pattern length then skip this row.stream length が pattern length
より小さい場合、この行を飛ばします。
Apply the "and" operator to the first pattern
length bytes of the resource and the given mask (the
bytes in the cell of first column of that row), and let the
result be the data.資源の最初の pattern
length バイトと与えられたマスク (その行の最初の列のこまのバイト列)
に「論理積」演算子を適用し、その結果を data とします。
If the bytes of the data matches the
given pattern bytes exactly, then the sniffed type of the
resource is the type given in the cell of the third column in
that row; abort these steps.data のバイト列が与えられたパターン・バイト列と正確に一致する場合、
資源の探知型はその行の3つ目の列のこまで与えられる型です。
これらの段階を停止します。
- If the row has a "WS" byte:行が「WS」バイトを持つ場合、
-
Let indexpattern be an
index into the mask and pattern byte strings of the
row.indexpattern を、行のマスクとパターンのバイト列の中の索引とします。
Let indexstream be an
index into the byte stream being examined.indexstream を、検査するバイト・ストリームの中の索引とします。
Loop: If indexstream points beyond the end of
the byte stream, then this row doesn't match, skip this
row.ループ: indexstream がバイト・ストリームの終わりの先を指している場合、
この行は一致せず、この行を飛ばします。
-
Examine the indexstreamth
byte of the byte stream as follows:バイト・ストリームの indexstream
番目のバイトを次のように検査します。
- If the indexpatternth byte
of the pattern is a normal hexadecimal byte and not a "WS"
byte:パターンの indexpattern
番目のバイトが通常の十六進数バイトであって「WS」バイトでない場合、
-
If the "and" operator, applied to the indexstreamth byte of the stream
and the indexpatternth byte
of the mask, yield a value different that the indexpatternth byte of the
pattern, then skip this row.
Otherwise, increment indexpattern to the next byte in
the mask and pattern and indexstream to the next byte in
the byte stream.そうでない場合、 indexpattern
をマスクとパターンの次のバイトに、
indexstream
をバイト・ストリームの次のバイトにと増加させます。
- Otherwise, if the indexpatternth byte of the pattern
is a "WS" byte:そうでない場合、パターンの indexpattern
番目のバイトが「WS」バイトの場合、
-
"WS" means "whitespace", and allows insignificant
whitespace to be skipped when sniffing for a type
signature.「WS」は「空白」を意味し、型署名の探知の時に重要でない空白を飛ばすことを認めます。
If the indexstreamth byte
of the stream is one of 0x09 (ASCII TAB), 0x0A (ASCII LF),
0x0C (ASCII FF), 0x0D (ASCII CR), or 0x20 (ASCII space),
then increment only the indexstream to the next byte in
the byte stream.ストリームの indexstream
番目のバイトが 0x09 (ASCII TAB)、0x0A (ASCII LF)、
0x0C (ASCII FF)、0x0D (ASCII CR)、0x20 (ASCII 間隔)
のいずれかの場合、 indexstream
をバイト・ストリームの次のバイトへと増加させます。
Otherwise, increment only the indexpattern to the next byte in
the mask and pattern.そうでない場合、 indexpattern
だけをマスクとパターンの次のバイトへと増加させます。
If indexpattern does not
point beyond the end of the mask and pattern byte strings, then
jump back to the loop step in this algorithm.indexpattern がマスクとパターンのバイト列の終わりの先を指していない場合、この算法のループの段階に飛んで戻ります。
Otherwise, the sniffed type of the resource is the type
given in the cell of the third column in that row; abort these
steps.そうでない場合、資源の探知型はその行の3番目の列のこまに与えられた型です。
これらの段階を停止します。
If none of the first n bytes of the
resource are binary data bytes then the sniffed type
of the resource is "text/plain". Abort these steps.資源の最初の n バイトのいずれもがバイナリー・データ・バイトでない場合、
資源の探知型は「text/plain」です。これらの段階を停止します。
Otherwise, the sniffed type of the resource is
"application/octet-stream".そうでない場合、資源の探知型は「application/octet-stream」です。
The table used by the above algorithm is:先述の算法で用いる表は、次の通りです。
| Bytes in Hexadecimal
バイトの十六進数表現 | Sniffed type
探知型 | Security
保安性 | Comment
注釈 |
|---|
| Mask
マスク | Pattern
パターン |
|---|
| FF FF DF DF DF DF DF DF DF FF DF DF DF DF
| 3C 21 44 4F 43 54 59 50 45 20 48 54 4D 4C
| text/html
| Scriptable
スクリプト可能 | The string "<!DOCTYPE HTML" in US-ASCII or compatible encodings, case-insensitively.
US-ASCII や互換な符号化で文字列「<!DOCTYPE HTML」
を大文字または小文字で。 |
| FF FF DF DF DF DF
| WS 3C 48 54 4D 4C
| text/html
| Scriptable
スクリプト可能 | The string "<HTML" in US-ASCII or compatible encodings, case-insensitively, possibly with leading spaces.
US-ASCII や互換な符号化で文字列「<HTML」
を大文字または小文字で、最初に間隔があってもよい。 |
| FF FF DF DF DF DF
| WS 3C 48 45 41 44
| text/html
| Scriptable
スクリプト可能 | The string "<HEAD" in US-ASCII or compatible encodings, case-insensitively, possibly with leading spaces.
US-ASCII や互換な符号化で文字列「<HEAD」
を大文字または小文字で、最初に間隔があってもよい。 |
| FF FF DF DF DF DF DF DF
| WS 3C 53 43 52 49 50 54
| text/html
| Scriptable
スクリプト可能 | The string "<SCRIPT" in US-ASCII or compatible encodings, case-insensitively, possibly with leading spaces.
US-ASCII や互換な符号化で文字列「<SCRIPT」
を大文字または小文字で、最初に間隔があってもよい。 |
| FF FF FF FF FF
| 25 50 44 46 2D
| application/pdf
| Scriptable
スクリプト可能 | The string "%PDF-", the PDF signature.
文字列「%PDF-」、 PDF 署名。 |
| FF FF FF FF FF FF FF FF FF FF FF
| 25 21 50 53 2D 41 64 6F 62 65 2D
| application/postscript
| Safe
安全 | The string "%!PS-Adobe-", the PostScript signature.
|
| FF FF 00 00
| FE FF 00 00
| text/plain
| n/a
N/A | UTF-16BE BOM
|
| FF FF 00 00
| FF FF 00 00
| text/plain
| n/a
N/A | UTF-16LE BOM
|
| FF FF FF 00
| EF BB BF 00
| text/plain
| n/a
N/A | UTF-8 BOM
|
| FF FF FF FF FF FF
| 47 49 46 38 37 61
| image/gif
| Safe
安全 | The string "GIF87a", a GIF signature.
文字列「GIF87a」、GIF 署名。 |
| FF FF FF FF FF FF
| 47 49 46 38 39 61
| image/gif
| Safe
安全 | The string "GIF89a", a GIF signature.
文字列「GIF89a」、GIF 署名。 |
| FF FF FF FF FF FF FF FF
| 89 50 4E 47 0D 0A 1A 0A
| image/png
| Safe
安全 | The PNG signature.
PNG 署名。 |
| FF FF FF
| FF D8 FF
| image/jpeg
| Safe
安全 | A JPEG SOI marker followed by the first byte of another marker.
JPEG SOI マーカーの後に別のマーカーの最初のバイト。 |
| FF FF
| 42 4D
| image/bmp
| Safe
安全 | The string "BM", a BMP signature.
文字列「BM」、BMP 署名。 |
| FF FF FF FF
| 00 00 01 00
| image/vnd.microsoft.icon
| Safe
安全 | A 0 word following by a 1 word, a Windows Icon file format signature.
語 0 の後に語 1、 Windows アイコン・ファイル書式署名。 |
I'd like to add types like MPEG, AVI, Flash,
Java, etc, to the above table.MPEG、AVI、Flash、Java などの型も上の表に追加したいと思っています。
User agents may support further types if desired, by implicitly
adding to the above table. However, user agents should not use any
other patterns for types already mentioned in the table above, as
this could then be used for privilege escalation (where, e.g., a
server uses the above table to determine that content is not HTML
and thus safe from XSS attacks, but then a user agent detects it as
HTML anyway and allows script to execute).利用者エージェントは、必要があれば、前掲の表に暗示的に追加することによって、
更に別の型に対応して構いません。
しかし、前掲の表で既に言及されている型に関して他のパターンを使うと、
特権昇格に使うことができてしまいます
(例えば、鯖が前掲の表を使って内容が HTML ではないと判定し、
よって XSS 攻撃に関して安全と判定したところ、
利用者エージェントがそれは HTML であると判定し、
スクリプトが実行されるのを認めてしまいます。) から、
利用者エージェントはそうするべきではありません。
The column marked "security" is used by the algorithm in the
"text or binary" section, to avoid sniffing text/plain content as a type that can be used for a
privilege escalation attack.「保安性」と印された列は、「テキストまたはバイナリー」の節の算法で、
text/plain
の内容を特権昇格攻撃に使える型と探知してしまうことを避けるために使います。
2.7.5 Content-Type sniffing: image2.7.5 Content-Type 探知: 画像
If the resource's official type is
"image/svg+xml", then the sniffed type of the resource is its official type (an XML type).資源の official type が
「image/svg+xml」の場合、資源の探知型はその
official type (XML 型) です。
Otherwise, if the first bytes of the resource match one of the
byte sequences in the first column of the following table, then the
sniffed type of the resource is the type given in the corresponding
cell in the second column on the same row:そうでない場合、資源の最初の数バイトが次の表の最初の列のバイト列のいずれかと一致する場合、
資源の探知型は同じ行の2番目の列の対応するこまで与えられる型です。
| Bytes in Hexadecimal
バイトの十六進数表現 | Sniffed type
探知型 | Comment
注釈
|
|---|
| 47 49 46 38 37 61
| image/gif
| The string "GIF87a", a GIF signature.
文字列「GIF87a」、GIF 署名。 |
| 47 49 46 38 39 61
| image/gif
| The string "GIF89a", a GIF signature.
文字列「GIF89a」、GIF 署名。 |
| 89 50 4E 47 0D 0A 1A 0A
| image/png
| The PNG signature.
PNG 署名。 |
| FF D8 FF
| image/jpeg
| A JPEG SOI marker followed by the first byte of another marker.
JPEG SOI マーカーの後に別のマーカーの最初のバイト。 |
| 42 4D
| image/bmp
| The string "BM", a BMP signature.
文字列「BM」、BMP 署名。 |
| 00 00 01 00
| image/vnd.microsoft.icon
| A 0 word following by a 1 word, a Windows Icon file format signature.
語 0 の後に語 1、 Windows アイコン・ファイル書式署名。
|
Otherwise, the sniffed type of the resource is the same as
its official type.そうでない場合、資源の探知型は official type と同じです。
2.7.6 Content-Type sniffing: feed or HTML2.7.6 Content-Type sniffing: フィードまたは HTML
The user agent may wait for 512 or more bytes of the
resource to be available.利用者エージェントは、資源の 512 バイト以上が利用可能となるまで待って構いません。
Let s be the stream of bytes, and let
s[i] represent
the byte in s with position i, treating s as zero-indexed
(so the first byte is at i=0).s をバイトのストリームとし、
s[i] を s
中の位置 i のバイトを表すとします。
ただし、 s は零索引付けされている
(ので最初のバイトは位置 i=0 にある) とします。
If at any point this algorithm requires the user agent to
determine the value of a byte in s which is not
yet available, or which is past the first 512 bytes of the
resource, or which is beyond the end of the resource, the user
agent must stop this algorithm, and assume that the sniffed type of
the resource is "text/html".この算法のいずれかの地点で利用者エージェントが s 中のまだ利用可能となっていないバイトや資源の最初の512バイトを越えたバイトや資源の終わりを越えたバイトの値を判断することを要求する場合には、
利用者エージェントはこの算法を停止し、資源の探知型は「text/html」
であるとしなければなりません。
User agents are allowed, by the first step of this
algorithm, to wait until the first 512 bytes of the resource are
available.利用者エージェントは、この算法の最初の段階により、資源の最初の 512 バイトが利用可能となるまで待つことが認められています。
Initialize pos to 0.pos を 0 に初期化します。
If s[0] is 0xEF, s[1] is 0xBB, and s[2] is 0xBF, then set pos to 3. (This skips over a leading UTF-8 BOM, if
any.)s[0] が 0xEF、
s[1] が 0xBB、
s[2] が 0xBF
の場合、 pos を 3 に設定します。
(これは先頭に UTF-8 BOM があれば読み飛ばします。)
Loop start: Examine s[pos].ループ開始: s[pos] を調べます。
- If it is 0x09 (ASCII tab), 0x20 (ASCII space), 0x0A (ASCII LF), or 0x0D (ASCII CR)0x09 (ASCII タブ)、0x20 (ASCII 間隔)、0x0A (ASCII LF)、0x0D (ASCII CR)
のいずれかの場合
- Increase pos by 1 and repeat this step.pos を 1 増加させ、この段階を繰り返します。
- If it is 0x3C (ASCII "
<")0x3C (ASCII "<") の場合
- Increase pos by 1 and go to the next step.pos を 1 増加させ、次の段階へ行きます。
- If it is anything elseそれ以外の場合
- The sniffed type of the resource is "text/html". Abort these
steps.資源の探知型は「text/html」です。これらの段階を停止します。
If the bytes with positions pos to
pos+2 in s are
exactly equal to 0x21, 0x2D, 0x2D respectively (ASCII for "!--"), then:s 中の位置 pos ～ pos+2
のバイトが 0x21、0x2D、0x2D
(ASCII の「!--」) とそれぞれ正確に等しい場合、
Increase pos by 3.pos を 3 増加させます。
If the bytes with positions pos to pos+2 in s are exactly
equal to 0x2D, 0x2D, 0x3E respectively (ASCII for "-->"), then increase pos
by 3 and jump back to the previous step (the step labeled
loop start) in the overall algorithm in this section.s 中の位置 pos ～ pos+2 のバイトがそれぞれ 0x2D、0x2D、0x3E (ASCII の
「-->」) と正確に等しい場合、
pos を 3 増加させ、この節の全体の算法の前の段階
(ループ開始と名札付けされた段階) に飛んで戻ります。
Otherwise, increase pos by 1.そうでない場合、 pos を 1 増加させます。
Return to step 2 in these substeps.手順 2 in these substeps に戻ります。
If s[pos] is 0x21 (ASCII "!"):s[pos] が 0x21 (ASCII "!") の場合、
Increase pos by 1.pos を 1 増加させます。
If s[pos] equal 0x3E, then increase pos by 1 and jump back to the step labeled
loop start in the overall algorithm in this section.
Otherwise, return to step 1 in these substeps.
If s[pos] is 0x3F (ASCII "?"):
Increase pos by 1.pos を 1 増加させます。
If s[pos] and s[pos+1] equal 0x3F and 0x3E respectively,
then increase pos by 1 and jump back to the
step labeled loop start in the overall algorithm in this
section.
Otherwise, return to step 1 in these substeps.
Otherwise, if the bytes in s starting at
pos match any of the sequences of bytes in the
first column of the following table, then the user agent must
follow the steps given in the corresponding cell in the second
column of the same row.
| Bytes in Hexadecimal
バイトの十六進数表現 | Requirement
要件 | Comment
注釈 |
|---|
| 72 73 73
| The sniffed type of the resource is "application/rss+xml"; abort these steps
| The three ASCII characters "rss"
ASCII 文字3文字「rss」 |
| 66 65 65 64
| The sniffed type of the resource is "application/atom+xml"; abort these steps
| The four ASCII characters "feed"
|
| 72 64 66 3A 52 44 46
| Continue to the next step in this algorithm
| The ASCII characters "rdf:RDF"
|
If none of the byte sequences above match the bytes in s starting at pos, then the
sniffed type of the resource is "text/html". Abort these
steps.
If, before the next ">", you find two
xmlns* attributes with http://www.w3.org/1999/02/22-rdf-syntax-ns#
and http://purl.org/rss/1.0/ as the namespaces, then the sniffed
type of the resource is "application/rss+xml", abort these
steps. (maybe we only need to check for http://purl.org/rss/1.0/
actually)
Otherwise, the sniffed type of the resource is
"text/html".そうでない場合、資源の探知型は「text/html」です。
For efficiency reasons, implementations may wish to
implement this algorithm and the algorithm for detecting the
character encoding of HTML documents in parallel.
2.8 Common DOM interfaces2.8 共通 DOM 界面
2.8.1 Reflecting content attributes in DOM attributes2.8.1 DOM 属性への内容属性の反映
Some DOM attributes are
defined to reflect a particular content
attribute. This means that on getting, the DOM attribute
returns the current value of the content attribute, and on setting,
the DOM attribute changes the value of the content attribute to the
given value.
If a reflecting DOM attribute is a DOMString
attribute whose content attribute is defined to contain a
URL, then on getting, the DOM attribute must resolve the value of the content
attribute and return the resulting absolute URL if that
was successful, or the empty string otherwise; and on setting, must
set the content attribute to the specified literal value. If the
content attribute is absent, the DOM attribute must return the
default value, if the content attribute has one, or else the empty
string.
If a reflecting DOM attribute is a DOMString
attribute whose content attribute is defined to contain one or more
URLs, then on getting, the DOM attribute
must split the content
attribute on spaces and return the concatenation of resolving each token URL to an
absolute URL, with a single U+0020 SPACE character
between each URL, ignoring any tokens that did not resolve
successfully. If the content attribute is absent, the DOM attribute
must return the default value, if the content attribute has one, or
else the empty string. On setting, the DOM attribute must set the
content attribute to the specified literal value.
If a reflecting DOM attribute is a DOMString whose
content attribute is an enumerated attribute, and the
DOM attribute is limited to only known values, then, on
getting, the DOM attribute must return the conforming value
associated with the state the attribute is in (in its canonical
case), or the empty string if the attribute is in a state that has
no associated keyword value; and on setting, if the new value is an
ASCII case-insensitive match for one of the keywords
given for that attribute, then the content attribute must be set to
the conforming value associated with the state that the attribute
would be in if set to the given new value, otherwise, if the new
value is the empty string, then the content attribute must be
removed, otherwise, the setter must raise a SYNTAX_ERR
exception.
If a reflecting DOM attribute is a DOMString but
doesn't fall into any of the above categories, then the getting and
setting must be done in a transparent, case-preserving manner.
If a reflecting DOM attribute is a boolean attribute, then on
getting the DOM attribute must return true if the attribute is set,
and false if it is absent. On setting, the content attribute must be
removed if the DOM attribute is set to false, and must be set to
have the same value as its name if the DOM attribute is set to
true. (This corresponds to the rules for boolean content attributes.)
If a reflecting DOM attribute is a signed integer type
(long) then, on getting, the content attribute must be
parsed according to the
rules for parsing signed integers, and if that is successful,
the resulting value must be returned. If, on the other hand, it
fails, or if the attribute is absent, then the default value must be
returned instead, or 0 if there is no default value. On setting, the
given value must be converted to the shortest possible string
representing the number as a valid integer in base ten
and then that string must be used as the new content attribute
value.
If a reflecting DOM attribute is an unsigned integer
type (unsigned long) then, on getting, the content
attribute must be parsed according to the rules for parsing unsigned
integers, and if that is successful, the resulting value must
be returned. If, on the other hand, it fails, or if the attribute is
absent, the default value must be returned instead, or 0 if there is
no default value. On setting, the given value must be converted to
the shortest possible string representing the number as a
valid non-negative integer in base ten and then that
string must be used as the new content attribute value.
If a reflecting DOM attribute is an unsigned integer type
(unsigned long) that is limited to only positive
non-zero numbers, then the behavior is similar to the previous
case, but zero is not allowed. On getting, the content attribute
must first be parsed according to the rules for parsing unsigned
integers, and if that is successful, the resulting value must
be returned. If, on the other hand, it fails, or if the attribute is
absent, the default value must be returned instead, or 1 if there is
no default value. On setting, if the value is zero, the user agent
must fire an INDEX_SIZE_ERR exception. Otherwise, the
given value must be converted to the shortest possible string
representing the number as a valid non-negative integer
in base ten and then that string must be used as the new content
attribute value.
If a reflecting DOM attribute is a floating point number type
(float) and it doesn't fall into one of the earlier
categories, then, on getting, the content attribute must be parsed
according to the rules for parsing floating point number values,
and if that is successful, the resulting value must be returned. If,
on the other hand, it fails, or if the attribute is absent, the
default value must be returned instead, or 0.0 if there is no
default value. On setting, the given value must be converted to the
shortest possible string representing the number as a valid
floating point number in base ten and then that string must
be used as the new content attribute value.
If a reflecting DOM attribute is of the type
DOMTokenList, then on getting it must return a
DOMTokenList object whose underlying string is the
element's corresponding content attribute. When the
DOMTokenList object mutates its underlying string, the
content attribute must itself be immediately mutated. When the
attribute is absent, then the string represented by the
DOMTokenList object is the empty string; when the
object mutates this empty string, the user agent must first add the
corresponding content attribute, and then mutate that attribute
instead. DOMTokenList attributes are always
read-only. The same DOMTokenList object must be
returned every time for each attribute.
If a reflecting DOM attribute has the type
HTMLElement, or an interface that descends from
HTMLElement, then, on getting, it must run the
following algorithm (stopping at the first point where a value is
returned):
If the corresponding content attribute is absent, then the
DOM attribute must return null.
Let candidate be the element that the document.getElementById() method would find if it
was passed as its argument the current value of the corresponding
content attribute.
If candidate is null, or if it is not
type-compatible with the DOM attribute, then the DOM attribute must
return null.
Otherwise, it must return candidate.
On setting, if the given element has an id attribute, then the content attribute must
be set to the value of that id
attribute. Otherwise, the DOM attribute must be set to the empty
string.
2.8.2 Collections2.8.2 集成
The HTMLCollection,
HTMLFormControlsCollection, and
HTMLOptionsCollection interfaces represent various
lists of DOM nodes. Collectively, objects implementing these
interfaces are called collections.
When a collection is created, a
filter and a root are associated with the collection.
For example, when the HTMLCollection
object for the document.images attribute is
created, it is associated with a filter that selects only
img elements, and rooted at the root of the
document.
The collection then represents a
live view of the subtree rooted at the collection's
root, containing only nodes that match the given filter. The view is
linear. In the absence of specific requirements to the contrary, the
nodes within the collection must be sorted in tree
order.
The rows list is
not in tree order.
An attribute that returns a collection must return the same
object every time it is retrieved.集成を返す属性は、オブジェクトが取り出される度に毎回同じオブジェクトを返さなければなりません。
2.8.2.1 HTMLCollection
The HTMLCollection interface represents a generic
collection of elements.HTMLCollection
界面は、一般的な要素の集成を表します。
interface HTMLCollection {
readonly attribute unsigned long length;
[IndexGetter] Element item(in unsigned long index);
[NameGetter] Element namedItem(in DOMString name);
};
The length
attribute must return the number of nodes represented by the
collection.length
属性は集成が表現する節点の数を返さなければなりません。
The item(index) method must return the indexth node in the collection. If there is no indexth node in the collection, then the method must
return null.item(index) メソッドは集成中の index 番目の節点を返さなければなりません。
集成中の index 番目の節点が存在しない場合は、
メソッドは null を返さなければなりません。
The namedItem(key) method must return the first node
in the collection that matches the following requirements:namedItem(key) メソッドは、
集成中で次のいずれかの要件に一致する最初の節点を返さなければなりません。
It is an a, applet,
area, form, img, or
object element with a name attribute equal to key, or,
It is an HTML element of any
kind with an id attribute equal to
key. (Non-HTML elements, even if they have IDs,
are not searched for the purposes of namedItem().)任意の種類の HTML
要素であって、 id 属性が key
と等しいもの。 (非 HTML 要素は、 ID を有していたとしても、
namedItem() では検索されません。)
If no such elements are found, then the method must return
null.そのような要素が存在しない場合、メソッドは null
を返さなければなりません。
The HTMLFormControlsCollection interface represents
a collection of listed elements in form
and fieldset elements.
interface HTMLFormControlsCollection {
readonly attribute unsigned long length;
[IndexGetter] HTMLElement item(in unsigned long index);
[NameGetter] Object namedItem(in DOMString name);
};
The length
attribute must return the number of nodes represented by the
collection.length
属性は集成が表現する節点の数を返さなければなりません。
The item(index) method must return the indexth node in the collection. If there is no indexth node in the collection, then the method must
return null.item(index) メソッドは集成中の index 番目の節点を返さなければなりません。集成中に
index 番目の節点が存在しなければ、メソッドは null
を返さなければなりません。
The namedItem(key)
method must act according to the following algorithm:
namedItem(key) メソッドは次の算法に従って動作しなければなりません。
If, at the time the method is called, there is exactly one node
in the collection that has either an id attribute or a name attribute equal to key, then return that node and stop the
algorithm.
Otherwise, if there are no nodes in the collection that have
either an id attribute or a name attribute equal to key, then return null and stop the algorithm.
Otherwise, create a NodeList object representing a
live view of the HTMLFormControlsCollection object,
further filtered so that the only nodes in the
NodeList object are those that have either an id attribute or a name attribute equal to key. The nodes in the NodeList object
must be sorted in tree order.
Return that NodeList object.その NodeList オブジェクトを返します。
2.8.2.3 HTMLOptionsCollection
The HTMLOptionsCollection interface represents a
list of option elements. It is always rooted on a
select element and has attributes and methods that
manipulate that element's descendants.
interface HTMLOptionsCollection {
attribute unsigned long length;
[IndexGetter] HTMLOptionElement item(in unsigned long index);
[NameGetter] Object namedItem(in DOMString name);
void add(in HTMLElement element, in HTMLElement before);
void add(in HTMLElement element, in long before);
void remove(in long index);
};
On getting, the length
attribute must return the number of nodes represented by the
collection.
On setting, the behavior depends on whether the new value is
equal to, greater than, or less than the number of nodes
represented by the collection at that time. If the
number is the same, then setting the attribute must do nothing. If
the new value is greater, then n new
option elements with no attributes and no child nodes
must be appended to the select element on which the
HTMLOptionsCollection is rooted, where n is the difference between the two numbers (new
value minus old value). If the new value is lower, then the last
n nodes in the collection must be removed from
their parent nodes, where n is the difference
between the two numbers (old value minus new value).
Setting length never removes
or adds any optgroup elements, and never adds new
children to existing optgroup elements (though it can
remove children from them).
The item(index) method must return the indexth node in the collection. If there is no indexth node in the collection, then the method must
return null.
The namedItem(key)
method must act according to the following algorithm:
If, at the time the method is called, there is exactly one node
in the collection that has either an id attribute or a name attribute equal to key, then return that node and stop the
algorithm.
Otherwise, if there are no nodes in the collection that have
either an id attribute or a name attribute equal to key, then return null and stop the algorithm.
Otherwise, create a NodeList object representing a
live view of the HTMLOptionsCollection object, further
filtered so that the only nodes in the NodeList object
are those that have either an id
attribute or a name attribute
equal to key. The nodes in the
NodeList object must be sorted in tree
order.
Return that NodeList object.その NodeList オブジェクトを返します。
The add(element, before)
method must act according to the following algorithm:
If element is not an option
or optgroup element, then return and abort these
steps.
If element is an ancestor of the
select element element on which the
HTMLOptionsCollection is rooted, then throw a
HIERARCHY_REQUEST_ERR exception.
If before is an element, but that
element isn't a descendant of the select element
element on which the HTMLOptionsCollection is rooted,
then throw a NOT_FOUND_ERR exception.
If element and before are the same element, then return and abort
these steps.
If before is a node, then let reference be that node. Otherwise, if before is an integer, and there is a beforeth node in the collection, let reference be that node. Otherwise, let reference be null.
If reference is not null, let parent be the parent node of reference. Otherwise, let parent
be the select element element on which the
HTMLOptionsCollection is rooted.
Act as if the DOM Core insertBefore() method was invoked
on the parent node, with element as the first argument and reference as the second argument.
The remove(index) method must act according to
the following algorithm:
If the number of nodes represented by the
collection is zero, abort these steps.
If index is not a number greater than or
equal to 0 and less than the number of nodes represented by
the collection, let element be the first
element in the collection. Otherwise, let element be the indexth element
in the collection.
Remove element from its parent
node.
2.8.3 DOMTokenList
The DOMTokenList interface represents an interface
to an underlying string that consists of an unordered set of
unique space-separated tokens.
Which string underlies a particular DOMTokenList
object is defined when the object is created. It might be a content
attribute (e.g. the string that underlies the classList object is the class attribute), or it might be an
anonymous string (e.g. when a DOMTokenList object is
passed to an author-implemented callback in the
datagrid APIs).
[Stringifies] interface DOMTokenList {
readonly attribute unsigned long length;
[IndexGetter] DOMString item(in unsigned long index);
boolean has(in DOMString token);
void add(in DOMString token);
void remove(in DOMString token);
boolean toggle(in DOMString token);
};
The length
attribute must return the number of unique tokens that
result from splitting the
underlying string on spaces.
The item(index) method must split the underlying string on spaces, sort
the resulting list of tokens by Unicode codepoint,
remove exact duplicates, and then return the indexth item in this list. If index is equal to or greater than the number of
tokens, then the method must return null.
The has(token) method must run the following
algorithm:
If the token argument contains any space characters, then raise an
INVALID_CHARACTER_ERR exception and stop the
algorithm.
Otherwise, split the
underlying string on spaces to get the list of tokens in the
object's underlying string.
If the token indicated by token is one of
the tokens in the object's underlying string then return true and
stop this algorithm.
Otherwise, return false.
The add(token) method must run the following
algorithm:
If the token argument contains any space characters, then raise an
INVALID_CHARACTER_ERR exception and stop the
algorithm.
Otherwise, split the
underlying string on spaces to get the list of tokens in the
object's underlying string.
If the given token is already one of the
tokens in the DOMTokenList object's underlying string
then stop the algorithm.
Otherwise, if the DOMTokenList object's underlying
string is not the empty string and the last character of that
string is not a space character, then append a U+0020
SPACE character to the end of that string.
Append the value of token to the end of the
DOMTokenList object's underlying string.
The remove(token) method must run the following
algorithm:
If the token argument contains any space characters, then raise an
INVALID_CHARACTER_ERR exception and stop the
algorithm.
Otherwise, remove
the given token from the underlying
string.
The toggle(token) method must run the following
algorithm:
If the token argument contains any space characters, then raise an
INVALID_CHARACTER_ERR exception and stop the
algorithm.
Otherwise, split the
underlying string on spaces to get the list of tokens in the
object's underlying string.
If the given token is already one of the
tokens in the DOMTokenList object's underlying string
then remove the given
token from the underlying string, and
stop the algorithm, returning false.
Otherwise, if the DOMTokenList object's underlying
string is not the empty string and the last character of that
string is not a space character, then append a U+0020
SPACE character to the end of that string.
Append the value of token to the end of the
DOMTokenList object's underlying string.
Return true.
Objects implementing the DOMTokenList interface must
stringify to the object's
underlying string representation.
2.8.4 DOMStringMap
The DOMStringMap interface represents a set of
name-value pairs. When a DOMStringMap object is
instanced, it is associated with three algorithms, one for getting
values from names, one for setting names to certain values, and one
for deleting names.DOMStringMap 界面は、
名前と値の組の集合を表します。
DOMStringMap オブジェクトが実現値化される時には、このオブジェクトは名前から値を取得する算法、
名前にある値を設定する算法、
名前を削除する算法の3つの算法と関連付けられます。
The names of the methods on this interface are
temporary and will be fixed when the Web IDL / "Language Bindings
for DOM Specifications" spec is ready to handle this case.
interface DOMStringMap {
[NameGetter] DOMString XXX1(in DOMString name);
[NameSetter] void XXX2(in DOMString name, in DOMString value);
[XXX] boolean XXX3(in DOMString name);
};
The XXX1(name) method must call the algorithm for
getting values from names, passing name as the
name, and must return the corresponding value, or null if name has no corresponding value.
The XXX2(name, value) method
must call the algorithm for setting names to certain values, passing
name as the name and value
as the value.
The XXX3(name) method must call the algorithm for
deleting names, passing name as the name, and
must return true.
2.8.5 DOM feature strings2.8.5 DOM 機能文字列
DOM3 Core defines mechanisms for checking for interface support,
and for obtaining implementations of interfaces, using feature
strings. [DOM3CORE]DOM 中核は、機能文字列を使って、界面に対応するか検査したり、
界面の実装を得たりする仕組みを定義してます。 [DOM3CORE]
A DOM application can use the hasFeature(feature,
version) method of the
DOMImplementation interface with parameter values
"HTML" and "5.0" (respectively)
to determine whether or not this module is supported by the
implementation. In addition to the feature string "HTML", the feature string "XHTML" (with version string "5.0") can
be used to check if the implementation supports XHTML. User agents
should respond with a true value when the hasFeature
method is queried with these values. Authors are cautioned, however,
that UAs returning true might not be perfectly compliant, and that
UAs returning false might well have support for features in this
specification; in general, therefore, use of this method is
discouraged.DOM アプリケーションは、 DOMImplementation 界面の hasFeature(feature,
version)
メソッドに、引数値をそれぞれ「HTML」と「5.0」と指定して、
実装がこのモジュールに対応しているかどうかを特定することができます。
機能文字列「HTML」の他、実装が XHTML
に対応しているかどうか検査する場合には機能文字列「XHTML」
(版文字列「5.0」) を使用することができます。
利用者エージェントは hasFeature メソッドがこれらの値で照会された時に真を返すべきです。
しかし、利用者エージェントが真を返しても、その利用者エージェントが完全に適合であるとは限らず、
逆に利用者エージェントが偽を返しても、この仕様書の機能に対応しているかもしれないことを著者には警告します。
従って、一般に、このメソッドの使用はお勧めしません。
The values "HTML" and "XHTML" (both with version "5.0") should
also be supported in the context of the getFeature()
and isSupported() methods, as defined by DOM3 Core.値「HTML」と値「XHTML」
(いずれも版「5.0」) については、 getFeature()
メソッドや isSupported() メソッドの文脈でも、
DOM3 中核で定義されている通り、対応するべきです。
The interfaces defined in this specification are not
always supersets of the interfaces defined in DOM2 HTML; some
features that were formerly deprecated, poorly supported, rarely
used or considered unnecessary have been removed. Therefore it is
not guaranteed that an implementation that supports "HTML" "5.0" also supports "HTML" "2.0".この仕様書で定義する界面は、必ずしも DOM2 HTML で定義されている界面の超集合ではありません。
以前非推奨とされていたり、十分対応されていなかったり、ほとんど使われていなかったり、不要と判断されたりした機能は削除されています。
従って、「HTML」 「5.0」
に対応している実装が「HTML」 「2.0」
にも対応していることは保証されません。
2.8.6 Exceptions2.8.6 例外
The following DOMException codes are defined in DOM
Core. [DOMCORE]次の DOMException 符号は DOM
中核で定義されています。 [DOMCORE]
INDEX_SIZE_ERR
DOMSTRING_SIZE_ERR
HIERARCHY_REQUEST_ERR
WRONG_DOCUMENT_ERR
INVALID_CHARACTER_ERR
NO_DATA_ALLOWED_ERR
NO_MODIFICATION_ALLOWED_ERR
NOT_FOUND_ERR
NOT_SUPPORTED_ERR
INUSE_ATTRIBUTE_ERR
INVALID_STATE_ERR
SYNTAX_ERR
INVALID_MODIFICATION_ERR
NAMESPACE_ERR
INVALID_ACCESS_ERR
VALIDATION_ERR
TYPE_MISMATCH_ERR
SECURITY_ERR
NETWORK_ERR
ABORT_ERR
URL_MISMATCH_ERR
QUOTA_EXCEEDED_ERR
PARSE_ERR
SERIALISE_ERR
3 Semantics and structure of HTML documents3 HTML 文書の意味と構造
3.1 Introduction3.1 はじめに
This section is non-normative.この節は規定の一部ではありません。
An introduction to marking up a document.
3.2 Documents3.2 文書
Every XML and HTML document in an HTML UA is represented by a
Document object. [DOM3CORE]HTML 利用者エージェントにおけるすべての XML や HTML の文書は
Document オブジェクトにより表現されます。 [DOM3CORE]
The document's address is an absolute URL
that is set when the Document is created.文書の番地は、
Document が作成された時に設定される絶対 URL
です。
When a Document is created by a script using the
createDocument() API, the document's
address is the same as the document's address of
the script document context of that script.Document が
createDocument() API
を使ってスクリプトにより作成された時は、文書の番地はそのスクリプトのスクリプト文書文脈の文書の番地と同じです。
Document objects are assumed to be XML
documents unless they are flagged as being HTML
documents when they are created. Whether a document is an
HTML document or an XML document affects the behavior of
certain APIs, as well as a few CSS rendering rules. [CSS21]Document オブジェクトは、作成された時に
HTML 文書であると旗付けされていなければ、 XML 文書であると見なします。
文書が HTML 文書であるか XML 文書であるかは、
いくつかの API の動作や CSS のレンダリング規則の一部に影響します。 [CSS21]
A Document object created by the createDocument() API on the
DOMImplementation object is initially an XML document, but can be made into an
HTML document by calling document.open() on it.DOMImplementation 上の createDocument() API により作成された Document
オブジェクトははじめ XML
文書ですが、 document.open()
を呼び出すことにより HTML 文書にすることができます。
3.2.1 Documents in the DOM3.2.1 DOM 中の文書
All Document objects (in user agents implementing
this specification) must also implement the
HTMLDocument interface, available using
binding-specific methods. (This is the case whether or not the
document in question is an HTML
document or indeed whether it contains any HTML
elements at all.) Document objects must also
implement the document-level interface of any other namespaces found
in the document that the UA supports. For example, if an HTML
implementation also supports SVG, then the Document
object must implement HTMLDocument and
SVGDocument.(この仕様書を実装する利用書エージェントにおける) すべての
Document
オブジェクトは、 HTMLDocument 界面をも実装し、
束縛規定の方式により利用可能としなければなりません。
(これは当該文書が HTML 文書であるか否かや、
そもそも HTML
要素を含んでいるか否かによらずのことです。)
Document オブジェクトは、文書中に現れ、利用者エージェントが対応している、
他の名前空間の文書水準の界面をも実装しなければなりません。
例えば、 HTML 実装が SVG にも対応している場合、 Document
オブジェクトは HTMLDocument と
SVGDocument を実装しなければなりません。
Because the HTMLDocument interface is
now obtained using binding-specific casting methods instead of
simply being the primary interface of the document object, it is no
longer defined as inheriting from Document.HTMLDocument
界面は現在では単純に文書オブジェクトの主たる界面であるとするのではなく、
束縛規定の型変換方式を使って得るものとしているので、
最早 Document から継承するとは定義していません。
interface HTMLDocument {
// resource metadata management
[PutForwards=href] readonly attribute Location location;
readonly attribute DOMString URL;
attribute DOMString domain;
readonly attribute DOMString referrer;
attribute DOMString cookie;
readonly attribute DOMString lastModified;
readonly attribute DOMString compatMode;
attribute DOMString charset;
readonly attribute DOMString characterSet;
readonly attribute DOMString defaultCharset;
readonly attribute DOMString readyState;
// DOM tree accessors
attribute DOMString title;
attribute DOMString dir;
attribute HTMLElement body;
readonly attribute HTMLCollection images;
readonly attribute HTMLCollection embeds;
readonly attribute HTMLCollection plugins;
readonly attribute HTMLCollection links;
readonly attribute HTMLCollection forms;
readonly attribute HTMLCollection anchors;
readonly attribute HTMLCollection scripts;
NodeList getElementsByName(in DOMString elementName);
NodeList getElementsByClassName(in DOMString classNames);
// dynamic markup insertion
attribute DOMString innerHTML;
HTMLDocument open();
HTMLDocument open(in DOMString type);
HTMLDocument open(in DOMString type, in DOMString replace);
Window open(in DOMString url, in DOMString name, in DOMString features);
Window open(in DOMString url, in DOMString name, in DOMString features, in boolean replace);
void close();
void write([Variadic] in DOMString text);
void writeln([Variadic] in DOMString text);
// user interaction
Selection getSelection();
readonly attribute Element activeElement;
boolean hasFocus();
attribute boolean designMode;
boolean execCommand(in DOMString commandId);
boolean execCommand(in DOMString commandId, in boolean showUI);
boolean execCommand(in DOMString commandId, in boolean showUI, in DOMString value);
boolean queryCommandEnabled(in DOMString commandId);
boolean queryCommandIndeterm(in DOMString commandId);
boolean queryCommandState(in DOMString commandId);
boolean queryCommandSupported(in DOMString commandId);
DOMString queryCommandValue(in DOMString commandId);
readonly attribute HTMLCollection commands;
};
Since the HTMLDocument interface holds methods and
attributes related to a number of disparate features, the members of
this interface are described in various different sections.HTMLDocument
界面は色々な機能に関係するメソッドや属性を持っていますので、
この界面の構成員はそれぞれの節で説明します。
3.2.2 Security3.2.2 保安性
User agents must raise a SECURITY_ERR exception whenever
any of the members of an HTMLDocument object are
accessed by scripts whose effective script origin is
not the same as the
Document's effective script origin.
The URL
attribute must return the document's address.
The referrer attribute
must return either the address of the active document of the
source browsing context at the time the navigation was
started (that is, the page which navigated the browsing context
to the current document), or the empty string if there is no such
originating page, or if the UA has been configured not to report
referrers in this case, or if the navigation was initiated for a
hyperlink with a noreferrer keyword.
In the case of HTTP, the referrer DOM attribute will
match the Referer (sic) header that was sent
when fetching the current page.HTTP の場合、 referrer DOM 属性は現在の頁を取ってくる時に送られた Referer (ママ) 頭部と一致します。
Typically user agents are configured to not report
referrers in the case where the referrer uses an encrypted protocol
and the current page does not (e.g. when navigating from an https: page to an http:
page).通常、利用者エージェントは、参照子が暗号化プロトコルを使っており、
現在の頁がそうではない場合 (例えば https:
頁から http: 頁へと操縦した時)
には参照子を報告しないように設定されています。
The cookie
attribute represents the cookies of the resource.cookie
属性は、資源のクッキーを表します。
On getting, if the document is not associated
with a browsing context then the user agent must raise
an INVALID_STATE_ERR exception. Otherwise, if the
sandboxed origin browsing context flag is set on the
browsing context of the document, the user agent must
raise a SECURITY_ERR exception. Otherwise, if the
document's address does not use a server-based naming
authority, it must return the empty string. Otherwise, it must
return the same string as the value of the Cookie HTTP header it would include if fetching the resource indicated by the
document's address over HTTP, as per RFC 2109 section 4.3.4
or later specifications. [RFC2109] [RFC2965]
On setting, if the document is not associated with a
browsing context then the user agent must raise an
INVALID_STATE_ERR exception. Otherwise, if the
sandboxed origin browsing context flag is set on the
browsing context of the document, the user agent must
raise a SECURITY_ERR exception. Otherwise, if the
document's address does not use a server-based naming
authority, it must do nothing. Otherwise, the user agent must act as
it would when processing cookies if it had just attempted to
fetch the document's address over HTTP,
and had received a response with a Set-Cookie header
whose value was the specified value, as per RFC 2109 sections 4.3.1,
4.3.2, and 4.3.3 or later specifications. [RFC2109] [RFC2965]
Since the cookie attribute is accessible
across frames, the path restrictions on cookies are only a tool to
help manage which cookies are sent to which parts of the site, and
are not in any way a security feature.cookie 属性はフレームをまたいでアクセス可能ですので、
クッキーの経路制限はクッキーがサイト上のどの部分に送られるかを管理することを助けるための道具に過ぎず、
保安性のための機能では決してありません。
The lastModified
attribute, on getting, must return the date and time of the
Document's source file's last modification, in the
user's local timezone, in the following format:lastModified
属性は、取得時、 Document の原始ファイルの最終修正の日時を、
利用者の地方時において、次の書式で返さなければなりません。
The month component of the date. 日付の月の部品。
A U+002F SOLIDUS character ('/'). U+002F SOLIDUS 文字 ('/')。
The day component of the date. 日付の日の部品。
A U+002F SOLIDUS character ('/'). U+002F SOLIDUS 文字 ('/')。
The year component of the date. 日付の年の部品。
A U+0020 SPACE character. U+0020 SPACE 文字。
The hours component of the time. 時刻の時の部品。
A U+003A COLON character (':'). U+003A COLON 文字 (':')。
The minutes component of the time. 時刻の分の部品。
A U+003A COLON character (':'). U+003A COLON 文字 (':')。
The seconds component of the time. 時刻の秒の部品。
All the numeric components above, other than the year, must be
given as two digits in the range U+0030 DIGIT ZERO to U+0039 DIGIT
NINE representing the number in base ten, zero-padded if
necessary.前述の数値の部品のうち年以外のすべては、範囲 U+0030 DIGIT ZERO ～
U+0039 DIGIT NINE の2つの数字によって十進数を表す、
必要なら零埋めしたものとして与えなければなりません。
The Document's source file's last modification date
and time must be derived from relevant features of the networking
protocols used, e.g. from the value of the HTTP Last-Modified header of the document, or from
metadata in the file system for local files. If the last modification
date and time are not known, the attribute must return the string
01/01/1970 00:00:00.Document の原始ファイルの最終修正日時は、
使用されているネットワークのプロトコルの関係する機能、例えば文書の HTTP Last-Modified 頭部から、または局所ファイルのファイル・システムのメタデータから得たものでなければなりません。
最終修正日時がわからない場合は、この属性は文字列 01/01/1970 00:00:00
を返さなければなりません。
A Document is always set to one of three modes:
no quirks mode, the default; quirks mode, used
typically for legacy documents; and limited quirks mode,
also known as "almost standards" mode. The mode is only ever changed
from the default by the HTML parser, based on the
presence, absence, or value of the DOCTYPE string.Document は常に3つのモードのいずれかに設定されています。無奇癖モードは既定値です。奇癖モードは、
普通、遺物文書に使われます。制限奇癖モードは、「ほぼ標準」モードとも呼ばれます。
このモードは
HTML 構文解析器によってのみ、
DOCTYPE 文字列が存在するか存在しないかやその値に基づいて既定値から変更されます。
The compatMode DOM
attribute must return the literal string "CSS1Compat" unless the document has been set to
quirks mode by the HTML parser, in which
case it must instead return the literal string "BackCompat".compatMode DOM
属性は、生の文字列「CSS1Compat」を返さなければなりません。
ただし、文書が HTML 構文解析器により奇癖モードに設定されている場合には、
代わりに名前の文字列「BackCompat」を返さなければなりません。
As far as parsing goes, the quirks I know of are:
Comment parsing is different.
p can contain table
Safari and IE have special parsing rules for <% ... %>
(even in standards mode, though clearly this should be
quirks-only).
Documents have an associated character encoding. When a Document
object is created, the document's character encoding
must be initialized to UTF-16. Various algorithms during page
loading affect this value, as does the charset setter. [IANACHARSET]
The charset
DOM attribute must, on getting, return the preferred MIME name of
the document's character encoding. On setting, if the
new value is an IANA-registered alias for a character encoding, the
document's character encoding must be set to that
character encoding. (Otherwise, nothing happens.)charset
DOM 属性は、取得時、文書の文字符号化の優先
MIME 名を返さなければなりません。
設定時、新しい値が文字符号化の IANA に登録された別名である場合、
文書の文字符号化をその文字符号化に設定しなければなりません。
(そうでない場合、何も起こりません。)
The characterSet
DOM attribute must, on getting, return the preferred MIME name of
the document's character encoding.characterSet
DOM 属性は、取得時、文書の文字符号化の優先
MIME 名を返さなければなりません。
The defaultCharset
DOM attribute must, on getting, return the preferred MIME name of a
character encoding, possibly the user's default encoding, or an
encoding associated with the user's current geographical location,
or any arbitrary encoding name.defaultCharset
DOM 属性は、取得時、文字符号化の優先 MIME 名を返さなければなりません。
この文字符号化は利用者の既定の符号化でもいいですし、
利用者の現在の地理的位置に関連付けられた符号化でもいいですし、
その他任意の符号化名でもあり得ます。
Each document has a current document readiness. When a
Document object is created, it must have its
current document readiness set to the string
"loading". Various algorithms during page loading affect this
value. When the value is set, the user agent must fire a
simple event called readystatechanged at the
Document object.
The readyState DOM
attribute must, on getting, return the current document
readiness.
3.2.4 DOM tree accessors3.2.4 DOM 木アクセス器
The html element of a document is the
document's root element, if there is one and it's an
html element, or null otherwise.文書の文書 html 要素は、
その文書の根要素があり、それが html 要素である場合はその要素、それ以外の場合には
null です。
The head element of a document is the
first head element that is a child of the
html element, if there is one, or null
otherwise.文書の文書 head 要素は、
文書 html 要素の子供である最初の
head 要素がある場合はその要素、
そうでない場合は null です。
The title element of a document is the
first title element in the document (in tree order), if
there is one, or null otherwise.文書の文書 title 要素は文書の (木順で)
最初の title 要素がある場合はその要素、
そうでない場合は null です。
The title attribute must,
on getting, run the following algorithm:title 属性は、
取得時、次の算法を走らせなければなりません。
If the root element is an svg
element in the "http://www.w3.org/2000/svg"
namespace, and the user agent supports SVG, then the getter must
return the value that would have been returned by the DOM attribute
of the same name on the SVGDocument
interface.根要素が
「http://www.w3.org/2000/svg」名前空間の svg
要素であり、利用者エージェントが SVG に対応している場合、取得器は SVGDocument
界面の同名の DOM 属性が返す値を返さなければなりません。
Otherwise, it must return a concatenation of the data of all
the child text nodes of the
title element, in tree order, or the empty
string if the title element is
null.そうでない場合、文書 title 要素のすべての子供テキスト節点のデータを木順に連結したものを返すか、
文書 title 要素が null
の場合には殻文字列を返さなければなりません。
On setting, the following algorithm must be run:設定時、次の算法を走らせなければなりません。
If the root element is an svg
element in the "http://www.w3.org/2000/svg"
namespace, and the user agent supports SVG, then the setter must
defer to the setter for the DOM attribute of the same name on the
SVGDocument interface (if it is readonly, then this
will raise an exception). Stop the algorithm here.根要素が
「http://www.w3.org/2000/svg」名前空間の
svg 要素で利用者エージェントが SVG に対応している場合、
設定器は SVGDocument 界面の同名の DOM 属性の設定器に委ねなければなりません
(それが読み取り専用である場合、例外を発生させることとなります)。算法をここで停止します。
If the title element is null and
the head element is null, then the
attribute must do nothing. Stop the algorithm here.文書 title 要素が null
で文書 head 要素が null
の場合、属性は何もしてはなりません。算法をここで停止します。
If the title element is null, then a
new title element must be created and appended to
the head element.文書 title 要素が null
の場合、新しい title 要素を作成し、
文書 head
要素の最後に追加しなければなりません。
The children of the title element (if
any) must all be removed.文書 title
要素の子供を (あれば) すべて削除しなければなりません。
A single Text node whose data is the new value
being assigned must be appended to the title
element.データが指定された新しい値である1つの Text 節点を
文書 title
要素の最後に追加しなければなりません。
The title attribute on
the HTMLDocument interface should shadow the attribute
of the same name on the SVGDocument interface when the
user agent supports both HTML and SVG.利用者エージェントが HTML と SVG の両方に対応する時には、
HTMLDocument 界面の
title 属性が
SVGDocument 界面の同名の属性を隠すべきです。
The body element of a document is the first child of
the html element that is either a
body element or a frameset element. If
there is no such element, it is null. If the body element is null,
then when the specification requires that events be fired at "the
body element", they must instead be fired at the
Document object.文書の文書 body 要素は、
文書 html 要素の最初の子供であって、
body 要素か frameset
要素のいずれかであるものです。そのような要素がない場合、 null です。
文書 body 要素が null の場合、仕様書により事象が「文書 body 要素」において発火されることが要求される時、
その事象は代わりに
Document オブジェクトにおいて発火されなければなりません。
The body
attribute, on getting, must return the body element of
the document (either a body element, a
frameset element, or null). On setting, the following
algorithm must be run:body
属性は、取得時、文書の文書 body 要素
(body 要素か、
frameset 要素か、 null のいずれか) を返さなければなりません。
設定時、次の算法を走らせなければなりません。
If the new value is not a body or
frameset element, then raise a
HIERARCHY_REQUEST_ERR exception and abort these
steps.
Otherwise, if the new value is the same as the body
element, do nothing. Abort these steps.そうでない場合、新しい値が文書 body
要素と同じであれば、なにもしません。これらの段階を停止します。
Otherwise, if the body element is not null, then
replace that element with the new value in the DOM, as if the root
element's replaceChild() method had been
called with the new value and the
incumbent body element as its two arguments respectively,
then abort these steps.そうでない場合、文書 body
要素が null でなければ、根要素の replaceChild()
メソッドに新しい値と現行の文書
body 要素をそれぞれ2つの引数として呼び出した場合と同様にして、
DOM 中のその要素を新しい値により置き換え、
これらの段階を停止します。
Otherwise, the the body element is null. Append
the new value to the root element.そうでない場合、文書 body
要素は null です。新しい値を根要素の末尾に追加します。
The images
attribute must return an HTMLCollection rooted at the
Document node, whose filter matches only
img elements.images
属性は、 Document 節点を根とする、
濾過器が img 要素にのみ一致するような
HTMLCollection
を返さなければなりません。
The embeds
attribute must return an HTMLCollection rooted at the
Document node, whose filter matches only
embed elements.embeds
属性は、 Document 節点を根とする、
濾過器が embed 要素にのみ一致するような
HTMLCollection
を返さなければなりません。
The plugins
attribute must return the same object as that returned by the embeds attribute.plugins
属性は、 embeds
属性が返すのと同じオブジェクトを返さなければなりません。
The links
attribute must return an HTMLCollection rooted at the
Document node, whose filter matches only a
elements with href
attributes and area elements with href attributes.links
属性は、Document 節点を根とする、
濾過器が href
属性を持つ a 要素と
href
属性を持つ area 要素にのみ一致するような
HTMLCollection
を返さなければなりません。
The forms
attribute must return an HTMLCollection rooted at the
Document node, whose filter matches only
form elements.forms
属性は、Document 節点を根とする、
濾過器が form 要素にのみ一致するような
HTMLCollection
を返さなければなりません。
The anchors
attribute must return an HTMLCollection rooted at the
Document node, whose filter matches only a
elements with name attributes.anchors
属性は、Document 節点を根とする、
濾過器が name 属性を持つ
a
要素にのみ一致するような
HTMLCollection
を返さなければなりません。
The scripts
attribute must return an HTMLCollection rooted at the
Document node, whose filter matches only
script elements.scripts
属性は、Document 節点を根とする、
濾過器が script
要素にのみ一致するような
HTMLCollection
を返さなければなりません。
The getElementsByName(name) method takes a string name, and must return a live NodeList
containing all the a, applet,
button, form, iframe, img, input,
map, meta, object, select, and textarea elements in
that document that have a name attribute whose
value is equal to the name argument (in a
case-sensitive manner), in tree order.getElementsByName(name)
メソッドは、文字列 name を取り、
文書中で
name
と (大文字・小文字を区別して)
等しい値の name
属性を持つ
a, applet、
button, form、iframe、img、input、
map、meta、
object、 select、textarea
各要素をすべて木順で含む生きた NodeList
を返さなければなりません。
The getElementsByClassName(classNames) method takes a string that
contains an unordered set of unique space-separated
tokens representing classes. When called, the method must
return a live NodeList object containing all the
elements in the document, in tree order, that have all
the classes specified in that argument, having obtained the classes
by splitting a string on
spaces. If there are no tokens specified in the argument,
then the method must return an empty NodeList. If the
document is in quirks mode, then the comparisons for
the classes must be done in an ASCII case-insensitive
manner, otherwise, the comparisons must be done in a
case-sensitive manner.getElementsByClassName(classNames) メソッドは、
クラスを表す固有間隔分離字句の非順序付き集合を含んだ文字列を取ります。
このメソッドが呼び出された時には、
この引数を文字列を間隔で分割することによって得たクラスについて、
すべてのクラスを持つ、
文書中にあるすべての要素を木順に含んだ生きた
NodeList オブジェクトを返さなければなりません。
引数に字句が1つも指定されなかった場合、
メソッドは空の NodeList を返さなければなりません。
文書が奇癖モードの場合、
クラスの比較は ASCII 大文字・小文字不区別な形で行わなければなりません。そうでない場合、比較は大文字・小文字を区別する形で行わなければなりません。
The getElementsByClassName()
method on the HTMLElement interface must return a live
NodeList with the nodes that the
HTMLDocument getElementsByClassName()
method would return when passed the same argument(s), excluding any
elements that are not descendants of the HTMLElement
object on which the method was invoked.
HTML, SVG, and MathML elements define which classes they are in
by having an attribute in the per-element partition with the name
class containing a space-separated list of
classes to which the element belongs. Other specifications may also
allow elements in their namespaces to be labeled as being in
specific classes.
Given the following XHTML fragment:次の XHTML 素片を考えます。
<div id="example">
<p id="p1" class="aaa bbb"/>
<p id="p2" class="aaa ccc"/>
<p id="p3" class="bbb ccc"/>
</div>
A call to
document.getElementById('example').getElementsByClassName('aaa')
would return a NodeList with the two paragraphs
p1 and p2 in it.
A call to getElementsByClassName('ccc bbb')
would only return one node, however, namely p3. A call
to
document.getElementById('example').getElementsByClassName('bbb ccc ')
would return the same thing.
A call to getElementsByClassName('aaa,bbb') would
return no nodes; none of the elements above are in the "aaa,bbb"
class.
The dir
attribute on the HTMLDocument interface is defined
along with the dir content
attribute.
3.3 Elements3.3 要素
3.3.1 Semantics3.3.1 意味
Elements, attributes, and attribute values in HTML are defined
(by this specification) to have certain meanings (semantics). For
example, the ol element represents an ordered list, and
the lang attribute represents the
language of the content.
Authors must not use elements, attributes, and attribute values
for purposes other than their appropriate intended semantic
purpose.著者は、要素、属性、属性値をその意図する適切な意味的な目的以外の目的で使用してはなりません。
For example, the following document is non-conforming, despite
being syntactically correct:例えば、次の文書は、構文的には正しいのですが、不適合です。
<!DOCTYPE html>
<html lang="en-GB">
<head> <title> Demonstration </title> </head>
<body>
<table>
<tr> <td> My favourite animal is the cat. </td> </tr>
<tr>
<td>
—<a href="http://example.org/~ernest/"><cite>Ernest</cite></a>,
in an essay from 1992
</td>
</tr>
</table>
</body>
</html>
...because the data placed in the cells is clearly not tabular
data (and the cite element mis-used). A corrected
version of this document might be:
<!DOCTYPE html>
<html lang="en-GB">
<head> <title> Demonstration </title> </head>
<body>
<blockquote>
<p> My favourite animal is the cat. </p>
</blockquote>
<p>
—<a href="http://example.org/~ernest/">Ernest</a>,
in an essay from 1992
</p>
</body>
</html>
This next document fragment, intended to represent the heading
of a corporate site, is similarly non-conforming because the second
line is not intended to be a heading of a subsection, but merely a
subheading or subtitle (a subordinate heading for the same
section).次の文書素片は、会社のサイトの見出しを表そうとしたものですが、
これもやはり不適合で、2行目は節の見出しを意図したものではなく、単に副題 (同じ節の従属的な見出し)
になっています。
<body>
<h1>ABC Company</h1>
<h2>Leading the way in widget design since 1432</h2>
...
The header element should be used in these kinds of
situations:このような場合には header 要素を使うべきです。
<body>
<header>
<h1>ABC Company</h1>
<h2>Leading the way in widget design since 1432</h2>
</header>
...
Through scripting and using other mechanisms, the values of
attributes, text, and indeed the entire structure of the document
may change dynamically while a user agent is processing it. The
semantics of a document at an instant in time are those represented
by the state of the document at that instant in time, and the
semantics of a document can therefore change over time. User agents
must update their presentation of the document as this occurs.スクリプティングその他の機構によって属性の値、テキスト、はたまた文書の構造全体までもが利用者エージェントの処理中に動的に変化して構いません。
ある時点での文書の意味は、その時点での文書の状態によって表現されるものであり、
従って文書の意味は時を経て変化することがあります。
利用者エージェントは、その度に文書の表現を更新しなければなりません。
HTML has a progress element that
describes a progress bar. If its "value" attribute is dynamically
updated by a script, the UA would update the rendering to show the
progress changing.
3.3.2 Elements in the DOM3.3.2 DOM 中の要素
The nodes representing HTML elements in the DOM must
implement, and expose to scripts, the interfaces listed for them in
the relevant sections of this specification. This includes
HTML elements in XML documents, even when
those documents are in another context (e.g. inside an XSLT
transform).DOM 中で HTML 要素を表す節点は、
この仕様書の関係する節でその要素について列挙した界面を実装し、
スクリプトに対して晒さなければなりません。
これには XML 文書中の HTML 要素も含まれ、
その文書が他の文脈 (例えば XSLT 変形の内側) にある場合であっても適用されます。
Elements in the DOM represent things; that is, they have
intrinsic meaning, also known as semantics.DOM 中の要素は何かを表します。つまり、要素は内在的な意味 (meaning)、
あるいは意味 (semantics) と呼ばれるものを持っています。
For example, an ol element
represents an ordered list.例えば、ol 要素は順序付きリストを表します。
The basic interface, from which all the HTML
elements' interfaces inherit, and which must be used by
elements that have no additional requirements, is the
HTMLElement interface.基本的な、すべての HTML
要素の継承元となり、
追加の要件のない要素で使われなければならない界面が、
HTMLElement 界面です。
interface HTMLElement : Element {
// DOM tree accessors
NodeList getElementsByClassName(in DOMString classNames);
// dynamic markup insertion
attribute DOMString innerHTML;
attribute DOMString outerHTML;
void insertAdjacentHTML(in DOMString position, in DOMString text);
// metadata attributes
attribute DOMString id;
attribute DOMString title;
attribute DOMString lang;
attribute DOMString dir;
attribute DOMString className;
readonly attribute DOMTokenList classList;
readonly attribute DOMStringMap dataset;
// user interaction
attribute boolean hidden;
void click();
void scrollIntoView();
void scrollIntoView(in boolean top);
attribute long tabIndex;
void focus();
void blur();
attribute boolean draggable;
attribute DOMString contentEditable;
readonly attribute boolean isContentEditable;
attribute HTMLMenuElement contextMenu;
// styling
readonly attribute CSSStyleDeclaration style;
// event handler DOM attributes
attribute EventListener onabort;
attribute EventListener onbeforeunload;
attribute EventListener onblur;
attribute EventListener onchange;
attribute EventListener onclick;
attribute EventListener oncontextmenu;
attribute EventListener ondblclick;
attribute EventListener ondrag;
attribute EventListener ondragend;
attribute EventListener ondragenter;
attribute EventListener ondragleave;
attribute EventListener ondragover;
attribute EventListener ondragstart;
attribute EventListener ondrop;
attribute EventListener onerror;
attribute EventListener onfocus;
attribute EventListener onhashchange;
attribute EventListener onkeydown;
attribute EventListener onkeypress;
attribute EventListener onkeyup;
attribute EventListener onload;
attribute EventListener onmessage;
attribute EventListener onmousedown;
attribute EventListener onmousemove;
attribute EventListener onmouseout;
attribute EventListener onmouseover;
attribute EventListener onmouseup;
attribute EventListener onmousewheel;
attribute EventListener onresize;
attribute EventListener onscroll;
attribute EventListener onselect;
attribute EventListener onstorage;
attribute EventListener onsubmit;
attribute EventListener onunload;
};
The HTMLElement interface holds methods and
attributes related to a number of disparate features, and the
members of this interface are therefore described in various
different sections of this specification.HTMLElement 界面は様々な機能に関係したメソッドや属性を持っているので、
この界面の成員についてはこの仕様書の色々な節で説明します。
3.3.3 Global attributes3.3.3 大域属性
The following attributes are common to and may be specified on
all HTML elements (even those not defined in this
specification):次の属性はすべての HTML 要素 (この仕様書で定義されていないものも含みます。) に共通であり、すべての HTML 要素 に指定して構いません。
- Global attributes:大域属性:
classcontenteditablecontextmenudirdraggableidhiddenlangstyletabindextitle
In addition, the following event handler content
attributes may be specified on any HTML
element:加えて、次の事象取扱器内容属性も、
任意の HTML
要素に指定して構いません。
- Event handler content attributes:事象取扱器内容属性:
onabortonbeforeunloadonbluronchangeonclickoncontextmenuondblclickondragondragendondragenterondragleaveondragoverondragstartondroponerroronfocusonhashchangeonkeydownonkeypressonkeyuponloadonmessageonmousedownonmousemoveonmouseoutonmouseoveronmouseuponmousewheelonresizeonscrollonselectonstorageonsubmitonunload
Also, custom data
attributes (e.g. data-foldername or
data-msgid) can be specified on any HTML
element, to store custom data specific to the page.また、頁固有のカスタム・データを蓄積するため、
カスタム・データ属性 (例えば data-foldername や
data-msgid)
を任意の HTML
要素に指定できます。
In HTML documents, elements in the HTML
namespace may have an xmlns attribute
specified, if, and only if, it has the exact value
"http://www.w3.org/1999/xhtml". This does not apply to
XML documents.HTML 文書では、 HTML
名前空間中の要素は、xmlns 属性を、その正確な値が「http://www.w3.org/1999/xhtml」
である場合に、その場合に限って、これを持って構いません。
これは XML 文書には適用しません。
In HTML, the xmlns attribute
has absolutely no effect. It is basically a talisman. It is allowed
merely to make migration to and from XHTML mildly easier. When
parsed by an HTML parser, the attribute ends up in no
namespace, not the "http://www.w3.org/2000/xmlns/"
namespace like namespace declaration attributes in XML do.HTML では、 xmlns 属性はまったく効果を持ちません。
基本的に護符に過ぎません。これは単に XHTML から、あるいは XHTML への移行をいささか簡単にするためだけに認められています。
HTML 構文解析器が構文解析を行う時には、
この属性は名前空間なしとなり、 XML での名前空間宣言属性のように名前空間
「http://www.w3.org/2000/xmlns/」とはなりません。
In XML, an xmlns attribute is
part of the namespace declaration mechanism, and an element cannot
actually have an xmlns attribute in no
namespace specified.XML では、 xmlns 属性は名前空間宣言機構の一部であり、
要素は実際には名前空間が指定されない xmlns
属性を持つことができません。
3.3.3.1 The id attribute3.3.3.1 id 属性
The id attribute represents its
element's unique identifier. The value must be unique in the subtree
within which the element finds itself and must contain at least one
character. The value must not contain any space characters.id 属性は、
その要素の固有識別子を表します。値はその要素が現れる部分木中で固有でなければならず、
最低1文字含まなければなりません。
値は間隔文字を含んではなりません。
If the value is not the empty string, user agents must associate
the element with the given value (exactly, including any space
characters) for the purposes of ID matching within the subtree the
element finds itself (e.g. for selectors in CSS or for the
getElementById() method in the DOM).利用者エージェントは、値が空文字列でない場合、
その要素が現れる部分木中で ID 一致を行うために
(例えば CSS の選択子や DOM の getElementById()
メソッドのために)、
その要素に指定された値を (間隔文字も含めてそのまま)
関連付けなければなりません。
Identifiers are opaque strings. Particular meanings should not be
derived from the value of the id
attribute.識別子は不透明な文字列です。特定の意味を id 属性の値から見出すべきではありません。
This specification doesn't preclude an element having multiple
IDs, if other mechanisms (e.g. DOM Core methods) can set an
element's ID in a way that doesn't conflict with the id attribute.この仕様書は、他の仕組み (例えば DOM 中核のメソッド) によって
id 属性と矛盾しない形で要素の ID
を設定することができる場合に、要素が複数の ID を持つことを禁じていません。
The id DOM attribute must
reflect the id content
attribute.id DOM 属性は id 内容属性を反映しなければなりません。
3.3.3.2 The title attribute3.3.3.2 title 属性
The title attribute represents
advisory information for the element, such as would be appropriate
for a tooltip. On a link, this could be the title or a description
of the target resource; on an image, it could be the image credit or
a description of the image; on a paragraph, it could be a footnote
or commentary on the text; on a citation, it could be further
information about the source; and so forth. The value is text.title 属性は、
要素に関する助言情報、例えばツールチップとして適切なものなどを表します。
例えば、リンクにおいては、対象資源の題名や説明とすることができます。
画像では、画像のクレジットや説明とすることができます。
段落では、出典に関する追加情報とすることができます。
値は文章です。
If this attribute is omitted from an element, then it implies
that the title attribute of the
nearest ancestor HTML element
with a title attribute set is also
relevant to this element. Setting the attribute overrides this,
explicitly stating that the advisory information of any ancestors is
not relevant to this element. Setting the attribute to the empty
string indicates that the element has no advisory information.ある要素でこの属性が省略されている場合、最も近い title 属性が設定された祖先
HTML 要素の
title 属性がその要素にも関係することを暗示しています。
属性を設定することでこれが上書きされ、祖先の助言情報がこの要素に関係しないと明示することとなります。
この属性を空文字列に設定すると、その要素が助言情報を持たないことが示されます。
If the title attribute's value
contains U+000A LINE FEED (LF) characters, the content is split into
multiple lines. Each U+000A LINE FEED (LF) character represents a
line break.title
属性の値が U+000A LINE FEED (LF) 文字を含んでいる場合、
内容は複数行に分割されます。 U+000A LINE FEED (LF)
文字それぞれが改行を表します。
Some elements, such as link, abbr, and
input, define additional semantics for the title attribute beyond the semantics
described above.link、abbr、
input
などいくつかの要素は、前述の意味の他、更に追加の意味を
title
属性に定義しています。
The title DOM attribute
must reflect the title
content attribute.title DOM
属性は title 内容属性を反映しなければなりません。
3.3.3.3 The lang and xml:lang
attributes3.3.3.3 lang 属性と xml:lang 属性
The lang attribute specifies the
primary language for the element's contents and for any
of the element's attributes that contain text. Its value must be a
valid RFC 3066 language code, or the empty string. [RFC3066]lang 属性は、
その要素の内容と文章を含むその要素の属性についての主たる言語を指定します。
値は妥当な RFC 3066 言語符号または空文字列でなければなりません。[RFC3066]
The xml:lang attribute (that
is, the lang attribute with the xml prefix in the http://www.w3.org/XML/1998/namespace namespace) is
defined in XML. [XML]xml:lang 属性 (すなわち、 xml 接頭辞で http://www.w3.org/XML/1998/namespace 名前空間にある
lang 属性) は XML で定義されています。
[XML]
If these attributes are omitted from an element, then it implies
that the language of this element is the same as the language of the
parent element. Setting the attribute to the empty string indicates
that the primary language is unknown.これらの属性が要素から省略されている場合、その要素の言語は親要素の言語と同じであることを暗示しています。
これらの属性を空文字列に設定することは、
主たる言語が不明であることを示します。
The lang attribute may be used on
any HTML element.lang
属性は任意の HTML 要素で使って構いません。
The xml:lang attribute may be
used on HTML elements in XML documents, as
well as elements in other namespaces if the relevant specifications
allow it (in particular, MathML and SVG allow xml:lang attributes to be specified on
their elements). If both the lang
attribute and the xml:lang
attribute are specified on the same element, they must have exactly
the same value when compared in an ASCII
case-insensitive manner.xml:lang
属性は XML 文書中の任意の HTML 要素で使って構いませんし、それ以外の名前空間でも関係する仕様書が認めていれば使って構いません
(特に MathML と SVG は xml:lang
属性を両者の要素に指定することを認めています)。
lang
属性と xml:lang
属性の両方が同じ要素に指定される場合は、両者は ASCII
大文字・小文字不区別な形で比較した時に正確に同じ値を持たなければなりません。
Authors must not use the xml:lang attribute (that is, the lang attribute with the xml
prefix in the http://www.w3.org/XML/1998/namespace namespace) in
HTML documents. To ease migration to and from XHTML,
authors may specify an attribute in no namespace with no prefix and
with the localname xml:lang on HTML
elements in HTML documents, but such attributes
must only be specified if a lang
attribute is also specified, and both attributes must have the same
value when compared in an ASCII case-insensitive
manner.著者は xml:lang 属性 (すなわち、 xml 接頭辞で http://www.w3.org/XML/1998/namespace 名前空間にある
lang 属性)
を HTML 文書中で使ってはなりません。
XHTML への移行や XHTML からの移行を簡単にするため、
著者は名前空間に属さず、接頭辞を持たない局所名 xml:lang
の属性を HTML 文書中の HTML
要素に指定しても構いませんが、そのような属性は
lang
属性も指定される場合に限って指定されなければならず、
両属性は ASCII 大文字・小文字不区別な形で比較した時に同じな値でなければなりません。
To determine the language of a node, user agents must look at the
nearest ancestor element (including the element itself if the node
is an element) that has an xml:lang attribute set or is an HTML element and has a lang attribute set. That attribute
specifies the language of the node.利用者エージェントは、ある節点の言語を決定する場合、
xml:lang 属性が設定されているか、 HTML 要素であって
lang 属性が設定されている直近の祖先要素
(当該節点が要素である場合、その要素自体を含みます。)
を見なければなりません。その属性が、当該節点の言語を指定します。
If both the xml:lang attribute
and the lang attribute are set on an
element, user agents must use the xml:lang attribute, and the lang attribute must be ignored for the purposes of determining the
element's language.利用者エージェントは、 xml:lang 属性と lang
属性が共にある要素に設定されている場合、 xml:lang 属性を使用しなければならず、
lang 属性は要素の言語の決定においては無視しなければなりません。
If no explicit language is given for the root
element, but there is a document-wide default
language set, then that is the language of the node.根要素に言語が明示的に指定されておらず、
文書規模既定言語が設定されている場合には、
それがその節点の言語です。
If there is no document-wide default language, then
language information from a higher-level protocol (such as HTTP), if
any, must be used as the final fallback language. In the absence of
any language information, the default value is unknown (the empty
string).文書規模既定言語が設定されていない場合、
上位層プロトコル (HTTP 等) からの言語情報があれば、それを最終的なフォールバックの言語として使わなければなりません。
言語情報がない場合には、既定値は未知 (空文字列) です。
If the resulting value is not a recognised language code, then it
must be treated as an unknown language (as if the value was the
empty string).得られた値が認識できる言語符号でない場合には、未知の言語として
(値が空文字列であった場合のように) 扱わなければなりません。
User agents may use the element's language to determine proper
processing or rendering (e.g. in the selection of appropriate
fonts or pronunciations, or for dictionary selection). 利用者エージェントは、適切な処理やレンダリングの決定 (例えば適切なフォントや発音の選択や辞書の選択)
のために要素の言語を使って構いません。
The lang DOM attribute
must reflect the lang
content attribute.lang DOM 属性は lang 内容属性を反映しなければなりません。
3.3.3.4 The xml:base
attribute (XML only)3.3.3.4 xml:base 属性 (XML のみ)
The xml:base attribute is
defined in XML Base. [XMLBASE]xml:base
属性は XML 基底で定義されています。 [XMLBASE]
The xml:base attribute may be
used on elements of XML documents. Authors must not
use the xml:base attribute in
HTML documents.xml:base
属性は XML 文書の要素で使って構いません。
著者は xml:base 属性を HTML
文書で使用してはなりません。
3.3.3.5 The dir attribute3.3.3.5 dir 属性
The dir attribute specifies the
element's text directionality. The attribute is an enumerated
attribute with the keyword ltr mapping
to the state ltr, and the keyword rtl
mapping to the state rtl. The attribute has no
defaults.dir 属性は要素のテキストの方向性を指定します。
この属性は列挙属性で、
キーワード ltr は状態 ltr
に写像され、キーワード rtl
は状態 rtl
に写像されます。この属性は既定値を持ちません。
The processing of this attribute is primarily performed by the
presentation layer. For example, CSS 2.1 defines a mapping from this
attribute to the CSS 'direction' and 'unicode-bidi' properties, and
defines rendering in terms of those properties.この属性の処理は主として表現層において行われます。
例えば、 CSS 2.1 はこの属性から CSS の 'direction' 特性や 'unicode-bidi'
特性への写像を定義しており、両特性の元でレンダリングを定義しています。
The directionality of an element, which is used in
particular by the canvas element's text rendering API,
is either 'ltr' or 'rtl'. If the user agent supports CSS and the
'direction' property on this element has a computed value of either
'ltr' or 'rtl', then that is the directionality of the
element. Otherwise, if the element is being rendered, then the
directionality of the element is the directionality used by
the presentation layer, potentially determined from the value of the
dir attribute on the
element. Otherwise, if the element's dir attribute has the state ltr,
the element's directionality is 'ltr' (left-to-right); if the
attribute has the state rtl, the element's directionality
is 'rtl' (right-to-left); and oherwise, the element's directionality
is the same as its parent element, or 'ltr' if there is no parent
element.
The dir DOM attribute on
an element must reflect the dir content attribute of that element,
limited to only known values.
The dir DOM
attribute on HTMLDocument objects must
reflect the dir content
attribute of the html element, if any,
limited to only known values. If there is no such
element, then the attribute must return the empty string and do
nothing on setting.
3.3.3.6 The class attribute3.3.3.6 class 属性
Every HTML element may have a
class attribute specified.すべての HTML 要素には class
属性を指定して構いません。
The attribute, if specified, must have a value that is an
unordered set of unique space-separated tokens
representing the various classes that the element belongs to.
The classes that an HTML
element has assigned to it consists of all the classes
returned when the value of the class
attribute is split on
spaces.
Assigning classes to an element affects class
matching in selectors in CSS, the getElementsByClassName()
method in the DOM, and other such features.
Authors may use any value in the class attribute, but are encouraged to use
the values that describe the nature of the content, rather than
values that describe the desired presentation of the
content.
The className and
classList DOM
attributes must both reflect the class content attribute.
3.3.3.7 The style attribute3.3.3.7 style 属性
All elements may have the style
content attribute set. If specified, the attribute must contain only
a list of zero or more semicolon-separated (;) CSS declarations. [CSS21]
The attribute, if specified, must be parsed and treated as the
body (the part inside the curly brackets) of a declaration block in
a rule whose selector matches just the element on which the
attribute is set. For the purposes of the CSS cascade, the attribute
must be considered to be a 'style' attribute at the author
level.
Documents that use style
attributes on any of their elements must still be comprehensible and
usable if those attributes were removed.
In particular, using the style attribute to hide and show content,
or to convey meaning that is otherwise not included in the document,
is non-conforming.
The style DOM attribute
must return a CSSStyleDeclaration whose value
represents the declarations specified in the attribute, if
present. Mutating the CSSStyleDeclaration object must
create a style attribute on the
element (if there isn't one already) and then change its value to be
a value representing the serialized form of the
CSSStyleDeclaration object. [CSSOM]
In the following example, the words that refer to colors are
marked up using the span element and the style attribute to make those words show
up in the relevant colors in visual media.
<p>My sweat suit is <span style="color: green; background:
transparent">green</span> and my eyes are <span style="color: blue;
background: transparent">blue</span>.</p>
3.3.3.8 Embedding custom non-visible data3.3.3.8 不可視カスタム・データの埋め込み
A custom data attribute is an attribute whose name
starts with the string "data-", has at least one
character after the hyphen, is XML-compatible, has no
namespace, and contains no characters in the range U+0041 .. U+005A
(LATIN CAPITAL LETTER A LATIN CAPITAL LETTER Z).
All attributes in HTML documents get
lowercased automatically, so the restriction on uppercase letters
doesn't affect such documents.
Custom data attributes
are intended to store custom data private to the page or
application, for which there are no more appropriate attributes or
elements.カスタム・データ属性は、
より適切な要素や属性がないような頁や応用の私的なカスタム・データを蓄積することを想定しています。
Every HTML element may have
any number of custom data
attributes specified, with any value.すべての HTML 要素には、
任意の値のカスタム・データ属性を任意の個数指定して構いません。
The dataset DOM
attribute provides convenient accessors for all the data-* attributes on an element. On
getting, the dataset DOM attribute
must return a DOMStringMap object, associated with the
following three algorithms, which expose these attributes on their
element:
- The algorithm for getting values from names名前から値を取得する算法
-
Let name be the concatenation of the
string data- and the name passed to the
algorithm, converted to lowercase.
If the element does not have an attribute with the name name, then the name has no corresponding value,
abort.要素が名前 name の属性を有しない場合は、
その名前は対応する値を持たず、停止します。
Otherwise, return the value of the attribute with the name
name.そうでない場合、名前 name の属性の値を返します。
- The algorithm for setting names to certain values名前をある値に設定する算法
-
Let name be the concatenation of the
string data- and the name passed to the
algorithm, converted to lowercase.
Let value be the value passed to the
algorithm.value を、算法に渡された値とします。
Set the value of the attribute with the name name, to the value value,
replacing any previous value if the attribute already existed. If
setAttribute() would have raised an
exception when setting an attribute with the name name, then this must raise the same
exception.名前 name の属性の値を値 value
に設定します。ここで、属性が既に存在する場合、元の値は置き換えられます。 setAttribute() が名前 name
の属性を設定しようとした時に例外を発生させるような場合には、
これも同じ例外を発生させなければなりません。
- The algorithm for deleting names名前を削除する算法
-
Let name be the concatenation of the
string data- and the name passed to the
algorithm, converted to lowercase.
Remove the attribute with the name name,
if such an attribute exists. Do nothing otherwise.名前 name の属性が存在すれば、これを削除します。
存在しない場合は、なにもしません。
If a Web page wanted an element to represent a space ship,
e.g. as part of a game, it would have to use the class attribute along with data-* attributes:
<div class="spaceship" data-id="92432"
data-weapons="laser 2" data-shields="50%"
data-x="30" data-y="10" data-z="90">
<button class="fire"
onclick="spaceships[this.parentNode.dataset.id].fire()">
Fire
</button>
</div>
Authors should carefully design such extensions so that when the
attributes are ignored and any associated CSS dropped, the page is
still usable.著者は、このような拡張を設計する際、この属性が無視され、関連付けられた CSS
が除去されたとしても、なおその頁が利用可能であるよう、注意するべきです。
User agents must not derive any implementation behavior from
these attributes or values. Specifications intended for user agents
must not define these attributes to have any meaningful values.利用者エージェントは、これらの属性や値によって実装の動作を決めてはなりません。
利用者エージェントを想定した仕様書は、
これらの属性が意味のある値を持つように定義してはなりません。
3.4 Content models3.4 内容モデル
All the elements in this specification have a defined content
model, which describes what nodes are allowed inside the elements,
and thus what the structure of an HTML document or fragment must
look like.
As noted in the conformance and terminology
sections, for the purposes of determining if an element matches its
content model or not, CDATASection nodes in the DOM are treated as
equivalent to Text nodes, and entity reference nodes are treated as if
they were expanded in place.
The space characters are
always allowed between elements. User agents represent these
characters between elements in the source markup as text nodes in
the DOM. Empty text nodes and text nodes consisting of just sequences of
those characters are considered inter-element
whitespace.
Inter-element whitespace, comment nodes, and
processing instruction nodes must be ignored when establishing
whether an element matches its content model or not, and must be
ignored when following algorithms that define document and element
semantics.
An element A is said to be preceded or
followed by a second element B if A and B have the same parent node
and there are no other element nodes or text nodes (other than
inter-element whitespace) between them.
Authors must not use elements in the HTML namespace
anywhere except where they are explicitly allowed, as defined for
each element, or as explicitly required by other specifications. For
XML compound documents, these contexts could be inside elements from
other namespaces, if those elements are defined as providing the
relevant contexts.
The SVG specification defines the SVG foreignObject
element as allowing foreign namespaces to be included, thus
allowing compound documents to be created by inserting subdocument
content under that element. This specification defines the
XHTML html element as being allowed where subdocument
fragments are allowed in a compound document. Together, these two
definitions mean that placing an XHTML html element as
a child of an SVG foreignObject element is
conforming. [SVG]
The Atom specification defines the Atom content element, when its type attribute has the value xhtml, as requiring that it contains a single HTML
div element. Thus, a div element is
allowed in that context, even though this is not explicitly
normatively stated by this specification. [ATOM]
In addition, elements in the HTML namespace may be
orphan nodes (i.e. without a parent node).
For example, creating a td element and storing it
in a global variable in a script is conforming, even though
td elements are otherwise only supposed to be used
inside tr elements.
var data = {
name: "Banana",
cell: document.createElement('td'),
};
3.4.1 Kinds of content3.4.1 内容の種類
Each element in HTML falls into zero or more categories that
group elements with similar characteristics together. The following
broad categories are used in this specification:
In addition, certain elements are categorised as form-associated elements and
further subcategorised so so to define their role in various
form-related processing models.
Some elements have unique requirements and do not fit into any
particular category.
3.4.1.1 Metadata content
Metadata content is content that sets up the
presentation or behavior of the rest of the content, or that sets
up the relationship of the document with other documents, or that
conveys other "out of band" information.
Elements from other namespaces whose semantics are primarily
metadata-related (e.g. RDF) are also metadata
content.
3.4.1.2 Flow content
Most elements that are used in the body of documents and
applications are categorized as flow content.
As a general rule, elements whose content model allows any
flow content should have either at least one
descendant text node that is not inter-element
whitespace, or at least one descendant element node that is
embedded content. For the purposes of this requirement,
del elements and their descendants must not be
counted as contributing to the ancestors of the del
element.
This requirement is not a hard requirement, however, as there are
many cases where an element can be empty legitimately, for example
when it is used as a placeholder which will later be filled in by a
script, or when the element is part of a template and would on most
pages be filled in but on some pages is not relevant.
3.4.1.3 Sectioning content
Sectioning content is content that defines the scope
of headers, footers, and contact
information.
Each sectioning content element potentially has a
heading. See the section on headings and sections for
further details.
3.4.1.4 Heading content
Heading content defines the header of a section
(whether explicitly marked up using sectioning content
elements, or implied by the heading content itself).
3.4.1.5 Phrasing content
Phrasing content is the text of the document, as well
as elements that mark up that text at the intra-paragraph
level. Runs of phrasing content form paragraphs.
All phrasing content is also flow
content. Any content model that expects flow
content also expects phrasing content.
As a general rule, elements whose content model allows any
phrasing content should have either at least one
descendant text node that is not inter-element
whitespace, or at least one descendant element node that is
embedded content. For the purposes of this requirement,
nodes that are descendants of del elements must not be
counted as contributing to the ancestors of the del
element.
Most elements that are categorized as phrasing
content can only contain elements that are themselves categorized as
phrasing content, not any flow content.
Text nodes that are not inter-element whitespace are
phrasing content.
3.4.1.6 Embedded content3.4.1.6 埋め込まれた内容
Embedded content is content that imports another
resource into the document, or content from another vocabulary that
is inserted into the document.
All embedded content is also phrasing
content (and flow content). Any content model
that expects phrasing content (or flow
content) also expects embedded content.
Elements that are from namespaces other than the HTML
namespace and that convey content but not metadata, are
embedded content for the purposes of the content models
defined in this specification. (For example, MathML, or SVG.)
Some embedded content elements can have fallback
content: content that is to be used when the external resource
cannot be used (e.g. because it is of an unsupported format). The
element definitions state what the fallback is, if any.
3.4.1.7 Interactive content
Interactive content is content that is specifically
intended for user interaction.
Certain elements in HTML have an activation
behavior, which means the user agent should allow the user to
manually trigger them in some way, for instance using keyboard or
voice input, or through mouse clicks. When the user triggers an
element with a defined activation behavior in a manner
other than clicking it, the default action of the interaction
event must be to run synthetic click activation
steps on the element.
When a user agent is to run synthetic click activation
steps on an element, the user agent must run pre-click
activation steps on the element, then fire a click event at the element. The
default action of this click event
must be to run post-click activation steps on the
element. If the event is canceled, the user agent must run
canceled activation steps on the element instead.
Given an element target, the nearest
activatable element is the element returned by the following
algorithm:
If target has a defined activation
behavior, then return target and abort
these steps.
If target has a parent element, then set
target to that parent element and return to the
first step.
Otherwise, there is no nearest activatable
element.
When a pointing device is clicked, the user agent must run these
steps:
Let e be the nearest
activatable element of the element designated by the user,
if any.
If there is an element e, run
pre-click activation steps on it.
-
Dispatching the required click
event.
Another specification presumably requires the
firing of the click event?
If there is an element e, then the default
action of the click event must be
to run post-click activation steps on element e.
If there is an element e but the event is
canceled, the user agent must run canceled activation
steps on element e.
The above doesn't happen for arbitrary synthetic
events dispatched by author script. However, the click() method can be used to make it
happen programmatically.
When a user agent is to run post-click activation
steps on an element, the user agent must fire a simple
event called DOMActivate at that element. The
default action of this event must be to run final activation
steps on that element. If the event is canceled, the user
agent must run canceled activation steps on the element
instead.
When a user agent is to run pre-click activation steps
on an element, it must run the pre-click activation steps
defined for that element, if any.
When a user agent is to run canceled activation steps
on an element, it must run the canceled activation steps
defined for that element, if any.
When a user agent is to run final activation steps on
an element, it must run the activation behavior defined
for that element. Activation behaviors can refer to the click and DOMActivate events that were fired
by the steps above leading up to this point.
3.4.2 Transparent content models
Some elements are described as transparent; they have
"transparent" as their content model. Some elements are described as
semi-transparent; this means that part of their content
model is "transparent" but that is not the only part of the content
model that must be satisfied.
When a content model includes a part that is "transparent", those
parts must not contain content that would not be conformant if all
transparent and semi-transparent elements in the tree were replaced,
in their parent element, by the children in the "transparent" part
of their content model, retaining order.
When a transparent or semi-transparent element has no parent,
then the part of its content model that is "transparent" must
instead be treated as accepting any flow content.
3.5 Paragraphs
A paragraph is typically a block of text with one or more
sentences that discuss a particular topic, as in typography, but can
also be used for more general thematic grouping. For instance, an
address is also a paragraph, as is a part of a form, a byline, or a
stanza in a poem.
Paragraphs in flow content are defined relative to
what the document looks like without the a,
ins and del elements complicating matters,
since those elements, with their hybrid content models, can straddle
paragraph boundaries.
Let view be a view of the DOM that replaces
all a, ins and del elements
in the document with their contents. Then, in view, for each run of phrasing content
uninterrupted by other types of content, in an element that accepts
content other than phrasing content, let first be the first node of the run, and let last be the last node of the run. For each run, a
paragraph exists in the original DOM from immediately before first to immediately after last. (Paragraphs can thus span across
a, ins and del elements.)
A paragraph is also formed explicitly by
p elements.
The p element can be used to wrap
individual paragraphs when there would otherwise not be any content
other than phrasing content to separate the paragraphs from each
other.
In the following example, there are two paragraphs in a
section. There is also a header, which contains phrasing content
that is not a paragraph. Note how the comments and
intra-element whitespace do not form paragraphs.
<section>
<h1>Example of paragraphs</h1>
This is the <em>first</em> paragraph in this example.
<p>This is the second.</p>
<!-- This is not a paragraph. -->
</section>
The following example takes that markup and puts
ins and del elements around some of the
markup to show that the text was changed (though in this case, the
changes don't really make much sense, admittedly). Notice how this
example has exactly the same paragraphs as the previous one,
despite the ins and del elements.
<section>
<ins><h1>Example of paragraphs</h1>
This is the <em>first</em> paragraph in</ins> this example<del>.
<p>This is the second.</p></del>
<!-- This is not a paragraph. -->
</section>
In the following example, the link spans half of the first
paragraph, all of the header separating the two paragraphs, and
half of the second paragraph.
<aside>
Welcome!
<a href="about.html">
This is home of...
<h1>The Falcons!</h1>
The Lockheed Martin multirole jet fighter aircraft!
</a>
This page discusses the F-16 Fighting Falcon's innermost secrets.
</aside>
Here is another way of marking this up, this time showing the
paragraphs explicitly, and splitting the one link element into
three:
<aside>
<p>Welcome! <a href="about.html">This is home of...</a></p>
<h1><a href="about.html">The Falcons!</a></h1>
<p><a href="about.html">The Lockheed Martin multirole jet
fighter aircraft!</a> This page discusses the F-16 Fighting
Falcon's innermost secrets.</p>
</aside>
Generally, having elements straddle paragraph
boundaries is best avoided. Maintaining such markup can be
difficult.
3.6 APIs in HTML documents
For HTML documents, and for HTML
elements in HTML documents, certain APIs defined
in DOM3 Core become case-insensitive or case-changing, as sometimes
defined in DOM3 Core, and as summarized or required below. [DOM3CORE].
This does not apply to XML documents or to elements
that are not in the HTML namespace despite being in
HTML documents.
Element.tagName and Node.nodeName-
These attributes must return element names converted to
uppercase, regardless of the case with which they were
created.
Document.createElement()-
The canonical form of HTML markup is all-lowercase; thus, this
method will lowercase
the argument before creating the requisite element. Also, the
element created must be in the HTML namespace.
This doesn't apply to Document.createElementNS(). Thus, it is possible,
by passing this last method a tag name in the wrong case, to
create an element that claims to have the tag name of an element
defined in this specification, but doesn't support its interfaces,
because it really has another tag name not accessible from the DOM
APIs.
Element.setAttributeNode()-
When an Attr node is set on an HTML element, it must have its name
converted to lowercase before the element is
affected.
This doesn't apply to Document.setAttributeNodeNS().
Element.setAttribute()-
When an attribute is set on an HTML
element, the name argument must be converted to
lowercas before the element is affected.
This doesn't apply to Document.setAttributeNS().
Document.getElementsByTagName() and Element.getElementsByTagName()-
These methods (but not their namespaced counterparts) must
compare the given argument in an ASCII
case-insensitive manner when looking at HTML elements, and in a
case-sensitive manner otherwise.
Thus, in an HTML
document with nodes in multiple namespaces, these methods
will be both case-sensitive and case-insensitive at the same
time.
Document.renameNode()-
If the new namespace is the HTML namespace, then
the new qualified name must be converted to lowercase
before the rename takes place.
3.7 Dynamic markup insertion
APIs for dynamically inserting markup into the document interact
with the parser, and thus their behavior varies depending on whether
they are used with HTML documents (and the HTML
parser) or XHTML in XML documents (and the
XML parser). The following table cross-references the
various versions of these APIs.
Regardless of the parsing mode, the document.writeln(...)
method must call the document.write() method with the
same argument(s), plus an extra argument consisting of a string
containing a single line feed character (U+000A).
The innerHTML
attribute applies to both Element nodes as well as
Document nodes. The outerHTML and insertAdjacentHTML() members,
on the other hand, only apply to Element nodes.
When inserted using the document.write() method,
script elements execute (typically synchronously), but
when inserted using innerHTML and outerHTML attributes, they do not
execute at all.
The open()
method comes in several variants with different numbers of
arguments.
When called with two or fewer arguments, the method must act as
follows:
Let type be the value of the first
argument, if there is one, or "text/html"
otherwise.
Let replace be true if there is a second
argument and it is an ASCII case-insensitive match for
the value "replace", and false otherwise.
-
If the document has an active parser that isn't a script-created parser, and the
insertion point associated with that parser's
input stream is not undefined (that is, it
does point to somewhere in the input stream), then the
method does nothing. Abort these steps and return the
Document object on which the method was invoked.
This basically causes document.open() to be ignored
when it's called in an inline script found during the parsing of
data sent over the network, while still letting it have an effect
when called asynchronously or on a document that is itself being
spoon-fed using these APIs.
onbeforeunload, onunload, reset timers, empty event queue, kill any pending transactions, XMLHttpRequests, etc
If the document has an active parser, then stop that parser, and throw away any pending content
in the input stream. what about if it
doesn't, because it's either like a text/plain, or Atom, or PDF, or
XHTML, or image document, or something?
Remove all child nodes of the document.
Change the document's character encoding to
UTF-16.
Change the document's address to the address of the script
document context of the script that invoked the document.open() method.
Create a new HTML parser and associate it with
the document. This is a script-created parser (meaning
that it can be closed by the document.open() and document.close() methods, and
that the tokeniser will wait for an explicit call to document.close() before emitting
an end-of-file token).
Mark the document as being an HTML
document (it might already be so-marked).
-
If the type string contains a U+003B
SEMICOLON (;) character, remove the first such character and all
characters from it up to the end of the string.
Strip all leading and trailing space characters from type.
If type is not now an ASCII
case-insensitive match for the string
"text/html", then act as if the tokeniser had emitted
a start tag token with the tag name "pre", then set the HTML
parser's tokenization stage's content
model flag to PLAINTEXT.
All other values are treated as
text/html.
-
If replace is false, then:
Remove all the entries in the browsing context's
session history after the current entry
in its Document's History object
Remove any earlier entries that share the same
Document
Add a new entry just before the last entry that is associated
with the text that was parsed by the previous parser associated
with the Document object, as well as the state of
the document at the start of these steps. (This allows the user
to step backwards in the session history to see the page before
it was blown away by the document.open() call.)
Finally, set the insertion point to point at
just before the end of the input stream (which at this
point will be empty).
Return the Document on which the method was
invoked.
When called with three or more arguments, the open() method on the
HTMLDocument object must call the open() method on the Window
interface of the object returned by the defaultView attribute of the
DocumentView interface of the HTMLDocument
object, with the same arguments as the original call to the open() method, and return whatever
that method returned. If the defaultView attribute of the
DocumentView interface of the HTMLDocument
object is null, then the method must raise an
INVALID_ACCESS_ERR exception.
The close()
method must do nothing if there is no script-created
parser associated with the document. If there is such a
parser, then, when the method is called, the user agent must insert
an explicit "EOF" character at the end of the parser's
input stream.
3.7.2 Dynamic markup insertion in HTML
In HTML, the document.write(...)
method must act as follows:
-
If the insertion point is undefined, the open() method must be called
(with no arguments) on the document
object. The insertion point will point at just before
the end of the (empty) input stream.
-
The string consisting of the concatenation of all the arguments
to the method must be inserted into the input
stream just before the insertion
point.
-
If there is a pending external script, then the
method must now return without further processing of the
input stream.
-
Otherwise, the tokeniser must process the characters that were
inserted, one at a time, processing resulting tokens as they are
emitted, and stopping when the tokeniser reaches the insertion
point or when the processing of the tokeniser is aborted by the
tree construction stage (this can happen if a script
end tag token is emitted by the tokeniser).
If the document.write() method was
called from script executing inline (i.e. executing because the
parser parsed a set of script tags), then this is a
reentrant invocation of the
parser.
-
Finally, the method must return.
On getting, the innerHTML DOM
attribute must return the result of running the HTML fragment
serialization algorithm on the node.
On setting, if the node is a document, the innerHTML DOM attribute must run
the following algorithm:
-
If the document has an active parser, then stop that parser, and throw away any pending content
in the input stream. what about if it
doesn't, because it's either like a text/plain, or Atom, or PDF,
or XHTML, or image document, or something?
-
Remove the children nodes of the Document whose
innerHTML attribute is
being set.
-
Create a new HTML parser, in its initial state,
and associate it with the Document node.
-
Place into the input stream for the HTML
parser just created the string being assigned into the
innerHTML attribute.
-
Start the parser and let it run until it has consumed all the
characters just inserted into the input stream. (The
Document node will have been populated with elements
and a load event will have fired
on its body element.)
Otherwise, if the node is an element, then setting the innerHTML DOM attribute must cause
the following algorithm to run instead:
-
Invoke the HTML fragment parsing algorithm, with
the element whose innerHTML attribute is being set
as the context element, and the string being
assigned into the innerHTML attribute as the input. Let new children be the
result of this algorithm.
-
Remove the children of the element whose innerHTML attribute is being
set.
-
Let target document be the ownerDocument of the Element node
whose innerHTML attribute
is being set.
-
Set the ownerDocument of all the nodes in
new children to the target
document.
-
Append all the new children nodes to the
node whose innerHTML
attribute is being set, preserving their order.
On getting, the outerHTML DOM
attribute must return the result of running the HTML fragment
serialization algorithm on a fictional node whose only child
is the node on which the attribute was invoked.
On setting, the outerHTML
DOM attribute must cause the following algorithm to run:
-
Let target be the element whose outerHTML attribute is being
set.
-
If target has no parent node, then abort
these steps. There would be no way to obtain a reference to the
nodes created even if the remaining steps were run.
-
If target's parent node is a
Document object, throw a
NO_MODIFICATION_ALLOWED_ERR exception and abort these
steps.
-
Let parent be target's
parent node, unless that is a DocumentFragment node,
in which case let parent be an arbitrary
body element.
-
Invoke the HTML fragment parsing algorithm, with
parent as the context
element and the string being assigned into the outerHTML attribute as the input. Let new children be the
result of this algorithm.
-
Let target document be the ownerDocument of target.
-
Set the ownerDocument of all the nodes in
new children to the target
document.
-
Remove target from its parent node and
insert in its place all the new children
nodes, preserving their order.
The insertAdjacentHTML(position, text)
method, when invoked, must run the following steps:
-
Let position and text
be the method's first and second arguments, respectively.
-
Let target be the element on which the
method was invoked.
-
Use the first matching item from this list:
- If position is an ASCII
case-insensitive match for the string "beforebegin"
- If position is an ASCII
case-insensitive match for the string "afterend"
-
If target has no parent node, then abort
these steps.
If target's parent node is a
Document object, then throw a
NO_MODIFICATION_ALLOWED_ERR exception and abort
these steps.
Otherwise, let context be the parent node
of target.
- If position is an ASCII
case-insensitive match for the string "afterbegin"
- If position is an ASCII
case-insensitive match for the string "beforeend"
-
Let context be the same as target.
- Otherwiseそれ以外の場合
-
Throw a SYNTAX_ERR exception.
-
Invoke the HTML fragment parsing algorithm, with
the context element being that selected by the
previous step, and input being the method's
text argument. Let new
children be the result of this algorithm.
-
Let target document be the ownerDocument of target.
-
Set the ownerDocument of all the nodes in
new children to the target
document.
-
Use the first matching item from this list:
- If position is an ASCII
case-insensitive match for the string "beforebegin"
-
Insert all the new children nodes
immediately before target, preserving their
order.
- If position is an ASCII
case-insensitive match for the string "afterbegin"
-
Insert all the new children nodes before
the first child of target, if there is one,
preserving their order. If there is no such child, append them
all to target, preserving their order.
- If position is an ASCII
case-insensitive match for the string "beforeend"
-
Append all the new children nodes to target, preserving their order.
- If position is an ASCII
case-insensitive match for the string "afterend"
-
Insert all the new children nodes
immediately after target, preserving their
order.
3.7.3 Dynamic markup insertion in XML
In an XML context, the innerHTML DOM attribute
on HTMLElements must return a string in the form of an
internal general
parsed entity, and on HTMLDocuments must return a
string in the form of a document
entity. The string returned must be XML namespace-well-formed
and must be an isomorphic serialization of all of that node's child
nodes, in document order. User agents may adjust prefixes and
namespace declarations in the serialization (and indeed might be
forced to do so in some cases to obtain namespace-well-formed
XML). For the innerHTML
attribute on HTMLElement objects, if any of the
elements in the serialization are in no namespace, the default
namespace in scope for those elements must be explicitly declared as
the empty string.
(This doesn't apply to the innerHTML attribute on
HTMLDocument objects.) [XML] [XMLNS]
If any of the following cases are found in the DOM being
serialized, the user agent must raise an
INVALID_STATE_ERR exception:
A Document node with no child element nodes.
A DocumentType node that has an external subset
public identifier or an external subset system identifier that
contains both a U+0022 QUOTATION MARK ('"') and a U+0027 APOSTROPHE
("'").
A node with a prefix or local name containing a U+003A COLON
(":").
An Attr node, Text node,
CDATASection node, Comment node, or
ProcessingInstruction node whose data contains
characters that are not matched by the XML Char production. [XML]
A CDATASection node whose data contains the string
"]]>".
A Comment node whose data contains two adjacent
U+002D HYPHEN-MINUS (-) characters or ends with such a
character.Comment node whose data contains two adjacent U+002D HYPHEN-MINUS (-) characters 文字か ends with such a 文字。
A ProcessingInstruction node whose target name is
an ASCII case-insensitive match for the string "xml".
A ProcessingInstruction node whose target name
contains a U+003A COLON (":").
A ProcessingInstruction node whose data contains
the string "?>".
These are the only ways to make a DOM
unserializable. The DOM enforces all the other XML constraints; for
example, trying to set an attribute with a name that contains an
equals sign (=) will raised an INVALID_CHARACTER_ERR
exception.
On setting, in an XML context, the innerHTML DOM attribute on
HTMLElements and HTMLDocuments must run
the following algorithm:
-
The user agent must create a new XML parser.
-
If the innerHTML
attribute is being set on an element, the user agent must
feed the parser just created the string corresponding
to the start tag of that element, declaring all the namespace
prefixes that are in scope on that element in the DOM, as well as
declaring the default namespace (if any) that is in scope on that
element in the DOM.
A namespace prefix is in scope if the DOM Core lookupNamespaceURI() method on the element would
return a non-null value for that prefix.
The default namespace is the namespace for which the DOM Core
isDefaultNamespace() method on the element
would return true.
-
The user agent must feed the parser just created
the string being assigned into the innerHTML attribute.
-
If the innerHTML
attribute is being set on an element, the user agent must
feed the parser the string corresponding to the end
tag of that element.
-
If the parser found an XML well-formedness or XML namespace
well-formedness error, the attribute's setter must raise a
SYNTAX_ERR exception and abort these steps.
-
The user agent must remove the children nodes of the node whose
innerHTML attribute is
being set.
-
If the attribute is being set on a Document node,
let new children be the children of the
document, preserving their order. Otherwise, the attribute is
being set on an Element node; let new
children be the children of the document's root element,
preserving their order.
-
If the attribute is being set on a Document node,
let target document be that
Document node. Otherwise, the attribute is being set
on an Element node; let target
document be the ownerDocument of that
Element.
-
Set the ownerDocument of all the nodes in
new children to the target
document.
-
Append all the new children nodes to the
node whose innerHTML
attribute is being set, preserving their order.
In an XML context, the document.write()
and insertAdjacentHTML()
methods, and the outerHTML attribute on
both getting and setting, must raise an
INVALID_ACCESS_ERR exception.
4 The elements of HTML4 HTML の要素
4.1 The root element4.1 根要素
4.1.1 The html element4.1.1 html 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As the root element of a document.文書の根要素として。
- Wherever a subdocument fragment is allowed in a compound document.複合文書中で部分文書素片が認められる時に。
- Content model:内容モデル:
- A
head element followed by a body element.head 要素と、その後に body 要素。
- Element-specific attributes:要素固有属性:
manifest- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The html element represents the root of an HTML
document.html 要素は HTML 文書の根を表します。
The manifest
attribute gives the address of the document's application
cache manifest, if there is
one. If the attribute is present, the attribute's value must be a
valid URL.
The manifest attribute
only has an
effect during the early stages of document load. Changing the
attribute dynamically thus has no effect (and thus, no DOM API is
provided for this attribute).manifest
属性は文書の読み込みの早い段階でのみ影響を持ちます。
この属性を動的に変更しても、影響はありません (ので、 DOM API
はこの属性には提供しません)。
Later base elements don't affect the
resolving of relative URLs in
manifest attributes, as the
attributes are processed before those elements are seen.後の base 要素は、それが見られるよりも前に manifest
属性が処理されるので、相対 URL
の解決には影響しません。
4.2.1 The head element4.2.1 head 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As the first element in an
html element.html 要素の最初の要素として。
- Content model:内容モデル:
- One or more elements of metadata content, of which exactly one is a
title element.1つ以上のメタデータ内容要素、
ただし、そのうちの丁度1つは title 要素。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The head element collects the document's
metadata.head 要素は文書のメタデータを集めています。
4.2.2 The title element4.2.2 title 要素
- Categories分類
- Metadata content.メタデータ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- In a
head element containing no other title elements.他に title
要素を含まない head 要素の中。
- Content model:内容モデル:
- Text.テキスト。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The title element represents the document's title or
name. Authors should use titles that identify their documents even
when they are used out of context, for example in a user's history
or bookmarks, or in search results. The document's title is often
different from its first header, since the first header does not
have to stand alone when taken out of context.title 要素は文書の題や名前を表します。
著者は、文書が文脈外、例えば利用者の履歴や栞、あるいは検索結果で使われた場合であっても、
その文書を識別できるような題名を使うべきです。
文書の題は最初の見出しと異なることもよくあります。
最初の見出しは文脈外で単独で使えるものでなくてもよいからです。
There must be no more than one title element per
document.文書中に複数の title
要素があってはなりません。
The title element must not contain any
elements.title 要素は要素を含んではなりません。
Here are some examples of appropriate titles, contrasted with
the top-level headers that might be used on those same pages.次に示すのは、適切な題名の例です。
同じ頁の最上位で使い得る見出しと比べてください。
<title>Introduction to The Mating Rituals of Bees</title>
...
<h1>Introduction</h1>
<p>This companion guide to the highly successful
<cite>Introduction to Medieval Bee-Keeping</cite> book is...
The next page might be a part of the same site. Note how the
title describes the subject matter unambiguously, while the first
header assumes the reader knowns what the context is and therefore
won't wonder if the dances are Salsa or Waltz:次の頁は同じサイトの中にありそうなものです。
題名が話題を曖昧なく説明している一方で、
最初の見出しは読者が文脈をわかっていることを前提にしていて、
踊りがサルサなのかワルツなのか困らないものと思っていることに注意してください。
<title>Dances used during bee mating rituals</title>
...
<h1>The Dances</h1>
The string to use as the document's title is given by the document.title DOM attribute. User
agents should use the document's title when referring to the
document in their user interface.文書の題名として使う文字列は document.title DOM 属性により与えられます。
利用者エージェントはその利用者界面において文書を指す時に文書の題名を使うべきです。
4.2.3 The base element4.2.3 base 要素
- Categories分類
- Metadata content.メタデータ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- In a
head element containing no other base elements.他に base 要素を含まない
head 要素の中で。
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
hreftarget- DOM interface:DOM 界面:
-
interface HTMLBaseElement : HTMLElement {
attribute DOMString href;
attribute DOMString target;
};
The base element allows authors to specify the
document base URL for the purposes of resolving relative URLs, and the name
of the default browsing context for the purposes of
following hyperlinks.base 要素を使うと、
著者は相対 URL を解決する際の文書基底 URL
やハイパーリンクをたどる際の既定の閲覧文脈の名前を指定することができます。
There must be no more than one base element per
document.文書中に複数の base
要素があってはなりません。
A base element must have either an href attribute, a target attribute, or both.base 要素は href 属性と
target
属性のいずれか、または両方を持たなければなりません。
The href content
attribute, if specified, must contain a valid URL.
A base element, if it has an href attribute, must come before any
other elements in the tree that have attributes defined as taking
URLs, except the html element
(its manifest attribute
isn't affected by base elements).base 要素は、href
属性を持つ場合、 URL
を取ると定義されている属性を持つ他の要素のうち、 html 要素以外より木上で前に来なければなりません
(html 要素の manifest
属性は base
要素に影響されません)。
If there are multiple base elements
with href attributes, all but the
first are ignored.href
属性のある base
要素が複数存在する場合、最初の要素以外はすべて無視されます。
The target
attribute, if specified, must contain a valid browsing context
name or keyword. User agents use this name when
following hyperlinks.
A base element, if it has a target attribute, must come before
any elements in the tree that represent hyperlinks.base 要素は、 target
属性を持つ場合、ハイパーリンクを表す要素よりも木上で前に来なければなりません。
If there are multiple base elements
with target attributes, all but
the first are ignored.target
属性を持つ base 要素が複数存在する場合、
最初の要素以外はすべて無視されます。
The href and target DOM attributes
must reflect the respective content attributes of the
same name.
4.2.4 The link element4.2.4 link 要素
- Categories分類
- Metadata content.メタデータ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where metadata content is expected.メタデータ内容が期待される場所。
- In a
noscript element that is a child of a head element.head 要素の子供である
noscript 要素の中。
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
hrefrelmediahreflangtypesizes- Also, the
title attribute has special semantics on this element.また、 title 属性はこの要素では特別な意味を持ちます。
- DOM interface:DOM 界面:
-
interface HTMLLinkElement : HTMLElement {
attribute boolean disabled;
attribute DOMString href;
attribute DOMString rel;
readonly attribute DOMTokenList relList;
attribute DOMString media;
attribute DOMString hreflang;
attribute DOMString type;
attribute DOMString sizes;
};
The LinkStyle interface must also be implemented
by this element, the styling processing model defines
how. [CSSOM]LinkStyle 界面もこの要素に実装されなければなりません。
その方法はスタイル付け処理モデルで定義します。
[CSSOM]
The link element allows authors to link their
document to other resources.link 要素を使うと、
文書から他の資源へリンクすることができます。
The destination of the link is given by the href attribute, which must
be present and must contain a valid URL. If the href attribute is absent, then the
element does not define a link.
The type of link indicated (the relationship) is given by the
value of the rel
attribute, which must be present, and must have a value that is a
set of space-separated tokens. The allowed values and their meanings are defined
in a later section. If the rel
attribute is absent, or if the value used is not allowed according
to the definitions in this specification, then the element does not
define a link.示されたリンクの型 (関係) は rel
属性の値により与えられます。この属性は存在しなければならず、 間隔区切字句集合であるような値を持たなければなりません。 認められている値とその意味は後の節で定義します。 rel 属性が存在しないか、
この仕様書の定義に照らして認められていない値である場合は、
その要素はリンクを定義しません。
Two categories of links can be created using the
link element. Links
to external resources are links to resources that are to be
used to augment the current document, and hyperlink links are links to
other documents. The link types
section defines whether a particular link type is an external
resource or a hyperlink. One element can create multiple links (of
which some might be external resource links and some might be
hyperlinks); exactly which and how many links are created depends on
the keywords given in the rel
attribute. User agents must process the links on a per-link basis,
not a per-element basis.link 要素を使って作成できるリンクは2種類あります。
外部資源へのリンクは、現在の文書を補うために使われる資源へのリンクで、 ハイパーリンク・リンクは 他の文書へのリンクです。 リンク型の節で、あるリンク型が外部資源なのかハイパーリンクなのかを定義します。
ある要素は複数のリンクを作成できます (そのうちいくつかは外部資源リンクで、
いくつかはハイパーリンクであっても構いません)。どのリンクが何個作成されるかは rel 属性に与えられたキーワードに依存します。
利用者エージェントはリンクを、要素毎ではなく、リンク毎に処理しなければなりません。
The exact behavior for links to external resources depends on the
exact relationship, as defined for the relevant link type. Some of
the attributes control whether or not the external resource is to be
applied (as defined below). For external resources that are
represented in the DOM (for example, style sheets), the DOM
representation must be made available even if the resource is not
applied. (However, user agents may opt to only fetch
such resources when they are needed, instead of pro-actively fetching all the external resources that are
not applied.)外部資源へのリンクの正確な動作は、関係がどうであるかに依存し、
各リンク型についてそれぞれ定義します。いくつかの属性は外部資源が適用されるかどうかを制御します (後で定義します)。
DOM で表される外部資源 (例えばスタイル・シート) については、
資源が適用されない場合であっても、 DOM 表現が利用可能とされなければなりません。
(しかし、利用者エージェントは適用されない外部資源をすべて予め取ってくる必要はなく、
必要になった時にだけそのような資源を取ってくることとしても構いません。)
The semantics of the protocol used (e.g. HTTP) must be followed
when fetching external resources. (For example, redirects must be
followed and 404 responses must cause the external resource to not
be applied.)外部資源を取ってくる際には、使用されるプロトコル (例えば HTTP) の意味に従わなければなりません。
(例えば、リダイレクトに従わなければなりませんし、
404 応答があると外部資源は適用されなくしなければなりません。)
Interactive user agents should provide users with a means to
follow the hyperlinks
created using the link element, somewhere within their
user interface. The exact interface is not defined by this
specification, but it should include the following information
(obtained from the element's attributes, again as defined below), in
some form or another (possibly simplified), for each hyperlink
created with each link element in the document:
The relationship between this document and the resource (given
by the rel attribute)
The title of the resource (given by the title attribute).
The address of the resource (given by the href attribute).
The language of the resource (given by the hreflang attribute).
The optimum media for the resource (given by the media attribute).
User agents may also include other information, such as the type
of the resource (as given by the type attribute).
Hyperlinks created with the link
element and its rel attribute
apply to the whole page. This contrasts with the rel attribute of a
and area elements, which indicates the type of a link
whose context is given by the link's location within the
document.
The media
attribute says which media the resource applies to. The value must
be a valid media query. [MQ]
If the link is a hyperlink
then the media attribute is
purely advisory, and describes for which media the document in
question was designed.
However, if the link is an external resource link,
then the media attribute is
prescriptive. The user agent must apply the external resource to
views while their state match the
listed media and the other relevant conditions apply, and must not
apply them otherwise.
The default, if the media attribute is omitted, is
all, meaning that by default links apply to all
media.
The hreflang
attribute on the link element has the same semantics as
the hreflang
attribute on hyperlink elements.
The type attribute
gives the MIME type of the linked resource. It is purely advisory.
The value must be a valid MIME type, optionally with parameters. [RFC2046]
For external resource
links, the type attribute
is used as a hint to user agents so that they can avoid fetching
resources they do not support. If the attribute is present, then the
user agent must assume that the resource is of the given type. If
the attribute is omitted, but the external resource link type has a
default type defined, then the user agent must assume that the
resource is of that type. If the UA does not support the given MIME
type for the given link relationship, then the UA should not fetch
the resource; if the UA does support the given MIME type for the
given link relationship, then the UA should fetch the
resource. If the attribute is omitted, and the external resource
link type does not have a default type defined, but the user agent
would fetch the resource if the type was known and supported, then
the user agent should fetch the resource under the
assumption that it will be supported.
User agents must not consider the type attribute authoritative —
upon fetching the resource, user agents must not use the type attribute to determine its actual
type. Only the actual type (as defined in the next paragraph) is
used to determine whether to apply the resource, not the
aforementioned assumed type.
If the resource is expected to be
an image, user agents may apply the image sniffing rules, with the official type being the type determined from the
resource's Content-Type metadata,
and use the resulting sniffed type of the resource as if it was the
actual type. Otherwise, if the resource is not expected to be an
image, or if the user agent opts not to apply those rules, then the
user agent must use the resource's Content-Type metadata to determine the
type of the resource. If there is no type metadata, but the external
resource link type has a default type defined, then the user agent
must assume that the resource is of that type.
Once the user agent has established the type of the resource, the
user agent must apply the resource if it is of a supported type and
the other relevant conditions apply, and must ignore the resource
otherwise.
If a document contains style sheet links labeled as follows:
<link rel="stylesheet" href="A" type="text/plain">
<link rel="stylesheet" href="B" type="text/css">
<link rel="stylesheet" href="C">
...then a compliant UA that supported only CSS style sheets
would fetch the B and C files, and skip the A file (since
text/plain is not the MIME type for CSS style
sheets).
For files B and C, it would then check the actual types returned
by the server. For those that are sent as text/css, it
would apply the styles, but for those labeled as
text/plain, or any other type, it would not.
If one the two files was returned without a
Content-Type metadata, or with a syntactically
incorrect type like Content-Type: "null", then the default type
for stylesheet links would kick
in. Since that default type is text/css, the
style sheet would nonetheless be applied.
The title
attribute gives the title of the link. With one exception, it is
purely advisory. The value is text. The exception is for style sheet
links, where the title
attribute defines alternative style sheet sets.
The title
attribute on link elements differs from the global
title attribute of most other
elements in that a link without a title does not inherit the title
of the parent element: it merely has no title.
The sizes attribute is used
with the icon link type. The attribute
must not be specified on link elements that do not have
a rel attribute that specifies
the icon keyword.
Some versions of HTTP defined a Link:
header, to be processed like a series of link elements.
If supported, for the purposes of ordering links defined by HTTP
headers must be assumed to come before any links in the document, in
the order that they were given in the HTTP entity header. (URIs in
these headers are to be processed and resolved according to the
rules given in HTTP; the rules of this specification don't
apply.) [RFC2616] [RFC2068]
The DOM attributes href, rel, media, hreflang, and type, and sizes each must
reflect the respective content attributes of the same
name.
The DOM attribute relList must
reflect the rel
content attribute.
The DOM attribute disabled only applies
to style sheet links. When the link element defines a
style sheet link, then the disabled attribute behaves as
defined for the alternative
style sheets DOM. For all other link elements it
always return false and does nothing on setting.
- Categories分類
- Metadata content.メタデータ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- If the
charset attribute is present, or if the element is in the Encoding declaration state: as the first element in a head element.
- If the
http-equiv attribute is present, and the element is not in the Encoding declaration state: in a head element.
- If the
http-equiv attribute is present, and the element is not in the Encoding declaration state: in a noscript element that is a child of a head element.
- If the
name attribute is present: where metadata content is expected.
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
namehttp-equivcontentcharset (HTML only)- DOM interface:DOM 界面:
-
interface HTMLMetaElement : HTMLElement {
attribute DOMString content;
attribute DOMString name;
attribute DOMString httpEquiv;
};
The meta element represents various kinds of
metadata that cannot be expressed using the title,
base, link, style, and
script elements.
The meta element can represent document-level
metadata with the name
attribute, pragma directives with the http-equiv attribute, and the
file's character encoding declaration when an HTML
document is serialized to string form (e.g. for transmission over
the network or for disk storage) with the charset attribute.
Exactly one of the name,
http-equiv, and charset attributes must be
specified.
If either name or http-equiv is specified, then
the content attribute must
also be specified. Otherwise, it must be omitted.
The charset
attribute specifies the character encoding used by the
document. This is called a character encoding
declaration.
The charset attribute may
be specified in HTML documents only, it
must not be used in XML documents. If the
charset attribute is
specified, the element must be the first element in the
head element of the file.
The content
attribute gives the value of the document metadata or pragma
directive when the element is used for those purposes. The allowed
values depend on the exact context, as described in subsequent
sections of this specification.
If a meta element has a name attribute, it sets
document metadata. Document metadata is expressed in terms of
name/value pairs, the name
attribute on the meta element giving the name, and the
content attribute on the same
element giving the value. The name specifies what aspect of metadata
is being set; valid names and the meaning of their values are
described in the following sections. If a meta element
has no content attribute,
then the value part of the metadata name/value pair is the empty
string.
If a meta element has the http-equiv attribute specified,
it must be either in a head element or in a
noscript element that itself is in a head
element. If a meta element does not have the http-equiv attribute specified,
it must be in a head element.
The DOM attributes name and content must
reflect the respective content attributes of the same
name. The DOM attribute httpEquiv must
reflect the content attribute http-equiv.
This specification defines a few names for the name attribute of the
meta element.
- application-name
The value must be a short free-form string that giving the
name of the Web application that the page represents. If the page
is not a Web application, the application-name metadata name
must not be used. User agents may use the application name in UI in
preference to the page's title, since the title might
include status messages and the like relevant to the status of the
page at a particular moment in time instead of just being the name
of the application.
- description
The value must be a free-form string that describes the
page. The value must be appropriate for use in a directory of
pages, e.g. in a search engine.
- generator
The value must be a free-form string that identifies the
software used to generate the document. This value must not be used
on hand-authored pages.
Extensions to the predefined
set of metadata names may be registered in the WHATWG Wiki
MetaExtensions page.
Anyone is free to edit the WHATWG Wiki MetaExtensions page at any
time to add a type. These new names must be specified with the
following information:
- Keywordキーワード
The actual name being defined. The name should not be
confusingly similar to any other defined name (e.g. differing only
in case).
- Brief description簡単な説明
A short description of what the metadata name's meaning is,
including the format the value is required to be in.
- Link to more details詳細へのリンク
- A link to a more detailed description of the metadata name's
semantics and requirements. It could be another page on the Wiki,
or a link to an external page.
- Synonyms同義語
A list of other names that have exactly the same processing
requirements. Authors should not use the names defined to be
synonyms, they are only intended to allow user agents to support
legacy content.
- Status状態
-
One of the following:次のいずれかです。
- Proposal提案
- The name has not received wide peer review and
approval. Someone has proposed it and is using it.
- Accepted承認済み
- The name has received wide peer review and approval. It has a
specification that unambiguously defines how to handle pages that
use the name, including when they use it in incorrect ways.
- Unendorsed
- The metadata name has received wide peer review and it has
been found wanting. Existing pages are using this keyword, but
new pages should avoid it. The "brief description" and "link to
more details" entries will give details of what authors should
use instead, if anything.
If a metadata name is added with the "proposal" status and
found to be redundant with existing values, it should be removed
and listed as a synonym for the existing value.
Conformance checkers must use the information given on the WHATWG
Wiki MetaExtensions page to establish if a value not explicitly
defined in this specification is allowed or not. When an author uses
a new type not defined by either this specification or the Wiki
page, conformance checkers should offer to add the value to the
Wiki, with the details described above, with the "proposal"
status.
This specification does not define how new values will get
approved. It is expected that the Wiki will have a community that
addresses this.
Metadata names whose values are to be URLs must not be proposed or accepted. Links must
be represented using the link element, not the
meta element.
4.2.5.3 Pragma directives
When the http-equiv attribute
is specified on a meta element, the element is a pragma
directive.
The http-equiv attribute
is an enumerated attribute. The following table lists
the keywords defined for this attribute. The states given in the
first cell of the rows with keywords give the states to which
those keywords map.
When a meta element is inserted into the document, if its
http-equiv attribute is
present and represents one of the above states, then the user agent
must run the algorithm appropriate for that state, as described in
the following list:
- Content language
-
This pragma sets the document-wide default
language. Until the pragma is successfully processed, there
is no document-wide default language.
If another meta element in the Content Language
state has already been successfully processed (i.e. when
it was inserted the user agent processed it and reached the last
step of this list of steps), then abort these steps.
If the meta element has no content attribute, or if that
attribute's value is the empty string, then abort these
steps.
Let input be the value of the
element's content
attribute.
Let position point at the first
character of input.
Skip whitespace. 空白を読み飛ばします。
Collect a
sequence of characters that are neither space characters nor a U+002C COMMA character
(",").
Let the document-wide default language be the
string that resulted from the previous step.
For meta elements in the Content Language
state, the content
attribute must have a value consisting of a valid RFC 3066
language code. [RFC3066]
This pragma is not exactly equivalent to the HTTP
Content-Language header, for instance it only
supports one language. [RFC2616]
- Encoding declaration state
-
The Encoding
declaration state's user agent requirements are all handled
by the parsing section of the specification. The state is just an
alternative form of setting the charset attribute: it is a
character encoding declaration.
For meta elements in the Encoding declaration
state, the content
attribute must have a value that is an ASCII
case-insensitive match for a string that consists of: the
literal string "text/html;", optionally
followed by any number of space
characters, followed by the literal string "charset=", followed by the character encoding name
of the character encoding declaration.
If the document contains a meta element in the
Encoding
declaration state then that element must be the first
element in the document's head element, and the
document must not contain a meta element with the
charset attribute
present.
The Encoding
declaration state may be used in HTML
documents only, elements in that state must not be used in
XML documents.
- Default style state
-
...
- Refresh state
-
If another meta element in the Refresh state has
already been successfully processed (i.e. when it was inserted
the user agent processed it and reached the last step of this
list of steps), then abort these steps.
If the meta element has no content attribute, or if that
attribute's value is the empty string, then abort these
steps.
Let input be the value of the
element's content
attribute.
Let position point at the first
character of input.
Skip whitespace. 空白を読み飛ばします。
Collect a
sequence of characters in the range U+0030 DIGIT ZERO to
U+0039 DIGIT NINE, and parse the resulting string using the
rules for parsing non-negative integers. If the
sequence of characters collected is the empty string, then no
number will have been parsed; abort these steps. Otherwise, let
time be the parsed number.
Collect a
sequence of characters in the range U+0030 DIGIT ZERO to
U+0039 DIGIT NINE and U+002E FULL STOP ("."). Ignore any collected characters.
Skip whitespace. 空白を読み飛ばします。
Let url be the address of the current
page.
If the character in input pointed to
by position is a U+003B SEMICOLON (";"), then advance position to
the next character. Otherwise, jump to the last step.
Skip whitespace. 空白を読み飛ばします。
If the character in input pointed to
by position is one of U+0055 LATIN CAPITAL
LETTER U or U+0075 LATIN SMALL LETTER U, then advance position to the next character. Otherwise, jump to
the last step.
If the character in input pointed to
by position is one of U+0052 LATIN CAPITAL
LETTER R or U+0072 LATIN SMALL LETTER R, then advance position to the next character. Otherwise, jump to
the last step.
If the character in input pointed to
by position is one of U+004C LATIN CAPITAL
LETTER L or U+006C LATIN SMALL LETTER L, then advance position to the next character. Otherwise, jump to
the last step.
Skip whitespace. 空白を読み飛ばします。
If the character in input pointed to
by position is a U+003D EQUALS SIGN ("="), then advance position to
the next character. Otherwise, jump to the last step.
Skip whitespace. 空白を読み飛ばします。
Let url be equal to the substring of
input from the character at position to the end of the string.
Strip any trailing space
characters from the end of url.
Strip any U+0009 CHARACTER TABULATION, U+000A LINE FEED
(LF), and U+000D CARRIAGE RETURN (CR) characters from url.
Resolve the url value to an absolute URL. (For
the purposes of determining the base URL, the url value comes from the value of a content
attribute of the meta element.) If this fails, abort
these steps.
-
Perform one or more of the following steps:
Set a timer so that in time seconds,
adjusted to take into account user or user agent preferences,
if the user has not canceled the redirect, the user agent navigates the document's browsing
context to url, with replacement
enabled, and with the document's browsing context as the
source browsing context.
Provide the user with an interface that, when selected,
navigates a browsing context to url, with the document's browsing context as the
source browsing context.
Do nothing.
In addition, the user agent may, as with anything, inform the
user of any and all aspects of its operation, including the
state of any timers, the destinations of any timed redirects,
and so forth.
For meta elements in the Refresh state, the
content attribute must have
a value consisting either of:
just a valid non-negative integer, or
a valid non-negative integer, followed by a
U+003B SEMICOLON (;), followed by one or
more space characters,
followed by either a U+0055 LATIN CAPITAL LETTER U or a U+0075
LATIN SMALL LETTER U, a U+0052 LATIN CAPITAL LETTER R or a U+0072
LATIN SMALL LETTER R, a U+004C LATIN CAPITAL LETTER L or a U+006C
LATIN SMALL LETTER L, a U+003D EQUALS SIGN (=), and then a valid URL.
In the former case, the integer represents a number of seconds
before the page is to be reloaded; in the latter case the integer
represents a number of seconds before the page is to be replaced
by the page at the given URL.
There must not be more than one meta element with
any particular state in the document at a time.
4.2.5.4 Specifying the document's character encoding
A character encoding declaration is a mechanism by
which the character encoding used to store or transmit a document is
specified.
The following restrictions apply to character encoding
declarations:
The character encoding name given must be the name of the
character encoding used to serialize the file.
The value must be a valid character encoding name, and must be
the preferred name for that encoding. [IANACHARSET]
The character encoding declaration must be serialized without
the use of character references
or character escapes of any kind.
If the document does not start with a BOM, and if its encoding is
not explicitly given by Content-Type
metadata, then the character encoding used must be an
ASCII-compatible character encoding, and, in addition,
if that encoding isn't US-ASCII itself, then the encoding must be
specified using a meta element with a charset attribute or a
meta element in the Encoding declaration
state.
If the document contains a meta element with a charset attribute or a
meta element in the Encoding declaration
state, then the character encoding used must be an
ASCII-compatible character encoding.
Authors should not use JIS_X0212-1990, x-JIS0208, and encodings
based on EBCDIC. Authors should not use UTF-32. Authors must not use
the CESU-8, UTF-7, BOCU-1 and SCSU encodings. [CESU8] [UTF7] [BOCU1] [SCSU]
Authors are encouraged to use UTF-8. Conformance checkers may
advise against authors using legacy encodings.
In XHTML, the XML declaration should be used for inline character
encoding information, if necessary.
4.2.6 The style element4.2.6 style 要素
- Categories分類
- Metadata content.メタデータ内容。
- If the
scoped attribute is present: flow content.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- If the
scoped attribute is absent: where metadata content is expected.
- If the
scoped attribute is absent: in a noscript element that is a child of a head element.
- If the
scoped attribute is present: where flow content is expected, but before any other flow content other than other style elements and inter-element whitespace.
- Content model:内容モデル:
- Depends on the value of the
type attribute.
- Element-specific attributes:要素固有属性:
mediatypescoped- Also, the
title attribute has special semantics on this element.また、title 属性はこの要素では特別な意味を持ちます。
- DOM interface:DOM 界面:
-
interface HTMLStyleElement : HTMLElement {
attribute boolean disabled;
attribute DOMString media;
attribute DOMString type;
attribute boolean scoped;
};
The LinkStyle interface must also be implemented
by this element, the styling processing model defines
how. [CSSOM]LinkStyle 界面もこの要素に実装されなければなりません。
その方法はスタイル付け処理モデルで定義します。
[CSSOM]
The style element allows authors to embed style
information in their documents. The style element is
one of several inputs to the styling processing
model.
If the type
attribute is given, it must contain a valid MIME type, optionally
with parameters, that designates a styling language. [RFC2046] If the attribute is absent, the
type defaults to text/css. [RFC2138]
When examining types to determine if they support the language,
user agents must not ignore unknown MIME parameters — types
with unknown parameters must be assumed to be unsupported.
The media
attribute says which media the styles apply to. The value must be a
valid media query. [MQ] User
agents must apply the styles to views while their state
match the listed media, and must not apply them otherwise. [DOM3VIEWS]
The default, if the media attribute is omitted, is
all, meaning that by default styles apply to all
media.
The scoped
attribute is a boolean attribute. If the attribute is
present, then the user agent must apply the specified style
information only to the style element's parent element
(if any), and that element's child nodes. Otherwise, the specified
styles must, if applied, be applied to the entire document.
The title attribute on
style elements defines alternative style sheet
sets. If the style element has no title attribute, then it has no
title; the title attribute of
ancestors does not apply to the style element.
The title
attribute on style elements, like the title attribute on link
elements, differs from the global title attribute in that a
style block without a title does not inherit the title
of the parent element: it merely has no title.
All descendant elements must be processed, according to their
semantics, before the style element itself is
evaluated. For styling languages that consist of pure text, user
agents must evaluate style elements by passing the
concatenation of the contents of all the text nodes that are direct children of the
style element (not any other nodes such as comments or
elements), in tree order, to the style system. For
XML-based styling languages, user agents must pass all the children
nodes of the style element to the style system.
This specification does not specify a style system,
but CSS is expected to be supported by most Web browsers. [CSS21]
The media, type and scoped DOM attributes
must reflect the respective content attributes of the
same name.
The DOM disabled attribute
behaves as defined for the
alternative style sheets DOM.
4.2.7 Styling
The link and style elements can provide
styling information for the user agent to use when rendering the
document. The DOM Styling specification specifies what styling
information is to be used by the user agent and how it is to be
used. [CSSOM]
The style and link elements implement
the LinkStyle interface. [CSSOM]
For style elements, if the user agent does not
support the specified styling language, then the sheet attribute of the element's
LinkStyle interface must return null. Similarly,
link elements that do not represent external resource links that contribute to
the styling processing model (i.e. that do not have a stylesheet keyword in their rel attribute), and link
elements whose specified resource has not yet been fetched, or is
not in a supported styling language, must have their
LinkStyle interface's sheet attribute return null.
Otherwise, the LinkStyle interface's sheet attribute must return a
StyleSheet object with the attributes implemented as
follows: [CSSOM]
- The content type (
type DOM attribute)
The content type must be the same as the style's specified
type. For style elements, this is the same as the
type content attribute's
value, or text/css if that is omitted. For
link elements, this is the Content-Type metadata of the specified
resource.
- The location (
href DOM attribute)
For link elements, the location must be the
result of resolving the
URL given by the element's href content attribute, or the empty
string if that fails. For style elements, there is no
location.
- The intended destination media for style information (
media DOM attribute)
The media must be the same as the value of the element's
media content attribute.
- The style sheet title (
title DOM attribute)
The title must be the same as the value of the element's
title content attribute. If the attribute is
absent, then the style sheet does not have a title. The title is
used for defining alternative style sheet sets.
The disabled DOM
attribute on link and style elements must
return false and do nothing on setting, if the sheet attribute of their
LinkStyle interface is null. Otherwise, it must return
the value of the StyleSheet interface's disabled attribute on
getting, and forward the new value to that same attribute on
setting.
4.3 Scripting4.3 スクリプティング
Scripts allow authors to add interactivity to their documents.
Authors are encouraged to use declarative alternatives to
scripting where possible, as declarative mechanisms are often more
maintainable, and many users disable scripting.
For example, instead of using script to show or hide a section
to show more details, the details element could be
used.
Authors are also encouraged to make their applications degrade
gracefully in the absence of scripting support.
For example, if an author provides a link in a table header to
dynamically resort the table, the link could also be made to
function without scripts by requesting the sorted table from the
server.
4.3.1 The script element4.3.1 script 要素
- Categories分類
- Metadata content.メタデータ内容。
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where metadata content is expected.メタデータ内容が期待される場所。
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- If there is no
src
attribute, depends on the value of the type attribute.
- If there is a
src
attribute, the element must be empty.
- Element-specific attributes:要素固有属性:
srcasyncdefertypecharset- DOM interface:DOM 界面:
-
interface HTMLScriptElement : HTMLElement {
attribute DOMString src;
attribute boolean async;
attribute boolean defer;
attribute DOMString type;
attribute DOMString charset;
attribute DOMString text;
};
The script element allows authors to include dynamic
script and data blocks in their documents.
When used to include dynamic scripts, the scripts may either be
embedded inline or may be imported from an external file using the
src attribute. If the language
is not that described by "text/javascript",
then the type attribute must
be present. If the type
attribute is present, its value must be the type of the script's
language.
When used to include data blocks, the data must be embedded
inline, the format of the data must be given using the type attribute, and the src attribute must not be
specified.
The type
attribute gives the language of the script or format of the data. If
the attribute is present, its value must be a valid MIME type,
optionally with parameters. The charset
parameter must not be specified. (The default, which is used if the
attribute is absent, is "text/javascript".) [RFC2046]
The src
attribute, if specified, gives the address of the external script
resource to use. The value of the attribute must be a valid
URL identifying a script resource of the type given by the
type attribute, if the
attribute is present, or of the type "text/javascript", if the attribute is absent.
The charset
attribute gives the character encoding of the external script
resource. The attribute must not be specified if the src attribute is not present. If the
attribute is set, its value must be a valid character encoding name,
and must be the preferred name for that encoding. [IANACHARSET]
The encoding specified must be the encoding used by the script
resource. If the charset
attribute is omitted, the character encoding of the document will be
used. If the script resource uses a different encoding than the
document, then the attribute must be specified.
The async and
defer attributes
are boolean attributes that
indicate how the script should be executed.
There are three possible modes that can be selected using these
attributes. If the async
attribute is present, then the script will be executed
asynchronously, as soon as it is available. If the async attribute is not present but
the defer attribute is
present, then the script is executed when the page has finished
parsing. If neither attribute is present, then the script is
fetched and executed immediately, before the user agent continues
parsing the page. The exact processing details for these attributes
is described below.
The defer attribute may be
specified even if the async
attribute is specified, to cause legacy Web browsers that only
support defer (and not async) to fall back to the defer behavior instead of the
synchronous blocking behavior that is the default.
Changing the src, type, charset, async, and defer attributes dynamically has no
direct effect; these attribute are only used at specific times
described below (namely, when the element is inserted into the document).
script elements have four associated pieces of
metadata. The first is a flag indicating whether or not the script
block has been "already executed". Initially,
script elements must have this flag unset (script
blocks, when created, are not "already executed"). When a
script element is cloned, the "already executed" flag,
if set, must be propagated to the clone when it is created. The
second is a flag indicating whether the element was
"parser-inserted". This flag is set by the HTML
parser and is used to handle document.write() calls. The
third and fourth pieces of metadata are the script's
type and the script's character
encoding. They are determined when the script is run,
based on the attributes on the element at that time.
When an XML parser creates a script
element, it must be marked as being
"parser-inserted". When the element's end tag is
parsed, the user agent must run the script element.
Equivalent requirements exist for the HTML
parser, but they are detailed in that section instead.
When a script element that is marked as neither
having "already executed" nor being
"parser-inserted" is inserted into a document, the user agent
must run the
script element.
Running a script: When a
script element is to be run, the user agent must act as
follows:
-
If either:
the script element has a type attribute and its value is
the empty string, or
the script element has no type attribute but it has a language attribute and
that attribute's value is the empty string, or
the script element has neither a type attribute nor a language attribute, then
...let the script's type for this
script element be "text/javascript".
Otherwise, if the script element has a type attribute, let the
script's type for this script element be the
value of that attribute.
Otherwise, the element has a language attribute; let
the script's type for this script element
be the concatenation of the string "text/"
followed by the value of the language attribute.
-
If the script element has a charset attribute, then let
the script's character encoding for this
script element be the encoding given by the charset attribute.
Otherwise, let the script's character encoding for
this script element be the same as the encoding of the document
itself.
-
If the script element is without
script, or if the script element was created
by an XML parser that itself was created as part of
the processing of the innerHTML attribute's setter, or if the user agent does not support the
scripting language given by the script's type
for this script element, then the user agent must
abort these steps at this point. The script is not executed.
-
The user agent must set the element's "already
executed" flag.
-
If the element has a src
attribute, then the specified resource must be fetched.
For historical reasons, if the URL is a javascript:
URL, then the user agent must not, despite the requirements
in the definition of the fetching
algorithm, actually execute the given script; instead the user
agent must act as if it had received an empty HTTP 400
response.
Once the fetching process has completed, and the script has
completed loading, the user agent will have to complete
the steps described
below. (If the parser is still active at that time, those
steps defer to the parser to handle the execution of pending
scripts.)
For performance reasons, user agents may start fetching the
script as soon as the attribute is set, instead, in the hope that
the element will be inserted into the document. Either way, once
the element is inserted into the document, the load must have
started. If the UA performs such prefetching, but the element is
never inserted in the document, or the src attribute is dynamically
changed, then the user agent will not execute the script, and the
fetching process will have been effectively wasted.
-
Then, the first of the following options that describes the
situation must be followed:
- If the document is still being parsed, and the element has a
defer attribute, and the
element does not have an async attribute
- The element must be added to the end of the list of
scripts that will execute when the document has finished
parsing.
This isn't compatible with IE for inline
deferred scripts, but then what IE does is pretty hard to pin down
exactly. Do we want to keep this like it is? Be more compatible?
- If the element has an
async attribute and a src attribute
- The element must be added to the end of the list of
scripts that will execute asynchronously.
- If the element has an
async attribute but no src attribute, and the list
of scripts that will execute asynchronously is not
empty
- The element must be added to the end of the list of
scripts that will execute asynchronously.
- If the element has a
src
attribute and has been flagged as
"parser-inserted"
- The element is the pending external
script. (There can only be one such script at a
time.)
- If the element has a
src
attribute
- The element must be added to the end of the list of
scripts that will execute as soon as possible.
- Otherwiseそれ以外の場合
- The user agent must immediately execute the script, even if other scripts
are already executing.
When a script completes loading: If the script's
element was added to one of the lists mentioned above and the
document is still being parsed, then the parser handles
it. Otherwise, the UA must run the following steps as the task that the networking task
source places on the task queue:
- If the script's element was added to the list of scripts
that will execute when the document has finished parsing:
-
-
If the script's element is not the first element in the list,
then do nothing yet. Stop going through these steps.
-
Otherwise, execute the
script (that is, the script associated with the first
element in the list).
-
Remove the script's element from the list (i.e. shift out the
first entry in the list).
-
If there are any more entries in the list, and if the script
associated with the element that is now the first in the list is
already loaded, then jump back to step two to execute it.
- If the script's element was added to the list of scripts
that will execute asynchronously:
-
-
If the script is not the first element in the list, then do
nothing yet. Stop going through these steps.
-
Execute the
script (the script associated with the first element in
the list).
-
Remove the script's element from the list (i.e. shift out the
first entry in the list).
-
If there are any more scripts in the list, and the element
now at the head of the list had no src attribute when it was added
to the list, or had one, but its associated script has finished
loading, then jump back to step two to execute the script
associated with this element.
- If the script's element was added to the list of scripts
that will execute as soon as possible:
-
-
Execute the
script.
-
Remove the script's element from the list.
Fetching an external script must delay the load event.
Executing a script
block: When the steps above require that the script be
executed, the user agent must act as follows:
- If the load resulted in an error (for example a DNS error, or
an HTTP 404 error)
Executing the script must just consist of firing an error
event at the element.
- If the load was successful
-
-
If the script element's Document is
the active document in its browsing
context, the user agent must execute the script:
- If the script is from an external file
-
That file must be used as the file to execute.
The file must be interpreted using the character encoding
given by the script's character encoding, regardless
of any metadata given by the file's Content-Type metadata.
This means that a UTF-16 document will
always assume external scripts are UTF-16...? This applies,
e.g., to document's created using createDocument()... It also
means changing document.charSet will affect the character
encoding used to interpret scripts, is that really what
happens?
- If the script is inline
-
For scripting languages that consist of pure text, user
agents must use the value of the DOM text attribute (defined below) as
the script to execute, and for XML-based scripting languages,
user agents must use all the child nodes of the
script element as the script to execute.
In any case, the user agent must execute the script according to
the semantics defined by the language associated with the
script's type (see the scripting
languages section below).
The script execution context of the script must
be the Window object of that browsing
context.
The script document context of the script must
be the Document object that owns the
script element.
The element's attributes' values might have changed
between when the element was inserted into the document and when the
script has finished loading, as may its other attributes; similarly,
the element itself might have been taken back out of the DOM, or had
other changes made. These changes do not in any way affect the above
steps; only the values of the attributes at the time the
script element is first inserted into the document
matter.
-
Then, the user agent must fire a load event at the
script element.
The DOM attributes src, type, charset, async, and defer, each must
reflect the respective content attributes of the same
name.
The DOM attribute text must return a
concatenation of the contents of all the text nodes that are direct children of the
script element (ignoring any other nodes such as
comments or elements), in tree order. On setting, it must act the
same way as the textContent DOM attribute.
In this example, two script elements are used. One
embeds an external script, and the other includes some data.
<script src="game-engine.js"></script>
<script type="text/x-game-map">
........U.........e
o............A....e
.....A.....AAA....e
.A..AAA...AAAAA...e
</script>
The data in this case might be used by the script to generate
the map of a video game. The data doesn't have to be used that way,
though; maybe the map data is actually embedded in other parts of
the page's markup, and the data block here is just used by the
site's search engine to help users who are looking for particular
features in their game maps.
4.3.1.1 Scripting languages
A user agent is said to support the scripting language
if the script's type matches the MIME type of a scripting
language that the user agent implements.
The following lists some MIME types and the languages to which
they refer:
text/javascripttext/javascript1.1text/javascript1.2text/javascript1.3- ECMAScript. [ECMA262]
text/javascript;e4x=1- ECMAScript with ECMAScript for XML. [ECMA357]
User agents may support other MIME types and other languages.
When examining types to determine if they support the language,
user agents must not ignore unknown MIME parameters — types
with unknown parameters must be assumed to be unsupported.
4.3.2 The noscript element4.3.2 noscript 要素
- Categories分類
- Metadata content.メタデータ内容。
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- In a
head element of an HTML document, if there are no ancestor noscript elements.
- Where phrasing content is expected in HTML documents, if there are no ancestor
noscript elements.
- Content model:内容モデル:
- Without script, in a
head element: in any order, zero or more link elements, zero or more style elements, and zero or more meta elements.
- Without script, not in a
head element: transparent, but there must be no noscript element descendants.
- With script: text that conforms to the requirements given in the prose.
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The noscript element does not represent anything. It
is used to present different markup to user agents that support
scripting and those that don't support scripting, by affecting how
the document is parsed.
The noscript element must not be used in XML
documents.
The noscript element is only
effective in the HTML serialization, it has no effect in the XML
serialization.
When used in HTML documents, the allowed content
model is as follows:
In a head element, if the noscript
element is without script, then the content model of a
noscript element must contain only link,
style, and meta elements. If the
noscript element is with script, then the
content model of a noscript element is text, except
that invoking the HTML fragment parsing algorithm with
the noscript element as the context
element and the text contents as the input must
result in a list of nodes that consists only of link,
style, and meta elements.
Outside of head elements, if the
noscript element is without script, then
the content model of a noscript element is
transparent, with the additional restriction that a
noscript element must not have a noscript
element as an ancestor (that is, noscript can't be
nested).
Outside of head elements, if the
noscript element is with script, then the
content model of a noscript element is text, except
that the text must be such that running the following algorithm
results in a conforming document with no noscript
elements and no script elements, and such that no step
in the algorithm causes an HTML parser to flag a
parse error:
Remove every script element from the
document.
Make a list of every noscript element in the
document. For every noscript element in that list,
perform the following steps:
Let the parent element be the parent
element of the noscript element.
Take all the children of the parent element
that come before the noscript element, and call these
elements the before children.
Take all the children of the parent element
that come after the noscript element, and
call these elements the after children.
Let s be the concatenation of all the
text node children of the noscript
element.
Set the innerHTML
attribute of the parent element to the value
of s. (This, as a side-effect, causes the
noscript element to be removed from the
document.)
Insert the before children at the start of
the parent element, preserving their original
relative order.
Insert the after children at the end of the
parent element, preserving their original
relative order.
The noscript element has no other requirements. In
particular, children of the noscript element are not
exempt from form submission, scripting, and so forth, even when the
element is with script.
All these contortions are required because, for
historical reasons, the noscript element is handled
differently by the HTML parser based on whether scripting was enabled or not when the
parser was invoked. The element is not allowed in XML, because in
XML the parser is not affected by such state, and thus the element
would not have the desired effect.
The noscript element interacts poorly
with the designMode
feature. Authors are encouraged to not use noscript
elements on pages that will have designMode enabled.
4.3.3 The eventsource element4.3.3 eventsource 要素
- Categories分類
- Metadata content.メタデータ内容。
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where metadata content is expected.メタデータ内容が期待される場所。
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
src- DOM interface:DOM 界面:
-
interface HTMLEventSourceElement : HTMLElement {
attribute DOMString src;
};
The eventsource element represents a target for
events generated by a remote server.
The src
attribute, if specified, must give a valid URL
identifying a resource that uses the text/event-stream
format.
When an eventsource element with a src attribute specified is inserted into the
document, and when an eventsource element that
is already in the document has a src attribute added, the user
agent must run the add declared event source
algorithm.
While an eventsource element is in a document, if its src
attribute is mutated, the user agent must must run the remove
declared event source algorithm followed by the add
declared event source algorithm.
When an eventsource element with a src attribute specified is
removed from a document, and when an
eventsource element that is in a document with a src
attribute specified has its src attribute removed, the user
agent must run the remove declared event source
algorithm.
When it is created, an eventsource element must
have its current declared event source set to
"undefined".
The add declared event source algorithm is as
follows:
Resolve the URL
specified by the eventsource element's src attribute.
If that fails, then set the element's current declared event
source to "undefined" and abort these steps.
Otherwise, act as if the addEventSource()
method on the eventsource element had been invoked
with the resulting absolute URL.
Let the element's current declared event source be that
absolute URL.
The remove declared event source algorithm is as
follows:
If the element's current declared event source is
"undefined", abort these steps.
Otherwise, act as if the removeEventSource()
method on the eventsource element had been invoked
with the element's current declared event source.
Let the element's current declared event source be
"undefined".
There can be more than one eventsource element per
document, but authors should take care to avoid opening multiple
connections to the same server as HTTP recommends a limit to the
number of simultaneous connections that a user agent can open per
server.
The src DOM
attribute must reflect the content attribute of the
same name.
4.4 Sections4.4 章節
Some elements, for example
address elements, are scoped to their nearest ancestor
sectioning content. For such elements x, the elements that apply to a sectioning
content element e are all the x elements whose nearest sectioning
content ancestor is e.
4.4.1 The body element4.4.1 body 要素
- Categories分類
- Sectioning content.章節付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As the second element in an
html element.html 要素の2つ目の要素として。
- Content model:内容モデル:
- Flow content.流れ内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
-
interface HTMLBodyElement : HTMLElement {};
The body element represents the main content of the
document.body 要素は文書の主な内容を表します。
In conforming documents, there is only one body
element. The document.body
DOM attribute provides scripts with easy access to a document's
body element.適合文書には1つだけ body
要素があります。
document.body
DOM 属性は文書の
body
要素への簡単なアクセス手段をスクリプトに提供します。
Some DOM operations (for example, parts of the
drag and drop model) are defined in terms of "the
body element". This refers to a particular element in the
DOM, as per the definition of the term, and not any arbitrary
body element.特定の DOM 操作 (例えば、ドラッグ・アンド・ドロップ・モデルの一部分)
は「文書
body 要素」に関して定義されています。文書 body 要素は、
その用語の定義の通り、 DOM 中の特定の要素を指しており、
任意の body 要素ではありません。
4.4.2 The section element4.4.2 section 要素
- Categories分類
- Flow content.流れ内容。
- Sectioning content.章節付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Flow content.流れ内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The section element represents a generic document or
application section. A section, in this context, is a thematic
grouping of content, typically with a header, possibly with a
footer.
Examples of sections would be chapters, the
various tabbed pages in a tabbed dialog box, or the numbered
sections of a thesis. A Web site's home page could be split into
sections for an introduction, news items, contact information.
4.4.3 The nav element4.4.3 nav 要素
- Categories分類
- Flow content.流れ内容。
- Sectioning content.章節付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Flow content.流れ内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The nav element represents a section of a page that
links to other pages or to parts within the page: a section with
navigation links. Not all groups of links on a page need to be in a
nav element — only sections that consist of
primary navigation blocks are appropriate for the nav
element. In particular, it is common for footers to have a list of
links to various key parts of a site, but the footer
element is more appropriate in such cases.
In the following example, the page has several places where
links are present, but only one of those places is considered a
navigation section.
<body>
<header>
<h1>Wake up sheeple!</h1>
<p><a href="news.html">News</a> -
<a href="blog.html">Blog</a> -
<a href="forums.html">Forums</a></p>
</header>
<nav>
<h1>Navigation</h1>
<ul>
<li><a href="articles.html">Index of all articles</a><li>
<li><a href="today.html">Things sheeple need to wake up for today</a><li>
<li><a href="successes.html">Sheeple we have managed to wake</a><li>
</ul>
</nav>
<article>
<p>...page content would be here...</p>
</article>
<footer>
<p>Copyright © 2006 The Example Company</p>
<p><a href="about.html">About</a> -
<a href="policy.html">Privacy Policy</a> -
<a href="contact.html">Contact Us</a></p>
</footer>
</body>
4.4.4 The article element4.4.4 article 要素
- Categories分類
- Flow content.流れ内容。
- Sectioning content.章節付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Flow content.流れ内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The article element represents a section of a page
that consists of a composition that forms an independent part of a
document, page, or site. This could be a forum post, a magazine or
newspaper article, a Web log entry, a user-submitted comment, or any
other independent item of content.
An article element is "independent" in
that its contents could stand alone, for example in syndication.
However, the element is still associated with its ancestors; for
instance, contact information that applies to a parent body
element still covers the article as well.
When article elements are nested, the inner
article elements represent articles that are in
principle related to the contents of the outer article. For
instance, a Web log entry on a site that accepts user-submitted
comments could represent the comments as article
elements nested within the article element for the Web
log entry.
Author information associated with an article
element (q.v. the address element) does not apply to
nested article elements.
4.4.5 The aside element4.4.5 aside 要素
- Categories分類
- Flow content.流れ内容。
- Sectioning content.章節付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Flow content.流れ内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The aside element represents a section of a page
that consists of content that is tangentially related to the content
around the aside element, and which could be considered
separate from that content. Such sections are often represented as
sidebars in printed typography.
The following example shows how an aside is used to mark up
background material on Switzerland in a much longer news story on Europe.
<aside>
<h1>Switzerland</h1>
<p>Switzerland, a land-locked country in the middle of geographic
Europe, has not joined the geopolitical European Union, though it is
a signatory to a number of European treaties.</p>
</aside>
The following example shows how an aside is used to mark up
a pull quote in a longer article.
...
<p>He later joined a large company, continuing on the same work.
<q>I love my job. People ask me what I do for fun when I'm not at
work. But I'm paid to do my hobby, so I never know what to
answer. Some people wonder what they would do if they didn't have to
work... but I know what I would do, because I was unemployed for a
year, and I filled that time doing exactly what I do
now.</q></p>
<aside>
<q> People ask me what I do for fun when I'm not at work. But I'm
paid to do my hobby, so I never know what to answer. </q>
</aside>
<p>Of course his work — or should that be hobby? —
isn't his only passion. He also enjoys other pleasures.</p>
...
4.4.6 The h1, h2,
h3, h4,
h5, and h6
elements4.4.6 h1、h2、
h3、h4、
h5、h6
各要素
- Categories分類
- Flow content.流れ内容。
- Heading content.見出し内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
These elements define headers for their sections.これらの要素は、その章節の見出しを定義します。
The semantics and meaning of these elements are defined in the
section on headings and sections.これらの要素の意味は見出しと章節の節で定義します。
These elements have a rank given by the number in
their name. The h1 element is said to have the highest
rank, the h6 element has the lowest rank, and two
elements with the same name have equal rank.これらの要素は、その名前中の数字により与えられる階数を持ちます。
h1 要素は最高の階数を持つといい、
h6 要素は最低の階数を持ち、
同じ名前の2つの要素は等しい階数を持ちます。
- Categories分類
- Flow content.流れ内容。
- Heading content.見出し内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Flow content, including at least one descendant
that is heading content, but no sectioning
content descendants, no
header element
descendants, and no footer element descendants.流れ内容で、最低1つの見出し内容の子孫を含み、
章節付け内容である子孫、header 要素である子孫、footer 要素である子孫を含まない。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The header element represents the header of a
section. The element is typically used to group a set of
h1–h6 elements to mark up a page's title
with its subtitle or tagline. However, header elements
may contain more than just the section's headings and subheadings
— for example it would be reasonable for the header to include
version history information.
header 要素は、
章節の見出しを表します。この要素は、普通、
h1–h6
要素の集合を群化し、頁の題名と副題や謳い文句をマーク付けするために使います。しかし、
header 要素は純粋に章節の見出しや副見出しではないものも含んで構いません。
例えば、版履歴情報も見出しに含めるのが適当かもしれません。
For the purposes of document summaries, outlines, and the like,
the text of header elements is defined to be the text
of the highest ranked
h1–h6 element descendant of the
header element, if there are any such elements, and the
first such element if there are multiple elements with that
rank. If there are no such elements, then the text of
the header element is the empty string.
Other heading elements in the header element
indicate subheadings or subtitles.header 要素中の他の見出し要素は副見出しや副題を表します。
The rank of a header element is the
same as for an h1 element (the highest rank).header 要素の階数は、
h1 要素のものと同じ (最高の階数) です。
The section on headings and sections
defines how header elements are assigned to individual
sections.見出しと章節の節で、
header 要素が個々の章節にどう割り当てられるかを定義します。
Here are some examples of valid headers. In each case, the
emphasised text represents the text that would be used as the
header in an application extracting header data and ignoring
subheadings.次に示すのは、妥当な見出しの例です。それぞれの場合で、
強調した文章が、見出しデータを取り出し、副見出しを無視する応用で見出しとして使われる文章を表します。
<header>
<h1>The reality dysfunction</h1>
<h2>Space is not the only void</h2>
</header>
<header>
<h1>Dr. Strangelove</h1>
<h2>Or: How I Learned to Stop Worrying and Love the Bomb</h2>
</header>
<header>
<p>Welcome to...</p>
<h1>Voidwars!</h1>
</header>
<header>
<h1>Scalable Vector Graphics (SVG) 1.2</h1>
<h2>W3C Working Draft 27 October 2004</h2>
<dl>
<dt>This version:</dt>
<dd><a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/">http://www.w3.org/TR/2004/WD-SVG12-20041027/</a></dd>
<dt>Previous version:</dt>
<dd><a href="http://www.w3.org/TR/2004/WD-SVG12-20040510/">http://www.w3.org/TR/2004/WD-SVG12-20040510/</a></dd>
<dt>Latest version of SVG 1.2:</dt>
<dd><a href="http://www.w3.org/TR/SVG12/">http://www.w3.org/TR/SVG12/</a></dd>
<dt>Latest SVG Recommendation:</dt>
<dd><a href="http://www.w3.org/TR/SVG/">http://www.w3.org/TR/SVG/</a></dd>
<dt>Editor:</dt>
<dd>Dean Jackson, W3C, <a href="mailto:dean@w3.org">dean@w3.org</a></dd>
<dt>Authors:</dt>
<dd>See <a href="#authors">Author List</a></dd>
</dl>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notic ...
</header>
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Flow content, but with no heading
content descendants, no sectioning content
descendants, and no
footer element descendants.流れ要素、ただし見出し内容である子孫、章節内容である子孫、footer 要素である子孫を含まない。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The footer element represents a footer for the
section it applies to. A footer
typically contains information about its section such as who wrote
it, links to related documents, copyright data, and the like.
Contact information for the section given in a
footer should be marked up using the
address element.footer 中で与えられる章節の連絡先情報は、 address 要素を使ってマーク付けするべきです。
Footers don't necessarily have to appear at the end of a section,
though they usually do.足部は、通常は章節の終わりに現れますが、必ずしもそうである必要はありません。
Here is a page with two footers, one at the top and one at the
bottom, with the same content:次に示すのは、2つの足部がある頁です。2つは同じ内容で、1つは上にあり、
もう1つは下にあります。
<body>
<footer><a href="../">Back to index...</a></footer>
<header>
<h1>Lorem ipsum</h1>
<h2>The ipsum of all lorems</h2>
</header>
<p>A dolor sit amet, consectetur adipisicing elit, sed do eiusmod
tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex
ea commodo consequat. Duis aute irure dolor in reprehenderit in
voluptate velit esse cillum dolore eu fugiat nulla
pariatur. Excepteur sint occaecat cupidatat non proident, sunt in
culpa qui officia deserunt mollit anim id est laborum.</p>
<footer><a href="../">Back to index...</a></footer>
</body>
4.4.9 The address element4.4.9 address 要素
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Flow content, but with no heading
content descendants, no sectioning content
descendants, no
footer element descendants, and no
address element descendants.
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The address element represents the contact
information for the section it applies
to. If it applies to the body element,
then it instead applies to the document as a whole.
For example, a page at the W3C Web site related to HTML might
include the following contact information:
<ADDRESS>
<A href="../People/Raggett/">Dave Raggett</A>,
<A href="../People/Arnaud/">Arnaud Le Hors</A>,
contact persons for the <A href="Activity">W3C HTML Activity</A>
</ADDRESS>
The address element must not be used to represent
arbitrary addresses (e.g. postal addresses), unless those addresses
are contact information for the section. (The p element
is the appropriate element for marking up such addresses.)
The address element must not contain information
other than contact information.
For example, the following is non-conforming use of the
address element:
<ADDRESS>Last Modified: 1999/12/24 23:37:50</ADDRESS>
Typically, the address element would be included
with other information in a footer element.
To determine the contact information for a sectioning
content element (such as a document's body
element, which would give the contact information for the page), UAs
must collect all the address elements that apply to that sectioning
content element and its ancestor sectioning
content elements. The contact information is the collection
of all the information given by those elements.
Contact information for one sectioning
content element, e.g. an aside element, does
not apply to its ancestor elements, e.g. the page's
body.
4.4.10 Headings and sections4.4.10 見出しと章節
The h1–h6 elements and the
header element are headings.
The first element of heading content in an element
of sectioning content gives the header for that
section. Subsequent headers of equal or higher rank
start new (implied) sections, headers of lower rank
start subsections that are part of the previous one.
Sectioning content elements are always considered
subsections of their nearest ancestor element of sectioning
content, regardless of what implied sections other headings
may have created.
Certain elements are said to be sectioning roots, including blockquote and
td elements. These elements can have their own
outlines, but the sections and headers inside these elements do not
contribute to the outlines of their ancestors.
For the following fragment:
<body>
<h1>Foo</h1>
<h2>Bar</h2>
<blockquote>
<h3>Bla</h3>
</blockquote>
<p>Baz</p>
<h2>Quux</h2>
<section>
<h3>Thud</h3>
</section>
<p>Grunt</p>
</body>
...the structure would be:
Foo (heading of explicit body section, containing the "Grunt" paragraph)
Bar (heading starting implied section, containing a block quote and the "Baz" paragraph)
Quux (heading starting implied section)
Thud (heading of explicit section section)
Notice how the section ends the earlier implicit
section so that a later paragraph ("Grunt") is back at the top
level.
Sections may contain headers of any rank, but
authors are strongly encouraged to either use only h1
elements, or to use elements of the appropriate rank
for the section's nesting level.
Authors are also encouraged to explicitly wrap sections in
elements of sectioning content, instead of relying on
the implicit sections generated by having multiple heading in one
element of sectioning content.
For example, the following is correct:
<body>
<h4>Apples</h4>
<p>Apples are fruit.</p>
<section>
<h2>Taste</h2>
<p>They taste lovely.</p>
<h6>Sweet</h6>
<p>Red apples are sweeter than green ones.</p>
<h1>Color</h1>
<p>Apples come in various colors.</p>
</section>
</body>
However, the same document would be more clearly expressed
as:
<body>
<h1>Apples</h1>
<p>Apples are fruit.</p>
<section>
<h2>Taste</h2>
<p>They taste lovely.</p>
<section>
<h3>Sweet</h3>
<p>Red apples are sweeter than green ones.</p>
</section>
</section>
<section>
<h2>Color</h2>
<p>Apples come in various colors.</p>
</section>
</body>
Both of the documents above are semantically identical and would
produce the same outline in compliant user agents.
4.4.10.1 Creating an outline
This section defines an algorithm for creating an outline for a
sectioning content element or a sectioning
root element. It is defined in terms of a walk over the nodes
of a DOM tree, in tree order, with each node being visited when it
is entered and when it is exited during the walk.
The outline for a sectioning content
element or a sectioning root element consists of a list
of one or more potentially nested sections. A section is a container that
corresponds to some nodes in the original DOM tree. Each section can
have one heading associated with it, and can contain any number of
further nested sections. The algorithm for the outline also
associates each node in the DOM tree with a particular section and
potentially a heading. (The sections in the outline aren't
section elements, though some may correspond to such
elements — they are merely conceptual sections.)
The following markup fragment:
<body>
<h1>A</h1>
<p>B</p>
<h2>C</h2>
<p>D</p>
<h2>E</h2>
<p>F</p>
</body>
...results in the following outline being created for the
body node (and thus the entire document):
-
Section created for body node.
Associated with heading "A".
Also associated with paragraph "B".
Nested sections:
-
Section implied for first h2 element.
Associated with heading "C".
Also associated with paragraph "D".
No nested sections.
-
Section implied for second h2 element.
Associated with heading "E".
Also associated with paragraph "F".
No nested sections.
The algorithm that must be followed during a walk of a DOM
subtree rooted at a sectioning content element or a
sectioning root element to determine that element's
outline is as follows:
Let current outlinee be null. (It holds
the element whose outline is being created.)
Let current section be null. (It holds a
pointer to a section, so that
elements in the DOM can all be associated with a section.)
Create a stack to hold elements, which is used to handle
nesting. Initialize this stack to empty.
-
As you walk over the DOM in tree order, trigger
the first relevant step below for each element as you enter and
exit it.
- If the top of the stack is an element, and you are exiting
that element
-
The element being exited is a heading
content element.
Pop that element from the stack.
- If the top of the stack is a heading content
element
Do nothing.
- When entering a sectioning content element or a
sectioning root element
-
If current outlinee is not null, push
current outlinee onto the stack.
Let current outlinee be the element
that is being entered.
Let current section be a newly created
section for the current outlinee element.
Let there be a new outline for the new current outlinee, initialized with just the new
current section as the only section in the outline.
- When exiting a sectioning content element, if
the stack is not empty
-
Pop the top element from the stack, and let the current outlinee be that element.
Let current section be the last section
in the outline of the current
outlinee element.
Append the outline of the sectioning
content element being exited to the current
section. (This does not change which section is the last
section in the outline.)
- When exiting a sectioning root element, if the
stack is not empty
-
Run these steps:
Pop the top element from the stack, and let the current outlinee be that element.
Let current section be the last
section in the outline of the current
outlinee element.
Finding the deepest child: If current section has no child sections, stop
these steps.
Let current section be the last
child section of the
current current section.
Go back to the substep labeled finding the deepest
child.
- When exiting a sectioning content element or a
sectioning root element
-
The current outlinee is
the element being exited.
Let current section be the first section in the
outline of the current outlinee
element.
Skip to the next step in the overall set of steps. (The walk
is over.)
- If the current outlinee is null.
Do nothing.
- When entering a heading content element
-
If the current section has no heading,
let the element being entered be the heading for the current section.
Otherwise, if the element being entered has a
rank equal to or greater than the heading of the
last section of the outline of the current outlinee, then create a new section and append it to the
outline of the current outlinee
element, so that this new section is the new last section of
that outline. Let current section be that
new section. Let the element being entered be the new heading
for the current section.
Otherwise, run these substeps:
Let candidate section be current section.
If the element being entered has a rank
lower than the rank of the heading of the candidate section, then create a new section, and append it to candidate section. (This does not change which
section is the last section in the outline.) Let current section be this new section. Let the
element being entered be the new heading for the current section. Abort these substeps.
Let new candidate section be the
section that contains candidate section in the outline of
current outlinee.
Let candidate section be new candidate section.
Return to step 2.手順 2 に戻ります。
Push the element being entered onto the stack. (This causes
the algorithm to skip any descendants of the element.)
Recall that h1 has the
highest rank, and h6 has the lowest
rank.
- Otherwiseそれ以外の場合
Do nothing.
In addition, whenever you exit a node,
after doing the steps above, if current
section is not null, associate the node with the section current
section.
If the current outlinee is null,
then there was no sectioning content element or
sectioning root element in the DOM. There is no
outline. Abort these steps.
Associate any nodes that were not associated with a section in the steps above with current outlinee as their section.
Associate all nodes with the heading of the section with which they are
associated, if any.
If current outlinee is the
body element, then the outline created for that
element is the outline of the entire document.
The tree of sections created by the algorithm above, or a proper
subset thereof, must be used when generating document outlines, for
example when generating tables of contents.
When creating an interactive table of contents, entries should
jump the user to the relevant sectioning content
element, if the section was
created for a real element in the original document, or to the
relevant heading content element, if the section in the tree was generated for
a heading in the above process.
Selecting the first section of the document therefore
always takes the user to the top of the document, regardless of
where the first header in the body is to be found.
The following JavaScript function shows how the tree walk could
be implemented. The root argument is the root
of the tree to walk, and the enter and exit arguments are callbacks that are called with
the nodes as they are entered and exited. [ECMA262]
function (root, enter, exit) {
var node = root;
start: while (node) {
enter(node);
if (node.firstChild) {
node = node.firstChild;
continue start;
}
while (node) {
exit(node);
if (node.nextSibling) {
node = node.nextSibling;
continue start;
}
if (node == root)
node = null;
else
node = node.parentNode;
}
}
}
4.4.10.2 Distinguishing site-wide headings from page headings
Given the outline of a document, but ignoring any
sections created for nav and aside
elements, and any of their descendants, if the only root of the tree
is the body element's section, and it has only a single
subsection which is created by an article element, then
the heading of the body element should be
assumed to be a site-wide heading, and the heading of the
article element should be assumed to be the page's
heading.
If a page starts with a heading that is common to the whole site,
the document must be authored such that, in the document's
outline, ignoring any sections created for
nav and aside elements and any of their
descendants, the tree has only one root section, the body
element's section, its heading is the site-wide heading,
the body element has just one subsection,
that subsection is created by an article element, and
that article's heading is the page heading.
If a page does not contain a site-wide heading, then the page
must be authored such that, in the document's outline,
ignoring any sections created for nav and
aside elements and any of their descendants, either
the body element has no subsections, or it
has more than one subsection, or it has a single subsection but that
subsection is not created by an article element, or
there is more than one section
at the root of the outline.
Conceptually, a site is thus a document with many
articles — when those articles are split into many pages, the
heading of the original single page becomes the heading of the site,
repeated on every page.
4.5 Grouping content
4.5.1 The p element4.5.1 p 要素
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The p element represents a
paragraph.
The following examples are conforming HTML fragments:
<p>The little kitten gently seated himself on a piece of
carpet. Later in his life, this would be referred to as the time the
cat sat on the mat.</p>
<fieldset>
<legend>Personal information</legend>
<p>
<label>Name: <input name="n"></label>
<label><input name="anon" type="checkbox"> Hide from other users</label>
</p>
<p><label>Address: <textarea name="a"></textarea></label></p>
</fieldset>
<p>There was once an example from Femley,<br>
Whose markup was of dubious quality.<br>
The validator complained,<br>
So the author was pained,<br>
To move the error from the markup to the rhyming.</p>
The p element should not be used when a more
specific element is more appropriate.
The following example is technically correct:
<section>
<!-- ... -->
<p>Last modified: 2001-04-23</p>
<p>Author: fred@example.com</p>
</section>
However, it would be better marked-up as:
<section>
<!-- ... -->
<footer>Last modified: 2001-04-23</footer>
<address>Author: fred@example.com</address>
</section>
Or:
<section>
<!-- ... -->
<footer>
<p>Last modified: 2001-04-23</p>
<address>Author: fred@example.com</address>
</footer>
</section>
4.5.2 The hr element4.5.2 hr 要素
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The hr element represents a
paragraph-level thematic break, e.g. a scene change in
a story, or a transition to another topic within a section of a
reference book.
4.5.3 The br element4.5.3 br 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The br element represents a line break.
br elements must be empty. Any content inside
br elements must not be considered part of the
surrounding text.
br elements must be used only for line breaks that
are actually part of the content, as in poems or addresses.
The following example is correct usage of the br
element:
<p>P. Sherman<br>
42 Wallaby Way<br>
Sydney</p>
br elements must not be used for separating thematic
groups in a paragraph.
The following examples are non-conforming, as they abuse the
br element:
<p><a ...>34 comments.</a><br>
<a ...>Add a comment.<a></p>
<p>Name: <input name="name"><br>
Address: <input name="address"></p>
Here are alternatives to the above, which are correct:
<p><a ...>34 comments.</a></p>
<p><a ...>Add a comment.<a></p>
<p>Name: <input name="name"></p>
<p>Address: <input name="address"></p>
If a paragraph consists of nothing but a single
br element, it represents a placeholder blank line
(e.g. as in a template). Such blank lines must not be used for
presentation purposes.
4.5.4 The pre element4.5.4 pre 要素
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The pre element represents a block of preformatted
text, in which structure is represented by typographic conventions
rather than by elements.
In the HTML
serialization, a leading newline character
immediately following the pre element start tag is
stripped.
Some examples of cases where the pre element could
be used:
Including an e-mail, with paragraphs indicated by blank lines,
lists indicated by lines prefixed with a bullet, and so on.電子メイルを含める場合で、段落を改行で示したり、リストを行頭に丸印を付けることで示したりなどしている時。
Including fragments of computer code, with structure indicated
according to the conventions of that language.計算機符号の素片を含める場合で、その言語の規約に従って構造を示す時。
Displaying ASCII art.ASCII 絵を表示する場合。
To represent a block of computer code, the pre
element can be used with a code element; to represent a
block of computer output the pre element can be used
with a samp element. Similarly, the kbd
element can be used within a pre element to indicate
text that the user is to enter.
In the following snippet, a sample of computer code is
presented.
<p>This is the <code>Panel</code> constructor:</p>
<pre><code>function Panel(element, canClose, closeHandler) {
this.element = element;
this.canClose = canClose;
this.closeHandler = function () { if (closeHandler) closeHandler() };
}</code></pre>
In the following snippet, samp and kbd
elements are mixed in the contents of a pre element to
show a session of Zork I.
<pre><samp>You are in an open field west of a big white house with a boarded
front door.
There is a small mailbox here.
></samp> <kbd>open mailbox</kbd>
<samp>Opening the mailbox reveals:
A leaflet.
></samp></pre>
The following shows a contemporary poem that uses the
pre element to preserve its unusual formatting, which
forms an intrinsic part of the poem itself.
<pre> maxling
it is with a heart
heavy
that i admit loss of a feline
so loved
a friend lost to the
unknown
(night)
~cdr 11dec07</pre>
4.5.5 The dialog element4.5.5 dialog 要素
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Zero or more pairs of one
dt element followed by
one dd element.
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The dialog element represents a conversation.
Each part of the conversation must have an explicit talker (or
speaker) given by a dt element, and a discourse (or
quote) given by a dd element.
This example demonstrates this using an extract from Abbot and
Costello's famous sketch, Who's on first:
<dialog>
<dt> Costello
<dd> Look, you gotta first baseman?
<dt> Abbott
<dd> Certainly.
<dt> Costello
<dd> Who's playing first?
<dt> Abbott
<dd> That's right.
<dt> Costello
<dd> When you pay off the first baseman every month, who gets the money?
<dt> Abbott
<dd> Every dollar of it.
</dialog>
Text in a dt element in a
dialog element is implicitly the source of the text
given in the following dd element, and the contents of
the dd element are implicitly a quote from that
speaker. There is thus no need to include cite,
q, or blockquote elements in this
markup. Indeed, a q element inside a dd
element in a conversation would actually imply the people talking
were themselves quoting another work. See the cite,
q, and blockquote elements for other ways
to cite or quote.
4.5.6 The blockquote element4.5.6 blockquote 要素
- Categories分類
- Flow content.流れ内容。
- Sectioning root.章節付け根。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Flow content.流れ内容。
- Element-specific attributes:要素固有属性:
cite- DOM interface:DOM 界面:
-
interface HTMLQuoteElement : HTMLElement {
attribute DOMString cite;
};
The HTMLQuoteElement interface is
also used by the q element.
The blockquote element represents a section that is
quoted from another source.
Content inside a blockquote must be quoted from
another source, whose address, if it has one, should be cited in the
cite
attribute.
If the cite attribute
is present, it must be a valid URL. User agents should
allow users to follow such citation links.
The cite DOM
attribute must reflect the element's cite content attribute.
cite DOM 属性は element's cite 内容属性を反映しなければなりません。
The best way to represent a conversation is not with
the cite and blockquote elements, but with
the dialog element.
This next example shows the use of cite alongside
blockquote:
<p>His next piece was the aptly named <cite>Sonnet 130</cite>:</p>
<blockquote cite="http://quotes.example.org/s/sonnet130.html">
<p>My mistress' eyes are nothing like the sun,<br>
Coral is far more red, than her lips red,<br>
...
4.5.7 The ol element4.5.7 ol 要素
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Zero or more
li elements.0個以上の li 要素。
- Element-specific attributes:要素固有属性:
reversedstart- DOM interface:DOM 界面:
-
interface HTMLOListElement : HTMLElement {
attribute boolean reversed;
attribute long start;
};
The ol element represents a list of items, where the
items have been intentionally ordered, such that changing the order
would change the meaning of the document.
The items of the list are the li element child nodes
of the ol element, in tree order.
The reversed
attribute is a boolean attribute. If present, it
indicates that the list is a descending list (..., 3, 2, 1). If the
attribute is omitted, the list is an ascending list (1, 2, 3,
...).
The start
attribute, if present, must be a valid integer giving
the ordinal value of the first list item.
If the start attribute is
present, user agents must parse it as an integer, in order to determine the
attribute's value. The default value, used if the attribute is
missing or if the value cannot be converted to a number according to
the referenced algorithm, is 1 if the element has no reversed attribute, and is the
number of child li elements otherwise.
The first item in the list has the ordinal value given by the
ol element's start
attribute, unless that li element has a value attribute with a value that can
be successfully parsed, in which case it has the ordinal value given
by that value attribute.
Each subsequent item in the list has the ordinal value given by
its value attribute, if it has
one, or, if it doesn't, the ordinal value of the previous item, plus
one if the reversed is absent,
or minus one if it is present.
The reversed DOM
attribute must reflect the value of the reversed content attribute.reversed DOM 属性は reversed 内容属性の値を反映しなければなりません。
The start DOM
attribute must reflect the value of the start content attribute.start DOM 属性は start 内容属性の値を反映しなければなりません。
The following markup shows a list where the order matters, and
where the ol element is therefore appropriate. Compare
this list to the equivalent list in the ul section to
see an example of the same items using the ul
element.
<p>I have lived in the following countries (given in the order of when
I first lived there):</p>
<ol>
<li>Switzerland
<li>United Kingdom
<li>United States
<li>Norway
</ol>
Note how changing the order of the list changes the meaning of
the document. In the following example, changing the relative order
of the first two items has changed the birthplace of the
author:
<p>I have lived in the following countries (given in the order of when
I first lived there):</p>
<ol>
<li>United Kingdom
<li>Switzerland
<li>United States
<li>Norway
</ol>
4.5.8 The ul element4.5.8 ul 要素
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Zero or more
li elements.0個以上の li 要素。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The ul element represents a list of items, where the
order of the items is not important — that is, where changing
the order would not materially change the meaning of the
document.ul 湯素は、項目の並びを表します。
ただし、項目の順序は重要ではない、
つまり順序変更が実質的に文書の意味を変更しない並びを表します。
The items of the list are the li element child nodes
of the ul element.並び中の項目は、 ul 要素中の
li 要素である子供節点です。
The following markup shows a list where the order does not
matter, and where the ul element is therefore
appropriate. Compare this list to the equivalent list in the
ol section to see an example of the same items using
the ol element.次のマーク付けは、順序が重要ではないので
ul 要素が適切であるような並びを示しています。
この並びと、 ol の節にある、
同じ項目で ol 要素を使った同じような並びを比べてみてください。
<p>I have lived in the following countries:</p>
<ul>
<li>Norway
<li>Switzerland
<li>United Kingdom
<li>United States
</ul>
Note that changing the order of the list does not change the
meaning of the document. The items in the snippet above are given
in alphabetical order, but in the snippet below they are given in
order of the size of their current account balance in 2007, without
changing the meaning of the document whatsoever:並びの順序を変えても文書の意味が変わらないことに注意してください。
先の例の項目は逆五十音順でしたが、次の例は2007年の経常収支の大きさの順です。
しかし、文書の意味は変わっていません。
<p>I have lived in the following countries:</p>
<ul>
<li>Switzerland
<li>Norway
<li>United Kingdom
<li>United States
</ul>
4.5.9 The li element4.5.9 li 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Inside
ol elements.
- Inside
ul elements.
- Inside
menu elements.
- Content model:内容モデル:
Flow content.
- Element-specific attributes:要素固有属性:
- If the element is a child of an
ol element: value
- If the element is not the child of an
ol element: None.
- DOM interface:DOM 界面:
-
interface HTMLLIElement : HTMLElement {
attribute long value;
};
The li element represents a list item. If its parent
element is an ol, ul, or menu
element, then the element is an item of the parent element's list,
as defined for those elements. Otherwise, the list item has no
defined list-related relationship to any other li
element.
The value
attribute, if present, must be a valid integer giving
the ordinal value of the list item.
If the value attribute is
present, user agents must parse it as an integer, in order to determine the
attribute's value. If the attribute's value cannot be converted to a
number, the attribute must be treated as if it was absent. The
attribute has no default value.
The value attribute is
processed relative to the element's parent ol element
(q.v.), if there is one. If there is not, the attribute has no
effect.
The value DOM
attribute must reflect the value of the value content attribute.value DOM 属性は value 内容属性の値を反映しなければなりません。
The following example, the top ten movies are listed (in reverse
order). Note the way the list is given a title by using a
figure element and its legend.
<figure>
<legend>The top 10 movies of all time</legend>
<ol>
<li value="10"><cite>Josie and the Pussycats</cite>, 2001</li>
<li value="9"><cite lang="sh">Црна мачка, бели мачор</cite>, 1998</li>
<li value="8"><cite>A Bug's Life</cite>, 1998</li>
<li value="7"><cite>Toy Story</cite>, 1995</li>
<li value="6"><cite>Monsters, Inc</cite>, 2001</li>
<li value="5"><cite>Cars</cite>, 2006</li>
<li value="4"><cite>Toy Story 2</cite>, 1999</li>
<li value="3"><cite>Finding Nemo</cite>, 2003</li>
<li value="2"><cite>The Incredibles</cite>, 2004</li>
<li value="1"><cite>Ratatouille</cite>, 2007</li>
</ol>
</figure>
The markup could also be written as follows, using the reversed attribute on the
ol element:
<figure>
<legend>The top 10 movies of all time</legend>
<ol reversed>
<li><cite>Josie and the Pussycats</cite>, 2001</li>
<li><cite lang="sh">Црна мачка, бели мачор</cite>, 1998</li>
<li><cite>A Bug's Life</cite>, 1998</li>
<li><cite>Toy Story</cite>, 1995</li>
<li><cite>Monsters, Inc</cite>, 2001</li>
<li><cite>Cars</cite>, 2006</li>
<li><cite>Toy Story 2</cite>, 1999</li>
<li><cite>Finding Nemo</cite>, 2003</li>
<li><cite>The Incredibles</cite>, 2004</li>
<li><cite>Ratatouille</cite>, 2007</li>
</ol>
</figure>
If the li element is the child of a
menu element and itself has a child that defines a
command, then the
li element must match the :enabled and :disabled
pseudo-classes in the same way as the first such child element
does.
4.5.10 The dl element4.5.10 dl 要素
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Zero or more groups each consisting of one or more
dt elements followed by one or more dd
elements.
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The dl element introduces an association list
consisting of zero or more name-value groups (a description
list). Each group must consist of one or more names (dt
elements) followed by one or more values (dd
elements).
Name-value groups may be terms and definitions, metadata topics
and values, or any other groups of name-value data.名前と値の群は、用語と定義でも、メタデータの話題と値でも、その他の名前と値のデータの群でも構いません。
The values within a group are alternatives; multiple paragraphs
forming part of the same value must all be given within the same
dd element.
The order of the list of groups, and of the names and values
within each group, may be significant.
If a dl element is empty, it contains no groups.
If a dl element contains non-whitespace text nodes, or elements other than dt and
dd, then those elements or text
nodes do not form part of any groups in that
dl.
If a dl element contains only dt
elements, then it consists of one group with names but no
values.
If a dl element contains only dd
elements, then it consists of one group with values but no
names.
If a dl element starts with one or more
dd elements, then the first group has no associated
name.
If a dl element ends with one or more
dt elements, then the last group has no associated
value.
When a dl element doesn't match its
content model, it is often due to accidentally using dd
elements in the place of dt elements and vice
versa. Conformance checkers can spot such mistakes and might be able
to advise authors how to correctly use the markup.
In the following example, one entry ("Authors") is linked to two
values ("John" and "Luke").
<dl>
<dt> Authors
<dd> John
<dd> Luke
<dt> Editor
<dd> Frank
</dl>
In the following example, one definition is linked to two
terms.
<dl>
<dt lang="en-US"> <dfn>color</dfn> </dt>
<dt lang="en-GB"> <dfn>colour</dfn> </dt>
<dd> A sensation which (in humans) derives from the ability of
the fine structure of the eye to distinguish three differently
filtered analyses of a view. </dd>
</dl>
The following example illustrates the use of the dl
element to mark up metadata of sorts. At the end of the example,
one group has two metadata labels ("Authors" and "Editors") and two
values ("Robert Rothman" and "Daniel Jackson").
<dl>
<dt> Last modified time </dt>
<dd> 2004-12-23T23:33Z </dd>
<dt> Recommended update interval </dt>
<dd> 60s </dd>
<dt> Authors </dt>
<dt> Editors </dt>
<dd> Robert Rothman </dd>
<dd> Daniel Jackson </dd>
</dl>
The following example shows the dl element used to
give a set of instructions. The order of the instructions here is
important (in the other examples, the order of the blocks was not
important).
<p>Determine the victory points as follows (use the
first matching case):</p>
<dl>
<dt> If you have exactly five gold coins </dt>
<dd> You get five victory points </dd>
<dt> If you have one or more gold coins, and you have one or more silver coins </dt>
<dd> You get two victory points </dd>
<dt> If you have one or more silver coins </dt>
<dd> You get one victory point </dd>
<dt> Otherwise </dt>
<dd> You get no victory points </dd>
</dl>
The following snippet shows a dl element being used
as a glossary. Note the use of dfn to indicate the
word being defined.
<dl>
<dt><dfn>Apartment</dfn>, n.</dt>
<dd>An execution context grouping one or more threads with one or
more COM objects.</dd>
<dt><dfn>Flat</dfn>, n.</dt>
<dd>A deflated tire.</dd>
<dt><dfn>Home</dfn>, n.</dt>
<dd>The user's login directory.</dd>
</dl>
The dl element is inappropriate for
marking up dialogue, since dialogue is ordered (each speaker/line
pair comes after the next). For an example of how to mark up
dialogue, see the dialog element.
4.5.11 The dt element4.5.11 dt 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Before
dd or dt elements inside dl elements.dl 要素中の
dd 要素か dt 要素の前。
- Before a
dd element inside a dialog element.dialog 要素中の
dd 要素の前。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The dt element represents the term, or name, part of
a term-description group in a description list (dl
element), and the talker, or speaker, part of a talker-discourse
pair in a conversation (dialog element).dt 要素は、説明並び (dl 要素) 中の用語・説明の群の一部として、
用語や名前を表し、会話 (dialog 要素)
中の話者・談話の組の一部として、
話者を表します。
The dt element itself, when used in a
dl element, does not indicate that its contents are a
term being defined, but this can be indicated using the
dfn element.dt 要素自体は、
dl 要素中で用いられた場合にも、
その内容が定義される用語であると示してはいませんが、
dfn
要素を使ってそうであると示すことができます。
If the dt element is the child of a
dialog element, and it further contains a
time element, then that time element
represents a timestamp for when the associated discourse
(dd element) was said, and is not part of the name of
the talker.
The following extract shows how an IM conversation log could be
marked up.次の抜粋は、即席メッセージの会話記録をどうマーク付けできるかを示しています。
<dialog>
<dt> <time>14:22</time> egof
<dd> I'm not that nerdy, I've only seen 30% of the star trek episodes
<dt> <time>14:23</time> kaj
<dd> if you know what percentage of the star trek episodes you have seen, you are inarguably nerdy
<dt> <time>14:23</time> egof
<dd> it's unarguably
<dt> <time>14:24</time> kaj
<dd> you are not helping your case
</dialog>
4.5.12 The dd element4.5.12 dd 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- After
dt or dd elements inside dl elements.dl 要素中の
dt 要素か dd 要素の後。
- After a
dt element inside a dialog element.dialog 要素中の
dt
要素の後。
- Content model:内容モデル:
- Flow content.流れ内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The dd element represents the description,
definition, or value, part of a term-description group in a
description list (dl element), and the discourse, or
quote, part in a conversation (dialog element).dd 要素は、説明並び
(dl 要素) 中の用語・説明の群の一部として説明や定義や値を表し、
会話 (dialog 要素) の一部として談話や引用を表します。
A dl can be used to define a vocabulary list, like
in a dictionary. In the following example, each entry, given by a
dt with a dfn, has several
dds, showing the various parts of the definition.
<dl>
<dt><dfn>happiness</dfn></dt>
<dd class="pronunciation">/'hæ p. nes/</dd>
<dd class="part-of-speech"><i><abbr>n.</abbr></i></dd>
<dd>The state of being happy.</dd>
<dd>Good fortune; success. <q>Oh <b>happiness</b>! It worked!</q></dd>
<dt><dfn>rejoice</dfn></dt>
<dd class="pronunciation">/ri jois'/</dd>
<dd><i class="part-of-speech"><abbr>v.intr.</abbr></i> To be delighted oneself.</dd>
<dd><i class="part-of-speech"><abbr>v.tr.</abbr></i> To cause one to be delighted.</dd>
</dl>
4.6 Text-level semantics4.6 テキスト水準の意味
4.6.1 The a element4.6.1 a 要素
- Categories分類
- Interactive content.対話的内容。
- When the element only contains phrasing content: phrasing content.要素が語句付け内容を含む時:
語句付け内容。
- Otherwise: flow content.その他の場合: 流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Transparent, but there must be no interactive content descendant.
- Element-specific attributes:要素固有属性:
hreftargetpingrelmediahreflangtype- DOM interface:DOM 界面:
-
[Stringifies=href] interface HTMLAnchorElement : HTMLElement {
attribute DOMString href;
attribute DOMString target;
attribute DOMString ping;
attribute DOMString rel;
readonly attribute DOMTokenList relList;
attribute DOMString media;
attribute DOMString hreflang;
attribute DOMString type;
};
The Command interface must also be implemented by
this element.Command
界面もこの要素に実装しなければなりません。
If the a element has an href attribute, then it
represents a hyperlink.a 要素が href 属性を持つ場合、
ハイパーリンクを表します。
If the a element has no href attribute, then the element
is a placeholder for where a link might otherwise have been placed,
if it had been relevant.a 要素が href
属性を持たない場合、その要素は、もし関係があったとするとリンクが置かれていたであろう場所に場所持ち子です。
The target, ping, rel, media, hreflang, and type attributes must be omitted
if the href attribute is
not present.
If a site uses a consistent navigation toolbar on every page,
then the link that would normally link to the page itself could be
marked up using an a element:あるサイトが各頁で共通の誘導ツールバーを用いている場合、
通常はその頁自体にリンクしているリンクは a
要素を用いてマーク付けすることができます。
<nav>
<ul>
<li> <a href="/">Home</a> </li>
<li> <a href="/news">News</a> </li>
<li> <a>Examples</a> </li>
<li> <a href="/legal">Legal</a> </li>
</ul>
</nav>
Interactive user agents should allow users to follow hyperlinks created using
the a element. The href, target and ping attributes decide how the
link is followed. The rel,
media, hreflang, and type attributes may be used to
indicate to the user the likely nature of the target resource before
the user follows the link.
The activation behavior of a elements
that represent hyperlinks is to run the following
steps:ハイパーリンクを表す a 要素の活性化動作は、
次の段階を動作させることです。
If the DOMActivate
event in question is not trusted (i.e. a click() method call was the reason for the
event being dispatched), and the a element's target attribute is ... then raise an
INVALID_ACCESS_ERR exception and abort these
steps.
If the target of the click
event is an img element with an ismap attribute specified, then
server-side image map processing must be performed, as follows:
If the DOMActivate
event was dispatched as the result of a real
pointing-device-triggered click
event on the img element, then let x be the distance in CSS pixels from the left edge
of the image's left border, if it has one, or the left edge of
the image otherwise, to the location of the click, and let y be the distance in CSS pixels from the top edge
of the image's top border, if it has one, or the top edge of the
image otherwise, to the location of the click. Otherwise, let
x and y be zero.
Let the hyperlink suffix be a U+003F
QUESTION MARK character, the value of x
expressed as a base-ten integer using ASCII digits (U+0030 DIGIT
ZERO to U+0039 DIGIT NINE), a U+002C COMMA character, and the
value of y expressed as a base-ten integer
using ASCII digits.ハイパーリンク接尾辞を
U+003F QUESTION MARK
文字、 x の値の ASCII 数字 (U+0030 DIGIT ZERO
から U+0039 DIGIT NINE) を使った十進整数表現、 U+002C COMMA
文字、 y の値の ASCII 数字を使った十進整数表現とします。
Finally, the user agent must follow the hyperlink defined by the
a element. If the steps above defined a hyperlink
suffix, then take that into account when following the
hyperlink.最後に、利用者エージェントは a 要素で定義されるハイパーリンクをたどらなければなりません。
先の段階がハイパーリンク接尾辞を定義している場合、
これをハイパーリンクをたどる時に考慮に入れます。
The DOM attributes href, ping, target, rel, media, hreflang, and type, must
reflect the respective content attributes of the same
name.
The DOM attribute relList must
reflect the rel
content attribute.DOM 属性 relList は rel 内容属性を反映しなければなりません。
The a element may be wrapped around entire
paragraphs, lists, tables, and so forth, even entire sections, so
long as there is no interactive content within (e.g. buttons or
other links). This example shows how this can be used to make an
entire advertising block into a link:
<aside class="advertising">
<h1>Advertising</h1>
<a href="http://ad.example.com/?adid=1929&pubid=1422">
<section>
<h1>Mellblomatic 9000!</h1>
<p>Turn all your widgets into mellbloms!</p>
<p>Only $9.99 plus shipping and handling.</p>
</section>
</a>
<a href="http://ad.example.com/?adid=375&pubid=1422">
<section>
<h1>The Mellblom Browser</h1>
<p>Web browsing at the speed of light.</p>
<p>No other browser goes faster!</p>
</section>
</a>
</aside>
4.6.2 The q element4.6.2 q 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
cite- DOM interface:DOM 界面:
-
The
q element uses the HTMLQuoteElement interface.
q element uses the HTMLQuoteElement 界面。
The q element represents some phrasing content quoted from another source.
Quotation punctuation (such as quotation marks) must not appear
immediately before, after, or inside q elements; they
will be inserted into the rendering by the user agent.
Content inside a q element must be quoted from
another source, whose address, if it has one, should be cited in the
cite attribute. The
source may be fictional, as when quoting characters in a novel or
screenplay.
If the cite attribute is
present, it must be a valid URL. User agents should
allow users to follow such citation links.
The q element must not be used in place of quotation
marks that do not represent quotes; for example, it is inappropriate
to use the q element for marking up sarcastic
statements.
The use of q elements to mark up quotations is
entirely optional; using explicit quotation punctuation without
q elements is just as correct.
Here is a simple example of the use of the q
element:
<p>The man said <q>Things that are impossible just take
longer</q>. I disagreed with him.</p>
Here is an example with both an explicit citation link in the
q element, and an explicit citation outside:
<p>The W3C page <cite>About W3C</cite> says the W3C's
mission is <q cite="http://www.w3.org/Consortium/">To lead the
World Wide Web to its full potential by developing protocols and
guidelines that ensure long-term growth for the Web</q>. I
disagree with this mission.</p>
In the following example, the quotation itself contains a
quotation:次の例では、引用自体が引用を含んでいます。
<p>In <cite>Example One</cite>, he writes <q>The man
said <q>Things that are impossible just take longer</q>. I
disagreed with him</q>. Well, I disagree even more!</p>
In the following example, quotation marks are used instead of
the q element:
<p>His best argument was ❝I disagree❞, which
I thought was laughable.</p>
In the following example, there is no quote — the
quotation marks are used to name a word. Use of the q
element in this case would be inappropriate.
<p>The word "ineffable" could have been used to describe the disaster
resulting from the campaign's mismanagement.</p>
4.6.3 The cite element4.6.3 cite 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The cite element represents the title of a work
(e.g.
a book,
a paper,
an essay,
a poem,
a score,
a song,
a script,
a film,
a TV show,
a game,
a sculpture,
a painting,
a theatre production,
a play,
an opera,
a musical,
an exhibition,
etc). This can be a work that is being quoted or
referenced in detail (i.e. a citation), or it can just be a work
that is mentioned in passing.
A person's name is not the title of a work — even if people
call that person a piece of work — and the element must
therefore not be used to mark up people's names. (In some cases, the
b element might be appropriate for names; e.g. in a
gossip article where the names of famous people are keywords
rendered with a different style to draw attention to them. In other
cases, if an element is really needed, the
span element can be used.)
A ship is similarly not a work, and the element must not be used
to mark up ship names (the i element can be used for
that purpose).
This next example shows a typical use of the cite
element:
<p>My favourite book is <cite>The Reality Dysfunction</cite> by
Peter F. Hamilton. My favourite comic is <cite>Pearls Before
Swine</cite> by Stephan Pastis. My favourite track is <cite>Jive
Samba</cite> by the Cannonball Adderley Sextet.</p>
This is correct usage:これは正しい用例です。
<p>According to the Wikipedia article <cite>HTML</cite>, as it
stood in mid-February 2008, leaving attribute values unquoted is
unsafe. This is obviously an over-simplification.</p>
The following, however, is incorrect usage, as the
cite element here is containing far more than the
title of the work:
<!-- do not copy this example, it is an example of bad usage! -->
<p>According to <cite>the Wikipedia article on HTML</cite>, as it
stood in mid-February 2008, leaving attribute values unquoted is
unsafe. This is obviously an over-simplification.</p>
The cite element is obviously a key part of any
citation in a bibliography, but it is only used to mark the
title:
<p><cite>Universal Declaration of Human Rights</cite>, United Nations,
December 1948. Adopted by General Assembly resolution 217 A (III).</p>
A citation is not a quote (for
which the q element is appropriate).
This is incorrect usage, because cite is not for
quotes:
<p><cite>This is wrong!</cite>, said Ian.</p>
This is also incorrect usage, because a person is not a
work:これも誤った用例で、人は作品ではありません。
<p><q>This is still wrong!</q>, said <cite>Ian</cite>.</p>
The correct usage does not use a cite element:
<p><q>This is correct</q>, said Ian.</p>
As mentioned above, the b element might be relevant
for marking names as being keywords in certain kinds of
documents:
<p>And then <b>Ian</b> said <q>this might be right, in a
gossip column, maybe!</q>.</p>
4.6.4 The em element4.6.4 em 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The em element represents stress emphasis of its
contents.
The level of emphasis that a particular piece of content has is
given by its number of ancestor em elements.
The placement of emphasis changes the meaning of the sentence.
The element thus forms an integral part of the content. The precise
way in which emphasis is used in this way depends on the
language.
These examples show how changing the emphasis changes the
meaning. First, a general statement of fact, with no emphasis:
<p>Cats are cute animals.</p>
By emphasizing the first word, the statement implies that the
kind of animal under discussion is in question (maybe someone is
asserting that dogs are cute):
<p><em>Cats</em> are cute animals.</p>
Moving the emphasis to the verb, one highlights that the truth
of the entire sentence is in question (maybe someone is saying cats
are not cute):
<p>Cats <em>are</em> cute animals.</p>
By moving it to the adjective, the exact nature of the cats
is reasserted (maybe someone suggested cats were mean
animals):
<p>Cats are <em>cute</em> animals.</p>
Similarly, if someone asserted that cats were vegetables,
someone correcting this might emphasize the last word:
<p>Cats are cute <em>animals</em>.</p>
By emphasizing the entire sentence, it becomes clear that the
speaker is fighting hard to get the point across. This kind of
emphasis also typically affects the punctuation, hence the
exclamation mark here.
<p><em>Cats are cute animals!</em></p>
Anger mixed with emphasizing the cuteness could lead to markup
such as:
<p><em>Cats are <em>cute</em> animals!</em></p>
4.6.5 The strong element4.6.5 strong 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The strong element represents strong importance for
its contents.
The relative level of importance of a piece of content is given
by its number of ancestor strong elements; each
strong element increases the importance of its
contents.
Changing the importance of a piece of text with the
strong element does not change the meaning of the
sentence.
Here is an example of a warning notice in a game, with the
various parts marked up according to how important they are:これはゲーム中の警告書きの例で、その中の各部分が重要度によってマーク付けされています。
<p><strong>Warning.</strong> This dungeon is dangerous.
<strong>Avoid the ducks.</strong> Take any gold you find.
<strong><strong>Do not take any of the diamonds</strong>,
they are explosive and <strong>will destroy anything within
ten meters.</strong></strong> You have been warned.</p>
4.6.6 The small element4.6.6 small 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The small element represents small print (part of a
document often describing legal restrictions, such as copyrights or
other disadvantages), or other side comments.
The small element does not
"de-emphasize" or lower the importance of text emphasised by the
em element or marked as important with the
strong element.
In this example the footer contains contact information and a
copyright.この例では、尾部に連絡先と著作権が記されています。
<footer>
<address>
For more details, contact
<a href="mailto:js@example.com">John Smith</a>.
</address>
<p><small>© copyright 2038 Example Corp.</small></p>
</footer>
In this second example, the small element is used
for a side comment.
<p>Example Corp today announced record profits for the
second quarter <small>(Full Disclosure: Foo News is a subsidiary of
Example Corp)</small>, leading to speculation about a third quarter
merger with Demo Group.</p>
In this last example, the small element is marked
as being important small print.
<p><strong><small>Continued use of this service will result in a kiss.</small></strong></p>
4.6.7 The mark element4.6.7 mark 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The mark element represents a run of text in one
document marked or highlighted for reference purposes, due to its
relevance in another context. When used in a quotation or other
block of text referred to from the prose, it indicates a highlight
that was not originally present but which has been added to bring
the reader's attention to a part of the text that might not have
been considered important by the original author when the block was
originally written, but which is now under previously unexpected
scrutiny. When used in the main prose of a document, it indicates a
part of the document that has been highlighted due to its likely
relevance to the user's current activity.
The rendering section will eventually suggest
that user agents provide a way to let users jump between
mark elements. Suggested rendering is a neon yellow
background highlight, though UAs maybe should allow this to be
toggled.
This example shows how the mark example can be used
to bring attention to a particular part of a quotation:
<p lang="en-US">Consider the following quote:</p>
<blockquote lang="en-GB">
<p>Look around and you will find, no-one's really
<mark>colour</mark> blind.</p>
</blockquote>
<p lang="en-US">As we can tell from the <em>spelling</em> of the word,
the person writing this quote is clearly not American.</p>
Another example of the mark element is highlighting
parts of a document that are matching some search string. If
someone looked at a document, and the server knew that the user was
searching for the word "kitten", then the server might return the
document with one paragraph modified as follows:
<p>I also have some <mark>kitten</mark>s who are visiting me
these days. They're really cute. I think they like my garden! Maybe I
should adopt a <mark>kitten</mark>.</p>
In the following snippet, a paragraph of text refers to a
specific part of a code fragment.
<p>The highlighted part below is where the error lies:</p>
<pre><code>var i: Integer;
begin
i := <mark>1.1</mark>;
end.</code></pre>
This is another example showing the use of mark to
highlight a part of quoted text that was originally not
emphasised. In this example, common typographic conventions have
led the author to explicitly style mark elements in
quotes to render in italics.
<article>
<style>
blockquote mark, q mark {
font: inherit; font-style: italic;
text-decoration: none;
background: transparent; color: inherit;
}
.bubble em {
font: inherit; font-size: larger;
text-decoration: underline;
}
</style>
<h1>She knew</h1>
<p>Did you notice the subtle joke in the joke on panel 4?</p>
<blockquote>
<p class="bubble">I didn't <em>want</em> to believe. <mark>Of course
on some level I realized it was a known-plaintext attack.</mark> But I
couldn't admit it until I saw for myself.</p>
</blockquote>
<p>(Emphasis mine.) I thought that was great. It's so pedantic, yet it
explains everything neatly.</p>
</article>
Note, incidentally, the distinction between the em
element in this example, which is part of the original text being
quoted, and the mark element, which is highlighting a
part for comment.
The following example shows the difference between denoting the
importance of a span of text (strong) as
opposed to denoting the relevance of a span of text
(mark). It is an extract from a textbook, where the
extract has had the parts relevant to the exam highlighted. The
safety warnings, important though they may be, are apparently not
relevant to the exam.
<h3>Wormhole Physics Introduction</h3>
<p><mark>A wormhole in normal conditions can be held open for a
maximum of just under 39 minutes.</mark> Conditions that can increase
the time include a powerful energy source coupled to one or both of
the gates connecting the wormhole, and a large gravity well (such as a
black hole).</p>
<p><mark>Momentum is preserved across the wormhole. Electromagnetic
radiation can travel in both directions through a wormhole,
but matter cannot.</mark></p>
<p>When a wormhole is created, a vortex normally forms.
<strong>Warning: The vortex caused by the wormhole opening will
annihilate anything in its path.</strong> Vortexes can be avoided when
using sufficiently advanced dialing technology.</p>
<p><mark>An obstruction in a gate will prevent it from accepting a
wormhole connection.</mark></p>
4.6.8 The dfn element4.6.8 dfn 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content, but there must be no descendant
dfn elements.
- Element-specific attributes:要素固有属性:
- None, but the
title attribute has special semantics on this element.
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The dfn element represents the defining instance of
a term. The paragraph, description list group, or section that is the nearest ancestor of the
dfn element must also contain the definition(s) for the
term given by the
dfn element.
Defining term: If the dfn element has a
title attribute, then
the exact value of that attribute is the term being defined.
Otherwise, if it contains exactly one element child node and no
child text nodes, and that child
element is an abbr element with a title attribute, then the exact value
of that attribute is the term being defined. Otherwise, it
is the exact textContent of the dfn
element that gives the term being defined.
If the title attribute of the
dfn element is present, then it must contain only the
term being defined.
The title attribute
of ancestor elements does not affect dfn elements.
An a element that links to a dfn
element represents an instance of the term defined by the
dfn element.
In the following fragment, the term "GDO" is first defined in
the first paragraph, then used in the second.次の素片では、用語「GDO」を最初の段落で定義して、2つ目の段落で使用しています。
<p>The <dfn><abbr title="Garage Door Opener">GDO</abbr></dfn>
is a device that allows off-world teams to open the iris.</p>
<!-- ... later in the document: -->
<p>Teal'c activated his <abbr title="Garage Door Opener">GDO</abbr>
and so Hammond ordered the iris to be opened.</p>
With the addition of an a element, the reference
can be made explicit:
<p>The <dfn id=gdo><abbr title="Garage Door Opener">GDO</abbr></dfn>
is a device that allows off-world teams to open the iris.</p>
<!-- ... later in the document: -->
<p>Teal'c activated his <a href=#gdo><abbr title="Garage Door Opener">GDO</abbr></a>
and so Hammond ordered the iris to be opened.</p>
4.6.9 The abbr element4.6.9 abbr 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None, but the
title attribute has special semantics on this element.
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The abbr element represents an abbreviation or
acronym, optionally with its expansion. The title attribute may be
used to provide an expansion of the abbreviation. The attribute, if
specified, must contain an expansion of the abbreviation, and
nothing else.
The paragraph below contains an abbreviation marked up with the
abbr element. This paragraph defines the term "Web Hypertext Application Technology
Working Group".
<p>The <dfn id=whatwg><abbr title="Web Hypertext Application
Technology Working Group">WHATWG</abbr></dfn> is a loose
unofficial collaboration of Web browser manufacturers and interested
parties who wish to develop new technologies designed to allow authors
to write and deploy Applications over the World Wide Web.</p>
An alternative way to write this would be:
<p>The <dfn id=whatwg>Web Hypertext Application Technology
Working Group</dfn> (<abbr title="Web Hypertext Application
Technology Working Group">WHATWG</abbr>) is a loose unofficial
collaboration of Web browser manufacturers and interested parties who
wish to develop new technologies designed to allow authors to write
and deploy Applications over the World Wide Web.</p>
This paragraph has two abbreviations. Notice how only one is
defined; the other, with no expansion associated with it, does not
use the abbr element.
<p>The <abbr title="Web Hypertext Application Technology Working
Group">WHATWG</abbr> started working on HTML5 in 2004.</p>
This paragraph links an abbreviation to its definition.
<p>The <a href="#whatwg"><abbr title="Web Hypertext Application
Technology Working Group">WHATWG</abbr></a> community does not
have much representation from Asia.</p>
This paragraph marks up an abbreviation without giving an
expansion, possibly as a hook to apply styles for abbreviations
(e.g. smallcaps).
<p>Philip` and Dashiva both denied that they were going to
get the issue counts from past revisions of the specification to
backfill the <abbr>WHATWG</abbr> issue graph.</p>
If an abbreviation is pluralized, the expansion's grammatical
number (plural vs singular) must match the grammatical number of the
contents of the element.省略形が複数形の場合は、展開形の文法的な数 (複数か単数か)
は要素の内容の文法的な数と一致しなければなりません。
Here the plural is outside the element, so the expansion is in
the singular:次の例では要素の外側で複数形になっていますから、展開形は単数形です。
<p>Two <abbr title="Working Group">WG</abbr>s worked on
this specification: the <abbr>WHATWG</abbr> and the
<abbr>HTMLWG</abbr>.</p>
Here the plural is inside the element, so the expansion is in
the plural:次の例では要素の内側で複数形になっていますから、展開形は複数形です。
<p>Two <abbr title="Working Groups">WGs</abbr> worked on
this specification: the <abbr>WHATWG</abbr> and the
<abbr>HTMLWG</abbr>.</p>
Abbreviations do not have to be marked up using this element. It
is expected to be useful in the following cases:
Abbreviations for which the author wants to give expansions,
where using the abbr element with a title attribute is an alternative to
including the expansion inline (e.g. in parentheses).
Abbreviations that are likely to be unfamiliar to the
document's readers, for which authors are encouraged to either mark
up the abbreviation using a abbr element with a title attribute or include the expansion
inline in the text the first time the abbreviation is used.
Abbreviations whose presence needs to be semantically
annotated, e.g. so that they can be identified from a style sheet
and given specific styles, for which the abbr element
can be used without a title
attribute.
Providing an expansion in a title attribute once will not necessarily
cause other abbr elements in the same document with the
same contents but without a title
attribute to behave as if they had the same expansion. Every
abbr element is independent.
4.6.10 The time element4.6.10 time 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
datetime- DOM interface:DOM 界面:
-
interface HTMLTimeElement : HTMLElement {
attribute DOMString dateTime;
readonly attribute DOMTimeStamp date;
readonly attribute DOMTimeStamp time;
readonly attribute DOMTimeStamp timezone;
};
The time element represents a precise date and/or a
time in the proleptic Gregorian calendar. [GREGORIAN]
The datetime
attribute, if present, must contain a valid date or time
string that identifies the date or time being specified.
If the datetime attribute
is not present, then the date or time must be specified in the
content of the element, such that the element's
textContent is a valid date or time string in
content.
The dateTime DOM
attribute must reflect the datetime content attribute.dateTime DOM 属性は datetime 内容属性を反映しなければなりません。
User agents, to obtain the date, time, and timezone represented by a
time element, must follow these steps:
If the datetime
attribute is present, then use the rules to parse a date or
time string with the flag in attribute from the value
of that attribute, and let the result be result.
Otherwise, use the rules to parse a date or time
string with the flag in content from the element's
textContent, and let the result be result.
If result is empty (because the parsing
failed), then the date is
unknown, the time is unknown,
and the timezone is
unknown.
Otherwise: if result contains a date, then
that is the date; if result contains a time, then that is the time; and if result contains a timezone, then the timezone is the
element's timezone. (A
timezone can only be present if both a date and a time are also
present.)
The date DOM
attribute must return null if the date is unknown, and otherwise must
return the time corresponding to midnight UTC (i.e. the first
second) of the given date.
The time DOM attribute
must return null if the time is
unknown, and otherwise must return the time corresponding to the
given time of 1970-01-01, with
the timezone UTC.
The timezone DOM
attribute must return null if the timezone is unknown, and otherwise
must return the time corresponding to 1970-01-01 00:00 UTC in the
given timezone, with the
timezone set to UTC (i.e. the time corresponding to 1970-01-01 at
00:00 UTC plus the offset corresponding to the timezone).
In the following snippet:
<p>Our first date was <time datetime="2006-09-23">a Saturday</time>.</p>
...the time element's date attribute would have the value
1,158,969,600,000ms, and the time
and timezone attributes would
return null.
In the following snippet:
<p>We stopped talking at <time datetime="2006-09-24T05:00-07:00">5am the next morning</time>.</p>
...the time element's date attribute would have the value
1,159,056,000,000ms, the time
attribute would have the value 18,000,000ms, and the timezone attribute would return
−25,200,000ms. To obtain the actual time, the three attributes can
be added together, obtaining 1,159,048,800,000, which is the
specified date and time in UTC.
Finally, in the following snippet:
<p>Many people get up at <time>08:00</time>.</p>
...the time element's date attribute would have the value null,
the time attribute would have the
value 28,800,000ms, and the timezone attribute would return
null.
The time element is not intended for
encoding times for which a precise date or time cannot be
established. For example, it would be inappropriate for encoding
times like "one millisecond after the big bang", "the early part of
the Jurassic period", or "a winter around 250 BCE".
4.6.11 The progress element4.6.11 progress 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
valuemax- DOM interface:DOM 界面:
-
interface HTMLProgressElement : HTMLElement {
attribute float value;
attribute float max;
readonly attribute float position;
};
The progress element represents the completion
progress of a task. The progress is either indeterminate, indicating
that progress is being made but that it is not clear how much more
work remains to be done before the task is complete (e.g. because
the task is waiting for a remote host to respond), or the progress
is a number in the range zero to a maximum, giving the fraction of
work that has so far been completed.
There are two attributes that determine the current task
completion represented by the element.
The value
attribute specifies how much of the task has been completed, and the
max attribute
specifies how much work the task requires in total. The units are
arbitrary and not specified.
Instead of using the attributes, authors are recommended to
include the current value and the maximum value inline as text
inside the element.
Here is a snippet of a Web application that shows the progress
of some automated task:
<section>
<h2>Task Progress</h2>
<p>Progress: <progress><span id="p">0</span>%</progress></p>
<script>
var progressBar = document.getElementById('p');
function updateProgress(newValue) {
progressBar.textContent = newValue;
}
</script>
</section>
(The updateProgress() method in this example would
be called by some other code on the page to update the actual
progress bar as the task progressed.)
Author requirements: The max and value attributes, when present,
must have values that are valid floating point numbers. The max attribute, if present, must
have a value greater than zero. The value attribute, if present, must
have a value equal to or greater than zero, and less than or equal
to the value of the max
attribute, if present, or 1, otherwise.
The progress element is the wrong
element to use for something that is just a gauge, as opposed to
task progress. For instance, indicating disk space usage using
progress would be inappropriate. Instead, the
meter element is available for such use cases.
User agent requirements: User agents must parse
the max and value attributes' values
according to the rules for parsing floating point number
values.
If the value attribute
is omitted, then user agents must also parse the
textContent of the progress element in
question using the steps for finding one or two numbers of a
ratio in a string. These steps will return nothing, one
number, one number with a denominator punctuation character, or two
numbers.
Using the results of this processing, user agents must determine
whether the progress bar is an indeterminate progress bar, or
whether it is a determinate progress bar, and in the latter case,
what its current and maximum values are, all as follows:
If the max attribute is
omitted, and the value is
omitted, and the results of parsing the textContent
was nothing, then the progress bar is an indeterminate progress
bar. Abort these steps.
Otherwise, it is a determinate progress bar.そうでない場合、これは決定的進捗バーです。
If the max attribute is
included, then, if a value could be parsed out of it, then the
maximum value is that value.
Otherwise, if the max
attribute is absent but the value attribute is present, or,
if the max attribute is
present but no value could be parsed from it, then the maximum is
1.
Otherwise, if neither attribute is included, then, if the
textContent contained one number with an associated
denominator punctuation character, then the maximum value is the
value associated with that denominator punctuation
character; otherwise, if the textContent
contained two numbers, the maximum value is the higher of the two
values; otherwise, the maximum value is 1.
If the value attribute
is present on the element and a value could be parsed out of it,
that value is the current value of the progress bar. Otherwise, if
the attribute is present but no value could be parsed from it, the
current value is zero.
Otherwise if the value
attribute is absent and the max attribute is present, then, if
the textContent was parsed and found to contain just
one number, with no associated denominator punctuation character,
then the current value is that number. Otherwise, if the value attribute is absent and
the max attribute is present
then the current value is zero.
Otherwise, if neither attribute is present, then the current
value is the lower of the one or two numbers that were found in the
textContent of the element.
If the maximum value is less than or equal to zero, then it is
reset to 1.最大値が零以下の場合、 1 に再設定します。
If the current value is less than zero, then it is reset to
zero.現在値が零以下の場合、零に再設定します。
Finally, if the current value is greater than the maximum
value, then the current value is reset to the maximum value.最後に、現在値が最大値より大きい場合、現在値を最大値に再設定します。
UA requirements for showing the progress bar:
When representing a progress element to the user, the
UA should indicate whether it is a determinate or indeterminate
progress bar, and in the former case, should indicate the relative
position of the current value relative to the maximum value.
The max and value DOM attributes
must reflect the respective content attributes of the
same name. When the relevant content attributes are absent, the DOM
attributes must return zero. The value parsed from the
textContent never affects the DOM values.
Would be cool to have the value DOM attribute update the
textContent in-line...
If the progress bar is an indeterminate progress bar, then the
position DOM
attribute must return −1. Otherwise, it must return the result of
dividing the current value by the maximum value.
4.6.12 The meter element4.6.12 meter 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
valueminlowhighmaxoptimum- DOM interface:DOM 界面:
-
interface HTMLMeterElement : HTMLElement {
attribute float value;
attribute float min;
attribute float max;
attribute float low;
attribute float high;
attribute float optimum;
};
The meter element represents a scalar measurement
within a known range, or a fractional value; for example disk usage,
the relevance of a query result, or the fraction of a voting
population to have selected a particular candidate.
This is also known as a gauge.
The meter element should not be used to
indicate progress (as in a progress bar). For that role, HTML
provides a separate progress element.
The meter element also does not
represent a scalar value of arbitrary range — for example, it
would be wrong to use this to report a weight, or height, unless
there is a known maximum value.
There are six attributes that determine the semantics of the
gauge represented by the element.
The min attribute
specifies the lower bound of the range, and the max attribute specifies
the upper bound. The value attribute
specifies the value to have the gauge indicate as the "measured"
value.
The other three attributes can be used to segment the gauge's
range into "low", "medium", and "high" parts, and to indicate which
part of the gauge is the "optimum" part. The low attribute specifies
the range that is considered to be the "low" part, and the high attribute specifies
the range that is considered to be the "high" part. The optimum attribute
gives the position that is "optimum"; if that is higher than the
"high" value then this indicates that the higher the value, the
better; if it's lower than the "low" mark then it indicates that
lower values are better, and naturally if it is in between then it
indicates that neither high nor low values are good.
Authoring requirements: The recommended way of
giving the value is to include it as contents of the element, either
as two numbers (the higher number represents the maximum, the other
number the current value, and the minimum is assumed to be zero), or
as a percentage or similar (using one of the characters such as
"%"), or as a fraction. However, it is also possible to use the
attributes to specify these values.
One of the following conditions, along with all the requirements
that are listed with that condition, must be met:
- There are exactly two numbers in the contents of the element,
and the
value, min, and max attributes are all omitted
-
If specified, the low,
high, and optimum attributes must have
values greater than or equal to zero and less than or equal to the
bigger of the two numbers in the contents of the element.
If both the low and high attributes are specified, then
the low attribute's value must
be less than or equal to the value of the high attribute.
- There is exactly one number followed by zero or more
White_Space characters and a valid denominator
punctuation character in the contents of the element, and
the
value, min, and max attributes are all omitted
-
If specified, the low,
high, and optimum attributes must have
values greater than or equal to zero and less than or equal to the
value associated with the denominator punctuation
character.
If both the low and high attributes are specified, then
the low attribute's value must
be less than or equal to the value of the high attribute.
- There is exactly one number in the contents of the element, and
the
value attribute is
omitted
- There are no numbers in the contents of the element, and the
value attribute is
specified
-
If the min attribute
attribute is specified, then the minimum is
that attribue's value; otherwise, it is 0.
If the max attribute
attribute is specified, then the maximum is
that attribue's value; otherwise, it is 1.
If there is exactly one number in the contents of the element,
then value is that number; otherwise, value is the value of the value attribute.
The following inequalities must hold, as applicable:
minimum ≤ value ≤ maximum
minimum ≤ low ≤ maximum (if low is specified)
minimum ≤ high ≤ maximum (if high is specified)
minimum ≤ optimum ≤ maximum (if optimum is specified)
If both the low and high attributes are specified, then
the low attribute's value must
be less than or equal to the value of the high attribute.
For the purposes of these requirements, a number is a sequence of
characters in the range U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE
(9), optionally including with a single U+002E FULL STOP character
(.), and separated from other numbers by at least one character that
isn't any of those; interpreted as a base ten number.
The value, min, low, high, max, and optimum attributes, when present,
must have values that are valid floating point numbers.
If no minimum or maximum is specified, then the
range is assumed to be 0..1, and the value thus has to be within
that range.
The following examples all represent a measurement of three
quarters (of the maximum of whatever is being measured):
<meter>75%</meter>
<meter>750‰</meter>
<meter>3/4</meter>
<meter>6 blocks used (out of 8 total)</meter>
<meter>max: 100; current: 75</meter>
<meter><object data="graph75.png">0.75</object></meter>
<meter min="0" max="100" value="75"></meter>
The following example is incorrect use of the element, because
it doesn't give a range (and since the default maximum is 1, both
of the gauges would end up looking maxed out):
<p>The grapefruit pie had a radius of <meter>12cm</meter>
and a height of <meter>2cm</meter>.</p> <!-- BAD! -->
Instead, one would either not include the meter element, or use
the meter element with a defined range to give the dimensions in
context compared to other pies:
<p>The grapefruit pie had a radius of 12cm and a height of
2cm.</p>
<dl>
<dt>Radius: <dd> <meter min=0 max=20 value=12>12cm</meter>
<dt>Height: <dd> <meter min=0 max=10 value=2>2cm</meter>
</dl>
There is no explicit way to specify units in the
meter element, but the units may be specified in the
title attribute in free-form text.
The example above could be extended to mention the units:
<dl>
<dt>Radius: <dd> <meter min=0 max=20 value=12 title="centimeters">12cm</meter>
<dt>Height: <dd> <meter min=0 max=10 value=2 title="centimeters">2cm</meter>
</dl>
User agent requirements: User agents must parse
the min, max, value, low, high, and optimum attributes using the
rules for parsing floating point number values.
If the value attribute has
been omitted, the user agent must also process the
textContent of the element according to the steps
for finding one or two numbers of a ratio in a string. These
steps will return nothing, one number, one number with a denominator
punctuation character, or two numbers.
User agents must then use all these numbers to obtain values for
six points on the gauge, as follows. (The order in which these are
evaluated is important, as some of the values refer to earlier
ones.)利用者エージェントは、その後、これらすべての数を、
計器の6点の値を得るために次のように使わなければなりません。
(これらが評価される順序は重要です。ある値が前の値を参照していたりします。)
- The minimum value最小値
-
If the min attribute is
specified and a value could be parsed out of it, then the minimum
value is that value. Otherwise, the minimum value is zero.
- The maximum value最大値
-
If the max attribute is
specified and a value could be parsed out of it, the maximum
value is that value.
Otherwise, if the max
attribute is specified but no value could be parsed out of it, or
if it was not specified, but either or both of the min or value attributes were
specified, then the maximum value is 1.
Otherwise, none of the max,
min, and value attributes were
specified. If the result of processing the
textContent of the element was either nothing or just
one number with no denominator punctuation character, then the
maximum value is 1; if the result was one number but it had an
associated denominator punctuation character, then the maximum
value is the value associated with that denominator
punctuation character; and finally, if there were two
numbers parsed out of the textContent, then the
maximum is the higher of those two numbers.
If the above machinations result in a maximum value less than
the minimum value, then the maximum value is actually the same as
the minimum value.
- The actual value実際値
-
If the value attribute is
specified and a value could be parsed out of it, then that value
is the actual value.value
属性が指定されており、その値を構文解析して得ることができる場合、
その値が実際値となります。
If the value attribute is
not specified but the max
attribute is specified and the result of processing the
textContent of the element was one number with no
associated denominator punctuation character, then that number is
the actual value.
If neither of the value
and max attributes are
specified, then, if the result of processing the
textContent of the element was one number (with or
without an associated denominator punctuation character), then
that is the actual value, and if the result of processing the
textContent of the element was two numbers, then the
actual value is the lower of the two numbers found.
Otherwise, if none of the above apply, the actual value is
zero.そうでない場合、前記のいずれも適用されない場合、
実際値は零です。
If the above procedure results in an actual value less than
the minimum value, then the actual value is actually the same as
the minimum value.前記の手続きの結果実際値が最小値より小さくなる場合、
実際値は実際には最小値と同じ値です。
If, on the other hand, the result is an actual value greater
than the maximum value, then the actual value is the maximum
value.一方、結果として実際値が最大値より大きくなる場合、実際値は実際には最大値です。
- The low boundary下界
-
If the low attribute is
specified and a value could be parsed out of it, then the low
boundary is that value. Otherwise, the low boundary is the same as
the minimum value.
If the low boundary is then less than the minimum value, then
the low boundary is actually the same as the minimum
value. Similarly, if the low boundary is greater than the maximum
value, then it is actually the maximum value instead.
- The high boundary上界
-
If the high attribute is
specified and a value could be parsed out of it, then the high
boundary is that value. Otherwise, the high boundary is the same
as the maximum value.
If the high boundary is then less than the low boundary, then
the high boundary is actually the same as the low
boundary. Similarly, if the high boundary is greater than the
maximum value, then it is actually the maximum value instead.
- The optimum point最適点
-
If the optimum
attribute is specified and a value could be parsed out of it, then
the optimum point is that value. Otherwise, the optimum point is
the midpoint between the minimum value and the maximum value.
If the optimum point is then less than the minimum value, then
the optimum point is actually the same as the minimum
value. Similarly, if the optimum point is greater than the maximum
value, then it is actually the maximum value instead.
All of which will result in the following inequalities all being
true:
minimum value ≤ actual value ≤ maximum value
minimum value ≤ low boundary ≤ high boundary ≤ maximum value
minimum value ≤ optimum point ≤ maximum value最小値 ≤ 最適点 ≤ 最大値
UA requirements for regions of the gauge: If the
optimum point is equal to the low boundary or the high boundary, or
anywhere in between them, then the region between the low and high
boundaries of the gauge must be treated as the optimum region, and
the low and high parts, if any, must be treated as
suboptimal. Otherwise, if the optimum point is less than the low
boundary, then the region between the minimum value and the low
boundary must be treated as the optimum region, the region between
the low boundary and the high boundary must be treated as a
suboptimal region, and the region between the high boundary and the
maximum value must be treated as an even less good region. Finally,
if the optimum point is higher than the high boundary, then the
situation is reversed; the region between the high boundary and the
maximum value must be treated as the optimum region, the region
between the high boundary and the low boundary must be treated as a
suboptimal region, and the remaining region between the low boundary
and the minimum value must be treated as an even less good
region.
UA requirements for showing the gauge: When
representing a meter element to the user, the UA should
indicate the relative position of the actual value to the minimum
and maximum values, and the relationship between the actual value
and the three regions of the gauge.
The following markup:次に、マーク付けの例を示します。
<h3>Suggested groups</h3>
<menu type="toolbar">
<a href="?cmd=hsg" onclick="hideSuggestedGroups()">Hide suggested groups</a>
</menu>
<ul>
<li>
<p><a href="/group/comp.infosystems.www.authoring.stylesheets/view">comp.infosystems.www.authoring.stylesheets</a> -
<a href="/group/comp.infosystems.www.authoring.stylesheets/subscribe">join</a></p>
<p>Group description: <strong>Layout/presentation on the WWW.</strong></p>
<p><meter value="0.5">Moderate activity,</meter> Usenet, 618 subscribers</p>
</li>
<li>
<p><a href="/group/netscape.public.mozilla.xpinstall/view">netscape.public.mozilla.xpinstall</a> -
<a href="/group/netscape.public.mozilla.xpinstall/subscribe">join</a></p>
<p>Group description: <strong>Mozilla XPInstall discussion.</strong></p>
<p><meter value="0.25">Low activity,</meter> Usenet, 22 subscribers</p>
</li>
<li>
<p><a href="/group/mozilla.dev.general/view">mozilla.dev.general</a> -
<a href="/group/mozilla.dev.general/subscribe">join</a></p>
<p><meter value="0.25">Low activity,</meter> Usenet, 66 subscribers</p>
</li>
</ul>
Might be rendered as follows:この例は、次のようにレンダリングされることでしょう。
User agents may combine the value of the title attribute and the other attributes
to provide context-sensitive help or inline text detailing the
actual values.
For example, the following snippet:
<meter min=0 max=60 value=23.2 title=seconds></meter>
...might cause the user agent to display a gauge with a tooltip
saying "Value: 23.2 out of 60." on one line and "seconds" on a
second line.
The min, max, value, low, high, and optimum DOM attributes
must reflect the respective content attributes of the
same name. When the relevant content attributes are absent, the DOM
attributes must return zero. The value parsed from the
textContent never affects the DOM values.
Would be cool to have the value DOM attribute update the
textContent in-line...
4.6.13 The code element4.6.13 code 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The code element represents a fragment of computer
code. This could be an XML element name, a filename, a computer
program, or any other string that a computer would recognize.
Although there is no formal way to indicate the language of
computer code being marked up, authors who wish to mark
code elements with the language used, e.g. so that
syntax highlighting scripts can use the right rules, may do so by
adding a class prefixed with "language-" to
the element.
The following example shows how the element can be used in a
paragraph to mark up element names and computer code, including
punctuation.次の例は、段落の中で要素名や計算機符号を句読点も含めてこの要素でどのようにマーク付けできるかを示しています。
<p>The <code>code</code> element represents a fragment of computer
code.</p>
<p>When you call the <code>activate()</code> method on the
<code>robotSnowman</code> object, the eyes glow.</p>
<p>The example below uses the <code>begin</code> keyword to indicate
the start of a statement block. It is paired with an <code>end</code>
keyword, which is followed by the <code>.</code> punctuation character
(full stop) to indicate the end of the program.</p>
The following example shows how a block of code could be marked
up using the pre and code elements.
<pre><code class="language-pascal">var i: Integer;
begin
i := 1;
end.</code></pre>
A class is used in that example to indicate the language
used.
See the pre element for more details.
4.6.14 The var element4.6.14 var 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The var element represents a variable. This could be
an actual variable in a mathematical expression or programming
context, or it could just be a term used as a placeholder in
prose.
In the paragraph below, the letter "n" is being used as a
variable in prose:
<p>If there are <var>n</var> pipes leading to the ice
cream factory then I expect at <em>least</em> <var>n</var>
flavours of ice cream to be available for purchase!</p>
4.6.15 The samp element4.6.15 samp 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The samp element represents (sample) output from a
program or computing system.
See the pre and kbd
elements for more details.
This example shows the samp element being used
inline:
<p>The computer said <samp>Too much cheese in tray
two</samp> but I didn't know what that meant.</p>
This second example shows a block of sample output. Nested
samp and kbd elements allow for the
styling of specific elements of the sample output using a
style sheet.
<pre><samp><samp class="prompt">jdoe@mowmow:~$</samp> <kbd>ssh demo.example.com</kbd>
Last login: Tue Apr 12 09:10:17 2005 from mowmow.example.com on pts/1
Linux demo 2.6.10-grsec+gg3+e+fhs6b+nfs+gr0501+++p3+c4a+gr2b-reslog-v6.189 #1 SMP Tue Feb 1 11:22:36 PST 2005 i686 unknown
<samp class="prompt">jdoe@demo:~$</samp> <samp class="cursor">_</samp></samp></pre>
4.6.16 The kbd element4.6.16 kbd 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The kbd element represents user input (typically
keyboard input, although it may also be used to represent other
input, such as voice commands).
When the kbd element is nested inside a
samp element, it represents the input as it was echoed
by the system.
When the kbd element contains a
samp element, it represents input based on system
output, for example invoking a menu item.
When the kbd element is nested inside another
kbd element, it represents an actual key or other
single unit of input as appropriate for the input mechanism.
Here the kbd element is used to indicate keys to press:
<p>To make George eat an apple, press <kbd><kbd>Shift</kbd>+<kbd>F3</kbd></kbd></p>
In this second example, the user is told to pick a particular
menu item. The outer kbd element marks up a block of
input, with the inner kbd elements representing each
individual step of the input, and the samp elements
inside them indicating that the steps are input based on something
being displayed by the system, in this case menu labels:
<p>To make George eat an apple, select
<kbd><kbd><samp>File</samp></kbd>|<kbd><samp>Eat Apple...</samp></kbd></kbd>
</p>
4.6.17 The sub and sup elements
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which these elements may be used:これらの要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The sup element represents a superscript and the
sub element represents a subscript.
These elements must be used only to mark up typographical
conventions with specific meanings, not for typographical
presentation for presentation's sake. For example, it would be
inappropriate for the sub and sup elements
to be used in the name of the LaTeX document preparation system. In
general, authors should use these elements only if the
absence of those elements would change the meaning of the
content.
When the sub element is used inside a
var element, it represents the subscript that
identifies the variable in a family of variables.
<p>The coordinate of the <var>i</var>th point is
(<var>x<sub><var>i</var></sub></var>, <var>y<sub><var>i</var></sub></var>).
For example, the 10th point has coordinate
(<var>x<sub>10</sub></var>, <var>y<sub>10</sub></var>).</p>
In certain languages, superscripts are part of the typographical
conventions for some abbreviations.
<p>The most beautiful women are
<span lang="fr"><abbr>M<sup>lle</sup></abbr> Gwendoline</span> and
<span lang="fr"><abbr>M<sup>me</sup></abbr> Denise</span>.</p>
Mathematical expressions often use subscripts and superscripts.
Authors are encouraged to use MathML for marking up mathematics, but
authors may opt to use sub and sup if
detailed mathematical markup is not desired. [MathML]
<var>E</var>=<var>m</var><var>c</var><sup>2</sup>
f(<var>x</var>, <var>n</var>) = log<sub>4</sub><var>x</var><sup><var>n</var></sup>
4.6.18 The span element4.6.18 span 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The span element doesn't mean anything on its own,
but can be useful when used together with other attributes,
e.g. class, lang, or dir.
4.6.19 The i element4.6.19 i 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The i element represents a span of text in an
alternate voice or mood, or otherwise offset from the normal prose,
such as a taxonomic designation, a technical term, an idiomatic
phrase from another language, a thought, a ship name, or some other
prose whose typical typographic presentation is italicized.
Terms in languages different from the main text should be
annotated with lang attributes (xml:lang in XML).
The examples below show uses of the i element:
<p>The <i class="taxonomy">Felis silvestris catus</i> is cute.</p>
<p>The term <i>prose content</i> is defined above.</p>
<p>There is a certain <i lang="fr">je ne sais quoi</i> in the air.</p>
In the following example, a dream sequence is marked up using
i elements.
<p>Raymond tried to sleep.</p>
<p><i>The ship sailed away on Thursday</i>, he
dreamt. <i>The ship had many people aboard, including a beautiful
princess called Carey. He watched her, day-in, day-out, hoping she
would notice him, but she never did.</i></p>
<p><i>Finally one night he picked up the courage to speak with
her—</i></p>
<p>Raymond woke with a start as the fire alarm rang out.</p>
The i element should be used as a last resort when
no other element is more appropriate. In particular, citations
should use the cite element, defining instances of
terms should use the dfn element, stress emphasis
should use the em element, importance should be denoted
with the strong element, quotes should be marked up
with the q element, and small print should use the
small element.
Authors are encouraged to use the class attribute on the i
element to identify why the element is being used, so that if the
style of a particular use (e.g. dream sequences as opposed to
taxonomic terms) is to be changed at a later date, the author
doesn't have to go through the entire document (or series of related
documents) annotating each use.
Style sheets can be used to format i
elements, just like any other element can be restyled. Thus, it is
not the case that content in i elements will
necessarily be italicized.
4.6.20 The b element4.6.20 b 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The b element represents a span of text to be
stylistically offset from the normal prose without conveying any
extra importance, such as key words in a document abstract, product
names in a review, or other spans of text whose typical typographic
presentation is boldened.
The following example shows a use of the b element
to highlight key words without marking them up as important:
<p>The <b>frobonitor</b> and <b>barbinator</b> components are fried.</p>
In the following example, objects in a text adventure are
highlighted as being special by use of the b
element.
<p>You enter a small room. Your <b>sword</b> glows
brighter. A <b>rat</b> scurries past the corner wall.</p>
Another case where the b element is appropriate is
in marking up the lede (or lead) sentence or paragraph. The
following example shows how a BBC
article about kittens adopting a rabbit as their own could be
marked up using HTML5 elements:
<article>
<h2>Kittens 'adopted' by pet rabbit</h2>
<p><b>Six abandoned kittens have found an unexpected new
mother figure — a pet rabbit.</b></p>
<p>Veterinary nurse Melanie Humble took the three-week-old
kittens to her Aberdeen home.</p>
[...]
The b element should be used as a last resort when
no other element is more appropriate. In particular, headers should
use the h1 to h6 elements, stress emphasis
should use the em element, importance should be denoted
with the strong element, and text marked or highlighted
should use the mark element.
The following would be incorrect usage:
<p><b>WARNING!</b> Do not frob the barbinator!</p>
In the previous example, the correct element to use would have
been strong, not b.
Style sheets can be used to format b
elements, just like any other element can be restyled. Thus, it is
not the case that content in b elements will
necessarily be boldened.
4.6.21 The bdo element4.6.21 bdo 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None, but the
dir global attribute has special requirements on this element.
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The bdo element allows authors to override the
Unicode bidi algorithm by explicitly specifying a direction
override. [BIDI]
Authors must specify the dir
attribute on this element, with the value ltr to
specify a left-to-right override and with the value rtl
to specify a right-to-left override.
If the element has the dir
attribute set to the exact value ltr, then for the
purposes of the bidi algorithm, the user agent must act as if there
was a U+202D LEFT-TO-RIGHT OVERRIDE character at the start of the
element, and a U+202C POP DIRECTIONAL FORMATTING at the end of the
element.
If the element has the dir
attribute set to the exact value rtl, then for the
purposes of the bidi algorithm, the user agent must act as if there
was a U+202E RIGHT-TO-LEFT OVERRIDE character at the start of the
element, and a U+202C POP DIRECTIONAL FORMATTING at the end of the
element.
The requirements on handling the bdo element for the
bidi algorithm may be implemented indirectly through the style
layer. For example, an HTML+CSS user agent should implement these
requirements by implementing the CSS unicode-bidi
property. [CSS21]
4.6.22 The ruby element4.6.22 ruby 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- One or more groups of: phrasing content followed either by a single
rt element, or an rp element, an rt element, and another rp element.次の群を1つ以上: 語句付け内容の後に、
rt 要素が1つか、または
rp 要素と rt 要素と別の rp 要素、のいずれかが続く。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The ruby element allows one or more spans of
phrasing content to be marked with ruby annotations.ruby 要素は、
1つ以上の語句付け内容の範囲にルビ注釈を付すことができます。
A ruby element represents the spans of phrasing
content it contains, ignoring all the child rt and
rp elements and their descendants. Those spans of
phrasing content have associated annotations created using the
rt element.ruby 要素は、すべての子供 rt 要素・rp 要素とその子孫を無視したときの、
当該要素に含まれる語句付け内容の範囲(群)を表します。
語句付け内容の範囲(群)は、 rt
要素を使って作成される、関連付けられた注釈を持ちます。
In this example, each ideograph in the text 斎藤信男 is annotated with
its reading.この例では、テキスト「斎藤信男」の中の漢字それぞれに読みを注釈付けしています。
... <ruby>
斎 <rt> さい </rt>
藤 <rt> とう </rt>
信 <rt> のぶ </rt>
男 <rt> お </rt>
</ruby> ...
This might be rendered as:これは、次のようにレンダリングされましょう。
4.6.23 The rt element4.6.23 rt 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
ruby element.ruby 要素の子供として。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The rt element marks the ruby text component of a
ruby annotation.rt 要素は、ルビ注釈のルビ文部分を示します。
An rt element that is a child of a ruby
element represents an annotation (given by its children) for the
zero or more nodes of phrasing content that immediately precedes it
in the ruby element, ignoring rp
elements.ruby 要素の子供である
rt 要素は、
当該 ruby 要素中で
(rp 要素を無視した時)
直前にある零個以上の語句付け内容の節点に対する注釈
(子供により与えられます。) を表します。
An rt element that is not a child of a
ruby element represents the same thing as its
children.ruby 要素の子供ではない
rt 要素は、
その子供と同じものを表します。
4.6.24 The rp element4.6.24 rp 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
ruby element, either immediately before or immediately after an rt element.ruby 要素の子供として、 rt 要素の直前または直後に。
- Content model:内容モデル:
- If the
rp element is immediately after an rt element that is immediately preceded by another rp element: a single character from Unicode character class Pe.rp 要素が別の rp
要素の直後にある rt 要素の直後の場合:
Unicode 文字クラス Pe から1文字。
- Otherwise: a single character from Unicode character class Ps.それ以外の場合: Unicode 文字クラス Ps から1文字。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The rp element can be used to provide parentheses
around a ruby text component of a ruby annotation, to be shown by
user agents that don't support ruby annotations.rp 要素は、
ルビ注釈に対応していない利用者エージェントが示す、
ルビ注釈のルビ文部分の周囲の括弧を提供するために使うことができます。
An rp element that is a child of a ruby
element represents nothing and it and its contents must be
ignored. An rp element whose parent element is not a
ruby element represents the same thing as its
children.ruby 要素の子供である
rp 要素は、何も表さず、
その要素と内容は無視されなければなりません。親要素が ruby 要素でない rp
要素は、その子供と同じものを表します。
The example above, in which each ideograph in the text 斎藤信男 is annotated with
its reading, could be expanded to use rp so that in
legacy user agentthe readings are in parentheses:先の例ではテキスト「斎藤信男」の中の漢字それぞれに読みを注釈付けしていましたが、
更に rp も使うことによって、
遺物利用者エージェントでは読みが括弧で括られるにできます。
... <ruby>
斎 <rp>(</rp><rt>さい</rt><rp>)</rp>
藤 <rp>(</rp><rt>とう</rt><rp>)</rp>
信 <rp>(</rp><rt>のぶ</rt><rp>)</rp>
男 <rp>(</rp><rt>お</rt><rp>)</rp>
</ruby> ...
In conforming user agents the rendering would be as above, but
in user agents that do not support ruby, the rendering would
be:適合利用者エージェントでのレンダリングは前掲の通りとなりますが、
ルビに対応していない利用者エージェントでのレンダリングは次のようになります。
... 斎 (さい) 藤 (とう) 信 (のぶ) 男 (お) ...
4.6.25 Usage summary4.6.25 利用法のまとめ
We need to summarize the various elements, in
particular to distinguish b/i/em/strong/var/q/mark/cite.
HTML does not have a dedicated mechanism for marking up
footnotes. Here are the recommended alternatives.HTML は脚注をマーク付けするための専用の仕組みを持っていません。
ここでは、推奨される代替法を紹介します。
For short inline annotations, the title attribute should be used.短い行内注釈については、 title 属性を使うべきです。
In this example, two parts of a dialog are annotated.次の例では、対話の2つの部分が注釈付けされています。
<dialog>
<dt>Customer
<dd>Hello! I wish to register a complaint. Hello. Miss?
<dt>Shopkeeper
<dd><span title="Colloquial pronunciation of 'What do you'"
>Watcha</span> mean, miss?
<dt>Customer
<dd>Uh, I'm sorry, I have a cold. I wish to make a complaint.
<dt>Shopkeeper
<dd>Sorry, <span title="This is, of course, a lie.">we're
closing for lunch</span>.
</dialog>
For longer annotations, the a element should be
used, pointing to an element later in the document. The convention
is that the contents of the link be a number in square brackets.より長い注釈については、 a
を使って、文書の後の要素を指すようにするべきです。
慣習的にはリンクの内容は数字を四角括弧で括ったものです。
In this example, a footnote in the dialog links to a paragraph
below the dialog. The paragraph then reciprocally links back to the
dialog, allowing the user to return to the location of the
footnote.次の例では、対話中の脚注が対話の後の段落へのリンクとなっています。
その段落の方は逆に対話へ逆リンクしており、
利用者が脚注の場所へ返れるようになっています。
<dialog>
<dt>Announcer
<dd>Number 16: The <i>hand</i>.
<dt>Interviewer
<dd>Good evening. I have with me in the studio tonight Mr
Norman St John Polevaulter, who for the past few years has
been contradicting people. Mr Polevaulter, why <em>do</em>
you contradict people?
<dt>Norman
<dd>I don't. <a href="#fn1" id="r1">[1]</a>
<dt>Interviewer
<dd>You told me you did!
</dialog>
<section>
<p id="fn1"><a href="#r1">[1]</a> This is, naturally, a lie,
but paradoxically if it were true he could not say so without
contradicting the interviewer and thus making it false.</p>
</section>
For side notes, longer annotations that apply to entire sections
of the text rather than just specific words or sentences, the
aside element should be used.傍注 (文章中の特定の語や文に対してだけではなく、節全体に適用される、
より長い注釈) には、 aside 要素を使うべきです。
In this example, a sidebar is given after a dialog, giving some
context to the dialog.次の例では、対話の後に傍注があり、対話の背景を説明しています。
<dialog>
<dt>Customer
<dd>I will not buy this record, it is scratched.
<dt>Shopkeeper
<dd>I'm sorry?
<dt>Customer
<dd>I will not buy this record, it is scratched.
<dt>Shopkeeper
<dd>No no no, this's'a tobacconist's.
</dialog>
<aside>
<p>In 1970, the British Empire lay in ruins, and foreign
nationalists frequented the streets — many of them Hungarians
(not the streets — the foreign nationals). Sadly, Alexander
Yalt has been publishing incompetently-written phrase books.
</aside>
4.7 Edits4.7 編集
The ins and del elements represent
edits to the document.ins 要素と del 要素は文書に対する編集を表します。
4.7.1 The ins element4.7.1 ins 要素
- Categories分類
- When the element only contains phrasing content: phrasing content.要素が語句付け内容を含む時:
語句付け内容。
- Otherwise: flow content.その他の場合: 流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Transparent.透過。
- Element-specific attributes:要素固有属性:
citedatetime- DOM interface:DOM 界面:
- Uses the
HTMLModElement interface.HTMLModElement 界面を使用します。
The ins element represents an addition to the
document.ins 要素は文書に対する追加を表します。
The following represents the addition of a single paragraph:次の例は、段落1つの追加を表します。
<aside>
<ins>
<p> I like fruit. </p>
</ins>
</aside>
As does this, because everything in the aside
element here counts as phrasing content and therefore
there is just one paragraph:次の場合もそうで、 aside 要素の中のものはすべて語句付け内容とみなされ、段落が1つだけ追加されています。
<aside>
<ins>
Apples are <em>tasty</em>.
</ins>
<ins>
So are pears.
</ins>
</aside>
ins elements should not cross implied paragraph boundaries.ins 要素は暗示段落の境界を越えるべきではありません。
The following example represents the addition of two paragraphs,
the second of which was inserted in two parts. The first
ins element in this example thus crosses a paragraph
boundary, which is considered poor form.次の例は2つの段落の追加を表しています。
2つ目の段落は2つの部分で挿入されています。
この例の1つ目の ins 要素は段落の境界を越えているので、
悪い形と考えられます。
<aside>
<ins datetime="2005-03-16T00:00Z">
<p> I like fruit. </p>
Apples are <em>tasty</em>.
</ins>
<ins datetime="2007-12-19T00:00Z">
So are pears.
</ins>
</aside>
Here is a better way of marking this up. It uses more elements,
but none of the elements cross implied paragraph boundaries.こちらは同じことをマーク付けするよりよい方法です。
こちらはより多くの要素を使っていますが、
どの要素も暗示段落境界は超えていません。
<aside>
<ins datetime="2005-03-16T00:00Z">
<p> I like fruit. </p>
</ins>
<ins datetime="2005-03-16T00:00Z">
Apples are <em>tasty</em>.
</ins>
<ins datetime="2007-12-19T00:00Z">
So are pears.
</ins>
</aside>
4.7.2 The del element4.7.2 del 要素
- Categories分類
- When the element only contains phrasing content: phrasing content.要素が語句付け内容を含む時:
語句付け内容。
- Otherwise: flow content.その他の場合: 流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Transparent.透過。
- Element-specific attributes:要素固有属性:
citedatetime- DOM interface:DOM 界面:
- Uses the
HTMLModElement interface.HTMLModElement 界面を使用します。
The del element represents a removal from the
document.del 要素は文書からの削除を表します。
del elements should not cross implied paragraph boundaries.del 要素は暗示段落境界を交差するべきではありません。
4.7.3 Attributes common to ins and del elements4.7.3 ins 要素と del 要素に共通の属性
The cite attribute
may be used to specify the address of a document that explains the
change. When that document is long, for instance the minutes of a
meeting, authors are encouraged to include a fragment identifier
pointing to the specific part of that document that discusses the
change.cite
属性は変更を説明する文書の番地を指定するために使って構いません。
文書が会議の議事録のように長い時には、その文書の中で変更について議論している特定の部分を指す素片識別子を含めることを著者にはお勧めします。
If the cite attribute is
present, it must be a valid URL that explains the
change. User agents should allow users to follow such citation
links.cite
属性が存在する場合には、変更を説明する妥当な URL
でなければなりません。利用者エージェントは利用者がそのような引用のリンクをたどれるようにするべきです。
The datetime
attribute may be used to specify the time and date of the change.datetime
属性は変更の日時を指定するために使って構いません。
If present, the datetime
attribute must be a valid global date and time string
value.datetime
属性が存在する場合には、妥当な大域日時文字列値でなければなりません。
User agents must parse the datetime attribute according to the
parse a global date and time string algorithm. If that
doesn't return a time, then the modification has no associated
timestamp (the value is non-conforming; it is not a valid
global date and time string). Otherwise, the modification is
marked as having been made at the given datetime. User agents should
use the associated timezone information to determine which timezone
to present the given datetime in.利用者エージェントは datetime
属性を大域日時文字列を構文解析する算法に従って構文解析しなければなりません。
同算法が時刻を返さない場合、修正は時刻印に関連付けられていません
(値は不適合で、妥当な大域日時文字列ではありません)。
そうでない場合、修正は与えられた日時に行われたと印付けされます。
利用者エージェントは関連付けられた時間帯の情報を与えられた日時を提示するための時間帯の決定に使うべきです。
The ins and del elements must implement
the HTMLModElement interface:ins 要素と del 要素は HTMLModElement
界面を実装しなければなりません。
interface HTMLModElement : HTMLElement {
attribute DOMString cite;
attribute DOMString dateTime;
};
The cite DOM
attribute must reflect the element's cite content attribute. The dateTime DOM attribute
must reflect the element's datetime content attribute.cite DOM
属性は要素の cite ないよう属性を反映しなければなりません。dateTime DOM
属性は要素の datetime 内容属性を反映しなければなりません。
4.7.4 Edits and paragraphs4.7.4 編集と段落
Since the ins and del elements do not
affect paragraphing, it is possible,
in some cases where paragraphs are implied (without explicit p
elements), for an ins or del element to
span both an entire paragraph or other non-phrasing
content elements and part of another paragraph.
For example:例:
<section>
<ins>
<p>
This is a paragraph that was inserted.
</p>
This is another paragraph whose first sentence was inserted
at the same time as the paragraph above.
</ins>
This is a second sentence, which was there all along.
</section>
By only wrapping some paragraphs in p elements, one
can even get the end of one paragraph, a whole second paragraph,
and the start of a third paragraph to be covered by the same
ins or del element (though this is very
confusing, and not considered good practice):
<section>
This is the first paragraph. <ins>This sentence was
inserted.
<p>This second paragraph was inserted.</p>
This sentence was inserted too.</ins> This is the
third paragraph in this example.
</section>
However, due to the way implied
paragraphs are defined, it is not possible to mark up the
end of one paragraph and the start of the very next one using the
same ins or del element. You instead have
to use one (or two) p element(s) and two
ins or del elements:
For example:例:
<section>
<p>This is the first paragraph. <del>This sentence was
deleted.</del></p>
<p><del>This sentence was deleted too.</del> That
sentence needed a separate <del> element.</p>
</section>
Partly because of the confusion described above, authors are
strongly recommended to always mark up all paragraphs with the
p element, and to not have any ins or
del elements that cross across any implied paragraphs.
4.7.5 Edits and lists
The content models of the ol and ul
elements do not allow ins and del elements
as children. Lists always represent all their items, including items
that would otherwise have been marked as deleted.
To indicate that an item is inserted or deleted, an
ins or del element can be wrapped around
the contents of the li element. To indicate that an
item has been replaced by another, a single li element
can have one or more del elements followed by one or
more ins elements.
In the following example, a list that started empty had items
added and removed from it over time. The bits in the example that
have been emphasised show the parts that are the "current" state of
the list. The list item numbers don't take into account the edits,
though.
<h1>Stop-ship bugs</h1>
<ol>
<li><ins datetime="2008-02-12T15:20Z">Bug 225:
Rain detector doesn't work in snow</ins></li>
<li><del datetime="2008-03-01T20:22Z"><ins datetime="2008-02-14T12:02Z">Bug 228:
Water buffer overflows in April</ins></del></li>
<li><ins datetime="2008-02-16T13:50Z">Bug 230:
Water heater doesn't use renewable fuels</ins></li>
<li><del datetime="2008-02-20T21:15Z"><ins datetime="2008-02-16T14:25Z">Bug 232:
Carbon dioxide emissions detected after startup</ins></del></li>
</ol>
In the following example, a list that started with just fruit
was replaced by a list with just colors.
<h1>List of <del>fruits</del><ins>colors</ins></h1>
<ul>
<li><del>Lime</del><ins>Green</ins></li>
<li><del>Apple</del></li>
<li>Orange</li>
<li><del>Pear</del></li>
<li><ins>Teal</ins></li>
<li><del>Lemon</del><ins>Yellow</ins></li>
<li>Olive</li>
<li><ins>Purple</ins>
</ul>
4.8 Embedded content4.8 埋め込まれた内容
- Categories分類
- Flow content.流れ内容。
- Sectioning root.章節付け根。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Either: one
legend element followed by flow content.
- Or: Flow content followed by one
legend element.
- Or: Flow content.
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The figure element represents some flow
content, optionally with a caption, which can be moved away
from the main flow of the document without affecting the document's
meaning.
The element can thus be used to annotate illustrations, diagrams,
photos, code listings, etc, that are referred to from the main
content of the document, but that could, without affecting the flow
of the document, be moved away from that primary content, e.g. to
the side of the page, to dedicated pages, or to an appendix.
The first legend element child of the element, if
any, represents the caption of the figure element's
contents. If there is no child legend element, then
there is no caption.
The remainder of the element's contents, if any, represents the
content.
This example shows the figure element to mark up a
code listing.
<p>In <a href="#l4">listing 4</a> we see the primary core interface
API declaration.</p>
<figure id="l4">
<legend>Listing 4. The primary core interface API declaration.</legend>
<pre><code>interface PrimaryCore {
boolean verifyDataLine();
void sendData(in sequence<byte> data);
void initSelfDestruct();
}</code></pre>
</figure>
<p>The API is designed to use UTF-8.</p>
Here we see a figure element to mark up a
photo.
<figure>
<img src="bubbles-work.jpeg"
alt="Bubbles, sitting in his office chair, works on his
latest project intently.">
<legend>Bubbles at work</legend>
</figure>
In this example, we see an image that is not
a figure, as well as an image and a video that are.
<h2>Malinko's comics</h2>
<p>This case centered on some sort of "intellectual property"
infringement related to a comic (see Exhibit A). The suit started
after a trailer ending with these words:</p>
<img src="promblem-packed-action.png" alt="ROUGH COPY! Promblem-Packed Action!">
<p>...was aired. A lawyer, armed with a Bigger Notebook, launched a
preemptive strike using snowballs. A complete copy of the trailer is
included with Exhibit B.</p>
<figure>
<img src="ex-a.png" alt="Two squiggles on a dirty piece of paper.">
<legend>Exhibit A. The alleged <cite>rough copy</cite> comic.</legend>
</figure>
<figure>
<video src="ex-b.mov"></video>
<legend>Exhibit B. The <code>Rough Copy</cite> trailer.</legend>
</figure>
<p>The case was resolved out of court.</p>
Here, a part of a poem is marked up using
figure.
<figure>
<p>'Twas brillig, and the slithy toves<br>
Did gyre and gimble in the wabe;<br>
All mimsy were the borogoves,<br>
And the mome raths outgrabe.</p>
<legend><cite>Jabberwocky</cite> (first verse). Lewis Carroll, 1832-98</legend>
</figure>
In this example, which could be part of a much larger work
discussing a castle, the figure has three images in it.
<figure>
<img src="castle1423.jpeg" title="Etching. Anonymous, ca. 1423."
alt="The castle has one tower, and a tall wall around it.">
<img src="castle1858.jpeg" title="Oil-based paint on canvas. Maria Towle, 1858."
alt="The castle now has two towers and two walls.">
<img src="castle1999.jpeg" title="Film photograph. Peter Jankle, 1999."
alt="The castle lies in ruins, the original tower all that remains in one piece.">
<legend>The castle through the ages: 1423, 1858, and 1999 respectively.</legend>
</figure>
4.8.2 The img element4.8.2 img 要素
- Categories分類
- Embedded content.埋め込まれた内容。
- If the element has an
usemap attribute: Interactive content.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where embedded content is expected.埋め込まれた内容が期待される場所。
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
altsrcusemapismapwidthheight- DOM interface:DOM 界面:
-
[NamedConstructor=Image(),
NamedConstructor=Image(in unsigned long width),
NamedConstructor=Image(in unsigned long width, in unsigned long height)]
interface HTMLImageElement : HTMLElement {
attribute DOMString alt;
attribute DOMString src;
attribute DOMString useMap;
attribute boolean isMap;
attribute unsigned long width;
attribute unsigned long height;
readonly attribute boolean complete;
};
An img element represents an image.img 要素は画像を表します。
The image given by the src attribute is the
embedded content, and the value of the alt attribute is the
img element's fallback content.
The src attribute must be
present, and must contain a valid URL referencing a
non-interactive, optionally animated, image resource that is neither
paged nor scripted.
Images can thus be static bitmaps (e.g. PNGs, GIFs,
JPEGs), single-page vector documents (single-page PDFs, XML files
with an SVG root element), animated bitmaps (APNGs, animated GIFs),
animated vector graphics (XML files with an SVG root element that
use declarative SMIL animation), and so forth. However, this also
precludes SVG files with script, multipage PDF files, interactive
MNG files, HTML documents, plain text documents, and so forth.
The requirements on the alt
attribute's value are described in the next
section.
There has been some suggestion that the longdesc attribute from HTML4, or some other
mechanism that is more powerful than alt="",
should be included. This has been considered and rejected in the
past, but may be considered again in the future.
The img must not be used as a layout tool. In
particular, img elements should not be used to display
fully transparent images, as they rarely convey meaning and rarely
add anything useful to the document.
When an img is created with a src attribute, and whenever the src attribute is set subsequently, the
user agent must fetch the resource specifed by the
src attribute's value, unless the
user agent cannot support images, or its support for images has been
disabled, or the user agent only fetches elements on demand.
Fetching the image must delay the load event.
This, unfortunately, can be used to perform a
rudimentary port scan of the user's local network (especially in
conjunction with scripting, though scripting isn't actually
necessary to carry out such an attack). User agents may implement
cross-origin access control policies
that mitigate this attack.
If the image's type is a supported image type, and the image is a
valid image of that type, then the image is said to be
available (this affects exactly what the element represents,
as defined below). This can be true even before the image is
completely downloaded, if the user agent supports incremental
rendering of images; in such cases, each task that is queued by the networking task source while
the image is being fetched must update
the presentation of the image appropriately.
Whether the image is fetched successfully or not (e.g. whether
the response code was a 2xx code or equivalent) must be
ignored when determining the image's type and whether it is a valid
image.
This allows servers to return images with error
responses, and have them displayed.
The user agents should apply the image sniffing rules to determine the type
of the image, with the image's associated
Content-Type headers giving the official
type. If these rules are not applied, then the type of the
image must be the type given by the image's associated Content-Type headers.
User agents must not support non-image resources with the
img element (e.g. XML files whose root element is an
HTML element). User agents must not run executable code
(e.g. scripts) embedded in the image resource. User agents must only
display the first page of a multipage resource (e.g. a PDF
file). User agents must not allow the resource to act in an
interactive fashion, but should honour any animation in the
resource.
This specification does not specify which image types are to be
supported.
The task that is queued by the networking task
source once the resource has been fetched, must, if the download was successful
and the image is available, queue a task to
fire a load event on
the img element (this happens after complete starts returning true); and
otherwise, if the fetching process fails without a response from the
remote server, or completes but the image is not a valid or
supported image, queue a task to fire an error event on the
img element.
What an img element represents depends on the src attribute and the alt attribute.
- If the
src attribute is set
and the alt attribute is set to
the empty string
-
The image is either decorative or supplemental to the rest of
the content, redundant with some other information in the
document.
If the image is available and the user agent is configured to
display that image, then the element represents the image
specified by the src
attribute.
Otherwise, the element represents nothing, and may be omitted
completely from the rendering. User agents may provide the user
with a notification that an image is present but has been omitted
from the rendering.
- If the
src attribute is set
and the alt attribute is set to a
value that isn't empty
-
The image is a key part of the content; the alt attribute gives a textual
equivalent or replacement for the image.
If the image is available and the user agent is configured to
display that image, then the element represents the image
specified by the src
attribute.
Otherwise, the element represents the text given by the alt attribute. User agents may provide
the user with a notification that an image is present but has been
omitted from the rendering.
- If the
src attribute is set
and the alt attribute is not
-
The image might be a key part of the content, and there is no
textual equivalent of the image available.
If the image is available, the element represents the
image specified by the src
attribute.
If the image is not available or if the user agent is
not configured to display the image, then the user agent should
display some sort of indicator that there is an image that is not
being rendered, and may, if requested by the user, or if so
configured, or when required to provide contextual information in
response to navigation, provide caption information for the image,
derived as follows:
If the image has a title
attribute whose value is not the empty string, then the value of
that attribute is the caption information; abort these
steps.
If the image is the child of a figure element
that has a child legend element, then the contents
of the first such legend element are the caption
information; abort these steps.
Run the algorithm to create the outline for
the document.
If the img element did not end up associated
with a heading in theoutline, or if there are any other images
that are lacking an alt
attribute and that are associated with the same heading in the
outline as the img element in question, then there
is no caption information; abort these steps.
The caption information is the heading with which the
image is associated according to the outline.
- If the
src attribute is not
set and either the alt attribute
is set to the empty string or the alt attribute is not set at all
-
The element represents nothing.
- Otherwiseそれ以外の場合
-
The element represents the text given by the alt attribute.
The alt attribute does not
represent advisory information. User agents must not present the
contents of the alt attribute in
the same way as content of the title
attribute.
User agents may always provide the user with the option to
display any image, or to prevent any image from being
displayed. User agents may also apply image analysis heuristics to
help the user make sense of the image when the user is unable to
make direct use of the image, e.g. due to a visual disability or
because they are using a text terminal with no graphics
capabilities.
The contents of img elements, if any, are
ignored for the purposes of rendering.
The usemap attribute,
if present, can indicate that the image has an associated
image map.
The ismap
attribute, when used on an element that is a descendant of an
a element with an href attribute, indicates by its
presence that the element provides access to a server-side image
map. This affects how events are handled on the corresponding
a element.
The ismap attribute is a
boolean attribute. The attribute must not be specified
on an element that does not have an ancestor a element
with an href attribute.
The img element supports dimension
attributes.
The DOM attributes alt, src, useMap, and isMap each must
reflect the respective content attributes of the same
name.
The DOM attributes width and height must return the
rendered width and height of the image, in CSS pixels, if the image
is being rendered, and is being rendered to a visual medium; or else
the intrinsic with and height of the image, in CSS pixels, if the
image is available but not being rendered to a visual medium; or
else 0, if the image is not available or its dimensions are not
known. [CSS21]
The DOM attribute complete must return
true if the user agent has fetched the image specified in the src attribute, and it is a valid image,
even if the final task queued by
the networking task source for the fetching of the image resource has not yet been
processed. Otherwise, the attribute must return false.
The value of complete can thus change while a
script is executing.
Three constructors are provided for creating
HTMLImageElement objects (in addition to the factory
methods from DOM Core such as createElement()): Image(), Image(width), and Image(width, height). When invoked as constructors,
these must return a new HTMLImageElement object (a new
img element). If the width argument
is present, the new object's width content attribute must be set to
width. If the height
argument is also present, the new object's height content attribute must be set
to height.
A single image can have different appropriate alternative text
depending on the context.
In each of the following cases, the same image is used, yet the
alt text is different each
time. The image is the coat of arms of the Canton Geneva in
Switzerland.
Here it is used as a supplementary icon:
<p>I lived in <img src="carouge.svg" alt=""> Carouge.</p>
Here it is used as an icon representing the town:
<p>Home town: <img src="carouge.svg" alt="Carouge"></p>
Here it is used as part of a text on the town:
<p>Carouge has a coat of arms.</p>
<p><img src="carouge.svg" alt="The coat of arms depicts a lion, sitting in front of a tree."></p>
<p>It is used as decoration all over the town.</p>
Here it is used as a way to support a similar text where the
description is given as well as, instead of as an alternative to,
the image:
<p>Carouge has a coat of arms.</p>
<p><img src="carouge.svg" alt=""></p>
<p>The coat of arms depicts a lion, sitting in front of a tree.
It is used as decoration all over the town.</p>
Here it is used as part of a story:
<p>He picked up the folder and a piece of paper fell out.</p>
<p><img src="carouge.svg" alt="Shaped like a shield, the paper had a
red background, a green tree, and a yellow lion with its tongue
hanging out and whose tail was shaped like an S."></p>
<p>He stared at the folder. S! The answer he had been looking for all
this time was simply the letter S! How had he not seen that before? It all
came together now. The phone call where Hector had referred to a lion's tail,
the time Marco had stuck his tongue out...</p>
Here it is not known at the time of publication what the image
will be, only that it will be a coat of arms of some kind, and thus
no replacement text can be provided, and instead only a brief
caption for the image is provided, in the title attribute:
<p>The last user to have uploaded a coat of arms uploaded this one:</p>
<p><img src="last-uploaded-coat-of-arms.cgi" title="User-uploaded coat of arms."></p>
Ideally, the author would find a way to provide real replacement
text even in this case, e.g. by asking the previous user. Not
providing replacement text makes the document more difficult to use
for people who are unable to view images, e.g. blind users, or
users or very low-bandwidth connections or who pay by the byte, or
users who are forced to use a text-only Web browser.
Here are some more examples showing the same picture used in
different contexts, with different appropriate alternate texts each
time.
<article>
<h1>My cats</h1>
<h2>Fluffy</h2>
<p>Fluffy is my favourite.</p>
<img src="fluffy.jpg" alt="She likes playing with a ball of yarn.">
<p>She's just too cute.</p>
<h2>Miles</h2>
<p>My other cat, Miles just eats and sleeps.</p>
</article>
<article>
<h1>Photography</h1>
<h2>Shooting moving targets indoors</h2>
<p>The trick here is to know how to anticipate; to know at what speed and
what distance the subject will pass by.</p>
<img src="fluffy.jpg" alt="A cat flying by, chasing a ball of yarn, can be
photographed quite nicely using this technique.">
<h2>Nature by night</h2>
<p>To achieve this, you'll need either an extremely sensitive film, or
immense flash lights.</p>
</article>
<article>
<h1>About me</h1>
<h2>My pets</h2>
<p>I've got a cat named Fluffy and a dog named Miles.</p>
<img src="fluffy.jpg" alt="Fluffy, my cat, tends to keep itself busy.">
<p>My dog Miles and I like go on long walks together.</p>
<h2>music</h2>
<p>After our walks, having emptied my mind, I like listening to Bach.</p>
</article>
<article>
<h1>Fluffy and the Yarn</h1>
<p>Fluffy was a cat who liked to play with yarn. He also liked to jump.</p>
<aside><img src="fluffy.jpg" alt="" title="Fluffy"></aside>
<p>He would play in the morning, he would play in the evening.</p>
</article>
4.8.2.1 Requirements for providing text to act as an alternative for images
The requirements for the alt
attribute depend on what the image is intended to represent, as
described in the following sections.
When an a element that is a hyperlink,
or a button element, has no textual content but
contains one or more images, the alt attributes must contain text that
together convey the purpose of the link or button.
In this example, a user is asked to pick his preferred color
from a list of three. Each color is given by an image, but for
users who have configured their user agent not to display images,
the color names are used instead:
<h1>Pick your color</h1>
<ul>
<li><a href="green.html"><img src="green.jpeg" alt="Green"></a></li>
<li><a href="blue.html"><img src="blue.jpeg" alt="Blue"></a></li>
<li><a href="red.html"><img src="red.jpeg" alt="Red"></a></li>
</ul>
In this example, each button has a set of images to indicate the
kind of color output desired by the user. The first image is used
in each case to give the alternative text.
<button name="rgb"><img src="red" alt="RGB"><img src="green" alt=""><img src="blue" alt=""></button>
<button name="cmyk"><img src="cyan" alt="CMYK"><img src="magenta" alt=""><img src="yellow" alt=""><img src="black" alt=""></button>
Since each image represents one part of the text, it could also
be written like this:
<button name="rgb"><img src="red" alt="R"><img src="green" alt="G"><img src="blue" alt="B"></button>
<button name="cmyk"><img src="cyan" alt="C"><img src="magenta" alt="M"><img src="yellow" alt="Y"><img src="black" alt="K"></button>
However, with other alternative text, this might not work, and
putting all the alternative text into one image in each case might
make more sense:
<button name="rgb"><img src="red" alt="sRGB profile"><img src="green" alt=""><img src="blue" alt=""></button>
<button name="cmyk"><img src="cyan" alt="CMYK profile"><img src="magenta" alt=""><img src="yellow" alt=""><img src="black" alt=""></button>
4.8.2.1.2 A phrase or paragraph with an alternative graphical representation: charts, diagrams, graphs, maps, illustrations
Sometimes something can be more clearly stated in graphical
form, for example as a flowchart, a diagram, a graph, or a simple
map showing directions. In such cases, an image can be given using
the img element, but the lesser textual version must
still be given, so that users who are unable to view the image
(e.g. because they have a very slow connection, or because they
are using a text-only browser, or because they are listening to
the page being read out by a hands-free automobile voice Web
browser, or simply because they are blind) are still able to
understand the message being conveyed.
The text must be given in the alt attribute, and must convey the
same message as the image specified in the src attribute.
It is important to realize that the alternative text is a
replacement for the image, not a description of the
image.
In the following example we have a flowchart in image
form, with text in the alt
attribute rephrasing the flowchart in prose form:
<p>In the common case, the data handled by the tokenization stage
comes from the network, but it can also come from script.</p>
<p><img src="images/parsing-model-overview.png" alt="The network
passes data to the Tokeniser stage, which passes data to the Tree
Construction stage. From there, data goes to both the DOM and to
Script Execution. Script Execution is linked to the DOM, and, using
document.write(), passes data to the Tokeniser."></p>
Here's another example, showing a good solution and a bad
solution to the problem of including an image in a
description.
First, here's the good solution. This sample shows how the
alternative text should just be what you would have put in the
prose if the image had never existed.
<!-- This is the correct way to do things. -->
<p>
You are standing in an open field west of a house.
<img src="house.jpeg" alt="The house is white, with a boarded front door.">
There is a small mailbox here.
</p>
Second, here's the bad solution. In this incorrect way of
doing things, the alternative text is simply a description of the
image, instead of a textual replacement for the image. It's bad
because when the image isn't shown, the text doesn't flow as well
as in the first example.
<!-- This is the wrong way to do things. -->
<p>
You are standing in an open field west of a house.
<img src="house.jpeg" alt="A white house, with a boarded front door.">
There is a small mailbox here.
</p>
4.8.2.1.3 A short phrase or label with an alternative graphical representation: icons, logos
A document can contain information in iconic form. The icon is
intended to help users of visual browsers to recognize features at
a glance.
In some cases, the icon is supplemental to a text label
conveying the same meaning. In those cases, the alt attribute must be present but must
be empty.
Here the icons are next to text that conveys the same meaning,
so they have an empty alt
attribute:
<nav>
<p><a href="/help/"><img src="/icons/help.png" alt=""> Help</a></p>
<p><a href="/configure/"><img src="/icons/configuration.png" alt="">
Configuration Tools</a></p>
</nav>
In other cases, the icon has no text next to it describing what
it means; the icon is supposed to be self-explanatory. In those
cases, an equivalent textual label must be given in the alt attribute.
Here, posts on a news site are labeled with an icon
indicating their topic.
<body>
<article>
<header>
<h1>Ratatouille wins <i>Best Movie of the Year</i> award</h1>
<p><img src="movies.png" alt="Movies"></p>
</header>
<p>Pixar has won yet another <i>Best Movie of the Year</i> award,
making this its 8th win in the last 12 years.</p>
</article>
<article>
<header>
<h1>Latest TWiT episode is online</h1>
<p><img src="podcasts.png" alt="Podcasts"></p>
</header>
<p>The latest TWiT episode has been posted, in which we hear
several tech news stories as well as learning much more about the
iPhone. This week, the panelists compare how reflective their
iPhones' Apple logos are.</p>
</article>
</body>
Many pages include logos, insignia, flags, or emblems, which
stand for a particular entity such as a company, organization,
project, band, software package, country, or some such.
If the logo is being used to represent the entity, e.g. as a page
header, the alt attribute must
contain the name of the entity being represented by the logo. The
alt attribute must not
contain text like the word "logo", as it is not the fact that it is
a logo that is being conveyed, it's the entity itself.
If the logo is being used next to the name of the entity that
it represents, then the logo is supplemental, and its alt attribute must instead be
empty.
If the logo is merely used as decorative material (as branding,
or, for example, as a side image in an article that mentions the
entity to which the logo belongs), then the entry below on purely
decorative images applies. If the logo is actually being
discussed, then it is being used as a phrase or paragraph (the
description of the logo) with an alternative graphical
representation (the logo itself), and the first entry above
applies.
In the following snippets, all four of the above cases are
present. First, we see a logo used to represent a company:
<h1><img src="XYZ.gif" alt="The XYZ company"></h1>
Next, we see a paragraph which uses a logo right next to the
company name, and so doesn't have any alternative text:
<article>
<h2>News</h2>
<p>We have recently been looking at buying the <img src="alpha.gif"
alt=""> ΑΒΓ company, a small Greek company
specializing in our type of product.</p>
In this third snippet, we have a logo being used in an aside,
as part of the larger article discussing the acquisition:
<aside><p><img src="alpha-large.gif" alt=""></p></aside>
<p>The ΑΒΓ company has had a good quarter, and our
pie chart studies of their accounts suggest a much bigger blue slice
than its green and orange slices, which is always a good sign.</p>
</article>
Finally, we have an opinion piece talking about a logo, and
the logo is therefore described in detail in the alternative
text.
<p>Consider for a moment their logo:</p>
<p><img src="/images/logo" alt="It consists of a green circle with a
green question mark centered inside it."></p>
<p>How unoriginal can you get? I mean, oooooh, a question mark, how
<em>revolutionary</em>, how utterly <em>ground-breaking</em>, I'm
sure everyone will rush to adopt those specifications now! They could
at least have tried for some sort of, I don't know, sequence of
rounded squares with varying shades of green and bold white outlines,
at least that would look good on the cover of a blue book.</p>
This example shows how the alternative text should be written
such that if the image isn't available, and the text is used
instead, the text flows seamlessly into the surrounding text, as
if the image had never been there in the first place.
4.8.2.1.4 Text that has been rendered to a graphic for typographical effect
Sometimes, an image just consists of text, and the purpose of the
image is not to highlight the actual typographic effects used to
render the text, but just to convey the text itself.
In such cases, the alt
attribute must be present but must consist of the same text as
written in the image itself.
Consider a graphic containing the text "Earth Day", but with the
letters all decorated with flowers and plants. If the text is
merely being used as a header, to spice up the page for graphical
users, then the correct alternative text is just the same text
"Earth Day", and no mention need be made of the decorations:
<h1><img src="earthdayheader.png" alt="Earth Day"></h1>
4.8.2.1.5 A graphical representation of some of the surrounding text
In many cases, the image is actually just supplementary, and
its presence merely reinforces the surrounding text. In these
cases, the alt attribute must be
present but its value must be the empty string.
In general, an image falls into this category if removing the
image doesn't make the page any less useful, but including the
image makes it a lot easier for users of visual browsers to
understand the concept.
A flowchart that repeats the previous paragraph in graphical form:
<p>The network passes data to the Tokeniser stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
the Tokeniser.</p>
<p><img src="images/parsing-model-overview.png" alt=""></p>
In these cases, it would be wrong to include alternative text
that consists of just a caption. If a caption is to be included,
then either the title attribute can
be used, or the figure and legend
elements can be used. In the latter case, the image would in fact
be a phrase or paragraph with an alternative graphical
representation, and would thus require alternative text.
<!-- Using the title="" attribute -->
<p>The network passes data to the Tokeniser stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
the Tokeniser.</p>
<p><img src="images/parsing-model-overview.png" alt=""
title="Flowchart representation of the parsing model."></p>
<!-- Using <figure> and <legend> -->
<p>The network passes data to the Tokeniser stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
the Tokeniser.</p>
<figure>
<img src="images/parsing-model-overview.png" alt="The Network leads
to the Tokeniser, which leads to the Tree Construction. The Tree
Construction leads to two items. The first is Script Execution, which
leads via document.write() back to the Tokeniser. The second item
from which Tree Construction leads is the DOM. The DOM is related to
the Script Execution.">
<legend>Flowchart representation of the parsing model.</legend>
</figure>
<!-- This is WRONG. Do not do this. Instead, do what the above examples do. -->
<p>The network passes data to the Tokeniser stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
the Tokeniser.</p>
<p><img src="images/parsing-model-overview.png"
alt="Flowchart representation of the parsing model."></p>
<!-- Never put the image's caption in the alt="" attribute! -->
A graph that repeats the previous paragraph in graphical form:
<p>According to a study covering several billion pages,
about 62% of documents on the Web in 2007 triggered the Quirks
rendering mode of Web browsers, about 30% triggered the Almost
Standards mode, and about 9% triggered the Standards mode.</p>
<p><img src="rendering-mode-pie-chart.png" alt=""></p>
In general, if an image is decorative but isn't especially
page-specific, for example an image that forms part of a site-wide
design scheme, the image should be specified in the site's CSS,
not in the markup of the document.
However, a decorative image that isn't discussed by the
surrounding text still has some relevance can be included in a page
using the img element. Such images are decorative, but
still form part of the content. In these cases, the alt attribute must be present but its
value must be the empty string.
Examples where the image is purely decorative despite being
relevant would include things like a photo of the Black Rock City
landscape in a blog post about an event at Burning Man, or an
image of a painting inspired by a poem, on a page reciting that
poem. The following snippet shows an example of the latter
case (only the first verse is included in this snippet):
<h1>The Lady of Shalott</h1>
<p><img src="shalott.jpeg" alt=""></p>
<p>On either side the river lie<br>
Long fields of barley and of rye,<br>
That clothe the wold and meet the sky;<br>
And through the field the road run by<br>
To many-tower'd Camelot;<br>
And up and down the people go,<br>
Gazing where the lilies blow<br>
Round an island there below,<br>
The island of Shalott.</p>
When a picture has been sliced into smaller image files that are
then displayed together to form the complete picture again, one of
the images must have its alt
attribute set as per the relevant rules that would be appropriate
for the picture as a whole, and then all the remaining images must
have their alt attribute set to
the empty string.
In the following example, a picture representing a company logo
for XYZ Corp has been split into two pieces,
the first containing the letters "XYZ" and the second with the word
"Corp". The alternative text ("XYZ Corp") is all in the first
image.
<h1><img src="logo1.png" alt="XYZ Corp"><img src="logo2.png" alt=""></h1>
In the following example, a rating is shown as three filled
stars and two empty stars. While the alternative text could have
been "★★★☆☆", the author has
instead decided to more helpfully give the rating in the form
"3/5". That is the alternative text of the first image, and the
rest have blank alternative text.
<p>Rating: <meter max=5 value=3><img src="1" alt="3/5"
><img src="1" alt=""><img src="1" alt=""><img src="0" alt=""
><img src="0" alt=""></meter></p>
Generally, image maps should be
used instead of slicing an image for links.
However, if an image is indeed sliced and any of the components
of the sliced picture are the sole contents of links, then one image
per link must have alternative text in its alt attribute representing the purpose
of the link.
In the following example, a picture representing the flying
spaghetti monster emblem, with each of the left noodly appendages
and the right noodly appendages in different images, so that the
user can pick the left side or the right side in an adventure.
<h1>The Church</h1>
<p>You come across a flying spaghetti monster. Which side of His
Noodliness do you wish to reach out for?</p>
<p><a href="?go=left" ><img src="fsm-left.png" alt="Left side. "></a
><img src="fsm-middle.png" alt=""
><a href="?go=right"><img src="fsm-right.png" alt="Right side."></a></p>
4.8.2.1.9 A key part of the content
In some cases, the image is a critical part of the
content. This could be the case, for instance, on a page that is
part of a photo gallery. The image is the whole point of
the page containing it.
How to provide alternative text for an image that is a key part
of the content depends on the image's provenance.
- The general case
-
When it is possible for detailed alternative text to be
provided, for example if the image is part of a series of
screenshots in a magazine review, or part of a comic strip, or is
a photograph in a blog entry about that photograph, text that
conveys can serve as a substitute for the image must be given as
the contents of the alt
attribute.
A screenshot in a gallery of screenshots for a new OS, with
some alternative text:
<figure>
<img src="KDE%20Light%20desktop.png"
alt="The desktop is blue, with icons along the left hand side in
two columns, reading System, Home, K-Mail, etc. A window is
open showing that menus wrap to a second line if they
cannot fit in the window. The window has a list of icons
along the top, with an address bar below it, a list of
icons for tabs along the left edge, a status bar on the
bottom, and two panes in the middle. The desktop has a bar
at the bottom of the screen with a few buttons, a pager, a
list of open applications, and a clock.">
<legend>Screenshot of a KDE desktop.</legend>
</figure>
A graph in a financial report:
<img src="sales.gif"
title="Sales graph"
alt="From 1998 to 2005, sales increased by the following percentages
with each year: 624%, 75%, 138%, 40%, 35%, 9%, 21%">
Note that "sales graph" would be inadequate alternative text
for a sales graph. Text that would be a good caption is
not generally suitable as replacement text.
- Images that defy a complete description
-
In certain cases, the nature of the image might be such that
providing thorough alternative text is impractical. For example,
the image could be indistinct, or could be a complex fractal, or
could be a detailed topographical map.
In these cases, the alt
attribute must contain some suitable alternative text, but it may
be somewhat brief.
Sometimes there simply is no text that can do justice to an
image. For example, there is little that can be said to usefully
describe a Rorschach inkblot test. However, a description, even
if brief, is still better than nothing:
<figure>
<img src="/commons/a/a7/Rorschach1.jpg" alt="A shape with left-right
symmetry with indistinct edges, with a small gap in the center, two
larger gaps offset slightly from the center, with two similar gaps
under them. The outline is wider in the top half than the bottom
half, with the sides extending upwards higher than the center, and
the center extending below the sides.">
<legend>A black outline of the first of the ten cards
in the Rorschach inkblot test.</legend>
</figure>
Note that the following would be a very bad use of alternative
text:
<!-- This example is wrong. Do not copy it. -->
<figure>
<img src="/commons/a/a7/Rorschach1.jpg" alt="A black outline
of the first of the ten cards in the Rorschach inkblot test.">
<legend>A black outline of the first of the ten cards
in the Rorschach inkblot test.</legend>
</figure>
Including the caption in the alternative text like this isn't
useful because it effectively duplicates the caption for users
who don't have images, taunting them twice yet not helping them
any more than if they had only read or heard the caption
once.
Another example of an image that defies full description is a
fractal, which, by definition, is infinite in complexity.
The following example shows one possible way of providing
alternative text for the full view of an image of the Mandelbrot
set.
<img src="ms1.jpeg" alt="The Mandelbrot set appears as a cardioid with
its cusp on the real axis in the positive direction, with a smaller
bulb aligned along the same center line, touching it in the negative
direction, and with these two shapes being surrounded by smaller bulbs
of various sizes.">
- Images whose contents are not known
-
In some unfortunate cases, there might be no alternative text
available at all, either because the image is obtained in some
automated fashion without any associated alternative text (e.g. a
Webcam), or because the page is being generated by a script using
user-provided images where the user did not provide suitable or
usable alternative text (e.g. photograph sharing sites), or
because the author does not himself know what the images represent
(e.g. a blind photographer sharing an image on his blog).
In such cases, the alt
attribute's value may be omitted, but one of the following
conditions must be met as well:
Such cases are to be kept to an absolute
minimum. If there is even the slightest possibility of the author
having the ability to provide real alternative text, then it would
not be acceptable to omit the alt
attribute.
A photo on a photo-sharing site, if the site received the
image with no metadata other than the caption:
<figure>
<img src="1100670787_6a7c664aef.jpg">
<legend>Bubbles traveled everywhere with us.</legend>
</figure>
It could also be marked up like this:
<article>
<h1>Bubbles traveled everywhere with us.</h1>
<img src="1100670787_6a7c664aef.jpg">
</article>
In either case, though, it would be better if a detailed
description of the important parts of the image obtained from the
user and included on the page.
A blind user's blog in which a photo taken by the user is
shown. Initially, the user might not have any idea what the photo
he took shows:
<article>
<h1>I took a photo</h1>
<p>I went out today and took a photo!</p>
<figure>
<img src="photo2.jpeg">
<legend>A photograph taken blindly from my front porch.</legend>
</figure>
</article>
Eventually though, the user might obtain a description of the
image from his friends and could then include alternative text:
<article>
<h1>I took a photo</h1>
<p>I went out today and took a photo!</p>
<figure>
<img src="photo2.jpeg" alt="The photograph shows my hummingbird
feeder hanging from the edge of my roof. It is half full, but there
are no birds around. In the background, out-of-focus trees fill the
shot. The feeder is made of wood with a metal grate, and it contains
peanuts. The edge of the roof is wooden too, and is painted white
with light blue streaks.">
<legend>A photograph taken blindly from my front porch.</legend>
</figure>
</article>
Sometimes the entire point of the image is that a textual
description is not available, and the user is to provide the
description. For instance, the point of a CAPTCHA image is to see
if the user can literally read the graphic. Here is one way to
mark up a CAPTCHA (note the title
attribute):
<p><label>What does this image say?
<img src="captcha.cgi?id=8934" title="CAPTCHA">
<input type=text name=captcha></label>
(If you cannot see the image, you can use an <a
href="?audio">audio</a> test instead.)</p>
Another example would be software that displays images and
asks for alternative text precisely for the purpose of then
writing a page with correct alternative text. Such a page could
have a table of images, like this:
<table>
<thead>
<tr> <th> Image <th> Description
<tbody>
<tr>
<td> <img src="2421.png" title="Image 640 by 100, filename 'banner.gif'">
<td> <input name="alt2421">
<tr>
<td> <img src="2422.png" title="Image 200 by 480, filename 'ad3.gif'">
<td> <input name="alt2422">
</table>
Notice that even in this example, as much useful information
as possible is still included in the title attribute.
Since some users cannot use images at all
(e.g. because they have a very slow connection, or because they
are using a text-only browser, or because they are listening to
the page being read out by a hands-free automobile voice Web
browser, or simply because they are blind), the alt attribute is only allowed to be
omitted rather than being provided with replacement text when no
alternative text is available and none can be made available, as
in the above examples. Lack of effort from the part of the author
is not an acceptable reason for omitting the alt attribute.
4.8.2.1.10 An image not intended for the user
Generally authors should avoid using img elements
for purposes other than showing images.
If an img element is being used for purposes other
than showing an image, e.g. as part of a service to count page
views, then the alt attribute must
be the empty string.
4.8.2.1.11 An image in an e-mail or document intended for a specific person who is known to be able to view images
When an image is included in a communication (such as an HTML
e-mail) aimed at someone who is known to be able to view images,
the alt attribute may be
omitted. However, even in such cases it is strongly recommended
that alternative text be included (as appropriate according to the
kind of image involved, as described in the above entries), so
that the e-mail is still usable should the user use a mail client
that does not support images, or should the e-mail be forwarded on
to other users whose abilities might not include easily seeing
images.
4.8.2.1.12 General guidelines
The most general rule for writing alternative text is that the
intent is that replacing every image with the text of its alt attribute not change the meaning of
the page.
So, in general, alternative text can be written by considering
what one would have written had one not been able to include the
image.
A corollary to this is that the alt attribute's value should never
contain text that could be considered the image's caption,
title, or legend. It is supposed to contain
replacement text that could be used by users instead of the
image; it is not meant to supplement the image. The title attribute can be used for
supplemental information.
One way to think of alternative text is to think
about how you would read the page containing the image to someone
over the phone, without mentioning that there is an image
present. Whatever you say instead of the image is typically a good
start for writing the alternative text.
4.8.2.1.13 Guidance for markup generators
Markup generators (such as WYSIWYG authoring tools) should,
wherever possible, obtain alternative text from their
users. However, it is recognised that in many cases, this will not
be possible.
For images that are the sole contents of links, markup generators
should examine the link target to determine the title of the target,
or the URL of the target, and use information obtained in this
manner as the alternative text.
As a last resort, implementors should either set the alt attribute to the empty string, under
the assumption that the image is a purely decorative image that
doesn't add any information but is still specific to the surrounding
content, or omit the alt attribute
altogther, under the assumption that the image is a key part of the
content.
Markup generators should generally avoid using the image's own
file name as the alternative text.
4.8.3 The iframe element4.8.3 iframe 要素
- Categories分類
- Embedded content.埋め込まれた内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where embedded content is expected.埋め込まれた内容が期待される場所。
- Content model:内容モデル:
- Text that conforms to the requirements given in the prose.本文中で述べる要件に適合するテキスト。
- Element-specific attributes:要素固有属性:
srcnamesandboxseamlesswidthheight- DOM interface:DOM 界面:
-
interface HTMLIFrameElement : HTMLElement {
attribute DOMString src;
attribute DOMString name;
attribute DOMString sandbox;
attribute boolean seamless;
attribute DOMString width;
attribute DOMString height;
};
Objects implementing the HTMLIFrameElement
interface must also implement the EmbeddingElement
interface defined in the Window Object specification. [WINDOW]HTMLIFrameElement 界面を実装するオブジェクトは、
Window オブジェクト仕様書で定義された EmbeddingElement
界面も実装しなければなりません。 [WINDOW]
The iframe element introduces a new nested
browsing context.
The src attribute
gives the address of a page that the nested browsing
context is to contain. The attribute, if present, must be a
valid URL. When the browsing context is created, if the
attribute is present, the user agent must navigate the
element's browsing context to the given URL, with
replacement enabled, and with the iframe
element's document's browsing context as the
source browsing context. If the user navigates away from this page, the
iframe's corresponding Window object will
reference new Document objects, but the src attribute will not change.
Whenever the src attribute
is set, the nested browsing context must be navigated to the URL given by
that attribute's value, with the iframe element's
document's browsing context as the source
browsing context.
If the src attribute is not
set when the element is created, the browsing context will remain at
the initial about:blank page.
The name
attribute, if present, must be a valid browsing context
name. When the browsing context is created, if the attribute
is present, the browsing context name must be set to
the value of this attribute; otherwise, the browsing context
name must be set to the empty string.
Whenever the name attribute
is set, the nested browsing context's name must be changed to the new
value. If the attribute is removed, the browsing context
name must be set to the empty string.
When content loads in an iframe, after any load events are fired within the content
itself, the user agent must fire a load event at the
iframe element. When content fails to load (e.g. due to
a network error), then the user agent must fire an error event at the element
instead.
When there is an active parser in the iframe, and
when anything in the iframe that is delaying the load
event in the iframe's browsing
context, the iframe must delay the load event.
If, during the handling of the load event, the browsing
context in the iframe is again navigated, that will further delay the
load event.
The sandbox
attribute, when specified, enables a set of extra restrictions on
any content hosted by the iframe. Its value must be an
unordered set of unique space-separated tokens. The
allowed values are allow-same-origin,
allow-forms,
and allow-scripts.
While the sandbox
attribute is specified, the iframe element's
nested browsing context, and all the browsing contexts
nested within it
(either directly or indirectly through other nested browsing
contexts) must have the following flags set:
- The sandboxed navigation browsing context flag
-
This flag prevents content from
navigating browsing contexts other than the sandboxed browsing
context itself (or browsing contexts further nested inside
it).
This flag also prevents content
from creating new auxiliary browsing contexts, e.g. using the
target attribute or the
window.open() method.
- The sandboxed plugins browsing context flag
-
This flag prevents content from instantiating plugins, whether using the embed element, the object element,
the applet
element, or through navigation of a nested
browsing context.
- The sandboxed annoyances browsing context flag
-
This flag prevents content from showing notifications outside of
the nested browsing context.
- The sandboxed origin browsing context flag, unless
the
sandbox attribute's
value, when split on
spaces, is found to have the allow-same-origin
keyword set
-
This flag forces content into a unique
origin for the purposes of the same-origin policy.
This flag also prevents script from
reading the document.cookies DOM
attribute.
The allow-same-origin
attribute is intended for two cases.
First, it can be used to allow content from the same site to
be sandboxed to disable scripting, while still allowing access to
the DOM of the sandboxed content.
Second, it can be used to embed content from a third-party
site, sandboxed to prevent that site from opening popup windows,
etc, without preventing the embedded page from communicating back
to its originating site, using the database APIs to store data,
etc.
- The sandboxed forms browsing context flag, unless
the
sandbox attribute's
value, when split on
spaces, is found to have the allow-forms
keyword set
-
This flag blocks form
submission.
- The sandboxed scripts browsing context flag, unless
the
sandbox attribute's
value, when split on
spaces, is found to have the allow-scripts
keyword set
-
This flag blocks script
execution.
These flags must not be set unless the conditions listed above
define them as being set.
In this example, some completely-unknown, potentially hostile,
user-provided HTML content is embedded in a page. Because it is
sandboxed, it is treated by the user agent as being from a unique
origin, despite the content being served from the same site. Thus
it is affected by all the normal cross-site restrictions. In
addition, the embedded page has scripting disabled, plugins
disabled, forms disabled, and it cannot navigate any frames or
windows other than itself (or any frames or windows it itself
embeds).
<p>We're not scared of you! Here is your content, unedited:</p>
<iframe sandbox src="getusercontent.cgi?id=12193"></iframe>
Note that cookies are still send to the server in the getusercontent.cgi request, though they are not
visible in the document.cookies DOM
attribute.
In this example, a gadget from another site is embedded. The
gadget has scripting and forms enabled, and the origin sandbox
restrictions are lifted, allowing the gadget to communicate with
its originating server. The sandbox is still useful, however, as it
disables plugins and popups, thus reducing the risk of the user
being exposed to malware and other annoyances.
<iframe sandbox="allow-same-origin allow-forms allow-scripts"
src="http://maps.example.com/embedded.html"></iframe>
The seamless
attribute is a boolean attribute. When specified, it indicates that
the iframe element's browsing context is
to be rendered in a manner that makes it appear to be part of the
containing document (seamlessly included in the parent
document). Specifically, when the attribute is set on an element and
while the browsing context's active
document has the same origin as the
iframe element's document, or the browsing
context's active document's address has the
same origin as the iframe element's
document, the following requirements apply:
The user agent must set the seamless browsing
context flag to true for that browsing
context. This will cause links to
open in the parent browsing context.
In a CSS-supporting user agent: the user agent must add all
the style sheets that apply to the iframe element to
the cascade of the active document of the
iframe element's nested browsing context,
at the appropriate cascade levels, before any style sheets
specified by the document itself.
In a CSS-supporting user agent: the user agent must, for the
purpose of CSS property inheritance only, treat the root element of
the active document of the iframe
element's nested browsing context as being a child of
the iframe element. (Thus inherited properties on the
root element of the document in the iframe will
inherit the computed values of those properties on the
iframe element instead of taking their initial
values.)
In visual media, in a CSS-supporting user agent: the user agent
should set the intrinsic width of the iframe to the
width that the element would have if it was a non-replaced
block-level element with 'width: auto'.
In visual media, in a CSS-supporting user agent: the user agent
should set the intrinsic height of the iframe to the
height of the bounding box around the content rendered in the
iframe at its current width.
-
In visual media, in a CSS-supporting user agent: the user agent
must force the height of the initial containing block of the
active document of the nested browsing
context of the iframe to zero.
This is intended to get around the otherwise
circular dependency of percentage dimensions that depend on the
height of the containing block, thus affecting the height of the
document's bounding box, thus affecting the height of the
viewport, thus affecting the size of the initial containing
block.
In speech media, the user agent should render the nested
browsing context without announcing that it is a separate
document.
-
User agents should, in general, act as if the active
document of the iframe's nested browsing
context was part of the document that the
iframe is in.
For example if the user agent supports listing
all the links in a document, links in "seamlessly" nested
documents would be included in that list without being
significantly distinguished from links in the document itself.
Parts of the above might get moved into the
rendering section at some point.
If the attribute is not specified, or if the origin
conditions listed above are not met, then the user agent should
render the nested browsing context in a manner that is
clearly distinguishable as a separate browsing context,
and the seamless browsing context flag must be set to
false for that browsing context.
It is important that user agents recheck the
above conditions whenever the active document of the
nested browsing context of the iframe
changes, such that the seamless browsing context flag
gets unset if the nested browsing context is navigated to another origin.
In this example, the site's navigation is embedded using a
client-side include using an iframe. Any links in the
iframe will, in new user agents, be automatically
opened in the iframe's parent browsing context; for
legacy user agents, the site could also include a base
element with a target
attribute with the value _parent. Similarly,
in new user agents the styles of the parent page will be
automatically applied to the contents of the frame, but to support
legacy user agents authors might wish to include the styles
explicitly.
<nav><iframe seamless src="nav.include.html"></iframe></nav>
The iframe element supports dimension
attributes for cases where the embedded content has specific
dimensions (e.g. ad units have well-defined dimensions).
An iframe element never has fallback
content, as it will always create a nested browsing
context, regardless of whether the specified initial contents
are successfully used.
Descendants of iframe elements represent
nothing. (In legacy user agents that do not support
iframe elements, the contents would be parsed as markup
that could act as fallback content.)
The content model of iframe elements is text, except
that the text must be such that ... anyone
have any bright ideas?
The HTML parser treats markup inside
iframe elements as text.
The DOM attributes src, name, sandbox, and seamless must
reflect the respective content attributes of the same
name.
4.8.4 The embed element4.8.4 embed 要素
- Categories分類
- Embedded content.埋め込まれた内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where embedded content is expected.埋め込まれた内容が期待される場所。
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
srctypewidthheight- Any other attribute that has no namespace (see prose).名前空間を持たない他の任意の属性 (本文参照)。
- DOM interface:DOM 界面:
-
interface HTMLEmbedElement : HTMLElement {
attribute DOMString src;
attribute DOMString type;
attribute DOMString width;
attribute DOMString height;
};
Depending on the type of content instantiated by the
embed element, the node may also support other
interfaces.節点は、 embed 要素により実現値化される内容の型によって、
他の界面にも対応して構いません。
The embed element represents an integration point
for an external (typically non-HTML) application or interactive
content.
The src attribute
gives the address of the resource being embedded. The attribute, if
present, must contain a valid URL.
The type
attribute, if present, gives the MIME type of the plugin to
instantiate. The value must be a valid MIME type, optionally with
parameters. If both the type
attribute and the src attribute
are present, then the type
attribute must specify the same type as the explicit Content-Type metadata of the
resource given by the src
attribute. [RFC2046]
When the element is created with neither a src attribute nor a type attribute, and when attributes
are removed such that neither attribute is present on the element
anymore, any plugins instantiated for the element must be removed,
and the embed element represents nothing.
When the sandboxed plugins browsing
context flag is set on the browsing context for
which the embed element's document is the active
document, then the user agent must render the
embed element in a manner that conveys that the
plugin was disabled. The user agent may offer the user
the option to override the sandbox and instantiate the
plugin anyway; if the user invokes such an option, the
user agent must act as if the sandboxed plugins browsing
context flag was not set for the purposes of this
element.
Plugins are disabled in sandboxed browsing
contexts because they might not honor the restrictions imposed by
the sandbox (e.g. they might allow scripting even when scripting in
the sandbox is disabled). User agents should convey the danger of
overriding the sandbox to the user if an option to do so is
provided.
When the element is created with a src attribute, and whenever the src attribute is subsequently set, and
whenever the type attribute is
set or removed while the element has a src attribute, if the element is not
in a sandboxed browsing context, user agents should
fetch the specified resource, find and instantiate an
appropriate plugin based on the content's type, and hand that
plugin the content of the resource, replacing any
previously instantiated plugin for the element.
Fetching the resource must delay the load event.
The type of the content
being embedded is defined as follows:
If the element has a type attribute, and that attribute's
value is a type that a plugin supports, then the value
of the type attribute is the
content's type.
-
Otherwise, if the <path>
component of the URL of the specified resource matches a pattern that a
plugin supports, then the content's type
is the type that that plugin can handle.
For example, a plugin might say that it can
handle resources with <path>
components that end with the four character string ".swf".
It would be better if browsers didn't do
extension sniffing like this, and only based their decision on the
actual contents of the resource. Couldn't we just apply the
sniffed type of a resource steps?
Otherwise, if the specified resource has explicit Content-Type metadata, then
that is the content's type.
Otherwise, the content has no type and there can be no
appropriate plugin for it.
Whether the resource is fetched successfully or not (e.g. whether
the response code was a 2xx code or equivalent) must be
ignored when determining the resource's type and when handing the
resource to the plugin.
This allows servers to return data for plugins even
with error responses (e.g. HTTP 500 Internal Server Error codes can
still contain plugin data).
When the element is created with a type attribute and no src attribute, and whenever the type attribute is subsequently set,
so long as no src attribute is
set, and whenever the src
attribute is removed when the element has a type attribute, if the element is not
in a sandboxed browsing context, user agents should find and
instantiate an appropriate plugin based on the value of
the type attribute.
Any (namespace-less) attribute may be specified on the
embed element, so long as its name is
XML-compatible and contains no characters in the range
U+0041 .. U+005A (LATIN CAPITAL LETTER A LATIN CAPITAL LETTER
Z).
All attributes in HTML documents get
lowercased automatically, so the restriction on uppercase letters
doesn't affect such documents.
The user agent should pass the names and values of all the
attributes of the embed element that have no namespace
to the plugin used, when it is instantiated.
If the plugin instantiated for the
embed element supports a scriptable interface, the
HTMLEmbedElement object representing the element should
expose that interface while the element is instantiated.
The embed element has no fallback
content. If the user agent can't find a suitable plugin, then
the user agent must use a default plugin. (This default could be as
simple as saying "Unsupported Format".)
The embed element supports dimension
attributes.
The DOM attributes src and type each must
reflect the respective content attributes of the same
name.
4.8.5 The object element4.8.5 object 要素
- Categories分類
- Embedded content.埋め込まれた内容。
- Listed, submittable, form-associated element.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where embedded content is expected.埋め込まれた内容が期待される場所。
- Content model:内容モデル:
- Zero or more
param elements, then, transparent.零個以上の param 要素の後、
透過。
- Element-specific attributes:要素固有属性:
datatypenameusemapformwidthheight- DOM interface:DOM 界面:
-
interface HTMLObjectElement : HTMLElement {
attribute DOMString data;
attribute DOMString type;
attribute DOMString name;
attribute DOMString useMap;
readonly attribute HTMLFormElement form;
attribute DOMString width;
attribute DOMString height;
};
Objects implementing the HTMLObjectElement
interface must also implement the EmbeddingElement
interface defined in the Window Object specification. [WINDOW]HTMLObjectElement 界面を実装するオブジェクトは、
Window オブジェクト仕様書で定義された EmbeddingElement
界面も実装しなければなりません。 [WINDOW]
Depending on the type of content instantiated by the
object element, the node may also support other
interfaces.節点は、 object 要素により実現値化される内容の型によって、他の界面にも対応して構いません。
The object element can represent an external
resource, which, depending on the type of the resource, will either
be treated as an image, as a nested browsing context,
or as an external resource to be processed by a
plugin.
The data
attribute, if present, specifies the address of the resource. If
present, the attribute must be a valid URL.
The type
attribute, if present, specifies the type of the resource. If
present, the attribute must be a valid MIME type, optionally with
parameters. [RFC2046]
One or both of the data and
type attributes must be
present.
The name
attribute, if present, must be a valid browsing context
name.
When the element is created, and subsequently whenever the classid attribute changes or is
removed, or, if the classid
attribute is not present, whenever the data attribute changes or is
removed, or, if neither classid attribute nor the data attribute are present, whenever
the type attribute changes or
is removed, the user agent must run the following steps to determine
what the object element represents:
-
If the element has an ancestor object element that
is not showing its fallback content, then
jump to the last step in the overall set of steps (fallback).
-
If the classid
attribute is present, and has a value that isn't the empty string,
then: if the user agent can find a plugin suitable
according to the value of the classid attribute, and plugins aren't being sandboxed,
then that plugin should be
used, and the value of the data attribute, if any, should be
passed to the plugin. If no suitable
plugin can be found, or if the plugin
reports an error, jump to the last step in the overall set of
steps (fallback).
If the data attribute
is present, then:
If the type
attribute is present and its value is not a type that the user
agent supports, and is not a type that the user agent can find a
plugin for, then the user agent may jump to the last
step in the overall set of steps (fallback) without fetching the
content to examine its real type.
-
Fetch the resource specified by the data attribute.
The fetching of the resource must delay the load event.
If the resource is not yet available (e.g. because the
resource was not available in the cache, so that loading the
resource required making a request over the network), then jump
to the last step in the overall set of steps (fallback). When the
resource becomes available, or if the load fails, restart this
algorithm from this step. Resources can load incrementally; user
agents may opt to consider a resource "available" whenever enough
data has been obtained to begin processing the resource.
If the load failed (e.g. an HTTP 404 error, a DNS error),
fire an error event
at the element, then jump to the last step in the overall set of
steps (fallback).
Determine the resource type, as follows:
-
Let the resource type be unknown.
-
If the resource has associated
Content-Type metadata, then let the resource type be the type specified in the resource's Content-Type
metadata.
-
If the resource type is unknown or
"application/octet-stream" and there is
a type attribute present
on the object element, then change the resource type to instead be the type specified
in that type
attribute.
Otherwise, if the resource type is
"application/octet-stream" but there is
no type attribute on the
object element, then change the resource type to be unknown, so that the
sniffing rules in the next step are invoked.
-
If the resource type is still unknown,
then change the resource type to instead
be the sniffed type
of the resource.
Handle the content as given by the first of the following
cases that matches:
- If the resource type can be handled by
a plugin and plugins aren't being
sandboxed
-
The user agent should use that
plugin and pass the content of the resource to that
plugin. If the plugin reports an
error, then jump to the last step in the overall set of steps
(fallback).
- If the resource type is an XML MIME
type
- If the resource type is HTML
- If the resource type does not start with
"
image/"
-
The object element must be associated with a
nested browsing context, if it does not already
have one. The element's nested browsing context
must then be navigated to the
given resource, with replacement enabled, and
with the object element's document's
browsing context as the source browsing
context. (The data attribute of the
object element doesn't get updated if the
browsing context gets further navigated to other
locations.)
If the name attribute
is present, the browsing context name must be set
to the value of this attribute; otherwise, the browsing
context name must be set to the empty string.
navigation might end up treating it as
something else, because it can do sniffing. how should we
handle that?
- If the resource type starts with
"
image/", and support for images has not been
disabled
-
Apply the image
sniffing rules to determine the type of the image.
The object element represents the specified
image. The image is not a nested browsing
context.
If the image cannot be rendered, e.g. because it is
malformed or in an unsupported format, jump to the last step
in the overall set of steps (fallback).
- Otherwiseそれ以外の場合
-
The given resource type is not
supported. Jump to the last step in the overall set of steps
(fallback).
The element's contents are not part of what the
object element represents.
Once the resource is completely loaded, fire a load event at the
element.
If the data attribute
is absent but the type
attribute is present, plugins
aren't being sandboxed, and the user agent can find a plugin
suitable according to the value of the type attribute, then that plugin
should be used. If no suitable plugin
can be found, or if the plugin reports an error, jump to the next
step (fallback).
(Fallback.) The object element represents what
the element's contents represent, ignoring any leading
param element children. This is the element's
fallback content.
When the algorithm above instantiates a
plugin, the user agent should pass the names and values
of all the attributes on the element, and all the names and
values of parameters
given by param elements that are children of the
object element, in tree order, to the
plugin used. If the plugin supports a
scriptable interface, the HTMLObjectElement object
representing the element should expose that interface. The
plugin is not a nested browsing
context.
If the sandboxed plugins browsing
context flag is set on the browsing context for
which the object element's document is the active
document, then the steps above must always act as if they had
failed to find a plugin, even if one would otherwise have been
used.
Due to the algorithm above, the contents of object
elements act as fallback content, used only when
referenced resources can't be shown (e.g. because it returned a 404
error). This allows multiple object elements to be
nested inside each other, targeting multiple user agents with
different capabilities, with the user agent picking the first one it
supports.
Whenever the name attribute
is set, if the object element has a nested
browsing context, its name must be changed to the new value. If the attribute
is removed, if the object element has a browsing
context, the browsing context name must be set
to the empty string.
The usemap attribute,
if present while the object element represents an
image, can indicate that the object has an associated image
map. The attribute must be ignored if the object
element doesn't represent an image.
The form attribute is used to
explicitly associate the object element with its
form owner.
Constraint validation: object
elements are always barred from constraint
validation.
The object element supports dimension
attributes.
The DOM attributes data, type, name, and useMap each must
reflect the respective content attributes of the same
name.
In the following example, a Java applet is embedded in a page
using the object element. (Generally speaking, it is
better to avoid using applets like these and instead use native
JavaScript and HTML to provide the functionality, since that way
the application will work on all Web browsers without requiring a
third-party plugin. Many devices, especially embedded devices, do
not support third-party technologies like Java.)
<figure>
<object type="application/x-java-applet">
<param name="code" value="MyJavaClass">
<p>You do not have Java available, or it is disabled.</p>
</object>
<legend>My Java Clock</legend>
</figure>
In this example, an HTML page is embedded in another using the
object element.
<figure>
<object data="clock.html"></object>
<legend>My HTML Clock</legend>
</figure>
4.8.6 The param element4.8.6 param 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of an
object element, before any flow content.
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
namevalue- DOM interface:DOM 界面:
-
interface HTMLParamElement : HTMLElement {
attribute DOMString name;
attribute DOMString value;
};
The param element defines parameters for plugins
invoked by object elements.
The name
attribute gives the name of the parameter.
The value
attribute gives the value of the parameter.
Both attributes must be present. They may have any value.
If both attributes are present, and if the parent element of the
param is an object element, then the
element defines a parameter with the given
name/value pair.
The DOM attributes name and value must both
reflect the respective content attributes of the same
name.
4.8.7 The video element4.8.7 video 要素
- Categories分類
- Embedded content.埋め込まれた内容。
- If the element has a
controls attribute: Interactive content.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where embedded content is expected.埋め込まれた内容が期待される場所。
- Content model:内容モデル:
- If the element has a
src attribute: transparent.
- If the element does not have a
src attribute: one or more source elements, then, transparent.
- Element-specific attributes:要素固有属性:
srcposterautoplayloopcontrolswidthheight- DOM interface:DOM 界面:
-
interface HTMLVideoElement : HTMLMediaElement {
attribute DOMString width;
attribute DOMString height;
readonly attribute unsigned long videoWidth;
readonly attribute unsigned long videoHeight;
attribute DOMString poster;
};
A video element represents a video or movie.
Content may be provided inside the video
element. User agents should not show this content to the user; it is
intended for older Web browsers which do not support
video, so that legacy video plugins can be tried, or to
show text to the users of these older browser informing them of how
to access the video contents.
In particular, this content is not fallback
content intended to address accessibility concerns. To make
video content accessible to the blind, deaf, and those with other
physical or cognitive disabilities, authors are expected to provide
alternative media streams and/or to embed accessibility aids (such
as caption or subtitle tracks) into their media streams.
The video element is a media element
whose media data is ostensibly video data, possibly
with associated audio data.
The src, autoplay, loop, and controls attributes are the attributes common to all media
elements.
The poster
attribute gives the address of an image file that the user agent can
show while no video data is available. The attribute, if present,
must contain a valid URL. If the specified resource is
to be used, it must be fetched when the
element is created or when the poster attribute is set. The
poster frame is then the image obtained from that
resource, if any.
The image given by the poster attribute, the poster
frame, is intended to be a representative frame of the video
(typically one of the first non-blank frames) that gives the user an
idea of what the video is like.
The poster DOM
attribute must reflect the poster content attribute.poster DOM 属性は poster 内容属性を反映しなければなりません。
When no video data is available (the element's readyState attribute is either
HAVE_NOTHING or HAVE_METADATA),
video elements represent either the poster
frame, or nothing.
When a video element is paused and the current playback position is the first
frame of video, the element represents either the frame of video
corresponding to the current
playback position or the poster frame, at the
discretion of the user agent.
Notwithstanding the above, the poster frame should
be preferred over nothing, but the poster frame should
not be shown again after a frame of video has been shown.
When a video element is paused at any other position, the
element represents the frame of video corresponding to the current playback position,
or, if that is not yet available (e.g. because the video is seeking
or buffering), the last frame of the video to have been
rendered.
When a video element is potentially
playing, it represents the frame of video at the continuously
increasing "current"
position. When the current playback position
changes such that the last frame rendered is no longer the frame
corresponding to the current playback position in the
video, the new frame must be rendered. Similarly, any audio
associated with the video must, if played, be played synchronized
with the current playback position, at the specified
volume with the specified
mute state.
When a video element is neither potentially
playing nor paused
(e.g. when seeking or stalled), the element represents the last
frame of the video to have been rendered.
Which frame in a video stream corresponds to a
particular playback position is defined by the video stream's
format.
In addition to the above, the user agent may provide messages to
the user (such as "buffering", "no video loaded", "error", or more
detailed information) by overlaying text or icons on the video or
other areas of the element's playback area, or in another
appropriate manner.
User agents that cannot render the video may instead make the
element represent a link to an external video playback utility or to
the video data itself.
The intrinsic
width and intrinsic height of the
media resource are the dimensions of the resource in
CSS pixels after taking into account the resource's dimensions,
aspect ratio, clean aperture, resolution, and so forth, as defined
for the format used by the resource..
The videoWidth DOM
attribute must return the intrinsic width of the
video in CSS pixels. The videoHeight DOM
attribute must return the intrinsic height of
the video in CSS pixels. If the element's readyState attribute is HAVE_NOTHING, then the
attributes must return 0.
The video element supports dimension
attributes.
Video content should be rendered inside the element's playback
area such that the video content is shown centered in the playback
area at the largest possible size that fits completely within it,
with the video content's aspect ratio being preserved. Thus, if the
aspect ratio of the playback area does not match the aspect ratio of
the video, the video will be shown letterboxed or pillarboxed. Areas
of the element's playback area that do not contain the video
represent nothing.
The intrinsic width of a video element's playback
area is the intrinsic
width of the video resource, if that is available; otherwise
it is the intrinsic width of the poster frame, if that
is available; otherwise it is 300 CSS pixels.
The intrinsic height of a video element's playback
area is the intrinsic
height of the video resource, if that is available; otherwise
it is the intrinsic height of the poster frame, if that
is available; otherwise it is 150 CSS pixels.
User agents should provide controls to enable or disable the
display of closed captions associated with the video stream, though
such features should, again, not interfere with the page's normal
rendering.
User agents may allow users to view the video content in manners
more suitable to the user (e.g. full-screen or in an independent
resizable window). As for the other user interface features,
controls to enable this should not interfere with the page's normal
rendering unless the user agent is exposing a user interface. In such an
independent context, however, user agents may make full user
interfaces visible, with, e.g., play, pause, seeking, and volume
controls, even if the controls attribute is absent.
User agents may allow video playback to affect system features
that could interfere with the user's experience; for example, user
agents could disable screensavers while video playback is in
progress.
User agents should not provide a public API to
cause videos to be shown full-screen. A script, combined with a
carefully crafted video file, could trick the user into thinking a
system-modal dialog had been shown, and prompt the user for a
password. There is also the danger of "mere" annoyance, with pages
launching full-screen videos when links are clicked or pages
navigated. Instead, user-agent specific interface features may be
provided to easily allow the user to obtain a full-screen playback
mode.
The spec does not currently define the
interaction of the "controls" attribute with the "height" and
"width" attributes. This will likely be defined in the rendering
section based on implementation experience. So far, browsers seem to
be making the controls overlay-only, thus somewhat sidestepping the
issue.
4.8.7.1 Video and audio codecs for video elements
User agents may support any video and audio codecs and container
formats.
It would be helpful for interoperability if all
browsers could support the same codecs. However, there are no known
codecs that satisfy all the current players: we need a codec that is
known to not require per-unit or per-distributor licensing, that is
compatible with the open source development model, that is of
sufficient quality as to be usable, and that is not an additional
submarine patent risk for large companies. This is an ongoing issue
and this section will be updated once more information is
available.
Certain user agents might support no codecs at all,
e.g. text browsers running over SSH connections.
4.8.8 The audio element4.8.8 audio 要素
- Categories分類
- Embedded content.埋め込まれた内容。
- If the element has a
controls attribute: Interactive content.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where embedded content is expected.埋め込まれた内容が期待される場所。
- Content model:内容モデル:
- If the element has a
src attribute: transparent.
- If the element does not have a
src attribute: one or more source elements, then, transparent.
- Element-specific attributes:要素固有属性:
srcautoplayloopcontrols- DOM interface:DOM 界面:
-
[NamedConstructor=Audio(),
NamedConstructor=Audio(in DOMString src)]
interface HTMLAudioElement : HTMLMediaElement {
// no members
};
An audio element represents a sound or audio
stream.
Content may be provided inside the audio
element. User agents should not show this content to the user; it is
intended for older Web browsers which do not support
audio, so that legacy audio plugins can be tried, or to
show text to the users of these older browser informing them of how
to access the audio contents.
In particular, this content is not fallback
content intended to address accessibility concerns. To make
audio content accessible to the deaf or to those with other physical
or cognitive disabilities, authors are expected to provide
alternative media streams and/or to embed accessibility aids (such
as transcriptions) into their media streams.
The audio element is a media element
whose media data is ostensibly audio data.
The src, autoplay, loop, and controls attributes are the attributes common to all media
elements.
When an audio element is potentially
playing, it must have its audio data played synchronized with
the current playback position, at the specified volume with the specified mute state.
When an audio element is not potentially
playing, audio must not play for the element.
Two constructors are provided for creating
HTMLAudioElement objects (in addition to the factory
methods from DOM Core such as createElement()): Audio() and Audio(src). When invoked as constructors,
these must return a new HTMLAudioElement object (a new
audio element). If the src argument
is present, the object created must have its src content attribute set to the
provided value, and the user agent must invoke the load() method on the object before
returning.
4.8.8.1 Audio codecs for audio elements
User agents may support any audio codecs and container
formats.
User agents must support the WAVE container format with audio
encoded using the PCM format.
4.8.9 The source element4.8.9 source 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a media element, before any flow content.
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
srctypemedia- DOM interface:DOM 界面:
-
interface HTMLSourceElement : HTMLElement {
attribute DOMString src;
attribute DOMString type;
attribute DOMString media;
};
The source element allows authors to specify
multiple media resources for
media elements.
The src attribute
gives the address of the media resource. The value must
be a valid URL. This attribute must be present.
The type
attribute gives the type of the media resource, to help
the user agent determine if it can play this media
resource before fetching it. If specified, its value must be
a MIME type. The codecs parameter may be
specified and might be necessary to specify exactly how the resource
is encoded. [RFC2046] [RFC4281]
The following list shows some examples of how to use the codecs= MIME parameter in the type attribute.
- H.264 Simple baseline profile video (main and extended video compatible) level 3 and Low-Complexity AAC audio in MP4 container
<source src="video.mp4" type="video/mp4; codecs="avc1.42E01E, mp4a.40.2"">
- H.264 Extended profile video (baseline-compatible) level 3 and Low-Complexity AAC audio in MP4 container
<source src="video.mp4" type="video/mp4; codecs="avc1.58A01E, mp4a.40.2"">
- H.264 Main profile video level 3 and Low-Complexity AAC audio in MP4 container
<source src="video.mp4" type="video/mp4; codecs="avc1.4D401E, mp4a.40.2"">
- H.264 "High" profile video (incompatible with main, baseline, or extended profiles) level 3 and Low-Complexity AAC audio in MP4 container
<source src="video.mp4" type="video/mp4; codecs="avc1.64001E, mp4a.40.2"">
- MPEG-4 Visual Simple Profile Level 0 video and Low-Complexity AAC audio in MP4 container
<source src="video.mp4" type="video/mp4; codecs="mp4v.20.8, mp4a.40.2"">
- MPEG-4 Advanced Simple Profile Level 0 video and Low-Complexity AAC audio in MP4 container
<source src="video.mp4" type="video/mp4; codecs="mp4v.20.240, mp4a.40.2"">
- MPEG-4 Visual Simple Profile Level 0 video and AMR audio in 3GPP container
<source src="video.3gp" type="video/3gpp; codecs="mp4v.20.8, samr"">
- Theora video and Vorbis audio in Ogg container
<source src="video.ogv" type="video/ogg; codecs="theora, vorbis"">
- Theora video and Speex audio in Ogg container
<source src="video.ogv" type="video/ogg; codecs="theora, speex"">
- Vorbis audio alone in Ogg container
<source src="audio.ogg" type="audio/ogg; codecs=vorbis">
- Speex audio alone in Ogg container
<source src="audio.spx" type="audio/ogg; codecs=speex">
- FLAC audio alone in Ogg container
<source src="audio.oga" type="audio/ogg; codecs=flac">
- Dirac video and Vorbis audio in Ogg container
<source src="video.ogv" type="video/ogg; codecs="dirac, vorbis"">
- Theora video and Vorbis audio in Matroska container
<source src="video.mkv" type="video/x-matroska; codecs="theora, vorbis"">
The media
attribute gives the intended media type of the media
resource, to help the user agent determine if this
media resource is useful to the user before fetching
it. Its value must be a valid media query. [MQ]
If a source element is inserted into a media
element that is already in a document and whose networkState is in the NETWORK_EMPTY state, the user
agent must queue a task that implicitly invokes the
load() method on the media
element, and ignores any resulting exceptions. The task
source for this task is the media element's own
media element new resource task source.
The DOM attributes src, type, and media must
reflect the respective content attributes of the same
name.
Media elements implement the
following interface:
interface HTMLMediaElement : HTMLElement {
// error state
readonly attribute MediaError error;
// network state
attribute DOMString src;
readonly attribute DOMString currentSrc;
const unsigned short NETWORK_EMPTY = 0;
const unsigned short NETWORK_IDLE = 1;
const unsigned short NETWORK_LOADING = 2;
const unsigned short NETWORK_LOADED = 3;
readonly attribute unsigned short networkState;
readonly attribute float bufferingRate;
readonly attribute boolean bufferingThrottled;
readonly attribute TimeRanges buffered;
void load();
DOMString canPlayType(in DOMString type);
// ready state
const unsigned short HAVE_NOTHING = 0;
const unsigned short HAVE_METADATA = 1;
const unsigned short HAVE_CURRENT_DATA = 2;
const unsigned short HAVE_FUTURE_DATA = 3;
const unsigned short HAVE_ENOUGH_DATA = 4;
readonly attribute unsigned short readyState;
readonly attribute boolean seeking;
// playback state
attribute float currentTime;
readonly attribute float duration;
readonly attribute boolean paused;
attribute float defaultPlaybackRate;
attribute float playbackRate;
readonly attribute TimeRanges played;
readonly attribute TimeRanges seekable;
readonly attribute boolean ended;
attribute boolean autoplay;
attribute boolean loop;
void play();
void pause();
// cue ranges
void addCueRange(in DOMString className, in DOMString id, in float start, in float end, in boolean pauseOnExit, in CueRangeCallback enterCallback, in CueRangeCallback exitCallback);
void removeCueRanges(in DOMString className);
// controls
attribute boolean controls;
attribute float volume;
attribute boolean muted;
};
// CueRangeCallback waiting on WebIDL
The media element attributes, src, autoplay, loop, and controls, apply to all media elements. They are defined in
this section.
Media elements are used to
present audio data, or video and audio data, to the user. This is
referred to as media data in this section, since this
section applies equally to media
elements for audio or for video. The term media
resource is used to refer to the complete set of media data,
e.g. the complete video file, or complete audio file.
Media elements use two task queues, the media element event
task source for asynchronous events and callbacks, and the
media element new resource task source for handling
implicit loads. Unless otherwise specified, the task
source for all the tasks queued in this section and its subsections is the
media element event task source.
4.8.10.1 Error codes
All media elements have an
associated error status, which records the last error the element
encountered since the load()
method was last invoked. The error attribute, on
getting, must return the MediaError object created for
this last error, or null if there has not been an error.
interface MediaError {
const unsigned short MEDIA_ERR_ABORTED = 1;
const unsigned short MEDIA_ERR_NETWORK = 2;
const unsigned short MEDIA_ERR_DECODE = 3;
const unsigned short MEDIA_ERR_NONE_SUPPORTED = 4;
readonly attribute unsigned short code;
};
The code
attribute of a MediaError object must return the code
for the error, which must be one of the following:
MEDIA_ERR_ABORTED (numeric value 1)MEDIA_ERR_ABORTED (数値 1)- The fetching process for the media resource was
aborted by the user agent at the user's request.
MEDIA_ERR_NETWORK (numeric value 2)MEDIA_ERR_NETWORK (数値 2)- A network error of some description caused the user agent to
stop fetching the media resource, after the resource
was established to be usable.
MEDIA_ERR_DECODE (numeric value 3)MEDIA_ERR_DECODE (数値 3)- An error of some description occurred while decoding the
media resource, after the resource was established to
be usable.
MEDIA_ERR_NONE_SUPPORTED (numeric value 4)MEDIA_ERR_NONE_SUPPORTED (数値 4)- No suitable media resource could be found.
The src content
attribute on media elements gives
the address of the media resource (video, audio) to show. The
attribute, if present, must contain a valid URL.
If the src attribute of a
media element that is already in a document and whose
networkState is in the
NETWORK_EMPTY state is
added, changed, or removed, the user agent must queue a
task that implicitly invokes the load() method on the media
element, and ignores any resulting exceptions. The task
source for this task is the media element's own
media element new resource task source.
If a src
attribute is specified, the resource it specifies is the media
resource that will be used. Otherwise, the resource specified
by the first suitable source element child of the
media element is the one used.
The src DOM
attribute on media elements must
reflect the respective content attribute of the same
name.
The currentSrc DOM
attribute is initially the empty string. Its value is changed by the
algorithm for the load() method
defined below.
To generate the list of potential media resources for
a media element, a user agent must use the following
steps. These steps return a list of absolute URLs giving a resource's address.
-
If the media element has a src attribute, then run these
substeps:
Resolve the
URL given in that attribute.
If that is successful, then return a list consisting of
only one entry, the resulting absolute URL as the
resource's address.
Otherwise, return the empty list.
Abort the algorithm.
Otherwise, the source elements will be used.
If the media element has no source
element children, then return the empty the list and abort these
steps.
Let result be an empty list.
Let candidate be the first
source element child in the media
element.
Loop: this is the start of the loop that looks at the
source elements.
-
If all the following conditions are true:
The candidate element has a src attribute.
Resolving the
URL given by the candidate
element's src attribute does
not fail.
The candidate element either has no type attribute, or its type attribute's value, when
parsed as a MIME type (including any codecs described by the
codec parameter), does not represent
a type that the user agent knows it cannot
render.
The candidate element either has no media attribute, or its media attribute's value, when
processed according to the rules for media
queries, matches the current environment. [MQ]
...then append the absolute URL resulting from
resolving the URL
given in that candidate element's src attribute to the result list.
Let candidate be the next
source element child in the media
element, or null if there are no more such
children.
If candidate is not null, return to the
step labeled loop.
Return result.result を返します。
A media resource can be described in terms of its
type, specifically a MIME type, optionally with a codecs parameter. [RFC2046] [RFC4281].
Types are usually somewhat incomplete descriptions; for example
"video/mpeg" doesn't say anything except what
the container type is, and even a type like "video/mp4; codecs="avc1.42E01E,
mp4a.40.2"" doesn't include information like the actual
bitrate (only the maximum bitrate). Thus, given a type, a user agent
can often only know whether it might be able to play
media of that type (with varying levels of confidence), or whether
it definitely cannot play media of that type.
A type that the user agent knows it cannot render is
one that describes a resource that the user agent definitely does
not support, for example because it doesn't recognise the container
type, or it doesn't support the listed codecs.
The canPlayType(type) method must return the string
"no" if type is a
type that the user agent knows it cannot render; it must
return "probably" if the user agent is
confident that the type represents a media resource
that it can render if used in with this audio or
video element; and it must return "maybe" otherwise. Implementors are encouraged to
return "maybe" unless the type can be
confidently established as being supported or not. Generally, a user
agent should never return "probably" if the
type doesn't have a codecs parameter.
This script tests to see if the user agent supports a
(fictional) new format to dynamically decide whether to use a
video element or a plugin:
<section id="video">
<p><a href="playing-cats.nfv">Download video</a></p>
</section>
<script>
var videoSection = document.getElementById('video');
var videoElement = document.createElement('video');
var support = videoElement.canPlayType('video/x-new-fictional-format;codecs="kittens,bunnies"');
if (support != "probably" && "New Fictional Video Plug-in" in navigator.plugins) {
// not confident of browser support
// but we have a plugin
// so use plugin instead
videoElement = document.createElement("embed");
} else if (support == "no") {
// no support from browser and no plugin
// do nothing
videoElement = null;
}
if (videoElement) {
while (videoSection.hasChildNodes())
videoSection.removeChild(videoSection.firstChild);
videoElement.setAttribute("src", "playing-cats.nfv");
videoSection.appendChild(videoElement);
}
</script>
To express the type of a media resource
to allow the user agent to avoid downloading resources it can't
render, authors can use the source element's type attribute.
4.8.10.4 Network states4.8.10.4 ネットワーク状態
As media elements interact
with the network, their current network activity is represented by
the networkState
attribute. On getting, it must return the current network state of
the element, which must be one of the following values:
NETWORK_EMPTY (numeric value 0)NETWORK_EMPTY (数値 0)- The element has not yet been initialized. All attributes are in
their initial states.要素は、まだ初期化されていません。すべての属性は、それぞれの初期状態にあります。
NETWORK_IDLE (numeric value 1)NETWORK_IDLE (数値 1)- The element's
load() method
algorithm is active, but it is not actually using the network at
this time.
NETWORK_LOADING (numeric value 2)NETWORK_LOADING (数値 2)- The user agent is actively trying to download data.
NETWORK_LOADED (numeric value 3)NETWORK_LOADED (数値 3)- The entire media resource has been obtained and is
available to the user agent locally. Network connectivity could be
lost without affecting the media playback.媒体資源の全体が取得され、
利用者エージェントに局所的に利用可能となりました。ネットワーク接続性が失われたとしても、
媒体の再生に影響することはありません。
The algorithm for the load()
method defined below describes exactly when the networkState attribute changes
value and what events fire to indicate changes in this state.
Some resources, e.g. streaming Web radio, can never
reach the NETWORK_LOADED state.
All media elements have a
begun flag, which must begin in the false state, and an
autoplaying flag, which must begin in the true state.
When the load()
method on a media element is invoked, the user agent
must run the following steps. Note that this algorithm might get
aborted, e.g. if the load()
method itself is invoked again.
-
If there are any tasks from
the media element's media element new resource
task source or its media element event task
source in one of the task
queues, then remove those tasks.
Basically, pending events, callbacks, and loads
for the media element are discarded when the media element starts
loading a new resource.
Abort any already-running instance of this algorithm for
this element. If those method calls have not yet returned, they
must finish the step they are on, and then immediately return. This
is not blocking; this algorithm must not wait for the earlier
instances to abort before continuing.
If the element's begun flag is true, then set
the begun flag to false, set the error attribute to a new
MediaError object whose code attribute is set to MEDIA_ERR_ABORTED,
and fire a progress event called abort at the media
element.
Set the error attribute
to null and the autoplaying flag to true.
Set the playbackRate attribute to the
value of the defaultPlaybackRate
attribute.
If the media element's networkState is not set to
NETWORK_EMPTY, then
run these substeps:
If a fetching process is in progress for the media
element, the user agent should stop it.
Set the networkState attribute to
NETWORK_EMPTY.
If readyState is
not set to HAVE_NOTHING, then set it
to that state.
If the paused attribute
is false, then set to true.
If seeking is true,
set it to false.
Set the current playback position to 0.
Fire a simple event called emptied at the media
element.
Generate the list of potential media resources
and let the resulting list be candidates.
Set the networkState to NETWORK_LOADING.
Set the begun flag to true and queue a
task to fire a progress event called loadstart at the media
element.
-
The method must return, but these steps must continue.
Playback of any previously playing media
resource for this element stops.
-
Candidate loop: For each item in candidates, if any, and in the same order as they
were added to the list, run the following steps:
Let the current media resource be the
resource given by the absolute URL for the current
item in candidates. This is now the element's
media resource.
Set the currentSrc attribute to the
absolute URL of the current media
resource.
-
Begin to fetch the current media
resource.
Every 350ms (±200ms) or for every byte received,
whichever is least frequent, queue a task
to fire a progress event called progress at the element.
If at any point the user agent has received no data for more
than about three seconds, then queue a task to
fire a progress event called stalled at the element.
User agents may allow users to selectively block or slow
media data downloads. When a media
element's download has been blocked altogether, the user
agent must act as if it was stalled (as opposed to acting as if
the connection was closed). The rate of the download may also be
throttled automatically by the user agent, e.g. to balance the
download with other connections sharing the same bandwidth.
User agents may decide to not download more content at any
time, e.g. after buffering five minutes of a one hour media
resource, while waiting for the user to decide whether to play
the resource or not, or while waiting for user input in an
interactive resource. When a media element's
download has been suspended, the user agent must set the networkState to NETWORK_IDLE and
queue a task to fire a progress event
called suspend at the
element. If and when downloading of the resource resumes, the
user agent must set the networkState to NETWORK_LOADING.
The user agent may use whatever means necessary to fetch the
resource (within the constraints put forward by this and other
specifications); for example, reconnecting to the server in the
face of network errors, using HTTP partial range requests, or
switching to a streaming protocol. The user agent must consider a
resource erroneous only if it has given up trying to fetch it.
The networking task source tasks to process the data as it is
being fetched must, when appropriate, include the relevant
substeps from the following list:
- If the media data cannot be fetched at all, due
to network errors, causing the user agent to give up trying to
fetch the resource
- If the media data can be fetched but is in an
unsupported format, or can otherwise not be rendered at
all
-
DNS errors, HTTP 4xx and 5xx errors (and equivalents in
other protocols), and other fatal network errors that occur
before the user agent has established whether the current media resource is usable, as well as
the file using an unsupported container format, or using
unsupported codecs for all the data, must cause the user agent
to execute the following steps:
The user agent should cancel the fetching
process.
If there are more items in the candidates list, then move on to the next one,
jumping back to the top of the candidate loop;
otherwise, jump to the final step in the overall algorithm
(the failure step).
- Once enough of the media
data has been fetched to determine the duration of the
media resource, its dimensions, and other
metadata
-
This indicates that the resource is usable. The user agent
must follow these substeps:
Set the current playback position to the
earliest possible position.
Set the readyState attribute to
HAVE_METADATA.
For video elements, set the videoWidth and videoHeight
attributes.
-
Set the duration
attribute to the duration of the resource.
The user agent will queue a task to
fire a simple event called durationchange at the
element at this point.
Queue a task to
fire a simple event called loadedmetadata at the
element.
-
If either the media resource or the address
of the current media resource indicate a
particular start time, then seek to that time. Ignore any
resulting exceptions (if the position is out of range, it is
effectively ignored).
For example, a fragment identifier could be
used to indicate a start position.
The user agent is required to
determine the duration of the media resource and
go through this step before playing.
- If the connection is interrupted, causing the user agent to
give up trying to fetch the resource
-
Fatal network errors that occur after the user agent has
established whether the current media
resource is usable must cause the user agent to execute
the following steps:
The user agent should cancel the fetching process.
Set the error
attribute to a new MediaError object whose code attribute is set to
MEDIA_ERR_NETWORK.
Set the begun flag to false and queue
a task to fire a progress event called
error at the media
element.
Set the element's networkState attribute
to the NETWORK_EMPTY value
and queue a task to fire a simple
event called emptied at the element.
Abort the overall load() method algorithm.
- If the media data is
corrupted
-
Fatal errors in decoding the media data that
occur after the user agent has established whether the current media resource is usable must cause the
user agent to execute the following steps:
The user agent should cancel the fetching process.
Set the error
attribute to a new MediaError object whose code attribute is set to
MEDIA_ERR_DECODE.
Set the begun flag to false and queue
a task to fire a progress event called
error at the media
element.
Set the element's networkState attribute
to the NETWORK_EMPTY value
and queue a task to fire a simple
event called emptied at the element.
Abort the overall load() method algorithm.
- If the media data fetching process is aborted by
the user
-
The fetching process is aborted by the user, e.g. because
the user navigated the browsing context to another page, the
user agent must execute the following steps. These steps are
not followed if the load()
method itself is reinvoked, as the steps above handle that
particular kind of abort.
The user agent should cancel the fetching process.
Set the error
attribute to a new MediaError object whose code attribute is set to
MEDIA_ERR_ABORT.
Set the begun flag to false and queue
a task to fire a progress event called
abort at the media
element.
If the media element's readyState attribute has
a value equal to HAVE_NOTHING, set the
element's networkState attribute
to the NETWORK_EMPTY value
and queue a task to fire a simple
event called emptied at the element. (If the
readyState
attribute has a value greater than HAVE_NOTHING, then this
doesn't happen; the available data, if any, will be
playable.)
Abort the overall load() method algorithm.
- If the media data can
be fetched but has non-fatal errors or uses, in part, codecs that
are unsupported, preventing the user agent from rendering the
content completely correctly but not preventing playback
altogether
-
The server returning data that is partially usable but cannot
be optimally rendered must cause the user agent to execute the
following steps.
Should we fire a 'warning' event? Set the
'error' flag to 'MEDIA_ERR_SUBOPTIMAL' or something?
When the user agent has completely fetched of the entire
media resource, it must move on to the next
step. This might never happen, e.g. when streaming an infinite
resource such as Web radio.
If the fetching process completes without errors, then set
the begun flag to false, set the networkState attribute to
NETWORK_LOADED, and
queue a task to fire a progress event
called load at the
element.
Then, abort the overall load() method algorithm.
-
Failure step: No usable resource was found. Run the
following steps:
Set the error attribute
to a new MediaError object whose code attribute is set to MEDIA_ERR_NONE_SUPPORTED.
Set the begun flag to false and queue a
task to fire a progress event called error at the media
element.
Set the element's networkState attribute to
the NETWORK_EMPTY
value and queue a task to fire a simple
event called emptied at
the element.
If a media element whose networkState has the value
NETWORK_EMPTY is inserted into a
document, the user agent must queue a task that
implicitly invokes the load()
method on the media element, and ignores any resulting
exceptions. The task source for this task is the
media element's own media element new resource
task source.
The bufferingRate
attribute must return the average number of bits received per second
for the current download over the past few seconds. If there is no
download in progress, the attribute must return 0.
The bufferingThrottled
attribute must return true if the user agent is intentionally
throttling the bandwidth used by the download (including when
throttling to zero to pause the download altogether), and false
otherwise.
The buffered
attribute must return a new static normalized
TimeRanges object that represents the ranges of
the media resource, if any, that the user agent has
buffered, at the time the attribute is evaluated. Users agents must
accurately determine the ranges available, even for media streams
where this can only be determined by tedious inspection.
Typically this will be a single range anchored at
the zero point, but if, e.g. the user agent uses HTTP range requests
in response to seeking, then there could be multiple ranges.
User agents may discard previously buffered data.
Thus, a time position included within a range of the
objects return by the buffered attribute at one time can
end up being not included in the range(s) of objects returned by the
same attribute at later times.
The duration
attribute must return the length of the media resource,
in seconds. If no media data is available, then the
attributes must return the Not-a-Number (NaN) value. If the
media resource is known to be unbounded (e.g. a
streaming radio), then the attribute must return the positive
Infinity value.
The user agent must determine the duration of the media
resource before playing any part of the media
data and before setting readyState to a value equal to
or greater than HAVE_METADATA, even if doing
so requires seeking to multiple parts of the resource.
When the length of the media
resource changes (e.g. from being unknown to known, or from a
previously established length to a new length) the user agent must
queue a task to fire a simple event called
durationchange at the
media element.
If an "infinite" stream ends for some reason,
then the duration would change from positive Infinity to the time of
the last frame or sample in the stream, and the durationchange event would be
fired. Similarly, if the user agent initially estimated the
media resource's duration instead of determining it
precisely, and later revises the estimate based on new information,
then the duration would change and the durationchange event would be
fired.
Media elements have a
current playback position, which must initially be
zero. The current position is a time.
The currentTime
attribute must, on getting, return the current playback
position, expressed in seconds. On setting, the user agent
must seek to the new value
(which might raise an exception).
If the media resource is a streaming resource, then
the user agent might be unable to obtain certain parts of the
resource after it has expired from its buffer. The
earliest possible position is the earliest
position in the stream that the user agent can ever obtain
again.
When the earliest possible position changes, if the
the current playback position is before the
earliest possible position, the user agent must seek to the earliest possible
position.
The loop
attribute is a boolean attribute that, if specified,
indicates that the media element is to seek back to the
start of the media resource upon reaching the end.
The loop DOM
attribute must reflect the content attribute of the
same name.
4.8.10.7 The ready states
Media elements have a
ready state, which describes to what degree they are ready
to be rendered at the current playback position. The
possible values are as follows; the ready state of a media element
at any particular time is the greatest value describing the state of
the element:
HAVE_NOTHING (numeric value 0)HAVE_NOTHING (数値 0)- No information regardig the media resource is
available. No data for the current playback position
is available. Media elements
whose
networkState
attribute is NETWORK_EMPTY are always in
the HAVE_NOTHING
state.
HAVE_METADATA (numeric value 1)HAVE_METADATA (数値 1)- Enough of the resource has been obtained that the duration of
the resource is available. In the case of a
video
element, the dimensions of the video are also available. The API
will no longer raise an exception when seeking. No media
data is available for the immediate current playback
position.
HAVE_CURRENT_DATA (numeric value 2)HAVE_CURRENT_DATA (数値 2)- Data for the immediate current playback position
is available, but not enough data is available that the user agent
could successfully advance the current playback
position at all without immediately reverting to the
HAVE_METADATA state. For
example, in video this corresponds to the user agent having data
from the current frame, but not the next frame.
HAVE_FUTURE_DATA (numeric value 3)HAVE_FUTURE_DATA (数値 3)- Data for the immediate current playback position
is available, as well as enough data for the user agent to advance
the current playback position at least a little
without immediately reverting to the
HAVE_METADATA state. For
example, In video this corresponds to the user agent having data
for at least the current frame and the next frame.
HAVE_ENOUGH_DATA (numeric value 4)HAVE_ENOUGH_DATA (数値 4)- Data for the immediate current playback position
is available, as well as enough data for the user agent to advance
the current playback position at least a little
without immediately reverting to the
HAVE_METADATA state, and,
in addition, the user agent estimates that data is being fetched at
a rate where the current playback position, if it were
to advance at the rate given by the defaultPlaybackRate
attribute, would not overtake the available data before playback
reaches the end of the media resource.
When the ready state of a media element whose networkState is not NETWORK_EMPTY changes, the
user agent must follow the steps given below:
- If the prevous ready state was
HAVE_NOTHING, and the new
ready state is HAVE_METADATA
-
A loadedmetadata DOM event will be fired as part of the load() algorithm.
- If the prevous ready state
was
HAVE_METADATA and
the new ready state is HAVE_CURRENT_DATA
-
If this is the first time this occurs for
this media element since the load() algorithm was last invoked,
the user agent must queue a task to fire a
simple event called loadeddata at the element.
- If the prevous ready state was
HAVE_FUTURE_DATA or more,
and the new ready state is HAVE_CURRENT_DATA or
less
-
A waiting DOM
event can be fired,
depending on the current state of playback.
- If the prevous ready state was
HAVE_CURRENT_DATA or
less, and the new ready state is HAVE_FUTURE_DATA
-
The user agent must queue a task to fire a
simple event called canplay.
If the element is potentially playing, the user
agent must queue a task to fire a simple
event called playing.
- If the new ready state is
HAVE_ENOUGH_DATA
-
The user agent must queue a task to fire a
simple event called canplay, and then queue a
task to fire a simple event called canplaythrough.
If the autoplaying flag is true, and the paused attribute is true, and the
media element has an autoplay attribute specified,
then the user agent may also set the paused attribute to false and
queue a task to fire a simple event
called play.
User agents are not required to autoplay, and it
is suggested that user agents honor user preferences on the
matter. Authors are urged to use the autoplay attribute rather than
using script to force the video to play, so as to allow the user
to override the behavior if so desired.
If the element is now potentially playing, and the
previous ready state was not HAVE_FUTURE_DATA, the
user agent must queue a task to fire a simple
event called playing.
It is possible for the ready state of a media
element to jump between these states discontinuously. For example,
the state of a media element can jump straight from HAVE_METADATA to HAVE_ENOUGH_DATA without
passing through the HAVE_CURRENT_DATA and
HAVE_FUTURE_DATA
states.
The readyState DOM
attribute must, on getting, return the value described above that
describes the current ready state of the media
element.
The autoplay
attribute is a boolean attribute. When present, the
algorithm described herein will cause the user agent to
automatically begin playback of the media resource as
soon as it can do so without stopping.
The autoplay
DOM attribute must reflect the content attribute of the
same name.
4.8.10.8 Cue ranges
Media elements have a set of
cue ranges. Each cue range is made up
of the following information:
- A class name
- A group of related ranges can be given the same class name so
that they can all be removed at the same time.
- An identifier
-
- A string can be assigned to each cue range for identification
by script. The string need not be unique and can contain any
value.
- A start time開始時刻
- An end time終了時刻
- The actual time range, using the same timeline as the
media resource itself.
- A "pause" boolean
- A flag indicating whether to pause playback on exit.
- An "enter" callback
- A callback that is called when the current playback
position enters the range.
- An "exit" callback
- A callback that is called when the current playback
position exits the range.
- An "active" boolean
- A flag indicating whether the range is active or not.
The addCueRange(className, id, start, end, pauseOnExit, enterCallback, exitCallback) method must, when called,
add a cue range to the media element, that
cue range having the class name className, the
identifier id, the start time start (in seconds), the end time end (in seconds), the "pause" boolean with the same
value as pauseOnExit, the "enter" callback enterCallback, the "exit" callback exitCallback, and an "active" boolean that is true if
the current playback position is equal to or greater
than the start time and less than the end time, and false
otherwise.
The removeCueRanges(className) method must, when called,
remove all the cue ranges of the
media element which have the class name className.
The paused
attribute represents whether the media element is
paused or not. The attribute must initially be true.
A media element is said to be potentially
playing when its paused
attribute is false, the readyState attribute is either
HAVE_FUTURE_DATA or
HAVE_ENOUGH_DATA,
the element has not ended playback, playback has not
stopped due to errors, and the element has not
paused for user interaction.
A media element is said to have ended
playback when the element's readyState attribute is HAVE_METADATA or greater, and
the current playback position is the end of the
media resource, and the media element does
not have a loop attribute
specified.
The ended
attribute must return true if the media element has
ended playback, and false otherwise.
A media element is said to have stopped due to
errors when the element's readyState attribute is HAVE_METADATA or greater, and
the user agent encounters a
non-fatal error during the processing of the media
data, and due to that error, is not able to play the content
at the current playback position.
A media element is said to have paused for user
interaction when its paused attribute is false, the readyState attribute is either
HAVE_FUTURE_DATA or
HAVE_ENOUGH_DATA and
the user agent has reached a point in the media
resource where the user has to make a selection for the
resource to continue.
It is possible for a media element to have both
ended playback and paused for user
interaction at the same time.
When a media element that is potentially
playing stops playing because it has paused for user
interaction, the user agent must queue a task to
fire a simple event called timeupdate at the element.
When a media element
that is potentially playing stops playing because its
readyState attribute
changes to a value lower than HAVE_FUTURE_DATA, without
the element having ended playback, or playback having
stopped due to errors, or playback having paused
for user interaction, or the seeking algorithm being invoked, the
user agent must queue a task to fire a simple
event called timeupdate
at the element, and queue a task to fire a simple
event called waiting at
the element.
When the current playback position reaches the end
of the media resource, then the user agent must follow
these steps:
If the media element has a loop attribute specified, then seek to the earliest possible
position of the media resource and abort these
steps.
Stop playback.
The ended attribute becomes
true.
The user agent must queue a task to fire
a simple event called timeupdate at the element.
The user agent must queue a task to fire
a simple event called ended
at the element.
The defaultPlaybackRate
attribute gives the desired speed at which the media
resource is to play, as a multiple of its intrinsic
speed. The attribute is mutable: on getting it must return the last
value it was set to, or 1.0 if it hasn't yet been set; on setting
the attribute must be set to the new value.
The playbackRate
attribute gives the speed at which the media resource
plays, as a multiple of its intrinsic speed. If it is not equal to
the defaultPlaybackRate,
then the implication is that the user is using a feature such as
fast forward or slow motion playback. The attribute is mutable: on
getting it must return the last value it was set to, or 1.0 if it
hasn't yet been set; on setting the attribute must be set to the new
value, and the playback must change speed (if the element is
potentially playing).
The "play" function in a user agent's interface must set the
playbackRate attribute
to the value of the defaultPlaybackRate
attribute before invoking the play() method's steps. Features such
as fast-forward or rewind must be implemented by only changing the
playbackRate
attribute.
When the defaultPlaybackRate or
playbackRate attributes
change value (either by being set by script or by being changed
directly by the user agent, e.g. in response to user control) the
user agent must queue a task to fire a simple
event called ratechange
at the media element.
The played
attribute must return a new static normalized
TimeRanges object that represents the ranges of
the media resource, if any, that the user agent has so
far rendered, at the time the attribute is evaluated.
When the play()
method on a media element is invoked, the user agent
must run the following steps.
If the media element's networkState attribute has
the value NETWORK_EMPTY, then the user
agent must invoke the load()
method and wait for it to return. If that raises an exception, that
exception must be reraised by the play() method.
-
If the playback has ended,
then the user agent must seek
to the earliest possible position of the media
resource.
This will cause the user
agent to queue a task to fire a simple
event called timeupdate at the media
element.
-
If the media element's paused attribute is true, it must
be set to false.
If this changed the value of paused, the user agent must run the following substeps:
Queue a task to fire a simple event
called play at the element.
If the media element's readyState attribute has the
value HAVE_METADATA
or HAVE_CURRENT_DATA,
queue a task to fire a simple event
called waiting at the
element.
Otherwise, the media element's readyState attribute has the value
HAVE_FUTURE_DATA
or HAVE_ENOUGH_DATA;
queue a task to fire a simple event
called playing at the
element.
The media element's autoplaying
flag must be set to false.
The method must then return.
When the pause()
method is invoked, the user agent must run the following steps:利用者エージェントは、 pause() メソッドが呼び出された時、
次の段階を走らせなければなりません。
If the media element's networkState attribute has
the value NETWORK_EMPTY, then the user
agent must invoke the load()
method and wait for it to return. If that raises an exception, that
exception must be reraised by the pause() method.
If the media element's paused attribute is false, it must
be set to true.
The media element's autoplaying
flag must be set to false.
The method must then return.
If the second step above changed the value of paused, then the user agent must
queue a task to fire a simple event
called timeupdate at the
element, and queue a task to fire a simple
event called pause at the
element.
When a media element is
potentially playing and its Document is an
active document, its current playback
position must increase monotonically at playbackRate units of media
time per unit time of wall clock time.
This specification doesn't define how the user agent
achieves the appropriate playback rate — depending on the
protocol and media available, it is plausible that the user agent
could negotiate with the server to have the server provide the media
data at the appropriate rate, so that (except for the period between
when the rate is changed and when the server updates the stream's
playback rate) the client doesn't actually have to drop or
interpolate any frames.
When the playbackRate
is negative (playback is backwards), any corresponding audio must be
muted. When the playbackRate is so low or so
high that the user agent cannot play audio usefully, the
corresponding audio must also be muted. If the playbackRate is not 1.0, the
user agent may apply pitch adjustments to the audio as necessary to
render it faithfully.
The playbackRate can
be 0.0, in which case the current playback position
doesn't move, despite playback not being paused (paused doesn't become true, and the
pause event doesn't fire).
Media elements that are
potentially playing while not in a
Document must not play any
video, but should play any audio component. Media elements must not
stop playing just because all references to them have been removed;
only once a media element to which no references exist has reached a
point where no further audio remains to be played for that element
(e.g. because the element is paused, or because the end of the clip
has been reached, or because its playbackRate is 0.0) may the
element be garbage collected.
When the current playback position of a media
element changes (e.g. due to playback or seeking), the user
agent must run the following steps. If the current playback
position changes while the steps are running, then the user
agent must wait for the steps to complete, and then must immediately
rerun the steps. (These steps are thus run as often as possible or
needed — if one iteration takes a long time, this can cause
certain ranges to be skipped over as the user agent rushes ahead to
"catch up".)
Let current ranges be an ordered list of
cue ranges, initialized to contain
all the cue ranges of the
media element whose start times are less than or equal
to the current playback position and whose end times
are greater than the current playback position, in the
order they were added to the element.
Let other ranges be an ordered list of
cue ranges, initialized to contain
all the cue ranges of the
media element that are not present in current ranges, in the order they were added to the
element.
If none of the cue ranges in
current ranges have their "active" boolean set
to "false" (inactive) and none of the cue
ranges in other ranges have their
"active" boolean set to "true" (active), then abort these
steps.
If the time was reached through the usual monotonic increase
of the current playback position during normal playback, and if the
user agent has not fired a timeupdate event at the element in
the past 15 to 250ms, then the user agent must queue a
task to fire a simple event called timeupdate at the element. (In the
other cases, such as explicit seeks, relevant events get fired as
part of the overall process of changing the current playback
position.)
The event thus is not to be fired faster than about
66Hz or slower than 4Hz. User agents are encouraged to vary the
frequency of the event based on the system load and the average
cost of processing the event each time, so that the UI updates are
not any more frequent than the user agent can comfortably handle
while decoding the video.
If the time was reached through the usual monotonic increase
of the current playback position during normal playback, and there
are cue ranges in other ranges that have both their "active" boolean
and their "pause" boolean set to "true", then immediately act as if
the element's pause() method
had been invoked. (In the other cases, such as explicit
seeks, playback is not paused by exiting a cue range, even if that
cue range has its "pause" boolean set to "true".)
For each non-null "exit" callback of the cue ranges in other
ranges that have their "active" boolean set to "true"
(active), in list order, queue a task that invokes the
callback, passing the cue range's identifier as the callback's only
argument.
For each non-null "enter" callback of the cue ranges in current ranges that
have their "active" boolean set to "false" (inactive), in list
order, queue a task that invokes the callback, passing
the cue range's identifier as the callback's only
argument.
Set the "active" boolean of all the cue ranges in the current ranges
list to "true" (active), and the "active" boolean of all the cue ranges in the other
ranges list to "false" (inactive).
When a media element is removed from a
Document, if the
media element's networkState attribute has a
value other than NETWORK_EMPTY then the user
agent must act as if the pause() method had been invoked.
If the media element's
Document stops being an active document, then the
playback will stop until the document
is active again.
4.8.10.10 Seeking
The seeking
attribute must initially have the value false.
When the user agent is required to seek to a particular new
playback position in the media resource, it means
that the user agent must run the following steps:
If the media element's readyState is HAVE_NOTHING, then the user
agent must raise an INVALID_STATE_ERR exception (if
the seek was in response to a DOM method call or setting of a DOM
attribute), and abort these steps.
If the new playback position is later
than the end of the media resource, then let it be the
end of the media resource instead.
If the new playback position is less
than the earliest possible position, let it be that
position instead.
If the (possibly now changed) new playback
position is not in one of the ranges given in the seekable attribute, then the user
agent must raise an INDEX_SIZE_ERR exception (if the
seek was in response to a DOM method call or setting of a DOM
attribute), and abort these steps.
The current playback position must be set to
the given new playback position.
The seeking DOM
attribute must be set to true.
The user agent must queue a
task to fire a simple event called timeupdate at the element.
If the media element was potentially
playing immediately before it started seeking, but seeking
caused its readyState
attribute to change to a value lower than HAVE_FUTURE_DATA, the
user agent must queue a task to fire a simple
event called waiting at
the element.
If, when it reaches this step, the user agent has still not
established whether or not the media data for the new playback position is available, and, if it is,
decoded enough data to play back that position, the user agent must
queue a task to fire a simple event
called seeking at the
element.
If the seek was in response to a DOM method call or setting
of a DOM attribute, then continue the script. The remainder of
these steps must be run asynchronously.
The user agent must wait until it has established whether or
not the media data for the new playback
position is available, and, if it is, until it has decoded
enough data to play back that position.
The seeking DOM
attribute must be set to false.
The user agent must queue a task to fire
a simple event called seeked at the element.
The seekable
attribute must return a new static normalized
TimeRanges object that represents the ranges of
the media resource, if any, that the user agent is able
to seek to, at the time the attribute is evaluated.
If the user agent can seek to anywhere in the
media resource, e.g. because it a simple movie file and
the user agent and the server support HTTP Range requests, then the
attribute would return an object with one range, whose start is the
time of the first frame (typically zero), and whose end is the same
as the time of the first frame plus the duration attribute's value (which
would equal the time of the last frame).
The range might be continuously changing, e.g. if
the user agent is buffering a sliding window on an infinite
stream. This is the behavior seen with DVRs viewing live TV, for
instance.
Media resources might be
internally scripted or interactive. Thus, a media
element could play in a non-linear fashion. If this happens,
the user agent must act as if the algorithm for seeking was used whenever the
current playback position changes in a discontinuous
fashion (so that the relevant events fire).
4.8.10.11 User interface
The controls
attribute is a boolean attribute. If the attribute is
present, or if the media element is without
script, then the user agent should expose a user
interface to the user. This user interface should include
features to begin playback, pause playback, seek to an arbitrary
position in the content (if the content supports arbitrary seeking),
change the volume, and show the media content in manners more
suitable to the user (e.g. full-screen video or in an independent
resizable window). Other controls may also be made available.
If the attribute is absent, then the user agent should avoid
making a user interface available that could conflict with an
author-provided user interface. User agents may make the following
features available, however, even when the attribute is absent:
User agents may provide controls to affect playback of the media
resource (e.g. play, pause, seeking, and volume controls), but such
features should not interfere with the page's normal rendering. For
example, such features could be exposed in the media
element's context menu.
Where possible (specifically, for starting, stopping, pausing,
and unpausing playback, for muting or changing the volume of the
audio, and for seeking), user interface features exposed by the user
agent must be implemented in terms of the DOM API described above,
so that, e.g., all the same events fire.
The controls
DOM attribute must reflect the content attribute of the
same name.
The volume
attribute must return the playback volume of any audio portions of
the media element, in the range 0.0 (silent) to 1.0
(loudest). Initially, the volume must be 1.0, but user agents may
remember the last set value across sessions, on a per-site basis or
otherwise, so the volume may start at other values. On setting, if
the new value is in the range 0.0 to 1.0 inclusive, the attribute
must be set to the new value and the playback volume must be
correspondingly adjusted as soon as possible after setting the
attribute, with 0.0 being silent, and 1.0 being the loudest setting,
values in between increasing in loudness. The range need not be
linear. The loudest setting may be lower than the system's loudest
possible setting; for example the user could have set a maximum
volume. If the new value is outside the range 0.0 to 1.0 inclusive,
then, on setting, an INDEX_SIZE_ERR exception must be
raised instead.
The muted
attribute must return true if the audio channels are muted and false
otherwise. Initially, the audio channels should not be muted
(false), but user agents may remember the last set value across
sessions, on a per-site basis or otherwise, so the muted state may
start as muted (true). On setting, the attribute must be set to the
new value; if the new value is true, audio playback for this
media resource must then be muted, and if false, audio
playback must then be enabled.
Whenever either the muted or
volume attributes are changed,
the user agent must queue a task to fire a simple
event called volumechange at the media
element.
4.8.10.12 Time ranges
Objects implementing the TimeRanges interface
represent a list of ranges (periods) of time.
interface TimeRanges {
readonly attribute unsigned long length;
float start(in unsigned long index);
float end(in unsigned long index);
};
The length
DOM attribute must return the number of ranges represented by the object.
The start(index) method must return the position
of the start of the indexth range represented by
the object, in seconds measured from the start of the timeline that
the object covers.
The end(index) method must return the position
of the end of the indexth range represented by
the object, in seconds measured from the start of the timeline that
the object covers.
These methods must raise INDEX_SIZE_ERR exceptions
if called with an index argument greater than or
equal to the number of ranges represented by the object.
When a TimeRanges object is said to be a
normalized TimeRanges object, the ranges it
represents must obey the following criteria:
In other words, the ranges in such an object are ordered, don't
overlap, aren't empty, and don't touch (adjacent ranges are folded
into one bigger range).
The timelines used by the objects returned by the buffered, seekable and played DOM attributes of media elements must be the same as that
element's media resource's timeline.
The following events fire on media
elements as part of the processing model described above:
| Event name
| Interface
| Dispatched when...
| Preconditions
|
|---|
loadstart
| ProgressEvent [PROGRESS]
| The user agent begins fetching the media data, synchronously during the load() method call.
| networkState equals NETWORK_LOADING
|
progress
| ProgressEvent [PROGRESS]
| The user agent is fetching media data.
| networkState equals NETWORK_LOADING
|
suspend
| ProgressEvent [PROGRESS]
| The user agent is intentionally not currently fetching media data, but does not have the entire media resource downloaded.
| networkState equals NETWORK_IDLE
|
load
| ProgressEvent [PROGRESS]
| The user agent finishes fetching the entire media resource.
| networkState equals NETWORK_LOADED
|
abort
| ProgressEvent [PROGRESS]
| The user agent stops fetching the media data before it is completely downloaded. This can be fired synchronously during the load() method call.
| error is an object with the code MEDIA_ERR_ABORTED.
networkState equals either NETWORK_EMPTY or NETWORK_LOADED, depending on when the download was aborted.
|
error
| ProgressEvent [PROGRESS]
| An error occurs while fetching the media data.
| error is an object with the code MEDIA_ERR_NETWORK_ERROR or higher.
networkState equals either NETWORK_EMPTY or NETWORK_LOADED, depending on when the download was aborted.
|
emptied
| Event
| A media element whose networkState was previously not in the NETWORK_EMPTY state has just switched to that state (either because of a fatal error during load that's about to be reported, or because the load() method was reinvoked, in which case it is fired synchronously during the load() method call).
| networkState is NETWORK_EMPTY; all the DOM attributes are in their initial states.
|
stalled
| ProgressEvent
| The user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
| networkState is NETWORK_LOADING.
|
play
| Event
| Playback has begun. Fired after the play() method has returned.
| paused is newly false.
|
pause
| Event
| Playback has been paused. Fired after the pause method has returned.
| paused is newly true.
|
loadedmetadata
| Event
| The user agent has just determined the the duration and dimensions of the media resource.
| readyState is newly equal to HAVE_METADATA or greater for the first time.
|
loadeddata
| Event
| The user agent can render the media data at the current playback position for the first time.
| readyState newly increased to HAVE_CURRENT_DATA or greater for the first time.
|
waiting
| Event
| Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.
| readyState is newly equal to or less than HAVE_CURRENT_DATA, and paused is false. Either seeking is true, or the current playback position is not contained in any of the ranges in buffered. It is possible for playback to stop for two other reasons without paused being false, but those two reasons do not fire this event: maybe playback ended, or playback stopped due to errors.
|
playing
| Event
| Playback has started.
| readyState is newly equal to or greater than HAVE_FUTURE_DATA, paused is false, seeking is false, or the current playback position is contained in one of the ranges in buffered.
|
canplay
| Event
| The user agent can resume playback of the media data, but estimates that if playback were to be started now, the media resource could not be rendered at the current playback rate up to its end without having to stop for further buffering of content.
| readyState newly increased to HAVE_FUTURE_DATA or greater.
|
canplaythrough
| Event
| The user agent estimates that if playback were to be started now, the media resource could be rendered at the current playback rate all the way to its end without having to stop for further buffering.
| readyState is newly equal to HAVE_ENOUGH_DATA.
|
seeking
| Event
| The seeking DOM attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event.
|
|
seeked
| Event
| The seeking DOM attribute changed to false.
|
|
timeupdate
| Event
| The current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously.
|
|
ended
| Event
| Playback has stopped because the end of the media resource was reached.
| currentTime equals the end of the media resource; ended is true.
|
ratechange
| Event
| Either the defaultPlaybackRate or the playbackRate attribute has just been updated.
|
|
durationchange
| Event
| The duration attribute has just been updated.
|
|
volumechange
| Event
| Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned.
|
|
4.8.10.14 Security and privacy considerations
Talk about making sure interactive media files
(e.g. SVG) don't have access to the container DOM (XSS potential);
talk about not exposing any sensitive data like metadata from tracks
in the media files (intranet snooping risk)
4.8.11 The canvas element4.8.11 canvas 要素
- Categories分類
- Embedded content.埋め込まれた内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where embedded content is expected.埋め込まれた内容が期待される場所。
- Content model:内容モデル:
- Transparent.透過。
- Element-specific attributes:要素固有属性:
widthheight- DOM interface:DOM 界面:
-
interface HTMLCanvasElement : HTMLElement {
attribute unsigned long width;
attribute unsigned long height;
DOMString toDataURL();
DOMString toDataURL(in DOMString type, [Variadic] in any args);
DOMObject getContext(in DOMString contextId);
};
The canvas element represents a resolution-dependent
bitmap canvas, which can be used for rendering graphs, game
graphics, or other visual images on the fly.
Authors should not use the canvas element in a
document when a more suitable element is available. For example, it
is inappropriate to use a canvas element to render a
page heading: if the desired presentation of the heading is
graphically intense, it should be marked up using appropriate
elements (typically h1) and then styled using CSS and
supporting technologies such as XBL.
When authors use the canvas element, they should
also provide content that, when presented to the user, conveys
essentially the same function or purpose as the bitmap canvas. This
content may be placed as content of the canvas
element. The contents of the canvas element, if any,
are the element's fallback content.
In interactive visual media, if the canvas element
is with script, the canvas element
represents an embedded element with a dynamically created image.
In non-interactive, static, visual media, if the
canvas element has been previously painted on (e.g. if
the page was viewed in an interactive visual medium and is now being
printed, or if some script that ran during the page layout process
painted on the element), then the canvas element
represents embedded content with the current image and
size. Otherwise, the element represents its fallback
content instead.
In non-visual media, and in visual media if the
canvas element is without script, the
canvas element represents its fallback
content instead.
The canvas element has two attributes to control the
size of the coordinate space: width and height. These
attributes, when specified, must have values that are valid non-negative
integers. The rules for parsing non-negative
integers must be used to obtain their numeric values. If an
attribute is missing, or if parsing its value returns an error, then
the default value must be used instead. The width attribute defaults to 300,
and the height attribute
defaults to 150.
The intrinsic dimensions of the canvas element equal
the size of the coordinate space, with the numbers interpreted in
CSS pixels. However, the element can be sized arbitrarily by a
style sheet. During rendering, the image is scaled to fit this layout
size.
The size of the coordinate space does not necessarily represent
the size of the actual bitmap that the user agent will use
internally or during rendering. On high-definition displays, for
instance, the user agent may internally use a bitmap with two device
pixels per unit in the coordinate space, so that the rendering
remains at high quality throughout.
Whenever the width and
height attributes are set
(whether to a new value or to the previous value), the bitmap and
any associated contexts must be cleared back to their initial state
and reinitialized with the newly specified coordinate space
dimensions.
The width and
height DOM
attributes must reflect the respective content
attributes of the same name.
Only one square appears to be drawn in the following example:
// canvas is a reference to a <canvas> element
var context = canvas.getContext('2d');
context.fillRect(0,0,50,50);
canvas.setAttribute('width', '300'); // clears the canvas
context.fillRect(0,100,50,50);
canvas.width = canvas.width; // clears the canvas
context.fillRect(100,0,50,50); // only this square remains
When the canvas is initialized it must be set to fully
transparent black.
To draw on the canvas, authors must first obtain a reference to a
context using the getContext(contextId) method of the
canvas element.
This specification only defines one context, with the name "2d". If getContext() is called with
that exact string for its contextId argument,
then the UA must return a reference to an object implementing
CanvasRenderingContext2D. Other specifications may
define their own contexts, which would return different objects.
Vendors may also define experimental contexts using the syntax
vendorname-context, for example, moz-3d.
When the UA is passed an empty string or a string specifying a
context that it does not support, then it must return null. String
comparisons must be case-sensitive.
Arguments other than the contextId must be
ignored.
A future version of this specification will probably
define a 3d context (probably based on the OpenGL ES
API).
The toDataURL() method
must, when called with no arguments, return a data: URL containing a representation of the image
as a PNG file. [PNG].
If the canvas has no pixels (i.e. either its horizontal dimension
or its vertical dimension is zero) then the method must return the
string "data:,". (This is the shortest data: URL; it represents the empty string in a text/plain resource.)
The toDataURL(type) method (when called with one
or more arguments) must return a data: URL containing a representation of the image
in the format given by type. The possible values
are MIME types with no parameters, for example
image/png, image/jpeg, or even maybe
image/svg+xml if the implementation actually keeps
enough information to reliably render an SVG image from the
canvas.
For image types that do not support an alpha channel, the image
must be composited onto a solid black background using the
source-over operator, and the resulting image must be the one used
to create the data: URL.
Only support for image/png is required. User agents
may support other types. If the user agent does not support the
requested type, it must return the image using the PNG format.
User agents must convert the provided type to lower case before
establishing if they support that type and before creating the data: URL.
When trying to use types other than
image/png, authors can check if the image was really
returned in the requested format by checking to see if the returned
string starts with one the exact strings "data:image/png," or "data:image/png;". If it does, the image is PNG, and
thus the requested type was not supported. (The one exception to
this is if the canvas has either no height or no width, in which
case the result might simply be "data:,".)
If the method is invoked with the first argument giving a type
corresponding to one of the types given in the first column of the
following table, and the user agent supports that type, then the
subsequent arguments, if any, must be treated as described in the
second cell of that row.
| Type | Other arguments
|
|---|
| image/jpeg
| The second argument, if it is a number between 0.0 and 1.0,
must be treated as the desired quality level. If it is not a
number or is outside that range, the user agent must use its
default value, as if the argument had been omitted.
|
Other arguments must be ignored and must not cause the user agent
to raise an exception. A future version of this specification will
probably define other parameters to be passed to toDataURL() to allow authors to
more carefully control compression settings, image metadata,
etc.
4.8.11.1 The 2D context
When the getContext()
method of a canvas element is invoked with 2d as the argument, a
CanvasRenderingContext2D object is returned.
There is only one CanvasRenderingContext2D object
per canvas, so calling the getContext() method with the
2d argument a second time
must return the same object.
The 2D context represents a flat Cartesian surface whose origin
(0,0) is at the top left corner, with the coordinate space having
x values increasing when going right, and y values increasing when going down.
interface CanvasRenderingContext2D {
// back-reference to the canvas
readonly attribute HTMLCanvasElement canvas;
// state
void save(); // push state on state stack
void restore(); // pop state stack and restore state
// transformations (default transform is the identity matrix)
void scale(in float x, in float y);
void rotate(in float angle);
void translate(in float x, in float y);
void transform(in float m11, in float m12, in float m21, in float m22, in float dx, in float dy);
void setTransform(in float m11, in float m12, in float m21, in float m22, in float dx, in float dy);
// compositing
attribute float globalAlpha; // (default 1.0)
attribute DOMString globalCompositeOperation; // (default source-over)
// colors and styles
attribute DOMObject strokeStyle; // (default black)
attribute DOMObject fillStyle; // (default black)
CanvasGradient createLinearGradient(in float x0, in float y0, in float x1, in float y1);
CanvasGradient createRadialGradient(in float x0, in float y0, in float r0, in float x1, in float y1, in float r1);
CanvasPattern createPattern(in HTMLImageElement image, in DOMString repetition);
CanvasPattern createPattern(in HTMLCanvasElement image, in DOMString repetition);
// line caps/joins
attribute float lineWidth; // (default 1)
attribute DOMString lineCap; // "butt", "round", "square" (default "butt")
attribute DOMString lineJoin; // "round", "bevel", "miter" (default "miter")
attribute float miterLimit; // (default 10)
// shadows
attribute float shadowOffsetX; // (default 0)
attribute float shadowOffsetY; // (default 0)
attribute float shadowBlur; // (default 0)
attribute DOMString shadowColor; // (default transparent black)
// rects
void clearRect(in float x, in float y, in float w, in float h);
void fillRect(in float x, in float y, in float w, in float h);
void strokeRect(in float x, in float y, in float w, in float h);
// path API
void beginPath();
void closePath();
void moveTo(in float x, in float y);
void lineTo(in float x, in float y);
void quadraticCurveTo(in float cpx, in float cpy, in float x, in float y);
void bezierCurveTo(in float cp1x, in float cp1y, in float cp2x, in float cp2y, in float x, in float y);
void arcTo(in float x1, in float y1, in float x2, in float y2, in float radius);
void rect(in float x, in float y, in float w, in float h);
void arc(in float x, in float y, in float radius, in float startAngle, in float endAngle, in boolean anticlockwise);
void fill();
void stroke();
void clip();
boolean isPointInPath(in float x, in float y);
// text
attribute DOMString font; // (default 10px sans-serif)
attribute DOMString textAlign; // "start", "end", "left", "right", "center" (default: "start")
attribute DOMString textBaseline; // "top", "hanging", "middle", "alphabetic", "ideographic", "bottom" (default: "alphabetic")
void fillText(in DOMString text, in float x, in float y);
void fillText(in DOMString text, in float x, in float y, in float maxWidth);
void strokeText(in DOMString text, in float x, in float y);
void strokeText(in DOMString text, in float x, in float y, in float maxWidth);
TextMetrics measureText(in DOMString text);
// drawing images
void drawImage(in HTMLImageElement image, in float dx, in float dy);
void drawImage(in HTMLImageElement image, in float dx, in float dy, in float dw, in float dh);
void drawImage(in HTMLImageElement image, in float sx, in float sy, in float sw, in float sh, in float dx, in float dy, in float dw, in float dh);
void drawImage(in HTMLCanvasElement image, in float dx, in float dy);
void drawImage(in HTMLCanvasElement image, in float dx, in float dy, in float dw, in float dh);
void drawImage(in HTMLCanvasElement image, in float sx, in float sy, in float sw, in float sh, in float dx, in float dy, in float dw, in float dh);
// pixel manipulation
ImageData createImageData(in float sw, in float sh);
ImageData getImageData(in float sx, in float sy, in float sw, in float sh);
void putImageData(in ImageData imagedata, in float dx, in float dy);
void putImageData(in ImageData imagedata, in float dx, in float dy, in float dirtyX, in float dirtyY, in float dirtyWidth, in float dirtyHeight);
};
interface CanvasGradient {
// opaque object
void addColorStop(in float offset, in DOMString color);
};
interface CanvasPattern {
// opaque object
};
interface TextMetrics {
readonly attribute float width;
};
interface ImageData {
readonly attribute unsigned long width;
readonly attribute unsigned long height;
readonly attribute CanvasPixelArray data;
};
interface CanvasPixelArray {
readonly attribute unsigned long length;
[IndexGetter] octet XXX5(in unsigned long index);
[IndexSetter] void XXX6(in unsigned long index, in octet value);
};
The canvas
attribute must return the canvas element that the
context paints on.
Unless otherwise stated, for the 2D context interface, any method
call with a numeric argument whose value is infinite or a NaN value
must be ignored.
Whenever the CSS value currentColor is used
as a color in this API, the "computed value of the 'color' property"
for the purposes of determining the computed value of the currentColor keyword is the computed value of the
'color' property on the element in question at the time that the
color is specified (e.g. when the appropriate attribute is set, or
when the method is called; not when the color is rendered or
otherwise used). If the computed value of the 'color' property is
undefined for a particular case (e.g. because the element is not in
a document), then the "computed value of the 'color' property" for
the purposes of determining the computed value of the currentColor keyword is fully opaque black. [CSS3COLOR]
4.8.11.1.1 The canvas state
Each context maintains a stack of drawing states. Drawing states consist of:
The current transformation matrix.
The current clipping region.
The current values of the following attributes: strokeStyle, fillStyle, globalAlpha, lineWidth, lineCap, lineJoin, miterLimit, shadowOffsetX, shadowOffsetY, shadowBlur, shadowColor, globalCompositeOperation, font, textAlign, textBaseline.
The current path and the current bitmap are not part
of the drawing state. The current path is persistent, and can only
be reset using the beginPath() method. The
current bitmap is a property of
the canvas, not the context.
The save()
method must push a copy of the current drawing state onto the
drawing state stack.
The restore() method
must pop the top entry in the drawing state stack, and reset the
drawing state it describes. If there is no saved state, the method
must do nothing.
The transformation matrix is applied to coordinates when creating
shapes and paths.
When the context is created, the transformation matrix must
initially be the identity transform. It may then be adjusted using
the transformation methods.
The transformations must be performed in reverse order. For
instance, if a scale transformation that doubles the width is
applied, followed by a rotation transformation that rotates drawing
operations by a quarter turn, and a rectangle twice as wide as it is
tall is then drawn on the canvas, the actual result will be a
square.
The scale(x, y) method must
add the scaling transformation described by the arguments to the
transformation matrix. The x argument represents
the scale factor in the horizontal direction and the y argument represents the scale factor in the
vertical direction. The factors are multiples.
The rotate(angle) method must add the rotation
transformation described by the argument to the transformation
matrix. The angle argument represents a
clockwise rotation angle expressed in radians.
The translate(x, y) method must
add the translation transformation described by the arguments to the
transformation matrix. The x argument represents
the translation distance in the horizontal direction and the y argument represents the translation distance in the
vertical direction. The arguments are in coordinate space units.
The transform(m11, m12, m21, m22, dx,
dy) method must multiply the
current transformation matrix with the matrix described by:
| m11 |
m21 |
dx |
| m12 |
m22 |
dy |
| 0 |
0 |
1 |
The setTransform(m11, m12, m21, m22, dx,
dy) method must reset the current
transform to the identity matrix, and then invoke the transform(m11, m12, m21, m22, dx,
dy) method with the same arguments.
4.8.11.1.3 Compositing
All drawing operations are affected by the global compositing
attributes, globalAlpha and globalCompositeOperation.
The globalAlpha
attribute gives an alpha value that is applied to shapes and images
before they are composited onto the canvas. The value must be in the
range from 0.0 (fully transparent) to 1.0 (no additional
transparency). If an attempt is made to set the attribute to a value
outside this range, the attribute must retain its previous
value. When the context is created, the globalAlpha attribute must
initially have the value 1.0.
The globalCompositeOperation
attribute sets how shapes and images are drawn onto the existing
bitmap, once they have had globalAlpha and the
current transformation matrix applied. It must be set to a value
from the following list. In the descriptions below, the source
image, A, is the shape or image being rendered,
and the destination image, B, is the current
state of the bitmap.
source-atop- A atop B. Display the
source image wherever both images are opaque. Display the
destination image wherever the destination image is opaque but the
source image is transparent. Display transparency elsewhere.
source-in- A in B. Display the
source image wherever both the source image and destination image
are opaque. Display transparency elsewhere.
source-out- A out B. Display the
source image wherever the source image is opaque and the
destination image is transparent. Display transparency
elsewhere.
source-over (default)- A over B. Display the
source image wherever the source image is opaque. Display the
destination image elsewhere.
destination-atop- B atop A. Same as
source-atop but using the
destination image instead of the source image and vice versa.
destination-in- B in A. Same as
source-in but using the destination
image instead of the source image and vice versa.
destination-out- B out A. Same as
source-out but using the destination
image instead of the source image and vice versa.
destination-over- B over A. Same as
source-over but using the
destination image instead of the source image and vice versa.
lighter- A plus B. Display the
sum of the source image and destination image, with color values
approaching 1 as a limit.
copy- A (B is
ignored). Display the source image instead of the destination
image.
xor- A xor B. Exclusive OR
of the source image and destination image.
vendorName-operationName- Vendor-specific extensions to the list of composition operators
should use this syntax.
These values are all case-sensitive — they must be used
exactly as shown. User agents must not recognize values that are not
a case-sensitive match for one of the values given
above.
The operators in the above list must be treated as described by
the Porter-Duff operator given at the start of their description
(e.g. A over B). [PORTERDUFF]
On setting, if the user agent does not recognize the specified
value, it must be ignored, leaving the value of globalCompositeOperation
unaffected.
When the context is created, the globalCompositeOperation
attribute must initially have the value
source-over.
4.8.11.1.4 Colors and styles
The strokeStyle
attribute represents the color or style to use for the lines around
shapes, and the fillStyle
attribute represents the color or style to use inside the
shapes.
Both attributes can be either strings,
CanvasGradients, or CanvasPatterns. On
setting, strings must be parsed as CSS <color> values and the
color assigned, and CanvasGradient and
CanvasPattern objects must be assigned themselves. [CSS3COLOR] If the value is a string but
is not a valid color, or is neither a string, a
CanvasGradient, nor a CanvasPattern, then
it must be ignored, and the attribute must retain its previous
value.
On getting, if the value is a color, then the serialization of the color
must be returned. Otherwise, if it is not a color but a
CanvasGradient or CanvasPattern, then the
respective object must be returned. (Such objects are opaque and
therefore only useful for assigning to other attributes or for
comparison to other gradients or patterns.)
The serialization of a color for a color value is a
string, computed as follows: if it has alpha equal to 1.0, then the
string is a lowercase six-digit hex value, prefixed with a "#"
character (U+0023 NUMBER SIGN), with the first two digits
representing the red component, the next two digits representing the
green component, and the last two digits representing the blue
component, the digits being in the range 0-9 a-f (U+0030 to U+0039
and U+0061 to U+0066). Otherwise, the color value has alpha less
than 1.0, and the string is the color value in the CSS rgba() functional-notation format: the literal
string rgba (U+0072 U+0067 U+0062 U+0061)
followed by a U+0028 LEFT PARENTHESIS, a base-ten integer in the
range 0-255 representing the red component (using digits 0-9, U+0030
to U+0039, in the shortest form possible), a literal U+002C COMMA
and U+0020 SPACE, an integer for the green component, a comma and a
space, an integer for the blue component, another comma and space, a
U+0030 DIGIT ZERO, a U+002E FULL STOP (representing the decimal
point), one or more digits in the range 0-9 (U+0030 to U+0039)
representing the fractional part of the alpha value, and finally a
U+0029 RIGHT PARENTHESIS.
When the context is created, the strokeStyle and fillStyle attributes must
initially have the string value #000000.
There are two types of gradients, linear gradients and radial
gradients, both represented by objects implementing the opaque
CanvasGradient interface.
Once a gradient has been created (see below),
stops are placed along it to define how the colors are distributed
along the gradient. The color of the gradient at each stop is the
color specified for that stop. Between each such stop, the colors
and the alpha component must be linearly interpolated over the RGBA
space without premultiplying the alpha value to find the color to
use at that offset. Before the first stop, the color must be the
color of the first stop. After the last stop, the color must be the
color of the last stop. When there are no stops, the gradient is
transparent black.
The addColorStop(offset, color)
method on the CanvasGradient interface adds a new stop
to a gradient. If the offset is less than 0,
greater than 1, infinite, or NaN, then an
INDEX_SIZE_ERR exception must be raised. If the color cannot be parsed as a CSS color, then a
SYNTAX_ERR exception must be raised. Otherwise, the
gradient must have a new stop placed, at offset offset relative to the whole gradient, and with the
color obtained by parsing color as a CSS
<color> value. If multiple stops are added at the same offset
on a gradient, they must be placed in the order added, with the
first one closest to the start of the gradient, and each subsequent
one infinitesimally further along towards the end point (in effect
causing all but the first and last stop added at each point to be
ignored).
The createLinearGradient(x0, y0, x1,
y1) method takes four arguments
that represent the start point (x0, y0) and end point (x1, y1) of the gradient. If any of the arguments to createLinearGradient()
are infinite or NaN, the method must raise a
NOT_SUPPORTED_ERR exception. Otherwise, the method must
return a linear CanvasGradient initialized with the
specified line.
Linear gradients must be rendered such that all points on a line
perpendicular to the line that crosses the start and end points have
the color at the point where those two lines cross (with the colors
coming from the interpolation and
extrapolation described above). The points in the linear
gradient must be transformed as described by the current transformation
matrix when rendering.
If x0 = x1 and y0 = y1, then the linear gradient must
paint nothing.
The createRadialGradient(x0, y0, r0,
x1, y1, r1) method takes six arguments, the
first three representing the start circle with origin (x0, y0) and radius r0, and the last three representing the end circle
with origin (x1, y1) and
radius r1. The values are in coordinate space
units. If any of the arguments are infinite or NaN, a
NOT_SUPPORTED_ERR exception must be raised. If either
of r0 or r1 are negative, an
INDEX_SIZE_ERR exception must be raised. Otherwise,
the method must return a radial CanvasGradient
initialized with the two specified circles.
Radial gradients must be rendered by following these steps:
If x0 = x1 and y0 = y1 and r0 = r1, then the radial gradient must
paint nothing. Abort these steps.
-
Let x(ω) = (x1-x0)ω + x0
Let y(ω) = (y1-y0)ω + y0
Let r(ω) = (r1-r0)ω + r0
Let the color at ω be the color at
that position on the gradient (with the colors coming from the interpolation and extrapolation
described above).
For all values of ω where
r(ω) > 0,
starting with the value of ω nearest to
positive infinity and ending with the value of ω nearest to negative infinity, draw the
circumference of the circle with radius r(ω) at position (x(ω), y(ω)), with the color at ω, but only painting on the parts of the
canvas that have not yet been painted on by earlier circles in this
step for this rendering of the gradient.
This effectively creates a cone, touched by the two
circles defined in the creation of the gradient, with the part of
the cone before the start circle (0.0) using the color of the first
offset, the part of the cone after the end circle (1.0) using the
color of the last offset, and areas outside the cone untouched by
the gradient (transparent black).
Gradients must be painted only where the relevant stroking or
filling effects requires that they be drawn.
The points in the radial gradient must be transformed as
described by the current
transformation matrix when rendering.
Patterns are represented by objects implementing the opaque
CanvasPattern interface.
To create objects of this type, the createPattern(image, repetition)
method is used. The first argument gives the image to use as the
pattern (either an HTMLImageElement or an
HTMLCanvasElement). Modifying this image after calling
the createPattern() method
must not affect the pattern. The second argument must be a string
with one of the following values: repeat,
repeat-x, repeat-y,
no-repeat. If the empty string or null is
specified, repeat must be assumed. If an
unrecognized value is given, then the user agent must raise a
SYNTAX_ERR exception. User agents must recognize the
four values described above exactly (e.g. they must not do case
folding). The method must return a CanvasPattern object
suitably initialized.
The image argument must be an instance of an
HTMLImageElement or HTMLCanvasElement. If
the image is of the wrong type or null, the
implementation must raise a TYPE_MISMATCH_ERR
exception.
If the image argument is an
HTMLImageElement object whose complete attribute is false, then
the implementation must raise an INVALID_STATE_ERR
exception.
If the image argument is an
HTMLCanvasElement object with either a horizontal
dimension or a vertical dimension equal to zero, then the
implementation must raise an INVALID_STATE_ERR
exception.
Patterns must be painted so that the top left of the first image
is anchored at the origin of the coordinate space, and images are
then repeated horizontally to the left and right (if the
repeat-x string was specified) or vertically up and
down (if the repeat-y string was specified) or in all
four directions all over the canvas (if the repeat
string was specified). The images are not scaled by this process;
one CSS pixel of the image must be painted on one coordinate space
unit. Of course, patterns must actually be painted only where the
stroking or filling effect requires that they be drawn, and are
affected by the current transformation matrix.
When the createPattern() method
is passed, as its image argument, an animated
image, the poster frame of the animation, or the first frame of the
animation if there is no poster frame, must be used.
4.8.11.1.5 Line styles
The lineWidth
attribute gives the width of lines, in coordinate space units. On
setting, zero, negative, infinite, and NaN values must be ignored,
leaving the value unchanged.
When the context is created, the lineWidth attribute must
initially have the value 1.0.
The lineCap attribute
defines the type of endings that UAs will place on the end of
lines. The three valid values are butt,
round, and square. The butt
value means that the end of each line has a flat edge perpendicular
to the direction of the line (and that no additional line cap is
added). The round value means that a semi-circle with
the diameter equal to the width of the line must then be added on to
the end of the line. The square value means that a
rectangle with the length of the line width and the width of half
the line width, placed flat against the edge perpendicular to the
direction of the line, must be added at the end of each line. On
setting, any other value than the literal strings butt,
round, and square must be ignored, leaving
the value unchanged.
When the context is created, the lineCap attribute must
initially have the value butt.
The lineJoin
attribute defines the type of corners that UAs will place where two
lines meet. The three valid values are bevel,
round, and miter.
On setting, any other value than the literal strings
bevel, round, and miter must
be ignored, leaving the value unchanged.
When the context is created, the lineJoin attribute must
initially have the value miter.
A join exists at any point in a subpath shared by two consecutive
lines. When a subpath is closed, then a join also exists at its
first point (equivalent to its last point) connecting the first and
last lines in the subpath.
In addition to the point where the join occurs, two additional
points are relevant to each join, one for each line: the two corners
found half the line width away from the join point, one
perpendicular to each line, each on the side furthest from the other
line.
A filled triangle connecting these two opposite corners with a
straight line, with the third point of the triangle being the join
point, must be rendered at all joins. The lineJoin attribute controls
whether anything else is rendered. The three aforementioned values
have the following meanings:
The bevel value means that this is all that is
rendered at joins.
The round value means that a filled arc connecting
the two aforementioned corners of the join, abutting (and not
overlapping) the aforementioned triangle, with the diameter equal to
the line width and the origin at the point of the join, must be
rendered at joins.
The miter value means that a second filled triangle
must (if it can given the miter length) be rendered at the join,
with one line being the line between the two aforementioned corners,
abutting the first triangle, and the other two being continuations of
the outside edges of the two joining lines, as long as required to
intersect without going over the miter length.
The miter length is the distance from the point where the lines
touch on the inside of the join to the intersection of the line
edges on the outside of the join. The miter limit ratio is the
maximum allowed ratio of the miter length to half the line width. If
the miter length would cause the miter limit ratio to be exceeded,
this second triangle must not be rendered.
The miter limit ratio can be explicitly set using the miterLimit
attribute. On setting, zero, negative, infinite, and NaN values must
be ignored, leaving the value unchanged.
When the context is created, the miterLimit attribute must
initially have the value 10.0.
4.8.11.1.6 Shadows
All drawing operations are affected by the four global shadow
attributes.
The shadowColor
attribute sets the color of the shadow.
When the context is created, the shadowColor attribute
initially must be fully-transparent black.
On getting, the serialization of the color must be returned.
On setting, the new value must be parsed as a CSS <color>
value and the color assigned. If the value is not a valid color,
then it must be ignored, and the attribute must retain its previous
value. [CSS3COLOR]
The shadowOffsetX
and shadowOffsetY
attributes specify the distance that the shadow will be offset in
the positive horizontal and positive vertical distance
respectively. Their values are in coordinate space units. They are
not affected by the current transformation matrix.
When the context is created, the shadow offset attributes must
initially have the value 0.
On getting, they must return their current value. On setting, the
attribute being set must be set to the new value, except if the
value is infinite or NaN, in which case the new value must be
ignored.
The shadowBlur
attribute specifies the size of the blurring effect. (The units do
not map to coordinate space units, and are not affected by the
current transformation matrix.)
When the context is created, the shadowBlur attribute must
initially have the value 0.
On getting, the attribute must return its current value. On
setting the attribute must be set to the new value, except if the
value is negative, infinite or NaN, in which case the new value must
be ignored.
When shadows are drawn, they must be rendered as follows:
-
Let A be the source image for which a
shadow is being created.
-
Let B be an infinite transparent black
bitmap, with a coordinate space and an origin identical to A.
-
Copy the alpha channel of A to B, offset by shadowOffsetX in the
positive x direction, and shadowOffsetY in the
positive y direction.
-
If shadowBlur is greater than
0:
-
If shadowBlur is less than
8, let σ be half the value of shadowBlur; otherwise,
let σ be the square root of multiplying
the value of shadowBlur by
2.
-
Perform a 2D Gaussian Blur on B,
using σ as the standard
deviation.
User agents may limit values of σ to
an implementation-specific maximum value to avoid exceeding
hardware limitations during the Gaussian blur operation.
-
Set the red, green, and blue components of every pixel in
B to the red, green, and blue components
(respectively) of the color of shadowColor.
-
Multiply the alpha component of every pixel in B by the alpha component of the color of shadowColor.
-
The shadow is in the bitmap B, and is
rendered as part of the drawing model described below.
4.8.11.1.7 Simple shapes (rectangles)
There are three methods that immediately draw rectangles to the
bitmap. They each take four arguments; the first two give the x and y coordinates of the top
left of the rectangle, and the second two give the width w and height h of the rectangle,
respectively.
The current
transformation matrix must be applied to the following four
coordinates, which form the path that must then be closed to get the
specified rectangle: (x, y), (x+w, y),
(x+w,
y+h),
(x, y+h).
Shapes are painted without affecting the current path, and are
subject to the clipping region,
and, with the exception of clearRect(), also shadow effects, global alpha, and global composition
operators.
The clearRect(x, y, w, h) method must clear the pixels in the
specified rectangle that also intersect the current clipping region
to a fully transparent black, erasing any previous image. If either
height or width are zero, this method has no effect.
The fillRect(x, y, w, h) method must paint the specified
rectangular area using the fillStyle. If either height
or width are zero, this method has no effect.
The strokeRect(x, y, w, h) method must stroke the specified
rectangle's path using the strokeStyle, lineWidth, lineJoin, and (if
appropriate) miterLimit attributes. If
both height and width are zero, this method has no effect, since
there is no path to stroke (it's a point). If only one of the two is
zero, then the method will draw a line instead (the path for the
outline is just a straight line along the non-zero dimension).
4.8.11.1.8 Complex shapes (paths)
The context always has a current path. There is only one current
path, it is not part of the drawing
state.
A path has a list of zero or more subpaths. Each
subpath consists of a list of one or more points, connected by
straight or curved lines, and a flag indicating whether the subpath
is closed or not. A closed subpath is one where the last point of
the subpath is connected to the first point of the subpath by a
straight line. Subpaths with fewer than two points are ignored when
painting the path.
Initially, the context's path must have zero subpaths.
The points and lines added to the path by these methods must be
transformed according to the current transformation
matrix as they are added.
The beginPath()
method must empty the list of subpaths so that the context once
again has zero subpaths.
The moveTo(x, y) method must
create a new subpath with the specified point as its first (and
only) point.
The closePath()
method must do nothing if the context has no subpaths. Otherwise, it
must mark the last subpath as closed, create a new subpath whose
first point is the same as the previous subpath's first point, and
finally add this new subpath to the path. (If the last subpath had
more than one point in its list of points, then this is equivalent
to adding a straight line connecting the last point back to the
first point, thus "closing" the shape, and then repeating the last
moveTo() call.)
New points and the lines connecting them are added to subpaths
using the methods described below. In all cases, the methods only
modify the last subpath in the context's paths.
The lineTo(x, y) method must do
nothing if the context has no subpaths. Otherwise, it must connect
the last point in the subpath to the given point (x, y) using a straight line, and
must then add the given point (x, y) to the subpath.
The quadraticCurveTo(cpx, cpy, x,
y) method must do nothing if the
context has no subpaths. Otherwise it must connect the last point in
the subpath to the given point (x, y) using a quadratic Bézier curve with control
point (cpx, cpy), and must
then add the given point (x, y) to the subpath. [BEZIER]
The bezierCurveTo(cp1x, cp1y, cp2x, cp2y, x, y) method must do
nothing if the context has no subpaths. Otherwise, it must connect
the last point in the subpath to the given point (x, y) using a cubic Bézier
curve with control points (cp1x, cp1y) and (cp2x, cp2y). Then, it must add the point (x, y) to the subpath. [BEZIER]
The arcTo(x1, y1, x2,
y2, radius)
method must do nothing if the context has no subpaths. If the
context does have a subpath, then the behavior depends on
the arguments and the last point in the subpath.
Negative values for radius must cause the
implementation to raise an INDEX_SIZE_ERR
exception.
Let the point (x0, y0) be
the last point in the subpath.
If the point (x0, y0) is
equal to the point (x1, y1),
or if the point (x1, y1) is
equal to the point (x2, y2),
or if the radius radius is zero, then the method
must add the point (x1, y1)
to the subpath, and connect that point to the previous point (x0, y0) by a straight line.
Otherwise, if the points (x0, y0), (x1, y1), and (x2, y2) all lie on a single straight line, then: if the
direction from (x0, y0) to
(x1, y1) is the same as the
direction from (x1, y1) to
(x2, y2), then the method
must add the point (x1, y1)
to the subpath, and connect that point to the previous point (x0, y0) by a straight line;
otherwise, the direction from (x0, y0) to (x1, y1) is the opposite of the direction from (x1, y1) to (x2, y2), and the method must add
a point (x∞, y∞) to the subpath, and connect that
point to the previous point (x0, y0) by a straight line, where (x∞, y∞) is the point that is infinitely
far away from (x1, y1), that
lies on the same line as (x0, y0), (x1, y1), and (x2, y2), and that is on the same side of (x1, y1) on that line as (x2, y2).
Otherwise, let The Arc be the shortest arc
given by circumference of the circle that has radius radius, and that has one point tangent to the
half-infinite line that crosses the point (x0,
y0) and ends at the point (x1, y1), and that has a different
point tangent to the half-infinite line that ends at the point (x1, y1) and crosses the point
(x2, y2). The points at
which this circle touches these two lines are called the start and
end tangent points respectively.
The method must connect the point (x0, y0) to the start tangent point by a straight line,
adding the start tangent point to the subpath, and then must connect
the start tangent point to the end tangent point by The Arc, adding the end tangent point to the
subpath.
The arc(x, y, radius,
startAngle, endAngle, anticlockwise) method draws an arc. If
the context has any subpaths, then the method must add a straight
line from the last point in the subpath to the start point of the
arc. In any case, it must draw the arc between the start point of
the arc and the end point of the arc, and add the start and end
points of the arc to the subpath. The arc and its start and end
points are defined as follows:
Consider a circle that has its origin at (x,
y) and that has radius radius. The points at startAngle
and endAngle along this circle's circumference,
measured in radians clockwise from the positive x-axis, are the
start and end points respectively.
If the anticlockwise argument is false and
endAngle-startAngle is equal to or greater than
2π, or, if the anticlockwise
argument is true and startAngle-endAngle is
equal to or greater than 2π, then the arc is the
whole circumference of this circle.
Otherwise, the arc is the path along the circumference of this
circle from the start point to the end point, going anti-clockwise
if the anticlockwise argument is true, and
clockwise otherwise. Since the points are on the circle, as opposed
to being simply angles from zero, the arc can never cover an angle
greater than 2π radians. If the two points are the
same, or if the radius is zero, then the arc is defined as being of
zero length in both directions.
Negative values for radius must cause the
implementation to raise an INDEX_SIZE_ERR
exception.
The rect(x, y, w, h) method must create a new subpath
containing just the four points (x, y), (x+w,
y), (x+w, y+h),
(x, y+h), with those four points connected by straight
lines, and must then mark the subpath as closed. It must then create
a new subpath with the point (x, y) as the only point in the subpath.
The fill()
method must fill all the subpaths of the current path, using
fillStyle, and using
the non-zero winding number rule. Open subpaths must be implicitly
closed when being filled (without affecting the actual
subpaths).
Thus, if two overlapping but otherwise independent
subpaths have opposite windings, they cancel out and result in no
fill. If they have the same winding, that area just gets painted
once.
The stroke() method
must calculate the strokes of all the subpaths of the current path,
using the lineWidth,
lineCap, lineJoin, and (if
appropriate) miterLimit attributes, and
then fill the combined stroke area using the strokeStyle
attribute.
Since the subpaths are all stroked as one,
overlapping parts of the paths in one stroke operation are treated
as if their union was what was painted.
Paths, when filled or stroked, must be painted without affecting
the current path, and must be subject to shadow effects, global alpha, the clipping region, and global composition
operators. (Transformations affect the path when the path is
created, not when it is painted, though the stroke style is
still affected by the transformation during painting.)
Zero-length line segments must be pruned before stroking a
path. Empty subpaths must be ignored.
The clip()
method must create a new clipping region by calculating
the intersection of the current clipping region and the area
described by the current path, using the non-zero winding number
rule. Open subpaths must be implicitly closed when computing the
clipping region, without affecting the actual subpaths. The new
clipping region replaces the current clipping region.
When the context is initialized, the clipping region must be set
to the rectangle with the top left corner at (0,0) and the width and
height of the coordinate space.
The isPointInPath(x, y) method must
return true if the point given by the x and y coordinates passed to the method, when treated as
coordinates in the canvas coordinate space unaffected by the current
transformation, is inside the current path as determined by the
non-zero winding number rule; and must return false
otherwise. Points on the path itself are considered to be inside the
path. If either of the arguments is infinite or NaN, then the method
must return false.
4.8.11.1.9 Text4.8.11.1.9 テキスト
The font DOM
attribute, on setting, must be parsed the same way as the 'font'
property of CSS (but without supporting property-independent
stylesheet syntax like 'inherit'), and the resulting font must be
assigned to the context, with the 'line-height' component forced to
'normal'. If the new value is syntactically incorrect, then it must
be ignored, without assigning a new font value. [CSS]
Font names must be interpreted in the context of the
canvas element's stylesheets; any fonts embedded using
@font-face must therefore be available. [CSSWEBFONTS]
Only vector fonts should be used by the user agent; if a user
agent were to use bitmap fonts then transformations would likely
make the font look very ugly.
On getting, the font
attribute must return the serialized form of the current font of the
context. [CSSOM]
When the context is created, the font of the context must be set
to 10px sans-serif. When the 'font-size' component is set to lengths
using percentages, 'em' or 'ex' units, or the 'larger' or 'smaller'
keywords, these must be interpreted relative to the computed value
of the 'font-size' property of the corresponding canvas
element at the time that the attribute is set. When the
'font-weight' component is set to the relative values 'bolder' and
'lighter', these must be interpreted relative to the computed value
of the 'font-weight' property of the corresponding
canvas element at the time that the attribute is
set. If the computed values are undefined for a particular case
(e.g. because the canvas element is not in a document),
then the relative keywords must be interpreted relative to the
normal-weight 10px sans-serif default.
The textAlign DOM
attribute, on getting, must return the current value. On setting, if
the value is one of start, end, left, right, or center, then the
value must be changed to the new value. Otherwise, the new value
must be ignored. When the context is created, the textAlign attribute must
initially have the value start.
The textBaseline
DOM attribute, on getting, must return the current value. On
setting, if the value is one of top, hanging, middle, alphabetic,
ideographic,
or bottom,
then the value must be changed to the new value. Otherwise, the new
value must be ignored. When the context is created, the textBaseline attribute
must initially have the value alphabetic.
The textBaseline
attribute's allowed keywords correspond to alignment points in the
font:
The keywords map to these alignment points as follows:
top
- The top of the em square
hanging
- The hanging baseline
middle
- The middle of the em square
alphabetic
- The alphabetic baseline
ideographic
- The ideographic baseline
bottom
- The bottom of the em square
The fillText() and
strokeText()
methods take three or four arguments, text, x, y, and optionally maxWidth, and render the given text at the given (x, y) coordinates ensuring that the text isn't wider
than maxWidth if specified, using the current
font, textAlign, and textBaseline
values. Specifically, when the methods are called, the user agent
must run the following steps:
Let font be the current font of the
context, as given by the font attribute.
Replace all the space
characters in text with U+0020 SPACE
characters.
Form a hypothetical infinitely wide CSS line box containing
a single inline box containing the text text,
with all the properties at their initial values except the 'font'
property of the inline box set to font and the
'direction' property of the inline box set to the
directionality of the canvas element. [CSS]
If the maxWidth argument was specified
and the hypothetical width of the inline box in the hypothetical
line box is greater than maxWidth CSS pixels,
then change font to have a more condensed font
(if one is available or if a reasonably readable one can be
synthesized by applying a horizontal scale factor to the font) or a
smaller font, and return to the previous step.
-
Let the anchor point be a point on the
inline box, determined by the textAlign and textBaseline values, as
follows:
Horizontal position:
- If
textAlign is left
- If
textAlign is start and the directionality of the
canvas element is 'ltr'
- If
textAlign is end and the directionality of the
canvas element is 'rtl'
- Let the anchor point's horizontal
position be the left edge of the inline box.
- If
textAlign is right
- If
textAlign is end and the directionality of the
canvas element is 'ltr'
- If
textAlign is start and the directionality of the
canvas element is 'rtl'
- Let the anchor point's horizontal
position be the right edge of the inline box.
- If
textAlign is center
- Let the anchor point's horizontal
position be half way between the left and right edges of the
inline box.
Vertical position:
- If
textBaseline is top
- Let the anchor point's vertical position
be the top of the em box of the first available font of the
inline box.
- If
textBaseline is hanging
- Let the anchor point's vertical position
be the hanging baseline of the first available font of the inline
box.
- If
textBaseline is middle
- Let the anchor point's vertical position
be half way between the bottom and the top of the em box of the
first available font of the inline box.
- If
textBaseline is alphabetic
- Let the anchor point's vertical position
be the alphabetic baseline of the first available font of the inline
box.
- If
textBaseline is ideographic
- Let the anchor point's vertical position
be the ideographic baseline of the first available font of the inline
box.
- If
textBaseline is bottom
- Let the anchor point's vertical position
be the bottom of the em box of the first available font of the
inline box.
-
Paint the hypothetical inline box as the shape given by the
text's glyphs, as transformed by the current transformation
matrix, and anchored and sized so that before applying the
current transformation
matrix, the anchor point is at (x, y) and each CSS pixel is
mapped to one coordinate space unit.
For fillText()
fillStyle must be
applied to the glyphs and strokeStyle must be
ignored. For strokeText() the reverse
holds and strokeStyle must be
applied to the glyph outlines and fillStyle must be
ignored.
Text is painted without affecting the current path, and is
subject to shadow effects, global alpha, the clipping region, and global composition
operators.
The measureText()
method takes one argument, text. When the method
is invoked, the user agent must replace all the space characters in text with
U+0020 SPACE characters, and then must form a hypothetical
infinitely wide CSS line box containing a single inline box
containing the text text, with all the
properties at their initial values except the 'font' property of the
inline element set to the current font of the context, as given by
the font attribute, and
must then return a new TextMetrics object with its
width attribute set to
the width of that inline box, in CSS pixels. [CSS]
The TextMetrics interface is used for the objects
returned from measureText(). It has one
attribute, width, which is set
by the measureText()
method.
Glyphs rendered using fillText() and strokeText() can spill out
of the box given by the font size (the em square size) and the width
returned by measureText() (the text
width). This version of the specification does not provide a way to
obtain the bounding box dimensions of the text. If the text is to be
rendered and removed, care needs to be taken to replace the entire
area of the canvas that the clipping region covers, not just the box
given by the em square height and measured text width.
A future version of the 2D context API may provide a
way to render fragments of documents, rendered using CSS, straight
to the canvas. This would be provided in preference to a dedicated
way of doing multiline layout.
4.8.11.1.10 Images
To draw images onto the canvas, the drawImage method
can be used.メソッド drawImage
は画布上に画像を描画するために使用することができます。
This method is overloaded with three variants: drawImage(image, dx, dy), drawImage(image, dx, dy, dw,
dh), and drawImage(image, sx, sy, sw, sh,
dx, dy, dw, dh). (Actually it is
overloaded with six; each of those three can take either an
HTMLImageElement or an HTMLCanvasElement
for the image argument.) If not specified, the
dw and dh arguments must
default to the values of sw and sh, interpreted such that one CSS pixel in the image
is treated as one unit in the canvas coordinate space. If the sx, sy, sw,
and sh arguments are omitted, they must default
to 0, 0, the image's intrinsic width in image pixels, and the
image's intrinsic height in image pixels, respectively.このメソッドは、drawImage(image, dx, dy)、drawImage(image, dx, dy, dw, dh)、drawImage(image, sx, sy, sw, sh, dx, dy, dw, dh) の3通りに多重定義されています。(実際には
6通りで、3通りのいずれの場合も、 image 引数に
HTMLImageElement か HTMLCanvasElement
のいずれかを指定できます。)
引数 dw および dh は、
指定されていない場合、既定値として、 sw と
sh の値を使用しなければなりません。
その場合、画像中の 1 CSS 画素が画布座標空間上の1単位として処理されることとなります。
引数 sx、sy、
sw、 sh が省略された場合、
それぞれ既定値の 0、0、画像の画素における画像の内在幅、
画像の画素における画像の内在高としなければなりません。
The image argument must be an instance of an
HTMLImageElement or HTMLCanvasElement. If
the image is of the wrong type or null, the
implementation must raise a TYPE_MISMATCH_ERR
exception.
If the image argument is an
HTMLImageElement object whose complete attribute is false, then
the implementation must raise an INVALID_STATE_ERR
exception.
The source rectangle is the rectangle whose corners are the four
points (sx, sy), (sx+sw, sy), (sx+sw, sy+sh), (sx, sy+sh).原始矩形は、その頂点が4点
(sx, sy), (sx+sw, sy),
(sx+sw, sy+sh), (sx,
sy+sh)
であるような矩形です。
If the source rectangle is not entirely within the source image,
or if one of the sw or sh
arguments is zero, the implementation must raise an
INDEX_SIZE_ERR exception.
The destination rectangle is the rectangle whose corners are the
four points (dx, dy),
(dx+dw, dy), (dx+dw, dy+dh), (dx, dy+dh).目的矩形は、その頂点が4点
(dx, dy), (dx+dw, dy),
(dx+dw, dy+dh), (dx,
dy+dh)
であるような矩形です。
When drawImage() is
invoked, the region of the image specified by the source rectangle
must be painted on the region of the canvas specified by the
destination rectangle, after applying the current transformation
matrix to the points of the destination rectangle.drawImage() が呼び出されたとき、
原始矩形で指定される画像上の領域は、
現在変形行列を目的矩形の点に適用した後、
目的矩形で指定される画布上の領域に塗られなければなりません。
When a canvas is drawn onto itself, the drawing
model requires the source to be copied before the image is drawn
back onto the canvas, so it is possible to copy parts of a canvas
onto overlapping parts of itself.画布がそれ自体に塗られるとき、この描画モデルに従うと原始画像は画布上に重ねて描画する以前に複写されなければなりませんから、
画布の一部分をそれと重複する部分に複写することが可能です。
When the drawImage() method is
passed, as its image argument, an animated
image, the poster frame of the animation, or the first frame of the
animation if there is no poster frame, must be used.drawImage() メソッドが image 引数にアニメーション画像を引き渡されたとき、
そのアニメーションのポスター枠か、ポスター枠がない場合には最初の枠が使用されなければなりません。
Images are painted without affecting the current path, and are
subject to shadow effects, global alpha, the clipping region, and global composition
operators.画像は現在経路に影響せずに塗られ、影効果、
大域アルファ、
くり抜き領域、
大域合成操作の対象でもあります。
4.8.11.1.11 Pixel manipulation
The createImageData(sw, sh) method must
return an ImageData object representing a rectangle
with a width in CSS pixels equal to the absolute magnitude of sw and a height in CSS pixels equal to the absolute
magnitude of sh, filled with transparent
black.
The getImageData(sx, sy, sw,
sh) method must return an
ImageData object representing the underlying pixel data
for the area of the canvas denoted by the rectangle whose corners are
the four points (sx, sy),
(sx+sw, sy), (sx+sw, sy+sh), (sx, sy+sh), in canvas
coordinate space units. Pixels outside the canvas must be returned
as transparent black. Pixels must be returned as non-premultiplied
alpha values.
If any of the arguments to createImageData() or
getImageData() are
infinite or NaN, the method must instead raise a
NOT_SUPPORTED_ERR exception. If either the sw or sh arguments are zero, the
method must instead raise an INDEX_SIZE_ERR
exception.
ImageData objects must be initialized so that their
width attribute
is set to w, the number of physical device
pixels per row in the image data, their height attribute is
set to h, the number of rows in the image data,
and their data
attribute is initialized to a CanvasPixelArray object
holding the image data. At least one pixel's worth of image data
must be returned.
The CanvasPixelArray object provides ordered,
indexed access to the color components of each pixel of the image
data. The data must be represented in left-to-right order, row by
row top to bottom, starting with the top left, with each pixel's
red, green, blue, and alpha components being given in that order for
each pixel. Each component of each device pixel represented in this
array must be in the range 0..255, representing the 8 bit value for
that component. The components must be assigned consecutive indices
starting with 0 for the top left pixel's red component.
The CanvasPixelArray object thus represents h×w×4 integers. The
length
attribute of a CanvasPixelArray object must return this
number.
The XXX5(index) method must return the value of
the indexth component in the array.
The XXX6(index, value) method
must set the value of the indexth component in
the array to value. JS undefined
values must be converted to zero. Other values must first be
converted to numbers using JavaScript's ToNumber algorithm, and if
the result is a NaN value, then the value be must converted to
zero. If the result is less than 0, it must be clamped to zero. If
the result is more than 255, it must be clamped to 255. If the
number is not an integer, it should be rounded to the nearest
integer using the IEEE 754r convertToIntegerTiesToEven
rounding mode. [ECMA262] [IEEE754R]
The above is not intended to cause these
methods to get any unusual behaviour, it's just supposed to be the
normal behaviour for passing values to a method expecting an octet type.
The width and height (w and h) might be different from the sw
and sh arguments to the above methods, e.g. if
the canvas is backed by a high-resolution bitmap, or if the sw and sh arguments are
negative.
The putImageData(imagedata, dx, dy) and putImageData(imagedata, dx, dy, dirtyX, dirtyY, dirtyWidth, dirtyHeight) methods write data from
ImageData structures back to the canvas.
If any of the arguments to the method are infinite or NaN, the
method must raise a NOT_SUPPORTED_ERR exception.
If the first argument to the method is null or not an
ImageData object then the putImageData() method
must raise a TYPE_MISMATCH_ERR exception.
When the last four arguments are omitted, they must be assumed to
have the values 0, 0, the width member of the imagedata structure, and the height member of the imagedata structure, respectively.
When invoked with arguments that do not, per the last few
paragraphs, cause an exception to be raised, the putImageData() method
must act as follows:
-
Let dxdevice be the x-coordinate
of the device pixel in the underlying pixel data of the canvas
corresponding to the dx coordinate in the
canvas coordinate space.
Let dydevice be the y-coordinate
of the device pixel in the underlying pixel data of the canvas
corresponding to the dy coordinate in the
canvas coordinate space.
-
If dirtyWidth is negative, let dirtyX be dirtyX+dirtyWidth, and let dirtyWidth be equal to the absolute magnitude of
dirtyWidth.
If dirtyHeight is negative, let dirtyY be dirtyY+dirtyHeight, and let dirtyHeight be equal to the absolute magnitude of
dirtyHeight.
-
If dirtyX is negative, let dirtyWidth be dirtyWidth+dirtyX, and
let dirtyX be zero.
If dirtyY is negative, let dirtyHeight be dirtyHeight+dirtyY, and
let dirtyY be zero.
-
If dirtyX+dirtyWidth is greater than the width attribute of the imagedata argument, let dirtyWidth be the value of that width attribute, minus the
value of dirtyX.
If dirtyY+dirtyHeight is greater than the height attribute of the imagedata argument, let dirtyHeight be the value of that height attribute, minus the
value of dirtyY.
-
If, after those changes, either dirtyWidth
or dirtyHeight is negative or zero, stop these
steps without affecting the canvas.
Otherwise, for all integer values of x
and y where dirtyX ≤ x < dirtyX+dirtyWidth
and dirtyY ≤ y < dirtyY+dirtyHeight, copy the four channels of
the pixel with coordinate (x, y) in the imagedata data
structure to the pixel with coordinate (dxdevice+x,
dydevice+y) in the underlying pixel data of the
canvas.
The handling of pixel rounding when the specified coordinates do
not exactly map to the device coordinate space is not defined by
this specification, except that the following must result in no
visible changes to the rendering:
context.putImageData(context.getImageData(x, y, w, h), x, y);
...for any value of x, y,
w, and h, and the following
two calls:
context.createImageData(w, h);
context.getImageData(0, 0, w, h);
...must return ImageData objects with the same
dimensions, for any value of w and h. In other words, while user agents may round the
arguments of these methods so that they map to device pixel
boundaries, any rounding performed must be performed consistently
for all of the createImageData(), getImageData() and putImageData()
operations.
The current path, transformation matrix,
shadow attributes, global alpha, the clipping region, and global composition
operator must not affect the getImageData() and putImageData()
methods.
The data returned by getImageData() is at the
resolution of the canvas backing store, which is likely to not be
one device pixel to each CSS pixel if the display used is a high
resolution display.
In the following example, the script generates an
ImageData object so that it can draw onto it.
// canvas is a reference to a <canvas> element
var context = canvas.getContext('2d');
// create a blank slate
var data = context.createImageData(canvas.width, canvas.height);
// create some plasma
FillPlasma(data, 'green'); // green plasma
// add a cloud to the plasma
AddCloud(data, data.width/2, data.height/2); // put a cloud in the middle
// paint the plasma+cloud on the canvas
context.putImageData(data, 0, 0);
// support methods
function FillPlasma(data, color) { ... }
function AddCloud(data, x, y) { ... }
Here is an example of using getImageData() and putImageData() to
implement an edge detection filter.
<!DOCTYPE HTML>
<html>
<head>
<title>Edge detection demo</title>
<script>
var image = new Image();
function init() {
image.onload = demo;
image.src = "image.jpeg";
}
function demo() {
var canvas = document.getElementsByTagName('canvas')[0];
var context = canvas.getContext('2d');
// draw the image onto the canvas
context.drawImage(image, 0, 0);
// get the image data to manipulate
var input = context.getImageData(0, 0, canvas.width, canvas.height);
// get an empty slate to put the data into
var output = context.createImageData(canvas.width, canvas.height);
// alias some variables for convenience
// notice that we are using input.width and input.height here
// as they might not be the same as canvas.width and canvas.height
// (in particular, they might be different on high-res displays)
var w = input.width, h = input.height;
var inputData = input.data;
var outputData = output.data;
// edge detection
for (var y = 1; y < h-1; y += 1) {
for (var x = 1; x < w-1; x += 1) {
for (var c = 0; c < 3; c += 1) {
var i = (y*w + x)*4 + c;
outputData[i] = 127 + -inputData[i - w*4 - 4] - inputData[i - w*4] - inputData[i - w*4 + 4] +
-inputData[i - 4] + 8*inputData[i] - inputData[i + 4] +
-inputData[i + w*4 - 4] - inputData[i + w*4] - inputData[i + w*4 + 4];
}
outputData[(y*w + x)*4 + 3] = 255; // alpha
}
}
// put the image data back after manipulation
context.putImageData(output, 0, 0);
}
</script>
</head>
<body onload="init()">
<canvas></canvas>
</body>
</html>
4.8.11.1.12 Drawing model
When a shape or image is painted, user agents must follow these
steps, in the order given (or act as if they do):
Render the shape or image, creating image A, as described in the previous sections. For
shapes, the current fill, stroke, and line styles must be honored,
and the stroke must itself also be subjected to the current
transformation matrix.
Render the shadow from image A, using
the current shadow styles, creating image B.
Multiply the alpha component of every pixel in B by globalAlpha.
Within the clipping region, composite B
over the current canvas bitmap using the current composition
operator.
Multiply the alpha component of every pixel in A by globalAlpha.
Within the clipping region, composite A
over the current canvas bitmap using the current composition
operator.
4.8.11.2 Color spaces and color correction
The canvas APIs must perform color correction at
only two points: when rendering images with their own gamma
correction and color space information onto the canvas, to convert
the image to the color space used by the canvas (e.g. using the
drawImage() method
with an HTMLImageElement object), and when rendering
the actual canvas bitmap to the output device.
Thus, in the 2D context, colors used to draw shapes
onto the canvas will exactly match colors obtained through the getImageData()
method.
The toDataURL() method
must not include color space information in the resource
returned. Where the output format allows it, the color of pixels in
resources created by toDataURL() must match those
returned by the getImageData()
method.
In user agents that support CSS, the color space used by a
canvas element must match the color space used for
processing any colors for that element in CSS.
The gamma correction and color space information of images must
be handled in such a way that an image rendered directly using an
img element would use the same colors as one painted on
a canvas element that is then itself
rendered. Furthermore, the rendering of images that have no color
correction information (such as those returned by the toDataURL() method) must be
rendered with no color correction.
Thus, in the 2D context, calling the drawImage() method to render
the output of the toDataURL() method to the
canvas, given the appropriate dimensions, has no visible effect.
4.8.11.3 Security with canvas elements
Information leakage can occur if scripts from
one origin can access information (e.g. read pixels)
from images from another origin (one that isn't the same).
To mitigate this, canvas elements are defined to
have a flag indicating whether they are origin-clean. All
canvas elements must start with their
origin-clean set to true. The flag must be set to false if
any of the following actions occur:
Whenever the toDataURL() method of a
canvas element whose origin-clean flag is set to
false is called, the method must raise a SECURITY_ERR
exception.
Whenever the getImageData() method of
the 2D context of a canvas element whose
origin-clean flag is set to false is called with otherwise
correct arguments, the method must raise a SECURITY_ERR
exception.
Even resetting the canvas state by changing its
width or height attributes doesn't reset
the origin-clean flag.
4.8.12 The map element4.8.12 map 要素
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Flow content.流れ内容。
- Element-specific attributes:要素固有属性:
name- DOM interface:DOM 界面:
-
interface HTMLMapElement : HTMLElement {
attribute DOMString name;
readonly attribute HTMLCollection areas;
readonly attribute HTMLCollection images;
};
The map element, in conjunction with any
area element descendants, defines an image
map.
The name attribute
gives the map a name so that it can be referenced. The attribute
must be present and must have a non-empty value with no space characters. If the id attribute is also specified, both
attributes must have the same value.
The areas attribute
must return an HTMLCollection rooted at the
map element, whose filter matches only
area elements.
The images
attribute must return an HTMLCollection rooted at the
Document node, whose filter matches only
img and object elements that are
associated with this map element according to the
image map processing model.
The DOM attribute name must
reflect the content attribute of the same name.
4.8.13 The area element4.8.13 area 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected, but only if there is a
map element ancestor.
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
altcoordsshapehreftargetpingrelmediahreflangtype- DOM interface:DOM 界面:
-
interface HTMLAreaElement : HTMLElement {
attribute DOMString alt;
attribute DOMString coords;
attribute DOMString shape;
attribute DOMString href;
attribute DOMString target;
attribute DOMString ping;
attribute DOMString rel;
readonly attribute DOMTokenList relList;
attribute DOMString media;
attribute DOMString hreflang;
attribute DOMString type;
};
The area element represents either a hyperlink with
some text and a corresponding area on an image map, or
a dead area on an image map.
If the area element has an href attribute, then the
area element represents a hyperlink. In
this case, the alt
attribute must be present. It specifies the text of the
hyperlink. Its value must be text that, when presented with the
texts specified for the other hyperlinks of the image
map, and with the alternative text of the image, but without
the image itself, provides the user with the same kind of choice as
the hyperlink would when used without its text but with its shape
applied to the image. The alt
attribute may be left blank if there is another area
element in the same image map that points to the same
resource and has a non-blank alt
attribute.
If the area element has no href attribute, then the area
represented by the element cannot be selected, and the alt attribute must be omitted.
In both cases, the shape and
coords attributes specify the
area.
The shape
attribute is an enumerated attribute. The following
table lists the keywords defined for this attribute. The states
given in the first cell of the rows with keywords give the
states to which those keywords map. Some of the keywords are
non-conforming, as noted in the last column.
The attribute may be omitted. The missing value default is
the rectangle state.
The coords
attribute must, if specified, contain a valid list of
integers. This attribute gives the coordinates for the shape
described by the shape
attribute. The processing for this attribute is described as part of
the image map processing model.
In the circle state,
area elements must have a coords attribute present, with three
integers, the last of which must be non-negative. The first integer
must be the distance in CSS pixels from the left edge of the image
to the center of the circle, the second integer must be the distance
in CSS pixels from the top edge of the image to the center of the
circle, and the third integer must be the radius of the circle,
again in CSS pixels.
In the default state
state, area elements must not have a coords attribute. (The area is the
whole image.)
In the polygon state,
area elements must have a coords attribute with at least six
integers, and the number of integers must be even. Each pair of
integers must represent a coordinate given as the distances from the
left and the top of the image in CSS pixels respectively, and all
the coordinates together must represent the points of the polygon,
in order.
In the rectangle state,
area elements must have a coords attribute with exactly four
integers, the first of which must be less than the third, and the
second of which must be less than the fourth. The four points must
represent, respectively, the distance from the left edge of the
image to the left side of the rectangle, the distance from the
top edge to the top side, the distance from the left edge to the
right side, and the distance from the top edge to the bottom side,
all in CSS pixels.
When user agents allow users to follow hyperlinks created using the
area element, as described in the next section, the
href,
target and ping attributes decide how the
link is followed. The rel,
media, hreflang, and type attributes may be used to
indicate to the user the likely nature of the target resource before
the user follows the link.
The target, ping, rel, media, hreflang, and type attributes must be omitted
if the href attribute is
not present.
The activation behavior of area
elements is to run the following steps:
If the DOMActivate event
in question is not trusted (i.e. a click() method call was the reason for the
event being dispatched), and the area element's target attribute is ... then raise an
INVALID_ACCESS_ERR exception.
Otherwise, the user agent must follow the hyperlink defined by the
area element, if any.
The DOM attributes alt, coords, href, target, ping, rel, media, hreflang, and type, each must
reflect the respective content attributes of the same
name.
The DOM attribute shape must
reflect the shape
content attribute, limited to only known values.
The DOM attribute relList must
reflect the rel
content attribute.
4.8.14 Image maps
4.8.14.1 Authoring
An image map allows geometric areas on an image to be
associated with hyperlinks.
An image, in the form of an img element or an
object element representing an image, may be associated
with an image map (in the form of a map element) by
specifying a usemap attribute on
the img or object element. The usemap attribute, if specified, must
be a valid hash-name reference to a map
element.
Consider an image that looks as follows:
If we wanted just the coloured areas to be clickable, we could
do it as follows:
<p>
Please select a shape:
<img src="shapes.png" usemap="#shapes"
alt="Four shapes are available: a red hollow box, a green circle, a blue triangle, and a yellow four-pointed star.">
<map name="shapes">
<area shape=rect coords="50,50,100,100"> <!-- the hole in the red box -->
<area shape=rect coords="25,25,125,125" href="red.html" alt="Red box.">
<area shape=circle coords="200,75,50" href="green.html" alt="Green circle.">
<area shape=poly coords="325,25,262,125,388,125" href="blue.html" alt="Blue triangle.">
<area shape=poly coords="450,25,435,60,400,75,435,90,450,125,465,90,500,75,465,60"
href="yellow.html" alt="Yellow star.">
</map>
</p>
4.8.14.2 Processing model4.8.14.2 処理モデル
If an img element or an object element
representing an image has a usemap attribute specified, user
agents must process it as follows:
First, rules for parsing a hash-name reference
to a map element must be followed. This will return
either an element (the map) or null.
If that returned null, then abort these steps. The image is
not associated with an image map after all.
Otherwise, the user agent must collect all the
area elements that are descendants of the map. Let those be the areas.
Having obtained the list of area elements that form
the image map (the areas), interactive user
agents must process the list in one of two ways.
If the user agent intends to show the text that the
img element represents, then it must use the following
steps.
In user agents that do not support images, or that
have images disabled, object elements cannot represent
images, and thus this section never applies (the fallback
content is shown instead). The following steps therefore only
apply to img elements.
Remove all the area elements in areas that have no href attribute.
Remove all the area elements in areas that have no alt attribute, or whose alt attribute's value is the empty
string, if there is another area element in
areas with the same value in the href attribute and with a
non-empty alt attribute.
Each remaining area element in areas represents a hyperlink. Those
hyperlinks should all be made available to the user in a manner
associated with the text of the img.
In this context, user agents may represent area and
img elements with no specified alt attributes, or whose alt
attributes are the empty string or some other non-visible text, in
a user-agent-defined fashion intended to indicate the lack of
suitable author-provided text.
If the user agent intends to show the image and allow interaction
with the image to select hyperlinks, then the image must be
associated with a set of layered shapes, taken from the
area elements in areas, in reverse
tree order (so the last specified area element in the
map is the bottom-most shape, and the first
element in the map, in tree order, is the
top-most shape).
Each area element in areas must
be processed as follows to obtain a shape to layer onto the
image:
Find the state that the element's shape attribute represents.
Use the rules for parsing a list of integers to
parse the element's coords
attribute, if it is present, and let the result be the coords list. If the attribute is absent, let the
coords list be the empty list.
If the number of items in the coords
list is less than the minimum number given for the
area element's current state, as per the following
table, then the shape is empty; abort these steps.
Check for excess items in the coords
list as per the entry in the following list corresponding to the
shape attribute's state:
- Circle state
- Drop any items in the list beyond the third.
- Default state
- Drop all items in the list.
- Polygon state
- Drop the last item if there's an odd number of items.
- Rectangle state
- Drop any items in the list beyond the fourth.
If the shape attribute
represents the rectangle
state, and the first number in the list is numerically less
than the third number in the list, then swap those two numbers
around.
If the shape attribute
represents the rectangle
state, and the second number in the list is numerically less
than the fourth number in the list, then swap those two numbers
around.
If the shape attribute
represents the circle
state, and the third number in the list is less than or
equal to zero, then the shape is empty; abort these steps.
Now, the shape represented by the element is the one
described for the entry in the list below corresponding to the
state of the shape
attribute:
- Circle state
-
Let x be the first number in coords, y be the second
number, and r be the third number.
The shape is a circle whose center is x
CSS pixels from the left edge of the image and x CSS pixels from the top edge of the image, and
whose radius is r pixels.
- Default state
-
The shape is a rectangle that exactly covers the entire
image.
- Polygon state
-
Let xi be the (2i)th entry in coords,
and yi be the (2i+1)th entry in coords
(the first entry in coords being the one
with index 0).
Let the coordinates be (xi, yi),
interpreted in CSS pixels measured from the top left of the
image, for all integer values of i from 0 to
(N/2)-1, where N is the number of items in coords.
The shape is a polygon whose vertices are given by the coordinates, and whose interior is
established using the even-odd rule. [GRAPHICS]
- Rectangle state
-
Let x1 be the first number in coords, y1 be the second
number, x2 be the third number, and y2 be the fourth number.
The shape is a rectangle whose top-left corner is given by
the coordinate (x1, y1)
and whose bottom right corner is given by the coordinate (x2, y2), those coordinates
being interpreted as CSS pixels from the top left corner of the
image.
For historical reasons, the coordinates must be interpreted
relative to the displayed image, even if it stretched
using CSS or the image element's width and
height attributes.
Mouse clicks on an image associated with a set of layered shapes
per the above algorithm must be dispatched to the top-most shape
covering the point that the pointing device indicated (if any), and
then, must be dispatched again (with a new Event
object) to the image element itself. User agents may also allow
individual area elements representing hyperlinks to be selected and activated
(e.g. using a keyboard); events from this are not also propagated to
the image.
Because a map element (and its
area elements) can be associated with multiple
img and object elements, it is possible
for an area element to correspond to multiple focusable
areas of the document.
Image maps are live; if the DOM is mutated, then the
user agent must act as if it had rerun the algorithms for image
maps.
4.8.15 MathML
The math element from the MathML
namespace falls into the embedded content
category for the purposes of the content models in this
specification.
User agents must handle text other than inter-element
whitespace found in MathML elements whose content models do
not allow raw text by pretending for the purposes of MathML content
models, layout, and rendering that that text is actually wrapped in
an mtext element in the MathML
namespace. (Such text is not, however, conforming.)
User agents must act as if any MathML element whose contents does
not match the element's content model was replaced, for the purposes
of MathML layout and rendering, by an merror
element in the MathML namespace containing some
appropriate error message.
To enable authors to use MathML tools that only accept MathML in
its XML form, interactive HTML user agents are encouraged to
provide a way to export any MathML fragment as a
namespace-well-formed XML fragment.
4.8.16 SVG
The svg element from the SVG namespace
falls into the embedded content category for the
purposes of the content models in this specification.
To enable authors to use SVG tools that only accept SVG in its
XML form, interactive HTML user agents are encouraged to provide a
way to export any SVG fragment as a namespace-well-formed XML
fragment.
4.8.17 Dimension attributes
The width and height attributes on
img, iframe, embed,
object, and video elements may be
specified to give the dimensions of the visual content of the
element (the width and height respectively, relative to the nominal
direction of the output medium), in CSS pixels. The attributes, if
specified, must have values that are valid positive non-zero
integers.
The specified dimensions given may differ from the dimensions
specified in the resource itself, since the resource may have a
resolution that differs from the CSS pixel resolution. (On screens,
CSS pixels have a resolution of 96ppi, but in general the CSS pixel
resolution depends on the reading distance.) If both attributes are
specified, then one of the following statements must be true:
The target ratio is the ratio of the
intrinsic width to the intrinsic height in the resource. The specified width and specified
height are the values of the width and height attributes respectively.
The two attributes must be omitted if the resource in question
does not have both an intrinsic width and an intrinsic height.
Basically, the dimension attributes can't be used to
stretch the image.
To parse the attributes, user agents must use the rules for
parsing dimension values. This will return either an integer
length, a percentage value, or nothing. The user agent requirements
for processing the values obtained from parsing these attributes are
described in the rendering
section. If one of these attributes, when
parsing, returns no value, it must be treated, for the purposes of
those requirements, as if it was not specified.
The width and height DOM attributes on
the iframe, embed, object,
and video elements must reflect the
respective content attributes of the same name.
4.9 Tabular data
4.9.1 Introduction4.9.1 はじめに
This section is non-normative.この節は規定の一部ではありません。
...examples, how to write tables accessibly, a
brief mention of the table model, etc...
4.9.2 The table element4.9.2 table 要素
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- In this order: optionally a
caption element,
followed by either zero or more colgroup elements,
followed optionally by a thead element, followed
optionally by a tfoot element, followed by either zero
or more tbody elements or one or more
tr elements, followed optionally by a
tfoot element (but there can only be one
tfoot element child in total).
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
-
interface HTMLTableElement : HTMLElement {
attribute HTMLTableCaptionElement caption;
HTMLElement createCaption();
void deleteCaption();
attribute HTMLTableSectionElement tHead;
HTMLElement createTHead();
void deleteTHead();
attribute HTMLTableSectionElement tFoot;
HTMLElement createTFoot();
void deleteTFoot();
readonly attribute HTMLCollection tBodies;
HTMLElement createTBody();
readonly attribute HTMLCollection rows;
HTMLElement insertRow(in long index);
void deleteRow(in long index);
};
The table element represents data with more than one
dimension (a table).
we need some editorial text on how layout
tables are bad practice and non-conforming
The children of a table element must be, in
order:
Zero or one caption elements.
Zero or more colgroup elements.
Zero or one thead elements.
Zero or one tfoot elements, if the last element
in the table is not a tfoot element.
Either:
Zero or more tbody elements, or
One or more tr elements. (Only expressible in the XML
serialization.)
Zero or one tfoot element, if there are no
other tfoot elements in the table.
The table element takes part in the table
model.
The caption DOM
attribute must return, on getting, the first caption
element child of the table element, if any, or null
otherwise. On setting, if the new value is a caption
element, the first caption element child of the
table element, if any, must be removed, and the new
value must be inserted as the first node of the table
element. If the new value is not a caption element,
then a HIERARCHY_REQUEST_ERR DOM exception must be
raised instead.
The createCaption()
method must return the first caption element child of
the table element, if any; otherwise a new
caption element must be created, inserted as the first
node of the table element, and then returned.
The deleteCaption()
method must remove the first caption element child of
the table element, if any.
The tHead DOM
attribute must return, on getting, the first thead
element child of the table element, if any, or null
otherwise. On setting, if the new value is a thead
element, the first thead element child of the
table element, if any, must be removed, and the new
value must be inserted immediately before the first element in the
table element that is neither a caption
element nor a colgroup element, if any, or at the end
of the table otherwise. If the new value is not a thead
element, then a HIERARCHY_REQUEST_ERR DOM exception
must be raised instead.
The createTHead()
method must return the first thead element child of the
table element, if any; otherwise a new
thead element must be created and inserted immediately
before the first element in the table element that is
neither a caption element nor a colgroup
element, if any, or at the end of the table otherwise, and then that
new element must be returned.
The deleteTHead()
method must remove the first thead element child of the
table element, if any.
The DOM
attribute must return, on getting, the first tfoot
element child of the table element, if any, or null
otherwise. On setting, if the new value is a tfoot
element, the first tfoot element child of the
table element, if any, must be removed, and the new
value must be inserted immediately before the first element in the
table element that is neither a caption
element, a colgroup element, nor a thead
element, if any, or at the end of the table if there are no such
elements. If the new value is not a tfoot element, then
a HIERARCHY_REQUEST_ERR DOM exception must be raised
instead.
The
method must return the first tfoot element child of the
table element, if any; otherwise a new
tfoot element must be created and inserted immediately
before the first element in the table element that is
neither a caption element, a colgroup
element, nor a thead element, if any, or at the end of
the table if there are no such elements, and then that new element
must be returned.
The
method must remove the first tfoot element child of the
table element, if any.
The tBodies
attribute must return an HTMLCollection rooted at the
table node, whose filter matches only
tbody elements that are children of the
table element.
The createTBody()
method must create a new tbody element, insert it
immediately after the last tbody element in the
table element, if any, or at the end of the
table element if the table element has no
tbody element children, and then must return the new
tbody element.
The rows attribute
must return an HTMLCollection rooted at the
table node, whose filter matches only tr
elements that are either children of the table element,
or children of thead, tbody, or
tfoot elements that are themselves children of the
table element. The elements in the collection must be
ordered such that those elements whose parent is a
thead are included first, in tree order, followed by
those elements whose parent is either a table or
tbody element, again in tree order, followed finally by
those elements whose parent is a tfoot element, still
in tree order.
The behavior of the insertRow(index) method depends on the state of
the table. When it is called, the method must act as required by the
first item in the following list of conditions that describes the
state of the table and the index argument:
- If index is less than −1 or greater than
the number of elements in
rows
collection:
- The method must raise an
INDEX_SIZE_ERR
exception.
- If the
rows collection has
zero elements in it, and the table has no
tbody elements in it:
- The method must create a
tbody element, then
create a tr element, then append the tr
element to the tbody element, then append the
tbody element to the table element, and
finally return the tr element.
- If the
rows collection has
zero elements in it:
- The method must create a
tr element, append it to
the last tbody element in the table, and return the
tr element.
- If index is equal to −1 or equal to the
number of items in
rows
collection:
- The method must create a
tr element, and append it
to the parent of the last tr element in the rows collection. Then, the newly
created tr element must be returned.
- Otherwise:それ以外の場合:
- The method must create a
tr element, insert it
immediately before the indexth tr
element in the rows collection,
in the same parent, and finally must return the newly created
tr element.
When the deleteRow(index) method is called, the user agent
must run the following steps:
If index is equal to −1, then
index must be set to the number if items in the
rows collection, minus
one.
Now, if index is less than zero, or
greater than or equal to the number of elements in the rows collection, the method must
instead raise an INDEX_SIZE_ERR exception, and these
steps must be aborted.
Otherwise, the method must remove the indexth element in the rows collection from its parent.
4.9.3 The caption element4.9.3 caption 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As the first element child of a
table element.
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The caption element represents the title of the
table that is its parent, if it has a parent and that
is a table element.
The caption element takes part in the table
model.
4.9.4 The colgroup element4.9.4 colgroup 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
table element, after any
caption elements and before any thead,
tbody, tfoot, and tr
elements.
- Content model:内容モデル:
- Zero or more
col elements.
- Element-specific attributes:要素固有属性:
span- DOM interface:DOM 界面:
-
interface HTMLTableColElement : HTMLElement {
attribute unsigned long span;
};
The colgroup element represents a group of one or more columns in the table that
is its parent, if it has a parent and that is a table
element.
If the colgroup element contains no col
elements, then the element may have a span content attribute
specified, whose value must be a valid non-negative
integer greater than zero.
The colgroup element and its span attribute take part in the
table model.
The span DOM
attribute must reflect the respective content attribute
of the same name. The value must be limited to only positive
non-zero numbers.
4.9.5 The col element4.9.5 col 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
colgroup element that doesn't have
a span attribute.
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
span- DOM interface:DOM 界面:
-
HTMLTableColElement, same as for
colgroup elements. This interface defines one member,
span.
If a col element has a parent and that is a
colgroup element that itself has a parent that is a
table element, then the col element
represents one or more columns
in the column group
represented by that colgroup.
The element may have a span content attribute
specified, whose value must be a valid non-negative
integer greater than zero.
The col element and its span attribute take part in the
table model.
The span DOM
attribute must reflect the content attribute of the
same name. The value must be limited to only positive non-zero
numbers.
4.9.6 The tbody element4.9.6 tbody 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
table element, after any
caption, colgroup, and
thead elements, but only if there are no
tr elements that are children of the
table element.table element, after any caption, colgroup, and thead elements, but only if there are no tr elements that are children of the table 要素の子供として。
- Content model:内容モデル:
- Zero or more
tr elements零個以上の tr 要素
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
-
interface HTMLTableSectionElement : HTMLElement {
readonly attribute HTMLCollection rows;
HTMLElement insertRow(in long index);
void deleteRow(in long index);
};
The HTMLTableSectionElement interface is also
used for thead and tfoot elements.
The tbody element represents a block of rows that consist of a body of data for
the parent table element, if the tbody
element has a parent and it is a table.
The tbody element takes part in the table
model.
The rows attribute
must return an HTMLCollection rooted at the element,
whose filter matches only tr elements that are children
of the element.
The insertRow(index) method must, when invoked on an
element table section, act as follows:
If index is less than −1 or greater than the
number of elements in the rows
collection, the method must raise an INDEX_SIZE_ERR
exception.
If index is equal to −1 or equal to the
number of items in the rows
collection, the method must create a tr element, append
it to the element table section, and return the
newly created tr element.
Otherwise, the method must create a tr element,
insert it as a child of the table section
element, immediately before the indexth
tr element in the rows collection, and finally must
return the newly created tr element.
The deleteRow(index) method must remove the indexth element in the rows collection from its parent. If
index is less than zero or greater than or equal
to the number of elements in the rows collection, the method must
instead raise an INDEX_SIZE_ERR exception.
4.9.7 The thead element4.9.7 thead 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
table element, after any
caption, and colgroup
elements and before any tbody, tfoot, and
tr elements, but only if there are no other
thead elements that are children of the
table element.table element, after any caption, and colgroup elements and before any tbody, tfoot, and tr elements, but only if there are no other thead elements that are children of the table 要素の子供として。
- Content model:内容モデル:
- Zero or more
tr elements零個以上の tr 要素
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
HTMLTableSectionElement, as defined for
tbody elements.
The thead element represents the block of rows that consist of the column labels
(headers) for the parent table element, if the
thead element has a parent and it is a
table.
The thead element takes part in the table
model.
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
table element, after any
caption, colgroup, and thead
elements and before any tbody and tr
elements, but only if there are no other tfoot
elements that are children of the table element.table element, after any caption, colgroup, and thead elements and before any tbody and tr elements, but only if there are no other tfoot elements that are children of the table 要素の子供として。
- As a child of a
table element, after any
caption, colgroup, thead,
tbody, and tr elements, but only if there
are no other tfoot elements that are children of the
table element.table element, after any caption, colgroup, thead, tbody, and tr elements, but only if there are no other tfoot elements that are children of the table 要素の子供として。
- Content model:内容モデル:
- Zero or more
tr elements零個以上の tr 要素
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
HTMLTableSectionElement, as defined for
tbody elements.
The tfoot element represents the block of rows that consist of the column summaries
(footers) for the parent table element, if the
tfoot element has a parent and it is a
table.
The tfoot element takes part in the table
model.
4.9.9 The tr element4.9.9 tr 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
thead element.thead 要素の子供として。
- As a child of a
tbody element.tbody 要素の子供として。
- As a child of a
tfoot element.tfoot 要素の子供として。
- As a child of a
table element, after any
caption, colgroup, and thead
elements, but only if there are no tbody elements that
are children of the table element.table element, after any caption, colgroup, and thead elements, but only if there are no tbody elements that are children of the table 要素の子供として。
- Content model:内容モデル:
- Zero or more
td or th elements零個以上の td 要素や
th 要素
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
-
interface HTMLTableRowElement : HTMLElement {
readonly attribute long rowIndex;
readonly attribute long sectionRowIndex;
readonly attribute HTMLCollection cells;
HTMLElement insertCell(in long index);
void deleteCell(in long index);
};
The tr element represents a row of cells in a table.
The tr element takes part in the table
model.
The rowIndex
attribute must, if the element has a parent table
element, or a parent tbody, thead, or
tfoot element and a grandparent
table element, return the index of the tr
element in that table element's rows collection. If there is no such
table element, then the attribute must return
−1.
The sectionRowIndex
attribute must, if the element has a parent table,
tbody, thead, or tfoot
element, return the index of the tr element in the
parent element's rows collection (for tables,
that's the rows collection; for
table sections, that's the rows
collection). If there is no such parent element, then the attribute
must return −1.
The cells attribute
must return an HTMLCollection rooted at the
tr element, whose filter matches only td
and th elements that are children of the
tr element.
The insertCell(index) method must act as follows:
If index is less than −1 or greater than the
number of elements in the cells
collection, the method must raise an INDEX_SIZE_ERR
exception.
If index is equal to −1 or equal to the
number of items in cells
collection, the method must create a td element, append
it to the tr element, and return the newly created
td element.
Otherwise, the method must create a td element,
insert it as a child of the tr element, immediately
before the indexth td or
th element in the cells collection, and finally must
return the newly created td element.
The deleteCell(index) method must remove the indexth element in the cells collection from its parent. If
index is less than zero or greater than or equal
to the number of elements in the cells collection, the method must
instead raise an INDEX_SIZE_ERR exception.
4.9.10 The td element4.9.10 td 要素
- Categories分類
- Sectioning root.章節付け根。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
tr element.tr 要素の子供として。
- Content model:内容モデル:
- Flow content.流れ内容。
- Element-specific attributes:要素固有属性:
colspanrowspanheaders- DOM interface:DOM 界面:
-
interface HTMLTableDataCellElement : HTMLTableCellElement {
attribute DOMString headers;
};
The td element represents a data cell in a table.
The td element may have a content attribute
specified. The headers
attribute, if specified, must contain a string consisting of an
unordered set of unique space-separated tokens, each of
which must have the value of an ID of a th element
taking part in the same table as
the td element (as defined by the table
model).
The exact effect of the attribute is described in detail in the
algorithm for assigning header cells to data cells,
which user agents must apply to determine the relationships between
data cells and header cells.
The td element and its colspan and rowspan attributes take part in the
table model.
The DOM
attribute must reflect the content attribute of the
same name.
4.9.11 The th element4.9.11 th 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
tr element.tr 要素の子供として。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
colspanrowspanscope- DOM interface:DOM 界面:
-
interface : HTMLTableCellElement {
attribute DOMString scope;
};
The th element represents a header cell in a table.
The th element may have a scope content attribute
specified. The scope attribute is
an enumerated attribute with five states, four of which
have explicit keywords:
- The
row
keyword, which maps to the row state
- The row state means the header cell applies to all the
remaining cells in the row.
- The
col
keyword, which maps to the column state
- The column state means the header cell applies to all
the remaining cells in the column.
- The
rowgroup keyword,
which maps to the row group state
- The row group state means the header cell applies to
all the remaining cells in the row group.
- The
colgroup keyword,
which maps to the column group state
- The column group state means the header cell applies
to all the remaining cells in the column group.
- The auto state
- The auto state makes the header cell apply to a set of
cells selected based on context.
The scope attribute's
missing value default is the auto state.
The exact effect of these values is described in detail in the
algorithm for assigning header cells to data cells,
which user agents must apply to determine the relationships between
data cells and header cells.
The th element and its colspan and rowspan attributes take part in the
table model.
The scope DOM
attribute must reflect the content attribute of the
same name.
4.9.12 Attributes common to td and th elements
The td and th elements may have a colspan content
attribute specified, whose value must be a valid non-negative
integer greater than zero.
The td and th elements may also have a
rowspan content
attribute specified, whose value must be a valid non-negative
integer.
The td and th elements implement
interfaces that inherit from the HTMLTableCellElement
interface:
interface HTMLTableCellElement : HTMLElement {
attribute long colSpan;
attribute long rowSpan;
readonly attribute long cellIndex;
};
The colSpan DOM
attribute must reflect the content attribute of the
same name. The value must be limited to only positive non-zero
numbers.
The rowSpan DOM
attribute must reflect the content attribute of the
same name. Its default value, which must be used if parsing the
attribute as a non-negative integer returns an error, is also
1.
The cellIndex
DOM attribute must, if the element has a parent tr
element, return the index of the cell's element in the parent
element's cells collection. If
there is no such parent element, then the attribute must return
0.
4.9.13 Processing model4.9.13 処理モデル
The various table elements and their content attributes together
define the table model.
A table consists of cells
aligned on a two-dimensional grid of slots with coordinates (x, y). The grid is finite, and is
either empty or has one or more slots. If the grid has one or more
slots, then the x coordinates are always in the
range 0 ≤ x < xwidth, and the y
coordinates are always in the range 0 ≤ y < yheight. If one or both of xwidth and yheight are zero, then the table is empty (has
no slots). Tables correspond to table elements.
A cell is a set of slots anchored
at a slot (cellx, celly), and with a particular
width and height such that
the cell covers all the slots with coordinates (x, y) where cellx ≤ x < cellx+width and
celly ≤ y < celly+height. Cells can
either be data cells or header cells. Data cells
correspond to td elements, and have zero or more
associated header cells. Header cells correspond to th
elements.
A row is a complete set of slots
from x=0 to x=xwidth-1, for a particular value of y. Rows correspond to tr elements.
A column is a complete set of
slots from y=0 to y=yheight-1, for a particular value of x. Columns can correspond to col
elements, but in the absence of col elements are
implied.
A row group is a set of
rows anchored at a slot (0, groupy) with a particular height such that the row group covers all the slots
with coordinates (x, y)
where 0 ≤ x < xwidth and groupy ≤ y < groupy+height. Row groups
correspond to tbody, thead, and
tfoot elements. Not every row is necessarily in a row
group.
A column group is a set
of columns anchored at a slot
(groupx, 0) with a
particular width such that the column group
covers all the slots with coordinates (x, y) where groupx ≤ x < groupx+width and
0 ≤ y < yheight. Column groups
correspond to colgroup elements. Not every column is
necessarily in a column group.
Row groups cannot overlap
each other. Similarly, column
groups cannot overlap each other.
A cell cannot cover slots that
are from two or more row
groups. It is, however, possible for a cell to be in multiple
column groups. All the
slots that form part of one cell are part of zero or one row groups and zero or more column groups.
In addition to cells, columns, rows, row
groups, and column
groups, tables can have a
caption element associated with them. This gives the
table a heading, or legend.
A table model error is an error with the data
represented by table elements and their
descendants. Documents must not have table model errors.
To determine which elements correspond to which slots in a table associated with a
table element, to determine the dimensions of the table
(xwidth and yheight), and to determine if
there are any table model
errors, user agents must use the following algorithm:
-
Let xwidth be zero.
-
Let yheight be zero.
-
Let pending tfoot elements be
a list of tfoot elements, initially empty.
-
Let the table be the table represented by the
table element. The xwidth and yheight variables give the
table's dimensions. The table is
initially empty.
-
If the table element has no children elements,
then return the table (which will be empty),
and abort these steps.
-
Associate the first caption element child of the
table element with the table. If
there are no such children, then it has no associated
caption element.
-
Let the current element be the first
element child of the table element.
If a step in this algorithm ever requires the current element to be advanced to the next child of the
table when there is no such next child, then
the user agent must jump to the step labeled end, near the
end of this algorithm.
-
While the current element is not one of the
following elements, advance the current element to the next child of the
table:
-
If the current element is a
colgroup, follow these substeps:
-
Column groups: Process the current
element according to the appropriate case below:
- If the current element has any
col element children
-
Follow these steps:次の段階群に従います。
-
Let xstart have
the value of xwidth.
-
Let the current column be the first
col element child of the colgroup
element.
-
Columns: If the current column
col element has a span attribute, then parse its
value using the rules for parsing non-negative
integers.
If the result of parsing the value is not an error or
zero, then let span be that value.
Otherwise, if the col element has no span attribute, or if trying to
parse the attribute's value resulted in an error, then let
span be 1.
-
Increase xwidth by
span.
-
Let the last span columns in the
table correspond to the current
column col element.
-
If current column is not the last
col element child of the colgroup
element, then let the current column be
the next col element child of the
colgroup element, and return to the step
labeled columns.
-
Let all the last columns in the
table from x=xstart to x=xwidth-1 form a
new column group,
anchored at the slot (xstart, 0), with width xwidth-xstart,
corresponding to the colgroup element.
- If the current element has no
col element children
-
-
If the colgroup element has a span attribute, then parse
its value using the rules for parsing non-negative
integers.
If the result of parsing the value is not an error or
zero, then let span be that value.
Otherwise, if the colgroup element has no
span attribute, or if
trying to parse the attribute's value resulted in an error,
then let span be 1.
-
Increase xwidth by
span.
-
Let the last span columns in the
table form a new column group, anchored
at the slot (xwidth-span,
0), with width span, corresponding to
the colgroup element.
-
Advance the current element to the next child of the
table.
-
While the current element is not one of
the following elements, advance the current element to the next child of the
table:
-
If the current element is a
colgroup element, jump to the step labeled
column groups above.
-
Let ycurrent be
zero.
-
Let the list of downward-growing cells be
an empty list.
-
Rows: While the current element is
not one of the following elements, advance the current element to the next child of the
table:
-
If the current element is a
tr, then run the algorithm for processing
rows, advance
the current element to the next child of the
table, and return to the step labeled
rows.
-
Run the algorithm for ending a row group.
-
If the current element is a
tfoot, then add that element to the list of pending tfoot elements, advance the current element to the next child of the
table, and return to the step labeled
rows.
-
The current element is either a
thead or a tbody.
Run the algorithm for processing row groups.
-
Advance the current element to the next child of the
table.
-
Return to the step labeled rows.
-
End: For each tfoot element in the list of
pending tfoot elements, in tree
order, run the algorithm for processing row
groups.
-
If there exists a row or column in the table the table
containing only slots that do
not have a cell anchored to
them, then this is a table model error.
-
Return the table.the table を返します。
The algorithm for processing row groups, which is
invoked by the set of steps above for processing
thead, tbody, and tfoot
elements, is:
-
Let ystart have the
value of yheight.
-
For each tr element that is a child of the element
being processed, in tree order, run the algorithm for
processing rows.
-
If yheight > ystart, then let all the last rows in the table
from y=ystart
to y=yheight-1 form a new row group, anchored at the slot
with coordinate (0, ystart), with height yheight-ystart, corresponding to the element
being processed.
-
Run the algorithm for ending a row group.
The algorithm for ending a row group, which is invoked
by the set of steps above when starting and ending a block of rows,
is:
-
While ycurrent is less
than yheight, follow these
steps:
-
Run the algorithm for growing downward-growing
cells.
-
Increase ycurrent by
1.
-
Empty the list of downward-growing
cells.
The algorithm for processing rows, which is invoked by
the set of steps above for processing tr elements,
is:
-
If yheight is equal to
ycurrent, then increase
yheight by 1. (ycurrent is never
greater than yheight.)
-
Let xcurrent be 0.
-
Run the algorithm for growing downward-growing
cells.
-
If the tr element being processed has no
td or th element children, then increase
ycurrent by 1, abort this
set of steps, and return to the algorithm above.
-
Let current cell be the first
td or th element in the tr
element being processed.
-
Cells: While xcurrent is less than xwidth and the slot with coordinate (xcurrent, ycurrent) already has a cell assigned to it,
increase xcurrent by
1.
-
If xcurrent is equal to
xwidth, increase xwidth by 1. (xcurrent is never
greater than xwidth.)
-
If the current cell has a colspan attribute, then parse that
attribute's value, and let colspan be
the result.
If parsing that value failed, or returned zero, or if the
attribute is absent, then let colspan be 1,
instead.
-
If the current cell has a rowspan attribute, then parse that attribute's
value, and let rowspan be the
result.
If parsing that value failed or if the attribute is absent,
then let rowspan be 1, instead.
-
If rowspan is zero, then let cell grows downward be true, and set rowspan to 1. Otherwise, let cell
grows downward be false.
-
If xwidth < xcurrent+colspan,
then let xwidth be
xcurrent+colspan.
-
If yheight < ycurrent+rowspan,
then let yheight be
ycurrent+rowspan.
-
Let the slots with coordinates (x, y) such that xcurrent ≤ x < xcurrent+colspan
and ycurrent ≤ y < ycurrent+rowspan be
covered by a new cell c, anchored at (xcurrent, ycurrent), which has width colspan and height rowspan,
corresponding to the current cell element.
If the current cell element is a
th element, let this new cell c
be a header cell; otherwise, let it be a data cell. To establish
what header cells apply to a data cell, use the algorithm
for assigning header cells to data cells described in the
next section.
If any of the slots involved already had a cell covering them, then this is a
table model error. Those slots now have two cells
overlapping.
-
If cell grows downward is true, then add
the tuple {c, xcurrent, colspan} to the
list of downward-growing cells.
-
Increase xcurrent by
colspan.
-
If current cell is the last td
or th element in the tr element being
processed, then increase ycurrent by 1, abort this set of steps, and
return to the algorithm above.
-
Let current cell be the next
td or th element in the tr
element being processed.
-
Return to the step labelled cells.
When the algorithms above require the user agent to run the
algorithm for growing downward-growing cells, the user
agent must, for each {cell, cellx, width}
tuple in the list of downward-growing cells, if
any, extend the cell cell so that it also covers the slots with
coordinates (x, ycurrent), where cellx ≤ x < cellx+width.
4.9.13.2 Forming relationships between data cells and header cells
Each data cell can be assigned zero or more header cells. The
is as
follows.
-
For each header cell in the table, in tree order,
run these substeps:
-
Let (headerx, headery) be the coordinate of
the slot to which the header cell is anchored.
-
Let headerwidth be
the width of the header cell.
-
Let headerheight be
the height of the header cell.
-
Let data cells be a list of data cells,
initially empty.
-
Examine the scope
attribute of the th element corresponding to the
header cell, and, based on its state, apply the appropriate
substep:
- If it is in the row state
-
Add all the data cells that cover slots with coordinates
(slotx, sloty), where headerx+headerwidth ≤ slotx < xwidth and
headery ≤ sloty < headery+headerheight, to the data
cells list.
- If it is in the column state
-
Add all the data cells that cover slots with coordinates
(slotx, sloty), where headerx ≤ slotx < headerx+headerwidth and
headery+headerheight ≤ sloty < yheight, to the data cells list.
- If it is in the row group state
-
If the header cell is not in a row group, then do
nothing.
Otherwise, let (0, groupy) be the slot at which the row group is
anchored, let height be the number of rows
in the row group, and add all the data cells that cover slots
with coordinates (slotx, sloty), where headerx ≤ slotx < xwidth and headery ≤ sloty < groupy+height, to the data
cells list.
- If it is in the column group state
-
If the header cell is not anchored in a column group, then do
nothing.
Otherwise, let (groupx, 0) be the slot at which that column
group is anchored, let width be the number
of columns in the column group, and add all the data cells
that cover slots with coordinates (slotx, sloty), where headerx ≤ slotx < groupx+width and
headery ≤ sloty < yheight, to the data
cells list.
- Otherwise, it is in the auto state
-
Run these steps:
-
If the header cell is equivalent to a wide
cell, let headerwidth equal xwidth-headerx.
-
Let x equal headerx+headerwidth.
-
Let y equal headery+headerheight.
-
Horizontal: If x is equal to
xwidth, then jump
down to the step below labeled vertical.
-
If there is a header cell anchored at (x, headery) with height headerheight, then jump down to the step
below labeled vertical.
-
Add all the data cells that cover slots with coordinates
(slotx, sloty), where slotx = x and headery ≤ sloty < headery+headerheight, to
the data cells list.
-
Increase x by 1.
-
Jump up to the step above labeled horizontal.
-
Vertical: If y is equal to
yheight, then jump
to the step below labeled end.
-
If there is a header cell cell
anchored at (headerx, y), then follow
these substeps:
-
If the header cell cell is
equivalent to a wide cell, then let width be xwidth-headerx. Otherwise, let width be the width of the header cell cell.
-
If width is equal to headerwidth, then jump
to the step below labeled end.
-
Add all the data cells that cover slots with coordinates
(slotx, sloty), where headerx ≤ slotx < headerx+headerwidth and
sloty = y, to the data
cells list.
-
Increase y by 1.
-
Jump up to the step above labeled vertical.
-
End: Coalesce all the duplicate entries in the
data cells list, so that each data cell
is only present once, in tree order.
-
Assign the header cell to all the data cells in the data cells list that correspond to
td elements that do not have a headers attribute specified.
-
For each data cell in the table, in tree order,
run these substeps:
-
If the data cell corresponds to a td element
that does not have a headers attribute specified, then
skip these substeps and move on to the next data cell (if
any).
-
Otherwise, take the value of the headers attribute and split it on spaces,
letting id list be the list of tokens
obtained.
-
For each token in the id list, run the
following steps:
Let id be the token.
If there is a header cell in the table whose corresponding
th element has an ID that is equal to the value of
id, then assign the first such header cell
in tree order to the data cell.
A header cell anchored at (headerx, headery) with width headerwidth and height headerheight is said to be equivalent to a wide
cell if all the slots with coordinates (slotx, sloty), where headerx+headerwidth ≤ slotx < xwidth and headery ≤ sloty < headery+headerheight, are all either empty or covered
by empty data cells.
A data cell is said to be an empty data cell if it
contains no elements and its text content, if any, consists only of
White_Space characters.
User agents may remove empty data
cells when analyzing data in a table.
Forms allow unscripted client-server interaction: given a form, a
user can provide data, submit it to the server, and have the server
act on it accordingly (e.g. returning the results of a search or
calculation). The elements used in forms can also be used for user
interaction with no associated submission mechanism, in conjunction
with scripts.
Mostly for historical reasons, elements in this section fall into
several overlapping (but subtly different) categories in addition to
the usual ones like flow content, phrasing
content, and interactive content.
A number of the elements are form-associated elements, which means they can have a
form owner and, to expose this, have a form content attribute with a matching
form DOM attribute.
The form-associated
elements fall into several subcategories:
- Submittable elements
- Denotes elements that can be used for constructing the form data
set when a
form element is submitted.
- Resettable elements
- Denotes elements that can be affected when a
form
element is reset.
- Listed
- Denotes elements that are listed in the
form.elements
and fieldset.elements APIs.
- Labelable
- Denotes elements that can be associated with
label
elements.
In addition, some submittable
elements can be, depending on their attributes, buttons. The prose below defines when
an element is a button. Some buttons are specifically submit buttons.
The object element is also a
form-associated element and can, with the use of a
suitable plugin, partake in form submission.
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Flow content, but with no
form element descendants.
- Element-specific attributes:要素固有属性:
accept-charsetactionenctypemethodnamenovalidatetarget- DOM interface:DOM 界面:
-
interface HTMLFormElement : HTMLElement {
attribute DOMString accept-charset;
attribute DOMString action;
attribute DOMString enctype;
attribute DOMString method;
attribute DOMString name;
attribute boolean novalidate;
attribute DOMString target;
readonly attribute HTMLFormControlsCollection elements;
readonly attribute long length;
[IndexGetter] HTMLElement XXX7(in unsigned long index);
[NameGetter] Object XXX8(in DOMString name);
void submit();
void reset();
boolean checkValidity();
void dispatchFormInput();
void dispatchFormChange();
};
The form element represents a collection of form-associated elements,
some of which can represent editable values that can be submitted to
a server for processing.
The accept-charset
attribute gives the character encodings that are to be used for the
submission. If specified, the value must be an ordered set of
unique space-separated tokens, and each token must be the
preferred name of an ASCII-compatible character
encoding. [IANACHARSET]
The name attribute
represents the form's name within the forms collection. The value must not be the
empty string, and the value must be unique amongst the
form elements in the forms collection that it is in, if any.
The action, enctype, method, novalidate, and target attributes are attributes
for form submission.
The accept-charset
and name DOM
attributes must reflect the respective content
attributes of the same name.
The elements
DOM attribute must return an HTMLFormControlsCollection
rooted at the Document node, whose filter matches listed elements whose form
owner is the form element, with the exception of
input elements whose type attribute is in the Image Button state, which must,
for historical reasons, be excluded from this particular
collection.
The length DOM
attribute must return the number of nodes represented by the elements collection.
The XXX7() method
must return the value that would be returned by the item() method of
the elements collection if it
was invoked with the same arguments.
The XXX8() method
must return the value that would be returned by the namedItem()
method of the elements
collection if it was invoked with the same arguments.
The submit()
method, when invoked, must submit the form
element from the form element itself.
The reset()
method, when invoked, must reset the form
element.
If the checkValidity()
method is invoked, the user agent must statically validate the
constraints of the form element, and return true
if the constraint validation return a positive result, and
false if it returned a negative result.
If the dispatchFormInput()
method is invoked, the user agent must broadcast forminput events from the
form element.
If the dispatchFormChange()
method is invoked, the user agent must broadcast formchange events from the
form element.
4.10.2 The fieldset element4.10.2 fieldset 要素
- Categories分類
- Flow content.流れ内容。
- Listed form-associated element.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- One
legend element follwed by flow content.
- Element-specific attributes:要素固有属性:
disabledformname- DOM interface:DOM 界面:
-
interface HTMLFieldSetElement : HTMLElement {
attribute boolean disabled;
readonly attribute HTMLFormElement form;
attribute DOMString name;
readonly attribute DOMString type;
readonly attribute HTMLFormControlsCollection elements;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
void setCustomValidity(in DOMString error);
};
The fieldset element represents a set of form
controls grouped under a common name.
The name of the group is given by the first legend
element that is a child of the fieldset element. The
remainder of the descendants form the group.
The disabled
attribute, when specified, causes all the form control descendants
of the fieldset element to be disabled.
The form attribute is used to
explicitly associate the fieldset element with its
form owner. The name
attribute represents the element's name.
The disabled DOM
attribute must reflect the content attribute of the
same name.
The type DOM
attribute must return the string "fieldset".
The elements DOM
attribute must return an HTMLFormControlsCollection
rooted at the fieldset element, whose filter matches
listed elements.
The willValidate,
validity, and validationMessage
attributes, and the checkValidity() and
setCustomValidity()
methods, are part of the constraint validation API.
Constraint validation: fieldset
elements are always barred from constraint
validation.
4.10.3 The label element4.10.3 label 要素
- Categories分類
- Phrasing content.語句付け内容。
- Interactive content.対話的内容。
- Form-associated element.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- If the element has a
for attribute: Phrasing content, but with no descendant labelable form-associated elements or label elements.
- Otherwise: Phrasing content, but with at most one descendant labelable form-associated element, and with no descendant
label elements.
- Element-specific attributes:要素固有属性:
formfor- DOM interface:DOM 界面:
-
interface HTMLLabelElement : HTMLElement {
readonly attribute HTMLFormElement form;
attribute DOMString htmlFor;
readonly attribute HTMLElement control;
};
The label represents a caption in a user
interface. The caption can be associated with a specific form
control, known as the label element's labeled
control.
Unless otherwise specified by the following rules, a
label element has no labeled control.
The for attribute
may be specified to indicate a form control with which the caption
is to be associated. If the attribute is specified, the attribute's
value must be the ID of a labelable
form-associated element in the same Document as
the label element. If the attribute is specified and
there is an element in the Document whose ID is equal
to the value of the for
attribute, and the first such element is a labelable form-associated element,
then that element is the label element's labeled
control.
If the for attribute is not
specified, but the label element has a labelable
form-associated element descendant, then the first such
descendant in tree order is the label
element's labeled control.
The label element's exact default presentation and
behavior, in particular what its activation behavior
might be, if anything, should match the platform's label
behavior.
For example, on platforms where clicking a checkbox label checks
the checkbox, clicking the label in the following
snippet could trigger the user agent to run synthetic click
activation steps on the input element, as if
the element itself had been triggered by the user:
<label><input type=checkbox name=lost> Lost</label>
On other platforms, the behavior might be just to focus the
control, or do nothing.
The form attribute is used to
explicitly associate the label element with its
form owner.
The htmlFor DOM
attribute must reflect the for content attribute.htmlFor DOM 属性は for 内容属性を反映しなければなりません。
The control DOM
attribute must return the label element's labeled
control, if any, or null if there isn't one.control DOM
属性は、当該 label
要素の名札付き制御子があればそれを、
なければ null を返さなければなりません。
Labelable form-associated
elements have a NodeList object associated with
them that represents the list of label elements, in
tree order, whose labeled control is the
element in question. The labels DOM attribute of
labelable form-associated
elements, on getting, must return that NodeList
object.
- Categories分類
- Phrasing content.語句付け内容。
- If the
type attribute is not in the Hidden state: Interactive content.
- Listed, labelable, submittable, and resettable form-associated element.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
acceptactionaltautocompleteautofocuscheckeddisabledenctypeformlistmaxmaxlengthmethodminmultiplenamenovalidatepatternplaceholderreadonlyrequiredsizesrcsteptargettypevalue- DOM interface:DOM 界面:
-
interface HTMLInputElement : HTMLElement {
attribute DOMString accept;
attribute DOMString action;
attribute DOMString alt;
attribute boolean autocomplete;
attribute boolean autofocus;
attribute boolean defaultChecked;
attribute boolean checked;
attribute boolean disabled;
attribute DOMString enctype;
readonly attribute HTMLFormElement form;
readonly attribute HTMLElement list;
attribute DOMString max;
attribute long maxLength;
attribute DOMString method;
attribute DOMString min;
attribute boolean multiple;
attribute DOMString name;
attribute boolean noValidate;
attribute DOMString pattern;
attribute DOMString placeholder;
attribute boolean readOnly;
attribute boolean required;
attribute unsigned long size;
attribute DOMString src;
attribute DOMString step;
attribute DOMString target;
attribute DOMString type;
attribute DOMString defaultValue;
attribute DOMString value;
attribute DOMTimeStamp valueAsDate;
attribute float valueAsNumber;
readonly attribute HTMLOptionElement selectedOption;
void stepUp(in long n);
void stepDown(in long n);
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
void setCustomValidity(in DOMString error);
readonly attribute NodeList labels;
};
The input element represents a typed data field,
usually with a form control to allow the user to edit the data.
The type
attribute controls the data type (and associated control) of the
element. It is an enumerated attribute. The following
table lists the keywords and states for the attribute — the
keywords in the left column map to the states in the cell in the
second column on the same row as the keyword.
| Keyword
キーワード | State
状態 | Data type
データ型 | Control type
制御子型 |
|---|
hidden
| Hidden
隠れ
| An arbitrary string
任意の文字列 | n/a
N/A |
text
| Text
| Text with no line breaks
改行無しのテキスト | Text field
テキスト欄 |
search
| Search
| Text with no line breaks
改行無しのテキスト | Search field
|
url
| URL
| An IRI
IRI | A text field
テキスト欄
|
email
| E-mail
電子メイル
| An e-mail address or list of e-mail addresses
| A text field
テキスト欄
|
password
| Password
| Text with no line breaks (sensitive information)
| Text field that obscures data entry
|
datetime
| Date and Time
| A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC
| A date and time control
|
date
| Date
| A date (year, month, day) with no time zone
| A date control
|
month
| Month
| A date consisting of a year and a month with no time zone
| A month control
|
week
| Week
| A date consisting of a week-year number and a week number with no time zone
| A week control
|
time
| Time
| A time (hour, minute, seconds, fractional seconds) with no time zone
| A time control
|
datetime-local
| Local Date and Time
| A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone
| A date and time control
|
number
| Number
| A numerical value
数値 | A text field or spinner control
|
range
| Range
| A numerical value, with the extra semantic that the exact value is not important
| A slider control or similar
|
color
| Color
| An sRGB color with 8-bit red, green, and blue components
| A color well
|
checkbox
| Checkbox
| A set of zero or more values from a predefined list
| A checkbox
|
radio
| Radio Button
| An enumerated value
| A radio button
|
file
| File Upload
| Zero or more files each with a MIME type and optionally a file name
| A label and a button
|
submit
| Submit Button
| An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission
| A button
ボタン |
image
| Image Button
| A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission
| Either a clickable image, or a button
|
reset
| Reset Button
| n/a
N/A | A button
ボタン |
button
| Button
| n/a
N/A | A button
ボタン |
The missing value default is the Text state.
Which of the accept, action, alt, autocomplete, checked, enctype, and list, max, maxlength, method, min, multiple, novalidate, pattern, readonly, required, size, src, step, and target attributes apply to an
input element depends on the state of its type attribute. Similarly, the checked, valueAsDate, valueAsNumber, list, and selectedOption DOM
attributes, and the stepUp()
and stepDown() methods, are
specific to certain states. The following table is non-normative and
summarises which content attributes, DOM attrbutes, and methods
apply to each state:
When an input element's type attribute changes state, and
when the element is first created, the element's rendering and
behaviour must change to the new state's accordingly and the
value sanitization algorithm, if one is defined for the
type attribute's new state,
must be invoked.
Each input element has a value, which is exposed by the value DOM attribute. Some states
define an algorithm
to convert a string to a number, an algorithm to convert a
number to a string, an algorithm to convert a
string to a Date object, and an algorithm to convert a
Date object to a string, which are used by
max,
min,
step,
valueAsDate,
valueAsNumber,
stepDown(), and
stepUp().
Each input element has a boolean dirty value flag. When
it is true, the element is said to have a dirty value. The
dirty value flag
must be initially set to false when the element is created, and must
be set to true whenever the user interacts with the control in a way
that changes the value.
The value
content attribute gives the default value of the input
element. When the value
content attribute is added, set, or removed, if the control does not
have a dirty value, the
user agent must set the value
of the element to the value of the value content attribute, if there is
one, or the empty string otherwise, and then run the current
value sanitization algorithm, if one is defined.
Each input element has a checkedness, which is exposed by
the checked DOM
attribute.
Each input element has a boolean dirty checkedness
flag. When it is true, the element is said to have a dirty
checkedness. The dirty checkedness
flag must be initially set to false when the element is
created, and must be set to true whenever the user interacts with
the control in a way that changes the checkedness.
The checked
content attribute gives the default checkedness of the
input element. When the checked content attribute is
added, if the control does not have dirty checkedness, the user
agent must set the checkedness of the element to
true; when the checked
content attribute is removed, if the control does not have dirty checkedness, the user
agent must set the checkedness of the element to
false.
The reset
algorithm for input elements is to set the dirty value flag and
dirty checkedness
flag back to false, set the value of the element to the value of
the value content attribute,
if there is one, or the empty string otherwise, set the checkedness of the element to true
if the element has a checked
content attribute and false if it does not, and then invoke the
value sanitization algorithm, if the type attribute's current state
defines one.
Each input element has a boolean mutability flag. When it is
true, the element is said to be mutable, and when it is
false the element is immutable. Unless
otherwise specified, an input element is always mutable. Unless otherwise
specified, the user agent should not allow the user to modify the
element's value or checkedness.
When an input element is disabled, it is immutable.
When an input element does not have a
Document node as one of its ancestors (i.e. when it is
not in the document), it is immutable.
The readonly attribute can also in
some cases make an input element immutable.
The form attribute is used to
explicitly associate the input element with its
form owner. The name
attribute represents the element's name. The disabled attribute is used to make
the control non-interactive and to prevent its value from being
submitted. The autofocus
attribute controls focus.
The accept, alt, autocomplete, max, min, multiple, pattern, placeholder, required, size, src, step, and type DOM attributes must
reflect the respective content attributes of the same
name. The maxLength DOM
attribute must reflect the maxlength content attribute. The
readOnly DOM
attribute must reflect the readonly content attribute. The
defaultChecked
DOM attribute must reflect the checked content attribute. The
defaultValue
DOM attribute must reflect the value content attribute.accept, alt, autocomplete, max, min, multiple, pattern, placeholder, required, size, src, step, and type DOM attributes must reflect the respective content attributes of the same name. The maxLength DOM attribute must reflect the maxlength content attribute. The readOnly DOM attribute must reflect the readonly content attribute. The defaultChecked DOM attribute must reflect the checked content attribute. The defaultValue DOM 属性は value 内容属性を反映しなければなりません。
The willValidate, validity, and validationMessage
attributes, and the checkValidity() and setCustomValidity()
methods, are part of the constraint validation API. The
labels attribute provides a list
of the element's labels.
4.10.4.1 States of the type attribute
4.10.4.1.1 Hidden state
When an input element's type attribute is in the Hidden state, the rules in
this section apply.
The input element represents a value that is not
intended to be examined or manipulated by the user.
Constraint validation: If an input
element's type attribute is in
the Hidden state, it is
barred from constraint validation.
If the name attribute is
present and has a value that is a case-sensitive match
for the string "_charset_", then the element's
value attribute must be
omitted.
The
value
DOM attribute applies to this element and is
in mode value.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
autocomplete,
checked,
enctype,
list,
max,
maxlength,
method,
min,
multiple,
novalidate,
pattern,
placeholder,
readonly,
required,
size,
src,
step, and
target.
The following DOM attributes and methods do not apply to the
element:
checked,
list,
selectedOption,
valueAsDate, and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
The input and change events do not apply.
4.10.4.1.2 Text state and Search state
When an input element's type attribute is in the Text state or the Search state, the rules in
this section apply.
The input element represents a one line plain text
edit control for the element's value.
If the element is mutable,
its value should be editable
by the user. User agents must not allow users to insert U+000A LINE
FEED (LF) or U+000D CARRIAGE RETURN (CR) characters into the
element's value.
The value attribute, if
specified, must have a value that contains no U+000A LINE FEED (LF)
or U+000D CARRIAGE RETURN (CR) characters.
The value sanitization algorithm is as
follows: Strip line breaks from the value.
The following common input element content
attributes and DOM attributes apply to the element:
autocomplete,
list,
maxlength,
pattern,
placeholder,
readonly,
required, and
size content attributes;
list,
selectedOption, and
value DOM attributes.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
max,
method,
min,
multiple,
novalidate,
src,
step, and
target.
The following DOM attributes and methods do not apply to the
element:
checked,
valueAsDate, and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
4.10.4.1.3 URL state
When an input element's type attribute is in the URL state, the rules in this
section apply.
The input element represents a control for editing a
single URL given in the element's value.
If the is mutable, the user
agent should allow the user to change the URL represented by its
value. User agents may allow
the user to set the value to a
string that is not a valid URL, but may also or instead
automatically escape characters entered by the user so that the
value is always a valid
URL (even if that isn't the actual value seen and edited by
the user in the interface). User agents should allow the user to set
the value to the empty
string. User agents must not allow users to insert U+000A LINE FEED
(LF) or U+000D CARRIAGE RETURN (CR) characters into the value.
The value attribute, if
specified, must have a value that is a valid URL.
The value sanitization algorithm is as
follows: Strip line breaks from the value.
Constraint validation: While the value of the element is not a
valid URL, the element is suffering from a type
mismatch.
The following common input element content
attributes and DOM attributes apply to the element:
autocomplete,
list,
maxlength,
pattern,
placeholder,
readonly,
required, and
size content attributes;
list,
selectedOption, and
value DOM attributes.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
max,
method,
min,
multiple,
novalidate,
src,
step, and
target.
The following DOM attributes and methods do not apply to the
element:
checked,
valueAsDate, and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
4.10.4.1.4 E-mail state
When an input element's type attribute is in the E-mail state, the rules in this
section apply.
The input element represents a control for editing a
list of e-mail addresses given in the element's value.
If the element is mutable,
the user agent should allow the user to change the e-mail addresses
represented by its value. If
the multiple attribute is
specified, then the user agent should allow the user to select or
provide multiple addresses; otherwise, the user agent should act in
a manner consistent with expecting the user to provide a single
e-mail address. User agents may allow the user to set the value to a string that is not an
valid e-mail address list. User agents should allow the
user to set the value to the
empty string. User agents must not allow users to insert U+000A LINE
FEED (LF) or U+000D CARRIAGE RETURN (CR) characters into the value. User agents may transform the
value for display and editing
(e.g. converting punycode in the value to IDN in the display and vice
versa).
If the multiple
attribute is specified on the element, then the value attribute, if specified, must
have a value that is a valid e-mail address list;
otherwise, the value
attribute, if specified, must have a value that is a single
valid e-mail address.
The value sanitization algorithm is as
follows: Strip line breaks from the value.
Constraint validation: If the multiple attribute is specified
on the element, then, while the value of the element is not a
valid e-mail address list, the element is
suffering from a type mismatch; otherwise, while the
value of the element is not a
single valid e-mail address, the element is
suffering from a type mismatch.
A valid e-mail address list is a set of
comma-separated tokens, where each token is itself a
valid e-mail address, possibly with one or more leading
or trailing space
characters.
A valid e-mail address is a string that matches the
production dot-atom "@" dot-atom
where dot-atom is defined in RFC 2822 section
3.2.4, excluding the CFWS production everywhere. [RFC2822]
The following common input element content
attributes and DOM attributes apply to the element:
autocomplete,
list,
maxlength,
multiple,
pattern,
placeholder,
readonly,
required, and
size content attributes;
list,
selectedOption, and
value DOM attributes.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
max,
method,
min,
novalidate,
src,
step, and
target.
The following DOM attributes and methods do not apply to the
element:
checked,
valueAsDate, and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
4.10.4.1.5 Password state
When an input element's type attribute is in the Password state, the rules in
this section apply.
The input element represents a one line plain text
edit control for the element's value. The user agent should obscure
the value so that people other than the user cannot see it.
If the element is mutable,
its value should be editable
by the user. User agents must not allow users to insert U+000A LINE
FEED (LF) or U+000D CARRIAGE RETURN (CR) characters into the value.
The value attribute, if
specified, must have a value that contains no U+000A LINE FEED (LF)
or U+000D CARRIAGE RETURN (CR) characters.
The value sanitization algorithm is as
follows: Strip line breaks from the value.
The following common input element content
attributes and DOM attributes apply to the element:
autocomplete,
maxlength,
pattern,
placeholder,
readonly,
required, and
size content attributes;
value DOM attribute.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
list,
max,
method,
min,
multiple,
novalidate,
src,
step, and
target.
The following DOM attributes and methods do not apply to the
element:
checked,
list,
selectedOption,
valueAsDate, and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
4.10.4.1.6 Date and Time state
When an input element's type attribute is in the Date and Time state, the
rules in this section apply.
The input element represents a control for setting
the element's value to a
string representing a specific global
date and time. User agents may display the date and time in
whatever timezone is appropriate for the user.
If the element is mutable,
the user agent should allow the user to change the global date and time represented by
its value, as obtained by
parsing a global
date and time from it. User agents must not allow the user to
set the value to a string that
is not a valid global date and time string expressed in
UTC, though user agents may allow the user to set and view the time
in another timezone and silently translate the time to and from the
UTC timezone in the value. If
the user agent provides a user interface for selecting a global date and time, then the value must be set to a valid
global date and time string expressed in UTC representing the
user's selection. User agents should allow the user to set the value to the empty string.
The value attribute, if
specified, must have a value that is a valid global date and
time string.
The value sanitization algorithm is as
follows: If the value
of the element is a valid global date and time string,
then adjust the time so that the value represents the same point in
time but expressed in the UTC timezone, otherwise, set it to the
empty string instead.
The min attribute, if
specified, must have a value that is a valid global date and
time string. The max
attribute, if specified, must have a value that is a valid
global date and time string.
The step attribute is
expressed in seconds. The step scale factor is 1000
(which converts the seconds to milliseconds, as used in the other
algorithms). The default
step is 60 seconds.
When the element is suffering from a step mismatch,
the user agent may round the element's value to the nearest global date and time for which the
element would not suffer from a step mismatch.
The algorithm to convert a
string to a number, given a string input,
is as follows: If parsing a global date and time from input results in an error, then return an error;
otherwise, return the number of milliseconds elapsed from midnight
UTC on the morning of 1970-01-01 (the time represented by the value
"1970-01-01T00:00:00.0Z") to the parsed global date and time, ignoring leap
seconds.
The algorithm to convert a
number to a string, given a number input,
is as follows: Return a valid global date and time
string expressed in UTC that represents the global date and time that is input milliseconds after midnight UTC on the morning
of 1970-01-01 (the time represented by the value "1970-01-01T00:00:00.0Z").
The algorithm to convert a
string to a Date object, given a string input, is as follows: If parsing a global date and time
from input results in an error, then return an
error; otherwise, return a Date object representing the
parsed global date and time,
expressed in UTC.
The algorithm to convert a
Date object to a string, given a
Date object input, is as
follows: Return a valid global date and time
string expressed in UTC that represents the global date and time that is
represented by input.
The following common input element content
attributes, DOM attributes, and methods apply to the element:
autocomplete,
list,
max,
min,
readonly,
required, and
step content attributes;
list,
value,
valueAsDate,
valueAsNumber, and
selectedOption DOM attributes;
stepDown() and
stepUp() methods.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
alt,
action,
checked,
enctype,
maxlength,
method,
multiple,
novalidate,
pattern,
placeholder,
size,
src, and
target.
The
checked
DOM attribute does not apply to the element.
4.10.4.1.7 Date state
When an input element's type attribute is in the Date state, the rules in this
section apply.
The input element represents a control for setting
the element's value to a
string representing a specific date.
If the element is mutable,
the user agent should allow the user to change the date represented by its value, as obtained by parsing a date from it. User
agents must not allow the user to set the value to a string that is not a
valid date string. If the user agent provides a user
interface for selecting a date,
then the value must be set to
a valid date string representing the user's
selection. User agents should allow the user to set the value to the empty string.
The value attribute, if
specified, must have a value that is a valid date
string.
The value sanitization algorithm is as
follows: If the value
of the element is not a valid date string, then set it
to the empty string instead.
The min attribute, if
specified, must have a value that is a valid date
string. The max
attribute, if specified, must have a value that is a valid
date string.
The step attribute is
expressed in days. The step
scale factor is 86,400,000 (which converts the days to
milliseconds, as used in the other algorithms). The default step is 1 day.
When the element is suffering from a step mismatch,
the user agent may round the element's value to the nearest date for which the element would not
suffer from a step
mismatch.
The algorithm to convert a
string to a number, given a string input,
is as follows: If parsing
a date from input results in an error,
then return an error; otherwise, return the number of milliseconds
elapsed from midnight UTC on the morning of 1970-01-01 (the time
represented by the value "1970-01-01T00:00:00.0Z") to midnight UTC on the
morning of the parsed date,
ignoring leap seconds.
The algorithm to convert a
number to a string, given a number input,
is as follows: Return a valid date string that
represents the date that, in UTC,
is current input milliseconds after midnight UTC
on the morning of 1970-01-01 (the time represented by the value
"1970-01-01T00:00:00.0Z").
The algorithm to convert a
string to a Date object, given a string input, is as follows: If parsing a date from input
results in an error, then return an error; otherwise, return a
Date object representing midnight UTC on the morning of
the parsed date.
The algorithm to convert a
Date object to a string, given a
Date object input, is as
follows: Return a valid date string that
represents the date current at the
time represented by input in the UTC
timezone.
The following common input element content
attributes, DOM attributes, and methods apply to the element:
autocomplete,
list,
max,
min,
readonly,
required, and
step content attributes;
list,
value,
valueAsDate,
valueAsNumber, and
selectedOption DOM attributes;
stepDown() and
stepUp() methods.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
maxlength,
method,
multiple,
novalidate,
pattern,
placeholder,
size,
src, and
target.
The
checked
DOM attribute does not apply to the element.
4.10.4.1.8 Month state
When an input element's type attribute is in the Month state, the rules in this
section apply.
The input element represents a control for setting
the element's value to a
string representing a specific month.
If the element is mutable,
the user agent should allow the user to change the month represented by its value, as obtained by parsing a month from it. User
agents must not allow the user to set the value to a string that is not a
valid month string. If the user agent provides a user
interface for selecting a month,
then the value must be set to
a valid month string representing the user's
selection. User agents should allow the user to set the value to the empty string.
The value attribute, if
specified, must have a value that is a valid month
string.
The value sanitization algorithm is as
follows: If the value
of the element is not a valid month string, then set it
to the empty string instead.
The min attribute, if
specified, must have a value that is a valid month
string. The max
attribute, if specified, must have a value that is a valid
month string.
The step attribute is
expressed in months. The step
scale factor is 1 (there is no conversion needed as the
algorithms use months). The default step is 1
month.
When the element is suffering from a step mismatch,
the user agent may round the element's value to the nearest month for which the element would not
suffer from a step
mismatch.
The algorithm to convert a
string to a number, given a string input,
is as follows: If parsing a month time from input
results in an error, then return an error; otherwise, return the
number of months between January 1970 and the parsed month.
The algorithm to convert a
number to a string, given a number input,
is as follows: Return a valid month string
that represents the month
that has input months between it and January
1970.
The algorithm to convert a
string to a Date object, given a string input, is as follows: If parsing a month from input results in an error, then return an error;
otherwise, return a Date object representing midnight
UTC on the morning of the first day of the parsed month.
The algorithm to convert a
Date object to a string, given a
Date object input, is as
follows: Return a valid month string that
represents the month current at
the time represented by input in the UTC
timezone.
The following common input element content
attributes, DOM attributes, and methods apply to the element:
autocomplete,
list,
max,
min,
readonly,
required, and
step content attributes;
list,
value,
valueAsDate,
valueAsNumber, and
selectedOption DOM attributes;
stepDown() and
stepUp() methods.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
maxlength,
method,
multiple,
novalidate,
pattern,
placeholder,
size,
src, and
target.
The
checked
DOM attribute does not apply to the element.
4.10.4.1.9 Week state
When an input element's type attribute is in the Week state, the rules in this
section apply.
The input element represents a control for setting
the element's value to a
string representing a specific week.
If the element is mutable,
the user agent should allow the user to change the week represented by its value, as obtained by parsing a week from it. User
agents must not allow the user to set the value to a string that is not a
valid week string. If the user agent provides a user
interface for selecting a week,
then the value must be set to
a valid week string representing the user's
selection. User agents should allow the user to set the value to the empty string.
The value attribute, if
specified, must have a value that is a valid week
string.
The value sanitization algorithm is as
follows: If the value
of the element is not a valid week string, then set it
to the empty string instead.
The min attribute, if
specified, must have a value that is a valid week
string. The max
attribute, if specified, must have a value that is a valid
week string.
The step attribute is
expressed in weeks. The step
scale factor is 604,800,000 (which converts the weeks to
milliseconds, as used in the other algorithms). The default step is 1
week.
When the element is suffering from a step mismatch,
the user agent may round the element's value to the nearest week for which the element would not
suffer from a step
mismatch.
The algorithm to convert a
string to a number, given a string input,
is as follows: If parsing
a week string from input results in an
error, then return an error; otherwise, return the number of
milliseconds elapsed from midnight UTC on the morning of 1970-01-01
(the time represented by the value "1970-01-01T00:00:00.0Z") to midnight UTC on the
morning of the Monday of the parsed week, ignoring leap seconds.
The algorithm to convert a
number to a string, given a number input,
is as follows: Return a valid week string that
represents the week that, in UTC,
is current input milliseconds after midnight UTC
on the morning of 1970-01-01 (the time represented by the value
"1970-01-01T00:00:00.0Z").
The algorithm to convert a
string to a Date object, given a string input, is as follows: If parsing a week from input
results in an error, then return an error; otherwise, return a
Date object representing midnight UTC on the morning of
the Monday of the parsed week.
The algorithm to convert a
Date object to a string, given a
Date object input, is as
follows: Return a valid week string that
represents the week current at the
time represented by input in the UTC
timezone.
The following common input element content
attributes, DOM attributes, and methods apply to the element:
autocomplete,
list,
max,
min,
readonly,
required, and
step content attributes;
list,
value,
valueAsDate,
valueAsNumber, and
selectedOption DOM attributes;
stepDown() and
stepUp() methods.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
maxlength,
method,
multiple,
novalidate,
pattern,
placeholder,
size,
src, and
target.
The
checked
DOM attribute does not apply to the element.
4.10.4.1.10 Time state
When an input element's type attribute is in the Time state, the rules in this
section apply.
The input element represents a control for setting
the element's value to a
string representing a specific time.
If the element is mutable,
the user agent should allow the user to change the time represented by its value, as obtained by parsing a time from it. User
agents must not allow the user to set the value to a string that is not a
valid time string. If the user agent provides a user
interface for selecting a time,
then the value must be set to
a valid time string representing the user's
selection. User agents should allow the user to set the value to the empty string.
The value attribute, if
specified, must have a value that is a valid time
string.
The value sanitization algorithm is as
follows: If the value
of the element is not a valid time string, then set it
to the empty string instead.
The min attribute, if
specified, must have a value that is a valid time
string. The max
attribute, if specified, must have a value that is a valid
time string.
The step attribute is
expressed in seconds. The step scale factor is 1000
(which converts the seconds to milliseconds, as used in the other
algorithms). The default
step is 60 seconds.
When the element is suffering from a step mismatch,
the user agent may round the element's value to the nearest time for which the element would not
suffer from a step
mismatch.
The algorithm to convert a
string to a number, given a string input,
is as follows: If parsing
a time from input results in an error,
then return an error; otherwise, return the number of milliseconds
elapsed from midnight to the parsed time on a day with no time changes.
The algorithm to convert a
number to a string, given a number input,
is as follows: Return a valid time string that
represents the time that is input milliseconds after midnight on a day with no
time changes.
The algorithm to convert a
string to a Date object, given a string input, is as follows: If parsing a time from input
results in an error, then return an error; otherwise, return a
Date object representing the parsed time in UTC on 1970-01-01.
The algorithm to convert a
Date object to a string, given a
Date object input, is as
follows: Return a valid time string that
represents the UTC time component
that is represented by input.
The following common input element content
attributes, DOM attributes, and methods apply to the element:
autocomplete,
list,
max,
min,
readonly,
required, and
step content attributes;
list,
value,
valueAsDate,
valueAsNumber, and
selectedOption DOM attributes;
stepDown() and
stepUp() methods.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
maxlength,
method,
multiple,
novalidate,
pattern,
placeholder,
size,
src, and
target.
The
checked
DOM attribute does not apply to the element.
4.10.4.1.11 Local Date and Time state
When an input element's type attribute is in the Local Date and Time
state, the rules in this section apply.
The input element represents a control for setting
the element's value to a
string representing a local
date and time, with no time zone information.
If the element is mutable,
the user agent should allow the user to change the date and time represented by
its value, as obtained by
parsing a date and
time from it. User agents must not allow the user to set the
value to a string that is not
a valid local date and time string. If the user agent
provides a user interface for selecting a local date and time, then the
value must be set to a
valid local date and time string representing the
user's selection. User agents should allow the user to set the value to the empty string.
The value attribute, if
specified, must have a value that is a valid local date and
time string.
The value sanitization algorithm is as
follows: If the value
of the element is not a valid local date and time
string, then set it to the empty string instead.
The min attribute, if
specified, must have a value that is a valid local date and
time string. The max
attribute, if specified, must have a value that is a valid
local date and time string.
The step attribute is
expressed in seconds. The step scale factor is 1000
(which converts the seconds to milliseconds, as used in the other
algorithms). The default
step is 60 seconds.
When the element is suffering from a step mismatch,
the user agent may round the element's value to the nearest local date and time for which
the element would not suffer from a step mismatch.
The algorithm to convert a
string to a number, given a string input,
is as follows: If parsing a date and time from input results in an error, then return an error;
otherwise, return the number of milliseconds elapsed from midnight
on the morning of 1970-01-01 (the time represented by the value
"1970-01-01T00:00:00.0") to the parsed local date and time, ignoring
leap seconds.
The algorithm to convert a
number to a string, given a number input,
is as follows: Return a valid local date and time
string that represents the date and time that is input milliseconds after midnight on the morning of
1970-01-01 (the time represented by the value "1970-01-01T00:00:00.0").
The following common input element content
attributes, DOM attributes, and methods apply to the element:
autocomplete,
list,
max,
min,
readonly,
required, and
step content attributes;
list,
value,
valueAsNumber, and
selectedOption DOM attributes;
stepDown() and
stepUp() methods.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
maxlength,
method,
multiple,
novalidate,
pattern,
placeholder,
size,
src, and
target.
The following DOM attributes do not apply to the element:
valueAsDate and
checked.
4.10.4.1.12 Number state
When an input element's type attribute is in the Number state, the rules in
this section apply.
The input element represents a control for setting
the element's value to a
string representing a number.
If the element is mutable,
the user agent should allow the user to change the number
represented by its value, as
obtained from applying the rules for parsing floating point
number values to it. User agents must not allow the user to
set the value to a string that
is not a valid floating point number. If the user agent
provides a user interface for selecting a number, then the value must be set to a valid
floating point number representing the user's selection. User
agents should allow the user to set the value to the empty string.
The value attribute, if
specified, must have a value that is a valid floating point
number.
The value sanitization algorithm is as
follows: If the value
of the element is not a valid floating point number,
then set it to the empty string instead.
The min attribute, if
specified, must have a value that is a valid floating point
number. The max
attribute, if specified, must have a value that is a valid
floating point number.
The step scale
factor is 1. The default step is 1
(allowing only integers, unless the min attribute has a non-integer
value).
When the element is suffering from a step mismatch,
the user agent may round the element's value to the nearest number for
which the element would not suffer from a step mismatch.
The algorithm to convert a
string to a number, given a string input,
is as follows: If applying the rules for parsing
floating point number values to input
results in an error, then return an error; otherwise, return the
resulting number.
The algorithm to convert a
number to a string, given a number input,
is as follows: Return a valid floating point
number that represents input.
The following common input element content
attributes, DOM attributes, and methods apply to the element:
autocomplete,
list,
max,
min,
readonly,
required, and
step content attributes;
list,
value,
valueAsNumber, and
selectedOption DOM attributes;
stepDown() and
stepUp() methods.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
maxlength,
method,
multiple,
novalidate,
pattern,
placeholder,
size,
src, and
target.
The following DOM attributes do not apply to the element:
valueAsDate and
checked.
4.10.4.1.13 Range state
When an input element's type attribute is in the Range state, the rules in this
section apply.
The input element represents a control for setting
the element's value to a
string representing a number, but with the caveat that the exact
value is not important, letting UAs provide a simpler interface than
they do for the Number
state.
In this state, the range and step constraints are
enforced even during user input, and there is no way to set the
value to the empty string.
If the element is mutable,
the user agent should allow the user to change the number
represented by its value, as
obtained from applying the rules for parsing floating point
number values to it. User agents must not allow the user to
set the value to a string that
is not a valid floating point number. If the user agent
provides a user interface for selecting a number, then the value must be set to a valid
floating point number representing the user's selection. User
agents must not allow the user to set the value to the empty string.
The value attribute, if
specified, must have a value that is a valid floating point
number.
The value sanitization algorithm is as
follows: If the value
of the element is not a valid floating point number,
then set it to a valid floating point number that
represents the default value.
The min attribute, if
specified, must have a value that is a valid floating point
number. The default
minimum is 0. The max
attribute, if specified, must have a value that is a valid
floating point number. The default maximum is 100.
The default
value is the minimum
plus half the difference between the minimum and the maximum, unless the maximum is less than the minimum, in which case the default value is
the minimum.
When the element is suffering from a range
underflow, the user agent must set the element's value to a valid floating point
number that represents the minimum.
When the element is suffering from a range overflow,
if the maximum is not less
than the minimum, the user
agent must set the element's value to a valid floating point
number that represents the maximum.
The step scale
factor is 1. The default step is 1
(allowing only integers, unless the min attribute has a non-integer
value).
When the element is suffering from a step mismatch,
the user agent must round the element's value to the nearest number for
which the element would not suffer from a step mismatch, and which is greater
than or equal to the minimum,
and, if the maximum is not
less than the minimum, which
is less than or equal to the maximum.
The algorithm to convert a
string to a number, given a string input,
is as follows: If applying the rules for parsing
floating point number values to input
results in an error, then return an error; otherwise, return the
resulting number.
The algorithm to convert a
number to a string, given a number input,
is as follows: Return a valid floating point
number that represents input.
The following common input element content
attributes, DOM attributes, and methods apply to the element:
autocomplete,
list,
max,
min, and
step content attributes;
list,
value,
valueAsNumber, and
selectedOption DOM attributes;
stepDown() and
stepUp() methods.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
maxlength,
method,
multiple,
novalidate,
pattern,
placeholder,
readonly,
required,
size,
src, and
target.
The following DOM attributes do not apply to the element:
checked and
valueAsDate.
4.10.4.1.14 Color state
When an input element's type attribute is in the Color state, the rules in this
section apply.
The input element represents a color well control,
for setting the element's value to a string representing a
simple color.
In this state, there is always a color picked, and
there is no way to set the value to the empty string.
If the element is mutable,
the user agent should allow the user to change the color represented
by its value, as obtained from
applying the rules for parsing simple color values to
it. User agents must not allow the user to set the value to a string that is not a
valid lowercase simple color. If the user agent
provides a user interface for selecting a color, then the value must be set to the result of
using the rules for serialising simple color values to
the user's selection. User agents must not allow the user to set the
value to the empty string.
The value attribute, if
specified, must have a value that is a valid simple
color.
The value sanitization algorithm is as
follows: If the value
of the element is a valid simple color, then set it to
the value of the element
converted to lowercase; otherwise, set it to the string
"#000000".
The following common input element content
attributes, DOM attributes, and methods apply to the element:
autocomplete and
list content attributes;
list,
value, and
selectedOption DOM attributes.
The value DOM attribute is
in mode value.
The input and change events apply.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
checked,
enctype,
maxlength,
max,
method,
min,
multiple,
novalidate,
pattern,
placeholder,
readonly,
required,
size,
src,
step, and
target.
The following DOM attributes and methods do not apply to the
element:
checked,
valueAsDate, and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
4.10.4.1.15 Checkbox state
When an input element's type attribute is in the Checkbox state, the rules in
this section apply.
The input element represents a two-state control
that represents the element's checkedness state. If the
element's checkedness state
is true, the control represents a positive selection, and if it is
false, a negative selection.
If the element is mutable,
then: The pre-click activation steps consist of setting
the element's checkedness to
its opposite value (i.e. true if it is false, false if it is
true). The canceled activation steps consist of setting
the checkedness back to the
value it had before the pre-click activation steps were
run. The activation behavior is to fire a simple
event called change at the
element, then broadcast formchange events at the
element's form owner.
Constraint validation: If the element is required and its checkedness is false, then the
element is suffering from being missing.
The following common input element content
attributes and DOM attributes apply to the element:
checked, and
required content attributes;
checked and
value DOM attributes.
The value DOM attribute is
in mode default/on.
The change event applies.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
autocomplete,
enctype,
list,
max,
maxlength,
method,
min,
multiple,
novalidate,
pattern,
placeholder,
readonly,
size,
src,
step, and
target.
The following DOM attributes and methods do not apply to the element:
list,
selectedOption,
valueAsDate and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
The input event does not
apply.
When an input element's type attribute is in the Radio Button state, the rules
in this section apply.
The input element represents a control that, when
used in conjunction with other input elements, forms a
radio button group in which only one control can have its
checkedness state set to
true. If the element's checkedness state is true, the
control represents the selected control in the group, and if it is
false, it indicates a control in the group that is not selected.
The radio button group that contains an
input element a also contains all
the other input elements b that
fulfill all of the following conditions:
A document must not contain an input element whose
radio button group contains only that element.
When any of the following events occur, if the element's checkedness state is true after
the event, the checkedness state of all the
other elements in the same radio button group must be set to
false:
The element's checkedness state is set to
true (for whatever reason).
The element's name
attribute is added, removed, or changes value.
The element's form owner changes.
If the element is mutable,
then: The pre-click activation steps consist of setting
the element's checkedness to
true. The canceled activation steps consist of setting
the element's checkedness to
false. The activation behavior is to fire a
simple event called change
at the element, then broadcast formchange events at the
element's form owner.
Constraint validation: If the element is required and all of the
input elements in the radio button group have a
checkedness that is
false, then the element is suffering from being
missing.
If none of the radio buttons in a radio button
group are checked when they are inserted into the document,
then they will all be initially unchecked in the interface, until
such time as one of them is checked (either by the user or by
script).
The following common input element content
attributes and DOM attributes apply to the element:
checked and
required content attributes;
checked and
value DOM attributes.
The value DOM attribute is
in mode default/on.
The change event applies.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
autocomplete,
enctype,
list,
max,
maxlength,
method,
min,
multiple,
novalidate,
pattern,
placeholder,
readonly,
size,
src,
step, and
target.
The following DOM attributes and methods do not apply to the element:
list,
selectedOption,
valueAsDate and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
The input event does not
apply.
4.10.4.1.17 File Upload state
When an input element's type attribute is in the File Upload state, the rules in this
section apply.
The input element represents a list of selected files, each
file consisting of a file name, a file type, and a file body (the
contents of the file).
If the element is mutable,
the user agent should allow the user to change the files on the
list, e.g. adding or removing files. Files can be from the
filesystem or created on the fly, e.g. a picture taken from a camera
connected to the user's device.
Constraint validation: If the element is required and the list of selected files is
empty, then the element is suffering from being
missing.
Unless the multiple
attribute is set, there must be no more than one file in the list of
selected
files.
The accept
attribute may be specified to provide user agents with a hint of
what file types the server will be able to accept.
If specified, the attribute must consist of a set of
comma-separated tokens, each of which must be an ASCII
case-insensitive match for one of the following:
- The string
audio/*文字列 audio/*
- Indicates that sound files are accepted.音声ファイルを受け付けることを示します。
- The string
video/*文字列 video/*
- Indicates that video files are accepted.動画ファイルを受け付けることを示します。
- The string
image/*文字列 image/*
- Indicates that image files are accepted.画像ファイルを受け付けることを示します。
- A valid MIME type, with no parameters妥当な MIME 型、引数なし
- Indicates that files of the specified type are accepted. [RFC2046]
The tokens must not be ASCII case-insensitive
matches for any of the other tokens (i.e. duplicates are not
allowed).
User agents should prevent the user from selecting files that are
not accepted by one (or more) of these tokens.
The following common input element content
attributes apply to the element:
accept,
multiple, and
required.
The change event applies.
The following content attributes must not be specified and do not
apply to the element:
action,
alt,
autocomplete,
checked,
enctype,
list,
max,
maxlength,
method,
min,
novalidate,
pattern,
placeholder,
readonly,
size,
src,
step, and
target.
The element's value
attribute must be omitted.
The following DOM attributes and methods do not apply to the element:
checked,
list,
selectedOption,
value,
valueAsDate and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
The input event does not
apply.
When an input element's type attribute is in the Submit Button state, the rules
in this section apply.
The input element represents a button that, when
activated, submits the form. If the element has a value attribute, the button's label
must be the value of that attribute; otherwise, it must be an
implementation-defined string that means "Submit" or some such. The
element is a button,
specifically a submit
button.
If the element is mutable,
the user agent should allow the user to activate the element.
The element's activation behavior, if the element
has a form owner, is to submit the form
owner from the input element; otherwise, it is
to do nothing.
The action, enctype, method, novalidate, and target attributes are attributes
for form submission.
The following common input element content
attributes and DOM attributes apply to the element:
action,
enctype,
method,
novalidate, and
target content attributes;
value DOM attribute.
The value DOM attribute is
in mode default.
The following content attributes must not be specified and do not
apply to the element:
accept,
alt,
autocomplete,
checked,
list,
max,
maxlength,
min,
multiple,
pattern,
placeholder,
readonly,
required
size,
src, and
step.
The following DOM attributes and methods do not apply to the element:
checked,
list,
selectedOption,
valueAsDate and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
The input and change events do not apply.
When an input element's type attribute is in the Image Button state, the rules
in this section apply.
The input element represents either an image from
which a user can select a coordinate and submit the form, or
alternatively a button from which the user can submit the form. The
element is a button,
specifically a submit
button.
The image is given by the src attribute. The src attribute must be present, and
must contain a valid URL referencing a non-interactive,
optionally animated, image resource that is neither paged nor
scripted.
When any of the following events occur, the user agent must
fetch the resource specifed by the src attribute's value, unless the user
agent cannot support images, or its support for images has been
disabled, or the user agent only fetches elements on demand:
The input element's type attribute is first set to the
Image Button state
(possibly when the element is first created), and the src attribute is present.
The input element's type attribute is changed back to
the Image Button state,
and the src attribute is
present, and its value has changed since the last time the type attribute was in the Image Button state.
The input element's type attribute is in the Image Button state, and the
src attribute is set or
changed.
Fetching the image must delay the load event.
If the image was successfully obtained, with no network errors,
and the image's type is a supported image type, and the image is a
valid image of that type, then the image is said to be
available. If this is true before the image is completely
downloaded, each task that is
queued by the networking
task source while the image is being fetched must update the presentation of the
image appropriately.
The user agents should apply the image sniffing rules to determine the type
of the image, with the image's associated
Content-Type headers giving the official
type. If these rules are not applied, then the type of the
image must be the type given by the image's associated Content-Type headers.
User agents must not support non-image resources with the
input element. User agents must not run executable code
embedded in the image resource. User agents must only display the
first page of a multipage resource. User agents must not allow the
resource to act in an interactive fashion, but should honour any
animation in the resource.
The task that is queued by the networking task
source once the resource has been fetched, must, if the download was successful
and the image is available, queue a task to
fire a load event on
the input element; and otherwise, if the fetching
process fails without a response from the remote server, or
completes but the image is not a valid or supported image,
queue a task to fire an error event on the
input element.
The alt attribute
provides the textual label for the alternative button for users and
user agents who cannot use the image. The alt attribute must also be present,
and must contain a non-empty string.
If the src attribute is set,
and the image is available and the user agent is configured
to display that image, then: The element represents a control for
selecting a coordinate from
the image specified by the src
attribute; if the element is mutable, the user agent should
allow the user to select this coordinate. The
activation behavior in this case consists of taking the
user's selected coordinate, and
then, if the element has a form owner, submitting the input
element's form owner from the input
element. If the user activates the control without explicitly
selecting a coordinate, then the coordinate (0,0) must be
assumed.
Otherwise, the element represents a submit button whose label is
given by the value of the alt
attribute; if the element is mutable, the user agent should
allow the user to activate the button. The activation
behavior in this case consists of setting the selected
coordinate to (0,0), and then, if the element has a
form owner, submitting the input
element's form owner from the input
element.
The selected
coordinate must consist of an x-component
and a y-component. The x-component must be greater than or equal to zero,
and less than or equal to the rendered width, in CSS pixels, of the
image, plus the widths of the left and right borders rendered around
the image, if any. The y-component must be
greater than or equal to zero, and less than or equal to the
rendered height, in CSS pixels, of the image, plus the widths of the
top and bottom bordered rendered around the image, if any. The
coordinates must be relative to the image's borders, where there are
any, and the edge of the image otherwise.
The action, enctype, method, novalidate, and target attributes are attributes
for form submission.
The following common input element content
attributes and DOM attributes apply to the element:
action,
alt,
enctype,
method,
novalidate,
src, and
target content attributes;
value DOM attribute.
The value DOM attribute is
in mode default.
The following content attributes must not be specified and do not
apply to the element:
accept,
autocomplete,
checked,
list,
max,
maxlength,
min,
multiple,
pattern,
placeholder,
readonly,
required
size, and
step.
The element's value
attribute must be omitted.
The following DOM attributes and methods do not apply to the element:
checked,
list,
selectedOption,
valueAsDate and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
The input and change events do not apply.
Many aspects of this state's behavior are similar to
the behavior of the img element. Readers are encouraged
to read that section, where many of the same requirements are
described in more detail.
When an input element's type attribute is in the Reset Button state, the rules
in this section apply.
The input element represents a button that, when
activated, resets the form. If the element has a value attribute, the button's label
must be the value of that attribute; otherwise, it must be an
implementation-defined string that means "Reset" or some such. The
element is a button.
If the element is mutable,
the user agent should allow the user to activate the element.
The element's activation behavior, if the element
has a form owner, is to reset the form owner;
otherwise, it is to do nothing.
Constraint validation: The element is
barred from constraint validation.
The value DOM attribute
applies to this element and is in mode default.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
autocomplete,
checked,
enctype,
list,
max,
maxlength,
method,
min,
multiple,
novalidate,
pattern,
placeholder,
readonly,
required
size,
src,
step, and
target.
The following DOM attributes and methods do not apply to the element:
checked,
list,
selectedOption,
valueAsDate and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
The input and change events do not apply.
When an input element's type attribute is in the Button state, the rules in
this section apply.
The input element represents a button with no
default behavior. If the element has a value attribute, the button's label
must be the value of that attribute; otherwise, it must be the empty
string. The element is a button.
If the element is mutable,
the user agent should allow the user to activate the element. The
element's activation behavior is to do nothing.
Constraint validation: The element is
barred from constraint validation.
The value DOM attribute
applies to this element and is in mode default.
The following content attributes must not be specified and do not
apply to the element:
accept,
action,
alt,
autocomplete,
checked,
enctype,
list,
max,
maxlength,
method,
min,
multiple,
novalidate,
pattern,
placeholder,
readonly,
required
size,
src,
step, and
target.
The following DOM attributes and methods do not apply to the element:
checked,
list,
selectedOption,
valueAsDate and
valueAsNumber DOM attributes;
stepDown() and
stepUp() methods.
The input and change events do not apply.
These attributes only apply to an input element if
its type attribute is in a
state whose definition declares that the attribute applies. When an
attribute doesn't apply to an input element, user
agents must ignore the attribute.
The autocomplete
attribute is an enumerated attribute. The attribute has
two states. The on
keyword maps to the on state, and the
off keyword maps to
the off
state. The attribute may also be omitted. The missing value
default is the on state.
The off
state indicates that the control's input data is either particularly
sensitive (for example the activation code for a nuclear weapon) or
is a value that will never be reused (for example a one-time-key for
a bank login) and the user will therefore have to explicitly enter
the data each time, instead of being able to rely on the UA to
prefill the value for him.
Conversely, the on state indicates
that the value is not particularly sensitive and the user can expect
to be able to rely on his user agent to remember values he has
entered for that control.
When an input element's autocomplete attribute is in
the on state,
the user agent may store the value entered by the user so that if
the user returns to the page, the UA can prefill the form. When an
input element's autocomplete attribute is in
the off
state, the user agent should not remember the control's value.
The autocompletion mechanism must be implemented by the user
agent acting as if the user had modified the element's value, and must be done at a time
where the element is mutable
(e.g. just after the element has been inserted into the document, or
when the user agent stops
parsing).
Banks frequently do not want UAs to prefill login
information:
<p>Account: <input type="text" name="ac" autocomplete="off"></p>
<p>PIN: <input type="text" name="pin" autocomplete="off"></p>
A user agent may allow the user to disable support for this
attribute's off state (causing
the attribute to always be in the on state and always
allowing values to be remembered and prefilled). Support for the
off state
should be enabled by default, and the ability to disable support
should not be trivially accessible, as there are significant
security implications for the user if support for this attribute is
disabled.
4.10.4.2.2 The list attribute4.10.4.2.2 list 属性
The list
attribute is used to identify an element that lists predefined
options suggested to the user.
If present, its value must be the ID of a datalist
element in the same document.
The suggestions source
element is the first element in the document in tree
order to have an ID equal to the value of the list attribute, if that element is a
datalist element. If there is no list attribute, or if there is no
element with that ID, or if the first element with that ID is not a
datalist element, then there is no suggestions source element.
If there is a suggestions source
element, then each option element that is a
descendant of the suggestions
source element, that is not disabled, and whose value is a string that isn't the
empty string and that the user would be allowed to enter as the
input element's value, represents a suggestion. Each
suggestion has a value and
a label.
When the user agent is allowing the user to edit the
input element's value, the user agent should offer
the suggestions to the user in a manner suitable for the type of
control used. The user agent may use the suggestion's label to identify the suggestion
if appropriate. If the user selects a suggestion, then the
input element's value must be set to the selected
suggestion's value, as if
the user had written that value himself.
User agents should filter the suggestions to hide suggestions
that would cause the element to not satisfy its constraints.
If the list attribute does
not apply, there is no suggestions
source element.
4.10.4.2.3 The readonly attribute4.10.4.2.3 readonly 属性
The readonly
attribute is a boolean attribute. When specified, the
element is immutable.
Constraint validation: If the readonly attribute is specified
on an input element, the element is barred from
constraint validation.
4.10.4.2.4 The size attribute4.10.4.2.4 size 属性
The size
attribute gives the number of characters that, in a visual
rendering, the user agent is to allow the user to see while editing
the element's value.
The size attribute, if
specified, must have a value that is a valid non-negative
integer greater than zero.
If the attribute is present, then its value must be parsed using
the rules for parsing non-negative integers, and if the
result is a number greater than zero, then the user agent should
ensure that at least that many characters are visible.
The rendering section will define this in more
detail.
The size DOM attribute
limited to only positive non-zero numbers.
4.10.4.2.5 The required attribute4.10.4.2.5 required 属性
The required
attribute is a boolean attribute. When specified, the
element is required.
Constraint validation: If the element is required, and its value DOM attribute applies and is in
the mode value, and the
element is mutable, and the
element's value is the empty
string, then the element is suffering from being
missing.
4.10.4.2.6 The multiple attribute4.10.4.2.6 multiple 属性
The multiple
attribute is a boolean attribute that indicates whether
the user is to be allowed to specify more than one value.
4.10.4.2.7 The maxlength attribute4.10.4.2.7 maxlength 属性
The maxlength attribute,
when it applies, is a form control
maxlength attribute controlled by the
input element's dirty value flag.
If the input element has a maximum allowed
value length, then the codepoint length of the
value of the element's value
attribute must be equal to or less than the element's maximum
allowed value length.
4.10.4.2.8 The pattern attribute4.10.4.2.8 pattern 属性
The pattern
attribute specifies a regular expression against which the control's
value is to be checked.
If specified, the attribute's value must match the Pattern production of ECMA 262's grammar. [ECMA262]
Constraint validation: If the element's value is not the empty string, and
the element's pattern
attribute is specified and the attribute's value, when compiled as
an ECMA 262 regular expression with the global, ignoreCase, and multiline flags disabled (see ECMA 262,
sections 15.10.7.2 through 15.10.7.4), compiles successfully but the
resulting regular expression does not match the entirety of the
element's value, then the
element is suffering from a pattern mismatch. [ECMA262]
This implies that the regular expression language
used for this attribute is the same as that defined in ECMA 262,
except that the pattern
attribute must match the entire value, not just any subset (somewhat
as if it implied a ^(?: at the start of the
pattern and a )$ at the end).
When an input element has a pattern attribute specified,
authors should include a title
attribute to give a description of the pattern. User agents may use
the contents of this attribute, if it is present, when informing the
user that the pattern is not matched, or at any other suitable time,
such as in a tooltip or read out by assistive technology when the
control gains focus.
For example, the following snippet:
<label> Part number:
<input pattern="[0-9][A-Z]{3}" name="part"
title="A part number is a digit followed by three uppercase letters."/>
</label>
...could cause the UA to display an alert such as:
part number is a digit followed by three uppercase letters.
You cannot complete this form until the field is correct.
When a control has a pattern attribute, the
title attribute, if used, must describe the pattern.
Additional information could also be included, so long as it assists
the user in filling in the control. Otherwise, assistive technology
would be impaired.
For instance, if the title attribute contained
the caption of the control, assistive technology could end up saying
something like The text you have entered does not match the
required pattern. Birthday, which is not useful.
UAs may still show the title in non-error situations
(for example, as a tooltip when hovering over the control), so
authors should be careful not to word titles as if an
error has necessarily occurred.
4.10.4.2.9 The min and max attributes
The min and max attributes indicate
the allowed range of values for the element.
Their syntax is defined by the section that defines the type attribute's current state.
If the element has a min
attribute, and the result of applying the algorithm to convert a
string to a number to the value of the min attribute is a a number, then that
number is the element's minimum; otherwise, if the the type attribute's current state
defines a default
minimum, then that is the minimum; otherwise, the element has
no minimum.)
Constraint validation: When the element has a
minimum, and the result of
applying the algorithm to convert a
string to a number to the string given by the element's value is a number, and the number
obtained from that algorithm is less than the minimum, the element is
suffering from an underflow.
The min attribute also
defines the step
base.
If the element has a max
attribute, and the result of applying the algorithm to convert a
string to a number to the value of the max attribute is a a number, then that
number is the element's maximum; otherwise, if the the type attribute's current state
defines a default
maximum, then that is the maximum; otherwise, the element has
no maximum.)
Constraint validation: When the element has a
maximum, and the result of
applying the algorithm to convert a
string to a number to the string given by the element's value is a number, and the number
obtained from that algorithm is more than the maximum, the element is
suffering from an overflow.
The max attribute's value
(the maximum) must not be
less than the min attribute's
value (its minimum).
If an element has a maximum that is less than its minimum, then so long as the element
has a value, it will either be
suffering from an underflow or suffering from an
overflow.
4.10.4.2.10 The step attribute4.10.4.2.10 step 属性
The step
attribute indicates the granularity that is expected (and required)
of the value, by limiting
the allowed values. The section that defines the type attribute's current state also
defines the default
step and the step
scale factor, which are used in processing the attribute as
described below.
The step attribute, if
specified, must either have a value that is a valid floating
point number that parses to a number that is greater than
zero, or must have a value that is an ASCII
case-insensitive match for the string "any".
The attribute provides the allowed value step for the element,
as follows:
If the attribute is absent, then the allowed value step is the default step multiplied
by the step scale
factor.
Otherwise, if the attribute's value is an ASCII
case-insensitive match for the string "any", then there is no allowed value step.
Otherwise, if the rules for parsing floating point number
values, when they are applied to the attribute's value,
return an error, zero, or a number less than zero, then the allowed value step is the default step multiplied
by the step scale
factor.
Otherwise, the allowed value
step is the number returned by the rules for parsing
floating point number values when they are applied to the
attribute's value, multiplied by the step scale factor.
The step base is the
result of applying the algorithm to convert a
string to a number to the value of the min attribute, unless the element does
not have a min attribute
specified or the result of applying that algorithm is an error, in
which case the step base
is zero.
Constraint validation: When the element has an
allowed value step, and the
result of applying the algorithm to convert a
string to a number to the string given by the element's value is a number, and that
number subtracted from the step
base is not an integral multiple of the allowed value step, the element is
suffering from a step mismatch.
The placeholder
attribute represents a short hint (a word or short phrase)
intended to aid the user with data entry. A hint could be a sample
value or a brief description of the expected format.
For a longer hint or other advisory text, the title attribute is more appropriate.
The placeholder
attribute should not be used as an alternative to a
label.
User agents should present this hint to the user only when the
element's value is the empty
string and the control is not focused (e.g. by displaying it inside
a blank unfocused control).
Here is an example of a mail configuration user interface that
uses the placeholder
attribute:
<fieldset>
<legend>Mail Account</legend>
<p><label>Name: <input type="text" name="fullname" placeholder="John Ratzenberger"></label></p>
<p><label>Address: <input type="email" name="address" placeholder="john@example.net"></label></p>
<p><label>Password: <input type="password" name="password"></label></p>
<p><label>Description: <input type="text" name="desc" placeholder="My Email Account"></label></p>
</fieldset>
The value DOM
attribute allows scripts to manipulate the value of an input
element. If the attribute applies, then it is in one of the
following modes, which define its behavior:
- value
- On getting, it must return the current value of the element. On setting,
it must set the element's value to the new value, set the
element's dirty value
flag to true, and then invoke the value sanitization
algorithm, if the element's
type attribute's current state
defines one.
- default
- On getting, if the element has a
value attribute, it must return
that attribute's value; otherwise, it must return the empty
string. On setting, it must set the element's value attribute to the new
value.
- default/on
- On getting, if the element has a
value attribute, it must return
that attribute's value; otherwise, it must return the string "on". On setting, it must set the element's value attribute to the new
value.
If the attribute does not apply, then on getting and setting it
must throw an INVALID_ACCESS_ERR exception.
The checked DOM
attribute allows scripts to manipulate the checkedness of an
input element. On getting, it must return the current
checkedness of the element;
and on setting, it must set the element's checkedness to the new value and
set the element's dirty checkedness
flag to true.
The valueAsDate DOM
attribute represents the value of the element, interpreted
as a date.
On getting, if the valueAsDate attribute does not
apply, as defined for the input element's type attribute's current state, then
return null. Otherwise, run the algorithm to convert a
string to a Date object defined for that state;
if the algorithm returned a Date object, then return
it, otherwise, return null.
On setting, if the valueAsDate attribute does not
apply, as defined for the input element's type attribute's current state, then
throw an INVALID_ACCESS_ERR exception; otherwise, if
the new value is null, then set the value of the element to the empty
string; otherwise, run the algorithm to convert a
Date object to a string, as defined for that
state, on the new value, and set the value of the element to resulting
string.
The valueAsNumber DOM
attribute represents the value
of the element, interpreted as a number.
On getting, if the valueAsNumber attribute does
not apply, as defined for the input element's type attribute's current state, then
return a Not-a-Number (NaN) value. Otherwise, if the valueAsDate
attribute applies, run the algorithm to convert a
string to a Date object defined for that state;
if the algorithm returned a Date object, then return
the time value of the object (the number of milliseconds from
midnight UTC the morning of 1970-01-01 to the time represented by
the Date object), otherwise, return a Not-a-Number
(NaN) value. Otherwise, run the algorithm to convert a
string to a number defined for that state; if the algorithm
returned a number, then return it, otherwise, return a Not-a-Number
(NaN) value.
On setting, if the valueAsNumber attribute does
not apply, as defined for the input element's type attribute's current state, then
throw an INVALID_ACCESS_ERR exception. Otherwise, if
the valueAsDate
attribute applies, run the algorithm to convert a
Date object to a string defined for that state,
passing it a Date object whose time value is the
new value, and set the value
of the element to resulting string. Otherwise, run the algorithm to convert a
number to a string, as defined for that state, on the new
value, and set the value of
the element to resulting string.
The stepDown()
and stepUp()
methods, when invoked, must run the following algorithm:
If the stepDown() and
stepUp() methods do not
apply, as defined for the input element's type attribute's current state, then
throw an INVALID_ACCESS_ERR exception, and abort these
steps.
If the element has no allowed value step, then throw an
INVALID_ACCESS_ERR exception, and abort these
steps.
If applying the algorithm to convert a
string to a number to the string given by the element's
value results in an error,
then throw an INVALID_ACCESS_ERR exception, and abort
these steps; otherwise, let value be the result
of that algorithm.
If the method invoked was the stepDown() method, negate value.
Let value be the result of adding the
allowed value step to value.
Let value as string be the result of
running the algorithm to convert a
number to a string, as defined for the input
element's type attribute's
current state, on value.
If the element has a minimum, and the value is less than that minimum, then throw a
INVALID_ACCESS_ERR exception.
If the element has a maximum, and the value is greater than that maximum, then throw a
INVALID_ACCESS_ERR exception.
Set the value of the
element to value as string.
The list DOM
attribute must return the current suggestions source element, if
any, or null otherwise.
The selectedOption
DOM attribute must return the first option element, in
tree order, to be a child of the suggestions source element and
whose value matches the
input element's value, if any. If there is no suggestions source element, or if
it contains no matching option element, then the selectedOption attribute
must return null.
4.10.4.4 Common event behaviors
When the input
event applies, any time the user causes the element's value to change, the user agent must
queue a task to fire a simple event called
input at the input
element, then broadcast forminput events at the
input element's form owner. User agents
may wait for a suitable break in the user's interaction before
queuing the task; for example, a user agent could wait for the user
to have not hit a key for 100ms, so as to only fire the event when
the user pauses, instead of continuously for each keystroke.
Examples of a user changing the element's value would include the user typing
into a text field, pasting a new value into the field, or undoing an
edit in that field. Some user interactions do not cause changes to
the value, e.g. hitting the "delete" key in an empty text field, or
replacing some text in the field with text from the clipboard that
happens to be exactly the same text.
When the change event applies,
if the element does not have an activation behavior
defined but uses a user interface that involves an explicit commit
action, then any time the user commits a change to the element's
value or list of selected files, the
user agent must queue a task to fire a simple
event called change at the
input element, then broadcast formchange events at the
input element's form owner.
An example of a user interface with a commit
action would be a File
Upload control that consists of a single button that brings
up a file selection dialog: when the dialog is closed, if that the
file selection
changed as a result, then the user has commited a new file selection.
Another example of a user interface with a commit
action would be a Date
control that allows both text-based user input and user selection
from a drop-down calendar: while text input might not have an
explicit commit step, selecting a date from the drop down calendar
and then dismissing the drop down would be a commit action.
When the user agent changes the element's value on behalf of the user (e.g. as
part of a form prefilling feature), the user agent must follow these
steps:
If the input event
applies, queue a task to fire a simple
event called input at the
input element.
If the input event
applies, broadcast forminput events at the
input element's form owner.
If the change event
applies, queue a task to fire a simple
event called change at the
input element.
If the change event
applies, broadcast formchange events at the
input element's form owner.
In addition, when the change event applies, change events can also be fired as part
of the element's activation behavior and as part of the
unfocusing steps.
The task source for these task is the user interaction task
source.
- Categories分類
- Phrasing content.語句付け内容。
- Interactive content.対話的内容。
- Listed, labelable, and submittable form-associated element.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content, but there must be no interactive content descendant.語句付け内容、ただし対話的内容な子孫があってはなりません。
- Element-specific attributes:要素固有属性:
actionautofocusdisabledenctypeformmethodnamenovalidatetargettypevalue- DOM interface:DOM 界面:
-
interface HTMLButtonElement : HTMLElement {
attribute DOMString action;
attribute boolean autofocus;
attribute boolean disabled;
attribute DOMString enctype;
readonly attribute HTMLFormElement form;
attribute DOMString method;
attribute DOMString name;
attribute DOMString noValidate;
attribute DOMString target;
attribute DOMString type;
attribute DOMString value;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
void setCustomValidity(in DOMString error);
readonly attribute NodeList labels;
};
The button element represents a button. If the
element is not disabled,
then the user agent should allow the user to activate the
button.
The element is a button.
The type
attribute controls the behavior of the button when it is activated.
It is an enumerated attribute. The following table
lists the keywords and states for the attribute — the keywords
in the left column map to the states in the cell in the second
column on the same row as the keyword.
The missing value default is the Submit Button
state.
If the type attribute is in
the Submit Button
state, the element is specifically a submit button.
If the element is not disabled, the activation
behavior of the button element is to run the
steps defined in the following list for the current state of the
element's type attribute.
- Submit Button
If the element has a form owner, the element
must submit the form
owner from the button element.
- Reset Button
If the element has a form owner, the element
must reset the form
owner.
- Button
Do nothing.
The form attribute is used to
explicitly associate the button element with its
form owner. The name
attribute represents the element's name. The disabled attribute is used to make
the control non-interactive and to prevent its value from being
submitted. The autofocus
attribute controls focus. The action, enctype, method, novalidate, and target attributes are attributes
for form submission.
The value
attribute gives the element's value for the purposes of form
submission. The value
attribute must not be present unless the form attribute is present. The
element's value is the value
of the element's value
attribute, if there is one, or the empty string otherwise.
The value and
type DOM attributes
must reflect the respective content attributes of the
same name.
The willValidate, validity, and validationMessage
attributes, and the checkValidity() and setCustomValidity()
methods, are part of the constraint validation API. The
labels attribute provides a list
of the element's labels.
4.10.6 The select element4.10.6 select 要素
- Categories分類
- Phrasing content.語句付け内容。
- Interactive content.対話的内容。
- Listed, labelable, submittable, and resettable form-associated element.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Zero or more
option or optgroup elements.
- Element-specific attributes:要素固有属性:
autofocusdisabledformmultiplenamesize- DOM interface:DOM 界面:
-
interface HTMLSelectElement : HTMLElement {
attribute boolean autofocus;
attribute boolean disabled;
readonly attribute HTMLFormElement form;
attribute boolean multiple;
attribute DOMString name;
attribute boolean size;
readonly attribute DOMString type;
readonly attribute HTMLOptionsCollection options;
attribute unsigned long length;
[IndexGetter] HTMLElement XXX9(in unsigned long index);
void add(in HTMLElement element, in HTMLElement before);
void add(in HTMLElement element, in long before);
void remove(in long index);
readonly attribute HTMLCollection selectedOptions;
attribute long selectedIndex;
attribute DOMString value;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
void setCustomValidity(in DOMString error);
readonly attribute NodeList labels;
};
The select element represents a control for
selecting amongst a set of options.
The multiple
attribute is a boolean attribute. If the attribute is
present, then the select element represents a control
for selecting zero or more options from the list of options. If the
attribute is absent, then the select element represents
a control for selecting a single option from the list of options.
The list of options
for a select element consists of all the
option element children of the select
element, and all the option element children of all the
optgroup element children of the select
element, in tree order.
The size
attribute gives the number of options to show to the user. The size attribute, if specified, must
have a value that is a valid non-negative integer
greater than zero. If the multiple attribute is present,
then the size attribute's
default value is 4. If the multiple attribute is absent,
then the size attribute's
default value is 1.
If the multiple
attribute is absent, and the element is not disabled, then the user agent
should allow the user to pick an option element in its
list of options that
is itself not disabled. Upon this
option element being picked (either through a click, or
through unfocusing the element after changing its value, or through
a menu command, or through any
other mechanism), and before the relevant user interaction event is
queued (e.g. before the click
event), the user agent must set the selectedness of the
picked option element to true and then queue a
task to fire a simple event called change at the select
element, using the user interaction task source as the
task source, then broadcast formchange events at the
element's form owner.
If the multiple
attribute is absent, whenever an option element in the
select element's list of options has its
selectedness set to
true, and whenever an option element with its selectedness set to true
is added to the select element's list of options, the user
agent must set the selectedness of all the
other option element in its list of options to
false.
If the multiple
attribute is absent, whenever there are no option
elements in the select element's list of options that have
their selectedness
set to true, the user agent must set the selectedness of the first
option element in the list of options in
tree order that is not disabled, if any, to
true.
If the multiple
attribute is present, and the element is not disabled, then the user agent
should allow the user to toggle the selectedness of the
option elements in its list of options that are
themselves not disabled
(either through a click, or through a menu command, or any other
mechanism). Upon the selectedness of one or
more option elements being changed by the user, and
before the relevant user interaction event is queued (e.g. before a
related click event), the user
agent must queue a task to fire a simple
event called change at the
select element, using the user interaction task
source as the task source, then broadcast formchange events at the
element's form owner.
The reset
algorithm for select elements is to go through
all the option elements in the element's list of options, and set
their selectedness
to true if the option element has a selected attribute, and false
otherwise.
The form attribute is used to
explicitly associate the select element with its
form owner. The name
attribute represents the element's name. The disabled attribute is used to make
the control non-interactive and to prevent its value from being
submitted. The autofocus
attribute controls focus.
The type DOM
attribute, on getting, must return the string "select-one" if the multiple attribute is absent,
and the string "select-multiple" if the multiple attribute is
present.
The options
DOM attribute must return an HTMLOptionsCollection
rooted at the select node, whose filter matches the
elements in the list of
options.options
DOM 属性は、
select
節点を根とし、濾過器が選択肢のリスト中の要素にだけ一致する
HTMLOptionsCollection
を返さなければなりません。
The length DOM
attribute, on getting and setting, must act like the length attribute on
the HTMLOptionsCollection object returned by the options attribute. Similarly, the
add() and remove() methods must
act like their namesake methods on that same
HTMLOptionsCollection object.
The selectedOptions
DOM attribute must return an HTMLCollection rooted at
the select node, whose filter matches the elements in
the list of options
that have their selectedness set to
true.
The selectedIndex
DOM attribute, on getting, must return the index of the first
option element in the list of options in
tree order that has its selectedness set to true,
if any. If there isn't one, then it must return -1.
On setting, the selectedIndex attribute must
set the selectedness of all the
option elements in the list of options to false,
and then the option element in the list of options whose
index is the given new
value, if any, must have its selectedness set to
true.
The value DOM
attribute, on getting, must return the value of the first
option element in the list of options in
tree order that has its selectedness set to true,
if any. If there isn't one, then it must return the empty
string.
On setting, the value
attribute must set the selectedness of all the
option elements in the list of options to false,
and then first the option element in the list of options, in
tree order, whose value is equal to the given new
value, if any, must have its selectedness set to
true.
The multiple
and size DOM
attributes must reflect the respective content
attributes of the same name. The size DOM attribute limited to
only positive non-zero numbers.
The willValidate, validity, and validationMessage
attributes, and the checkValidity() and setCustomValidity()
methods, are part of the constraint validation API. The
labels attribute provides a list
of the element's labels.
4.10.7 The datalist element4.10.7 datalist 要素
- Categories分類
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Either: phrasing content.語句付け内容。
- Or: Zero or more
option elements.または、零個以上の option 要素。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
-
interface HTMLDataListElement : HTMLElement {
readonly attribute HTMLCollection options;
};
The datalist element represents a set of
option elements that represent predefined options for
other controls. The contents of the element represents fallback
content for legacy user agents, intermixed with option
elements that represent the predefined options. In the rendering,
the datalist element represents nothing and it, along
with its children, should be hidden.datalist 要素は、
他の制御子の定義済み選択肢を表します。要素の内容は、遺物利用者エージェントのための後退内容と、定義済み選択肢を表す option 要素とが混在したものを表します。
レンダリングでは、 datalist 要素は何も表さず、要素とその子供は隠されるべきです。
The datalist element is hooked up to an
input element using the list attribute on the
input element.datalist 要素は、
input 要素の
list
属性を使って input
要素に引っ掛けます。
The options
DOM attribute must return an HTMLCollection rooted at
the datalist node, whose filter matches
option elements.options
DOM 属性は、 datalist
節点を根とし、濾過器が option
要素に一致する HTMLCollection
を返さなければなりません。
Constraint validation: If an element has a
datalist element ancestor, it is barred from
constraint validation.制約検証: ある要素が datalist 要素の祖先を持つ場合、その要素は制約検証から除外されます。
4.10.8 The optgroup element4.10.8 optgroup 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
select element.select 要素の子供として。
- Content model:内容モデル:
- Zero or more
option elements.零個以上の option 要素。
- Element-specific attributes:要素固有属性:
disabledlabel- DOM interface:DOM 界面:
-
interface HTMLOptGroupElement : HTMLElement {
attribute boolean disabled;
attribute DOMString label;
};
The optgroup element represents a group of
option elements with a common label.
The element's group of option elements consists of
the option elements that are children of the
optgroup element.
When showing option elements in select
elements, user agents should show the option elements
of such groups as being related to each other and separate from
other option elements.
The disabled attribute
is a boolean attribute and can be used to disable a group of
option elements together.
The label
attribute must be specified. Its value gives the name of the group,
for the purposes of the user interface. User agents should use this
attribute's value when labelling the group of option
elements in a select element.
The disabled and label attributes must
reflect the respective content attributes of the same
name.
4.10.9 The option element4.10.9 option 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As a child of a
select element.select 要素の子供として。
- As a child of a
datalist element.datalist 要素の子供として。
- As a child of an
optgroup element.
- Content model:内容モデル:
- Text.テキスト。
- Element-specific attributes:要素固有属性:
disabledlabelselectedvalue- DOM interface:DOM 界面:
-
[NamedConstructor=Option(),
NamedConstructor=Option(in DOMString text),
NamedConstructor=Option(in DOMString text, in DOMString value),
NamedConstructor=Option(in DOMString text, in DOMString value, in boolean defaultSelected),
NamedConstructor=Option(in DOMString text, in DOMString value, in boolean defaultSelected, in boolean selected)]
interface HTMLOptionElement : HTMLElement {
attribute boolean disabled;
readonly attribute HTMLFormElement form;
attribute DOMString label;
attribute boolean defaultSelected;
attribute boolean selected;
attribute DOMString value;
readonly attribute DOMString text;
readonly attribute long index;
};
The option element represents an option in a
select element or as part of a list of suggestions in a
datalist element.
The disabled
attribute is a boolean attribute. An
option element is disabled if its disabled attribute is present or
if it is a child of an optgroup element whose disabled attribute is
present.
An option element that is disabled must prevent any click events that are queued on the user interaction task
source from being dispatched on the element.
The label
attribute provides a label for element. The label of an option
element is the value of the label attribute, if there is one,
or the textContent of the element, if there isn't.
The value
attribute provides a value for element. The value of an option
element is the value of the value attribute, if there is one,
or the textContent of the element, if there isn't.
The selected
attribute represents the default selectedness of the
element.
The selectedness
of an option element is a boolean state, initially
false. If the element is disabled, then the element's
selectedness is
always false and cannot be set to true. Unless othewise specified,
when the element is created, its selectedness must be set
to true if the element has a selected attribute. Whenever an
option element's selected attribute is added, its
selectedness must
be set to true.
The Option()
constructor with two or more arguments overrides the initial state
of the selectedness
state to always be false even if the third argument is true
(implying that a selected
attribute is to be set).
An option element's index is the number of
option element that are in the same list of options but that
come before it in tree order. If the
option element is not in a list of options, then the
option element's index is zero.
The disabled,
label, and value DOM attributes
must reflect the respective content attributes of the
same name. The defaultSelected
DOM attribute must reflect the selected content attribute.disabled、 label、
value
各 DOM 属性は同じ名前の各内容属性を反映しなければなりません。
defaultSelected
DOM 属性は selected
内容属性を反映しなければなりません。
The selected
DOM attribute must return true if the element's selectedness is true, and
false otherwise.
The index DOM
attribute must return the element's index.
The text DOM
attribute must return the same value as the textContent
DOM attribute on the element.
The form DOM
attribute's behavior depends on whether the option
element is in a select element or not. If the
option has a select element as its parent,
or has a colgroup element as its parent and that
colgroup element has a select element as
its parent, then the form DOM
attribute must return the same value as the form DOM attribute on that
select element. Otherwise, it must return null.
Several constructors are provided for creating
HTMLOptionElement objects (in addition to the factory
methods from DOM Core such as createElement()): Option(), Option(text), Option(text, value), Option(text, value, defaultSelected), and Option(text, value, defaultSelected, selected). When invoked as constructors,
these must return a new HTMLOptionElement object (a new
option element). If the text
argument is present, the new object must have a text node with the
value of that argument as its data as its only child. If the value argument is present, the new object must have a
value attribute set with the
value of the argument as its value. If the defaultSelected argument is present and true, the new
object must have a selected attribute set with no
value. If the selected argument is present and
true, the new object must have its selectedness set to true;
otherwise the fouth argument is absent or false, and the selectedness must be set
to false, even if the defaultSelected argument
is present and true.
4.10.10 The textarea element4.10.10 textarea 要素
- Categories分類
- Phrasing content.語句付け内容。
- Interactive content.対話的内容。
- Listed, labelable, submittable, and resettable form-associated element.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Text.テキスト。
- Element-specific attributes:要素固有属性:
autofocuscolsdisabledformmaxlengthnamereadonlyrequiredrowswrap- DOM interface:DOM 界面:
-
interface HTMLTextAreaElement : HTMLElement {
attribute boolean autofocus;
attribute unsigned long cols;
attribute boolean disabled;
readonly attribute HTMLFormElement form;
attribute long maxLength;
attribute DOMString name;
attribute boolean readOnly;
attribute boolean required;
attribute unsigned long rows;
attribute DOMString wrap;
readonly attribute DOMString type;
attribute DOMString defaultValue;
attribute DOMString value;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
void setCustomValidity(in DOMString error);
readonly attribute NodeList labels;
};
The textarea element represents a multiline plain
text edit control for the element's raw value. The contents of
the control represent the control's default value.
The raw value of
a textarea control must be initially the empty
string.
The readonly attribute
is a boolean attribute used to control whether the text
can be edited by the user or not.
Constraint validation: If the readonly attribute is
specified on a textarea element, the element is
barred from constraint validation.
A textarea element is mutable if it is neither
disabled nor has a readonly attribute
specified.
When a textarea is mutable, its raw value should be
editable by the user.
A textarea element has a dirty value flag, which must be
initially set to false, and must be set to true whenever the user
interacts with the control in a way that changes the raw value.
When the textarea element's textContent
DOM attribute changes value, if the element's dirty value flag is false,
then the element's raw
value must be set to the value of the element's
textContent DOM attribute.
The reset
algorithm for textarea elements is to set the
element's value to
the value of the element's textContent DOM
attribute.
The cols
attribute specifies the expected maximum number of characters per
line. If the cols attribute
is specified, its value must be a valid non-negative
integer greater than zero. If applying the rules for
parsing non-negative integers to the attribute's value
results in a number greater than zero, then the element's character width is that value;
otherwise, it is 20.
The user agent may use the textarea element's character width as a hint to
the user as to how many characters the server prefers per line
(e.g. for visual user agents by making the width of the control be
that many characters). In visual renderings, the user agent should
wrap the user's input in the rendering so that each line is no wider
than this number of characters.
The rows
attribute specifies the number of lines to show. If the rows attribute is specified, its
value must be a valid non-negative integer greater than
zero. If applying the rules for parsing non-negative
integers to the attribute's value results in a number greater
than zero, then the element's character height is that
value; otherwise, it is 2.
Visual user agents should set the height of the control to the
number of lines given by character height.
The wrap
attribute is an enumerated attribute with two keywords
and states: the soft keyword
which maps to the Soft state, and the the
hard keyword
which maps to the Hard state. The
missing value default is the Soft state.
If the element's wrap
attribute is in the Hard state, the cols attribute must be
specified.
The element's value is
defined to be the element's raw value with the
following transformation applied:
Replace every occurance of a U+000D CARRIAGE RETURN (CR)
character not followed by a U+000A LINE FEED (LF) character, and
every occurance of a U+000A LINE FEED (LF) character not proceeded
by a U+000D CARRIAGE RETURN (CR) character, by a two-character
string consisting of a U+000D CARRIAGE RETURN - U+000A LINE FEED
(CRLF) character pair.
If the element's wrap attribute is in the Hard state, insert
U+000D CARRIAGE RETURN - U+000A LINE FEED (CRLF) character pairs
into the string using a UA-defined algorithm so that each line so
that each line has no more than character width
characters. The the purposes of this requirement, lines are
delimited by the start of the string, the end of the string, and
U+000D CARRIAGE RETURN - U+000A LINE FEED (CRLF) character
pairs.
The maxlength
attribute is a form control maxlength attribute controlled by the
textarea element's dirty value flag.
If the textarea element has a maximum allowed
value length, then the element's children must be such that
the codepoint length of the value of the element's
textContent DOM attribute is equal to or less than the
element's maximum allowed value length.
The required attribute
is a boolean attribute.
Constraint validation: If the element has its
required attribute
specified, and the element is mutable, and the element's
value is the empty string,
then the element is suffering from being missing.
The form attribute is used to
explicitly associate the textarea element with its
form owner. The name
attribute represents the element's name. The disabled attribute is used to make
the control non-interactive and to prevent its value from being
submitted. The autofocus
attribute controls focus.
The cols, required, rows, and wrap attributes must
reflect the respective content attributes of the same
name. The cols and rows attributes are limited
to only positive non-zero numbers. The maxLength DOM
attribute must reflect the maxlength content attribute.
The readOnly
DOM attribute must reflect the readonly content
attribute.cols, required, rows, and wrap attributes must reflect the respective content attributes of the same name. The cols and rows attributes are limited to only positive non-zero numbers. The maxLength DOM attribute must reflect the maxlength content attribute. The readOnly DOM 属性は readonly 内容属性を反映しなければなりません。
The type DOM
attribute must return the value "textarea".
The defaultValue
DOM attribute must act like the element's textContent
DOM attribute.
The value
attribute must, on getting, return the element's raw value; on setting, it
must set the element's raw
value to the new value.
The willValidate, validity, and validationMessage
attributes, and the checkValidity() and setCustomValidity()
methods, are part of the constraint validation API. The
labels attribute provides a list
of the element's labels.
4.10.11 The output element4.10.11 output 要素
- Categories分類
- Phrasing content.語句付け内容。
- Listed and resettable form-associated element.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
forformname- DOM interface:DOM 界面:
-
interface HTMLOutputElement : HTMLElement {
attribute DOMString htmlFor;
readonly attribute HTMLFormElement form;
attribute DOMString name;
readonly attribute DOMString type;
attribute DOMString defaultValue;
attribute DOMString value;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
void setCustomValidity(in DOMString error);
};
The output element represents the result of a
calculation.
The for content
attribute allows an explicit relationship to be made between the
result of a calculation and the elements that represent the values
that went into the calculation or that otherwise influenced the
calculation. The for attribute,
if specified, must contain a string consisting of an unordered
set of unique space-separated tokens, each of which must have
the value of an ID of an element in the same
Document.
The form attribute is used to
explicitly associate the output element with its
form owner. The name
attribute represents the element's name.
The element has a value mode
flag which is either value or default. Initially the value mode flag must be set to default.
When the to value mode
flag is in mode default, the contents of the
element represent both the value of the element and its default
value. When the value mode
flag is in mode value, the contents of the
element represent the value of the element only, and the default
value is only accessible using the defaultValue DOM
attribute.
The element also has a default value. Initially,
the default value
must be the empty string.
Whenever the element's descendants are changed in any way, if the
value mode flag is in mode
default, the element's
default value must
be set to the value of the element's textContent DOM
attribute.
The reset
algorithm for textarea elements is to set the
element's textContent DOM attribute to the value of the
element's defaultValue
DOM attribute (thus replacing the element's child nodes), and then
to set the element's value mode
flag to default.
The value DOM
attribute must act like the element's textContent DOM
attribute, except that on setting, in addition, before the child
nodes are changed, the element's value mode flag must be set to value.
The defaultValue DOM
attribute, on getting, must return the element's default value. On
setting, the attribute must set the element's default value, and, if
the element's value mode
flag is in the mode default, set the element's
textContent DOM attribute as well.
The type
attribute must return the string "output".
The htmlFor
DOM attribute must reflect the for content attribute.htmlFor DOM 属性は for 内容属性を反映しなければなりません。
The willValidate,
validity, and validationMessage
attributes, and the checkValidity() and
setCustomValidity()
methods, are part of the constraint validation API.
Constraint validation: output
elements are always barred from constraint
validation.
A form-associated element can have a relationship
with a form element, which is called the element's
form owner. If a form-associated element is
not associated with a form element, its form
owner is said to be null.
A form-associated element is, by default, associated
with its nearest ancestor form element (as described
below), but may have a form attribute specified to
override this.
If a form-associated element has a form attribute specified, then its
value must be the ID of a form element in the element's
owner Document.
When a form-associated element is created, its
form owner must be initialized to null (no owner).
When a form-associated element is to be associated with a form, its
form owner must be set to that form.
When a form-associated element's ancestor chain
changes, e.g. because it or one of its ancestors was inserted or
removed from a Document, then the user agent
must reset the form owner of that element.
When a form-associated element's form attribute is added, removed, or
has its value changed, then the user agent must reset the form
owner of that element.
When a form-associated element has a form attribute and the ID of any of the
form elements in the Document changes,
then the user agent must reset the form owner of that
form-associated element.
When the user agent is to reset the form owner of a
form-associated element, it must run the following
steps:
If the element's form owner is not null, and
the element's form content
attribute is not present, and the element's form owner
is one of the ancestors of the element after the change to the
ancestor chain, then do nothing, and abort these steps.
Let the element's form owner be null.
-
If the element has a form
content attribute, then run these substeps:
If the first element in the Document to have
an ID that is equal to the element's form content attribute's value is a
form element, then associate the
form-associated element with that form
element.
Abort the "reset the form owner" steps.
Otherwise, if the form-associated element in
question has an ancestor form element, then associate the
form-associated element with the nearest such ancestor
form element.
Otherwise, the element is left unassociated.
Form-associated
elements have a form DOM attribute, which,
on getting, must return the element's form owner, or
null if there isn't one.
Constraint validation: If an element has no
form owner, it is barred from constraint
validation.
The name content
attribute gives the name of the form control, as used in form
submission and in the form element's elements object. If the attribute
is specified, its value must not be the empty string.
Constraint validation: If an element does not
have a name attribute specified,
or its name attribute's value is
the empty string, then it is barred from constraint
validation.
The name DOM
attribute must reflect the name content attribute.name DOM 属性は name 内容属性を反映しなければなりません。
The disabled
content attribute is a boolean attribute.
A form control is disabled
if its disabled attribute is
set, or if it is a descendant of a fieldset element
whose disabled attribute
is set.
A form control that is disabled must prevent any click events that are queued on the user interaction task
source from being dispatched on the element.
Constraint validation: If an element is disabled, it is barred from
constraint validation.
The disabled DOM
attribute must reflect the disabled content attribute.disabled DOM 属性は disabled 内容属性を反映しなければなりません。
Form controls have a value
and a checkedness. (The latter
is only used by input elements.) These are used to
describe how the user interacts with the control.
The autofocus
content attribute allows the user to indicate that a control is to
be focused as soon as the page is loaded, allowing the user to just
start typing without having to manually focus the main control.
The autofocus attribute is
a boolean attribute.
There must not be more than one element in the document with the
autofocus attribute
specified.
Whenever an element with the autofocus attribute specified is
inserted into a
document, the user agent should queue a task
that checks to see if the element is focusable, and if
so, runs the focusing steps for that element. User
agents may also change the scrolling position of the document, or
perform some other action that brings the element to the user's
attention. The task source for this task is the
DOM manipulation task source.
User agents may ignore this attribute if the user has indicated
(for example, by starting to type in a form control) that he does
not wish focus to be changed.
Focusing the control does not imply that the user
agent must focus the browser window if it has lost focus.
The autofocus
DOM attribute must reflect the content attribute of the
same name.
In the following snippet, the text control would be focused when
the document was loaded.
<input maxlength="256" name="q" value="" autofocus>
<input type="submit" value="Search">
A form control maxlength attribute, controlled by a dirty value flag declares a limit on the number of
characters a user can input.
If an element has its form
control maxlength attribute specified,
the attribute's value must be a valid non-negative
integer. If the attribute is specified and applying the
rules for parsing non-negative integers to its value
results in a number, then that number is the element's maximum
allowed value length. If the attribute is omitted or parsing
its value results in an error, then there is no maximum
allowed value length.
Constraint validation: If an element has a
maximum allowed value length, and its dirty value flag is false, and the codepoint
length of the element's value is greater than the element's
maximum allowed value length, then the element is
suffering from being too long.
User agents may prevent the user from causing the element's value to be set to a value whose
codepoint length is greater than the element's
maximum allowed value length.
Attributes for form submission can be specified both on
form elements and on elements that represent buttons
that submit forms, e.g. an input element whose type attribute is in the Submit Button state. The
attributes on the buttons, when omitted, default to the values given
on the corresponding the form element.
The action content
attribute, if specified, must have a value that is a valid
URL.
The action of an element is
the value of the element's action attribute, if it has one, or
the value of its form owner's action attribute, if it has
one, or else the empty string.
The method content
attribute is an enumerated attribute with the following
keywords and states:
The keyword GET, mapping
to the state GET, indicating
the HTTP GET method.
The keyword POST, mapping
to the state POST, indicating
the HTTP POST method.
The keyword PUT, mapping
to the state PUT, indicating
the HTTP PUT method.
The keyword DELETE, mapping
to the state DELETE, indicating
the HTTP DELETE method.
The missing value default is the GET state.
The method of an element is
one of those four states. If the element has a method attribute, then the element's
method is that attribute's
state; otherwise, it is the form owner's method attribute's state.
The enctype
content attribute is an enumerated attribute with the
following keywords and states:
The "application/x-www-form-urlencoded" keyword and corresponding state.
The "multpart/form-data" keyword and corresponding state.
The "text/plain" keyword and corresponding state.
The missing value default is the application/x-www-form-urlencoded
state.
The enctype of an element is
one of those four states. If the element has a enctype attribute, then the element's
enctype is that attribute's
state; otherwise, it is the form owner's enctype attribute's state.
The target content
attribute, if present, must be a valid browsing context name
or keyword.
The target of an element is
the value of the element's target attribute, if it has one; or
the value of its form owner's target attribute, if it has
one; or, if one of the child nodes of the head
element is a base element with a target attribute, then the the value
of the target attribute of the
first such base element; or, if there is no such
element, the empty string.
The novalidate
content attribute is a boolean attribute. If present,
it indicates that the form is not to be validated during
submission.
The no-validate state of
an element is true if the element's novalidate attribute is present or
if the element's form owner's novalidate attribute is present,
and false otherwise.
The action, method, enctype, and target DOM attributes must
reflect the respective content attributes of the same
name. The noValidate DOM
attribute must reflect the novalidate content attribute.
4.10.14 Constraints4.10.14 制約
4.10.14.1 Definitions4.10.14.1 定義
A listed form-associated
element is a candidate for constraint validation
unless a condition has barred the element from constraint
validation. (For example, an element is barred from
constraint validation if it is an output or
fieldset element.)
An element can have a custom validity error message
defined. Initially, an element must have its custom validity
error message set to the empty string. When its value is not
the empty string, the element is suffering from a custom
error. It can be set using the setCustomValidity()
method. The user agent should use the custom validity error
message when alerting the user to the problem with the
control.
An element can be constrained in various ways. The following is
the list of validity states that a form control can be
in, making the control invalid for the purposes of constraint
validation. (The definitions below are non-normative; other parts of
this specification define more precisely when each state applies or
does not.)
- Suffering from being missing
-
When a control has no value but has a required attribute (input required, textarea
required).
- Suffering from a type mismatch
-
When a control that allows arbitrary user input has a value that is not in the correct
syntax (E-mail, URL).
- Suffering from a pattern mismatch
-
When a control has a value that doesn't satisfy the
pattern attribute.
- Suffering from being too long
-
When a control has a value that is too long for the
form control maxlength attribute (input
maxlength,
textarea maxlength).
- Suffering from an underflow
-
When a control has a value that is too low for the min attribute.
- Suffering from an overflow
-
When a control has a value that is too high for the
max attribute.
- Suffering from a step mismatch
-
When a control has a value that doesn't fit the rules
given by the step
attribute.
- Suffering from a custom error
-
When a control's custom validity error message
(as set by the element's setCustomValidity()
method) is not the empty string.
An element can still suffer from these states even
when the element is disabled; thus these states can
be represented in the DOM even if validating the form during
submission wouldn't indicate a problem to the user.
An element satisfies its
constraints if it is not suffering from any of the above
validity states.
4.10.14.2 Constraint validation
When the user agent is required to statically validate the
constraints of form element form, it must run the following steps, which return
either a positive result (all the controls in the form are
valid) or a negative result (there are invalid controls)
along with a (possibly empty) list of elements that are invalid and
for which no script has claimed responsibility:
Let controls be a list of all the submittable elements whose
form owner is form, in tree
order.
Let invalid controls be an initially
empty list of elements.
-
For each element field in controls, in tree order, run the
following substeps:
If field is not a candidate for
constraint validation, then move on to the next
element.
Otherwise, if field satisfies its constaints, then
move on to the next element.
Otherwise, add field to invalid controls.
If invalid controls is empty, then
return a positive result and abort these steps.
Let unhandled invalid controls be an
initially empty list of elements.
-
For each element field in invalid controls, if any, in tree
order, run the following substeps:
Fire a simple event named invalid at field.
If the event was not canceled, then add field to unhandled invalid
controls.
Return a negative result with the list of elements in
the unhandled invalid controls list.
If a user agent is to interactively validate the
constraints of form element form, then the user agent must run the following
steps:
Statically validate the constraints of form, and let unhandled invalid
controls be the list of elements returned if the result was
negative.
If the result was positive, then return that result
and abort these steps.
Report the problems with the constraints of at least one of
the elements given in unhandled invalid
controls to the user. User agents may focus one of those
elements in the process, by running the focusing steps
for that element, and may change the scrolling position of the
document, or perform some other action that brings the element to
the user's attention. User agents may report more than one
constraint violation. User agents may coalesce related constraint
violation reports if appropriate (e.g. if multiple radio buttons in
a group are marked as
required, only one error need be reported). If one of the controls
is not visible to the user (e.g. it has the hidden attribute set) then user agents
may report a script error.
Return a negative result.
4.10.14.3 The constraint validation API4.10.14.3 制約検証 API
The willValidate
attribute must return true if an element is a candidate for
constraint validation, and false otherwise (i.e. false if any
conditions are barring it from constraint validation).
The setCustomValidity(message), when invoked, must set the
custom validity error message to the value of the given
message argument.
The validity
attribute must return a ValidityState object that
represents the validity states of the element. This
object is live, and the same object must be returned each time the
element's validity attribute
is retrieved.
interface ValidityState {
readonly attribute boolean valueMissing;
readonly attribute boolean typeMismatch;
readonly attribute boolean patternMismatch;
readonly attribute boolean tooLong;
readonly attribute boolean rangeUnderflow;
readonly attribute boolean rangeOverflow;
readonly attribute boolean stepMismatch;
readonly attribute boolean customError;
readonly attribute boolean valid;
};
A ValidityState object has the following
attributes. On getting, they must return true if the corresponding
condition given in the following list is true, and false
otherwise.
valueMissing-
The control is suffering from being missing.
typeMismatch-
The control is suffering from a type mismatch.
patternMismatch-
The control is suffering from a pattern mismatch.
tooLong-
The control is suffering from being too long.
rangeUnderflow-
The control is suffering from an underflow.
rangeOverflow-
The control is suffering from an overflow.
stepMismatch-
The control is suffering from a step mismatch.
customError-
The control is suffering from a custom error.
valid-
None of the other conditions are true.
When the checkValidity()
method is invoked, if the element is a candidate for
constraint validation and does not satisfy its constaints, the user
agent must fire a simple event named invalid at the element and return
false. Otherwise, it must only return true without doing anything
else.
The validationMessage
attribute must return the empty string if the element is not a
candidate for constraint validation or if it is one but
it satisfies its constaints;
otherwise, it must return a suitably localised message that the user
agent would show the user if this were the only form with a validity
constraint problem. If the element is suffering from a custom
error, then the custom validity error message
should be present in the return value.
4.10.14.4 Security4.10.14.4 保安性
Servers should not rely on client-side validation. Client-side
validation can be intentionally bypassed by hostile users, and
unintentionally bypassed by users of older user agents or automated
tools that do not implement these features. The constraint
validation features are only intended to improve the user
experience, not to provide any kind of security mechanism.
4.10.15.1 Implicit submission
User agents may establish a button in each form as being the
form's default button. This should be the first submit button in tree
order whose form owner is that form
element, but user agents may pick another button if another would be
more appropriate for the platform. If the platform supports letting
the user submit a form implicitly (for example, on some platforms
hitting the "enter" key while a text field is focused implicitly
submits the form), then doing so must cause the form's default
button's activation behavior, if any, to be
run.
Consequently, if the default button is
disabled, the form is not
submitted when such an implicit submission mechanism is used. (A
button has no activation behavior when disabled.)
If the form has no submit
button, then the implicit submission mechanism must just
submit the
form element from the form element
itself.
When a form form is submitted from an element submitter (typically a button), the user agent must
run the following steps:
If form is in
a Document that has no associated browsing
context or whose browsing context has its
sandboxed forms browsing context flag set, then abort
these steps without doing anything.
If form is already being submitted
(i.e. the form was submitted again while processing
the events fired from the next two steps, probably from a script
redundantly calling the submit() method on form), then abort these steps. This doesn't affect
the earlier instance of this algorithm.
If the submitter is anything but a
form element, and the submitter
element's no-validate
state is false, then interactively validate the
constraints of form and examine the
result: if the result is negative (the constraint validation
concluded that there were invalid fields and probably informed the
user of this) then abort these steps.
If the submitter is anything but a
form element, then fire a simple event
that bubbles, named submit, at form. If
the event's default action is prevented (i.e. if the event is
canceled) then abort these steps. Otherwise, continue (effectively
the default action is to perform the submission).
Let controls be a list of all the submittable elements whose
form owner is form, in tree
order.
Let the form data set be a list of
name-value-type tuples, initially empty.
-
Constructing the form data set. For each
element field in controls,
in tree order, run the following substeps:
-
If any of the following conditions are met, then skip these
substeps for this element:
The field element has a
datalist element ancestor.
The field element is disabled.
The field element is a button but it is not submitter.
The field element is an
input element whose type attribute is in the Checkbox state and
whose checkedness is
false.
The field element is an
input element whose type attribute is in the Radio Button state and
whose checkedness is
false.
The field element is an
input element whose type attribute is in the File Upload state but
the control does not have any files selected.
The field element is an
object element that is not using a
plugin.
Otherwise, process field as follows:
Let type be the value of the type DOM attribute of field.
-
If the field element is an
input element whose type attribute is in the Image Button state,
then run these further nested substeps:
If the field element has an name attribute specified and value
is not the empty string, let name be that
value followed by a single U+002E FULL STOP (.)
character. Otherwise, let name be the empty
string.
Let namex be the
string consisting of the concatenation of name and a single U+0078 LATIN SMALL LETTER X
(x) character.
Let namey be the
string consisting of the concatenation of name and a single U+0079 LATIN SMALL LETTER Y
(y) character.
The field element is submitter, and before this algorithm was invoked
the user indicated a
coordinate. Let x be the x-component of the coordindate selected by the
user, and let y be the y-component of the coordinate selected by the
user.
Append an entry in the form data set
with the name namex,
the value x, and the type type.
Append an entry in the form data set
with the name namey and
the value y, and the type type.
Skip the remaining substeps for this element: if there
are any more elements in controls, return
to the top of the constructing the form data
set step, otherwise, jump to the next step in the overall
form submission algorithm.
If the field element does not have a
name attribute specified, or
its name attribute's value is
the empty string, skip these substeps for this element: if there
are any more elements in controls, return to
the top of the constructing
the form data set step, otherwise, jump to the next step in
the overall form submission algorithm.
Let name be the value of the field element's name attribute.
If the field element is a
select element, then for each option
element in the select element whose selectedness is true,
append an entry in the form data set with the
name as the name, the value of the
option element as the value, and type as the type.
-
Otherwise, if the field element is an
input element whose type attribute is in the Checkbox state or the
Radio Button state,
then then run these further nested substeps:
If the field element has a value attribute specified, then
let value be the value of that attribute;
otherwise, let value be the string
"on".
Append an entry in the form data set
with name as the name, value as the value, and type
as the type.
Otherwise, if the field element is an
input element whose type attribute is in the File Upload state, then for
each file selected in the
input element, append an entry in the form data set with the name as
the name, the file (consisting of the name, the type, and the
body) as the value, and type as the
type.
Otherwise, if the field element is an
object element: try to obtain a form submission
value from the plugin,
and if that is successful, append an entry in the form data set with name as the
name, the returned form submission value as the value, and the
string "object" as the type.
Otherwise, append an entry in the form data
set with name as the name, the value of the field element as the value, and type as the type.
Let action be the submitter element's action.
-
If action is the empty string, let action be the document's address.
This step is a willful violation of RFC 3986. [RFC3986]
Resolve the
URL action. If this fails, abort
these steps.
Let scheme be the <scheme> of the resulting
absolute URL.
Let enctype be the submitter element's enctype.
Let method be the submitter element's method.
Let target be the submitter element's target.
-
Select the appropriate row in the table below based on the
value of scheme as given by the first cell of
each row. Then, select the appropriate cell on that row based on
the value of method as given in the first cell
of each column. Then, jump to the steps named in that cell and
defined below the table.
If scheme is not one of those listed in
this table, then the behavior is not defined by this
specification. User agents should, in the absence of another
specification defining this, act in a manner analogous to that
defined in this specification for similar schemes.
The behaviors are as follows:
- Mutate action
-
Let query be the result of encoding the
form data set using the application/x-www-form-urlencoded encoding
algorithm, interpreted as a US-ASCII string.
Let destination be a new URL
that is equal to the action except that its
<query> component is
replaced by query (adding a U+003F QUESTION
MARK (?) character if appropriate).
Let target browsing context be the
form submission target browsing context.
Navigate target browsing
context to destination. If target browsing context was newly created for
this purpose by the steps above, then it must be navigated with
replacement enabled.
- Submit as entity body
-
Let entity body be the result of encoding
the form data set using the
appropriate form encoding algorithm.
Let target browsing context be the
form submission target browsing context.
Let MIME type be determined as
follows:
- If enctype is
application/x-www-form-urlencoded
- Let MIME type be "
application/x-www-form-urlencoded".
- If enctype is
multpart/form-data
- Let MIME type be "
multipart/form-data".
- If enctype is
text/plain
- Let MIME type be "
text/plain".
Navigate target browsing
context to action using the HTTP
method given by method and with entity body as the entity body, of type MIME type. If target browsing
context was newly created for this purpose by the steps
above, then it must be navigated with replacement
enabled.
- Delete action
-
Let target browsing context be the
form submission target browsing context.
Navigate target browsing
context to action using the DELETE
method. If target browsing context was newly
created for this purpose by the steps above, then it must be
navigated with replacement enabled.
- Get action
-
Let target browsing context be the
form submission target browsing context.
Navigate target browsing
context to action. If target browsing context was newly created for
this purpose by the steps above, then it must be navigated with
replacement enabled.
- Post to data:
-
Let data be the result of encoding the
form data set using the appropriate
form encoding algorithm.
If action contains the string "%%%%" (four U+0025 PERCENT SIGN characters),
then %-escape all bytes in data that, if
interpreted as US-ASCII, do not match the unreserved production in the URI Generic Syntax,
and then, treating the result as a US-ASCII string, further
%-escape all the U+0025 PERCENT SIGN characters in the resulting
string and replace the first occurance of "%%%%" in action with the
resulting double-escaped string. [RFC3986]
Otherwise, if action contains the string
"%%" (two U+0025 PERCENT SIGN characters
in a row, but not four), then %-escape all characters in data that, if interpreted as US-ASCII, do not
match the unreserved production in the URI
Generic Syntax, and then, treating the result as a US-ASCII
string, replace the first occurance of "%%" in action with the
resulting escaped string. [RFC3986]
Let target browsing context be the
form submission target browsing context.
Navigate target browsing
context to the potentially modified action. If target browsing
context was newly created for this purpose by the steps
above, then it must be navigated with replacement
enabled.
- Put to data:
-
Let data be the result of encoding the
form data set using the appropriate
form encoding algorithm.
Let MIME type be determined as
follows:
- If enctype is
application/x-www-form-urlencoded
- Let MIME type be "
application/x-www-form-urlencoded".
- If enctype is
multpart/form-data
- Let MIME type be "
multipart/form-data".
- If enctype is
text/plain
- Let MIME type be "
text/plain".
Let destination be the result of
concatenating the following:
The string "data:".
The value of MIME type.
The string ";base64,".
A base-64 encoded representation of data. [RFC2045]
Let target browsing context be the
form submission target browsing context.
Navigate target browsing
context to destination. If target browsing context was newly created for
this purpose by the steps above, then it must be navigated with
replacement enabled.
-
-
Let headers be the resulting encoding the
form data set using the application/x-www-form-urlencoded encoding
algorithm, interpreted as a US-ASCII string.
Replace occurances of U+002B PLUS SIGN characters (+) in headers with the string "%20".
Let destination consist of all the
characters from the first character in action to the character immediately before the
first U+003F QUESTION MARK character (?), if any, or the end of
the string if there are none.
Append a single U+003F QUESTION MARK character (?) to destination.
Append headers to destination.
Let target browsing context be the
form submission target browsing context.
Navigate target browsing
context to destination. If target browsing context was newly created for
this purpose by the steps above, then it must be navigated with
replacement enabled.
- Mail as body
-
Let body be the resulting encoding the
form data set using the appropriate
form encoding algorithm and then %-escaping all the bytes
in the resulting byte string that, when interpreted as US-ASCII,
do not match the unreserved production in
the URI Generic Syntax. [RFC3986]
Let destination have the same value as
action.
If destination does not contain a U+003F
QUESTION MARK character (?), append a single U+003F QUESTION
MARK character (?) to destination. Otherwise, append a single U+0026
AMPERSAND character (&).
Append the string "body=" to destination.
Append body, interpreted as a US-ASCII
string, to destination.
Let target browsing context be the
form submission target browsing context.
Navigate target browsing
context to destination. If target browsing context was newly created for
this purpose by the steps above, then it must be navigated with
replacement enabled.
The form submission target browsing context is
obtained, when needed by the behaviors described above, as
follows: If the user indicated a specific browsing
context to use when submitting the form, then that is the
target browsing context. Otherwise, apply the rules for
choosing a browsing context given a browsing context name
using target as the name and the
browsing context of form as the
context in which the algorithm is executed; the resulting
browsing context is the target browsing context.
The appropriate form encoding algorithm is
determined as follows:
- If enctype is
application/x-www-form-urlencoded
- Use the
application/x-www-form-urlencoded encoding
algorithm.
- If enctype is
multpart/form-data
- Use the
multipart/form-data encoding
algorithm.
- If enctype is
text/plain
- Use the
text/plain encoding
algorithm.
The application/x-www-form-urlencoded encoding
algorithm is as follows:
Let result be the empty string.result を空文字列とします。
-
If the form element has an accept-charset attribute,
then, taking into account the characters found in the form data set's names and values, and the character
encodings supported by the user agent, select a character encoding
from the list given in the form's accept-charset attribute
that is an ASCII-compatible character encoding. If
none of the encodings are supported, then let the selected
character encoding be UTF-8.
Otherwise, if the document's character encoding is
an ASCII-compatible character encoding, then that is
the selected character encoding.
Otherwise, let the selected character encoding be UTF-8.
Let charset be the preferred MIME name
of the selected character encoding.
If the entry's name is "_charset_" and
its type is "hidden", replace its value with
charset.
If the entry's type is "file", replace
its value with the file's filename only.
-
For each entry in the form data set,
perform these substeps:
For each character in the entry's name and value that
cannot be expressed using the selected character encoding,
replace the character by a string consisting of a U+0026
AMPERSAND character (&), one of more characters in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9) representing the
Unicode codepoint of the character in base ten, and finally a
U+003B SEMICOLON character (;).
-
For each character in the entry's name and value, apply the
following subsubsteps:
If the character isn't in the range U+0020, U+002A,
U+002D, U+002E, U+0030 .. U+0039, U+0041 .. U+005A, U+005F,
U+0061 .. U+007A then replace the character with a string
formed as follows: Start with the empty string, and then,
taking each byte of the character when expressed in the
selected character encoding in turn, append to the string a
U+0025 PERCENT SIGN character (%) followed by two characters in
the ranges U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9) and
U+0041 LATIN CAPITAL LETTER A to U+005A LATIN CAPITAL LETTER Z
representing the hexadecimal value of the byte (zero-padded if
necessary).
If the character is a U+0020 SPACE character, replace it
with a single U+002B PLUS SIGN character (+).
If the entry's name is "isindex",
its type is "text", and this is the first
entry in the form data set, then append the
value to result and skip the rest of the
substeps for this entry, moving on to the next entry, if any, or
the next step in the overall algorithm otherwise.
If this is not the first entry, append a single U+0026
AMPERSAND character (&) to result.
Append the entry's name to result.
Append a single U+003D EQUALS SIGN character (=) to result.
Append the entry's value to result.
Encode result as US-ASCII and return the
resulting byte stream.
The multipart/form-data encoding
algorithm is to encode the form data set
using the rules described by RFC2388, Returning Values from
Forms: multipart/form-data, and return
the resulting byte stream. [RFC2388]
Each entry in the form data set is a
field, the name of the entry is the field name and the
value of the entry is the field value.
The order of parts must be the same as the order of fields in the
form data set. Multiple entries with the same
name must be treated as distinct fields.
4.10.15.5 Plain text form data
The text/plain encoding
algorithm is as follows:
Let result be the empty string.result を空文字列とします。
-
If the form element has an accept-charset attribute,
then, taking into account the characters found in the form data set's names and values, and the character
encodings supported by the user agent, select a character encoding
from the list given in the form's accept-charset
attribute. If none of the encodings are supported, then let the
selected character encoding be UTF-8.
Otherwise, the selected character encoding is the
document's character encoding.
Let charset be the preferred MIME name
of the selected character encoding.
If the entry's name is "_charset_" and
its type is "hidden", replace its value with
charset.
If the entry's type is "file", replace
its value with the file's filename only.
-
For each entry in the form data set,
perform these substeps:
Append the entry's name to result.
Append a single U+003D EQUALS SIGN character (=) to result.
Append the entry's value to result.
Append a U+000D CARRIAGE RETURN (CR) U+000A LINE FEED (LF)
character pair to result.
Encode result using the selected
character encoding and return the resulting byte stream.
When a form form is reset, the user agent must invoke
the reset algorithm
of each resettable elements
whose form owner is form, and must
then broadcast formchange events from form.
Each resettable element
defines its own reset
algorithm. Changes made to form controls as part of these
algorithms do not count as changes caused by the user (and thus,
e.g., do not cause input events to
fire).
4.10.17 Event dispatch4.10.17 事象の発送
When the user agent is to broadcast forminput events or
broadcast formchange
events from a form element form, it must run the following steps:利用者エージェントが form 要素 form から
forminput 事象を放送する時や
formchange
事象を放送する時は、次の段階群を走らせなければなりません。
Let controls be a list of all the resettable elements whose form
owner is form.controls を、
再設定可能要素であってフォーム所有者が form
であるものすべてのリストとします。
If the user agent was to broadcast forminput events, let event name be forminput. Otherwise the user agent
was to broadcast formchange events; let event name be formchange.利用者エージェントが
forminput 事象を放送する場合、
event name を forminput
とします。そうでない場合、利用者エージェントが
formchange 事象を放送する場合です。
event name を
formchange
とします。
For each element in controls, in
tree order, fire a simple event named
event name at the element.controls 中の各要素について、
木順に、その要素において
event name と名付けられた単純事象を発火します。
4.11 Interactive elements4.11 対話的要素
4.11.1 The details element4.11.1 details 要素
- Categories分類
- Flow content.流れ内容。
- Interactive content.対話的内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- One
legend element followed by flow content.legend 要素1つの後に流れ内容。
- Element-specific attributes:要素固有属性:
open- DOM interface:DOM 界面:
-
interface HTMLDetailsElement : HTMLElement {
attribute boolean open;
};
The details element represents additional
information or controls which the user can obtain on demand.details 要素は、
利用者が望んだ時に得られる追加の情報や制御子を表します。
The details element is not appropriate
for footnotes. Please see the section on
footnotes for details on how to mark up footnotes.details 要素は脚注には不適切です。
脚注のマークの付け方の詳細は脚注の節をご覧ください。
The first element child of a details element, if it
is a legend element, represents the summary of the
details.details 要素の最初の要素子は、
それが legend
要素である場合、詳細の要約を表します。
If the first element is not a legend element, the
UA should provide its own legend (e.g. "Details").最初の要素が legend
要素でない場合、利用者エージェントは自身で銘文 (例えば「詳細」) を用意するべきです。
The open
content attribute is a boolean attribute. If present,
it indicates that the details should be shown to the user. If the
attribute is absent, the details should not be shown.open 内容属性はブール型属性です。この属性が存在する場合、
詳細が利用者に示されるべきであることを示します。
この属性が存在しない場合、詳細は示されるべきではありません。
If the attribute is removed, then the details should be
hidden. If the attribute is added, the details should be shown.属性が削除された場合、詳細は隠されるべきです。
属性が追加された場合、詳細は示されるべきです。
The user agent should allow the user to request that the details
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 value open. To honour a request for the
details to be hidden, the user agent must remove the open attribute from the
element.利用者エージェントは利用者が詳細を示すか隠すか要求できるようにするべきです。
利用者エージェントは詳細を示すとの要求を受けると要素の open 属性を値 open
に設定しなければなりません。
利用者エージェントは詳細を隠すとの要求を受けると open 属性を削除しなければなりません。
The open
attribute must reflect the open content attribute.open
属性は open
内容属性を反映しなければなりません。
Rendering will be described in the Rendering
section in due course. Basically CSS :open and :closed match the
element, it's a block-level element by default, and when it matches
:closed it renders as if it had an XBL binding attached to it whose
template was just <template>▶<content
includes="legend:first-child">Details</content></template>,
and when it's :open it acts as if it had an XBL binding attached to
it whose template was just <template>▼<content
includes="legend:first-child">Details</content><content/></template>
or some such.
4.11.2 The datagrid element4.11.2 datagrid 要素
- Categories分類
- Flow content.流れ内容。
- Interactive content.対話的内容。
- Sectioning root.章節付け根。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Either: Nothing.
- Or: Flow content, but where the first element child node, if any, is not a
table, select, or datalist element.
- Or: A single
table element.
- Or: A single
select element.
- Or: A single
datalist element.
- Element-specific attributes:要素固有属性:
multipledisabled- DOM interface:DOM 界面:
-
interface HTMLDataGridElement : HTMLElement {
attribute DataGridDataProvider data;
readonly attribute DataGridSelection selection;
attribute boolean multiple;
attribute boolean disabled;
void updateEverything();
void updateRowsChanged(in RowSpecification row, in unsigned long count);
void updateRowsInserted(in RowSpecification row, in unsigned long count);
void updateRowsRemoved(in RowSpecification row, in unsigned long count);
void updateRowChanged(in RowSpecification row);
void updateColumnChanged(in unsigned long column);
void updateCellChanged(in RowSpecification row, in unsigned long column);
};
One possible thing to be added is a way to
detect when a row/selection has been deleted, activated, etc, by the
user (delete key, enter key, etc).
The datagrid element represents an interactive
representation of tree, list, or tabular data.datagrid 要素は木やリストや表のデータの対話的表現を表します。
The data being presented can come either from the content, as
elements given as children of the datagrid element, or
from a scripted data provider given by the data DOM attribute.
The multiple and
disabled attributes are
boolean attributes. Their
effects are described in the processing model sections below.
The multiple and disabled DOM
attributes must reflect the multiple and disabled content attributes
respectively.
4.11.2.1 The datagrid data model4.11.2.1 datagrid データ・モデル
This section is non-normative.この節は規定の一部ではありません。
In the datagrid data model, data is structured as a
set of rows representing a tree, each row being split into a number
of columns. The columns are always present in the data model,
although individual columns may be hidden in the presentation.
Each row can have child rows. Child rows may be hidden or
shown, by closing or opening (respectively) the parent row.
Rows are referred to by the path along the tree that one would
take to reach the row, using zero-based indices. Thus, the first row
of a list is row "0", the second row is row "1"; the first child row
of the first row is row "0,0", the second child row of the first row
is row "0,1"; the fourth child of the seventh child of the third
child of the tenth row is "9,2,6,3", etc.
The columns can have captions. Those captions are not considered
a row in their own right, they are obtained separately.
Selection of data in a datagrid operates at the row
level. If the multiple
attribute is present, multiple rows can be selected at once,
otherwise the user can only select one row at a time.
The datagrid element can be disabled entirely by
setting the disabled
attribute.
Columns, rows, and cells can each have specific flags, known as
classes, applied to them by the data provider. These classes affect the functionality of the
datagrid element, and are also passed to the style system. They are
similar in concept to the class
attribute, except that they are not specified on elements but are
given by scripted data providers.
4.11.2.2 How rows are identified4.11.2.2 行の識別の方法
The chains of numbers that give a row's path, or identifier, are
represented by objects that implement the
RowSpecification interface.行の経路や識別子を与える数の鎖は、
RowSpecification
界面を実装するオブジェクトにより表現されます。
[NoInterfaceObject] interface RowSpecification {
// binding-specific interface
};
In ECMAScript, two classes of objects are said to implement this
interface: Numbers representing non-negative integers, and
homogeneous arrays of Numbers representing non-negative
integers. Thus, [1,0,9] is a
RowSpecification, as is 1 on its
own. However, [1,0.2,9] is not a
RowSpecification object, since its second value is not
an integer.
User agents must always represent RowSpecifications
in ECMAScript by using arrays, even if the path only has one
number.
The root of the tree is represented by the empty path; in
ECMAScript, this is the empty array ([]). Only the
getRowCount() and
GetChildAtPosition()
methods ever get called with the empty path.
4.11.2.3 The data provider interface4.11.2.3 データ提供器界面
The conformance criteria in this section apply to any
implementation of the DataGridDataProvider, including
(and most commonly) the content author's implementation(s).
// To be implemented by Web authors as a JS object
[NoInterfaceObject] interface DataGridDataProvider {
void initialize(in HTMLDataGridElement datagrid);
unsigned long getRowCount(in RowSpecification row);
unsigned long getChildAtPosition(in RowSpecification parentRow, in unsigned long position);
unsigned long getColumnCount();
DOMString getCaptionText(in unsigned long column);
void getCaptionClasses(in unsigned long column, in DOMTokenList classes);
DOMString getRowImage(in RowSpecification row);
HTMLMenuElement getRowMenu(in RowSpecification row);
void getRowClasses(in RowSpecification row, in DOMTokenList classes);
DOMString getCellData(in RowSpecification row, in unsigned long column);
void getCellClasses(in RowSpecification row, in unsigned long column, in DOMTokenList classes);
void toggleColumnSortState(in unsigned long column);
void setCellCheckedState(in RowSpecification row, in unsigned long column, in long state);
void cycleCell(in RowSpecification row, in unsigned long column);
void editCell(in RowSpecification row, in unsigned long column, in DOMString data);
};
The DataGridDataProvider interface represents the
interface that objects must implement to be used as custom data
views for datagrid elements.
Not all the methods are required. The minimum number of methods
that must be implemented in a useful view is two: the getRowCount() and getCellData() methods.
Once the object is written, it must be hooked up to the
datagrid using the data DOM attribute.
The following methods may be usefully implemented:
initialize(datagrid)- Called by the
datagrid element (the one given by
the datagrid argument) after it has first
populated itself. This would typically be used to set the initial
selection of the datagrid element when it is first
loaded. The data provider could also use this method call to
register a select event handler
on the datagrid in order to monitor selection
changes.
getRowCount(row)- Must return the number of rows that are children of the
specified row, including rows that are
off-screen. If row is empty, then the number of
rows at the top level must be returned. If the value that this
method would return for a given row changes,
the relevant update methods on the
datagrid must be
called first. Otherwise, this method must always return the same
number. For a list (as opposed to a tree), this method must return
0 whenever it is called with a row identifier
that is not empty.
getChildAtPosition(parentRow, position)- Must return the index of the row that is a child of parentRow and that is to be positioned as the positionth row under parentRow
when rendering the children of parentRow. If
parentRow is empty, then position refers to the positionth row at the top level of the data
grid. May be omitted if the rows are always to be sorted in the
natural order. (The natural order is the one where the method
always returns position.) For a given parentRow, this method must never return the same
value for different values of position. The
returned value x must be in the range
0 ≤ x < n, where n is the value returned
by
getRowCount(parentRow).
getColumnCount()- Must return the number of columns currently in the data model
(including columns that might be hidden). May be omitted if there
is only one column. If the value that this method would return
changes, the
datagrid's updateEverything()
method must be called.
getCaptionText(column)- Must return the caption, or label, for column column. May be omitted if the columns have no
captions. If the value that this method would return changes, the
datagrid's updateColumnChanged()
method must be called with the appropriate column index.
getCaptionClasses(column, classes)- Must add the classes that apply to column column to the classes object.
May be omitted if the columns have no special classes. If the
classes that this method would add changes, the
datagrid's updateColumnChanged()
method must be called with the appropriate column index. Some
classes have predefined
meanings.
getRowImage(row)- Must return a URL giving the address of an image
that represents row row, or the empty string if
there is no applicable image. May be omitted if no rows have
associated images. If the value that this method would return
changes, the
datagrid's update methods must be called
to update the row in question.
- Must return an
HTMLMenuElement object that is to
be used as a context menu for row row, or null
if there is no particular context menu. May be omitted if none of
the rows have a special context menu. As this method is called
immediately before showing the menu in question, no precautions
need to be taken if the return value of this method changes.
getRowClasses(row, classes)- Must add the classes that apply to row row
to the classes object. May be omitted if the
rows have no special classes. If the classes that this method would
add changes, the
datagrid's update methods must be
called to update the row in question. Some classes have predefined meanings.
getCellData(row, column)- Must return the value of the cell on row row in column column. For text
cells, this must be the text to show for that cell. For progress bar cells,
this must be either a floating point number in the range 0.0 to 1.0
(converted to a string representation), indicating the
fraction of the progress bar to show as full (1.0 meaning
complete), or the empty string, indicating an indeterminate
progress bar. If the value that this method would return changes,
the
datagrid's update methods must be called to update
the rows that changed. If only one cell changed, the updateCellChanged()
method may be used.
getCellClasses(row, column, classes)- Must add the classes that apply to the cell on row row in column column to the classes object. May be omitted if the cells have no
special classes. If the classes that this method would add changes,
the
datagrid's update methods must be called to update
the rows or cells in question. Some classes have predefined meanings.
toggleColumnSortState(column)- Called by the
datagrid when the user tries to sort
the data using a particular column column. The
data provider must update its state so that the GetChildAtPosition()
method returns the new order, and the classes of the columns
returned by getCaptionClasses()
represent the new sort status. There is no need to tell the
datagrid that it the data has changed, as the
datagrid automatically assumes that the entire data
model will need updating.
setCellCheckedState(row, column, state)- Called by the
datagrid when the user changes the
state of a checkbox cell on row row, column
column. The checkbox should be toggled to the
state given by state, which is a positive
integer (1) if the checkbox is to be checked, zero (0) if it is to
be unchecked, and a negative number (−1) if it is to be set to the
indeterminate state. There is no need to tell the
datagrid that the cell has changed, as the
datagrid automatically assumes that the given cell
will need updating.
cycleCell(row, column)- Called by the
datagrid when the user changes the
state of a cyclable cell on row row, column
column. The data provider should change the
state of the cell to the new state, as appropriate. There is no
need to tell the datagrid that the cell has
changed, as the datagrid automatically assumes that
the given cell will need updating.
editCell(row, column, data)- Called by the
datagrid when the user edits the
cell on row row, column column. The new value of the cell is given by data. The data provider should update the cell
accordingly. There is no need to tell the datagrid
that the cell has changed, as the datagrid
automatically assumes that the given cell will need updating.
The following classes (for rows, columns, and cells) may be
usefully used in conjunction with this interface:
| Class name |
Applies to |
Description説明 |
|---|
checked |
Cells |
The cell has a checkbox and it is checked. (The cyclable and progress classes
override this, though.) |
cyclable |
Cells |
The cell can be cycled through multiple values. (The progress class
overrides this, though.) |
editable |
Cells |
The cell can be edited. (The cyclable, progress, checked, unchecked and indeterminate classes
override this, though.) |
|
Rows |
The row is a heading, not a data row. |
indeterminate |
Cells |
The cell has a checkbox, and it can be set to an indeterminate
state. If neither the checked nor unchecked classes are
present, then the checkbox is in that state, too. (The cyclable and progress classes
override this, though.) |
initially-hidden |
Columns |
The column will not be shown when the datagrid is
initially rendered. If this class is not present on the column
when the datagrid is initially rendered, the column
will be visible if space allows. |
initially-closed |
Rows |
The row will be closed when the datagrid is
initially rendered. If neither this class nor the initially-open
class is present on the row when the datagrid is
initially rendered, the initial state will depend on platform
conventions. |
initially-open |
Rows |
The row will be opened when the datagrid is
initially rendered. If neither this class nor the initially-closed
class is present on the row when the datagrid is
initially rendered, the initial state will depend on platform
conventions. |
progress |
Cells |
The cell is a progress bar. |
reversed |
Columns |
If the cell is sorted, the sort direction is descending,
instead of ascending. |
selectable-separator |
Rows |
The row is a normal, selectable, data row, except that instead
of having data, it only has a separator. (The header and separator classes
override this, though.) |
separator |
Rows |
The row is a separator row, not a data row. (The header class
overrides this, though.) |
sortable |
Columns |
The data can be sorted by this column. |
sorted |
Columns |
The data is sorted by this column. Unless the reversed class is
also present, the sort direction is ascending. |
unchecked |
Cells |
The cell has a checkbox and, unless the checked class is
present as well, it is unchecked. (The cyclable and progress classes
override this, though.) |
4.11.2.4 The default data provider
The user agent must supply a default data provider for the case
where the datagrid's data attribute is null. It must act
as described in this section.
The behavior of the default data provider depends on the nature
of the first element child of the datagrid.
- While the first element child is a
table element
-
getRowCount(row):
The number of rows returned by the default data provider for the
root of the tree (when row is empty) must be the total number of tr elements
that are children of tbody elements that are children
of the table, if there are any such child
tbody elements. If there are no such
tbody elements then the number of rows returned for
the root must be the number of tr elements that are
children of the table.
When row is not empty, the number of rows
returned must be zero.
The table-based default data provider
cannot represent a tree.
Rows in thead elements do not
contribute to the number of rows returned, although they do affect
the columns and column captions. Rows in tfoot
elements are ignored completely by
this algorithm.
getChildAtPosition(row, i): The
default data provider must return the mapping appropriate to the
current sort
order.
getColumnCount():
The number of columns returned must be the number of
td element children in the first tr
element child of the first tbody element child of the
table, if there are any such tbody
elements. If there are no such tbody elements, then
it must be the number of td element children in the
first tr element child of the table, if
any, or otherwise 1. If the number that would be returned by these
rules is 0, then 1 must be returned instead.
getCaptionText(i): If the table has
no thead element child, or if its first
thead element child has no tr element
child, the default data provider must return the empty string for
all captions. Otherwise, the value of the textContent
attribute of the ith th element
child of the first tr element child of the first
thead element child of the table element
must be returned. If there is no such th element, the
empty string must be returned.
getCaptionClasses(i, classes): If
the table has no thead element child, or
if its first thead element child has no
tr element child, the default data provider must not
add any classes for any of the captions. Otherwise, each class
in the class attribute of the ith th element child of the first
tr element child of the first thead
element child of the table element must be added to
the classes. If there is no such
th element, no classes must be added. The user agent
must then:
Remove the sorted and reversed
classes.
If the table element has a class attribute that includes the sortable class, add the sortable
class.
If the column is the one currently being used to
sort the data, add the sorted class.
If the column is the one currently being used to sort the
data, and it is sorted in descending order, add the reversed class as
well.
The various row- and cell- related methods operate relative to
a particular element, the element of the row or cell specified by
their arguments.
For rows: Since the default data provider for
a table always returns 0 as the number of children
for any row other than the root, the path to the row passed to
these methods will always consist of a single number. In the prose
below, this number is referred to as i.
If the table has tbody element
children, the element for the ith row is the
ith tr element that is a child of
a tbody element that is a child of the
table element. If the table does not
have tbody element children, then the element for the
ith real row is the ith
tr element that is a child of the table
element.
For cells: Given a row and its element, the
row's ith cell's element is the ith td element child of the row
element.
The colspan and rowspan
attributes are ignored by this
algorithm.
getRowImage(i): The URL of the
row's image is the absolute URL obtained by resolving the value of the src attribute of the first
img element child of the row's first cell's element,
if there is one and resolving its attribute is
successful. Otherwise, the URL of the row's image is
the empty string.
getRowMenu(i): If the row's first cell's
element has a menu element child, then the row's menu
is the first menu element child of the row's first
cell's element. Otherwise, the row has no menu.
getRowClasses(i, classes):
The default data provider must never add a class to the row's
classes.
toggleColumnSortState(i): If the data is already being
sorted on the given column, then the user agent must change the
current sort mapping to be the inverse of the current sort
mapping; if the sort order was ascending before, it is now
descending, otherwise it is now ascending. Otherwise, if the
current sort column is another column, or the data model is
currently not sorted, the user agent must create a new mapping,
which maps rows in the data model to rows in the DOM so that the
rows in the data model are sorted by the specified column, in
ascending order. (Which sort comparison operator to use is left up
to the UA to decide.)
When the sort mapping is changed, the values returned by the
getChildAtPosition()
method for the default data provider will change
appropriately.
getCellData(i, j), getCellClasses(i, j, classes), getCellCheckedState(i, j, state), cycleCell(i,
j), and editCell(i,
j, data):
See the common
definitions below.
The data provider must call the datagrid's update
methods appropriately whenever the descendants of the
datagrid mutate. For example, if a tr is
removed, then the updateRowsRemoved()
methods would probably need to be invoked, and any change to a
cell or its descendants must cause the cell to be updated. If the
table element stops being the first child of the
datagrid, then the data provider must call the updateEverything()
method on the datagrid. Any change to a cell that is
in the column that the data provider is currently using as its
sort column must also cause the sort to be reperformed, with a
call to updateEverything() if
the change did affect the sort order.
- While the first element child is a
select or datalist element
-
The default data provider must return 1 for the column count,
the empty string for the column's caption, and must not add any
classes to the column's classes.
For the rows, assume the existence of a node filter view of the
descendants of the first element child of the
datagrid element (the select or
datalist element), that skips all nodes other than
optgroup and option elements, as well as
any descendents of any option elements.
Given a path row, the corresponding element
is the one obtained by drilling into the view, taking the child
given by the path each time.
Given the following XML markup:
<datagrid>
<select>
<!-- the options and optgroups have had their labels and values removed
to make the underlying structure clearer -->
<optgroup>
<option/>
<option/>
</optgroup>
<optgroup>
<option/>
<optgroup id="a">
<option/>
<option/>
<bogus/>
<option id="b"/>
</optgroup>
<option/>
</optgroup>
</select>
</datagrid>
The path "1,1,2" would select the element with ID "b". In the
filtered view, the text nodes, comment nodes, and bogus elements
are ignored; so for instance, the element with ID "a" (path
"1,1") has only 3 child nodes in the view.
getRowCount(row) must drill through the view to find the
element corresponding to the method's argument, and return the
number of child nodes in the filtered view that the corresponding
element has. (If the row is empty, the
corresponding element is the select element at the
root of the filtered view.)
getChildAtPosition(row, position) must
return position. (The
select/datalist default data provider
does not support sorting the data grid.)
getRowImage(i) must return the empty string, getRowMenu(i) must return null.
getRowClasses(row, classes) must add the
classes from the following list to classes
when their condition is met:
If the row's corresponding element is an
optgroup element: header
If the row's corresponding element
contains other elements that are also in the view, and the
element's class attribute
contains the closed class: initially-closed
If the row's corresponding element
contains other elements that are also in the view, and the
element's class attribute
contains the open class: initially-open
The getCellData(row, cell) method must
return the value of the label attribute if the row's corresponding element is an
optgroup element, otherwise, if the row's corresponding element is an
optionelement, its label attribute if it has one,
otherwise the value of its textContent DOM
attribute.
The getCellClasses(row, cell, classes) method must add no classes.
autoselect some rows when initialized, reflect the selection
in the select, reflect the multiple attribute somehow.
The data provider must call the datagrid's update
methods appropriately whenever the descendants of the
datagrid mutate.
- While the first element child is another element
-
The default data provider must return 1 for the column count,
the empty string for the column's caption, and must not add any
classes to the column's classes.
For the rows, assume the existence of a node filter view of the
descendants of the datagrid that skips all nodes
other than li, h1–h6, and
hr elements, and skips any descendants of
menu elements.
Given this view, each element in the view represents a row in
the data model. The element corresponding to a path row is the one obtained by drilling into the view,
taking the child given by the path each time. The element of the
row of a particular method call is the element given by drilling
into the view along the path given by the method's arguments.
getRowCount(row) must return the number of child
elements in this view for the given row, or the number of elements
at the root of the view if the row is
empty.
In the following example, the elements are identified by the
paths given by their child text nodes:
<datagrid>
<ol>
<li> row 0 </li>
<li> row 1
<ol>
<li> row 1,0 </li>
</ol>
</li>
<li> row 2 </li>
</ol>
</datagrid>
In this example, only the li elements actually
appear in the data grid; the ol element does not
affect the data grid's processing model.
getChildAtPosition(row, position) must
return position. (The generic default data
provider does not support sorting the data grid.)
getRowImage(i) must return the absolute URL
obtained from resolving the
value of the src attribute of
the first img element descendant (in the real DOM) of
the row's element, that is not also a descendant of another
element in the filtered view that is a descendant of the row's
element, if such an element exists and resolving its attribute is
successful. Otherwise, it must return the empty string.
In the following example, the row with path "1,0" returns
"http://example.com/a" as its image URL, and the other rows
(including the row with path "1") return the empty string:
<datagrid>
<ol>
<li> row 0 </li>
<li> row 1
<ol>
<li> row 1,0 <img src="http://example.com/a" alt=""> </li>
</ol>
</li>
<li> row 2 </li>
</ol>
</datagrid>
getRowMenu(i) must return the first menu
element descendant (in the real DOM) of the row's element, that is
not also a descendant of another element in the filtered view that
is a descendant of the row's element. (This is analogous to the
image case above.)
getRowClasses(i, classes) must add the
classes from the following list to classes
when their condition is met:
If the row's element contains other elements that are also in
the view, and the element's class
attribute contains the closed class: initially-closed
If the row's element contains other elements that are also in
the view, and the element's class
attribute contains the open class: initially-open
If the row's element is an h1–h6
element: header
If the row's element is an hr element: separator
The getCellData(i, j), getCellClasses(i, j, classes), getCellCheckedState(i, j, state), cycleCell(i,
j), and editCell(i, j, data) methods must
act as described in the common
definitions below, treating the row's element as being the
cell's element.
selection
handling?
The data provider must call the datagrid's update
methods appropriately whenever the descendants of the
datagrid mutate.
- Otherwise, while there is no element child
-
The data provider must return 0 for the number of rows, 1 for
the number of columns, the empty string for the first column's
caption, and must add no classes when asked for that column's
classes. If the datagrid's child list changes such
that there is a first element child, then the data provider must
call the updateEverything()
method on the datagrid.
4.11.2.4.1 Common default data
provider method definitions for cells
These definitions are used for the cell-specific methods of the
default data providers (other than in the
select/datalist case). How they behave is
based on the contents of an element that represents the cell given
by their first two arguments. Which element that is is defined in
the previous section.
- Cyclable cells
-
If the first element child of a cell's element is a
select element that has a no multiple attribute and has at
least one option element descendent, then the cell
acts as a cyclable cell.
The "current" option element is the selected
option element, or the first option
element if none is selected.
The getCellData()
method must return the textContent of the current
option element (the label attribute is ignored in this context as the
optgroups are not displayed).
The getCellClasses() method
must add the cyclable class and
then all the classes of the current option
element.
The cycleCell()
method must change the selection of the select
element such that the next option element after the
current option element is the only one that is
selected (in tree order). If the current option
element is the last option element descendent of the
select, then the first option element
descendent must be selected instead.
The setCellCheckedState()
and editCell() methods
must do nothing.
- Progress bar cells
-
If the first element child of a cell's element is a
progress element, then the cell acts as a progress
bar cell.
The getCellData()
method must return the value returned by the progress
element's position DOM
attribute.
The getCellClasses() method
must add the progress class.
The setCellCheckedState(),
cycleCell(), and
editCell() methods must
do nothing.
- Checkbox cells
-
If the first element child of a cell's element is an
input element that has a type attribute with the value checkbox, then the cell acts as a check box
cell.
The getCellData()
method must return the textContent of the cell
element.
The getCellClasses() method
must add the checked class if the
input element's checkedness is true, and the
unchecked class
otherwise.
The setCellCheckedState()
method must set the input element's checkbox checkedness to true if the
method's third argument is 1, and to false otherwise.
The cycleCell() and
editCell() methods must
do nothing.
- Editable cells
-
If the first element child of a cell's element is an
input element that has a type attribute with the value text or that has no type attribute at all, then the
cell acts as an editable cell.
The getCellData()
method must return the value
of the input element.
The getCellClasses() method
must add the editable class.
The editCell()
method must set the input element's value DOM attribute to the value of
the third argument to the method.
The setCellCheckedState()
and cycleCell()
methods must do nothing.
4.11.2.5 Populating the datagrid element
A datagrid must be disabled until its end tag has
been parsed (in the case of a
datagrid element in the original document markup) or
until it has been inserted into the document (in the case of a
dynamically created element). After that point, the element must
fire a single load event at itself,
which doesn't bubble and cannot be canceled.
The end-tag parsing thing should be moved to
the parsing section.
The datagrid must then populate itself using the
data provided by the data provider assigned to the data DOM attribute. After the view
is populated (using the methods described below), the
datagrid must invoke the initialize() method on the
data provider specified by the data attribute, passing itself (the
HTMLDataGridElement object) as the only argument.
When the data attribute is
null, the datagrid must use the default data provider
described in the previous section.
To obtain data from the data provider, the element must invoke
methods on the data provider object in the following ways:
- To determine the total number of columns
- Invoke the
getColumnCount() method
with no arguments. The return value is the number of columns. If
the return value is zero or negative, not an integer, or simply not
a numeric type, or if the method is not defined, then 1 must be
used instead.
- To get the captions to use for the columns
- Invoke the
getCaptionText() method
with the index of the column in question. The index i must be in the range 0 ≤ i
< N, where N is the
total number of columns. The return value is the string to use when
referring to that column. If the method returns null or the empty
string, the column has no caption. If the method is not defined,
then none of the columns have any captions.
- To establish what classes apply to a column
- Invoke the
getCaptionClasses()
method with the index of the column in question, and an object
implementing the DOMTokenList interface, associated
with an anonymous empty string. The index i
must be in the range 0 ≤ i < N, where N is the total number
of columns. The tokens contained in the string underlying
DOMTokenList object when the method returns represent
the classes that apply to the given column. If the method is not
defined, no classes apply to the column.
- To establish whether a column should be initially included in
the visible columns
- Check whether the
initially-hidden
class applies to the column. If it does, then the column should not
be initially included; if it does not, then the column should be
initially included.
- To establish whether the data can be sorted
relative to a particular column
- Check whether the
sortable class
applies to the column. If it does, then the user agent should offer
the user the option to have the data displayed sorted by that
column; if it does not, then the user agent must not allow the user
to ask for the data to be sorted by that column.
- To establish if a column is a sorted column
- If the user agent can handle multiple columns being marked as
sorted simultaneously: Check whether the
sorted class applies to
the column. If it does, then that column is the sorted column,
otherwise it is not.
- If the user agent can only handle one column being marked as
sorted at a time: Check each column in turn, starting with the
first one, to see whether the
sorted class applies to
that column. The first column that has that class, if any, is the
sorted column. If none of the columns have that class, there is no
sorted column.
- To establish the sort direction of a sorted column
- Check whether the
reversed class
applies to the column. If it does, then the sort direction is
descending (down; first rows have the highest values), otherwise it
is ascending (up; first rows have the lowest values).
- To determine the total number of rows
- Determine the number of rows for the root of the data grid, and
determine the number of child rows for each open row. The total
number of rows is the sum of all these numbers.
- To determine the number of rows for the root of the data grid
- Invoke the
getRowCount() method with a
RowSpecification object representing the empty path as
its only argument. The return value is the number of rows at the
top level of the data grid. If the return value of the method is
negative, not an integer, or simply not a numeric type, or if the
method is not defined, then zero must be used instead.
- To determine the number of child rows for a row
- Invoke the
getRowCount() method with a
RowSpecification object representing the path to the
row in question. The return value is the number of child rows for
the given row. If the return value of the method is negative, not
an integer, or simply not a numeric type, or if the method is not
defined, then zero must be used instead.
- To determine what order to render rows in
-
Invoke the getChildAtPosition()
method with a RowSpecification object representing
the path to the parent of the rows that are being rendered as the
first argument, and the position that is being rendered as the
second argument. The return value is the index of the row to
render in that position.
If the rows are:
Row "0"
Row "0,0"
Row "0,1"
Row "1"
Row "1,0"
Row "1,1"
...and the getChildAtPosition()
method is implemented as follows:
function getChildAtPosition(parent, child) {
// always return the reverse order
return getRowCount(parent)-child-1;
}
...then the rendering would actually be:
Row "1"
Row "1,1"
Row "1,0"
Row "0"
Row "0,1"
Row "0,0"
If the return value of the method is negative, larger than the
number of rows that the getRowCount() method
reported for that parent, not an integer, or simply not a numeric
type, then the entire data grid should be disabled. Similarly, if
the method returns the same value for two or more different values
for the second argument (with the same first argument, and
assuming that the data grid hasn't had relevant update methods
invoked in the meantime), then the data grid should be
disabled. Instead of disabling the data grid, the user agent may
act as if the getChildAtPosition()
method was not defined on the data provider (thus disabling
sorting for that data grid, but still letting the user interact
with the data). If the method is not defined, then the return
value must be assumed to be the same as the second argument (an
identity transform; the data is rendered in its natural
order).
- To establish what classes apply to a row
- Invoke the
getRowClasses() method
with a RowSpecification object representing the row in
question, and a DOMTokenList associated with an empty
string. The tokens contained in the DOMTokenList
object's underlying string when the method returns represent the
classes that apply to the row in question. If the method is not
defined, no classes apply to the row.
- To establish whether a row is a data row or a special row
- Examine the classes that apply to the row. If the
header class applies to
the row, then it is not a data row, it is a subheading. The data
from the first cell of the row is the text of the subheading, the
rest of the cells must be ignored. Otherwise, if the separator class applies
to the row, then in the place of the row, a separator should be
shown. Otherwise, if the selectable-separator
class applies to the row, then the row should be a data row, but
represented as a separator. (The difference between a separator and a selectable-separator
is that the former is not an item that can be actually selected,
whereas the second can be selected and thus has a context menu that
applies to it, and so forth.) For both kinds of separator rows, the
data of the rows' cells must all be ignored. If none of those three
classes apply then the row is a simple data row.
- To establish whether a row is openable
- Determine the number of child rows for that row. If there are
one or more child rows, then the row is openable.
- To establish whether a row should be initially open or closed
- If the row is openable, examine the
classes that apply to the row. If the
initially-open
class applies to the row, then it should be initially
open. Otherwise, if the initially-closed
class applies to the row, then it must be initially
closed. Otherwise, if neither class applies to the row, or if the
row is not openable, then the initial state of the row should be
based on platform conventions.
- To obtain a URL identifying an image representing a row
- Invoke the
getRowImage() method with a
RowSpecification object representing the row in
question. The return value is a URL. Immediately resolve that URL as if it came from an
attribute of the datagrid element to obtain an
absolute URL identifying the image that represents the
row. If the method returns the empty string, null, or if the method
is not defined, then the row has no associated image.
- To obtain a context menu appropriate for a particular row
- Invoke the
getRowMenu() method with a
RowSpecification object representing the row in
question. The return value is a reference to an object implementing
the HTMLMenuElement interface, i.e. a
menu element DOM node. (This element must then be
interpreted as described in the section on context menus to obtain
the actual context menu to use.) If the method returns something that is not
an HTMLMenuElement, or if the method is not defined,
then the row has no associated context menu. User agents may
provide their own default context menu, and may add items to the
author-provided context menu. For example, such a menu could allow
the user to change the presentation of the datagrid
element.
- To establish the value of a particular cell
- Invoke the
getCellData() method with
the first argument being a RowSpecification object
representing the row of the cell in question and the second
argument being the index of the cell's column. The second argument
must be a non-negative integer less than the total number of
columns. The return value is the value of the cell. If the return
value is null or the empty string, or if the method is not defined,
then the cell has no data. (For progress bar cells, the cell's
value must be further interpreted, as described below.)
- To establish what classes apply to a cell
- Invoke the
getCellClasses() method
with the first argument being a RowSpecification
object representing the row of the cell in question, the second
argument being the index of the cell's column, and the third being
an object implementing the DOMTokenList interface,
associated with an empty string. The second argument must be a
non-negative integer less than the total number of columns. The
tokens contained in the DOMTokenList object's
underlying string when the method returns represent the classes
that apply to that cell. If the method is not defined, no classes
apply to the cell.
- To establish the type of a cell
- Examine the classes that apply to the cell. If the
progress class applies
to the cell, it is a progress bar. Otherwise, if the cyclable class applies
to the cell, it is a cycling cell whose value can be cycled between
multiple states. Otherwise, none of these classes apply, and the
cell is a simple text cell.
- To establish the value of a progress bar cell
- If the value x of the cell is a string that
can be converted to a floating-point number in the range
0.0 ≤ x ≤ 1.0, then
the progress bar has that value (0.0 means no progress, 1.0 means
complete). Otherwise, the progress bar is an indeterminate progress
bar.
- To establish how a simple text cell should be presented
- Check whether one of the
checked, unchecked, or indeterminate
classes applies to the cell. If any of these are present, then the
cell has a checkbox, otherwise none are present and the cell does
not have a checkbox. If the cell has no checkbox, check whether the
editable class
applies to the cell. If it does, then the cell value is editable,
otherwise the cell value is static.
- To establish the state of a cell's checkbox, if it has one
- Check whether the
checked class applies to
the cell. If it does, the cell is checked. Otherwise, check whether
the unchecked
class applies to the cell. If it does, the cell is unchecked.
Otherwise, the indeterminate
class applies to the cell and the cell's checkbox is in an
indeterminate state. When the indeterminate
class applies to the cell, the checkbox is a tristate checkbox,
and the user can set it to the indeterminate state. Otherwise, only
the checked and/or
unchecked
classes apply to the cell, and the cell can only be toggled between
those two states.
If the data provider ever raises an exception while the
datagrid is invoking one of its methods, the
datagrid must act, for the purposes of that particular
method call, as if the relevant method had not been defined.
A RowSpecification object p with
n path components passed to a method of the data
provider must fulfill the constraint 0 ≤ pi < m-1 for all integer values of i in the range 0 ≤ i < n-1,
where m is the value that was last returned by
the getRowCount()
method when it was passed the RowSpecification object
q with i-1
items, where pi = qi for all integer
values of i in the range
0 ≤ i < n-1, with any changes implied by the update
methods taken into account.
The data model is considered
stable: user agents may assume that subsequent calls to the data
provider methods will return the same data, until one of the update
methods is called on the datagrid element. If a user
agent is returned inconsistent data, for example if the number of
rows returned by getRowCount() varies in ways
that do not match the calls made to the update methods, the user
agent may disable the datagrid. User agents that do not
disable the datagrid in inconsistent cases must honor
the most recently returned values.
User agents may cache returned values so that the data provider
is never asked for data that could contradict earlier data. User
agents must not cache the return value of the getRowMenu method.
The exact algorithm used to populate the data grid is not defined
here, since it will differ based on the presentation used. However,
the behavior of user agents must be consistent with the
descriptions above. For example, it would be non-conformant for a
user agent to make cells have both a checkbox and be editable, as
the descriptions above state that cells that have a checkbox cannot
be edited.
4.11.2.6 Updating the datagrid
Whenever the data
attribute is set to a new value, the datagrid must
clear the current selection, remove all the displayed rows, and plan
to repopulate itself using the information from the new data
provider at the earliest opportunity.
There are a number of update methods that can be invoked on the
datagrid element to cause it to refresh itself in
slightly less drastic ways:
When the updateEverything()
method is called, the user agent must repopulate the entire
datagrid. If the number of rows decreased, the
selection must be updated appropriately. If the number of rows
increased, the new rows should be left unselected.
When the updateRowsChanged(row, count) method
is called, the user agent must refresh the rendering of the rows
starting from the row specified by row, and
including the count next siblings of the row (or
as many next siblings as it has, if that is less than count), including all descendant rows.
When the updateRowsInserted(row, count) method
is called, the user agent must assume that count
new rows have been inserted, such that the first new row is
identified by row. The user agent must update
its rendering and the selection accordingly. The new rows should not
be selected.
When the updateRowsRemoved(row, count) method
is called, the user agent must assume that count
rows have been removed starting from the row that used to be
identifier by row. The user agent must update
its rendering and the selection accordingly.
The updateRowChanged(row) method must be exactly equivalent
to calling updateRowsChanged(row, 1).
When the updateColumnChanged(column) method is called, the user agent
must refresh the rendering of the specified column column, for all rows.
When the updateCellChanged(row, column) method
is called, the user agent must refresh the rendering of the cell on
row row, in column column.
Any effects the update methods have on the
datagrid's selection is not considered a change to the
selection, and must therefore not fire the select event.
These update methods should be called only by the data provider,
or code acting on behalf of the data provider. In particular,
calling the updateRowsInserted()
and updateRowsRemoved()
methods without actually inserting or removing rows from the data
provider is likely to result in
inconsistent renderings, and the user agent is likely to disable
the data grid.
4.11.2.7 Requirements for interactive user agents4.11.2.7 対話的利用者エージェントに対する要件
This section only applies to interactive user agents.この節は対話的利用者エージェントにのみ適用されます。
If the datagrid element has a disabled
attribute, then the user agent must disable the
datagrid, preventing the user from interacting with it.
The datagrid element should still continue to update
itself when the data provider signals changes to the data, though.
Obviously, conformance requirements stating that
datagrid elements must react to users in particular
ways do not apply when one is disabled.
If a row is openable, then the user agent
should offer to the user the option of toggling the row's
open/closed state. When a row's open/closed state changes, the user
agent must update the rendering to match the new state.
If a cell is a cell whose value can be
cycled between multiple states, then the user agent should allow
the user to activate the cell to cycle its value. When the user
activates this "cycling" behavior of a cell, then the
datagrid must invoke the data provider's cycleCell() method, with a
RowSpecification object representing the cell's row as
the first argument and the cell's column index as the second. The
datagrid must then act as if the
datagrid's updateCellChanged()
method had been invoked with those same arguments.
When a cell has a checkbox, the user
agent should allow the user to set the checkbox's state. When the
user changes the state of a checkbox in such a cell, the
datagrid must invoke the data provider's setCellCheckedState()
method, with a RowSpecification object representing the
cell's row as the first argument, the cell's column index as the
second, and the checkbox's new state as the third. The state should
be represented by the number 1 if the new state is checked, 0 if the
new state is unchecked, and −1 if the new state is
indeterminate (which must be possible only if the cell has the indeterminate class
set). The datagrid must then act as if the
datagrid's updateCellChanged()
method had been invoked, specifying the same cell.
If a cell is editable, the user agent
should allow the user to edit the data for that cell, and doing so
must cause the user agent to invoke the editCell() method of the data
provider with three arguments: a RowSpecification
object representing the cell's row, the cell's column's index, and
the new text entered by the user. The user agent must then act as if
the updateCellChanged()
method had been invoked, with the same row and column specified.
4.11.2.8 The selection4.11.2.8 選択
This section only applies to interactive user agents. For
other user agents, the selection attribute must
return null.
interface DataGridSelection {
readonly attribute unsigned long length;
[IndexGetter] RowSpecification item(in unsigned long index);
boolean isSelected(in RowSpecification row);
void setSelected(in RowSpecification row, in boolean selected);
void selectAll();
void invert();
void clear();
};
Each datagrid element must keep track of which rows
are currently selected. Initially no rows are selected, but this can
be changed via the methods described in this section.
The selection of a datagrid is represented by its
selection DOM
attribute, which must be a DataGridSelection object.
DataGridSelection objects represent the rows in the
selection. In the selection the rows must be ordered in the natural
order of the data provider (and not, e.g., the rendered order). Rows
that are not rendered because one of their ancestors is closed must
share the same selection state as their nearest rendered
ancestor. Such rows are not considered part of the selection for the
purposes of iterating over the selection.
This selection API doesn't allow for hidden rows to
be selected because it is trivial to create a data provider that has
infinite depth, which would then require the selection to be
infinite if every row, including every hidden row, was selected.
The length
attribute must return the number of rows currently present in the
selection. The item(index) method must return the indexth row in the selection. If the argument is out
of range (less than zero or greater than the number of selected rows
minus one), then it must raise an INDEX_SIZE_ERR
exception. [DOM3CORE]
The isSelected()
method must return the selected state of the row specified by its
argument. If the specified row exists and is selected, it must
return true, otherwise it must return false.
The setSelected()
method takes two arguments, row and selected. When invoked, it must set the selection
state of row row to selected if selected is true, and unselected if it is false. If
row is not a row in the data grid, the method
must raise an INDEX_SIZE_ERR exception. If the
specified row is not rendered because one of its ancestors is
closed, the method must do nothing.
The selectAll()
method must mark all the rows in the data grid as selected. After a
call to selectAll(), the
length attribute
will return the number of rows in the data grid, not counting
children of closed rows.
The invert()
method must cause all the rows in the selection that were marked as
selected to now be marked as not selected, and vice versa.
The clear()
method must mark all the rows in the data grid to be marked as not
selected. After a call to clear(), the length attribute will
return zero.
If the datagrid element has a multiple
attribute, then the user agent should allow the user to select any
number of rows (zero or more). If the attribute is not present, then
the user agent must not allow the user to select more than a single
row at a time, and selecting another one must unselect all the other
rows.
This only applies to the user. Scripts can select
multiple rows even when the multiple attribute is
absent.
Whenever the selection of a datagrid changes,
whether due to the user interacting with the element, or as a result
of calls to methods of the selection object, a select event
that bubbles but is not cancelable must be fired on the
datagrid element. If changes are made to the selection
via calls to the object's methods during the execution of a
script, then the
select events must be coalesced
into one, which must then be fired when the
script execution has completed.
The DataGridSelection interface has no
relation to the Selection interface.DataGridSelection interface has no relation to the Selection 界面。
4.11.2.9 Columns and captions4.11.2.9 列と見出し
This section only applies to interactive user agents.この節は対話的利用者エージェントにのみ適用されます。
Each datagrid element must keep track of which
columns are currently being rendered. User agents should initially
show all the columns except those with the initially-hidden
class, but may allow users to hide or show columns. User agents
should initially display the columns in the order given by the data
provider, but may allow this order to be changed by the user.
If columns are not being used, as might be the case if the data
grid is being presented in an icon view, or if an overview of data
is being read in an aural context, then the text of the first column
of each row should be used to represent the row.
If none of the columns have any captions (i.e. if the data
provider does not provide a getCaptionText() method),
then user agents may avoid showing the column headers at all. This
may prevent the user from performing actions on the columns (such as
reordering them, changing the sort column, and so on).
Whatever the order used for rendering, and
irrespective of what columns are being shown or hidden, the "first
column" as referred to in this specification is always the column
with index zero, and the "last column" is always the column with the
index one less than the value returned by the getColumnCount() method
of the data provider.
If a column is sortable, then the user
agent should allow the user to request that the data be sorted using
that column. When the user does so, then the datagrid
must invoke the data provider's toggleColumnSortState()
method, with the column's index as the only argument. The
datagrid must then act as if the
datagrid's updateEverything()
method had been invoked.
4.11.3 The command element4.11.3 command 要素
- Categories分類
- Metadata content.メタデータ内容。
- Phrasing content.語句付け内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where metadata content is expected.メタデータ内容が期待される場所。
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Empty.空。
- Element-specific attributes:要素固有属性:
typelabelicondisabledcheckedradiogroupdefault- Also, the
title attribute has special semantics on this element.また、title 属性はこの要素では特別な意味を持ちます。
- DOM interface:DOM 界面:
-
interface HTMLCommandElement : HTMLElement {
attribute DOMString type;
attribute DOMString label;
attribute DOMString icon;
attribute boolean disabled;
attribute boolean checked;
attribute DOMString radiogroup;
attribute boolean default;
void click(); // shadows HTMLElement.click()
};
The Command interface must also be implemented by
this element.Command
界面もこの要素に実装しなければなりません。
The command element represents a command that the user
can invoke.
The type
attribute indicates the kind of command: either a normal command
with an associated action, or a state or option that can be toggled,
or a selection of one item from a list of items.
The attribute is an enumerated attribute with three
keywords and states. The keyword "command"
maps to the Command state, the
checkbox"
maps to the Checkbox, and the
"radio"
keyword maps to the Radio state. The
missing value default is the Command state.
- The Command state
The element represents a normal command with an associated action.
- The Checkbox state
The element represents a state or option that can be toggled.
- The Radio state
The element represents a selection of one item from a list of items.
The label
attribute gives the name of the command, as shown to the user.
The title
attribute gives a hint describing the command, which might be shown
to the user to help him.
The icon
attribute gives a picture that represents the command. If the
attribute is specified, the attribute's value must contain a
valid URL.
The disabled attribute
is a boolean attribute that, if present, indicates that
the command is not available in the current state.
The distinction between disabled and hidden is subtle. A command should be
disabled if, in the same context, it could be enabled if only
certain aspects of the situation were changed. A command should be
marked as hidden if, in that situation, the command will never be
enabled. For example, in the context menu for a water faucet, the
command "open" might be disabled if the faucet is already open, but
the command "eat" would be marked hidden since the faucet could
never be eaten.
The checked
attribute is a boolean attribute that, if present,
indicates that the command is selected. The attribute must be
omitted unless the type
attribute is in either the Checkbox state or
the Radio
state.
The radiogroup
attribute gives the name of the group of commands that will be
toggled when the command itself is toggled, for commands whose type attribute has the value "radio". The scope of the name is the child list of
the parent element. The attribute must be omitted unless the type attribute is in the Radio state.
If the command element is used when generating a context
menu, then the default attribute
indicates, if present, that the command is the one that would have
been invoked if the user had directly activated the menu's subject
instead of using its context menu. The default attribute is a
boolean attribute. The attribute must be omitted
unless the type attribute is
in the Command
state.
Need an example that shows an element that, if
double-clicked, invokes an action, but that also has a context
menu, showing the various command attributes off, and
that has a default command.
The type, label, icon, disabled, checked, radiogroup, and
default DOM
attributes must reflect the respective content
attributes of the same name.
The click()
method's behavior depends on the value of the type attribute of the element, as
follows:
- If the
type attribute is
in the Checkbox state
If the element has a checked attribute, the UA must
remove that attribute. Otherwise, the UA must add a checked attribute, with the
literal value checked. The UA must then
fire a click event at the
element.
- If the
type attribute is
in the Radio state
If the element has a parent, then the UA must walk the list
of child nodes of that parent element, and for each node that is a
command element, if that element has a radiogroup attribute whose
value exactly matches the current element's (treating missing radiogroup attributes as if
they were the empty string), and has a checked attribute, must remove
that attribute and fire a click
event at the element.
Then, the element's checked attribute attribute
must be set to the literal value checked and
a click
event must be fired at the element.
- Otherwiseそれ以外の場合
The UA must fire a click
event at the element.
Firing a synthetic click event at the element does not cause
any of the actions described above to happen.
Need to define the command="" attribute
command elements are not rendered
unless they form part of a menu.
4.11.4 The bb element4.11.4 bb 要素
- Categories分類
- Phrasing content.語句付け内容。
- Interactive content.対話的内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where phrasing content is expected.語句付け内容が期待される場所。
- Content model:内容モデル:
- Phrasing content, but there must be no interactive content descendant.語句付け内容、ただし対話的内容な子孫があってはなりません。
- Element-specific attributes:要素固有属性:
type- DOM interface:DOM 界面:
-
interface HTMLBrowserButtonElement : HTMLElement {
attribute DOMString type;
readonly attribute boolean supported;
readonly attribute boolean disabled;
};
The Command interface must also
be implemented by this element.Command
界面もこの要素に実装しなければなりません。
The bb element represents a user agent command that
the user can invoke.
The type attribute
indicates the kind of command. The type attribute is an enumerated
attribute. The following table lists the keywords and states
for the attribute — the keywords in the left column map to the
states listed in the cell in the second column on the same row as
the keyword.
The missing value default state is the null state.
Each state has an action and a relevance, defined
in the following sections.
When the attribute is in the null state, the
action is to not do anything, and the relevance is
unconditionally false.
A bb element whose type attribute is in a state whose
relevance is true must be enabled. Conversely, a
bb element whose type
attribute is in a state whose relevance is false must be
disabled.
If a bb element is enabled, it must match the :enabled pseudo-class; otherwise, it must match the
:disabled pseudo-class.
User agents should allow users to invoke bb elements
when they are enabled. When a user invokes a bb
element, its type attribute's
state's action must be invoked.
When the element has no descendant element children and has no
descendant text node children of non-zero length, the element
represents a browser button with a user-agent-defined icon or text
representing the type attribute's
state's action and relevance (enabled vs
disabled). Otherwise, the element represents its descendants.
The type DOM
attribute must reflect the content attribute of the
same name.
The supported
DOM attribute must return true if the type attribute is in a state other than
the null state and the user
agent supports that state's action (i.e. when the attribute's
value is one that the user agent recognises and supports), and false
otherwise.
The disabled DOM
attribute must return true if the element is disabled, and false
otherwise (i.e. it returns the opposite of the type attribute's state's
relevance).
4.11.4.1.1 The make application state4.11.4.1.1 アプリケーション作成状態
Some user agents support making sites accessible as independent
applications, as if they were not Web sites at all. The make application state exists
to allow Web pages to offer themselves to the user as targets for
this mode of operation.
The action of the make application state is to
confirm the user's intent to use the current site in a standalone
fashion, and, provided the user's intent is confirmed, offer the
user a way to make the resource identified by the document's
address available in such a fashion.
The confirmation is needed because it is
relatively easy to trick users into activating buttons. The
confirmation could, e.g. take the form of asking the user where to
"save" the application, or non-modal information panel that is
clearly from the user agent and gives the user the opportunity to
drag an icon to their system's application launcher.
The relevance of the make application state is
false if the user agent is already handling the site in such a
fashion, or if the user agent doesn't support making the site
available in that fashion, and true otherwise.
In the following example, a few links are listed on an
application's page, to allow the user perform certain actions,
including making the application standalone:
<menu>
<li><a href="settings.html" onclick="panels.show('settings')">Settings</a>
<li><bb type="makeapp">Download standalone application</bb>
<li><a href="help.html" onclick="panels.show('help')">Help</a>
<li><a href="logout.html" onclick="panels.show('logout')">Sign out</a>
</menu>
With the following stylesheet, it could be make to look like a
single line of text with vertical bars separating the options, with
the "make app" option disappearing when it's not supported or
relevant:
menu li { display: none; }
menu li:enabled { display: inline; }
menu li:not(:first-child)::before { content: ' | '; }
This could look like this:
The following example shows another way to do the same thing as
the previous one, this time not relying on CSS support to hide the
"make app" link if it doesn't apply:
<menu>
<a href="settings.html" onclick="panels.show('settings')">Settings</a> |
<bb type="makeapp" id="makeapp"> </bb>
<a href="help.html" onclick="panels.show('help')">Help</a> |
<a href="logout.html" onclick="panels.show('logout')">Sign out</a>
</menu>
<script>
var bb = document.getElementById('makeapp');
if (bb.supported && bb.enabled) {
bb.parentNode.nextSibling.textContent = ' | ';
bb.textContent = 'Download standalone application';
} else {
bb.parentNode.removeChild(bb);
}
</script>
- Categories分類
- Flow content.流れ内容。
- If the element's
type attribute is in the tool bar state: Interactive content.
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Either: Zero or more
li elements.零個以上の li 要素。
- Or: Flow content.
- Element-specific attributes:要素固有属性:
typelabel- DOM interface:DOM 界面:
-
interface : HTMLElement {
attribute DOMString type;
attribute DOMString label;
};
The menu element represents a list of commands.
The attribute
is an enumerated attribute indicating the kind of menu
being declared. The attribute has three states. The context keyword maps to the
state, in which
the element is declaring a context menu. The toolbar keyword maps to the
tool bar state, in which the
element is declaring a tool bar. The attribute may also be
omitted. The missing value default is the list state, which indicates that the element is merely
a list of commands that is neither declaring a context menu nor
defining a tool bar.
If a menu element's type attribute is in the context menu state, then the
element represents the commands of a context menu, and the user can
only interact with the commands if that context menu is
activated.
If a menu element's type attribute is in the tool bar state, then the element
represents a list of active commands that the user can immediately
interact with.
If a menu element's type attribute is in the list state, then the element either
represents an unordered list of items (each represented by an
li element), each of which represents a command that
the user can perform or activate, or, if the element has no
li element children, flow content
describing available commands.
The
attribute gives the label of the menu. It is used by user agents to
display nested menus in the UI. For example, a context menu
containing another menu would use the nested menu's label attribute for the submenu's
menu label.
The and DOM attributes must
reflect the respective content attributes of the same
name.
This section is non-normative.この節は規定の一部ではありません。
...
A menu (or tool bar) consists of a list of zero or more of the
following components:メニュー (やツールバー) は、次の部品の零以上の並びで構成されます。
Commands, which can be marked as default commands命令 (これは既定命令として印付けできます。)
Separators分離子
Other menus (which allows the list to be nested)他のメニュー (並びを入れ子にできます)
The list corresponding to a particular menu element
is built by iterating over its child nodes. For each child node in
tree order, the required behavior depends on what the
node is, as follows:特定の menu 要素に対応する並びは、
その子供節点に対して反復 (iteration) を行うことで構築できます。
各子供節点について、木順で、
節点の種類によって次に示すような動作が要求されます。
- An element that defines a command命令を定義する要素
- Append the command to the menu, respecting its facets. If the element is a
command element with a default attribute, mark the
command as being a default command.
- An
hr elementhr 要素
- An
option element that has a value attribute set to the empty
string, and has a disabled attribute, and whose
textContent consists of a string of one or more
hyphens (U+002D HYPHEN-MINUS)option 要素で value
属性が空文字列に設定されており、
disabled 属性を持ち、
textContent
が1文字以上のハイフン (U+002D HYPHEN-MINUS) の文字列から成るもの
- Append a separator to the menu.区切子をメニューの最後に追加します。
- An
li elementli 要素
- Iterate over the children of the
li element.li 要素の子供について反復
(iteration) します。
- A
menu element with no label attributemenu 要素で label 属性のないもの
- A
select elementselect 要素
- Append a separator to the menu, then iterate over the children
of the
menu or select element, then
append another separator.分離子をメニューの末尾に追加した後、
menu 要素または select 要素の子供について反復し、
その後もう1つ分離子を末尾に追加します。
- A
menu element with a label attributemenu 要素で
label
属性のあるもの
- An
optgroup elementoptgroup 要素
- Append a submenu to the menu, using the value of the element's
label attribute as the label of the menu. The
submenu must be constructed by taking the element and creating a
new menu for it using the complete process described in this
section.部分メニューをメニューの最後に追加します。このとき、その要素の label 属性の値をメニューの名札として使います。
部分メニューは、その要素をもってこの節で説明した処理全体を用いて新たなメニューを作成することにより構築しなければなりません。
- Any other nodeその他の節点
- Ignore the node.その節点を無視します。
We should support label in the
algorithm above -- just iterate through the contents like with
li, to support input elements in
label elements. Also, optgroup elements
without labels should be ignored (maybe? or at least should say they
have no label so that they are dropped below), and
select elements inside label elements may
need special processing.
Once all the nodes have been processed as described above, the
user agent must the post-process the menu as follows:利用者エージェントは、すべての節点が前述のように処理されたら、
メニューを次のように後処理しなければなりません。
Any menu item with no label, or whose label is the empty string, must be removed.名札がないか名札が空文字列であるメニュー項目は削除しなければなりません。
Any sequence of two or more separators in a row must be collapsed to a single separator.2つ以上の連続した区切子の列は1つの区切子に折り畳まなければなりません。
Any separator at the start or end of the menu must be removed.メニューの最初と最後の区切子は削除しなければなりません。
The
attribute gives the element's context
menu. The value must be the ID of a menu element
in the DOM. If the node that would be obtained by the invoking the
getElementById() method using the attribute's value as
the only argument is null or not a menu element, then
the element has no assigned context menu. Otherwise, the element's
assigned context menu is the element so identified.
When an element's context menu is requested (e.g. by the user
right-clicking the element, or pressing a context menu key), the UA
must fire a contextmenu event on
the element for which the menu was requested.
Typically, therefore, the firing of the contextmenu event will be the
default action of a mouseup or keyup event. The exact sequence of events
is UA-dependent, as it will vary based on platform conventions.
The default action of the contextmenu event depends on
whether the element has a context menu assigned (using the contextmenu attribute) or not. If it
does not, the default action must be for the user agent to show its
default context menu, if it has one.
Context menus should inherit (so clicking on a
span in a paragraph with a context menu should show the menu).
If the element does have a context menu assigned, then
the user agent must fire a show
event on the relevant menu element.
The default action of this event is that the user agent
must show a context menu built from the menu element.
The user agent may also provide access to its default context
menu, if any, with the context menu shown. For example, it could
merge the menu items from the two menus together, or provide the
page's context menu as a submenu of the default menu.
If the user dismisses the menu without making a selection,
nothing in particular happens.
If the user selects a menu item that represents a command, then the UA must invoke
that command's Action.
Context menus must not, while being shown, reflect changes in the
DOM; they are constructed as the default action of the show event and must remain like that until
dismissed.
User agents may provide means for bypassing the context menu
processing model, ensuring that the user can always access the UA's
default context menus. For example, the user agent could handle
right-clicks that have the Shift key depressed in such a way that it
does not fire the contextmenu
event and instead always shows the default context menu.
The
attribute must reflect the contextmenu content attribute.
Toolbars are a kind of menu that is always visible.
When a menu element has a type attribute with the value toolbar, then the user agent must build the menu for that
menu element and render it in the
document in a position appropriate for that menu
element.
The user agent must reflect changes made to the
menu's DOM immediately in the UI.
4.11.6 Commands4.11.6 命令
A command is the abstraction
behind menu items, buttons, and links. Once a command is defined,
other parts of the interface can refer to the same command, allowing
many access points to a single feature to share aspects such as the
disabled state.
Commands are defined to have the following
facets:
- Type型
- The kind of command: "command", meaning it is a normal command;
"radio", meaning that triggering the command will, amongst other
things, set the Checked
State to true (and probably uncheck some other commands); or
"checkbox", meaning that triggering the command will, amongst other
things, toggle the value of the Checked State.
- ID
- The name of the command, for referring to the command from the
markup or from script. If a command has no ID, it is an
anonymous command.
- Label名札
- The name of the command as seen by the user.
- Hintヒント
- A helpful or descriptive string that can be shown to the
user.
- Iconアイコン
- An absolute URL identifying a graphical image that
represents the action. A command might not have an Icon.
- Hidden State
- Whether the command is hidden or not (basically, whether it
should be shown in menus).
- Disabled State
- Whether the command is relevant and can be triggered or not.
- Checked State
- Whether the command is checked or not.
- Action
- The actual effect that triggering the command will have. This
could be a scripted event handler, a URL to which to
navigate, or a form submission.
- Triggers
- The list of elements that can trigger the command. The element
defining a command is always in the list of elements that can
trigger the command. For anonymous commands, only the element
defining the command is on the list, since other elements have no
way to refer to it.
Commands are represented by elements in the DOM. Any element that
can define a command also implements the Command interface:
Actually even better would be to just mix it
straight into those interfaces somehow.
[NoInterfaceObject] interface Command {
readonly attribute DOMString commandType;
readonly attribute DOMString id;
readonly attribute DOMString label;
readonly attribute DOMString title;
readonly attribute DOMString icon;
readonly attribute boolean hidden;
readonly attribute boolean disabled;
readonly attribute boolean checked;
void click();
readonly attribute HTMLCollection triggers;
readonly attribute Command command;
};
The Command interface is
implemented by any element capable of defining a command. (If an
element can define a command, its definition will list this
interface explicitly.) All the attributes of the Command interface are read-only. Elements
implementing this interface may implement other interfaces that have
attributes with identical names but that are mutable; in bindings
that flatten all supported interfaces on the object, the mutable
attributes must shadow the readonly attributes defined in the Command interface.Command interface is implemented by any element capable of defining a command. (If an element can define a command, its definition will list this interface explicitly.) All the attributes of the Command interface are read-only. Elements implementing this interface may implement other interfaces that have attributes with identical names but that are mutable; in bindings that flatten all supported interfaces on the object, the mutable attributes must shadow the readonly attributes defined in the Command 界面。
The commandType
attribute must return a string whose value is either "command", "radio", or "checked", depending on whether the Type of the command defined by the
element is "command", "radio", or "checked" respectively. If the
element does not define a command, it must return null.
The id attribute
must return the command's ID,
or null if the element does not define a command or defines an
anonymous command. This attribute will be shadowed by
the id DOM attribute on the
HTMLElement interface.id attribute must return the command's ID, or null if the element does not define a command or defines an anonymous command. This attribute will be shadowed by the id DOM attribute on the HTMLElement 界面。
The label
attribute must return the command's Label, or null if the element
does not define a command or does not specify a Label. This attribute will be
shadowed by the label DOM attribute on
option and command elements.
The title
attribute must return the command's Hint, or null if the element does
not define a command or does not specify a Hint. This attribute will be
shadowed by the title DOM attribute
on the HTMLElement interface.title attribute must return the command's Hint, or null if the element does not define a command or does not specify a Hint. This attribute will be shadowed by the title DOM attribute on the HTMLElement 界面。
The icon
attribute must return the absolute URL of the command's
Icon. If the element does
not specify an icon, or if the element does not define a command,
then the attribute must return null. This attribute will be shadowed
by the icon DOM attribute on
command elements.
The hidden
attribute must return true if the command's Hidden State is that the
command is hidden, and false if it is that the command is not
hidden. If the element does not define a command, the attribute must
return false. This attribute will be shadowed by the hidden DOM attribute on the
HTMLElement interface.hidden attribute must return true if the command's Hidden State is that the command is hidden, and false if it is that the command is not hidden. If the element does not define a command, the attribute must return false. This attribute will be shadowed by the hidden DOM attribute on the HTMLElement 界面。
The disabled
attribute must return true if the command's Disabled State is that
the command is disabled, and false if the command is not
disabled. This attribute is not affected by the command's Hidden State. If the
element does not define a command, the attribute must return
false. This attribute will be shadowed by the disabled attribute on button,
input, option, and command
elements.
The checked attribute
must return true if the command's Checked State is that the
command is checked, and false if it is that the command is not
checked. If the element does not define a command, the attribute
must return false. This attribute will be shadowed by the checked attribute on input and
command elements.
The click()
method must trigger the Action for the command. If the
element does not define a command, this method must do nothing. This
method will be shadowed by the click() method on HTML
elements, and is included only for completeness.
The triggers
attribute must return a list containing the elements that can
trigger the command (the command's Triggers). The list must be
live. While the element does not define a command, the
list must be empty.
The commands attribute
of the document's HTMLDocument interface must return an
HTMLCollection rooted at the Document
node, whose filter matches only elements that define commands and
have IDs.
The following elements can define commands: a, button, input, option, command, bb.
4.11.6.1 Using the a element to define a command
An a element with an href attribute defines a command.
The Type of the command
is "command".
The ID of the command is
the value of the id attribute of the
element, if the attribute is present and not empty. Otherwise the
command is an anonymous command.
The Label of the command
is the string given by the element's textContent DOM
attribute.
The Hint of the command
is the value of the title attribute
of the element. If the attribute is not present, the Hint is the empty string.
The Icon of the command
is the absolute URL obtained from resolving the value of the src attribute of the first
img element descendant of the element, if there is such
an element and resolving its attribute is successful. Otherwise,
there is no Icon for the
command.
The Hidden State
of the command is true (hidden) if the element has a hidden attribute, and false
otherwise.
The Disabled
State facet of the command is always false. (The command is
always enabled.)
The Checked State
of the command is always false. (The command is never checked.)
The Action of the
command is to fire a click event at the element.
A button element always defines a command.
The Type, ID, Label, Hint, Icon, Hidden State, Checked State, and Action facets of the command are
determined as for a
elements (see the previous section).
The Disabled
State of the command mirrors the disabled state of the button.
An input element whose type attribute is in one of the Submit Button, Reset Button, Button, Radio Button, or Checkbox states defines a command.
The Type of the command
is "radio" if the type
attribute is in the Radio
Button state, "checkbox" if the type attribute is in the Checkbox state, and
"command" otherwise.
The ID of the command is
the value of the id attribute of the
element, if the attribute is present and not empty. Otherwise the
command is an anonymous command.
The Label of the command
depends on the Type of the command:
If the Type is "command",
then it is the string given by the value attribute, if any, and a
UA-dependent value that the UA uses to
label the button itself if the attribute is absent.
Otherwise, the Type is
"radio" or "checkbox". 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 the
string given by element.labels[0].textContent). Otherwise,
the value of the value
attribute, if present, is the Label. Otherwise, the Label is the empty string.
The Hint of the command
is the value of the title attribute
of the input element. If the attribute is not present, the
Hint is the empty
string.
There is no Icon for the
command.
The Hidden State
of the command is true (hidden) if the element has a hidden attribute, and false
otherwise.
The Disabled
State of the command mirrors the disabled state of the
control.
The Checked State
of the command is true if the command is of Type "radio" or "checkbox" and the
element is checked
attribute, and false otherwise.
The Action of the
command is to fire a click event at the element.
4.11.6.4 Using the option element to define a command
An 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 Type of the command
is "radio" if the option's nearest ancestor
select element has no multiple attribute, and
"checkbox" if it does.
The ID of the command is
the value of the id attribute of the
element, if the attribute is present and not empty. Otherwise the
command is an anonymous command.
The Label of the command
is the value of the option element's label attribute, if there is one,
or the value of the option element's
textContent DOM attribute if there isn't.
The Hint of the command
is the string given by the element's title attribute, if any, and the empty
string if the attribute is absent.
There is no Icon for the
command.
The Hidden State
of the command is true (hidden) if the element has a hidden attribute, and false
otherwise.
The Disabled
State of the command is true (disabled) if the element is
disabled or if its
nearest ancestor select element is disabled, and false
otherwise.
The Checked State
of the command is true (checked) if the element's selectedness is true, and
false otherwise.
The Action of the
command depends on its Type. If the command is of Type "radio" then it must pick the option
element. Otherwise, it must toggle the option
element.
4.11.6.5 Using the command element to define
a command
A command element defines a command.
The Type of the command
is "radio" if the command's type attribute is
"radio", "checkbox" if the attribute's value is
"checkbox", and "command" otherwise.
The ID of the command is
the value of the id attribute of the
element, if the attribute is present and not empty. Otherwise the
command is an anonymous command.
The Label of the command
is the value of the element's label attribute, if there is one,
or the empty string if it doesn't.
The Hint of the command
is the string given by the element's title attribute, if any, and the
empty string if the attribute is absent.
The Icon for the command
is the absolute URL obtained from resolving the value of the element's icon attribute, if it has such an
attribute and resolving it is successful. Otherwise, there is no
Icon for the command.
The Hidden State
of the command is true (hidden) if the element has a hidden attribute, and false
otherwise.
The Disabled
State of the command is true (disabled) if the element has a
disabled attribute, and
false otherwise.
The Checked State
of the command is true (checked) if the element has a checked attribute, and false
otherwise.
The Action of the
command is to invoke the behavior described in the definition of
the click() method of the
HTMLCommandElement interface.Action of the command is to invoke the behavior described in the definition of the click() method of the HTMLCommandElement 界面。
4.11.6.6 Using the bb element to define a command
A bb element always defines a command.
The Type of the command
is "command".
The ID of the command is
the value of the id attribute of the
element, if the attribute is present and not empty. Otherwise the
command is an anonymous command.
The Label of the command
is the string given by the element's textContent DOM
attribute, if that is not the empty string, or a user-agent-defined
string appropriate for the bb element's type attribute's state.
The Hint of the command
is the value of the title attribute
of the element. If the attribute is not present, the Hint is a user-agent-defined
string appropriate for the bb element's type attribute's state.
The Icon of the command
is the absolute URL obtained from resolving the value of the src attribute of the first
img element descendant of the element, if there is such
an element and resolving its attribute is successful. Otherwise, the
Icon is a user-agent-defined
image appropriate for the bb element's type attribute's state.
The Hidden State
facet of the command is true (hidden) if the bb
element's type attribute's state
is null or if the element has
a hidden attribute, and false
otherwise.
The Disabled
State facet of the command is true if the bb
element's type attribute's state's
relevance is false, and true otherwise.
The Checked State
of the command is always false. (The command is never checked.)
The Action of the
command is to perform the action of the bb
element's type attribute's
state.
4.12 Miscellaneous elements4.12 その他の要素
4.12.1 The legend element4.12.1 legend 要素
- Categories分類
- None.なし。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- As the first child of a
fieldset element.
- As the first child of a
details element.details 要素の最初の子供として。
- As a child of a
figure element, if there are no other legend element children of that element. figure 要素の子供として。
ただし、その要素に他に legend
要素の子供がない場合。
- Content model:内容モデル:
- Phrasing content.語句付け内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The legend element represents a title or explanatory
caption for the rest of the contents of the legend
element's parent element.legend 要素は、
その親要素の内容の残りの部分に対する題名、説明的な見出しを表します。
4.12.2 The div element4.12.2 div 要素
- Categories分類
- Flow content.流れ内容。
- Contexts in which this element may be used:この要素を使ってもよい文脈:
- Where flow content is expected.流れ内容が期待される場所。
- Content model:内容モデル:
- Flow content.流れ内容。
- Element-specific attributes:要素固有属性:
- None.なし。
- DOM interface:DOM 界面:
- Uses
HTMLElement.HTMLElement を使用。
The div element represents nothing at all. It can be
used with the class, lang/xml:lang, and title attributes to mark up semantics
common to a group of consecutive elements.div 要素はまったく何も表しません。
この要素は class、lang/xml:lang、title
属性と併用することによって連続する要素群に共通な意味をマーク付けすることができます。
Allowing div elements to contain
phrasing content makes it easy for authors to abuse
div, using it with the class="" attribute
to the point of not having any other elements in the markup. This is
a disaster from an accessibility point of view, and it would be nice
if we could somehow make such pages non-compliant without preventing
people from using divs as the extension mechanism that
they are, to handle things the spec can't otherwise do (like making
new widgets).
5 Web browsers5 Web ブラウザー
This section describes features that apply most directly to Web
browsers. Having said that, unless specified elsewhere, the
requirements defined in this section do apply to all user
agents, whether they are Web browsers or not.この章では、 Web ブラウザーに最も直接的に適用される機能について説明します。
とはいえ、この章で定義する要件は、特に断らない限り、
Web ブラウザーであるか否かを問わず全ての利用者エージェントに適用されます。
5.1 Browsing contexts5.1 閲覧文脈
A browsing context is a collection of one or more
Document objects, and one or more views.閲覧文脈は1つ以上の Document
オブジェクトと1つ以上の表示の集成です。
At any one time, one of the Documents in a
browsing context is the active document. The
collection of Documents is the browsing
context's session history.いかなる時点においても、ある 閲覧文脈の中の Document
の1つは活性文書です。
Document の集成は閲覧文脈のセッション履歴です。
A view is a user agent interface tied to a particular
media used for the presentation of Document objects in
some media. A view may be interactive. Each view is represented by
an AbstractView object. Each view belongs to a
browsing context. [DOM2VIEWS]表示は、何らかの媒体における Document
オブジェクトの表現のために用いられる、特定の媒体に紐付けされた利用者エージェント界面です。
提示は対話的であっても構いません。各表示は AbstractView
オブジェクトにより現れます。各表示は閲覧文脈に属します。 [DOM2VIEWS]
The document attribute of an
AbstractView object representing a view
gives the Document object of the view's browsing
context's active document. [DOM2VIEWS]表示を表す
AbstractView オブジェクトの document
属性は、その表示の閲覧文脈の活性文書の
Document オブジェクトを与えます。
[DOM2VIEWS]
Events that use the UIEvent interface
are related to a specific view (the view in which the
event happened); the AbstractView of that view is given
in the event object's view attribute. [DOM3EVENTS]UIEvent 界面を用いる事象は特定の表示
(事象が発生した表示) に関係付けられています。その表示の
AbstractView は事象オブジェクトの view
属性で与えられます。 [DOM3EVENTS]
A typical Web browser has one obvious
view per browsing context: the browser's
window (screen media). If a page is printed, however, a second view
becomes evident, that of the print media. The two views always share
the same underlying Document, but they have a different
presentation of that document. A speech browser also establishes a
browsing context, one with a view in the speech media.一般的な Web ブラウザーは閲覧文脈毎に1つの自明な表示、つまりブラウザーの窓 (画面媒体) を持っています。
しかし、頁が印刷される場合、2つ目の、印刷媒体の表示が現れます。
2つの表示は常に同じ元の Document を共有していますが、
その文書の異なる提示を有しています。会話ブラウザーも、
会話媒体での表示を有する閲覧文脈を確立します。
A Document does not necessarily have a
browsing context associated with it. In particular,
data mining tools are likely to never instantiate browsing
contexts.Document は必ずしも閲覧文脈に関連付けられているとは限りません。
特に、データ・マイニング・ツールは閲覧文脈を決して実現値化しないでしょう。
The main view through which a user primarily
interacts with a user agent is the default view.利用者が利用者エージェントと対話するために主に使用する表示が既定表示です。
The default view of a
Document is given by the defaultView attribute on the Document
object's DocumentView interface. [DOM3VIEWS]Document の 既定表示は
Document オブジェクトの DocumentView
界面の defaultView
属性により与えられます。 [DOM3VIEWS]
When a browsing context is first created, it must be
created with a single Document in its session history,
whose address is
about:blank, which is marked as being an HTML document, and whose character encoding is
UTF-8. The Document must have a single child
html node, which itself has a single child
body node. If the browsing context is
created specifically to be immediately navigated, then that initial
navigation will have replacement enabled.
The origin of the
about:blank Document is set when the
Document is created, in a manner dependent on whether
the browsing context created is a nested browsing
context, as follows:
about:blank Document の起源は、
その Document が作成されるときに、作成された閲覧文脈が入れ子閲覧文脈であるかどうかにより、
次のように設定されます:
- If the new browsing context is a nested
browsing context新しい閲覧文脈が入れ子閲覧文脈である場合
- The origin of the
about:blank
Document is the origin of the
active document of the new browsing
context's parent browsing context at the time
of its creation.about:blank Document の起源は、
新しい閲覧文脈の作成の時点でのその親閲覧文脈の活性文書の起源です。
- If the new browsing context is an auxiliary
browsing context新しい閲覧文脈が補助閲覧文脈である場合
- The origin of the
about:blank
Document is the origin of the
active document of the new browsing
context's opener browsing context at the time
of the new browsing context's creation.about:blank Document の起点は、
新しい閲覧文脈の作成の時点でのその開き元閲覧文脈の活性文書の起点です。
- Otherwiseそれ以外の場合
- The origin of the
about:blank
Document is a globally unique identifier assigned when
the new browsing context is created.about:blank Document の起点は、
その新しい閲覧文脈が作成されたときに割り当てられた大域的に固有な識別子です。
5.1.1 Nested browsing contexts5.1.1 入れ子の閲覧文脈
Certain elements (for example, iframe elements) can
instantiate further browsing
contexts. These are called nested browsing contexts. If a browsing context P has an element E in one of its
Documents D that nests another
browsing context C inside it, then P is said to be the parent browsing
context of C, C is
said to be a child browsing context of P, C is said to be nested through D, and E is said to be the
browsing context container of C.要素によっては (例えば iframe
要素は)、更に閲覧文脈を実現値化することができます。このようなものを入れ子の閲覧文脈と呼びます。
閲覧文脈 P がその Document の1つ
D 中に要素 E を持っていて、その要素の内側に別の閲覧文脈 C
を入れ子にしている場合、 P は C の親閲覧文脈であるといい、
C は P の子閲覧文脈であるといい、 C は D を通じて入れ子であるといい、
E は C の閲覧文脈包含子であるといいます。
A browsing context A is said to be an
ancestor of a browsing context B if there exists
a browsing context A' that is a child
browsing context of A and that is itself
an ancestor of B, or if there is a browsing
context P that is a child browsing
context of A and that is the parent
browsing context of B.閲覧文脈 A が閲覧文脈 B
の祖先であるというのは、 A
の子閲覧文脈である閲覧文脈 A'
が存在して、それ自体が B の祖先である場合、または閲覧文脈 P があって、それが A
の子閲覧文脈であり、かつ B
の親閲覧文脈である場合です。
The browsing context with no parent browsing context
is the top-level browsing context of all the browsing
contexts nested within
it (either directly or indirectly through other nested browsing
contexts).親閲覧文脈のない閲覧文脈は、
それに (直接的に、または他の入れ子閲覧文脈を通じて間接的に)
入れ子になっている閲覧文脈すべての最上位閲覧文脈です。
The transitive closure of parent browsing contexts for a nested browsing
context gives the list of ancestor browsing contexts.入れ子閲覧文脈の親閲覧文脈の推移的閉包が祖先閲覧文脈の並びを与えます。
A Document is said to be fully active
when it is the active document of its browsing
context, and either its browsing context is a top-level
browsing context, or the Document through which that
browsing context is nested is itself fully active.Document が完全に活性であるというのは、
これがその閲覧文脈の活性文書であり、かつその閲覧文脈が最上位閲覧文脈であるか、
またはその閲覧文脈がそれを通じて入れ子になっているような
Document もそれ自体完全に活性であることをいいます。
Because they are nested through an element, child browsing contexts are always tied to
a specific Document in their parent browsing
context. User agents must not allow the user to interact with
child browsing contexts
of elements that are in Documents that are not
themselves fully active.子閲覧文脈は、要素を通じて入れ子になっているため、
常に親閲覧文脈中の特定の Document
と紐付けされています。利用者エージェントは、完全に活性でない
Document 中の要素の子閲覧文脈に対して利用者が対話することを認めてはなりません。
A nested browsing context can have a seamless
browsing context flag set, if it is embedded through an
iframe element with a seamless attribute.入れ子閲覧文脈には、これが
seamless
属性のある iframe
要素を通じて埋め込まれている場合、継ぎ目なし閲覧文脈旗が設定されることがあります。
5.1.1.1 Navigating nested browsing contexts in the DOM5.1.1.1 DOM における入れ子閲覧文脈のナビゲーション
The top DOM attribute on
the Window object of a browsing context
b must return the Window object of
its top-level browsing context (which would be its own
Window object if it was a top-level browsing
context itself).閲覧文脈 b の
Window オブジェクトの top DOM
属性は、その最上位閲覧文脈の
Window
オブジェクト (その閲覧文脈自体が最上位閲覧文脈の場合、
その Window
オブジェクト自体) を返さなければなりません。
The parent DOM
attribute on the Window object of a browsing
context b must return the
Window object of the parent browsing
context, if there is one (i.e. if b is a
child browsing context), or the Window
object of the browsing context b
itself, otherwise (i.e. if it is a top-level browsing
context).閲覧文脈 b の
Window オブジェクトの parent DOM
属性は、その親閲覧文脈があれば
(つまり b が子閲覧文脈である場合) その親閲覧文脈の
Window
オブジェクトを、そうでない場合 (つまりそれ自体が最上位閲覧文脈の場合)
閲覧文脈 b
自体の Window オブジェクトを返さなければなりません。
The frameElement
DOM attribute on the Window object of a browsing
context b, on getting, must run the
following algorithm:閲覧文脈 b の
Window オブジェクトの frameElement DOM
属性は、取得時、次の算法を走らせなければなりません。
If b is not a child browsing
context, return null and abort these steps.b が子閲覧文脈でない場合、
null を返し、これらの段階を停止します。
If the parent browsing context's active
document does not have the same effective
script origin as the script that is accessing the frameElement attribute, then throw
a SECURITY_ERR exception.
Otherwise, return the browsing context
container for b.そうでない場合、 b の閲覧文脈包含子を返します。
5.1.2 Auxiliary browsing contexts5.1.2 補助閲覧文脈
It is possible to create new browsing contexts that are related
to a top level browsing context without being nested
through an element. Such browsing contexts are called auxiliary browsing
contexts. Auxiliary browsing contexts are always top-level browsing
contexts.ある最上位閲覧文脈に関係する新しい閲覧文脈を、
要素を通じて入れ子にせずに作成することができます。このような閲覧文脈を補助閲覧文脈と呼びます。
補助閲覧文脈は常に最上位閲覧文脈です。
An auxiliary browsing context has an opener
browsing context, which is the browsing context
from which the auxiliary browsing context was created,
and it has a furthest ancestor browsing context, which is
the top-level browsing context of the opener
browsing context when the auxiliary browsing
context was created.補助閲覧文脈は、開闢器閲覧文脈を持ちます。これは、補助閲覧文脈を作成した閲覧文脈です。また、最遠祖先閲覧文脈も持ちます。
これは、補助閲覧文脈が作成された時の開闢器閲覧文脈の最上位閲覧文脈です。
5.1.2.1 Navigating auxiliary browsing contexts in the DOM5.1.2.1 DOM における補助閲覧文脈のナビゲーション
The opener DOM
attribute on the Window object must return the
Window object of the browsing context from
which the current browsing context was created (its opener
browsing context), if there is one and it is still
available.Window オブジェクトの
opener DOM 属性は、
現在の閲覧文脈が作成された閲覧文脈 (開闢器閲覧文脈)
の Window
オブジェクトを、これがあって、まだ利用可能であれば、返さなければなりません。
5.1.3 Secondary browsing contexts5.1.3 二次閲覧文脈
User agents may support secondary browsing contexts, which are browsing contexts that form part of
the user agent's interface, apart from the main content area.利用者エージェントは、二次閲覧文脈に対応しても構いません。これは、利用者エージェントの界面の一部を形成する、
主たる内容領域とは別の閲覧文脈です。
5.1.4 Security5.1.4 保安性
A browsing context A is
allowed to navigate a second browsing
context B if one of the following
conditions is true:閲覧文脈 A は、
次の条件のいずれかが真である場合、別の閲覧文脈 B
ナビゲーションすることが認められます。
5.1.5 Groupings of browsing contexts5.1.5 閲覧文脈の群化
Each browsing context is defined as having a list of
zero or more directly reachable browsing contexts. These
are:各閲覧文脈は、零以上の直接到達可能閲覧文脈の並びを持つと定義します。
これは、次の閲覧文脈を含みます。
The transitive closure of all the browsing contexts that are directly reachable
browsing contexts forms a unit of related browsing
contexts.直接到達可能閲覧文脈である閲覧文脈すべての推移的閉包は、関連閲覧文脈の単位を形成します。
Each unit of related browsing contexts is then
further divided into the smallest number of groups such that every
member of each group has an effective script origin
that, through appropriate manipulation of the document.domain attribute, could
be made to be the same as other members of the group, but could not
be made the same as members of any other group. Each such group is a
unit of related similar-origin browsing contexts.関連閲覧文脈の単位のそれぞれを更に分割して、
各群のすべての成員が document.domain 属性の適切な操作によって同じ群の他の成員と同じ実効スクリプト起源となり得、
かつ他のいずれの群の成員とも同じとはなり得ないようになる、
最小の個数の群に分けます。
この群は、それぞれが関連類似起源閲覧文脈の単位です。
5.1.6 Browsing context names5.1.6 閲覧文脈名
Browsing contexts can have a browsing context name. By
default, a browsing context has no name (its name is not set).閲覧文脈は閲覧文脈名を持つことができます。
既定では閲覧文脈は名前を持ちません (名前は設定されません)。
A valid browsing context name is any string with at
least one character that does not start with a U+005F LOW LINE
character. (Names starting with an underscore are reserved for
special keywords.)妥当な閲覧文脈名は、
最低1文字あって U+005F LOW LINE 文字で始まらないような文字列です。
(下線で始まる名前は特別なキーワードに予約します。)
A valid browsing context name or keyword is any string
that is either a valid browsing context name or that is
an ASCII case-insensitive match for one of: _blank, _self, _parent, or _top.妥当な閲覧文脈名かキーワードは、
妥当な閲覧文脈名であるか、
または
_blank、
_self、
_parent、
_top
のいずれかと
ASCII 大文字・小文字不区別で一致するような文字列です。
The rules for choosing a browsing context given a browsing
context name are as follows. The rules assume that they are
being applied in the context of a browsing context.閲覧文脈名から閲覧文脈を選ぶ規則は次の通りです。
この規則はある閲覧文脈の文脈において適用されることを想定しています。
If the given browsing context name is the empty string or
_self, then the chosen browsing context must
be the current one.与えられた閲覧文脈名が空文字列であるか、_self である場合、選ばれる閲覧文脈は現在のものでなければなりません。
If the given browsing context name is _parent, then the chosen browsing context must be
the parent browsing context of the current
one, unless there isn't one, in which case the chosen browsing
context must be the current browsing context.与えられた閲覧文脈名が _parent である場合、
選ばれる閲覧文脈は現在の閲覧文脈の親閲覧文脈があればそれでなければならず、
なければ現在の閲覧文脈でなければなりません。
If the given browsing context name is _top, then the chosen browsing context must be the
most top-level browsing context of the current
one.与えられた閲覧文脈名が _top である場合、
選ばれる閲覧文脈は現在の閲覧文脈の一番最上位閲覧文脈でなければなりません。
-
If the given browsing context name is not _blank and there exists a browsing context whose
name is the same as the
given browsing context name, and the current browsing context is
allowed to navigate that browsing context, and the
user agent determines that the two browsing contexts are related
enough that it is ok if they reach each other, then that browsing
context must be the chosen one. If there are multiple matching
browsing contexts, the user agent should select one in some
arbitrary consistent manner, such as the most recently opened,
most recently focused, or more closely related.与えられた閲覧文脈名が _blank ではなく、
名前が与えられた閲覧文脈名と同じ閲覧文脈が存在し、
現在の閲覧文脈がその閲覧文脈にナビゲーションすることが認められており、
両閲覧文脈の関係が十分深くて互いに到達してもよいと利用者エージェントが判断する場合には、
閲覧文脈はその選んだものでなければなりません。
一致する閲覧文脈が複数ある場合には、利用者エージェントはいずれかを何らかの一貫した方法、
例えば最も新しく開かれたもの、最も新しく焦点が与えられたもの、最も関係が深いものなどを選ぶべきです。
-
Otherwise, a new browsing context is being requested, and what
happens depends on the user agent's configuration and/or
abilities:それ以外の場合、新しい閲覧文脈が要求されており、
利用者エージェントの設定や能力、あるいはその両方によって動作が決まります。
- If the current browsing context has
the sandboxed navigation browsing context flag
set.現在の閲覧文脈が砂箱化操縦閲覧文脈旗を設定されている場合。
- The user agent may offer to create a new top-level
browsing context or reuse an existing top-level
browsing context. If the user picks one of those options,
then the designated browsing context must be the chosen one (the
browsing context's name isn't set to the given browsing context
name). Otherwise (if the user agent doesn't offer the option to
the user, or if the user declines to allow a browsing context to
be used) there must not be a chosen browsing context.利用者エージェントは新しい最上位閲覧文脈を作成することや既存の最上位閲覧文脈を再利用することを提示して構いません。
利用者エージェントがこれらの選択肢の1つを選んだ場合、
指定された閲覧文脈を選ばれた閲覧文脈としなければなりません
(閲覧文脈名は与えられた閲覧文脈名に設定しません)。
そうでない場合 (利用者エージェントが利用者に選択肢を提示しない場合、
あるいは利用者が閲覧文脈を使うことを認めないことにした場合)、
どの閲覧文脈も選んではなりません。
- If the user agent has been configured such that
in this instance it will create a new browsing context, and the
browsing context is being requested as part of following a hyperlink whose
link types include the
noreferrer keyword利用者エージェントがこの実現値において新しい閲覧文脈を作るように設定されており、
リンク型が noreferrer キーワードを含むハイパーリンクをたどる過程で閲覧文脈が要求されている場合
- A new top-level browsing context must be
created. If the given browsing context name is not
_blank, then the new top-level browsing context's
name must be the given browsing context name (otherwise, it has
no name). The chosen browsing context must be this new browsing
context. If it is immediately navigated, then the navigation will be
done with replacement enabled.新しい最上位閲覧文脈を作らなければなりません。
与えられた閲覧文脈名が _blank でない場合、
新しい最上位閲覧文脈の名前は与えられた閲覧文脈名でなければなりません
(そうでない場合、名前を持ちません)。
選ばれる閲覧文脈はこの新しい閲覧文脈でなければなりません。
即座にナビゲーションされる場合には、
そのナビゲーションは置換有効でなされます。
- If the user agent has been configured such that in this
instance it will create a new browsing context, and the
noreferrer keyword doesn't
apply利用者エージェントがこの実現値において新しい閲覧文脈を作るように設定されており、
noreferrer
キーワードが適用されない場合
- A new auxiliary browsing context must be
created, with the opener browsing context being the
current one. If the given browsing context name is not
_blank, then the new auxiliary browsing context's
name must be the given browsing context name (otherwise, it has
no name). The chosen browsing context must be this new browsing
context. If it is immediately navigated, then the navigation will be
done with replacement enabled.新しい補助閲覧文脈を、
現在の閲覧文脈を開闢器閲覧文脈として作らなければなりません。
与えられた閲覧文脈名が _blank でない場合、
新しい補助閲覧文脈の名前は与えられた閲覧文脈名でなければなりません
(そうでない場合、名前を持ちません)。
選ばれる閲覧文脈はこの新しい閲覧文脈でなければなりません。
即座にナビゲーションされる場合は、
そのナビゲーションは置換有効でなされます。
- If the user agent has been configured such that in this
instance it will reuse the current browsing context利用者エージェントがこの実現値において現在の閲覧文脈を再利用するよう設定されている場合
- The chosen browsing context is the current browsing
context.選ばれる閲覧文脈は現在の閲覧文脈です。
- If the user agent has been configured such that in this
instance it will not find a browsing context利用者エージェントがこの実現値において閲覧文脈を探さないよう設定されている場合
- There must not be a chosen browsing context.選ばれる閲覧文脈があってはなりません。
User agent implementors are encouraged to provide a way for
users to configure the user agent to always reuse the current
browsing context.利用者エージェントが常に現在の閲覧文脈を再利用するように利用者が設定できるようにすることを利用者エージェント実装者にはお勧めします。
5.2 The default view5.2 既定表示
The AbstractView object of default views must also implement the
Window and EventTarget interfaces.既定表示の AbstractView オブジェクトは
Window 界面と EventTarget
界面も実装しなければなりません。
[NoInterfaceObject] interface Window {
// the current browsing context
readonly attribute Window window;
readonly attribute Window self;
attribute DOMString name;
[PutForwards=href] readonly attribute Location location;
readonly attribute History history;
readonly attribute UndoManager undoManager;
Selection getSelection();
// other browsing contexts
readonly attribute Window frames;
readonly attribute unsigned long length;
[IndexGetter] Window XXX4(in unsigned long index);
readonly attribute Window top;
readonly attribute Window opener;
readonly attribute Window parent;
readonly attribute Element frameElement;
Window open();
Window open(in DOMString url);
Window open(in DOMString url, in DOMString target);
Window open(in DOMString url, in DOMString target, in DOMString features);
Window open(in DOMString url, in DOMString target, in DOMString features, in DOMString replace);
// the user agent
readonly attribute Navigator navigator;
readonly attribute Storage localStorage;
readonly attribute Storage sessionStorage;
Database openDatabase(in DOMString name, in DOMString version, in DOMString displayName, in unsigned long estimatedSize);
// user prompts
void alert(in DOMString message);
boolean confirm(in DOMString message);
DOMString prompt(in DOMString message);
DOMString prompt(in DOMString message, in DOMString default);
void print();
any showModalDialog(in DOMString url);
any showModalDialog(in DOMString url, in any arguments);
void showNotification(in DOMString title, in DOMString subtitle, in DOMString description);
void showNotification(in DOMString title, in DOMString subtitle, in DOMString description, in VoidCallback onclick);
// cross-document messaging
void postMessage(in DOMString message, in DOMString targetOrigin);
void postMessage(in DOMString message, in MessagePort messagePort, in DOMString targetOrigin);
// event handler DOM attributes
attribute EventListener onabort;
attribute EventListener onbeforeunload;
attribute EventListener onblur;
attribute EventListener onchange;
attribute EventListener onclick;
attribute EventListener oncontextmenu;
attribute EventListener ondblclick;
attribute EventListener ondrag;
attribute EventListener ondragend;
attribute EventListener ondragenter;
attribute EventListener ondragleave;
attribute EventListener ondragover;
attribute EventListener ondragstart;
attribute EventListener ondrop;
attribute EventListener onerror;
attribute EventListener onfocus;
attribute EventListener onhashchange;
attribute EventListener onkeydown;
attribute EventListener onkeypress;
attribute EventListener onkeyup;
attribute EventListener onload;
attribute EventListener onmessage;
attribute EventListener onmousedown;
attribute EventListener onmousemove;
attribute EventListener onmouseout;
attribute EventListener onmouseover;
attribute EventListener onmouseup;
attribute EventListener onmousewheel;
attribute EventListener onresize;
attribute EventListener onscroll;
attribute EventListener onselect;
attribute EventListener onstorage;
attribute EventListener onsubmit;
attribute EventListener onunload;
};
// VoidCallback waiting on WebIDL
The window, frames, and self DOM attributes must all
return the Window object itself.DOM 属性 window、
frames、
self
はすべて Window オブジェクト自体を返さなければなりません。
The Window object also provides the scope for script
execution. Each Document in a browsing
context has an associated list of added properties
that, when a document is active, are available on the
Document's default view's
Window object. A Document object's
list of added properties must be empty when the
Document object is created.Window オブジェクトはスクリプト実行の適用範囲をも提供します。
閲覧文脈中の各 Document
は関連付けられた追加特性のリストを持ち、
この追加特性は、文書が活性な時、
Document の既定表示の
Window オブジェクト上で利用可能となります。
Document オブジェクトの追加特性のリストは、
Document オブジェクトが作られた時には空でなければなりません。
5.2.1 Security5.2.1 保安性
User agents must raise a SECURITY_ERR exception whenever
any of the members of a Window object are accessed by
scripts whose effective script origin is not the same
as the Window object's browsing context's
active document's effective script origin,
with the following exceptions:
User agents must not allow scripts to override the location object's setter.利用者エージェントはスクリプトが location
オブジェクトの設定器を上書きすることを認めてはなりません。
5.2.2 APIs for creating and navigating browsing contexts by name5.2.2 名前により閲覧文脈を作成・ナビゲーションする API
The open() method on
Window objects provides a mechanism for navigating an existing browsing
context or opening and navigating an auxiliary browsing
context.Window オブジェクトの
open()
メソッドは既存の閲覧文脈をナビゲーションしたり、
補助閲覧文脈を開いたりナビゲーションしたりする機構を提供します。
The method has four arguments, though they are all optional.このメソッドは4つの引数を持ちますが、そのすべてが任意選択です。
The first argument, url, must be a
valid URL for a page to load in the browsing
context. If no arguments are provided, or if the first argument is
the empty string, then the url argument defaults
to "about:blank". The argument must be resolved to an absolute
URL (or an error) when the method is invoked.
The second argument, target, specifies the
name of the browsing
context that is to be navigated. It must be a valid browsing
context name or keyword. If fewer than two arguments are
provided, then the name argument defaults to the
value "_blank".2つ目の引数 target は、ナビゲーションされる閲覧文脈の名前を指定します。
これは妥当な閲覧文脈名かキーワードでなければなりません。
引数が2つ未満の場合には、 name 引数には既定値の「_blank」
が用いられます。
The third argument, features, has no effect
and is supported for historical reasons only.3つ目の引数 features は、効果を持たず、
歴史的な理由のみにより対応しています。
The fourth argument, replace, specifies
whether or not the new page will replace the page currently loaded in the browsing
context, when target identifies an existing
browsing context (as opposed to leaving the current page in the
browsing context's session history). When three or
fewer arguments are provided, replace defaults
to false.4つ目の引数 replace は、 target
が既存の閲覧文脈を識別する時に、
閲覧文脈中に現在読み込まれている頁を
(閲覧文脈のセッション履歴に現在の頁を残さずに)
新しい頁が置き換えるかどうかを指定します。
引数が3つ以下の場合、 replace には既定値の偽が用いられます。
When the method is invoked, the user agent must first select a
browsing context to navigate by applying the
rules for choosing a browsing context given a browsing context
name using the target argument as the
name and the browsing context of the script as the
context in which the algorithm is executed, unless the user has
indicated a preference, in which case the browsing context to
navigate may instead be the one indicated by the user.利用者エージェントは、このメソッドが呼び出された時、まずは、
target 引数を名前、スクリプトの閲覧文脈を算法が実行される文脈として用いて閲覧文脈名から閲覧文脈を選ぶ規則を適用してナビゲーションを行う
閲覧文脈を選択しなければなりません。
ただし、利用者が希望を示した場合は例外で、その場合は利用者が示した閲覧文脈をナビゲーションを行うものとして構いません。
For example, suppose there is a user agent that
supports control-clicking a link to open it in a new tab. If a user
clicks in that user agent on an element whose onclick handler uses the window.open() API to open a page in an
iframe, but, while doing so, holds the control key down, the user
agent could override the selection of the target browsing context to
instead target a new tab.例えば、制御鍵を押しながらリンクをクリックすると新しいタブで開く利用者エージェントがあるとします。
利用者がこの利用者エージェント上で onclick 取扱器が window.open() を用いて頁を iframe
で開く要素をクリックした場合で、利用者がクリック中に制御鍵を押し続けていた場合、
利用者エージェントは対象閲覧文脈の選択を上書きして、代わりに新しいタブで開くことができます。
Then, the user agent must navigate the selected
browsing context to the absolute URL (or
error) obtained from resolving
url. If the replace is true,
then replacement must be
enabled; otherwise, it must not be enabled unless the
browsing context was just created as part of the
the rules for choosing a browsing context given a browsing
context name. The navigation must be done with the
script browsing context of the script that invoked the
method as the source browsing context.その後、利用者エージェントは選ばれた閲覧文脈を url
の解決によって得られた絶対
URL (または誤り) にナビゲーションしなければなりません。
replace が真の場合、置換を有効としなければなりません。そうでない場合、
閲覧文脈が閲覧文脈名から閲覧文脈を選ぶ規則の中で作成されたばかりである場合を除き、
置換を有効としてはなりません。ナビゲーションは、
メソッドを呼び出したスクリプトのスクリプト閲覧文脈を原始閲覧文脈として行わなければなりません。
The method must return the Window object of the
default view of the browsing context that was
navigated, or null if no browsing context was navigated.メソッドはナビゲーションされる閲覧文脈の既定表示の Window
オブジェクトか、ナビゲーションされる閲覧文脈がない場合には null を返さなければなりません。
The name attribute of
the Window object must, on getting, return the current
name of the browsing context, and, on setting, set the
name of the browsing context to the new value.Window オブジェクトの name
属性は、取得時には閲覧文脈の現在の名前を返し、
設定時には閲覧文脈の名前を新しい値に設定しなければなりません。
The name gets reset when
the browsing context is navigated to another domain.名前は、他のドメインにナビゲーションされた時に再設定されます。
5.2.3 Accessing other browsing contexts5.2.3 他の閲覧文脈へのアクセス
The length DOM
attribute on the Window interface must return the
number of child browsing
contexts of the active
Document.Window
界面の length DOM 属性は活性
Document の子閲覧文脈の数を返さなければなりません。
The XXX4(index) method must return the indexth child browsing context of the
active Document,
sorted in document order of the elements nesting those browsing
contexts.
5.3 Origin5.3 起源
The origin of a resource and the effective script
origin of a resource are both either opaque identifiers or
tuples consisting of a scheme component, a host component, a port
component, and optionally extra data.資源の起源と資源の実効スクリプト起源は、いずれも、不透明な識別子か、または scheme 部品、 host 部品、 port 部品、任意選択で余剰データの組かのいずれかです。
The extra data could include the certificate of the
site when using encrypted connections, to ensure that if the site's
secure certificate changes, the origin is considered to change as
well.余剰データは、暗号化接続を使っている時に、サイトの保安証明書が変化した場合に起源も同時に変化したとみなすためにこれを含めることができます。
These characteristics are defined as follows:両者の性質は次のように定義されます。
- For URLsURL に関して
-
The origin and effective script
origin of the URL is whatever is returned by
the following algorithm:URL の起源と実効スクリプト起源は、次の算法によって返されるものです。
Let url be the URL for
which the origin is being determined.url を、起源を決定しようとしている URL
とします。
Parse url.url を構文解析します。
If url does not use a server-based
naming authority, or if parsing url failed,
or if url is not an absolute
URL, then return a new globally unique
identifier.url が鯖型命名局を用いていない場合や、
url の構文解析が失敗した場合や、
url が絶対
URL
でない場合、新しい大域的に固有な識別子を返します。
Let scheme be the <scheme> component of url, converted to lowercase.scheme を、url の <scheme> 部品を、小文字に変換したものとします。
If the UA doesn't support the protocol given by scheme, then return a new globally unique
identifier.利用者エージェントが scheme によって与えられるプロトコルに対応していない場合、
新しい大域的に固有な識別子を返します。
If scheme is "file", then the user agent may return a
UA-specific value.scheme が「file」
の場合、利用者エージェントは利用者エージェント規定の値を返して構いません。
Let host be the <host> component of url.host を、url の <host>
部品とします。
-
Apply the IDNA ToASCII algorithm to host,
with both the AllowUnassigned and UseSTD3ASCIIRules flags
set. Let host be the result of the ToASCII
algorithm.host に対して、 IDNA ToASCII 算法を、
AllowUnassigned 旗と UseSTD3ASCIIRules 旗の両方を設定して適用します。
host を、 ToASCII 算法の結果とします。
If ToASCII fails to convert one of the components of the
string, e.g. because it is too long or because it contains
invalid characters, then return a new globally unique
identifier. [RFC3490]ToASCII が文字列の部品のいずれかの変換に失敗した場合、
例えば長すぎたり非妥当な文字を含んだりして失敗した場合、
新しい大域的に固有な識別子を返します。 [RFC3490]
Let host be the result of converting
host to
lowercase.host を、 host を小文字に変換した結果とします。
If there is no <port>
component, then let port be the default port
for the protocol given by scheme. Otherwise,
let port be the <port> component of url.<port> 部品がない場合、
port を、 scheme によって与えられたプロトコルの既定のポートとします。
そうでない場合、 port を、url の <port>
部品とします。
Return the tuple (scheme, host, port).組 (scheme, host, port)
を返します。
In addition, if the URL is in fact associated with
a Document object that was created by parsing the
resource obtained from fetching URL, and this was
done over a secure connection, then the server's secure
certificate may be added to the origin as additional data.加えて、 URL が実は URL の取得によって得られた資源を構文解析することによって作られた Document オブジェクトと関連付けられており、
その取得が安全な接続の上で行われた場合には、
鯖の保安証明書を起源に追加データとして加えて構いません。
- For scriptsスクリプトに関して
-
The origin and effective script
origin of a script are determined from another resource,
called the owner:スクリプトの起源と実効スクリプト起源は、所有者と呼ぶ他の資源によって決定されます。
- If a script is in a
script elementスクリプトが script 要素中にある場合
- The owner is the
Document to which the
script element belongs.所有者は script 要素が所属する Document です。
- If a script is in an event handler content attributeスクリプトが事象取扱器内容属性中にある場合
- The owner is the
Document to which the
attribute node belongs.所有者は属性節点が所属する Document です。
- If a script is a function or other code reference created by
another scriptスクリプトが他のスクリプトによって作成された関数その他の符号参照の場合
- The owner is the script that created it.所有者は作成したスクリプトです。
- If a script is a
javascript: URL that was returned as the
location of an HTTP redirect (or equivalent in
other protocols)
- The owner is the URL that redirected to the
javascript: URL.所有者は javascript: URL
にリダイレクトした URL です。
- If a script is a
javascript: URL in an attributeスクリプトが属性中の javascript: URL の場合
- The owner is the
Document of the element on
which the attribute is found.所有者は属性がある要素の Document です。
- If a script is a
javascript: URL in a style sheetスクリプトがスタイル・シート中の javascript: URL の場合
- The owner is the URL of the style sheet.所有者はスタイル・シートの URL です。
- If a script is a
javascript: URL to which a browsing
context is being navigated,
the URL having been provided by the user (e.g. by using a
bookmarklet)スクリプトが javascript: URL であって、
閲覧文脈がその URL へナビゲーションされていて、
その URL が利用者によって
(例えばブックマークレットを使うことによって)
提供されたものである場合
- The owner is the
Document of the browsing
context's active document.所有者は閲覧文脈の活性文書の Document
です。
- If a script is a
javascript: URL to which a browsing
context is being navigated,
the URL having been declared in markupスクリプトが javascript: URL であって、
閲覧文脈がその URL にナビゲーションされており、
その URL がマーク付け中に宣言されていた場合
- The owner is the
Document of the element
(e.g. an a or area element) that
declared the URL.所有者は当該 URL を宣言している要素
(例えば a 要素や
area 要素)
の Document です。
- If a script is a
javascript: URL to which a browsing
context is being navigated,
the URL having been provided by scriptスクリプトが javascript: URL であって、その URL
に閲覧文脈がナビゲーションされており、
その URL がスクリプトにより提供された場合
- The owner is the script that provided the URL.所有者は当該 URL を提供したスクリプトです。
The origin of the script is then equal to the
origin of the owner, and the effective script
origin of the script is equal to the effective script
origin of the owner.さて、スクリプトの起源は所有者の起源と等しく、
スクリプトの実効スクリプト起源は所有者の実効スクリプト起源と等しいです。
- For
Document objects and imagesDocument オブジェクトと画像に関して
-
- If a
Document is in a
browsing context whose sandboxed origin
browsing context flag is setDocument が砂箱化起源閲覧文脈旗の設定された閲覧文脈中にある場合
- The origin is a globally unique identifier
assigned when the
Document is created.起源は Document が作成された時に割り当てられた大域的に固有な識別子です。
- If a
Document or image was returned by the
XMLHttpRequest APIDocument や画像が XMLHttpRequest API
により返された場合
- The origin and effective script
origin are equal to the origin and
effective script origin of the
Document
object that was the active document of the browsing context of the
Window object from which the
XMLHttpRequest constructor was invoked. (That is,
they track the Document to which the
XMLHttpRequest object's Document
pointer pointed when it was created.) [XHR]起源と実効スクリプト起源は、
XMLHttpRequest 構築子が呼び出された Window
オブジェクトの閲覧文脈の活性文書であった Document
の起源と実効スクリプト起源と等しいです。
(つまり、 XMLHttpRequest オブジェクトが作成された時の Document
指示子が指していた Document を追跡します。)
- If a
Document or image was generated from a
javascript:
URLDocument や画像が javascript:
URL により生成された場合
- The origin is equal to the origin
of the script of that
javascript: URL.起源は当該 javascript: URL のスクリプトの起源と等しいです。
- If a
Document or image was served over the
network and has an address that uses a URL scheme with a
server-based naming authorityDocument や画像がネットワーク上で供給されたもので、鯖型命名局を用いる URL
scheme を使った番地を有する場合
- The origin is the origin of the
address of the
Document or the URL of the image, as
appropriate.
- If a
Document or image was generated from a
data: URL that was returned as the location
of an HTTP redirect (or equivalent in
other protocols)
- The origin is the origin of the
URL that redirected to the
data: URL.起源は data: URL にリダイレクトした
URL の起源です。
- If a
Document or image was generated from a
data: URL found in another
Document or in a scriptDocument や画像が他の Document かスクリプトの中にあった data: URL
から生成された場合
- The origin is the origin of the
Document or script in which the data: URL was found.起源は当該 data: URL
があった Document やスクリプトの起源です。
- If a
Document has the address
"about:blank"
- The origin of the
Document is the origin it was
assigned when its browsing context was created.Document の起源は当該閲覧文脈が作成された時に割り当てられた起源です。
- If a
Document or image was obtained in some
other manner (e.g. a data: URL typed in by
the user, a Document created using the createDocument() API, a data: URL returned as the location of an HTTP
redirect, etc)Document や画像がその他の方法で得られた場合 (例えば利用者によって打鍵された data: URL
の場合、 createDocument() API を使って作られた Document
の場合、 HTTP リダイレクトの所在として返された data: URL の場合など)
- The origin is a globally unique identifier
assigned when the
Document or image is created.起源は Document や画像が作成された時に割り当てられた大域的に固有な識別子です。
When a Document is created, unless stated
otherwise above, its effective script origin is
initialized to the origin of the
Document. However, the document.domain attribute can
be used to change it.Document が作成された時、既に述べた場合を除き、
実効スクリプト起源は Document
の起源に初期化されます。しかし、
document.domain
を使ってこれを変更することができます。
The Unicode serialization of an origin is the string
obtained by applying the following algorithm to the given
origin:起源の Unicode 直列化は、
与えられた起源に次の算法を適用することによって得られる文字列です。
If the origin in question is not a
scheme/host/port tuple, then return the literal string "null" and abort these steps.当該起源が scheme・host・port の組でない場合、
生の文字列「null」を返し、これらの段階を停止します。
Otherwise, let result be the scheme part
of the origin tuple.そうでない場合、 result を、origin
組の scheme 部分とします。
Append the string "://" to result.文字列「://」を result の末尾に追加します。
Apply the IDNA ToUnicode algorithm to each component of the
host part of the origin tuple, and append the results
— each component, in the same order, separated by U+002E FULL
STOP characters (".") — to result.IDNA ToUnicode 算法を origin 組の host 部分の各部品に適用し、
各部品の結果を同じ順序で U+002E FULL
STOP 文字 (".") で分離して result の末尾に追加します。
If the port part of the origin tuple gives a port
that is different from the default port for the protocol given by
the scheme part of the origin tuple, then append a
U+003A COLON character (":") and the given port, in base ten, to
result.起源組の port 部分が 起源
組の scheme 部分で与えられるプロトコルの既定のポートと異なるポートである場合、
U+003A COLON 文字 (":") と与えられたポートを十進数で result
の末尾に追加します。
Return result.result を返します。
The ASCII serialization of an origin is the string
obtained by applying the following algorithm to the given
origin:起源の ASCII 直列化は、
与えられた起源に次の算法を適用して得られる文字列です。
If the origin in question is not a
scheme/host/port tuple, then return the literal string "null" and abort these steps.当該起源が scheme・host・port の組でない場合、
生の文字列「null」を返し、これらの段階を停止します。
Otherwise, let result be the scheme part
of the origin tuple.そうでない場合、 result を、origin
組の scheme 部分とします。
Append the string "://" to result.文字列「://」を result の末尾に追加します。
-
Apply the IDNA ToASCII algorithm the host part of the
origin tuple, with both the AllowUnassigned and
UseSTD3ASCIIRules flags set, and append the results result.起源組の host 部分に ToASCII 算法を AllowUnassigned
旗と UseSTD3ASCIIRules 旗の両方を設定して適用し、結果を result
の末尾に追加します。
If ToASCII fails to convert one of the components of the
string, e.g. because it is too long or because it contains invalid
characters, then return the empty string and abort these steps. [RFC3490]ToASCII が文字列の部品のいずれかの変換に失敗した場合、
例えば長過ぎたり非妥当な文字を含んだりして失敗した場合には、
空文字列を返し、これらの段階を停止します。 [RFC3490]
If the port part of the origin tuple gives a port
that is different from the default port for the protocol given by
the scheme part of the origin tuple, then append a
U+003A COLON character (":") and the given port, in base ten, to
result.起源組の port 部分が 起源
組の scheme 部分で与えられるプロトコルの既定のポートと異なるポートである場合、
U+003A COLON 文字 (":") と与えられたポートを十進数で result
の末尾に追加します。
Return result.result を返します。
Two origins are said to be the
same origin if the following algorithm returns true:次の算法が真を返す場合、2つの起源は同起源であるといいます。
Let A be the first origin
being compared, and B be the second
origin being compared.A を比較する最初の起源とし、
B を比較する2つ目の起源とします。
If A and B are both
opaque identifiers, and their value is equal, then return
true.A と B の両方が不透明な識別子であり、
両者の値が等しければ、真を返します。
Otherwise, if either A or B or both are opaque identifiers, return
false.そうでない場合、 A と B の一方または両方が不透明な文字列であれば、
偽を返します。
If A and B have
scheme components that are not identical, return false.A と B の scheme 部品が同一でない場合、
偽を返します。
If A and B have host
components that are not identical, return false.A と B の host 部品が同一でない場合、
偽を返します。
If A and B have port
components that are not identical, return false.A と B の port 部品が同一でない場合、
偽を返します。
If either A or B
have additional data, but that data is not identical for both,
return false.A と B のいずれかが追加データを持ち、
そのデータが両者同一でない場合、
偽を返します。
Return true.
5.3.1 Relaxing the same-origin restriction5.3.1 同起源制限の緩和
The domain
attribute on Document objects must be initialized to
the document's domain, if it has one, and the empty
string otherwise. On getting, the attribute must return its current
value, unless the document was created by
XMLHttpRequest, in which case it must throw an
INVALID_ACCESS_ERR exception. On setting, the user
agent must run the following algorithm:
-
If the document was created by XMLHttpRequest,
throw an INVALID_ACCESS_ERR exception and abort these
steps.
-
Apply the IDNA ToASCII algorithm to the new value, with both
the AllowUnassigned and UseSTD3ASCIIRules flags set. Let new value be the result of the ToASCII
algorithm.新しい値に IDNA ToASCII 算法を、 AllowUnassigned 旗と UseSTD3ASCIIRules
旗の両方を設定して適用します。 new value を、
ToASCII 算法の結果とします。
If ToASCII fails to convert one of the components of the
string, e.g. because it is too long or because it contains invalid
characters, then throw a SECURITY_ERR exception and abort
these steps. [RFC3490]
-
If new value is not exactly equal to the
current value of the document.domain attribute, then
run these substeps:new value が document.domain 属性の現在の値と正確に等しくない場合、
次の部分段階を走らせます。
-
If the current value is an IP address, throw a SECURITY_ERR
exception and abort these steps.
-
If new value, prefixed by a U+002E FULL
STOP ("."), does not exactly match the end of the current value,
throw a SECURITY_ERR exception and abort these
steps.
-
Set the attribute's value to new value.属性の値を new value に設定します。
-
Set the host part of the effective script origin
tuple of the Document to new
value.Document の実効スクリプト起源の組の host
部分を new
value に設定します。
-
Set the port part of the effective script origin
tuple of the Document to "manual override" (a value
that, for the purposes of comparing
origins, is identical to "manual override" but not
identical to any other value).Document の実効スクリプト起源の組の port
部分を「手動上書き」 (起源の比較においては、
「手動上書き」と同一であり、他の値とは同一ではない値) に設定します。
The domain of a
Document is the host part of the document's
origin, if that is a scheme/host/port tuple. If it
isn't, then the document does not have a domain.Document のドメインは、文書の起源が scheme・host・port 組である場合には、
その host 部分です。そうでない場合には、文書はドメインを持ちません。
The domain
attribute is used to enable pages on different hosts of a domain to
access each others' DOMs.domain 属性は、
あるドメインの異なるホストの頁が互いの DOM にアクセス可能とするために使います。
5.4 Scripting5.4 スクリプティング
Various mechanisms can cause author-provided executable code to
run in the context of a document. These mechanisms include, but are
probably not limited to:著者が提供した実行可能符号を、文書の文脈の中で様々な機構によって走らせることができます。
そのような機構には次のものがありますが、おそらく他にも存在します。
When a script is created, it is associated with a script execution
context, a script browsing context, and a
script document context.スクリプトが作成された時に、スクリプトはスクリプト実行文脈、
スクリプト閲覧文脈、
スクリプト文書文脈と関連付けられます。
5.4.1 Script execution contexts5.4.1 スクリプト実行文脈
The script execution context of a script is defined
when that script is created. In this specification, it is either a
Window object or an empty object; other specifications
might make the script execution context be some other object.
When the script execution context of a script is an
empty object, it can't do anything that interacts with the
environment.
A script execution context always has an associated
browsing context, known as the script browsing
context. If the script execution context is a
Window object, then that object's browsing
context is it. Otherwise, the script execution
context is associated explicitly with a browsing
context when it is created.
Every script whose script execution context is a
Window object is also associated with a
Document object, known as its script document
context. It is used to resolve URLs. The document is assigned when the script
is created, as with the script browsing context.
It is said that scripting is disabled in a
script execution context when any of the following
conditions are true:
A node is said to be without script if either the
Document object of the node (the node itself, if it is
itself a Document object) does not have an associated
browsing context, or scripting is disabled
in that browsing context.
A node is said to be with script if it is not
without script.
If you can find a better pair of terms than
"with script" and "without script" let me know. The only things I
can find that are less confusing are also way, way longer.
When a script is to be executed in a script execution
context in which scripting is disabled, the
script must do nothing and return nothing (a void return value).
Thus, for instance, enabling designMode will disable any
event handler attributes, event listeners, timeouts, etc, that were
set by scripts in the document.
5.4.2 Event loops
To coordinate events, user interaction, scripts, rendering,
networking, and so forth, user agents must use event loops as described in this section.
There must be at least one event loop per user
agent, and at most one event loop per unit of
related similar-origin browsing contexts.
An event loop always has at least one browsing
context. If an event loop's browsing contexts all go away, then
the event loop goes away as well. A browsing
context always has an event loop coordinating
its activities.
An event loop has one or more task queues. A task queue is an ordered
list of tasks, which can be:
- Events
-
Asynchronously dispatching an Event object at a
particular EventTarget object is a task.
Not all events are dispatched using the task
queue, many are dispatched synchronously during other
tasks.
- Parsing
The HTML parser tokenising a single byte, and
then processing any resulting tokens, is a task.
- Callbacks
Calling a callback asynchronously is a task.
- Using a resource
When an algorithm fetches a
resource, if the fetching occurs asynchronously then the processing
of the resource once some or all of the resource is available is a
task.
- Reacting to DOM manipulation
Some elements have tasks that trigger in response to DOM
manipulation, e.g. when that element is inserted into the document.
When a user agent is to queue a task, it must add the
given task to one of the task queues
of the relevant event loop. All the tasks from one
particular task source (e.g. the callbacks generated by
timers, the events dispatched for mouse movements, the tasks queued
for the parser) must always be added to the same task
queue, but tasks from different task sources may be placed in different task queues.
For example, a user agent could have one
task queue for mouse and key events (the user
interaction task source), and another for everything
else. The user agent could then give keyboard and mouse events
preference over other tasks three quarters of the time, keeping the
interface responsive but not starving other task queues, and never
processing events from any one task source out of
order.
An event loop must continually run through the
following steps for as long as it exists:
Run the oldest task on one of the event loop's
task queues. The user agent may
pick any task queue.
Remove that task from its task queue.
If necessary, update the rendering or user interface of any
Document or browsing context to reflect
the current state.
Return to the first step of the event
loop.
5.4.2.1 Generic task sources
The following task sources are
used by a number of mostly unrelated features in this and other
specifications.
- The DOM manipulation task source
-
This task source is used for features that react
to DOM manipulations, such as things that happen asynchronously
when an element is inserted into the document.
Asynchronous mutation events must be dispatched using tasks queued with the DOM manipulation task
source. [DOMEVENTS]
- The user interaction task source
-
This task source is used for features that react
to user interaction, for example keyboard or mouse input.
Asynchronous events sent in response to user input (e.g. click events) must be dispatched using
tasks queued with the user interaction task
source. [DOMEVENTS]
- The networking task source
-
This task source is used for features that trigger
in response to network activity.
5.4.3 The javascript: protocol
A URL using the javascript: protocol must,
if and when dereferenced, be
evaluated by executing the script obtained using the content
retrieval operation defined for javascript:
URLs. [JSURL]
When a browsing context is navigated to a javascript: URL,
and the active document of that browsing context has
the same origin as the script given by that URL, the
script execution context must be the
Window object of the browsing context
being navigated, and the script document context must
be that active document.
When a browsing context is navigated to a javascript: URL,
and the active document of that browsing context has an
origin that is not the same as that of the script given by the URL, the
script execution context must be an empty object, and
the script browsing context must be the browsing
context being navigated.
Otherwise, if the Document object of the element,
attribute, or style sheet from which the javascript:
URL was reached has an associated browsing context, the
script execution context must be an empty object, and
the script execution context's associated
browsing context must be that browsing
context.
Otherwise, the script is not executed and its return value is
void.
If the result of executing the script is void (there is no return
value), then the URL must be treated in a manner equivalent to an
HTTP resource with an HTTP 204 No Content response.
Otherwise, the URL must be treated in a manner equivalent to an
HTTP resource with a 200 OK response whose Content-Type metadata is text/html and whose response body is the return
value converted to a string value.
Certain contexts, in particular img
elements, ignore the Content-Type
metadata.
So for example a javascript: URL for a
src attribute of an
img element would be evaluated in the context of an
empty object as soon as the attribute is set; it would then be
sniffed to determine the image type and decoded as an image.
A javascript: URL in an href attribute of an a
element would only be evaluated when the link was followed.
The src attribute of an
iframe element would be evaluated in the context of
the iframe's own browsing context; once
evaluated, its return value (if it was not void) would replace that
browsing context's document, thus changing the
variables visible in that browsing context.
The rules for handling script execution in a
script execution context include making the script not
execute (and just return void) in certain cases, e.g. in a sandbox
or when the user has disabled scripting altogether.
5.4.4 Events
We need to define how to handle events that are
to be fired on a Document that is no longer the active document of
its browsing context, and for Documents that have no browsing
context. Do the events fire? Do the handlers in that document not
fire? Do we just define scripting to be disabled when the document
isn't active, with events still running as is? See also the
script element section, which says scripts don't run
when the document isn't active.
5.4.4.1 Event handler attributes5.4.4.1 事象取扱器属性
HTML elements can have event handler
attributes specified. These act as bubbling event listeners
for the element on which they are specified.
Each event handler attribute has two parts, an event handler content attribute
and an event handler DOM
attribute. Event handler attributes must initially be set to
null. When their value changes (through the changing of their event
handler content attribute or their event handler DOM attribute),
they will either be null, or have an EventListener
object assigned to them.
Objects other than Element objects, in particular
Window, only have event handler DOM attribute (since they have no
content attributes).
Event handler content attributes, when specified, must
contain valid ECMAScript code matching the ECMAScript FunctionBody production. [ECMA262]
When an event handler content attribute is set, if the element is
owned by a Document that is in a browsing
context, its new value must be interpreted as the body of an
anonymous function with a single argument called event,
with the new function's scope chain being linked from the activation
object of the handler, to the element, to the element's
form element if it is a form control, to the
Document object, to the Window object of
the browsing context of that Document. The
function's this parameter must be the
Element object representing the element. The resulting
function must then be set as the value of the corresponding event
handler attribute, and the new value must be set as the value of the
content attribute. If the given function body fails to compile, then
the corresponding event handler attribute must be set to null
instead (the content attribute must still be updated to the new
value, though).
See ECMA262 Edition 3, sections 10.1.6 and 10.2.3,
for more details on activation objects. [ECMA262]活性化オブジェクトの詳細については、 ECMA 262 第3版の
10.1.6 節と 10.2.3 節を参照してください。
[ECMA262]
The script execution context of the event handler
must be the Window object at the end of the scope
chain. The script document context of the event handler
must be the Document object that owns the event handler
content attribute that was set.事象取扱器のスクリプト実行文脈は、
適用範囲鎖の最後の Window
オブジェクトでなければなりません。事象取扱器のスクリプト文書文脈は、
設定された事象取扱器内容属性を所有する Document
オブジェクトでなければなりません。
When an event handler content attribute is set on an element
owned by a Document that is not in a browsing
context, the corresponding event handler attribute is not
changed.
Removing an event handler content attribute does not
reset the corresponding event handler attribute either.
How do we allow non-JS event handlers?
Event handler DOM attributes, on setting, must set the
corresponding event handler attribute to their new value, and on
getting, must return whatever the current value of the corresponding
event handler attribute is (possibly null).
The following are the event handler attributes that must be
supported by all HTML elements, as both content
attributes and DOM attributes, and on Window objects,
as DOM attributes:次に示すのは、すべての HTML 要素で内容属性としても DOM
属性としても対応しなければならず、 Window
オブジェクトで DOM 属性として対応しなければならない事象取扱器属性です。
onabortMust be invoked whenever an abort event is targeted at or bubbles
through the element.abort 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onbeforeunloadMust be invoked whenever a beforeunload event is targeted at or bubbles
through the element.beforeunload 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onblurMust be invoked whenever a blur event is targeted at or bubbles
through the element.blur 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onchangeMust be invoked whenever a change event is targeted at or bubbles
through the element.change 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onclickMust be invoked whenever a click event is targeted at or bubbles
through the element.click 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
oncontextmenuMust be invoked whenever a contextmenu event is targeted at or bubbles
through the element.contextmenu 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
ondblclickMust be invoked whenever a dblclick event is targeted at or bubbles
through the element.dblclick 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
ondragMust be invoked whenever a drag event is targeted at or bubbles
through the element.drag 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
ondragendMust be invoked whenever a dragend event is targeted at or bubbles
through the element.dragend 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
ondragenterMust be invoked whenever a dragenter event is targeted at or bubbles
through the element.dragenter 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
ondragleaveMust be invoked whenever a dragleave event is targeted at or bubbles
through the element.dragleave 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
ondragoverMust be invoked whenever a dragover event is targeted at or bubbles
through the element.dragover 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
ondragstartMust be invoked whenever a dragstart event is targeted at or bubbles
through the element.dragstart 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
ondropMust be invoked whenever a drop event is targeted at or bubbles
through the element.drop 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onerrorMust be invoked whenever an error event is targeted at or bubbles
through the element.error 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
The onerror
handler is also used for reporting
script errors.onerror 取扱器はスクリプト誤りの報告にも使われます。
onfocusMust be invoked whenever a focus event is targeted at or bubbles
through the element.focus 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onhashchangeMust be invoked whenever a hashchange event is targeted at or bubbles
through the element.hashchange 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onkeydownMust be invoked whenever a keydown event is targeted at or bubbles
through the element.keydown 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onkeypressMust be invoked whenever a keypress event is targeted at or bubbles
through the element.keypress 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onkeyupMust be invoked whenever a keyup event is targeted at or bubbles
through the element.keyup 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onloadMust be invoked whenever a load event is targeted at or bubbles
through the element.load 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onmessageMust be invoked whenever a message event is targeted at or bubbles
through the element.message 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onmousedownMust be invoked whenever a mousedown event is targeted at or bubbles
through the element.mousedown 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onmousemoveMust be invoked whenever a mousemove event is targeted at or bubbles
through the element.mousemove 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onmouseoutMust be invoked whenever a mouseout event is targeted at or bubbles
through the element.mouseout 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onmouseoverMust be invoked whenever a mouseover event is targeted at or bubbles
through the element.mouseover 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onmouseupMust be invoked whenever a mouseup event is targeted at or bubbles
through the element.mouseup 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onmousewheelMust be invoked whenever a mousewheel event is targeted at or bubbles
through the element.mousewheel 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onresizeMust be invoked whenever a resize event is targeted at or bubbles
through the element.resize 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onscrollMust be invoked whenever a scroll event is targeted at or bubbles
through the element.scroll 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onselectMust be invoked whenever a select event is targeted at or bubbles
through the element.select 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onstorageMust be invoked whenever a storage event is targeted at or bubbles
through the element.storage 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onsubmitMust be invoked whenever a submit event is targeted at or bubbles
through the element.submit 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
onunloadMust be invoked whenever an unload event is targeted at or bubbles
through the element.unload 事象が当該要素を対象としているか、泡立って当該要素を通過する時には、
常に呼び出されなければなりません。
When an event handler attribute is invoked, its argument must be
set to the Event object of the event in question. If
the function returns the exact boolean value false, the event's
preventDefault() method must then invoked. Exception:
for historical reasons, for the HTML mouseover event,
the preventDefault() method must be called when the
function returns true instead.事象取扱器属性が呼び出される時、その引数には当該事象の Event
オブジェクトを設定しなければなりません。関数がブール値の偽そのものを返した場合には、
事象の preventDefault() メソッドを呼び出さなければなりません。
例外: 歴史的理由により、 HTML mouseover
事象に関しては、 preventDefault() メソッドは、
代わりに関数が真を返した時に呼び出されなければなりません。
All event handler attributes on an element, whether set to null
or to a function, must be registered as event listeners on the
element, as if the addEventListenerNS()
method on the Element object's EventTarget
interface had been invoked when the element was created, with the
event type (type argument) equal
to the type described for the event handler attribute in the list
above, the namespace (namespaceURI argument) set to
null, the listener set to be a target and bubbling phase listener
(useCapture argument set to
false), the event group set to the default group (evtGroup argument set to null), and
the event listener itself (listener argument) set to do
nothing while the event handler attribute is null, and set to invoke
the function associated with the event handler attribute
otherwise. (The listener
argument is emphatically not the event handler attribute
itself.)要素のすべての事象取扱器属性は、 null に設定されている場合も関数が設定されている場合も、
要素が作成された時に Element オブジェクトの EventTarget
界面の
addEventListenerNS()
メソッドが事象型 (type 引数) は前述の並び中で当該事象取扱属性について示した型、
名前空間 (namespaceURI 引数) は
null、聴取器は対象位相と泡立ち位相の聴取器として (useCapture 引数は偽)、
事象群は既定群として (evtGroup 引数は null)、
事象聴取器自体 (listener 引数) は事象取扱器属性が
null の場合はなにもしないとして、それ以外の場合は事象取扱器属性に関連付けられた関数を呼び出すとして
(listener 引数は事象取扱器属性自体ではないと強調しておきます。)
呼び出した場合のように要素の事象取扱器として登録されなければなりません。
5.4.4.2 Event firing
maybe this should be moved higher up
(terminology? conformance? DOM?) Also, the whole terminology thing
should be changed so that we don't define any specific events here,
we only define 'simple event', 'progress event', 'mouse event', 'key
event', and the like, and have the actual dispatch use those generic
terms when firing events.
Certain operations and methods are defined as firing events on
elements. For example, the click()
method on the HTMLElement interface is defined as
firing a click event on the
element. [DOM3EVENTS]
Firing a click event means that a click
event with no
namespace, which bubbles and is cancelable, and which uses the
MouseEvent interface, must be dispatched at the given
element. The event object must have its screenX, screenY, clientX, clientY, and button attributes set to 0, its ctrlKey, shiftKey, altKey, and metaKey attributes
set according to the current state of the key input device, if any
(false for any keys that are not available), its detail attribute set to 1, and its relatedTarget attribute set to null. The getModifierState() method on the object must return
values appropriately describing the state of the key input device at
the time the event is created.
means that
a contextmenu event with no
namespace, which bubbles and is cancelable, and which uses the
Event interface, must be dispatched at the given
element.
Firing a simple event called
e means that an event with the name e, with no namespace, which does not bubble but is
cancelable (unless otherwise stated), and which uses the
Event interface, must be dispatched at the given
element.
Firing a show event means firing a simple event called show. Actually this should fire an event that has
modifier information (shift/ctrl etc), as well as having a pointer
to the node on which the menu was fired, and with which the menu was
associated (which could be an ancestor of the former).
Firing a load event means firing a simple event called load.
Firing an error event means firing a simple event called error.
Firing a
progress event called e means something
that hasn't yet been defined, in the [PROGRESS] spec.
The default action of these event is to do nothing unless
otherwise stated.
If you dispatch a custom "click" event at an
element that would normally have default actions, should they get
triggered? If so, we need to go through the entire spec and make
sure that any default actions are defined in terms of any
event of the right type on that element, not those that are
dispatched in expected ways.
5.4.4.3 Events and the Window object5.4.4.3 事象と Window オブジェクト
When an event is dispatched at a DOM node in a
Document in a browsing context, if the
event is not a load event, the user
agent must also dispatch the event to the Window, as
follows:事象が閲覧文脈中の
Document 中の DOM 節点で発送された場合で、
その事象が load
事象ではない場合、
利用者エージェントは、
その事象を Window
でも次のように発送しなければなりません。
In the capture phase, the event must be dispatched to the
Window object before being dispatched to any of the
nodes.捕獲位相では、事象は他の節点で発送する前に Window
オブジェクトに発送しなければなりません。
In the bubble phase, the event must be dispatched to the
Window object at the end of the phase, unless bubbling
has been prevented.泡立ち位相では、事象は、泡立ちを防がれていない場合に、位相の終わりで Window
オブジェクトに発送しなければなりません。
5.4.4.4 Runtime script errors5.4.4.4 実行時スクリプト誤り
This section only applies to user agents that support
scripting in general and ECMAScript in particular.この節は一般にスクリプティング、中でも特に ECMAScript に対応している利用者エージェントにだけ適用します。
Whenever a runtime script error occurs in one of the scripts
associated with the document, the value of the onerror event handler DOM
attribute of the Window object must be
processed, as follows:実行時スクリプト誤りが文書に関連付けられtスクリプトのいずれかで起こった時には、
常に Window オブジェクトの onerror 事象取扱器 DOM 属性の値を次のように処理しなければなりません。
- If the value is a function値が関数の場合
-
The function referenced by the onerror attribute must be invoked
with three arguments, before notifying the user of the error.誤りを利用者に通知する前に、 onerror 属性が参照している関数を、3引数で呼び出さなければなりません。
The three arguments passed to the function are all
DOMStrings; the first must give the message that the
UA is considering reporting, the second must give the
absolute URL of the resource in which the error
occurred, and the third must give the line number in that resource
on which the error occurred.関数に渡す3つの引数はすべて DOMString です。
最初の引数は、利用者エージェントが報告しようと考えているメッセージでなければなりません。
2つ目の引数は、誤りが起こった資源の絶対 URL
でなければなりません。
3つ目の引数は、誤りが起こった資源中の行番号でなければなりません。
If the function returns false, then the error should not be
reported to the user. Otherwise, if the function returns another
value (or does not return at all), the error should be reported to
the user.関数が偽を返した場合、誤りを利用者に報告するべきではありません。
そうでない場合、関数が他の値を返した場合 (や何も返さなかった場合)、
誤りを利用者に報告するべきです。
Any exceptions thrown or errors caused by this function must be
reported to the user immediately after the error that the function
was called for, without calling the function again.この関数が投げた例外や起こした誤りは、その関数を呼ぶこととなった誤りの直後に、
この関数を再度呼ぶことなく利用者に報告しなければなりません。
- If the value is
null値が null の場合
-
The error should not reported to the user.誤りを利用者に報告するべきではありません。
- If the value is anything else値がそれ以外の場合
-
The error should be reported to the user.誤りを利用者に報告するべきです。
The initial value of onerror
must be undefined.onerror の初期値は
undefined でなければなりません。
5.5 User prompts
5.5.1 Simple dialogs
The alert(message) method, when invoked, must show
the given message to the user. The user agent
may make the method wait for the user to acknowledge the message
before returning; if so, the user agent must pause
while the method is waiting.
The confirm(message) method, when invoked, must show
the given message to the user, and ask the user
to respond with a positive or negative response. The user agent must
then pause as the method waits for the user's
response. If the user responds positively, the method must return
true, and if the user responds negatively, the method must return
false.
The prompt(message, default)
method, when invoked, must show the given message to the user, and ask the user to either
respond with a string value or abort. The user agent must then
pause as the method waits for the user's
response. The second argument is optional. If the second argument
(default) is present, then the response must be
defaulted to the value given by default. If the
user aborts, then the method must return null; otherwise, the method
must return the string that the user responded with.
5.5.2 Printing5.5.2 印刷
The print() method,
when invoked, must run the printing steps.
User agents should also run the printing steps
whenever the user attempts to obtain a physical form (e.g. printed
copy), or the representation of a physical form (e.g. PDF copy), of
a document.
The printing steps are as follows:
-
The user agent may display a message to the user and/or may
abort these steps.
For instance, a kiosk browser could silently
ignore any invocations of the print() method.
For instance, a browser on a mobile device
could detect that there are no printers in the vicinity and
display a message saying so before continuing to offer a "save to
PDF" option.
-
The user agent must fire a simple event called
beforeprint at the
Window object of the browsing context of the
Document that is being printed, as well as any nested browsing contexts in
it.
The beforeprint event can be used
to annotate the printed copy, for instance adding the time at
which the document was printed.
-
The user agent should offer the user the opportunity to
obtain a physical form (or the representation of a
physical form) of the document. The user agent may wait for the
user to either accept or decline before returning; if so, the user
agent must pause while the method is waiting. Even if
the user agent doesn't wait at this point, the user agent must use
the state of the relevant documents as they are at this point in
the algorithm if and when it eventually creates the alternate
form.
-
The user agent must fire a simple event called
afterprint at the
Window object of the browsing context of the
Document that is being printed, as well as any nested browsing contexts in
it.
The afterprint event can be used
to revert annotations added in the earlier event, as well as
showing post-printing UI. For instance, if a page is walking the
user through the steps of applying for a home loan, the script
could automatically advance to the next step after having printed
a form or other.
5.5.3 Dialogs implemented using separate documents
The showModalDialog(url, arguments) method, when invoked, must
cause the user agent to run the following steps:
-
If the user agent is configured such that this invocation of
showModalDialog() is
somehow disabled, then the method returns the empty string; abort
these steps.
User agents are expected to disable this method in
certain cases to avoid user annoyance. For instance, a user agent
could require that a site be white-listed before enabling this
method, or the user agent could be configured to only allow one
modal dialog at a time.
-
Let the list of background browsing
contexts be a list of all the browsing contexts that:
...as well as any browsing contexts that are nested inside any
of the browsing contexts matching those conditions.
-
Disable the user interface for all the browsing contexts in
the list of background browsing contexts. This
should prevent the user from navigating those browsing contexts,
causing events to to be sent to those browsing context, or editing
any content in those browsing contexts. However, it does not
prevent those browsing contexts from receiving events from sources
other than the user, from running scripts, from running
animations, and so forth.
-
Create a new auxiliary browsing context, with the
opener browsing context being the browsing context of
the Window object on which the showModalDialog() method was
called. The new auxiliary browsing context has no name.
This browsing context implements the
ModalWindow interface.
-
Let the dialog arguments of the new browsing
context be set to the value of arguments.
-
Let the dialog arguments' origin be the
origin of the script that called the showModalDialog() method.
-
Navigate the new browsing context to url, with replacement enabled, and
with the script browsing context of the script that
invoked the method as the source browsing
context.
-
Wait for the browsing context to be closed. (The user agent
must allow the user to indicate that the browsing context is to be
closed.)
-
Reenable the user interface for all the browsing contexts in
the list of background browsing contexts.
-
Return the auxiliary browsing context's
return value.
Browsing contexts created by the above algorithm must implement
the ModalWindow interface:
[XXX] interface ModalWindow {
readonly attribute any dialogArguments;
attribute DOMString returnValue;
};
Such browsing contexts have associated dialog
arguments, which are stored along with the dialog
arguments' origin. These values are set by the showModalDialog() method in the
algorithm above, when the browsing context is created, based on the
arguments provided to the method.
The dialogArguments
DOM attribute, on getting, must check whether its browsing context's
active document's origin is the same as the dialog arguments'
origin. If it is, then the browsing context's dialog
arguments must be returned unchanged. Otherwise, if the
dialog arguments are an object, then the empty string
must be returned, and if the dialog arguments are not
an object, then the stringification of the dialog
arguments must be returned.
These browsing contexts also have an associated return
value. The return value of a browsing context
must be initialized to the empty string when the browsing context is
created.
The returnValue
DOM attribute, on getting, must return the return value
of its browsing context, and on setting, must set the return
value to the given new value.
5.5.4 Notifications
Notifications are short, transient messages that bring the user's
attention to new information, or remind the user of scheduled
events.
Since notifications can be annoying if abused, this specification
defines a mechanism that scopes notifications to a site's existing
rendering area unless the user explicitly indicates that the site
can be trusted.
To this end, each origin can be flagged as being a
trusted notification source. By default origins should
not be flagged as such, but user agents may allow users to whitelist
origins or groups of origins as being trusted notification sources. Only
origins flagged as trusted in this way are allowed to show
notification UI outside of their tab.
For example, a user agent could allow a user to
mark all subdomains and ports of example.org as trusted
notification sources. Then, mail.example.org and
calendar.example.org would both be able to show notifications,
without the user having to flag them individually.
The showNotification(title, subtitle, description, onclick) method, when invoked, must
cause the user agent to show a notification.
If the method was invoked from a script
whose script browsing context has the sandboxed
annoyances browsing context flag set, then the notification
must be shown within that browsing context. The
notification is said to be a sandboxed notification.
Otherwise, if the origin of the script
browsing context of the script that invoked the method is
not flagged as being a trusted notification
source, then the notification should be rendered within the
top-level browsing context of the script browsing
context of the script that invoked the method. The
notification is said to be a normal notification. User
agents should provide a way to set the origin's trusted
notification source flag from the notification, so that the
user can benefit from notifications even when the user agent is not
the active application.
Otherwise, the origin is flagged as a trusted
notification source, and the notification should be shown
using the platform conventions for system-wide notifications. The
notification is said to be a trusted notification. User
agents may provide a way to unset the origin's trusted
notification source flag from within the notification, so as
to allow users to easily disable notifications from sites that abuse
the privilege.
For example, if a site contains a gadget of a mail application
in a sandboxed iframe and that frame triggers a
notification upon the receipt of a new e-mail message, that
notification would be displayed on top of the gadget only.
However, if the user then goes to the main site of that mail
application, the notification would be displayed over the entire
rendering area of the tab for the site.
The notification, in this case, would have a button on it to let
the user indicate that he trusts the site. If the user clicked this
button, the next notification would use the system-wide
notification system, appearing even if the tab for the mail
application was buried deep inside a minimised window.
The style of notifications varies from platform to platform. On
some, it is typically displayed as a "toast" window that slides in
from the bottom right corner. In others, notifications are shown as
semi-transparent white-on-grey overlays centered over the
screen. Other schemes could include simulated ticker tapes, and
speech-synthesis playback.
When a normal notification (but not a
sandboxed notification) is shown, the user agent may
bring the user's attention to the top-level browsing
context of the script browsing context of the
script that invoked the method, if that would be useful; but user
agents should not use system-wide notification mechanisms to do
so.
When a trusted notification is shown, the user agent
should bring the user's attention to the notification and the
script browsing context of the script that invoked the
method, as per the platform conventions for attracting the user's
attention to applications.
In the case of normal
notifications, typically the only attention-grabbing device
that would be employed would be something like flashing the tab's
caption, or making it bold, or some such.
In addition, in the case of a trusted notification,
the entire window could flash, or the browser's application icon
could bounce or flash briefly, or a short sound effect could be
played.
Notifications should include the following content:
If a new notification from one browsing context has
title, subtitle, and description strings that are identical to the title, subtitle, and description strings of an already-active notification
from the same browsing context or another browsing context with the same
origin, the user agent should not display the new
notification, but should instead add an indicator to the
already-active notification that another identical notification
would otherwise have been shown.
For instance, if a user has his mail application open in three
windows, and thus the same "New Mail" notification is fired three
times each time a mail is received, instead of displaying three
identical notifications each time, the user agent could just show
one, with the title "New Mail x3".
Notifications should have a lifetime based on the platform
conventions for notifications. However, the lifetime of a
notification should not begin until the user has had the opportunity
to see it, so if a notification is spawned for a browsing
context that is hidden, it should be shown for its complete
lifetime once the user brings that browsing context
into view.
User agents should support multiple notifications at once.
User agents should support user interaction with notifications,
if and as appropriate given the platform conventions. If a user
activates a notification, and the onclick
callback argument was present and is not null, then the script
browsing context of the function given by onclick should be brought to the user's attention,
and the onclick callback should then be
invoked.
5.6 System state and capabilities
The navigator
attribute of the Window interface must return an
instance of the Navigator interface, which represents
the identity and state of the user agent (the client), and allows
Web pages to register themselves as potential protocol and content
handlers:
interface Navigator {
// objects implementing this interface also implement the interfaces given below
};
[NoInterfaceObject] interface NavigatorID {
readonly attribute DOMString appName;
readonly attribute DOMString appVersion;
readonly attribute DOMString platform;
readonly attribute DOMString userAgent;
};
[NoInterfaceObject] interface NavigatorOnLine {
readonly attribute boolean onLine;
};
[NoInterfaceObject] interface NavigatorAbilities {
// content handler registration
void registerProtocolHandler(in DOMString protocol, in DOMString url, in DOMString title);
void registerContentHandler(in DOMString mimeType, in DOMString url, in DOMString title);
};
Objects implementing the Navigator interface must
also implement the NavigatorID,
NavigatorOnLine, and
NavigatorAbilities interfaces. (These
interfaces are defined separately so that other specifications can
re-use parts of the Navigator interface.)
5.6.1 Client identification
In certain cases, despite the best efforts of the entire
industry, Web browsers have bugs and limitations that Web authors
are forced to work around.
This section defines a collection of attributes that can be used
to determine, from script, the kind of user agent in use, in order
to work around these issues.
Client detection should always be limited to detecting known
current versions; future versions and unknown versions should always
be assumed to be fully compliant.
appNameMust return either the string "Netscape" or the full name of the browser, e.g. "Mellblom Browsernator".
appVersionMust return either the string "4.0" or a string representing the version of the browser in detail, e.g. "1.0 (VMS; en-US) Mellblomenator/9000".
platformMust return either the empty string or a string representing the platform on which the browser is executing, e.g. "MacIntel", "Win32", "FreeBSD i386", "WebTV OS".
userAgentMust return the string used for the value of the "User-Agent" header in HTTP requests, or the empty string if no such header is ever sent.
5.6.2 Custom protocol and content handlers
The registerProtocolHandler()
method allows Web sites to register themselves as possible handlers
for particular protocols. For example, an online fax service could
register itself as a handler of the fax: protocol ([RFC2806]), so that if the user clicks on
such a link, he is given the opportunity to use that Web
site. Analogously, the registerContentHandler()
method allows Web sites to register themselves as possible handlers
for content in a particular MIME type. For example, the same online
fax service could register itself as a handler for
image/g3fax files ([RFC1494]), so that if the user has no
native application capable of handling G3 Facsimile byte streams,
his Web browser can instead suggest he use that site to view the
image.
User agents may, within the constraints described in this
section, do whatever they like when the methods are called. A UA
could, for instance, prompt the user and offer the user the
opportunity to add the site to a shortlist of handlers, or make the
handlers his default, or cancel the request. UAs could provide such
a UI through modal UI or through a non-modal transient notification
interface. UAs could also simply silently collect the information,
providing it only when relevant to the user.
There is an example of how these
methods could be presented to the user below.
The arguments to the methods have the following meanings:
- protocol (
registerProtocolHandler() only)
-
A scheme, such as ftp or fax. The
scheme must be compared in an ASCII case-insensitive
manner by user agents for the purposes of comparing with the
scheme part of URLs that they consider against the list of
registered handlers.
The protocol value, if it contains a colon
(as in "ftp:"), will never match anything, since
schemes don't contain colons.
- mimeType (
registerContentHandler() only)
-
A MIME type, such as model/vrml or
text/richtext. The MIME type must be compared in an
ASCII case-insensitive manner by user agents for the
purposes of comparing with MIME types of documents that they
consider against the list of registered handlers.
User agents must compare the given values only to the MIME
type/subtype parts of content types, not to the complete type
including parameters. Thus, if mimeType values
passed to this method include characters such as commas or
whitespace, or include MIME parameters, then the handler being
registered will never be used.
- url
-
The URL of the page that will handle the
requests. When the user agent uses this URL, it must replace the
first occurrence of the exact literal string "%s"
with an escaped version of the URL of the content in question (as
defined below), then resolve
the resulting URL (using the document base URL of the
script document context of the script that originally
invoked the registerContentHandler()
or registerProtocolHandler()
method), and then fetch the resulting URL using the
GET method (or
equivalent for non-HTTP URLs).
To get the escaped version of the URL of the content in
question, the user agent must resolve the URL, and then every character in the URL
that doesn't match the <query> production defined in RFC
3986 must be replaced by the percent-encoded form of the
character. [RFC3986]
If the user had visited a site at http://example.com/ that made the following
call:
navigator.registerContentHandler('application/x-soup', 'soup?url=%s', 'SoupWeb™')
...and then, much later, while visiting http://www.example.net/, clicked on a link such
as:
<a href="chickenkïwi.soup">Download our Chicken Kiwi soup!</a>
...then, assuming this chickenkïwi.soup file
was served with the MIME type application/x-soup,
the UA might navigate to the following URL:
http://example.com/soup?url=http://www.example.net/chickenk%C3%AFwi.soup
This site could then fetch the chickenkïwi.soup
file and do whatever it is that it does with soup (synthesize it
and ship it to the user, or whatever).
- title
-
A descriptive title of the handler, which the UA might use to
remind the user what the site in question is.
User agents should raise SECURITY_ERR exceptions if
the methods are called with protocol or mimeType values that the UA deems to be
"privileged". For example, a site attempting to register a handler
for http URLs or text/html content in a
Web browser would likely cause an exception to be raised.
User agents must raise a SYNTAX_ERR exception if the
url argument passed to one of these methods does
not contain the exact literal string "%s".
User agents must not raise any other exceptions (other than
binding-specific exceptions, such as for an incorrect number of
arguments in an ECMAScript implementation).
This section does not define how the pages registered by these
methods are used, beyond the requirements on how to process the url value (see above). To some extent, the processing model for navigating across
documents defines some cases where these methods are
relevant, but in general UAs may use this information wherever they
would otherwise consider handing content to native plugins or helper
applications.
UAs must not use registered content handlers to handle content
that was returned as part of a non-GET transaction (or rather, as
part of any non-idempotent transaction), as the remote site would
not be able to fetch the same data.
5.6.2.1 Security and privacy
These mechanisms can introduce a number of concerns, in
particular privacy concerns.
Hijacking all Web usage. User agents should not
allow protocols that are key to its normal operation, such as
http or https, to be rerouted through
third-party sites. This would allow a user's activities to be
trivially tracked, and would allow user information, even in secure
connections, to be collected.
Hijacking defaults. It is strongly recommended
that user agents do not automatically change any defaults, as this
could lead the user to send data to remote hosts that the user is
not expecting. New handlers registering themselves should never
automatically cause those sites to be used.
Registration spamming. User agents should
consider the possibility that a site will attempt to register a
large number of handlers, possibly from multiple domains (e.g. by
redirecting through a series of pages each on a different domain,
and each registering a handler for video/mpeg —
analogous practices abusing other Web browser features have been
used by pornography Web sites for many years). User agents should
gracefully handle such hostile attempts, protecting the user.
Misleading titles. User agents should not rely
wholly on the title argument to the methods when
presenting the registered handlers to the user, since sites could
easily lie. For example, a site hostile.example.net
could claim that it was registering the "Cuddly Bear Happy Content
Handler". User agents should therefore use the handler's domain in
any UI along with any title.
Hostile handler metadata. User agents should
protect against typical attacks against strings embedded in their
interface, for example ensuring that markup or escape characters in
such strings are not executed, that null bytes are properly handled,
that over-long strings do not cause crashes or buffer overruns, and
so forth.
Leaking Intranet URLs. The mechanism described
in this section can result in secret Intranet URLs being leaked, in
the following manner:
The user registers a third-party content handler as the default
handler for a content type.
The user then browses his corporate Intranet site and accesses
a document that uses that content type.
The user agent contacts the third party and hands the third
party the URL to the Intranet content.
No actual confidential file data is leaked in this manner, but
the URLs themselves could contain confidential information. For
example, the URL could be
http://www.corp.example.com/upcoming-aquisitions/the-sample-company.egf,
which might tell the third party that Example Corporation is
intending to merge with The Sample Company. Implementors might wish
to consider allowing administrators to disable this feature for
certain subdomains, content types, or protocols.
Leaking secure URLs. User agents should not send
HTTPS URLs to third-party sites registered as content handlers, in
the same way that user agents do not send Referer
headers from secure sites to third-party sites.
Leaking credentials. User agents must never send
username or password information in the URLs that are escaped and
included sent to the handler sites. User agents may even avoid
attempting to pass to Web-based handlers the URLs of resources
that are known to require authentication to access, as such sites
would be unable to access the resources in question without
prompting the user for credentials themselves (a practice that would
require the user to know whether to trust the third-party handler, a
decision many users are unable to make or even understand).
5.6.2.2 Sample user interface
This section is non-normative.この節は規定の一部ではありません。
A simple implementation of this feature for a desktop Web browser
might work as follows.
The registerProtocolHandler()
method could display a modal dialog box:
||[ Protocol Handler Registration ]|||||||||||||||||||||||||||
| |
| This Web page: |
| |
| Kittens at work |
| http://kittens.example.org/ |
| |
| ...would like permission to handle the protocol "x-meow:" |
| using the following Web-based application: |
| |
| Kittens-at-work displayer |
| http://kittens.example.org/?show=%s |
| |
| Do you trust the administrators of the "kittens.example. |
| org" domain? |
| |
| ( Trust kittens.example.org ) (( Cancel )) |
|____________________________________________________________|
...where "Kittens at work" is the title of the page that invoked
the method, "http://kittens.example.org/" is the URL of that page,
"x-meow" is the string that was passed to the registerProtocolHandler()
method as its first argument (protocol),
"http://kittens.example.org/?show=%s" was the second argument (url), and "Kittens-at-work displayer" was the third
argument (title).
If the user clicks the Cancel button, then nothing further
happens. If the user clicks the "Trust" button, then the handler is
remembered.
When the user then attempts to fetch a URL that uses the
"x-meow:" scheme, then it might display a dialog as follows:
||[ Unknown Protocol ]||||||||||||||||||||||||||||||||||||||||
| |
| You have attempted to access: |
| |
| x-meow:S2l0dGVucyBhcmUgdGhlIGN1dGVzdCE%3D |
| |
| How would you like FerretBrowser to handle this resource? |
| |
| (o) Contact the FerretBrowser plugin registry to see if |
| there is an official way to handle this resource. |
| |
| ( ) Pass this URL to a local application: |
| [ /no application selected/ ] ( Choose ) |
| |
| ( ) Pass this URL to the "Kittens-at-work displayer" |
| application at "kittens.example.org". |
| |
| [ ] Always do this for resources using the "x-meow" |
| protocol in future. |
| |
| ( Ok ) (( Cancel )) |
|____________________________________________________________|
...where the third option is the one that was primed by the site
registering itself earlier.
If the user does select that option, then the browser, in
accordance with the requirements described in the previous two
sections, will redirect the user to
"http://kittens.example.org/?show=x-meow%3AS2l0dGVucyBhcmUgdGhlIGN1dGVzdCE%253D".
The registerContentHandler()
method would work equivalently, but for unknown MIME types instead
of unknown protocols.
5.7 Offline Web applications5.7 オフライン Web アプリケーション
5.7.1 Introduction5.7.1 はじめに
This section is non-normative.この節は規定の一部ではありません。
...
5.7.2 Application caches5.7.2 アプリケーション・キャッシュ
An application cache is a collection of resources. An
application cache is identified by the absolute URL of
a resource manifest which is used to populate the cache.
Application caches are versioned, and there can be different
instances of caches for the same manifest URL, each having a
different version. A cache is newer than another if it was created
after the other (in other words, caches in a group have a
chronological order).
Each group of application caches for the same manifest URL has a
common update status,
which is one of the following: idle, checking,
downloading.
Each group of application caches for the same manifest URL also
has a common lifecycle
status, which is one of the following: new,
mature, obsolete. A relevant application
cache is an application cache whose lifecycle status is
mature.
A browsing context is
associated with the application cache appropriate for its
active document, if any. A Document
initially has no appropriate cache, but steps in the parser and in the navigation sections cause cache selection
to occur early in the page load process. A browsing context's
associated cache can also change
during session history
traversal.
An application cache consists of:
-
One of more resources (including their out-of-band metadata,
such as HTTP headers, if any), identified by URLs, each falling
into one (or more) of the following categories:
- Master entries
- Documents that were added to the cache because a
browsing context was navigated to that document and the
document indicated that this was its cache, using the
manifest attribute.
- The manifest
- The resource corresponding to the URL that was given in an
master entry's
html element's manifest attribute. The
manifest is fetched and processed during the application
cache update process. All the master entries have
the same origin as the manifest.
- Explicit entries
- Resources that were listed in the cache's manifest. Explicit
entries can also be marked as foreign, which means that they
have a
manifest
attribute but that it doesn't point at this cache's manifest.
- Fallback entries
- Resources that were listed in the cache's manifest as fallback
entries.
- Dynamic entries
- Resources that were added to the cache by the
add() method.
A URL in the list can be flagged with multiple
different types, and thus an entry can end up being categorized as
multiple entries. For example, an entry can be an explicit entry
and a dynamic entry at the same time.
Zero or more fallback
namespaces: URLs, used as prefix match
patterns, each of which is mapped to a fallback entry. Each
namespace URL has the same origin as the manifest.
Zero or more URLs that form the online whitelist
namespaces.
Multiple application caches can contain the same resource,
e.g. if their manifests all reference that resource. If the user
agent is to select an
application cache from a list of relevant application caches that contain a
resource, that the user agent must use the application cache that
the user most likely wants to see the resource from, taking into
account the following:
which application cache was most recently updated,
which application cache was being used to display the
resource from which the user decided to look at the new resource,
and
which application cache the user prefers.
5.7.3 The cache manifest syntax
5.7.3.1 A sample manifest
This section is non-normative.この節は規定の一部ではありません。
This example manifest requires two images and a style sheet to be
cached and whitelists a CGI script.
CACHE MANIFEST
# the above line is required
# this is a comment
# there can be as many of these anywhere in the file
# they are all ignored
# comments can have spaces before them
# but most be alone on the line
# blank lines are ignored too
# these are files that need to be cached they can either be listed
# first, or a "CACHE:" header could be put before them, as is done
# lower down.
images/sound-icon.png
images/background.png
# note that each file has to be put on its own line
# here is a file for the online whitelist -- it isn't cached, and
# references to this file will bypass the cache, always hitting the
# network (or trying to, if the user is offline).
NETWORK:
comm.cgi
# here is another set of files to cache, this time just the CSS file.
CACHE:
style/default.css
5.7.3.2 Writing cache manifests
Manifests must be served using the text/cache-manifest MIME type. All resources served
using the text/cache-manifest MIME type must
follow the syntax of application cache manifests, as described in
this section.
An application cache manifest is a text file, whose text is
encoded using UTF-8. Data in application cache manifests is
line-based. Newlines must be represented by U+000A LINE FEED (LF)
characters, U+000D CARRIAGE RETURN (CR) characters, or U+000D
CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs.
This is a willful double violation of RFC2046. [RFC2046]
The first line of an application cache manifest must consist of
the string "CACHE", a single U+0020 SPACE character, the string
"MANIFEST", and zero or more U+0020 SPACE and U+0009 CHARACTER
TABULATION (tab) characters. The first line may optionally be
preceded by a U+FEFF BYTE ORDER MARK (BOM) character. If any other
text is found on the first line, the user agent will ignore the
entire file.
Subsequent lines, if any, must all be one of the following:
- A blank line
-
Blank lines must consist of zero or more U+0020 SPACE and
U+0009 CHARACTER TABULATION (tab) characters only.
- A comment
-
Comment lines must consist of zero or more U+0020 SPACE and
U+0009 CHARACTER TABULATION (tab) characters, followed by a single
U+0023 NUMBER SIGN (#) character, followed by zero or more
characters other than U+000A LINE FEED (LF) and U+000D CARRIAGE
RETURN (CR) characters.
Comments must be on a line on their own. If they
were to be included on a line with a URL, the "#" would be
mistaken for part of a fragment identifier.
- A section header
-
Section headers change the current section. There are three
possible section headers:
CACHE:
- Switches to the explicit section.
FALLBACK:
- Switches to the fallback section.
NETWORK:
- Switches to the online whitelist section.
Section header lines must consist of zero or more U+0020 SPACE
and U+0009 CHARACTER TABULATION (tab) characters, followed by one
of the names above (including the U+003A COLON (:) character)
followed by zero or more U+0020 SPACE and U+0009 CHARACTER
TABULATION (tab) characters.
Ironically, by default, the current section is the explicit
section.
- Data for the current section
-
The format that data lines must take depends on the current
section.
When the current section is the explicit section or the online
whitelist section, data lines must consist of zero or more U+0020
SPACE and U+0009 CHARACTER TABULATION (tab) characters, a
valid URL identifying a resource other than the
manifest itself, and then zero or more U+0020 SPACE and U+0009
CHARACTER TABULATION (tab) characters.
When the current section is the fallback section, data lines
must consist of zero or more U+0020 SPACE and U+0009 CHARACTER
TABULATION (tab) characters, a valid URL identifying
a resource other than the manifest itself, one or more U+0020
SPACE and U+0009 CHARACTER TABULATION (tab) characters, another
valid URL identifying a resource other than the
manifest itself, and then zero or more U+0020 SPACE and U+0009
CHARACTER TABULATION (tab) characters.
The URLs in data lines can't be empty strings,
since those would be relative URLs to the manifest itself. Such
lines would be confused with blank or invalid lines, anyway.
Manifests may contain sections more than once. Sections may be
empty.
URLs that are to be fallback pages associated with fallback namespaces, and
those namespaces themselves, must be given in fallback sections,
with the namespace being the first URL of the data line, and the
corresponding fallback page being the second URL. All the other
pages to be cached must be listed in explicit sections.
Fallback
namespaces and fallback entries must have
the same origin as the manifest itself.
A fallback
namespace must not be listed more than once.
URLs that the user agent is to put into the online whitelist
must all be specified in online whitelist sections. (This is needed
for any URL that the page is intending to use to communicate back to
the server.)
Relative URLs must be given relative to the manifest's own
URL.
URLs in manifests must not have fragment identifiers (i.e. the
U+0023 NUMBER SIGN character isn't allowed in URLs in
manifests).
5.7.3.3 Parsing cache manifests
When a user agent is to parse a manifest, it means
that the user agent must run the following steps:
The user agent must decode the byte stream corresponding with
the manifest to be parsed, treating it as UTF-8. Bytes or sequences
of bytes that are not valid UTF-8 sequences must be interpreted as
a U+FFFD REPLACEMENT CHARACTER.
Let explicit URLs be an initially empty
list of explicit
entries.
Let fallback URLs be an initially empty
mapping of fallback
namespaces to fallback entries.
Let online whitelist URLs be an
initially empty list of URLs for a online
whitelist.
Let input be the decoded text of the
manifest's byte stream.
Let position be a pointer into input, initially pointing at the first
character.
If position is pointing at a U+FEFF BYTE
ORDER MARK (BOM) character, then advance position to the next character.
If the characters starting from position
are "CACHE", followed by a U+0020 SPACE character, followed by
"MANIFEST", then advance position to the next
character after those. Otherwise, this isn't a cache manifest;
abort this algorithm with a failure while checking for the magic
signature.
Collect a sequence of characters that are
U+0020 SPACE or U+0009 CHARACTER TABULATION (tab)
characters.
If position is not past the end of input and the character at position is neither a U+000A LINE FEED (LF)
characters nor a U+000D CARRIAGE RETURN (CR) character, then this
isn't a cache manifest; abort this algorithm with a failure while
checking for the magic signature.
This is a cache manifest. The algorithm cannot fail beyond
this point (though bogus lines can get ignored).
Let mode be "explicit".
Start of line: If position is
past the end of input, then jump to the last
step. Otherwise, collect a sequence of characters that
are U+000A LINE FEED (LF), U+000D CARRIAGE RETURN (CR), U+0020
SPACE, or U+0009 CHARACTER TABULATION (tab) characters.
Now, collect a sequence of characters that are
not U+000A LINE FEED (LF) or U+000D CARRIAGE RETURN (CR)
characters, and let the result be line.
Drop any trailing U+0020 SPACE and U+0009 CHARACTER
TABULATION (tab) characters at the end of line.
If line is the empty string, then jump
back to the step labeled "start of line".
If the first character in line is a
U+0023 NUMBER SIGN (#) character, then jump back to the step
labeled "start of line".
If line equals "CACHE:" (the word
"CACHE" followed by a U+003A COLON (:) character), then set mode to "explicit" and jump back to the step
labeled "start of line".
If line equals "FALLBACK:" (the word
"FALLBACK" followed by a U+003A COLON (:) character), then set mode to "fallback" and jump back to the step
labeled "start of line".
If line equals "NETWORK:" (the word
"NETWORK" followed by a U+003A COLON (:) character), then set mode to "online whitelist" and jump back to the step
labeled "start of line".
If line ends with a U+003A COLON (:)
character, then set mode to "unknown" and jump
back to the step labeled "start of line".
This is either a data line or it is syntactically
incorrect.
Let position be a pointer into line, initially pointing at the start of the
string.
Let tokens be a list of strings,
initially empty.
-
While position doesn't point past the end
of line:
Let current token be an empty
string.
While position doesn't point past the
end of line and the character at position is neither a U+0020 SPACE nor a U+0009
CHARACTER TABULATION (tab) character, add the character at position to current token and
advance position to the next character in
input.
Add current token to the tokens list.
While position doesn't point past the
end of line and the character at position is either a U+0020 SPACE or a U+0009
CHARACTER TABULATION (tab) character, advance position to the next character in input.
-
Process tokens as follows:
- If mode is "explicit"
-
Resolve the first item in
tokens; ignore the rest.
If this fails, then jump back to the step labeled "start of
line".
If the resulting absolute URL has a different
<scheme> component than
the manifest's URL (compared in an ASCII
case-insensitive manner), then jump back to the step
labeled "start of line".
Drop the <fragment>
component of the resulting absolute URL, if it has
one.
Add the resulting absolute URL to the explicit URLs.
- If mode is "fallback"
-
Let part one be the first token in tokens, and let part two be
the second token in tokens.
Resolve part
one and part two.
If either fails, then jump back to the step labeled "start of
line".
If the absolute URL corresponding to either part one or part two does not
have the same origin as the manifest's URL, then
jump back to the step labeled "start of line".
Drop any the <fragment> components of the
resulting absolute URLs.
If the absolute URL corresponding to part one is already in the fallback
URLs mapping as a fallback namespace,
then jump back to the step labeled "start of line".
Otherwise, add the absolute URL corresponding to
part one to the fallback
URLs mapping as a fallback namespace,
mapped to the absolute URL corresponding to part two as the fallback entry.
- If mode is "online whitelist"
-
Resolve the first item in
tokens; ignore the rest.
If this fails, then jump back to the step labeled "start of
line".
If the resulting absolute URL has a different
<scheme> component than
the manifest's URL (compared in an ASCII
case-insensitive manner), then jump back to the step
labeled "start of line".
Drop the <fragment>
component of the resulting absolute URL, if it has
one.
Add the resulting absolute URL to the online whitelist URLs.
- If mode is "unknown"
-
Do nothing. The line is ignored.
Jump back to the step labeled "start of line". (That step
jumps to the next, and last, step when the end of the file is
reached.)
Return the explicit URLs list, the fallback URLs mapping, and the online
whitelist URLs.
If a resource is listed in the explicit section and
matches an entry in the online whitelist, or if a resource matches
both an entry in the fallback section and the online whitelist, the
resource will taken from the cache, and the online whitelist entry
will be ignored.
5.7.4 Updating an application cache
When the user agent is required (by other parts of this
specification) to start the application cache update
process for a manifest URL or for an
application cache, potentially given a particular
browsing context, and potentially given a new master resource, the user
agent must run the following steps:
the event stuff needs to be more consistent --
something about showing every step of the ui or no steps or
something; and we need to deal with showing ui for browsing contexts
that open when an update is already in progress, and we may need to
give applications control over the ui the first time they cache
themselves (right now the original cache is done without
notifications to the browsing contexts); also, we need to update
this so all event firing uses queues
-
Atomically, so as to avoid race conditions, perform the
following substeps:
Let manifest URL be the URL of the
manifest to be
updated, or of the manifest of the
application cache to be updated, as
appropriate.
If these steps were invoked with a URL (as opposed to a
specific cache), and there is no application cache
identified by manifest URL whose lifecycle status is not
obsolete, then create a new application cache
identified with that URL and set the group's lifecycle status to
new.
If these steps were invoked
with a new master
resource, then flag the resource's Document as a
candidate for this manifest URL's caches, so that it will be associated with an
application cache identified by this manifest URL later, when
such an application cache is ready.
Let cache group be the group of application caches identified by
manifest URL.
Let cache be the most recently updated
application cache identified by manifest
URL (that is, the newest version found in cache
group).
If these steps were invoked with a browsing
context, and the status of the cache group is checking or
downloading, then fire a simple event called
checking at the
ApplicationCache singleton of that browsing
context.
If these steps were invoked with a browsing
context, and the status of the cache group is downloading, then also
fire a simple event called downloading at the
ApplicationCache singleton of that browsing
context.
If the status
of the cache group is either checking
or downloading, then abort this instance of the update
process, as an update is already in progress for them.
Set the status of this group of
caches to checking.
The remainder of the steps run asychronously.
-
If there is already a resource with the URL of manifest URL in cache, and
that resource is categorized as a manifest, then this is an
upgrade
attempt. Otherwise, this is a cache attempt.
If this is a cache attempt, then cache is forcibly the only application cache in
cache group, and it hasn't ever been populated
from its manifest (i.e. this update is an attempt to download the
application for the first time). It also can't have any browsing
contexts associated with it.
-
Fire a simple event called checking at the
ApplicationCache singleton of each browsing
context whose active document is associated
with a cache in cache group. The default
action of this event should be the display of some sort of user
interface indicating to the user that the user agent is checking
for the availability of updates.
Again, if this is a cache attempt, then cache group has only one cache and it has no
browsing contexts associated with it, so no events are dispatched
due to this step or any of the other steps that fire events other
than the final cached event.
-
Fetch the resource from manifest
URL, and let manifest be that
resource.
If the resource is labeled with the MIME type text/cache-manifest, parse manifest according to the rules for parsing manifests, obtaining a list of
explicit entries,
fallback entries
and the fallback
namespaces that map to them, and entries for the online
whitelist.
-
If the previous step fails due to a 404 or 410 response or equivalent, then
run the cache removal steps
If the previous step fails in some other way (e.g. the server
returns another 4xx or 5xx response or equivalent, or
there is a DNS error, or the connection times out, or the user
cancels the download, or the parser for manifests fails when
checking the magic signature), or if the server returned a
redirect, or if the resource is labeled with a MIME type other
than text/cache-manifest, then run the
cache failure steps.
-
If this is an upgrade
attempt and the newly downloaded manifest is byte-for-byte identical to the manifest
found in cache, or if the server reported it
as "304 Not Modified" or equivalent, then
run these substeps:
Fire a simple event called noupdate at the
ApplicationCache singleton of each browsing
context whose active document is associated
with a cache in cache group. The default
action of this event should be the display of some sort of user
interface indicating to the user that the application is up to
date.
If there are any pending downloads of master entries that are
being stored in the cache, then wait for all of them to have
completed. If any of these downloads fail (e.g. the server
returns a 4xx or 5xx response or equivalent, or
there is a DNS error, or the connection times out, or the user
cancels the download), then run the cache failure
steps.
Let the status of the group of
caches to which cache belongs be
idle. If appropriate, remove any user interface indicating
that an update for this cache is in progress.
Abort the update process.
Set the status
of cache group to downloading.
Fire a simple event called downloading at the
ApplicationCache singleton of each browsing
context whose active document is associated
with a cache in cache group. The default action
of this event should be the display of some sort of user interface
indicating to the user that a new version is being
downloaded.
If this is an upgrade
attempt, then let new cache be a newly
created application cache identified by manifest URL, being a new version in cache group. Otherwise, let new
cache and cache be the same version of
the application cache.
Let file list be an empty list of
URLs with flags.
Add all the URLs in the list of explicit entries obtained
by parsing manifest to file
list, each flagged with "explicit entry".
Add all the URLs in the list of fallback entries obtained
by parsing manifest to file
list, each flagged with "fallback entry".
If this is an upgrade
attempt, then add all the URLs of master entries in cache to file list, each flagged
with "master entry".
If this is an upgrade
attempt, then add all the URLs of dynamic entries in cache to file list, each flagged
with "dynamic entry".
If any URL is in file list more than
once, then merge the entries into one entry for that URL, that
entry having all the flags that the original entries had.
-
For each URL in file list, run the
following steps. These steps may be run in parallel for two or
more of the URLs at a time.
-
If the resource URL being processed was flagged as neither an
"explicit entry" nor or a "fallback entry", then the user agent
may skip this URL.
This is intended to allow user agents to expire
resources (other than those in the manifest itself) from the
cache. Generally, implementors are urged to use an approach that
expires lesser-used resources first.
Fire a simple event called progress at the
ApplicationCache singleton of each browsing
context whose active document is associated
with a cache in cache group. The default
action of this event should be the display of some sort of user
interface indicating to the user that a file is being downloaded
in preparation for updating the application.
-
Fetch the resource. If this is an upgrade attempt, then
use cache as an HTTP cache, and honor HTTP
caching semantics (such as expiration, ETags, and so forth) with
respect to that cache. User agents may also have other caches in
place that are also honored.
If the resource in question is already being
downloaded for other reasons then the existing download process
can be used for the purposes of this step, as defined by the
fetching algorithm.
An example of a resource that might already
be being downloaded is a large image on a Web page that is being
seen for the first time. The image would get downloaded to
satisfy the img element on the page, as well as
being listed in the cache manifest. According to the rules for
fetching that image only need be
downloaded once, and it can be used both for the cache and for
the rendered Web page.
-
If the previous step fails (e.g. the server returns a 4xx or
5xx response or
equivalent, or there is a DNS error, or the connection
times out, or the user cancels the download), or if the server
returned a redirect, then run the first appropriate step from
the following list:
- If the URL being processed was flagged as an "explicit
entry" or a "fallback entry"
-
Run the cache failure steps.
Redirects are fatal because they are either
indicative of a network problem (e.g. a captive portal); or
would allow resources to be added to the cache under URLs that
differ from any URL that the networking model will allow
access to, leaving orphan entries; or would allow resources to
be stored under URLs different than their true URLs. All of
these situations are bad.
- If the error was a 404 or 410 HTTP response or equivalent
-
Skip this resource. It is dropped from the cache.
- Otherwiseそれ以外の場合
-
Copy the resource and its metadata from cache, and act as if that was the fetched
resource, ignoring the resource obtained from the network.
User agents may warn the user of these errors as an aid to
development.
These rules make errors for resources listed in
the manifest fatal, while making it possible for other resources
to be removed from caches when they are removed from the server,
without errors, and making non-manifest resources survive
server-side errors.
Otherwise, the fetching succeeded. Store the resource in
the new cache.
If the URL being processed was flagged as an "explicit
entry" in file list, then categorize the
entry as an explicit
entry.
If the URL being processed was flagged as a "fallback
entry" in file list, then categorize the
entry as a fallback
entry.
If the URL being processed was flagged as an "master
entry" in file list, then categorize the
entry as a master
entry.
If the URL being processed was flagged as an "dynamic
entry" in file list, then categorize the
entry as a dynamic
entry.
As an optimization, if the resource is an HTML or XML file
whose root element is an html element with a manifest attribute whose value
doesn't match the manifest URL of the application cache being
processed, then the user agent should mark the entry as being
foreign.
Store the list of fallback namespaces,
and the URLs of the fallback entries that they
map to, in new cache.
Store the URLs that form the new online whitelist in
new cache.
-
Wait for all pending downloads of master entries that are
being stored in the cache to have completed.
For example, if the browsing
context's active document isn't itself listed
in the cache manifest, then it might still be being
downloaded.
If any of these downloads fail (e.g. the connection times out,
or the user cancels the download), then run the cache
failure steps.
-
Fetch the resource from manifest
URL again, and let second manifest be
that resource.
-
If the previous step failed for any reason, or if the fetching
attempt involved a redirect, or if second
manifest and manifest are not
byte-for-byte identical, then schedule a rerun of the entire
algorithm with the same parameters after a short delay, and run
the cache failure steps.
-
Otherwise, store manifest in new cache, if it's not there already, and
categorize this entry (whether newly added or not) as the manifest.
-
If this is a cache
attempt, then:
Associate any
Document objects that were flagged as candidates for this
manifest URL's caches with cache.
Fire a simple event called cached at the
ApplicationCache singleton of each browsing
context whose active document is associated
with a cache in cache group. The default
action of this event should be the display of some sort of user
interface indicating to the user that the application has been
cached and that they can now use it offline.
Set the lifecycle
status of cache group to
mature.
Set the update
status of cache group to
idle.
-
Otherwise, this is an upgrade attempt:
Fire a simple event called updateready at the
ApplicationCache singleton of each browsing
context whose active document is associated
with a cache in cache group. The default
action of this event should be the display of some sort of user
interface indicating to the user that a new version is available
and that they can activate it by reloading the page.
Set the status of
cache group to idle.
The cache removal steps are as follows:
If this is a cache
attempt, then discard cache and abort
the update process.
Fire a simple event called obsolete at the
ApplicationCache singleton of each browsing
context whose active document is associated
with a cache in cache group. The default action
of this event should be the display of some sort of user interface
indicating to the user that the application is no longer available
for offline use.
Set the lifecycle
status of cache group to
obsolete.
Let the update
status of the group of caches to which cache belongs be idle. If appropriate, remove
any user interface indicating that an update for this cache is in
progress. Abort the update process.
The cache failure steps are as follows:
Fire a simple event called error at the
ApplicationCache singleton of each browsing
context whose active document is associated
with a cache in cache group. The default action
of this event should be the display of some sort of user interface
indicating to the user that the user agent failed to save the
application for offline use.
If this is a cache
attempt, then discard cache and abort
the update process.
Otherwise, let the status of the group of
caches to which cache belongs be
idle. If appropriate, remove any user interface indicating
that an update for this cache is in progress. Abort the update
process.
User agents may invoke the application cache update
process, in the background, for any application
cache, at any time (with no browsing
context). This allows user agents to keep caches primed and
to update caches even before the user visits a site.
5.7.5 Processing model5.7.5 処理モデル
The processing model of application caches for offline support in
Web applications is part of the navigation model, but references the
algorithms defined in this section.
A URL matches a
fallback namespace if there exists a relevant
application cache whose manifest's URL has the
same origin as the URL in question, and that has a
fallback namespace
that is a prefix match for the URL being examined. If
multiple fallback namespaces match the same URL, the longest one is
the one that matches. A URL looking for an fallback namespace can
match more than one application cache at a time, but only matches
one namespace in each cache.
If a manifest http://example.com/app1/manifest declares that
http://example.com/resources/images is a
fallback namespace, and the user navigates to HTTP://EXAMPLE.COM:80/resources/images/cat.png,
then the user agent will decide that the application cache
identified by http://example.com/app1/manifest contains a
namespace with a match for that URL.
When the application cache
selection algorithm algorithm is invoked with a manifest URL,
the user agent must run the first applicable set of steps from the
following list:
- If the resource is not being loaded as part of navigation of a
browsing context
-
Do nothing.
- If the resource being loaded was loaded from an application
cache and the URL of that application cache's manifest is the
same as the manifest URL with which the algorithm was invoked
-
Associate the Document with the cache from which
it was loaded. Invoke the application cache update
process for that cache and with the browsing
context being navigated.
- If the resource being loaded was loaded from an application
cache and the URL of that application cache's manifest is
not the same as the manifest URL with which the algorithm
was invoked
-
Mark the entry for this resource in the application cache from
which it was loaded as foreign.
Restart the current navigation from the top of the navigation algorithm, undoing any changes
that were made as part of the initial load (changes can be avoided
by ensuring that the step to update the session history with
the new page is only ever completed after the
application cache selection algorithm is run, though this is not
required).
The navigation will not result in the same
resource being loaded, because "foreign" entries are never picked
during navigation.
User agents may notify the user of the inconsistency between
the cache manifest and the resource's own metadata, to aid in
application development.
- If the resource being loaded was not loaded from an application
cache, but it was loaded using HTTP GET or equivalent
-
If the manifest URL does not have the same
origin as the resource's own URL, then invoke the application cache
selection algorithm again, but without a manifest, and
abort these steps.
Otherwise, invoke the application cache update
process for the given manifest URL, with the
browsing context being navigated, and with the
resource's Document as the new master
resource.
- Otherwiseそれ以外の場合
-
Invoke the application cache
selection algorithm again, but without a manifest.
When the application cache
selection algorithm is invoked without a manifest, if
the resource is being loaded as part of navigation of a
browsing context, and the resource was fetched from a
particular application cache, then the user agent must
associate the Document with that application cache and
invoke the application cache update process for that
cache, with that browsing context. Otherwise, nothing
special happens.
5.7.5.1 Changes to the networking model
When a browsing context is associated with an
application cache, any and all loads for resources in
that browsing context other than those for child browsing contexts must
go through the following steps instead of immediately invoking the
mechanisms appropriate to that resource's scheme:
If the resource is not to be fetched using the HTTP GET
mechanism or
equivalent, or if it has a javascript: URL, then
fetch the resource normally and abort these
steps.
If the resource's URL is an master entry, the manifest, an explicit entry, a fallback entry, or a
dynamic entry in the
application cache, then get the resource from the
cache (instead of fetching it), and abort these steps.
-
If the resource's URL has the same origin as the
manifest's URL, and there is a fallback namespace in
the application cache that is a prefix
match for the resource's URL, then:
Fetch the resource normally. If this results in a
redirect to a resource with another origin
(indicative of a captive portal), or a 4xx or 5xx status code
or equivalent,
or if there were network errors (but not if the user canceled the
download), then instead get, from the cache, the resource of the
fallback entry
corresponding to the matched namespace. Abort these steps.
If there is an entry in the application cache's
online
whitelist that has the same origin as the
resource's URL and that is a prefix match for the
resource's URL, then fetch the resource normally and
abort these steps.
Fail the resource load.
The above algorithm ensures that resources that are
not present in the manifest will always fail to load (at least,
after the cache has been primed the first time), making the testing
of offline applications simpler.
5.7.6 Application cache API5.7.6 アプリケーション・キャッシュ API
interface ApplicationCache {
// update status
const unsigned short UNCACHED = 0;
const unsigned short IDLE = 1;
const unsigned short CHECKING = 2;
const unsigned short DOWNLOADING = 3;
const unsigned short UPDATEREADY = 4;
const unsigned short OBSOLETE = 5;
readonly attribute unsigned short status;
// updates
void update();
void swapCache();
// dynamic entries
readonly attribute DOMStringList items;
boolean hasItem(in DOMString url);
void add(in DOMString url);
void remove(in DOMString url);
// events
attribute EventListener onchecking;
attribute EventListener onerror;
attribute EventListener onnoupdate;
attribute EventListener ondownloading;
attribute EventListener onprogress;
attribute EventListener onupdateready;
attribute EventListener oncached;
attribute EventListener onobsolete;
};
Objects implementing the ApplicationCache interface
must also implement the EventTarget interface.
There is a one-to-one mapping from Document objects
to ApplicationCache objects. The applicationCache
attribute on Window objects must return the
ApplicationCache object associated with the
active document of the Window's
browsing context.
An ApplicationCache object might be associated with
an application cache. When the Document
object that the ApplicationCache object maps to is
associated with an application cache, then that is the application
cache with which the ApplicationCache object is
associated.
The status
attribute, on getting, must return the current state of the
application cache ApplicationCache object
is associated with, if any. This must be the appropriate value from
the following list:
UNCACHED
(numeric value 0)UNCACHED (数値 0)The ApplicationCache object is not associated
with an application cache at this time.
IDLE
(numeric value 1)IDLE (数値 1)The ApplicationCache object is associated with
an application cache whose group is in the idle
update status and the
mature lifecycle
status and that application cache is the newest cache in its
group.
CHECKING
(numeric value 2)CHECKING (数値 2)The ApplicationCache object is associated with
an application cache whose group is in the
checking update
status.
DOWNLOADING
(numeric value 3)DOWNLOADING (数値 3)The ApplicationCache object is associated with
an application cache whose group is in the
downloading update
status.
UPDATEREADY
(numeric value 4)UPDATEREADY (数値 4)The ApplicationCache object is associated with
an application cache whose group is in the idle
update status and the
mature lifecycle
status but that application cache is not the newest
cache in its group.
OBSOLETE
(numeric value 5)OBSOLETE (数値 5)The ApplicationCache object is associated with
an application cache whose group is in the
obsolete lifecycle
status.
The dynamic entries
in the application cache are ordered in the same order
as they were added to the cache by the add() method, with the oldest entry
being the zeroth entry.
The items DOM
attribute must return a new DOMStringList object. If
the ApplicationCache object has an associated
application cache with one or more dynamic entries, then the
DOMStringList object's items must be the absolute URLs of the dynamic entries in that
application cache, in order; otherwise, the object must
have no entries.
The hasItem(url) method must run the following
steps:
If the ApplicationCache object is not
associated with any application cache, then raise an
INVALID_STATE_ERR exception and abort these
steps.
Resolve the url argument. If this fails, raise a
SYNTAX_ERR exception and abort these steps.
If there is already a resource in in the application
cache with which the ApplicationCache object is
associated that has the address url, and that
entry is categorized as a dynamic entry, then return
true.
Otherwise, return false.
The add(url) method must run the following
steps:
If the ApplicationCache object is not
associated with any application cache, then raise an
INVALID_STATE_ERR exception and abort these
steps.
Resolve the url argument. If this fails, raise a
SYNTAX_ERR exception and abort these steps.
If there is already a resource in in the application
cache with which the ApplicationCache object is
associated that has the address url, then
ensure that entry is categorized as a dynamic entry and return
and abort these steps.
If url has a different <scheme> component than the
manifest's URL, then raise a SECURITY_ERR
exception.
Return, but do not abort these steps.
Fetch the resource referenced by url.
If this results in a redirect, or a 4xx or 5xx status code
or equivalent,
or if there were network errors, or if the user canceled the
download, then abort these steps.
Add the fetched resource to the application
cache and categorize it as a dynamic entry.
The remove(url) method must resolve the url argument and, if
that is successful, remove the dynamic entry categorization
of any entry whose address is the resulting absolute
URL in the application cache with which the
ApplicationCache object is associated. If this removes
the last categorization of an entry in that cache, then the entry
must be removed entirely (such that if it is re-added, it will be
loaded from the network again). If the ApplicationCache
object is not associated with any application cache, then the method
must raise an INVALID_STATE_ERR exception instead.
Authors should bear in mind that multiple scripts
could be simultaneously modifying the same application cache.
If the update() method is
invoked, the user agent must invoke the application cache
update process, in the background, for the application
cache with which the ApplicationCache object is
associated, but with no browsing context. If there is
no such application cache, then the method must raise an
INVALID_STATE_ERR exception instead.
If the swapCache() method
is invoked, the user agent must run the following steps:
Let document be the
Document with which the ApplicationCache
object is associated.
-
Check that document is associated with an
application cache. If it is not, then raise an
INVALID_STATE_ERR exception and abort these
steps.
This is not the same thing as the
ApplicationCache object being itself associated with
an application cache! In particular, the
Document with which the ApplicationCache
object is associated can only itself be associated with an
application cache if it is in a top-level browsing
context.
Let cache be the application
cache with which the ApplicationCache object is
associated. (By definition, this is the same as the one that was
found in the previous step.)
If the group of application
caches to which cache belongs has the
lifecycle status
obsolete, unassociate document from cache and abort these steps.
Otherwise, check that there is an application cache in the
same group as cache which has an entry
categorized as a manifest that is newer
than cache. If there is not, then raise an
INVALID_STATE_ERR exception and abort these
steps.
Let new cache be the newest
application cache in the same group as cache which has an entry categorized as a manifest.
Unassociate document from cache and instead associate it with new cache.
The following are the event handler DOM attributes
that must be supported by objects implementing the
ApplicationCache interface:
oncheckingMust be invoked whenever an checking event is targeted at or
bubbles through the ApplicationCache object.
onerrorMust be invoked whenever an error event is targeted at or bubbles
through the ApplicationCache object.
onnoupdateMust be invoked whenever an noupdate event is targeted at or
bubbles through the ApplicationCache object.
ondownloadingMust be invoked whenever an downloading event is targeted at
or bubbles through the ApplicationCache
object.
onprogressMust be invoked whenever an progress event is targeted at or
bubbles through the ApplicationCache object.
onupdatereadyMust be invoked whenever an updateready event is targeted at
or bubbles through the ApplicationCache
object.
oncachedMust be invoked whenever a cached event is targeted at or bubbles
through the ApplicationCache object.cached 事象が当該 ApplicationCache オブジェクトを対象としているか、泡立って当該オブジェクトを通過する時に、
呼び出されなければなりません。
onobsoleteMust be invoked whenever an obsolete event is targeted at or bubbles
through the ApplicationCache object.
5.7.7 Browser state5.7.7 ブラウザー状態
The navigator.onLine
attribute must return false if the user agent will not contact the
network when the user follows links or when a script requests a
remote page (or knows that such an attempt would fail), and must
return true otherwise.
When the value that would be returned by the navigator.onLine attribute of
the Window changes from true to false, the user agent
must fire a simple event called offline at the body
element.
On the other hand, when the value that would be returned by the
navigator.onLine attribute
of the Window changes from false to true, the user
agent must fire a simple event called online at the body
element.
5.8 Session history and navigation5.8 セッション履歴とナビゲーション
5.8.1 The session history of browsing contexts5.8.1 閲覧文脈のセッション履歴
The sequence of Documents in a browsing
context is its session history.
History objects provide a representation of the
pages in the session history of browsing contexts. Each browsing context has a
distinct session history.
Each Document object in a browsing context's session
history is associated with a unique instance of the
History object, although they all must model the same
underlying session history.
The history attribute
of the Window interface must return the object
implementing the History interface for that
Window object's active document.
History objects represent their browsing
context's session history as a flat list of session history entries. Each
session history entry consists of either a
URL or a state object, or both, and may in
addition have a title, a Document object, form data, a
scroll position, and other information associated with it.
This does not imply that the user interface need be
linear. See the notes below.
URLs without associated state
objects are added to the session history as the user (or
script) navigates from page to page.
A state object is an object representing a user
interface state.
Pages can add state objects between their entry in the
session history and the next ("forward") entry. These are then returned to the script when the user
(or script) goes back in the history, thus enabling authors to use
the "navigation" metaphor even in one-page applications.
Every Document in the session history is defined to
have a last activated entry, which is the state
object entry associated with that Document which
was most recently activated. Initially, the last activated
entry of a Document must be the first entry for
the Document, representing the fact that no state
object entry has yet been activated.
At any point, one of the entries in the session history is the
current entry. This is the entry representing the
active document of the browsing
context. The current entry is usually an entry
for the location of the
Document. However, it can also be one of the entries
for state objects added to the
history by that document.
Entries that consist of state
objects share the same Document as the entry for
the page that was active when they were added.
Contiguous entries that differ just by fragment identifier also
share the same Document.
All entries that share the same
Document (and that are therefore merely different
states of one particular document) are contiguous by definition.
User agents may discard
the Document objects of entries other than the
current entry that are not referenced from any script,
reloading the pages afresh when the user or script navigates back to
such pages. This specification does not specify when user agents
should discard Document objects and when they should
cache them.
Entries that have had their Document objects
discarded must, for the purposes of the algorithms given below, act
as if they had not. When the user or script navigates back or
forwards to a page which has no in-memory DOM objects, any other
entries that shared the same Document object with it
must share the new object as well.
When state object entries are added, a URL can be provided. This
URL is used to replace the state object entry if the
Document is evicted.
When a user agent discards the Document object from
an entry in the session history, it must also discard all the
entries that share that Document but do not have an
associated URL (i.e. entries that only have a state
object). Entries that shared that Document
object but had a state object and have a different URL must then
have their state objects removed. Removed entries are not
recreated if the user or script navigates back to the page. If there
are no state object entries for that Document object
then no entries are removed.
5.8.2 The History interface5.8.2 History 界面
interface History {
readonly attribute long length;
void go(in long delta);
void go();
void back();
void forward();
void pushState(in DOMObject data, in DOMString title);
void pushState(in DOMObject data, in DOMString title, in DOMString url);
void clearState();
};
The length
attribute of the History interface must return the
number of entries in this session history.
The actual entries are not accessible from script.
The go(delta)
method causes the UA to move the number of steps specified by
delta in the session history.
If the index of the current entry plus
delta is less than zero or greater than or equal to the
number of items in the session
history, then the user agent must do nothing.
If the delta is zero, then the user agent must act as
if the location.reload()
method was called instead.
Otherwise, the user agent must cause the current browsing
context to traverse the history to the specified
entry. The specified entry is the one whose index equals the
index of the current entry plus delta.
When the user navigates through a browsing context,
e.g. using a browser's back and forward buttons, the user agent must
translate this action into the equivalent invocations of the history.go(delta)
method on the various affected window objects.
Some of the other members of the History interface
are defined in terms of the go()
method, as follows:
| Member成員 |
Definition定義 |
|---|
go() |
Must do the same as go(0)go(0) と同じことをしなければなりません。 |
back() |
Must do the same as go(-1)go(-1)
と同じことをしなければなりません。 |
forward() |
Must do the same as go(1)go(1)
と同じことをしなければなりません。 |
The pushState(data, title, url) method adds a state object to the
history.
When this method is invoked, the user agent must run the following steps:
-
If a third argument is specified, run these substeps:
Resolve the value of the
third argument.
If that fails, raise a SECURITY_ERR exception and
abort the pushState()
steps.
Compare the resulting absolute URL to the
document's address. If any part of these two URLs differ other than the <path>, <query>, and <fragment> components, then
raise a SECURITY_ERR exception and abort the pushState() steps.
For the purposes of the comparison in the above substeps, the
<path> and <query> components can only be the
same if the URLs use a hierarchical <scheme>.
Remove from the session history any entries for
the Document from the entry after the current
entry up to the last entry in the session history that
references the same Document object, if any. If the
current entry is the last entry in the session
history, or if there are no entries after the current
entry that reference the same Document object,
then no entries are removed.
Add a state object entry to the session history, after the
current entry, with the specified data as the state object, the given title as the title, and, if the third argument is
present, the absolute URL that was found in the first
step as the URL of the entry.
Set this new entry as being the last activated
entry for the Document.
Update the current entry to be the this newly
added entry.
The title is purely
advisory. User agents might use the title in the user interface.title は純粋に助言を与えるだけです。
利用者エージェントは利用者界面中でその題名を使うかもしれません。
User agents may limit the number of state objects added to the
session history per page. If a page hits the UA-defined limit, user
agents must remove the entry immediately after the first entry for
that Document object in the session history after
having added the new entry. (Thus the state history acts as a FIFO
buffer for eviction, but as a LIFO buffer for navigation.)
The clearState()
method removes all the state objects for the Document
object from the session history.
When this method is invoked, the user agent must remove from the
session history all the entries from the first state object entry
for that Document object up to the last entry that
references that same Document object, if any.
Then, if the current entry was removed in the
previous step, the current entry must be set to the
last entry for that Document object in the session
history.
5.8.3 Activating state object entries
When an entry in the session history is activated (which happens
during session traversal,
as described above), the user agent must run the following
steps:
First, the user agent must set this new entry as being the
last activated entry for the Document to
which the entry belongs.
If the entry is a state object entry, let state be that state object. Otherwise, the entry is
the first entry for the Document; let state be null.
The user agent must then fire a popstate event in no
namespace on the body element using the
PopStateEvent interface, with the state attribute set to the
value of state. This event bubbles but is not
cancelable and has no default action.
interface PopStateEvent : Event {
readonly attribute DOMObject state;
void initPopStateEvent(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMObject stateArg);
void initPopStateEventNS(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMObject stateArg);
};
The initPopStateEvent()
and initPopStateEventNS()
methods must initialize the event in a manner analogous to the
similarly-named methods in the DOM3 Events interfaces. [DOM3EVENTS]initPopStateEvent()
メソッドと initMessageEventNS()
メソッドは、 DOM3 事象界面の似たような名前のメソッドと同じような方法で事象を初期化しなければなりません。
[DOM3EVENTS]
The state
attribute represents the context information for the event, or null,
if the state represented is the initial state of the
Document.
Each Document object in a browsing
context's session history is associated with a unique
instance of a Location object.
The location attribute
of the HTMLDocument interface must return the
Location object for that Document object,
if it is in a browsing context, and null otherwise.
The location
attribute of the Window interface must return the
Location object for that Window object's
active document.
Location objects provide a representation of their document's address, and
allow the current entry of the browsing
context's session history to be changed, by adding or
replacing entries in the history
object.
interface Location {
readonly attribute DOMString href;
void assign(in DOMString url);
void replace(in DOMString url);
void reload();
// URL decomposition attributes
attribute DOMString protocol;
attribute DOMString host;
attribute DOMString hostname;
attribute DOMString port;
attribute DOMString pathname;
attribute DOMString search;
attribute DOMString hash;
// resolving relative URLs
DOMString resolveURL(in DOMString url);
};
The href
attribute must return the
address of the associated Document object, as an
absolute URL.
On setting, the user agent must act as if the assign() method had been called
with the new value as its argument.
When the assign(url) method is invoked, the UA must
navigate the browsing context to the
specified url.
When the replace(url) method is invoked, the UA must
navigate the browsing context to the
specified url with replacement
enabled.
Navigation for the assign() and replace() methods must be done
with the script browsing context of the script that
invoked the method as the source browsing context.
The Location interface also has the complement of
URL decomposition attributes, protocol, host, port, hostname, pathname, search, and hash. These must follow
the rules given for URL decomposition attributes, with the input being the address of the associated
Document object, as an absolute URL (same
as the href attribute), and
the common setter action
being the same as setting the href attribute to the new output
value.
The resolveURL(url) method must resolve its url argument, and if
that succeeds, return the resulting absolute URL. If it
fails, it must throw a SYNTAX_ERR exception
instead.
5.8.4.1 Security5.8.4.1 保安性
User agents must raise a SECURITY_ERR exception whenever
any of the members of a Location object are accessed by
scripts whose effective script origin is not the same as the Location
object's associated Document's effective script
origin, with the following exceptions:
User agents must not allow scripts to override the href attribute's setter.
5.8.5 Implementation notes for session history5.8.5 セッション履歴実装上の注意
This section is non-normative.この節は規定の一部ではありません。
The History interface is not meant to place
restrictions on how implementations represent the session history to
the user.
For example, session history could be implemented in a tree-like
manner, with each page having multiple "forward" pages. This
specification doesn't define how the linear list of pages in the
history object are derived from the
actual session history as seen from the user's perspective.
Similarly, a page containing two iframes has a history object distinct from the
iframes' history
objects, despite the fact that typical Web browsers present the user
with just one "Back" button, with a session history that interleaves
the navigation of the two inner frames and the outer page.
Security: It is suggested that to avoid letting
a page "hijack" the history navigation facilities of a UA by abusing
pushState(), the UA
provide the user with a way to jump back to the previous page
(rather than just going back to the previous state). For example,
the back button could have a drop down showing just the pages in the
session history, and not showing any of the states. Similarly, an
aural browser could have two "back" commands, one that goes back to
the previous state, and one that jumps straight back to the previous
page.
In addition, a user agent could ignore calls to pushState() that are invoked on
a timer, or from event handlers that do not represent a clear user
action, or that are invoked in rapid succession.
5.9 Browsing the Web5.9 Web の閲覧
5.9.1 Navigating across documents5.9.1 文書間のナビゲーション
Certain actions cause the browsing context to
navigate to a new resource. Navigation always involves
source browsing context, which is the browsing context
which was responsible for starting the navigation.
For example, following a hyperlink, form submission, and the window.open() and location.assign() methods can all
cause a browsing context to navigate.
A user agent may provide various ways for the user to explicitly
cause a browsing context to navigate, in addition to those defined
in this specification.
When a browsing context is navigated to a new resource, the user
agent must run the following steps:
If the source browsing
context is not the same as the browsing context
being navigated, and the source browsing context is
not one of the ancestor
browsing contexts of the browsing context being
navigated, and the source browsing context has its
sandboxed navigation browsing context flag set, then
abort these steps. The user agent may offer to open the new
resource in a new top-level browsing context or in the
top-level browsing context of the source
browsing context, at the user's option, in which case the
user agent must navigate that designated
top-level browsing context to the new resource as if
the user had requested it independently.
If the source browsing
context is the same as the browsing context
being navigated, and this browsing context has its seamless
browsing context flag set, then find the nearest
ancestor browsing context that does not have its
seamless browsing context flag set, and continue these
steps as if that browsing context was the one
that was going to be navigated
instead.
Cancel any preexisting attempt to navigate the
browsing context.
Resolve the URL
of the new resource. If that fails, the user agent may abort these
steps, or may treat the URL as identifying some sort of user-agent
defined error resource, which could display some sort of inline
content, or could be handled using a mechanism that does not affect
the browsing context.
Fragment identifiers: If
the absolute URL of the new resource is the same as
the address of the
active document of the browsing context
being navigated, ignoring any <fragment> components of those
URLs, and the new resource is to be
fetched using HTTP GET or
equivalent, then navigate to
that fragment identifier and abort these steps.
If the new resource is to be handled by displaying some sort
of inline content, e.g. an error message because the specified
scheme is not one of the supported protocols, or an inline prompt
to allow the user to select a registered
handler for the given scheme, then display the inline content and
abort these steps.
If the new resource is to be handled using a mechanism that
does not affect the browsing context, e.g. ignoring the navigation
request altogether because the specified scheme is not one of the
supported protocols, then abort these steps and proceed with that
mechanism instead.
-
If the new resource is to be fetched using HTTP GET or equivalent, then
check if there are any relevant application caches that are identified by a
URL with the same origin as the URL in question, and
that have this URL as one of their entries, excluding entries
marked as foreign. If so, then the
user agent must then get the resource from the most appropriate application
cache of those that match.
Otherwise, fetch the new resource. If this results
in a redirect, return to the step
labeled "fragment identifiers" with the new resource.
For example, imagine an HTML page with an
associated application cache displaying an image and a form, where
the image is also used by several other application caches. If the
user right-clicks on the image and chooses "View Image", then the
user agent could decide to show the image from any of those
caches, but it is likely that the most useful cache for the user
would be the one that was used for the aforementioned HTML
page. On the other hand, if the user submits the form, and the
form does a POST submission, then the user agent will not use an
application cache at all; the submission will be made to the
network.
-
If fetching the resource is synchronous (i.e. for javascript:
URLs and about:blank), then this must be
synchronous, but if fetching the resource depends on external
resources, as it usually does for URLs that use HTTP or other
networking protocols, then at this point the user agents must
yield to whatever script invoked the navigation steps, if they
were invoked by script.
Wait for one or more bytes to be available or for the user
agent to establish that the resource in question is empty. During
this time, the user agent may allow the user to cancel this
navigation attempt or start other navigation attempts.
-
If the resource was not fetched from an application
cache, and was to be fetched using HTTP GET or equivalent, and its
URL matches the
fallback namespace of one or more relevant application caches, and the
user didn't cancel the navigation attempt during the previous
step, and the navigation attempt failed (e.g. the server returned
a 4xx or 5xx status code or equivalent, or
there was a DNS error), then:
Let candidate be the fallback resource
specified for the fallback namespace in
question. If multiple application caches match, the user agent
must use the fallback of the most appropriate application
cache of those that match.
If candidate is not marked as foreign, then the user
agent must discard the failed load and instead continue along
these steps using candidate as the
resource.
For the purposes of session history (and features that depend
on session history, e.g. bookmarking) the user agent must use the
URL of the resource that was requested (the one that matched the
fallback
namespace), not the fallback resource, as the resource's
address. However, the
user agent may indicate to the user that the original page load
failed, that the page used was a fallback resource, and what the
URL of the fallback resource actually is.
If the document's out-of-band metadata (e.g. HTTP headers),
not counting any type information
(such as the Content-Type HTTP header), requires some sort of
processing that will not affect the browsing context, then perform
that processing and abort these steps.
Such processing might be triggered by, amongst other things, the
following:
HTTP 401 responses that do not include a challenge recognised
by the user agent must be processed as if they had no challenge,
e.g. rendering the entity body as if the response had been 200
OK.
User agents may show the entity body of an HTTP 401 response
even when the response do include a recognised challenge, with the
option to login being included in a non-modal fashion, to enable
the information provided by the server to be used by the user
before authenticating. Similarly, user agents should allow the
user to authenticate (in a non-modal fashion) against
authentication challenges included in other responses such as HTTP
200 OK responses, effectively allowing resources to present HTTP
login forms without requiring their use.
Let type be the sniffed type of the resource.
If the user agent has been configured to process resources
of the given type using some mechanism other
than rendering the content in a browsing context, then
skip this step. Otherwise, if the type is one
of the following types, jump to the appropriate entry in the
following list, and process the resource as described there:
- "text/html"
- Follow the steps given in the HTML document section, and abort
these steps.
- Any type ending in "+xml"
- "application/xml"
- "text/xml"
- Follow the steps given in the XML
document section. If that section determines that the
content is not to be displayed as a generic XML
document, then proceed to the next step in this overall set of
steps. Otherwise, abort these steps.
- "text/plain"
- Follow the steps given in the plain text file section, and abort
these steps.
- A supported image type
- Follow the steps given in the image section, and abort these
steps.
- A type that will use an external application to render the
content in the browsing context
- Follow the steps given in the plugin section, and abort these
steps.
Any Document created by these steps must have its
address set to the
URL that was originally to be fetched, ignoring any other data that was
used to obtain the resource (e.g. the entity body in the case of a
POST submission is not part of the document's
address, nor is the URL of the fallback resource in the
case of the original load having failed and that URL having been
found to match a fallback
namespace).
Non-document content: If,
given type, the new resource is to be handled
by displaying some sort of inline content, e.g. a native rendering
of the content, an error message because the specified type is not
supported, or an inline prompt to allow the user to select a registered
handler for the given type, then display the inline content and
abort these steps.
Otherwise, the document's type is such
that the resource will not affect the browsing context,
e.g. because the resource is to be handed to an external
application. Process the resource appropriately.
Some of the sections below, to which the above algorithm defers
in certain cases, require the user agent to update the session
history with the new page. When a user agent is required to do
this, it must follows the set of steps given below that is
appropriate for the situation at hand. From the point of view of any
script, these steps must occur atomically.
pause for scripts -- but don't use the
"pause" definition since that involves not running script!
onbeforeunload, and if present set flag that we will kill document
onunload, and if present set flag that we will kill document
if flag is set: discard the Document
-
- If the navigation was initiated for entry update of
an entry
-
Replace the entry being updated with a new entry
representing the new resource and its Document
object and related state. The user agent may propagate state from
the old entry to the new entry (e.g. scroll position).
Traverse the history to the new
entry.
- Otherwiseそれ以外の場合
-
Remove all the entries after the current
entry in the browsing context's
Document object's History object.
This doesn't necessarily
have to affect the user
agent's user interface.
Append a new entry at the end of the History
object representing the new resource and its
Document object and related state.
Traverse the history to the new entry.
If the navigation was initiated with replacement
enabled, remove the entry immediately before the new
current entry in the session history.
5.9.2 Page load processing model for HTML files5.9.2 HTML ファイルの頁読み込み処理モデル
When an HTML document is to be loaded in a browsing
context, the user agent must create a Document
object, mark it as being an HTML
document, create an HTML parser, associate it
with the document, and begin to use the bytes provided for the
document as the input stream for that parser.
The input stream converts bytes into
characters for use in the tokeniser. This process relies, in part, on character encoding information
found in the real Content-Type
metadata of the resource; the "sniffed type" is not used for
this purpose.
When no more bytes are available, an EOF character is implied,
which eventually causes a load event
to be fired.それ以上のバイトが存在しなくなると、暗黙の EOF 文字の存在が仮定され、
それによって load 事象が発火されることとなります。
After creating the Document object, but potentially
before the page has finished parsing, the user agent must
update the session history with the new page.Document オブジェクトが作成された後に、
頁が構文解析を完了される前でも構いませんが、
利用者エージェントは、新しい頁によりセッション履歴を更新しなければなりません。
Application cache
selection happens in the HTML
parser.アプリケーション・キャッシュの選択が
HTML 構文解析器の中で起こります。
5.9.3 Page load processing model for XML files5.9.3 XML ファイルの頁読み込み処理モデル
When faced with displaying an XML file inline, user agents must
first create a Document object, following the
requirements of the XML and Namespaces in XML recommendations, RFC
3023, DOM3 Core, and other relevant specifications. [XML] [XMLNS] [RFC3023] [DOM3CORE]利用者エージェントは、 XML ファイルを行内で表示することになったとき、
まず Document オブジェクトを XML と XML 名前空間の勧告、
RFC 3023、DOM3 中核、その他関連する仕様書に従って作成しなければなりません。
[XML] [XMLNS] [RFC3023] [DOM3CORE]
The actual HTTP headers and other metadata, not the headers as
mutated or implied by the algorithms given in this specification,
are the ones that must be used when determining the character
encoding according to the rules given in the above
specifications. Once the character encoding is established, the
document's character encoding must be set to that
character encoding.
If the root element, as parsed according to the XML
specifications cited above, is found to be an html
element with an attribute manifest, then, as soon as the
element is inserted
into the document, the user agent must resolve the value of that attribute, and if that is
successful, must run the application cache
selection algorithm with the resulting absolute
URL as the manifest URL. Otherwise, if the attribute is
absent or resolving it fails, then as soon as the root element is
inserted into the
document, the user agent must run the application cache
selection algorithm with no manifest.
Because the processing of the manifest attribute happens
only once the root element is parsed, any URLs referenced by
processing instructions before the root element (such as <?xml-styleesheet?> and <?xbl?> PIs) will be fetched from the network and
cannot be cached.
User agents may examine the namespace of the root
Element node of this Document object to
perform namespace-based dispatch to alternative processing tools,
e.g. determining that the content is actually a syndication feed and
passing it to a feed handler. If such processing is to take place,
abort the steps in this section, and jump to the next step (labeled
"non-document content") in the navigate steps
above.
Otherwise, then, with the newly created Document,
the user agents must update the session history with the new
page. User agents may do this before the complete document
has been parsed (thus achieving incremental rendering).そうでない場合には、利用者エージェントは、新たに作成された
Document によって、
新しい頁によりセッション履歴を更新しなければなりません。
利用者エージェントは、これを文書全体が構文解析される前に行って
(逐次的レンダリングを実現して) も構いません。
Error messages from the parse process (e.g. XML namespace
well-formedness errors) may be reported inline by mutating the
Document.
5.9.4 Page load processing model for text files
When a plain text document is to be loaded in a browsing
context, the user agent should create a Document
object, mark it as being an HTML
document, create an HTML parser, associate it
with the document, act as if the tokeniser had emitted a start tag
token with the tag name "pre", set the tokenization
stage's content model flag to PLAINTEXT, and
begin to pass the stream of characters in the plain text document to
that tokeniser.
The rules for how to convert the bytes of the plain text document
into actual characters are defined in RFC 2046, RFC 2646, and
subsequent versions thereof. [RFC2046] [RFC2646]
The document's character encoding must be set to the
character encoding used to decode the document.
Upon creation of the Document object, the user agent
must run the application cache
selection algorithm with no manifest.
When no more character are available, an EOF character is
implied, which eventually causes a load event to be fired.
After creating the Document object, but potentially
before the page has finished parsing, the user agent must
update the session history with the new page.Document オブジェクトが作成された後に、
頁が構文解析を完了される前でも構いませんが、
利用者エージェントは、新しい頁によりセッション履歴を更新しなければなりません。
User agents may add content to the head element of
the Document, e.g. linking to stylesheet or an XBL
binding, providing script, giving the document a title,
etc.
5.9.5 Page load processing model for images
When an image resource is to be loaded in a browsing
context, the user agent should create a Document
object, mark it as being an HTML
document, append an html element to the
Document, append a head element and a
body element to the html element, append
an img to the body element, and set the
src attribute of the
img element to the address of the image.
Then, the user agent must act as if it had stopped parsing.
Upon creation of the Document object, the user agent
must run the application cache
selection algorithm with no manifest.
After creating the Document object, but potentially
before the page has finished fully loading, the user agent must
update the session history with the new page.
User agents may add content to the head element of
the Document, or attributes to the img
element, e.g. to link to stylesheet or an XBL binding, to provide a
script, to give the document a title, etc.
5.9.6 Page load processing model for content that uses plugins
When a resource that requires an external resource to be rendered
is to be loaded in a browsing context, the user agent
should create a Document object, mark it as being an
HTML document, append an
html element to the Document, append a
head element and a body element to the
html element, append an embed to the
body element, and set the src attribute of the
embed element to the address of the resource.
Then, the user agent must act as if it had stopped parsing.
Upon creation of the Document object, the user agent
must run the application cache
selection algorithm with no manifest.
After creating the Document object, but potentially
before the page has finished fully loading, the user agent must
update the session history with the new page.
User agents may add content to the head element of
the Document, or attributes to the embed
element, e.g. to link to stylesheet or an XBL binding, or to give
the document a title.
If the sandboxed
plugins browsing context flag is set on the browsing
context, the synthesized embed element will fail to render the content.
5.9.7 Page load processing model for inline content that doesn't have a DOM
When the user agent is to display a user agent page inline in a
browsing context, the user agent should create a
Document object, mark it as being an HTML document, and then either associate that
Document with a custom rendering that is not rendered
using the normal Document rendering rules, or mutate
that Document until it represents the content the user
agent wants to render.
Once the page has been set up, the user agent must act as if it
had stopped parsing.
Upon creation of the Document object, the user agent
must run the application cache
selection algorithm with no manifest.
After creating the Document object, but potentially
before the page has been completely set up, the user agent must
update the session history with the new page.
When a user agent is supposed to navigate to a fragment
identifier, then the user agent must update the session
history with the new page, where "the new page" has the same
Document as before but with the URL having the newly
specified fragment identifier.
Part of that algorithm involves the user agent having to
scroll to the fragment identifier, which is the
important part for this step.
When the user agent is required to scroll to the fragment
identifier, it must change the scrolling position of the
document, or perform some other action, such that the
indicated part of the document is brought to the user's
attention. If there is no indicated part, then the user agent must
not scroll anywhere.
The indicated part of the document is the one that
the fragment identifier, if any, identifies. The semantics of the
fragment identifier in terms of mapping it to a specific DOM Node is
defined by the MIME type specification of the document's MIME Type
(for example, the processing of fragment identifiers for XML MIME
types is the responsibility of RFC3023).
For HTML documents (and the text/html MIME type),
the following processing model must be followed to determine what
the indicated part of the document is.
Parse the URL,
and let fragid be the <fragment> component of the
URL.
If fragid is the empty string, then the indicated
part of the document is the top of the document.
If there is an element in the DOM that has an ID exactly
equal to fragid, then the first such element in tree order
is the indicated part of the document; stop the
algorithm here.
If there is an a element in the DOM that has a
name attribute whose value is
exactly equal to fragid, then the first such element in tree
order is the indicated part of the document; stop the
algorithm here.
Otherwise, there is no indicated part of the
document.
For the purposes of the interaction of HTML with Selectors' :target pseudo-class, the target element is
the indicated part of the document, if that is an
element; otherwise there is no target element. [SELECTORS]
5.9.9 History traversal
When a user agent is required to traverse the history
to a specified entry, the user agent must act as
follows:
If there is no longer a Document object for the
entry in question, the user agent must navigate the
browsing context to the location for that entry to perform an
entry update of that entry, and abort these steps. The
"navigate" algorithm reinvokes this "traverse"
algorithm to complete the traversal, at which point there
is a Document object and so this step gets
skipped. The navigation must be done using the same source
browsing context as was used the first time this entry was
created.
If appropriate, update the current entry in the
browsing context's Document object's
History object to reflect any state that the user
agent wishes to persist.
For example, some user agents might want to
persist the scroll position, or the values of form controls.
If the specified entry has a different
Document object than the current entry
then the user agent must run the following substeps:
freeze any timers, intervals,
XMLHttpRequests, database transactions, etc
The user agent must move any properties that have been added
to the browsing context's default view's Window
object to the active document's
Document's list of added
properties.
If the browsing context is a top-level browsing
context (and not an auxiliary browsing
context), and the origin of the
Document of the specified entry is not the
same as the origin
of the Document of the current entry,
then the following sub-sub-steps must be run:
The current browsing context name must be
stored with all the entries in the history that are associated
with Document objects with the same
origin as the active document and
that are contiguous with the current entry.
The browsing context's browsing
context name must be unset.
The user agent must make the
specified entry's Document object the
active document of the browsing
context. (If it is a top-level browsing
context, this might change which application
cache it is associated with.)
If the specified entry has a browsing
context name stored with it, then the following
sub-sub-steps must be run:
The browsing context's browsing context name
must be set to the name stored with the specified entry.
Any browsing context name stored with the
entries in the history that are associated with
Document objects with the same origin
as the new active document, and that are
contiguous with the specified entry, must be cleared.
The user agent must move any properties that have been added
to the active document's Document's
list of added properties to browsing context's
default view's Window object.
unfreeze any timers, intervals,
XMLHttpRequests, database transactions, etc
If there are any entries with state objects between the
last activated entry for the Document of
the specified entry and the specified entry itself
(not inclusive), then the user agent must iterate through every
entry between that last activated entry and the
specified entry, starting with the entry closest to the
current entry, and ending with the one closest to the
specified entry. For each entry, if the entry is a state
object, the user agent must activate the state
object.
If the specified entry is a state object or the
first entry for a Document, the user agent must activate that
entry.
If the specified entry has a URL that differs from
the current entry's only by its fragment identifier,
and the two share the same Document object, then
fire a simple event with the name hashchange at the
body element, and, if the new URL has a
fragment identifier, scroll to the fragment
identifier.
User agents may also update other aspects of the document
view when the location changes in this way, for instance the scroll
position, values of form fields, etc.
The current entry is now the specified
entry.
how does the changing of the global attributes
affect .watch() when seen from other Windows?
5.9.10 Closing a browsing context
Closing a browsing context and discarding it
(vs closing it and keeping it around in memory).
when a browsing context is closed, all session
history entries' Document objects must be
discarded.
When a user agent is to discard a
Document, any frozen timers, intervals,
XMLHttpRequests, database transactions, etc, must be killed, and any
MessagePorts owned by the Window object must be
unentangled.
Also, unload
events should fire.
5.10 Structured client-side storage
5.10.1 Storing name/value pairs
5.10.1.1 Introduction5.10.1.1 はじめに
This section is non-normative.この節は規定の一部ではありません。
This specification introduces two related mechanisms, similar to
HTTP session cookies, for storing structured data on the client
side. [RFC2109] [RFC2965]
The first is designed for scenarios where the user is carrying
out a single transaction, but could be carrying out multiple
transactions in different windows at the same time.
Cookies don't really handle this case well. For example, a user
could be buying plane tickets in two different windows, using the
same site. If the site used cookies to keep track of which ticket
the user was buying, then as the user clicked from page to page in
both windows, the ticket currently being purchased would "leak" from
one window to the other, potentially causing the user to buy two
tickets for the same flight without really noticing.
To address this, this specification introduces the sessionStorage DOM attribute.
Sites can add data to the session storage, and it will be accessible
to any page from the same site opened in that window.
For example, a page could have a checkbox that the user ticks to
indicate that he wants insurance:
<label>
<input type="checkbox" onchange="sessionStorage.insurance = checked">
I want insurance on this trip.
</label>
A later page could then check, from script, whether the user had
checked the checkbox or not:
if (sessionStorage.insurance) { ... }
If the user had multiple windows opened on the site, each one
would have its own individual copy of the session storage object.
The second storage mechanism is designed for storage that spans
multiple windows, and lasts beyond the current session. In
particular, Web applications may wish to store megabytes of user
data, such as entire user-authored documents or a user's mailbox, on
the client side for performance reasons.
Again, cookies do not handle this case well, because they are
transmitted with every request.
The localStorage DOM
attribute is used to access a page's local storage area.
The site at example.com can display a count of how many times
the user has loaded its page by putting the following at the bottom
of its page:
<p>
You have viewed this page
<span id="count">an untold number of</span>
time(s).
</p>
<script>
if (!localStorage.pageLoadCount)
localStorage.pageLoadCount = 0;
localStorage.pageLoadCount = parseInt(localStorage.pageLoadCount, 10) + 1;
document.getElementById('count').textContent = localStorage.pageLoadCount;
</script>
Each site has its own separate storage area.
Storage areas (both session storage and local storage) store
strings. To store structured data in a storage area, you must first
convert it to a string.
5.10.1.2 The Storage interface5.10.1.2 Storage 界面
interface Storage {
readonly attribute unsigned long length;
[IndexGetter] DOMString key(in unsigned long index);
[NameGetter] DOMString getItem(in DOMString key);
[NameSetter] void setItem(in DOMString key, in DOMString data);
[XXX] void removeItem(in DOMString key);
void clear();
};
Each Storage object provides access to a list of
key/value pairs, which are sometimes called items. Keys and values
are strings. Any string (including the empty string) is a valid
key.
To store more structured data, authors may consider
using the SQL interfaces instead.
Each Storage object is associated with a list of
key/value pairs when it is created, as defined in the sections on
the sessionStorage and localStorage attributes. Multiple
separate objects implementing the Storage interface can
all be associated with the same list of key/value pairs
simultaneously.
The length
attribute must return the number of key/value pairs currently
present in the list associated with the object.
The key(n) method must return the name of the
nth key in the list. The order of keys is
user-agent defined, but must be consistent within an object between
changes to the number of keys. (Thus, adding or removing a key may change the
order of the keys, but merely changing the value of an existing key
must not.) If n is less than zero or greater than
or equal to the number of key/value pairs in the object, then this
method must raise an INDEX_SIZE_ERR exception.
The getItem(key) method must return the current
value associated with the given key. If the
given key does not exist in the list associated
with the object then this method must return null.
The setItem(key, value) method
must first check if a key/value pair with the given key already exists in the list associated with the
object.
If it does not, then a new key/value pair must be added to the
list, with the given key and value.
If the given key does exist in the
list, then it must have its value updated to the value given in the
value argument.
If it couldn't set the new value, the method must raise an
QUOTA_EXCEEDED_ERR exception. (Setting could fail if,
e.g., the user has disabled storage for the domain, or if the quota
has been exceeded.)
The removeItem(key) method must cause the key/value
pair with the given key to be removed from the
list associated with the object, if it exists. If no item with that
key exists, the method must do nothing.
The setItem() and removeItem() methods must be
atomic with respect to failure. That is, changes to the data storage
area must either be successful, or the data storage area must not be
changed at all.
The clear()
method must atomically cause the list associated with the object to
be emptied of all key/value pairs.
When the setItem(),
removeItem(), and clear() methods are invoked, events
are fired on other HTMLDocument objects that can access
the newly stored or removed data, as defined in the sections on the
sessionStorage and localStorage attributes.
The sessionStorage
attribute represents the set of storage areas specific to the
current top-level browsing context.
Each top-level browsing context has a unique set of
session storage areas, one for each origin.
User agents should not expire data from a browsing context's
session storage areas, but may do so when the user requests that
such data be deleted, or when the UA detects that it has limited
storage space, or for security reasons. User agents should always
avoid deleting data while a script that could access that data is
running. When a top-level browsing context is destroyed (and
therefore permanently inaccessible to the user) the data stored in
its session storage areas can be discarded with it, as the API
described in this specification provides no way for that data to
ever be subsequently retrieved.
The lifetime of a browsing context can be unrelated
to the lifetime of the actual user agent process itself, as the user
agent may support resuming sessions after a restart.
When a new HTMLDocument is created, the user agent
must check to see if the document's top-level browsing
context has allocated a session storage area for that
document's origin. If it has not, a new storage area
for that document's origin must be created.
The Storage object for the document's associated
Window object's sessionStorage attribute must then
be associated with that origin's session storage area
for that top-level browsing context.
When a new top-level browsing context is created by
cloning an existing browsing context, the new browsing
context must start with the same session storage areas as the
original, but the two sets must from that point on be considered
separate, not affecting each other in any way.
When a new top-level browsing context is created by
a script in an existing browsing context, or by the
user following a link in an existing browsing context, or in some
other way related to a specific HTMLDocument, then the
session storage area of the origin of that
HTMLDocument must be copied into the new browsing
context when it is created. From that point on, however, the two
session storage areas must be considered separate, not affecting
each other in any way.
When the setItem(), removeItem(), and clear() methods are called on a
Storage object x that is associated
with a session storage area, then in every HTMLDocument
object whose Window object's sessionStorage attribute's
Storage object is associated with the same storage
area, other than x, a storage event must be fired, as described below.
The localStorage
object provides a Storage object for an
origin.
User agents must have a set of local storage areas, one for each
origin.
User agents should expire data from the local storage areas only
for security reasons or when requested to do so by the user. User
agents should always avoid deleting data while a script that could
access that data is running. Data stored in local storage areas
should be considered potentially user-critical. It is expected that
Web applications will use the local storage areas for storing
user-written documents.
When the localStorage
attribute is accessed, the user agent must check to see if it has
allocated local storage area for the for the origin of
the active document of the browsing
context of the Window object on which the method
was invoked. If it has not, a new storage area for that
origin must be created.
The user agent must then create a Storage object
associated with that origin's local storage area, and return
it.
When the setItem(), removeItem(), and clear() methods are called on a
Storage object x that is associated
with a local storage area, then in every HTMLDocument
object whose Window object's localStorage attribute's
Storage object is associated with the same storage
area, other than x, a storage event must be fired, as described below.
5.10.1.5 The storage event5.10.1.5 storage 事象
The storage event
is fired in an HTMLDocument when a storage area
changes, as described in the previous two sections (for session storage, for local storage).storage
事象は、 HTMLDocument
において、ストレージ領域が変化した時に。前の2つの節
(セッション・ストレージ対象、局所ストレージ対象)
で説明したように発火されます。
When this happens, the user agent must dispatch an event with the
name storage, with no namespace, which does not bubble
but is cancelable, and which uses the StorageEvent, at
the body element of each active HTMLDocument object
affected.利用者エージェントは、これが起こる時、名前
storage、
名前空間なし、
泡立たず取消し可能で StorageEvent
を使った事象を、関係する活性 HTMLDocument
オブジェクトそれぞれの文書
body 要素に対して発送しなければなりません。
If the event is being fired due to an invocation of the
setItem() or removeItem() methods, the
event must have its key
attribute set to the name of the key in question, its oldValue attribute set to
the old value of the key in question, or null if the key is newly
added, and its newValue
attribute set to the new value of the key in question, or null if
the key was removed.事象が setItem() メソッドや removeItem() メソッドの呼び出しによって発火されている場合には、
事象の key 属性は当該鍵名に、 oldValue
属性は当該鍵の古い値に、 newValue は当該鍵の新しい値か、鍵が削除される場合には null に設定しなければなりません。
Otherwise, if the event is being fired due to an invocation of
the clear() method, the event
must have its key, oldValue, and newValue attributes set to
null.そうでない場合、事象が clear() メソッドの呼び出しによって発火されている場合には、
事象の key、oldValue、newValue 各属性はいずれも null に設定しなければなりません。
In addition, the event must have its url attribute set to the address
of the page whose Storage object was affected, and its
source attribute set to
the Window object of the browsing context
that that document is in, if the two documents are in the same
unit of related browsing contexts, or null
otherwise.更に、事象の url 属性は Storage
オブジェクトが影響を受ける頁の番地に、
source
属性はその文書が含まれる閲覧文脈の
Window
オブジェクトか、両文書が同じ関連閲覧文脈の単位に属さない場合には null
に設定しなければなりません。
5.10.1.5.1 Event definition5.10.1.5.1 事象定義
interface StorageEvent : Event {
readonly attribute DOMString key;
readonly attribute DOMString oldValue;
readonly attribute DOMString newValue;
readonly attribute DOMString url;
readonly attribute Window source;
void initStorageEvent(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMString keyArg, in DOMString oldValueArg, in DOMString newValueArg, in DOMString urlArg, in Window sourceArg);
void initStorageEventNS(in DOMString namespaceURI, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMString keyArg, in DOMString oldValueArg, in DOMString newValueArg, in DOMString urlArg, in Window sourceArg);
};
The initStorageEvent()
and initStorageEventNS()
methods must initialize the event in a manner analogous to the
similarly-named methods in the DOM3 Events interfaces. [DOM3EVENTS]initStorageEvent()
メソッドと initMessageEventNS()
メソッドは、 DOM3 事象界面の似たような名前のメソッドと同じような方法で事象を初期化しなければなりません。
[DOM3EVENTS]
The key
attribute represents the key being changed.key
属性は、変化する鍵を表します。
The oldValue
attribute represents the old value of the key being changed.oldValue
属性は、変化する鍵の古い値を表します。
The newValue
attribute represents the new value of the key being changed.newValue
属性は、変化する鍵の新しい値を表します。
The url
attribute represents the address of the document that changed the
key.url
属性は、鍵を変更した文書の番地を表します。
The source attribute
represents the Window that changed the key.source 属性は、
鍵を変更した Window
を表します。
5.10.1.6 Threads5.10.1.6 スレッド
Multiple browsing contexts must be able to access the local
storage areas simultaneously in a predictable manner. Scripts must
not be able to detect any concurrent script execution.複数の閲覧文脈は、局所ストレージ領域に同時に予測可能な方法でアクセスできなければなりません。
スクリプトが並行スクリプト実行を検知可能であってはなりません。
This is required to guarantee that the length attribute of a
Storage object never changes while a script is
executing, other than in a way that is predictable by the script
itself.これは Storage オブジェクトの length
属性がスクリプトの実行中にスクリプト自身が予測できない形で変化してしまわないために必要です。
There are various ways of implementing this
requirement. One is to just have one event loop for all
browsing contexts. Another is
that if a script running in one browsing context accesses a storage
area, the user agent blocks scripts in other browsing contexts when
they try to access the same storage area until the event
loop running the first script has completed running the task
that started that script. Another (potentially more efficient but
certainly more complex) implementation strategy is to use optimistic
transactional script execution. This specification does not require
any particular implementation strategy, so long as the requirement
above is met.この要件を実装する方法は色々あります。
一つは、すべての閲覧文脈が1つだけ事象ループを持つという方法です。
もう一つは、ある閲覧文脈で走っているスクリプトがストレージ領域にアクセスする場合には、
最初のスクリプトが走っている事象ループがそのスクリプトをはじめたタスクを走らせ終えるまで、
同じストレージ領域にアクセスしようとする別閲覧文脈のスクリプトを利用者エージェントがブロックするという方法です。
また別の (より効率がよさそうでより複雑になりそうな) 実装戦略は、楽観的トランザクション的スクリプト実行を使うという方法です。
この仕様書は前述の要件が満たされる限りにおいて特定の実装戦略を要求していません。
5.10.2 Database storage5.10.2 データベース・ストレージ
5.10.2.1 Introduction5.10.2.1 はじめに
This section is non-normative.この節は規定の一部ではありません。
...
5.10.2.2 Databases5.10.2.2 データベース
Each origin has an associated set of databases. Each
database has a name and a current version. There is no way to
enumerate or delete the databases available for a domain from this
API.各起源は、それに関連付けられたデータベースの集合を持ちます。
各データベースは、名前と現在の版を持ちます。
この API を使ってあるドメインに利用可能なデータベースを列挙したり、
削除したりする方法はありません。
Each database has one version at a time, a database
can't exist in multiple versions at once. Versions are intended to
allow authors to manage schema changes incrementally and
non-destructively, and without running the risk of old code (e.g. in
another browser window) trying to write to a database with incorrect
assumptions.各データベースはある時点で1つの版を持ち、
1つのデータベースの複数の版が同時に存在することはできません。
版は著者がスキーマの変更を随時、非破壊的に、
かつ古い符号 (例えば他のブラウザ窓中のもの)
が誤った仮定の下でデータベースに書き込もうとする危険なしで行えるようにすることを意図したものです。
The openDatabase() method
returns a Database object. The method takes four
arguments: a database name, a database version, a display name, and
an estimated size, in bytes, of the data that will be stored in the
database.openDatabase()
メソッドは
Database
オブジェクトを返します。
このメソッドは、データベース名、データベース版、
表示名、データベース中に蓄積されるデータの大きさの見積もり (バイト単位)
の4つの引数を取ります。
The openDatabase() method
must use and create databases from the origin of the
active document of the browsing context of
the Window object on which the method was invoked.openDatabase()
メソッドは、それが呼び出された Window
オブジェクトの閲覧文脈の活性文書の起源からのデータベースを使用・作成しなければなりません。
If the database version provided is not the empty string, and the
database already exists but has a different version, or no version,
then the method must raise an INVALID_STATE_ERR
exception.
Otherwise, if the database version provided is the empty string,
or if the database doesn't yet exist, or if the database exists and
the version provided to the openDatabase() method is the same as
the current version associated with the database, then the method
must return a Database object representing the database
that has the name that was given. If no such database exists, it
must be created first.そうでない場合、指定されたデータベースの版が空文字列の場合、
またはデータベースがまだ存在しない場合、
またはデータベースが存在し、 openDatabase()
メソッドに指定されて版がデータベースに関連付けられている現在の版と同じである場合には、
メソッドは、指定された名前を持つデータベースを表す
Database
オブジェクトを返さなければなりません。
そのようなデータベースが存在しない場合、
まずそれを作らなければなりません。
All strings including the empty string are valid database
names. Database names must be compared in a
case-sensitive manner.空文字列を含むすべての文字列は妥当なデータベース名です。
データベース名は大文字・小文字を区別した形で比較しなければなりません。
The user agent may raise a SECURITY_ERR exception
instead of returning a Database object if the request
violates a policy decision (e.g. if the user agent is configured to
not allow the page to open databases).
Implementations can support this even in
environments that only support a subset of all strings as database
names by mapping database names (e.g. using a hashing algorithm) to
the supported set of names.実装は、すべての文字列の部分集合をデータベース名として扱う環境であっても、
データベース名を対応している名前の集合に写像する
(例えばハッシュ算法を使う) ことにより、これに対応することができます。
User agents are expected to use the display name and the
estimated database size to optimize the user experience. For
example, a user agent could use the estimated size to suggest an
initial quota to the user. This allows a site that is aware that it
will try to use hundreds of megabytes to declare this upfront,
instead of the user agent prompting the user for permission to
increase the quota every five megabytes.利用者エージェントに対しては、表示名とデータベースの大きさの見積もりを、
利用者の体験の最適化のために使うことを期待しています。
例えば、利用者エージェントは、利用者に対して最初の割当量を提示するために大きさの見積もりを使うことができます。
それによって、はじめから数百メガバイトを使うであろうことがわかっているサイトがそれを予め宣言しておけば、
利用者エージェントは5メガバイト毎に割当量を増やすかどうかを利用者に問わなくてもよくなります。
interface Database {
void transaction(in SQLTransactionCallback callback);
void transaction(in SQLTransactionCallback callback, in SQLTransactionErrorCallback errorCallback);
void transaction(in SQLTransactionCallback callback, in SQLTransactionErrorCallback errorCallback, in VoidCallback successCallback);
readonly attribute DOMString version;
void changeVersion(in DOMString oldVersion, in DOMString newVersion, in SQLTransactionCallback callback, in SQLTransactionErrorCallback errorCallback, in VoidCallback successCallback);
};
interface SQLTransactionCallback {
void handleEvent(in SQLTransaction transaction);
};
interface SQLTransactionErrorCallback {
void handleEvent(in SQLError error);
};
The transaction()
method takes one or two arguments. When called, the method must
immediately return and then asynchronously run the transaction
steps with the transaction callback being the first
argument, the error callback being the second argument, if
any, the success callback being the third argument, if any,
and with no preflight operation or postflight
operation.transaction()
メソッドは1つか2つの引数を取ります。
このメソッドは、呼び出された時、
すぐに返り、それから非同期に、
取引呼び戻しを最初の引数とし、
誤り呼び戻しを2つ目の引数があればそれとし、
成功呼び戻しを3つ目の引数があればそれとし、
飛行前操作と飛行後操作はなしとして、
取引段階を走らせなければなりません。
The version that the database was opened with is the expected version of
this Database object. It can be the empty string, in
which case there is no expected version — any version is
fine.
On getting, the version attribute
must return the current version of the database (as opposed to the
expected
version of the Database object).
The changeVersion()
method allows scripts to atomically verify the version number and
change it at the same time as doing a schema update. When the method
is invoked, it must immediately return, and then asynchronously run
the transaction steps with the transaction
callback being the third argument, the error callback
being the fourth argument, the success callback being the
fifth argument, the preflight operation being the
following:
Check that the value of the first argument to the changeVersion() method
exactly matches the database's actual version. If it does not, then
the preflight operation fails.
...and the postflight operation being the following:
Change the database's actual version to the value of the second
argument to the changeVersion()
method.
Change the Database object's expected version to
the value of the second argument to the changeVersion()
method.
5.10.2.3 Executing SQL statements
The transaction()
and changeVersion()
methods invoke callbacks with SQLTransaction
objects.
typedef sequence<any> ObjectArray;
interface SQLTransaction {
void executeSql(in DOMString sqlStatement);
void executeSql(in DOMString sqlStatement, in ObjectArray arguments);
void executeSql(in DOMString sqlStatement, in ObjectArray arguments, in SQLStatementCallback callback);
void executeSql(in DOMString sqlStatement, in ObjectArray arguments, in SQLStatementCallback callback, in SQLStatementErrorCallback errorCallback);
};
interface SQLStatementCallback {
void handleEvent(in SQLTransaction transaction, in SQLResultSet resultSet);
};
interface SQLStatementErrorCallback {
boolean handleEvent(in SQLTransaction transaction, in SQLError error);
};
When the executeSql(sqlStatement, arguments, callback, errorCallback) method is invoked, the
user agent must run the following algorithm. (This algorithm is
relatively simple and doesn't actually execute any SQL — the
bulk of the work is actually done as part of the transaction
steps.)
If the method was not invoked during the execution of a
SQLTransactionCallback,
SQLStatementCallback, or
SQLStatementErrorCallback then raise an
INVALID_STATE_ERR exception. (Calls from inside a
SQLTransactionErrorCallback thus raise an
exception. The SQLTransactionErrorCallback handler is
only called once a transaction has failed, and no SQL statements
can be added to a failed transaction.)
Parse the first argument to the method (sqlStatement) as a SQL statement, with the
exception that ? characters can be used in
place of SQL literals in the statement. [SQL]
-
Replace each ? placeholder with the value
of the argument in the arguments array with
the same position. (So the first ?
placeholder gets replaced by the first value in the arguments array, and generally the nth ? placeholder gets
replaced by the nth value in the arguments array.)
Substitutions for ?
placeholders are done at the literal level, not as string
concatenations, so this provides a way to dynamically insert
parameters into a statement without risk of a SQL injection
attack.
If the second argument is omitted or null, then treat the arguments array as empty.
The result is the statement.
Implementation feedback is requested on what
to do with arguments that are of types that are not supported by
the underlying SQL backend. For example, SQLite doesn't support
booleans, so what should the UA do if passed a boolean? The Gears
team suggests failing, not silently converting types.
If the syntax of sqlStatement is not
valid (except for the use of ? characters in
the place of literals), or the statement uses features that are not
supported (e.g. due to security reasons), or the number of items in
the arguments array is not equal to the number
of ? placeholders in the statement, or the
statement cannot be parsed for some other reason, then mark the
statement as bogus.
If the Database object that the
SQLTransaction object was created from has an expected version
that is neither the empty string nor the actual version of the
database, then mark the statement as bogus. (Error code 2.)
Queue up the statement in the transaction, along with
the third argument (if any) as the statement's result set callback
and the fourth argument (if any) as the error callback.
The user agent must act as if the database was hosted in an
otherwise completely empty environment with no resources. For
example, attempts to read from or write to the file system will
fail.
SQL inherently supports multiple concurrent connections. Authors
should make appropriate use of the transaction features to handle
the case of multiple scripts interacting with the same database
simultaneously (as could happen if the same page was opened in two
different browsing
contexts).
User agents must consider statements that use the BEGIN, COMMIT, and ROLLBACK SQL features as being unsupported (and thus
will mark them as bogus), so as to not let these statements
interfere with the explicit transactions managed by the database API
itself.
A future version of this specification will probably
define the exact SQL subset required in more detail.この仕様書の将来の版はおそらく実際に要求される SQL の部分集合をより詳しく定義することとなるでしょう。
5.10.2.4 Database query results5.10.2.4 データベース照会結果
The executeSql()
method invokes its callback with a SQLResultSet object
as an argument.
interface SQLResultSet {
readonly attribute long insertId;
readonly attribute long rowsAffected;
readonly attribute SQLResultSetRowList rows;
};
The insertId
attribute must return the row ID of the row that the
SQLResultSet object's SQL statement inserted into the
database, if the statement inserted a row. If the statement inserted
multiple rows, the ID of the last row must be the one returned. If
the statement did not insert a row, then the attribute must instead
raise an INVALID_ACCESS_ERR exception.
The rowsAffected
attribute must return the number of rows that were affected by the
SQL statement. If the statement did not affected any rows, then the
attribute must return zero. For "SELECT" statements, this returns
zero (querying the database doesn't affect any rows).
The rows
attribute must return a SQLResultSetRowList
representing the rows returned, in the order returned by the
database. If no rows were returned, then the object will be empty
(its length will
be zero).
interface SQLResultSetRowList {
readonly attribute unsigned long length;
[IndexGetter] DOMObject item(in unsigned long index);
};
SQLResultSetRowList objects have a length
attribute that must return the number of rows it represents (the
number of rows returned by the database).
The item(index) attribute must return the row
with the given index index. If there is no such
row, then the method must raise an INDEX_SIZE_ERR
exception.
Each row must be represented by a native ordered dictionary data
type. In the ECMAScript binding, this must be Object.
Each row object must have one property (or dictionary entry) per
column, with those properties enumerating in the order that these
columns were returned by the database. Each property must have the
name of the column and the value of the cell, as they were returned
by the database.
5.10.2.5 Errors5.10.2.5 誤り
Errors in the database API are reported using callbacks that have
a SQLError object as one of their arguments.
interface SQLError {
readonly attribute unsigned long code;
readonly attribute DOMString message;
};
The code DOM
attribute must return the most appropriate code from the following
table:
| Code
符号 | Situation
状況 |
|---|
| 0
| The transaction failed for reasons unrelated to the database
itself and not covered by any other error code.
|
| 1
| The statement failed for database reasons not covered by any
other error code.
|
| 2
| The statement failed because the expected version
of the database didn't match the actual database version.
|
| 3
| The statement failed because the data returned from the
database was too large. The SQL "LIMIT" modifier might be useful
to reduce the size of the result set.
|
| 4
| The statement failed because there was not enough remaining
storage space, or the storage quota was reached and the user
declined to give more space to the database.
|
| 5
| The statement failed because the transaction's first
statement was a read-only statement, and a subsequent statement
in the same transaction tried to modify the database, but the
transaction failed to obtain a write lock before another
transaction obtained a write lock and changed a part of the
database that the former transaction was depending upon.
|
| 6
| An INSERT, UPDATE, or REPLACE
statement failed due to a constraint failure. For example,
because a row was being inserted and the value given for the
primary key column duplicated the value of an existing row.
|
We should define a more thorough list of
codes. Implementation feedback is requested to determine what codes
are needed.
The message
DOM attribute must return an error message describing the error
encountered. The message should be localized to the user's
language.
5.10.2.6 Processing model5.10.2.6 処理モデル
The transaction steps are as follows. These steps must
be run asynchronously. These steps are invoked with a transaction
callback, optionally an error callback, optionally a
success callback, optionally a preflight operation,
and optionally a postflight operation.
Open a new SQL transaction to the database, and create a
SQLTransaction object that represents that
transaction.
If an error occurred in the opening of the transaction, jump
to the last step.
If a preflight operation was defined for this
instance of the transaction steps, run that. If it fails, then jump
to the last step. (This is basically a hook for the changeVersion()
method.)
Queue a task to invoke the transaction
callback with the aforementioned SQLTransaction
object as its only argument, and wait for that task to be
run.
If the callback couldn't be called (e.g. it was null), or if
the callback was invoked and raised an exception, jump to the last
step.
While there are any statements queued up in the transaction,
perform the following steps for each queued up statement in the
transaction, oldest first. Each statement has a statement,
optionally a result set callback, and optionally an error
callback.
If the statement is marked as bogus, jump to the "in case
of error" steps below.
Execute the statement in the context of the transaction.
[SQL]
If the statement failed, jump to the "in case of error"
steps below.
Create a SQLResultSet object that represents
the result of the statement.
If the statement has a result set callback, queue a
task to invoke it with the SQLTransaction
object as its first argument and the new
SQLResultSet object as its second argument, and wait
for that task to be run.
If the callback was invoked and raised an exception, jump
to the last step in the overall steps.
Move on to the next statement, if any, or onto the next
overall step otherwise.
In case of error (or more specifically, if the above substeps
say to jump to the "in case of error" steps), run the following
substeps:
If the statement had an associated error callback, then
queue a task to invoke that error callback with the
SQLTransaction object and a newly constructed
SQLError object that represents the error that
caused these substeps to be run as the two arguments,
respectively, and wait for the task to be run.
If the error callback returns false, then move on to the
next statement, if any, or onto the next overall step
otherwise.
Otherwise, the error callback did not return false, or
there was no error callback. Jump to the last step in the overall
steps.
If a postflight operation was defined for this
instance of the transaction steps, run that. If it fails, then jump
to the last step. (This is basically a hook for the
changeVersion()
method.)
Commit the transaction.
If an error occurred in the committing of the transaction,
jump to the last step.
Queue a task to invoke the success
callback.
End these steps. The next step is only used when something
goes wrong.
Queue a task to invoke the error
callback with a newly constructed SQLError object
that represents the last error to have occurred in this
transaction. Rollback the transaction. Any still-pending statements
in the transaction are discarded.
5.10.3 Disk space
User agents should limit the total amount of space allowed for
storage areas and databases.
User agents should guard against sites storing data in the
storage areas or databases of subdomains, e.g. storing up to the
limit in a1.example.com, a2.example.com, a3.example.com, etc,
circumventing the main example.com storage limit.
User agents may prompt the user when quotas are reached, allowing
the user to grant a site more space. This enables sites to store
many user-created documents on the user's computer, for
instance.
User agents should allow users to see how much space each domain
is using.
A mostly arbitrary limit of five megabytes per domain is
recommended. Implementation feedback is welcome and will be used to
update this suggestion in future.
5.10.4 Privacy
5.10.4.1 User tracking
A third-party advertiser (or any entity capable of getting
content distributed to multiple sites) could use a unique identifier
stored in its local storage area or in its client-side database to
track a user across multiple sessions, building a profile of the
user's interests to allow for highly targeted advertising. In
conjunction with a site that is aware of the user's real identity
(for example an e-commerce site that requires authenticated
credentials), this could allow oppressive groups to target
individuals with greater accuracy than in a world with purely
anonymous Web usage.
There are a number of techniques that can be used to mitigate the
risk of user tracking:
-
Blocking third-party storage: user agents may restrict access
to the localStorage and
database objects to scripts originating at the domain of the
top-level document of the browsing context, for
instance denying access to the API for pages from other domains
running in iframes.
-
Expiring stored data: user agents may automatically delete
stored data after a period of time.
For example, a user agent could treat third-party local
storage areas as session-only storage, deleting the data once the
user had closed all the browsing contexts that could
access it.
This can restrict the ability of a site to track a user, as the
site would then only be able to track the user across multiple
sessions when he authenticates with the site itself (e.g. by
making a purchase or logging in to a service).
However, this also puts the user's data at risk.
-
Treating persistent storage as cookies: user agents should
present the persistent storage and database features to the user
in a way that does not distinguish them from HTTP session
cookies. [RFC2109] [RFC2965]
This might encourage users to view persistent storage with
healthy suspicion.
-
Site-specific white-listing of access to local storage areas
and databases: user agents may allow sites to access session
storage areas in an unrestricted manner, but require the user to
authorize access to local storage areas and databases.
-
Origin-tracking of persistent storage data: user
agents may record the origins of sites that contained content from
third-party origins that caused data to be stored.
If this information is then used to present the view of data
currently in persistent storage, it would allow the user to make
informed decisions about which parts of the persistent storage to
prune. Combined with a blacklist ("delete this data and prevent
this domain from ever storing data again"), the user can restrict
the use of persistent storage to sites that he trusts.
-
Shared blacklists: user agents may allow users to share their
persistent storage domain blacklists.
This would allow communities to act together to protect their
privacy.
While these suggestions prevent trivial use of these APIs for
user tracking, they do not block it altogether. Within a single
domain, a site can continue to track the user during a session, and
can then pass all this information to the third party along with any
identifying information (names, credit card numbers, addresses)
obtained by the site. If a third party cooperates with multiple
sites to obtain such information, a profile can still be
created.
However, user tracking is to some extent possible even with no
cooperation from the user agent whatsoever, for instance by using
session identifiers in URLs, a technique already commonly used for
innocuous purposes but easily repurposed for user tracking (even
retroactively). This information can then be shared with other
sites, using using visitors' IP addresses and other user-specific
data (e.g. user-agent headers and configuration settings) to combine
separate sessions into coherent user profiles.
5.10.4.2 Cookie resurrection
If the user interface for persistent storage presents data in the
persistent storage features separately from data in HTTP session
cookies, then users are likely to delete data in one and not the
other. This would allow sites to use the two features as redundant
backup for each other, defeating a user's attempts to protect his
privacy.
5.10.5 Security5.10.5 保安性
5.10.5.1 DNS spoofing attacks
Because of the potential for DNS spoofing attacks, one cannot
guarantee that a host claiming to be in a certain domain really is
from that domain. To mitigate this, pages can use SSL. Pages using
SSL can be sure that only pages using SSL that have certificates
identifying them as being from the same domain can access their
local storage areas and databases.
5.10.5.2 Cross-directory attacks
Different authors sharing one host name, for example users
hosting content on geocities.com, all share one
persistent storage object and one set of databases. There is no
feature to restrict the access by pathname. Authors on shared hosts
are therefore recommended to avoid using the persistent storage
features, as it would be trivial for other authors to read from and
write to the same storage area or database.
Even if a path-restriction feature was made
available, the usual DOM scripting security model would make it
trivial to bypass this protection and access the data from any
path.
5.10.5.3 Implementation risks
The two primary risks when implementing these persistent storage
features are letting hostile sites read information from other
domains, and letting hostile sites write information that is then
read from other domains.
Letting third-party sites read data that is not supposed to be
read from their domain causes information leakage, For
example, a user's shopping wishlist on one domain could be used by
another domain for targeted advertising; or a user's
work-in-progress confidential documents stored by a word-processing
site could be examined by the site of a competing company.
Letting third-party sites write data to the storage areas of
other domains can result in information spoofing, which is
equally dangerous. For example, a hostile site could add items to a
user's wishlist; or a hostile site could set a user's session
identifier to a known ID that the hostile site can then use to track
the user's actions on the victim site.
Thus, strictly following the origin model described
in this specification is important for user security.
5.10.5.4 SQL and user agents
User agent implementors are strongly encouraged to audit all
their supported SQL statements for security implications. For
example, LOAD DATA INFILE is likely to pose
security risks and there is little reason to support it.
In general, it is recommended that user agents not support
features that control how databases are stored on disk. For example,
there is little reason to allow Web authors to control the character
encoding used in the disk representation of the data, as all data in
ECMAScript is implicitly UTF-16.
5.10.5.5 SQL injection
Authors are strongly recommended to make use of the ? placeholder feature of the executeSql() method,
and to never construct SQL statements on the fly.
5.11 Links5.11 リンク
5.11.1 Hyperlink elements5.11.1 ハイパーリンク要素
The a, area, and link
elements can, in certain situations described in the definitions of
those elements, represent hyperlinks.
The href
attribute on a hyperlink element must have a value that is a
valid URL. This URL is the destination
resource of the hyperlink.
The href attribute on
a and area elements is not required; when
those elements do not have href attributes they do not
represent hyperlinks.
The href attribute on the
link element is required, but whether a
link element represents a hyperlink or not depends on
the value of the rel attribute
of that element.
The target
attribute, if present, must be a valid browsing context name
or keyword. User agents use this name when following
hyperlinks.
The ping attribute, if
present, gives the URLs of the resources that are interested in
being notified if the user follows the hyperlink. The value must be
a space separated list of one or more valid URLs. The
value is used by the user agent when following
hyperlinks.
For a and area elements that represent
hyperlinks, the relationship between the document containing the
hyperlink and the destination resource indicated by the hyperlink is
given by the value of the element's rel attribute, which
must be a set of space-separated tokens. The allowed values and their meanings are defined
below. The rel attribute has
no default value. If the attribute is omitted or if none of the
values in the attribute are recognized by the UA, then the document
has no particular relationship with the destination resource other
than there being a hyperlink between the two.
The media
attribute describes for which media the target document was
designed. It is purely advisory. The value must be a valid media query. [MQ] The default,
if the media attribute is
omitted, is all.
The hreflang
attribute on hyperlink elements, if present, gives the language of
the linked resource. It is purely advisory. The value must be a
valid RFC 3066 language code. [RFC3066]
User agents must not consider this attribute authoritative —
upon fetching the resource, user agents must use only language
information associated with the resource to determine its language,
not metadata included in the link to the resource.
The type
attribute, if present, gives the MIME type of the linked
resource. It is purely advisory. The value must be a valid MIME
type, optionally with parameters. [RFC2046] User agents must not consider the
type attribute
authoritative — upon fetching the resource, user agents must
not use metadata included in the link to the resource to determine
its type.
5.11.2 Following hyperlinks
When a user follows a hyperlink, the user agent must
navigate a browsing context to the
URL given by the href attribute of that
hyperlink. In the case of server-side image maps, the URL of the
hyperlink must further have its hyperlink suffix appended
to it.
If the user indicated a specific browsing context
when following the hyperlink, or if the user agent is configured to
follow hyperlinks by navigating a particular browsing context, then
that must be the browsing context that is
navigated.
Otherwise, if the hyperlink element is an a or
area element that has a target attribute, then the
browsing context that is navigated must be chosen by
applying the rules for choosing a browsing context given a
browsing context name, using the value of the target attribute as the
browsing context name. If these rules result in the creation of a
new browsing context, it must be navigated with
replacement enabled.
Otherwise, if the hyperlink element is a sidebar hyperlink and the user
agent implements a feature that can be considered a secondary
browsing context, such a secondary browsing context may be selected
as the browsing context to be navigated.
Otherwise, if the hyperlink element is an a or
area element with no target attribute, but one of
the child nodes of the head element is a
base element with a target attribute, then the browsing
context that is navigated must be chosen by applying the rules
for choosing a browsing context given a browsing context name,
using the value of the target
attribute of the first such base element as the
browsing context name. If these rules result in the creation of a
new browsing context, it must be navigated with
replacement enabled.
Otherwise, the browsing context that must be navigated is the
same browsing context as the one which the hyperlink element itself
is in.そうでない場合、ナビゲーションが行われなければならない閲覧文脈は、ハイパーリンク要素自体が含まれている閲覧文脈と同じものです。
The navigation must be done with the browsing
context that contains the Document object with
which the hyperlink's element in question is associated as the
source browsing context.
5.11.2.1 Hyperlink auditing
If an a or area hyperlink element has a
ping attribute and the user
follows the hyperlink, the user agent must take the ping attribute's value, split that string on
spaces, resolve each
resulting token, and then should send a request (as described below)
to each of the resulting absolute
URLs. (Tokens that fail to resolve are ignored.) This may be
done in parallel with the primary request, and is independent of the
result of that request.利用者エージェントは、a や area のハイパーリンク要素が ping 属性を持つ場合で、
利用者が当該ハイパーリンクをたどった場合、ping
属性の値をもってこの文字列を間隔で分割し、
得られた字句のそれぞれを解決しなければならず、
その後、得られた絶対
URL のそれぞれについて要求 (後述) を送信するべきです。
(解決に失敗した字句は無視します。)
これは主たる要求と並列に行っても構わず、
主たる要求の結果とは独立したものです。
User agents should allow the user to adjust this behavior, for
example in conjunction with a setting that disables the sending of
HTTP Referer headers. Based on the user's
preferences, UAs may either ignore the ping attribute altogether, or
selectively ignore URLs in the list (e.g. ignoring any third-party
URLs).利用者エージェントは、利用者にこの動作の調整、例えば HTTP Referer 頭部の送信を無効化する設定と組み合わせることを認めるべきです。
利用者エージェントは、利用者の設定に基づき、ping
属性全体を無視するか、または並び中の一部の URL
を選択的に無視 (例えば第3者 URL を無視) するかのいずれかを行って構いません。
For URLs that are HTTP URLs, the requests must be performed by
fetching the specified URLs using the
POST method, with an entity body with the MIME type text/ping consisting of the four-character string
"PING". All relevant cookie and HTTP
authentication headers must be included in the request. Which other
headers are required depends on the URLs involved.
- If both the address
of the
Document object containing the hyperlink being
audited and the ping URL have the same origin
- The request must include a
Ping-From HTTP
header with, as its value, the address of the document containing the hyperlink,
and a Ping-To HTTP header with, as its value,
the address of the absolute URL of the target of the
hyperlink. The request must not include a Referer HTTP header.
- Otherwise, if the origins are different, but the document
containing the hyperlink being audited was not retrieved over an
encrypted connectionそれ以外の場合、起源が異なる場合で、監査されるハイパーリンクを含んでいる文書が暗号化された接続上で取り出された場合
- The request must include a
Referer HTTP
header [sic] with, as its value, the address of the document containing the hyperlink, a
Ping-From HTTP header with the same value,
and a Ping-To HTTP header with, as its value,
the address of the target of the hyperlink.
- Otherwise, the origins are different and the document
containing the hyperlink being audited was retrieved over an
encrypted connectionそれ以外の場合、起源が異なっており監査されるハイパーリンクが含まれている文書が暗号化された接続上で取り出された場合
- The request must include a
Ping-To HTTP
header with, as its value, the address of the target of the
hyperlink. The request must neither include a Referer HTTP header nor include a Ping-From HTTP header.要求は Ping-To HTTP
頭部を、ハイパーリンクの対象の番地を値として含めなければなりません。
要求は、 Referer HTTP 頭部を含んでも、
Ping-From HTTP 頭部を含んでもなりません。
To save bandwidth, implementors might also wish to
consider omitting optional headers such as Accept from
these requests.実装者は、帯域を節約するため、 Accept などの省略可能な頭部をこれらの要求から省くことを検討するといいかもしれません。
User agents must, unless otherwise specified by the user, honor
the HTTP headers (including, in particular, redirects and HTTP
cookie headers), but must ignore any entity bodies returned in the
responses. User agents may close the connection prematurely once
they start receiving an entity body. [RFC2109] [RFC2965]
For URLs that are not HTTP URLs, the requests must be performed
by fetching the specified URL normally,
and discarding the results.
When the ping attribute is
present, user agents should clearly indicate to the user that
following the hyperlink will also cause secondary requests to be
sent in the background, possibly including listing the actual target
URLs.利用者エージェントは、ping
属性が存在する場合、ハイパーリンクをたどると二次要求も背景で送られることになることも、
例えば実際の対象 URL の一覧を含めることにより、明確に示すべきです。
For example, a visual user agent could include
the hostnames of the target ping URLs along with the hyperlink's
actual URL in a status bar or tooltip.
The ping attribute is redundant
with pre-existing technologies like HTTP redirects and JavaScript
in allowing Web pages to track which off-site links are most
popular or allowing advertisers to track click-through rates.ping
属性は、 HTTP リダイレクトや JavaScript で Web 頁がサイト外のリンクのどれが人気が高いかを調べたり、
広告主がクリック通過率を追跡したりできるようにします。
However, the ping attribute
provides these advantages to the user over those alternatives:しかし、 ping 属性はこれらの代替案に対して利用者に次のような利点を与えます。
It allows the user to see the final target URL
unobscured.最終的な対象 URL を利用者が不明瞭にせずに見れるようにします。
It allows the UA to inform the user about the out-of-band
notifications.利用者エージェントが利用者に帯域外通知を知らせます。
It allows the paranoid user to disable the notifications
without losing the underlying link functionality.偏執証の利用者が下位リンク機能を損なわずに通知を無効化できます。
It allows the UA to optimize the use of available network
bandwidth so that the target page loads faster.利用者エージェントが利用可能ネットワーク帯域の利用量を最適化し、
対象頁の読み込みが早くなるようにします。
Thus, while it is possible to track users without this feature,
authors are encouraged to use the ping attribute so that the user agent
can improve the user experience.ですから、この機能をなしに利用者を追跡することも可能ですが、
ping 属性を使い、
利用者エージェントが利用者の体験を向上させられるようにすることを著者にはお勧めします。
5.11.3 Link types5.11.3 リンク型
The following table summarizes the link types that are defined by
this specification. This table is non-normative; the actual
definitions for the link types are given in the next few
sections.
In this section, the term referenced document refers to
the resource identified by the element representing the link, and
the term current document refers to the resource within
which the element representing the link finds itself.
To determine which link types apply to a link,
a, or area element, the element's rel attribute must be split on spaces. The resulting tokens are the link
types that apply to that element.
Unless otherwise specified, a keyword must not be specified more
than once per rel
attribute.
| Link typeリンク型 |
Effect on... |
Brief description簡単な説明 |
|---|
link |
a and area |
|---|
alternate |
Hyperlink |
Hyperlink |
Gives alternate representations of the current document. |
archives |
Hyperlink |
Hyperlink |
Provides a link to a collection of records, documents, or other materials of historical interest. |
author |
Hyperlink |
Hyperlink |
Gives a link to the current document's author. |
bookmark |
not allowed |
Hyperlink |
Gives the permalink for the nearest ancestor section. |
external |
not allowed |
Hyperlink |
Indicates that the referenced document is not part of the same site as the current document. |
feed |
Hyperlink |
Hyperlink |
Gives the address of a syndication feed for the current document. |
first |
Hyperlink |
Hyperlink |
Indicates that the current document is a part of a series, and that the first document in the series is the referenced document. |
help |
Hyperlink |
Hyperlink |
Provides a link to context-sensitive help. |
icon |
External Resource |
not allowed |
Imports an icon to represent the current document. |
index |
Hyperlink |
Hyperlink |
Gives a link to the document that provides a table of contents or index listing the current document. |
last |
Hyperlink |
Hyperlink |
Indicates that the current document is a part of a series, and that the last document in the series is the referenced document. |
license |
Hyperlink |
Hyperlink |
Indicates that the current document is covered by the copyright license described by the referenced document. |
next |
Hyperlink |
Hyperlink |
Indicates that the current document is a part of a series, and that the next document in the series is the referenced document. |
nofollow |
not allowed |
Hyperlink |
Indicates that the current document's original author or publisher does not endorse the referenced document. |
noreferrer |
not allowed |
Hyperlink |
Requires that the user agent not send an HTTP Referer header if the user follows the hyperlink. |
pingback |
External Resource |
not allowed |
Gives the address of the pingback server that handles pingbacks to the current document. |
prefetch |
External Resource |
not allowed |
Specifies that the target resource should be preemptively cached. |
prev |
Hyperlink |
Hyperlink |
Indicates that the current document is a part of a series, and that the previous document in the series is the referenced document. |
search |
Hyperlink |
Hyperlink |
Gives a link to a resource that can be used to search through the current document and its related pages. |
stylesheet |
External Resource |
not allowed |
Imports a stylesheet. |
sidebar |
Hyperlink |
Hyperlink |
Specifies that the referenced document, if retrieved, is intended to be shown in the browser's sidebar (if it has one). |
tag |
Hyperlink |
Hyperlink |
Gives a tag (identified by the given address) that applies to the current document. |
up |
Hyperlink |
Hyperlink |
Provides a link to a document giving the context for the current document. |
Some of the types described below list synonyms for these
values. These are to be handled as specified by user agents, but
must not be used in documents.
5.11.3.1 Link type "alternate"5.11.3.1 リンク型「alternate」
The alternate keyword may be
used with link, a, and area
elements. For link elements, if the rel attribute does not also contain the
keyword stylesheet, it creates a
hyperlink; but if it
does also contain the keyword stylesheet, the alternate keyword instead modifies the
meaning of the stylesheet
keyword in the way described for that keyword, and the rest of this
subsection doesn't apply.
The alternate keyword
indicates that the referenced document is an alternate
representation of the current document.
The nature of the referenced document is given by the media, hreflang, and type attributes.
If the alternate keyword is
used with the media
attribute, it indicates that the referenced document is intended for use
with the media specified.
If the alternate keyword is
used with the hreflang
attribute, and that attribute's value differs from the root
element's language, it indicates that the
referenced document is a translation.
If the alternate keyword is
used with the type
attribute, it indicates that the referenced document is a
reformulation of the current document in the specified format.
The media, hreflang, and type attributes can be combined
when specified with the alternate
keyword.
For example, the following link is a French translation that
uses the PDF format:
<link rel=alternate type=application/pdf hreflang=fr href=manual-fr>
If the alternate keyword is
used with the type
attribute set to the value application/rss+xml
or the value application/atom+xml, then the
user agent must treat the link as it would if it had the feed keyword specified as well.
The alternate link
relationship is transitive — that is, if a document links to
two other documents with the link type "alternate", then, in addition to
implying that those documents are alternative representations of the
first document, it is also implying that those two documents are
alternative representations of each other.
5.11.3.2 Link type "archives"5.11.3.2 リンク型「archives」
The archives keyword may be
used with link, a, and area
elements. For link elements, it creates a hyperlink.
The archives keyword indicates
that the referenced document describes a collection of records,
documents, or other materials of historical interest.
A blog's index page could link to an index of the
blog's past posts with rel="archives".
Synonyms: For historical reasons, user agents
must also treat the keyword "archive" like the
archives keyword.
5.11.3.3 Link type "author"5.11.3.3 リンク型「author」
The author keyword may be
used with link, a, and area
elements. For link elements, it creates a hyperlink.
For a and area elements, the author keyword indicates that the
referenced document provides further information about the author of
the section that the element defining the hyperlink applies to.
For link elements, the author keyword indicates that the
referenced document provides further information about the author
for the page as a whole.
The "referenced document" can be, and often is, a
mailto: URL giving the e-mail address of the
author. [MAILTO]
Synonyms: For historical reasons, user agents
must also treat link, a, and
area elements that have a rev
attribute with the value "made" as having the author keyword specified as a link
relationship.
5.11.3.4 Link type "bookmark"5.11.3.4 リンク型「bookmark」
The bookmark keyword may be
used with a and area elements.
The bookmark keyword gives a
permalink for the nearest ancestor article element of
the linking element in question, or of the section the linking element is most
closely associated with, if there are no ancestor
article elements.
The following snippet has three permalinks. A user agent could
determine which permalink applies to which part of the spec by
looking at where the permalinks are given.
...
<body>
<h1>Example of permalinks</h1>
<div id="a">
<h2>First example</h2>
<p><a href="a.html" rel="bookmark">This</a> permalink applies to
only the content from the first H2 to the second H2. The DIV isn't
exactly that section, but it roughly corresponds to it.</p>
</div>
<h2>Second example</h2>
<article id="b">
<p><a href="b.html" rel="bookmark">This</a> permalink applies to
the outer ARTICLE element (which could be, e.g., a blog post).</p>
<article id="c">
<p><a href="c.html" rel="bookmark">This</a> permalink applies to
the inner ARTICLE element (which could be, e.g., a blog comment).</p>
</article>
</article>
</body>
...
5.11.3.5 Link type "external"5.11.3.5 リンク型「external」
The external keyword may be
used with a and area elements.
The external keyword indicates
that the link is leading to a document that is not part of the site
that the current document forms a part of.
5.11.3.6 Link type "feed"5.11.3.6 リンク型「feed」
The feed keyword may be used with
link, a, and area
elements. For link elements, it creates a hyperlink.
The feed keyword indicates that the
referenced document is a syndication feed. If the alternate link type is also specified,
then the feed is specifically the feed for the current document;
otherwise, the feed is just a syndication feed, not necessarily
associated with a particular Web page.
The first link, a, or area
element in the document (in tree order) that creates a hyperlink
with the link type feed must be
treated as the default syndication feed for the purposes of feed
autodiscovery.
The feed keyword is
implied by the alternate link
type in certain cases (q.v.).
The following two link elements are equivalent:
both give the syndication feed for the current page:
<link rel="alternate" type="application/atom+xml" href="data.xml">
<link rel="feed alternate" href="data.xml">
The following extract offers various different syndication
feeds:
<p>You can access the planets database using Atom feeds:</p>
<ul>
<li><a href="recently-visited-planets.xml" rel="feed">Recently Visited Planets</a></li>
<li><a href="known-bad-planets.xml" rel="feed">Known Bad Planets</a></li>
<li><a href="unexplored-planets.xml" rel="feed">Unexplored Planets</a></li>
</ul>
5.11.3.7 Link type "help"5.11.3.7 リンク型「help」
The help keyword may be used with
link, a, and area
elements. For link elements, it creates a hyperlink.
For a and area elements, the help keyword indicates that the referenced
document provides further help information for the parent of the
element defining the hyperlink, and its children.
In the following example, the form control has associated
context-sensitive help. The user agent could use this information,
for example, displaying the referenced document if the user presses
the "Help" or "F1" key.
<p><label> Topic: <input name=topic> <a href="help/topic.html" rel="help">(Help)</a></label></p>
For link elements, the help keyword indicates that the referenced
document provides help for the page as a whole.
5.11.3.8 Link type "icon"5.11.3.8 リンク型「icon」
The icon keyword may be used with
link elements, for which it creates an external resource link.
The specified resource is an icon representing the page or site,
and should be used by the user agent when representing the page in
the user interface.specified resource is an icon representing the page or site, and should be used by the user agent when representing the page in the user 界面。
Icons could be auditory icons, visual icons, or other kinds of
icons. If multiple icons are provided, the user agent must select
the most appropriate icon according to the type, media, and sizes attributes. If there are
multiple equally appropriate icons, user agents must use the last
one declared in tree order. If the user agent tries to
use an icon but that icon is determined, upon closer examination, to
in fact be inappropriate (e.g. because it uses an unsupported
format), then the user agent must try the next-most-appropriate icon
as determined by the attributes.
There is no default type for resources given by the icon keyword. However, for the purposes of
determining the type of the
resource, user agents must expect the resource to be an image.
The sizes
attribute gives the sizes of icons for visual media.
If specified, the attribute must have a value that is an
unordered set of unique space-separated tokens. The
values must all be either any or a value that consists of
two valid non-negative
integers that do not have a leading U+0030 DIGIT ZERO (0)
character and that are separated by a single U+0078 LATIN SMALL
LETTER X character.
The keywords represent icon sizes.
To parse and process the attribute's value, the user agent must
first split the attribute's
value on spaces, and must then parse each resulting keyword
to determine what it represents.
The any keyword
represents that the resource contains a scalable icon, e.g. as
provided by an SVG image.
Other keywords must be further parsed as follows to determine
what they represent:
If the keyword doesn't contain exactly one U+0078 LATIN
SMALL LETTER X character, then this keyword doesn't represent
anything. Abort these steps for that keyword.
Let width string be the string before
the "x".
Let height string be the string after the
"x".
If either width string or height string start with a U+0030 DIGIT ZERO (0)
character or contain any characters other than characters in the
range U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9), then this
keyword doesn't represent anything. Abort these steps for that
keyword.
Apply the rules for parsing non-negative
integers to width string to obtain width.
Apply the rules for parsing non-negative
integers to height string to obtain height.
The keyword represents that the resource contains a bitmap
icon with a width of width device pixels and a
height of height device pixels.
The keywords specified on the sizes attribute must not represent
icon sizes that are not actually available in the linked
resource.
If the attribute is not specified, then the user agent must
assume that the given icon is appropriate, but less appropriate than
an icon of a known and appropriate size.
The following snippet shows the top part of an application with
several icons.
<!DOCTYPE HTML>
<html>
<head>
<title>lsForums — Inbox</title>
<link rel=icon href=favicon.png sizes="16x16">
<link rel=icon href=windows.ico sizes="32x32 48x48">
<link rel=icon href=mac.icns sizes="128x128 512x512 8192x8192 32768x32768">
<link rel=icon href=iphone.png sizes="59x60">
<link rel=icon href=gnome.svg sizes="any">
<link rel=stylesheet href=lsforums.css>
<script src=lsforums.js></script>
<meta name=application-name content="lsForums">
</head>
<body>
...
5.11.3.9 Link type "license"5.11.3.9 リンク型「license」
The license keyword may be used
with link, a, and area
elements. For link elements, it creates a hyperlink.
The license keyword indicates
that the referenced document provides the copyright license terms
under which the current document is provided.
Synonyms: For historical reasons, user agents
must also treat the keyword "copyright" like
the license keyword.
5.11.3.10 Link type "nofollow"5.11.3.10 リンク型「nofollow」
The nofollow keyword may be
used with a and area elements.
The nofollow keyword indicates
that the link is not endorsed by the original author or publisher of
the page, or that the link to the referenced document was included
primarily because of a commercial relationship between people
affiliated with the two pages.
5.11.3.11 Link type "noreferrer"5.11.3.11 リンク型「noreferrer」
The noreferrer keyword may be
used with a and area elements.
If a user agent follows a link defined by an a or
area element that has the noreferrer keyword, the user agent
must not include a Referer HTTP header (or equivalent for
other protocols) in the request.
This keyword also causes the opener attribute to remain null if the
hyperlink creates a new browsing context.
5.11.3.12 Link type "pingback"5.11.3.12 リンク型「pingback」
The pingback keyword may be
used with link elements, for which it creates an external resource link.
For the semantics of the pingback keyword, see the Pingback 1.0
specification. [PINGBACK]
5.11.3.13 Link type "prefetch"5.11.3.13 リンク型「prefetch」
The prefetch keyword may be
used with link elements, for which it creates an external resource link.
The prefetch keyword indicates
that preemptively fetching and caching the specified resource is
likely to be beneficial, as it is highly likely that the user will
require this resource.
There is no default type for resources given by the prefetch keyword.
5.11.3.14 Link type "search"5.11.3.14 リンク型「search」
The search keyword may be used
with link, a, and area
elements. For link elements, it creates a hyperlink.
The search keyword indicates that
the referenced document provides an interface specifically for
searching the document and its related resources.
OpenSearch description documents can be used with
link elements and the search link type to enable user agents to
autodiscover search interfaces. [OPENSEARCH]
5.11.3.15 Link type "stylesheet"5.11.3.15 リンク型「stylesheet」
The stylesheet keyword may be
used with link elements, for which it creates an external resource link that
contributes to the styling processing model.
The specified resource is a resource that describes how to
present the document. Exactly how the resource is to be processed
depends on the actual type of the resource.
If the alternate keyword is
also specified on the link element, then the link is an
alternative stylesheet; in this case, the title attribute must be specified on the
link element, with a non-empty value.
The default type for resources given by the stylesheet keyword is text/css.
Quirk: If the document has been set to
quirks mode and the Content-Type metadata of the external
resource is not a supported style sheet type, the user agent must
instead assume it to be text/css.
The sidebar keyword may be used
with link, a, and area
elements. For link elements, it creates a hyperlink.
The sidebar keyword indicates
that the referenced document, if retrieved, is intended to be shown
in a secondary browsing context (if possible), instead
of in the current browsing context.
A hyperlink element with with the
sidebar keyword specified is a .
5.11.3.17 Link type "tag"5.11.3.17 リンク型「tag」
The tag keyword may be used
with link, a, and area
elements. For link elements, it creates a hyperlink.
The tag keyword indicates that the
tag that the referenced document represents applies to the
current document.
5.11.3.18 Hierarchical link types5.11.3.18 階層的リンク型
Some documents form part of a hierarchical structure of
documents.文書によっては、文書群の階層的な構造の一部を形成していることがあります。
A hierarchical structure of documents is one where each document
can have various subdocuments. The document of which a document is a
subdocument is said to be the document's parent. A document
with no parent forms the top of the hierarchy.
A document may be part of multiple hierarchies.文書は複数の階層の一部であっても構いません。
5.11.3.18.1 Link type "index"5.11.3.18.1 リンク型「index」
The index keyword may be used with
link, a, and area
elements. For link elements, it creates a hyperlink.
The index keyword indicates that
the document is part of a hierarchical structure, and that the link
is leading to the document that is the top of the hierarchy. It
conveys more information when used with the up keyword (q.v.).
Synonyms: For historical reasons, user agents
must also treat the keywords "top", "contents", and "toc" like the
index keyword.
5.11.3.18.2 Link type "up"5.11.3.18.2 リンク型「up」
The up keyword may be used with
link, a, and area
elements. For link elements, it creates a hyperlink.
The up keyword indicates that the
document is part of a hierarchical structure, and that the link is
leading to the document that is the parent of the current
document.
The up keyword may be repeated within
a rel attribute to indicate
the hierarchical distance from the current document to the
referenced document. Each occurrence of the keyword represents one
further level. If the index keyword
is also present, then the number of up
keywords is the depth of the current page relative to the top of the
hierarchy. Only one link is created for the set of one or more up keywords and, if present, the index keyword.
If the page is part of multiple hierarchies, then they should be
described in different paragraphs. User agents must scope any
interpretation of the up and index keywords together indicating the
depth of the hierarchy to the paragraph in which the
link finds itself, if any, or to the document otherwise.
When two links have both the up and
index keywords specified together in
the same scope and contradict each other by having a different
number of up keywords, the link with the
greater number of up keywords must be
taken as giving the depth of the document.
This can be used to mark up a navigation style sometimes known
as bread crumbs. In the following example, the current page can be
reached via two paths.
<nav>
<p>
<a href="/" rel="index up up up">Main</a> >
<a href="/products/" rel="up up">Products</a> >
<a href="/products/dishwashers/" rel="up">Dishwashers</a> >
<a>Second hand</a>
</p>
<p>
<a href="/" rel="index up up">Main</a> >
<a href="/second-hand/" rel="up">Second hand</a> >
<a>Dishwashers</a>
</p>
</nav>
The relList DOM
attribute (e.g. on the a element) does not currently
represent multiple up keywords (the
interface hides duplicates).
5.11.3.19 Sequential link types
Some documents form part of a sequence of documents.
A sequence of documents is one where each document can have a
previous sibling and a next sibling. A document
with no previous sibling is the start of its sequence, a document
with no next sibling is the end of its sequence.
A document may be part of multiple sequences.
5.11.3.19.1 Link type "first"5.11.3.19.1 リンク型「first」
The first keyword may be used with
link, a, and area
elements. For link elements, it creates a hyperlink.
The first keyword indicates that
the document is part of a sequence, and that the link is leading to
the document that is the first logical document in the sequence.
Synonyms: For historical reasons, user agents
must also treat the keywords "begin" and
"start" like the first keyword.
5.11.3.19.2 Link type "last"5.11.3.19.2 リンク型「last」
The last keyword may be used with
link, a, and area
elements. For link elements, it creates a hyperlink.
The last keyword indicates that the
document is part of a sequence, and that the link is leading to the
document that is the last logical document in the sequence.
Synonyms: For historical reasons, user agents
must also treat the keyword "end" like the
last keyword.
5.11.3.19.3 Link type "next"5.11.3.19.3 リンク型「next」
The next keyword may be used with
link, a, and area
elements. For link elements, it creates a hyperlink.
The next keyword indicates that the
document is part of a sequence, and that the link is leading to the
document that is the next logical document in the sequence.
5.11.3.19.4 Link type "prev"5.11.3.19.4 リンク型「prev」
The prev keyword may be used with
link, a, and area
elements. For link elements, it creates a hyperlink.
The prev keyword indicates that the
document is part of a sequence, and that the link is leading to the
document that is the previous logical document in the sequence.
Synonyms: For historical reasons, user agents
must also treat the keyword "previous" like
the prev keyword.
5.11.3.20 Other link types5.11.3.20 その他のリンク型
Other than the types defined above, only types defined as
extensions in the WHATWG Wiki
RelExtensions page may be used with the rel attribute on link, a,
and area elements. [WHATWGWIKI]
Anyone is free to edit the WHATWG Wiki RelExtensions page at any
time to add a type. Extension types must be specified with the
following information:誰でもいつでも自由に WHATWG Wiki RelExtensions 頁を編集して型を追加できます。
拡張型には次の情報を指定しなければなりません。
- Keywordキーワード
The actual value being defined. The value should not be
confusingly similar to any other defined value (e.g. differing only
in case).実際の定義される値です。対は他の定義済みの値と混乱するような似た値 (例えば大文字・小文字の違いだけのもの) ではないべきです。
- Effect on...
link
-
One of the following:次のいずれかです。
- not allowed認めない
- The keyword is not allowed to be specified on
link elements.
- Hyperlinkハイパーリンク
- The keyword may be specified on a
link element;
it creates a hyperlink
link.
- External Resource外部資源
- The keyword may be specified on a
link element;
it creates a external
resource link.
- Effect on...
a and area
-
One of the following:次のいずれかです。
- not allowed認めない
- The keyword is not allowed to be specified on
a
and area elements.
- Hyperlinkハイパーリンク
- The keyword may be specified on
a and
area elements.
- Brief description簡単な説明
A short description of what the keyword's meaning is.キーワードが何を意味するかの短い説明です。
- Link to more details詳細へのリンク
A link to a more detailed description of the keyword's
semantics and requirements. It could be another page on the Wiki,
or a link to an external page.キーワードの意味と要件についてのより詳しい説明へのリンクです。
リンク先は Wiki の他の頁でもいいですし、外部の頁へのリンクにもできます。
- Synonyms同義語
A list of other keyword values that have exactly the same
processing requirements. Authors must not use the values defined to
be synonyms, they are only intended to allow user agents to support
legacy content.まったく同じ処理要件を持つ他のキーワード値のリストです。
著者は同義語として定義された値を使ってはなりません。
同義語は利用者エージェントが遺物内容に対応できるようにすることを想定しています。
- Status状態
-
One of the following:次のいずれかです。
- Proposal提案
- The keyword has not received wide peer review and
approval. It is included for completeness because pages use the
keyword. Pages should not use the keyword.
- Accepted承認済み
- The keyword has received wide peer review and approval. It
has a specification that unambiguously defines how to handle
pages that use the keyword, including when they use them in
incorrect ways. Pages may use the keyword.
- Rejected却下済み
- The keyword has received wide peer review and it has been
found to have significant problems. Pages must not use the
keyword. When a keyword has this status, the "Effect
on...
link" and "Effect on... a and
area" information should be set to "not
allowed".
If a keyword is added with the "proposal" status and found to
be redundant with existing values, it should be removed and listed
as a synonym for the existing value. If a keyword is added with
the "proposal" status and found to be harmful, then it should be
changed to "rejected" status, and its "Effect on..." information
should be changed accordingly.
Conformance checkers must use the information given on the WHATWG
Wiki RelExtensions page to establish if a value not explicitly
defined in this specification is allowed or not. When an author uses
a new type not defined by either this specification or the Wiki
page, conformance checkers should offer to add the value to the
Wiki, with the details described above, with the "proposal"
status.
This specification does not define how new values will get
approved. It is expected that the Wiki will have a community that
addresses this.
6 User Interaction6 利用者対話
This section describes various features that allow authors to
enable users to edit documents and parts of documents
interactively.この章では、著者が文書や文書の一部を利用者が対話的に編集させられるようにするための様々な機能を説明します。
6.1 Introduction6.1 はじめに
This section is non-normative.この節は規定の一部ではありません。
Would be nice to explain how these features
work together.
6.2 The hidden attribute6.2 hidden 属性
All elements may have the hidden
content attribute set. The hidden
attribute is a boolean attribute. When specified on an
element, it indicates that the element is not yet, or is no longer,
relevant. User agents should not render elements that have the hidden attribute specified.
In the following skeletal example, the attribute is used to hide
the Web game's main screen until the user logs in:
<h1>The Example Game</h1>
<section id="login">
<h2>Login</h2>
<form>
...
<!-- calls login() once the user's credentials have been checked -->
</form>
<script>
function login() {
// switch screens
document.getElementById('login').hidden = true;
document.getElementById('game').hidden = false;
}
</script>
</section>
<section id="game" hidden>
...
</section>
The hidden attribute must not be
used to hide content that could legitimately be shown in another
presentation. For example, it is incorrect to use hidden to hide panels in a tabbed dialog,
because the tabbed interface is merely a kind of overflow
presentation — showing all the form controls in one big page
with a scrollbar would be equivalent, and no less correct.
Elements in a section hidden by the hidden attribute are still active,
e.g. scripts and form controls in such sections still render execute
and submit respectively. Only their presentation to the user
changes.
The hidden DOM
attribute must reflect the content attribute of the
same name.
6.3 Activation6.3 活性化
The click() method must, if the
element has a defined activation behavior, run
synthetic click activation steps on the element. Otherwise,
the user agent must fire a click event at
the element.
The scrollIntoView([top]) method, when called, must cause
the element on which the method was called to have the attention of
the user called to it.
In a speech browser, this could happen by having the
current playback position move to the start of the given
element.
In visual user agents, if the argument is present and has the
value false, the user agent should scroll the element into view such
that both the bottom and the top of the element are in the viewport,
with the bottom of the element aligned with the bottom of the
viewport. If it isn't possible to show the entire element in that
way, or if the argument is omitted or is true, then the user agent
should instead align the top of the element with the top of the
viewport. If the entire scrollable part of the content is visible
all at once (e.g. if a page is shorter than the viewport), then the
user agent should not scroll anything. Visual user agents should
further scroll horizontally as necessary to bring the element to the
attention of the user.
Non-visual user agents may ignore the argument, or may treat it
in some media-specific manner most useful to the user.
6.5 Focus6.5 焦点
When an element is focused, key events received by the
document must be targeted at that element. There may be no element
focused; when no element is focused, key events received by the
document must be targetted at the body
element.
User agents may track focus for each browsing
context or Document individually, or may support
only one focused elment per top-level browsing context
— user agents should follow platform conventions in this
regard.
Which element(s) within a top-level browsing context
currently has focus must be independent of whether or not the
top-level browsing context itself has the system
focus.
When an element is focused, the element matches the
CSS :focus pseudo-class.
6.5.1 Sequential focus navigation
The tabindex
content attribute specifies whether the element is focusable,
whether it can be reached using sequential focus navigation, and the
relative order of the element for the purposes of sequential focus
navigation. The name "tab index" comes from the common use of the
"tab" key to navigate through the focusable elements. The term
"tabbing" refers to moving forward through the focusable elements
that can be reached using sequential focus navigation.
The tabindex attribute, if
specified, must have a value that is a valid
integer.
If the attribute is specified, it must be parsed using the
rules for parsing integers. The attribute's values have
the following meanings:
- If the attribute is omitted or parsing the value returns an
error
-
The user agent should follow platform conventions to determine if
the element is to be focusable and, if so, whether the element can
be reached using sequential focus navigation, and if so, what its
relative order should be.
- If the value is a negative integer
-
The user agent must allow the element to be focused, but should
not allow the element to be reached using sequential focus
navigation.
- If the value is a zero
-
The user agent must allow the element to be focused, should
allow the element to be reached using sequential focus navigation,
and should follow platform conventions to determine the element's
relative order.
- If the value is greater than zero
-
The user agent must allow the element to be focused, should
allow the element to be reached using sequential focus navigation,
and should place the element in the sequential focus navigation
order so that it is:
before any focusable element whose tabindex attribute has been
omitted or whose value, when parsed, returns an error,
before any focusable element whose tabindex attribute has a value equal
to or less than zero,
after any element whose tabindex attribute has a value
greater than zero but less than the value of the tabindex attribute on the
element,
after any element whose tabindex attribute has a value equal
to the value of the tabindex
attribute on the element but that is earlier in the document in
tree order than the element,
before any element whose tabindex attribute has a value equal
to the value of the tabindex
attribute on the element but that is later in the document in
tree order than the element, and
before any element whose tabindex attribute has a value
greater than the value of the tabindex attribute on the
element.
An element is focusable if the tabindex attribute's definition above
defines the element to be focusable and the element is
being rendered.
The tabIndex DOM
attribute must reflect the value of the tabindex content attribute. If the
attribute is not present, or parsing its value returns an error,
then the DOM attribute must return 0 for elements that are focusable
and −1 for elements that are not focusable.
6.5.2 Focus management6.5.2 焦点管理
The focusing steps are as follows:
If focusing the element will remove the focus from another
element, then run the unfocusing steps for that
element.
-
Make the element the currently focused element in its
top-level browsing context.
Some elements, most notably area, can correspond
to more than one distinct focusable area. If a particular area was
indicated when the element was focused, then that is the area that
must get focus; otherwise, e.g. when using the focus() method, the first such region in
tree order is the one that must be focused.
Fire a simple event that doesn't bubble called
focus at the element.
User agents must run the focusing steps for an
element whenever the user moves the focus to a
focusable element.
The unfocusing steps are as follows:
If the element is an input element, and the
change event applies to the
element, and the element does not have a defined activation
behavior, and the user has changed the element's value or its list of selected files
while the control was focused without committing that change, then
fire a simple event called change at the element, then
broadcast formchange
events at the element's form owner.
Unfocus the element.
Fire a simple event that doesn't bubble called
blur at the element.
User agents should run the unfocusing steps for an
element whenever the user moves the focus away from any
focusable element.
6.5.3 Document-level focus APIs6.5.3 文書水準焦点 API
The activeElement
attribute must return the element in the document that is
focused. If no element in the Document is focused, this
must return the body element.
The hasFocus() method
must return true if the document, one of its nested browsing contexts, or any element in
the document or its browsing contexts currently has the system
focus.
6.5.4 Element-level focus APIs6.5.4 要素水準焦点 API
The focus() method,
when invoked, must run the following algorithm:
If the element is marked as locked for focus, then abort
these steps.
If the element is not focusable, then abort these
steps.
Mark the element as locked for focus.
If the element is not already focused, run the focusing
steps for the element.
Unmark the element as locked for focus.
The blur() method, when
invoked, should run the unfocusing steps for the
element. User agents may selectively or uniformly ignore calls to
this method for usability reasons.
6.6 The text selection APIs6.6 テキスト選択 API
Every browsing context has a selection. The selection can be empty, and the
selection can have more than one range (a disjointed selection). The
user agent should allow the user to change the selection. User
agents are not required to let the user select more than one range,
and may collapse multiple ranges in the selection to a single range
when the user interacts with the selection. (But, of course, the
user agent may let the user create selections with multiple
ranges.)
This one selection must be shared by all the content of the
browsing context (though not by nested browsing contexts), including any editing hosts in
the document. (Editing hosts that are not inside a document cannot
have a selection.)
If the selection is empty (collapsed, so that it has only one
segment and that segment's start and end points are the same) then
the selection's position should equal the caret position. When the
selection is not empty, this specification does not define the caret
position; user agents should follow platform conventions in deciding
whether the caret is at the start of the selection, the end of the
selection, or somewhere else.
On some platforms (such as those using Wordstar editing
conventions), the caret position is totally independent of the start
and end of the selection, even when the selection is empty. On such
platforms, user agents may ignore the requirement that the cursor
position be linked to the position of the selection altogether.
Mostly for historical reasons, in addition to the browsing
context's selection, each
textarea and input element has an
independent selection. These are the text field selections.
User agents may selectively ignore attempts to use the API to
adjust the selection made after the user has modified the
selection. For example, if the user has just selected part of a
word, the user agent could ignore attempts to use the API call to
immediately unselect the selection altogether, but could allow
attempts to change the selection to select the entire word.
User agents may also allow the user to create selections that are
not exposed to the API.
The datagrid and select elements also
have selections, indicating which items have been picked by the
user. These are not discussed in this section.
This specification does not specify how selections
are presented to the user. The Selectors specification, in
conjunction with CSS, can be used to style text selections using the
::selection pseudo-element. [SELECTORS] [CSS21]
6.6.1 APIs for the browsing context selection6.6.1 閲覧文脈選択の API
The getSelection() method on
the Window interface must return the
Selection object representing the
selection of that Window object's
browsing context.
For historical reasons, the getSelection()
method on the HTMLDocument interface must return the
same Selection object.
[Stringifies] interface Selection {
readonly attribute Node anchorNode;
readonly attribute long anchorOffset;
readonly attribute Node focusNode;
readonly attribute long focusOffset;
readonly attribute boolean isCollapsed;
void collapse(in Node parentNode, in long offset);
void collapseToStart();
void collapseToEnd();
void selectAllChildren(in Node parentNode);
void deleteFromDocument();
readonly attribute long rangeCount;
Range getRangeAt(in long index);
void addRange(in Range range);
void removeRange(in Range range);
void removeAllRanges();
};
The Selection interface is represents a list of
Range objects. The first item in the list has index 0,
and the last item has index count-1, where
count is the number of ranges in the list. [DOM2RANGE]
All of the members of the Selection interface are
defined in terms of operations on the Range objects
represented by this object. These operations can raise exceptions,
as defined for the Range interface; this can therefore
result in the members of the Selection interface
raising exceptions as well, in addition to any explicitly called out
below.
The anchorNode
attribute must return the value returned by the startContainer attribute of the last
Range object in the list, or null if the list is
empty.
The anchorOffset
attribute must return the value returned by the startOffset attribute of the last Range
object in the list, or 0 if the list is empty.
The focusNode
attribute must return the value returned by the endContainer attribute of the last
Range object in the list, or null if the list is
empty.
The focusOffset
attribute must return the value returned by the endOffset attribute of the last Range
object in the list, or 0 if the list is empty.
The isCollapsed
attribute must return true if there are zero ranges, or if there is
exactly one range and its collapsed attribute
is itself true. Otherwise it must return false.
The collapse(parentNode, offset)
method must raise a WRONG_DOCUMENT_ERR DOM exception if
parentNode's Document is not the
HTMLDocument object with which the
Selection object is associated. Otherwise it is, and
the method must remove all the ranges in the Selection
list, then create a new Range object, add it to the
list, and invoke its setStart() and setEnd() methods with the parentNode and offset values as
their arguments.
The collapseToStart()
method must raise an INVALID_STATE_ERR DOM exception if
there are no ranges in the list. Otherwise, it must invoke the collapse() method with the
startContainer and startOffset values of the first Range
object in the list as the arguments.
The collapseToEnd()
method must raise an INVALID_STATE_ERR DOM exception if
there are no ranges in the list. Otherwise, it must invoke the collapse() method with the
endContainer and endOffset values of the last Range
object in the list as the arguments.
The selectAllChildren(parentNode)
method must invoke the collapse() method with the
parentNode value as the first argument and 0 as the
second argument, and must then invoke the selectNodeContents() method on the first (and only)
range in the list with the parentNode value as the
argument.
The deleteFromDocument()
method must invoke the deleteContents() method
on each range in the list, if any, from first to last.
The rangeCount
attribute must return the number of ranges in the list.
The getRangeAt(index)
method must return the indexth range in the list. If
index is less than zero or greater or equal to the value
returned by the rangeCount attribute, then
the method must raise an INDEX_SIZE_ERR DOM
exception.
The addRange(range)
method must add the given range Range object to the list
of selections, at the end (so the newly added range is the new last
range). Duplicates are not prevented; a range may be added more than
once in which case it appears in the list more than once, which (for
example) will cause stringification to return the
range's text twice.
The removeRange(range)
method must remove the first occurrence of range in the
list of ranges, if it appears at all.
The removeAllRanges()
method must remove all the ranges from the list of ranges, such that
the rangeCount
attribute returns 0 after the removeAllRanges()
method is invoked (and until a new range is added to the list,
either through this interface or via user interaction).
Objects implementing this interface must stringify to a concatenation
of the results of invoking the toString()
method of the Range object on each of the ranges of the
selection, in the order they appear in the list (first to last).
In the following document fragment, the emphasised parts
indicate the selection.
<p>The cute girl likes the <cite>Oxford English Dictionary</cite>.</p>
If a script invoked window.getSelection().toString(), the return value
would be "the Oxford English".
The Selection interface has no relation
to the DataGridSelection interface.Selection interface has no relation to the DataGridSelection 界面。
6.6.2 APIs for the text field selections6.6.2 テキスト欄選択の API
When we define HTMLTextAreaElement and
HTMLInputElement we will have to add the IDL given below to both of
their IDLs.
The input and textarea elements define
four members in their DOM interfaces for handling their text
selection:
void select();
attribute unsigned long selectionStart;
attribute unsigned long selectionEnd;
void setSelectionRange(in unsigned long start, in unsigned long end);
These methods and attributes expose and control the selection of
input and textarea text fields.
The select() method
must cause the contents of the text field to be fully selected.
The selectionStart
attribute must, on getting, return the offset (in logical order) to
the character that immediately follows the start of the
selection. If there is no selection, then it must return the offset
(in logical order) to the character that immediately follows the
text entry cursor.
On setting, it must act as if the setSelectionRange()
method had been called, with the new value as the first argument,
and the current value of the selectionEnd
attribute as the second argument, unless the current value of the
selectionEnd is
less than the new value, in which case the second argument must also
be the new value.
The selectionEnd
attribute must, on getting, return the offset (in logical order) to
the character that immediately follows the end of the selection. If
there is no selection, then it must return the offset (in logical
order) to the character that immediately follows the text entry
cursor.
On setting, it must act as if the setSelectionRange()
method had been called, with the current value of the selectionStart
attribute as the first argument, and new value as the second
argument.
The setSelectionRange(start, end) method
must set the selection of the text field to the sequence of
characters starting with the character at the startth position (in logical order) and ending with
the character at the (end-1)th
position. Arguments greater than the length of the value in the text
field must be treated as pointing at the end of the text field. If
end is less than or equal to start then the start of the selection and the end of
the selection must both be placed immediately before the character
with offset end. In UAs where there is no
concept of an empty selection, this must set the cursor to be just
before the character with offset end.
To obtain the currently selected text, the following JavaScript
suffices:
var selectionText = control.value.substring(control.selectionStart, control.selectionEnd);
...where control is the input
or textarea element.
Characters with no visible rendering, such as U+200D ZERO WIDTH
JOINER, still count as characters. Thus, for instance, the selection
can include just an invisible character, and the text insertion
cursor can be placed to one side or another of such a character.
When these methods and attributes are used with
input elements that are not displaying simple text
fields, they must raise an INVALID_STATE_ERR
exception.
The contenteditable
attribute is an enumerated attribute whose keywords are
the empty string, true, and false. The empty string and the true keyword map to the true state. The false keyword maps to the false state. In
addition, there is a third state, the inherit state, which is
the missing value default (and the invalid value
default).
If an HTML element has a contenteditable attribute set to
the true state, or it has its contenteditable attribute set to
the inherit state and if its nearest ancestor HTML element with the contenteditable attribute set to
a state other than the inherit state has its attribute set to the
true state, or if it and its ancestors all have their contenteditable attribute set to
the inherit state but the Document has designMode enabled, then the
UA must treat the element as editable (as described
below).
Otherwise, either the HTML
element has a contenteditable attribute set to
the false state, or its contenteditable attribute is set
to the inherit state and its nearest ancestor HTML element with the contenteditable attribute set to
a state other than the inherit state has its attribute set to the
false state, or all its ancestors have their contenteditable attribute set to
the inherit state and the Document itself has designMode disabled; either
way, the element is not editable.
The contentEditable DOM
attribute, on getting, must return the string "true" if the content attribute is set to the true
state, false" if the content attribute is set
to the false state, and "inherit"
otherwise. On setting, if the new value is an ASCII
case-insensitive match for the string "inherit" then the content attribute must be removed,
if the new value is an ASCII case-insensitive match for
the string "true" then the content attribute
must be set to the string "true", if the new
value is an ASCII case-insensitive match for the string
"false" then the content attribute must be set
to the string "false", and otherwise the
attribute setter must raise a SYNTAX_ERR exception.
The isContentEditable
DOM attribute, on getting, must return true if the element is
editable, and false otherwise.
If an element is editable and its parent element is
not, or if an element is editable and it has no parent
element, then the element is an editing host. Editable
elements can be nested. User agents must make editing hosts
focusable (which typically means they enter the tab order). An editing host can contain
non-editable sections, these are handled as described below. An
editing host can contain non-editable sections that contain further
editing hosts.
When an editing host has focus, it must have a caret
position that specifies where the current editing position
is. It may also have a selection.
How the caret and selection are represented depends
entirely on the UA.
6.7.1 User editing actions
There are several actions that the user agent should allow the
user to perform while the user is interacting with an editing
host. How exactly each action is triggered is not defined for every
action, but when it is not defined, suggested key bindings are
provided to guide implementors.利用者が編集ホストと対話している間に利用者が実行することを利用者エージェントが認めるべきである作用がいくつかあります。
すべての作用について正確にどのように誘発するのかを定義しているわけではありませんが、
定義していない場合には、実装者に対する指針として、鍵の束縛の案を提示します。
- Move the caret脱字記号を移動する
User agents must allow users to move the caret to any
position within an editing host, even into nested editable
elements. This could be triggered as the default action of keydown events with various key
identifiers and as the default action of mousedown events.利用者エージェントは、利用者が編集ホスト中の任意の位置
(入れ子になった編集可能要素の中を含みます。)
に脱字記号を移動させることを認めなければなりません。これは、
各種の鍵識別子についての keydown 事象の既定作用として、および mousedown 事象の既定作用として誘発することができます。
- Change the selection選択を変更する
User agents must allow users to change the
selection within an editing host, even into nested editable
elements. User agents may prevent selections from being made in
ways that cross from editable elements into non-editable elements
(e.g. by making each non-editable descendant atomically selectable,
but not allowing text selection within them). This could be
triggered as the default action of keydown events with various key
identifiers and as the default action of mousedown events.利用者エージェントは、利用者が編集ホスト中の選択を変更することを認めなければなりません
(入れ子になった編集可能要素の中を含みます)。
利用者エージェントは、編集可能要素と非編集可能要素を選択がまたぐことを
(例えば、非編集可能子孫がそれぞれ原子的に選択可能としながら、その中の文章を選択できないようにすることで)
拒んでも構いません。これは、各種の鍵識別子についての keydown 事象の既定作用として、および mousedown 事象の既定作用として誘発することができます。
- Insert text文章を挿入する
This action must be triggered as the default action of a
textInput event, and may be
triggered by other commands as well. It must cause the user agent
to insert the specified text (given by the event object's data attribute in the case of the textInput event) at the caret.この作用は、 textInput 事象の既定作用として誘発しなければならず、
他の命令によって誘発しても構いません。
これにより、利用者エージェントは指定された文章 (textInput 事象の場合には事象オブジェクトの
data 属性で与えられるもの) を脱字記号の位置に挿入することにならなければなりません。
If the caret is positioned somewhere where phrasing
content is not allowed (e.g. inside an empty ol
element), then the user agent must not insert the text directly at
the caret position. In such cases the behavior is UA-dependent,
but user agents must not, in response to a request to insert text,
generate a DOM that is less conformant than the DOM prior to the
request.利用者エージェントは、脱字記号が語句付け内容の認められていない場所に位置付けられている場合
(例えば空の ol 要素の内側の場合)、
脱字記号の位置に直接文章を挿入してはなりません。このような場合、
動作は利用者エージェント依存ですが、利用者エージェントは、
文章の挿入の要求に対して、要求以前の DOM よりも適合性の低い DOM を生成してはなりません。
User agents should allow users to insert new paragraphs into
elements that contains only content other than paragraphs.利用者エージェントは、利用者に、段落以外の内容だけを含む要素に新しい段落を挿入することを認めるべきです。
For example, given the markup:例えば、次のマーク付けについて、
<section>
<dl>
<dt> Ben </dt>
<dd> Goat </dd>
</dl>
</section>
...the user agent should allow the user to insert
p elements before and after the dl
element, as children of the section element.・・・利用者エージェントは、利用者が dl 要素の前後に p 要素を section 要素の子供として挿入することを認めるべきです。
- Break block
UAs should offer a way for the user to request that the
current paragraph be broken at the caret, e.g. as the default
action of a keydown event whose
identifier is the "Enter" key and that has no modifiers set.
The exact behavior is UA-dependent, but user agents must not,
in response to a request to break a paragraph, generate a DOM that
is less conformant than the DOM prior to the request.
- Insert a line separator
UAs should offer a way for the user to request an explicit
line break at the caret position without breaking the paragraph,
e.g. as the default action of a keydown event whose identifier is the
"Enter" key and that has a shift modifier set. Line separators are
typically found within a poem verse or an address. To insert a line
break, the user agent must insert a br element.
If the caret is positioned somewhere where phrasing
content is not allowed (e.g. in an empty ol
element), then the user agent must not insert the br
element directly at the caret position. In such cases the behavior
is UA-dependent, but user agents must not, in response to a request
to insert a line separator, generate a DOM that is less conformant
than the DOM prior to the request.
- Delete削除
UAs should offer a way for the user to delete text and
elements, including non-editable descendants, e.g. as the default
action of keydown events whose
identifiers are "U+0008" or "U+007F".
Five edge cases in particular need to be considered carefully
when implementing this feature: backspacing at the start of an
element, backspacing when the caret is immediately after an
element, forward-deleting at the end of an element,
forward-deleting when the caret is immediately before an element,
and deleting a selection whose
start and end points do not share a common parent node.
In any case, the exact behavior is UA-dependent, but user
agents must not, in response to a request to delete text or an
element, generate a DOM that is less conformant than the DOM prior
to the request.
- Insert, and wrap text in,
semantic elements
UAs should offer the user the ability to mark text and
paragraphs with semantics that HTML can express.
UAs should similarly offer a way for the user to insert empty
semantic elements to subsequently fill by entering text
manually.
UAs should also offer a way to remove those semantics from
marked up text, and to remove empty semantic element that have been
inserted.
In response to a request from a user to mark text up in italics,
user agents should use the i element to represent the
semantic. The em element should be used only if the
user agent is sure that the user means to indicate stress
emphasis.
In response to a request from a user to mark text up in bold,
user agents should use the b element to represent the
semantic. The strong element should be used only if
the user agent is sure that the user means to indicate
importance.
The exact behavior is UA-dependent, but user agents must not,
in response to a request to wrap semantics around some text or to
insert or remove a semantic element, generate a DOM that is less
conformant than the DOM prior to the request.
- Select and move non-editable elements nested inside editing hosts
UAs should offer a way for the user to move images and other
non-editable parts around the content within an editing host. This
may be done using the drag and drop mechanism. User
agents must not, in response to a request to move non-editable
elements nested inside editing hosts, generate a DOM that is less
conformant than the DOM prior to the request.
- Edit form controls nested inside editing hosts
When an editable form control is edited, the
changes must be reflected in both its current value and
its default value. For input elements this means
updating the defaultValue DOM attribute as
well as the value DOM
attribute; for select elements it means updating the
option elements' defaultSelected DOM
attribute as well as the selected DOM attribute; for
textarea elements this means updating the defaultValue DOM attribute
as well as the value DOM
attribute. (Updating the default* DOM
attributes causes content attributes to be updated as well.)
User agents may perform several commands per user request; for
example if the user selects a block of text and hits
Enter, the UA might interpret that as a
request to delete the content of the selection followed
by a request to break the paragraph at that position.
6.7.2 Making entire documents editable6.7.2 文書全体の編集可能化
Documents have a designMode, which
can be either enabled or disabled.
The designMode DOM
attribute on the Document object takes two values,
"on" and "off". When it
is set, the new value must be compared in an ASCII
case-insensitive manner to these two values. If it matches
the "on" value, then designMode must be enabled,
and if it matches the "off" value, then designMode must be
disabled. Other values must be ignored.
When designMode is
enabled, the DOM attribute must return the value "on", and when it is disabled, it must return the
value "off".
The last state set must persist until the document is destroyed
or the state is changed. Initially, documents must have their designMode disabled.
Enabling designMode
causes scripts in general to be
disabled and the document to become editable.
6.8 Drag and drop
This section defines an event-based drag-and-drop mechanism.
This specification does not define exactly what a
drag-and-drop operation actually is.
On a visual medium with a pointing device, a drag operation could
be the default action of a mousedown event that is followed by a
series of mousemove events, and
the drop could be triggered by the mouse being released.
On media without a pointing device, the user would probably have
to explicitly indicate his intention to perform a drag-and-drop
operation, stating what he wishes to drag and what he wishes to
drop, respectively.
However it is implemented, drag-and-drop operations must have a
starting point (e.g. where the mouse was clicked, or the start of
the selection or element that was selected for the
drag), may have any number of intermediate steps (elements that the
mouse moves over during a drag, or elements that the user picks as
possible drop points as he cycles through possibilities), and must
either have an end point (the element above which the mouse button
was released, or the element that was finally selected), or be
canceled. The end point must be the last element selected as a
possible drop point before the drop occurs (so if the operation is
not canceled, there must be at least one element in the middle
step).
6.8.1 Introduction6.8.1 はじめに
This section is non-normative.この節は規定の一部ではありません。
It's also currently non-existent.
The drag-and-drop processing model involves several events. They
all use the DragEvent interface.drag-and-drop processing model involves several events. They all use the DragEvent 界面。
interface DragEvent : MouseEvent {
readonly attribute DataTransfer dataTransfer;
void initDragEvent(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in boolean ctrlKeyArg, in boolean altKeyArg, in boolean shiftKeyArg, in boolean metaKeyArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in DataTransfer dataTransferArg);
void initDragEventNS(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in DOMString modifiersListArg, in DataTransfer dataTransferArg);
};
The initDragEvent()
and initDragEventNS()
methods must initialize the event in a manner analogous to the
similarly-named methods in the DOM3 Events interfaces. [DOM3EVENTS]initDragEvent()
メソッドと initMessageEventNS()
メソッドは、 DOM3 事象界面の似たような名前のメソッドと同じような方法で事象を初期化しなければなりません。
[DOM3EVENTS]
The initDragEvent() and initDragEventNS()
methods handle modifier keys differently, much like the equivalent
methods on the MouseEvent interface.initDragEvent() and initDragEventNS() methods handle modifier keys differently, much like the equivalent methods on the MouseEvent 界面。
The dataTransfer
attribute of the DragEvent interface represents the
context information for the event.
interface DataTransfer {
attribute DOMString dropEffect;
attribute DOMString effectAllowed;
readonly attribute DOMStringList types;
void clearData();
void clearData(in DOMString format);
void setData(in DOMString format, in DOMString data);
DOMString getData(in DOMString format);
void setDragImage(in Element image, in long x, in long y);
void addElement(in Element element);
};
DataTransfer objects can conceptually contain
various kinds of data.
When a DataTransfer object is created, it must be
initialized as follows:
The dropEffect
attribute controls the drag-and-drop feedback that the user is given
during a drag-and-drop operation.
The attribute must ignore any attempts to set it to a value other
than none, copy, link, and move. On getting,
the attribute must return the last of those four values that it was
set to.
The effectAllowed
attribute is used in the drag-and-drop processing model to
initialize the dropEffect attribute
during the dragenter and dragover events.
The attribute must ignore any attempts to set it to a value other
than none, copy, copyLink, copyMove, link, linkMove, move, all, and uninitialized. On getting, the attribute must return
the last of those values that it was set to.
DataTransfer objects can hold pieces of data, each
associated with a unique format. Formats are generally given by MIME
types, with some values special-cased for legacy reasons. For the
purposes of this API, however, the format strings are opaque,
case-sensitive, strings, and the empty string is a
valid format string.
The clearData()
method, with no arguments, must clear the DataTransfer
object of al data (for all formats).
The clearData(format) method must clear the
DataTransfer object of any data associated with the
given format. If format is
the value "Text", then it must be treated as
"text/plain". If the format is "URL", then it must
be treated as "text/uri-list".
The setData(format, data) method
must add data to the data stored in the
DataTransfer object, labeled as being of the type format. This must replace any previous data that had
been set for that format. If format is the value
"Text", then it must be treated as "text/plain". If the format is
"URL", then it must be treated as "text/uri-list".
The getData(format) method must return the data that
is associated with the type format, if any, and
must return the empty string otherwise. If format is the value "Text",
then it must be treated as "text/plain". If
the format is "URL", then
the data associated with the "text/uri-list"
format must be parsed as appropriate for text/uri-list data, and the first URL from the list
must be returned. If there is no data with that format, or if there
is but it has no URLs, then the method must return the empty
string. [RFC2483]
The types
attribute must return a live DOMStringList that
contains the list of formats that are stored in the
DataTransfer object.
The setDragImage(element, x, y) method sets which element to use to generate the drag feedback. The
element argument can be any
Element; if it is an img element, then the
user agent should use the element's image (at its intrinsic size) to
generate the feedback, otherwise the user agent should base the
feedback on the given element (but the exact mechanism for doing so
is not specified).
The addElement(element) method is an alternative way of
specifying how the user agent is to render the drag feedback. It adds an
element to the DataTransfer object.
The difference between setDragImage() and
addElement() is
that the latter automatically generates the image based on the
current rendering of the elements added, whereas the former uses the
exact specified image.
6.8.3 Events fired during a drag-and-drop action
The following events are involved in the drag-and-drop
model. Whenever the processing model described below causes one of
these events to be fired, the event fired must use the
DragEvent interface defined above, must have the
bubbling and cancelable behaviors given in the table below, and must
have the context information set up as described after the table,
with the view attribute set to
the view with which the user interacted to trigger the drag-and-drop
event, the detail attribute
set to zero, the mouse and key attributes set according to the state
of the input devices as they would be for user interaction events,
and the relatedTarget attribute set to
null.
The dataTransfer
object's contents are empty except for dragstart events and drop events, for which the contents are
set as described in the processing model, below.
The effectAllowed
attribute must be set to "uninitialized" for
dragstart events, and to
whatever value the field had after the last drag-and-drop event was
fired for all other events (only counting events fired by the user
agent for the purposes of the drag-and-drop model described
below).
The dropEffect attribute must
be set to "none" for dragstart, drag, and dragleave events (except when stated
otherwise in the algorithms given in the sections below), to the
value corresponding to the current drag operation for
drop and dragend events, and to a value based on
the effectAllowed
attribute's value and to the drag-and-drop source, as given by the
following table, for the remaining events (dragenter and dragover):
effectAllowed |
dropEffect |
|---|
none |
none |
copy, copyLink, copyMove, all |
copy |
link, linkMove |
link |
move |
move |
uninitialized when what is being dragged is a selection from a text field |
move |
uninitialized when what is being dragged is a selection |
copy |
uninitialized when what is being dragged is an a element with an href attribute |
link |
| Any other case |
copy |
6.8.4 Drag-and-drop processing model
When the user attempts to begin a drag operation, the user agent
must first determine what is being dragged. If the drag operation
was invoked on a selection, then it is the selection that is being
dragged. Otherwise, it is the first element, going up the ancestor
chain, starting at the node that the user tried to drag, that has
the DOM attribute draggable set
to true. If there is no such element, then nothing is being dragged,
the drag-and-drop operation is never started, and the user agent
must not continue with this algorithm.
img elements and a
elements with an href
attribute have their draggable
attribute set to true by default.
If the user agent determines that something can be dragged, a
dragstart event must then be
fired.
If it is a selection that is being dragged, then this event must
be fired on the node that the user started the drag on (typically
the text node that the user originally clicked). If the user did not
specify a particular node, for example if the user just told the
user agent to begin a drag of "the selection", then the event must
be fired on the deepest node that is a common ancestor of all parts
of the selection.
We should look into how browsers do other types
(e.g. Firefox apparently also adds text/html for internal drag and
drop of a selection).
If it is not a selection that is being dragged, then the event
must be fired on the element that is being dragged.
The node on which the event is fired is the source
node. Multiple events are fired on this node during the course
of the drag-and-drop operation.
If it is a selection that is being dragged, the dataTransfer member of the event
must be created with no nodes. Otherwise, it must be created
containing just the source node. Script can use the
addElement() method
to add further elements to the list of what is being dragged.
If it is a selection that is being dragged, the dataTransfer member of the
event must have the text of the selection added to it as the data
associated with the text/plain
format. Otherwise, if it is an img element being
dragged, then the value of the element's src DOM attribute must be added,
associated with the text/uri-list
format. Otherwise, if it is an a element being dragged,
then the value of the element's href
DOM attribute must be added, associated with the text/uri-list format. Otherwise, no data is added to
the object by the user agent.
If the event is canceled, then the drag-and-drop operation must
not occur; the user agent must not continue with this algorithm.
If it is not canceled, then the drag-and-drop operation must be
initiated.
Since events with no event handlers registered are,
almost by definition, never canceled, drag-and-drop is always
available to the user if the author does not specifically prevent
it.
The drag-and-drop feedback must be
generated from the first of the following sources that is
available:
The element specified in the last call to the setDragImage() method
of the dataTransfer
object of the dragstart event,
if the method was called. In visual media, if this is used, the
x and y arguments that were
passed to that method should be used as hints for where to put the
cursor relative to the resulting image. The values are expressed as
distances in CSS pixels from the left side and from the top side of
the image respectively. [CSS21]
The elements that were added to the dataTransfer object, both
before the event was fired, and during the handling of the event
using the addElement()
method, if any such elements were indeed added.
The selection that the user is dragging.
The user agent must take a note of the data that was placed in
the dataTransfer
object. This data will be made available again when the drop event is fired.
From this point until the end of the drag-and-drop operation,
device input events (e.g. mouse and keyboard events) must be
suppressed. In addition, the user agent must track all DOM changes
made during the drag-and-drop operation, and add them to its undo history as one atomic operation once the
drag-and-drop operation has ended.
During the drag operation, the element directly indicated by the
user as the drop target is called the immediate user
selection. (Only elements can be selected by the user; other
nodes must not be made available as drop targets.)
However, the immediate user selection is not
necessarily the current target element, which is the
element currently selected for the drop part of the drag-and-drop
operation.
The immediate user selection changes as the user
selects different elements (either by pointing at them with a
pointing device, or by selecting them in some other way). The
current target element changes when the immediate
user selection changes, based on the results of event
handlers in the document, as described below.
Both the current target element and the
immediate user selection can be null, which means no
target element is selected. They can also both be elements in other
(DOM-based) documents, or other (non-Web) programs altogether. (For
example, a user could drag text to a word-processor.) The
current target element is initially null.
In addition, there is also a current drag operation,
which can take on the values "none", "copy", "link", and "move".
Initially it has the value "none". It is updated by the user agent
as described in the steps below.
User agents must, every 350ms (±200ms), perform the
following steps in sequence. (If the user agent is still performing
the previous iteration of the sequence when the next iteration
becomes due, the user agent must not execute the overdue iteration,
effectively "skipping missed frames" of the drag-and-drop
operation.)
-
First, the user agent must fire a drag event at the source
node. If this event is canceled, the user agent must set
the current drag operation to none (no drag
operation).
-
Next, if the drag event was not
canceled and the user has not ended the drag-and-drop operation,
the user agent must check the state of the drag-and-drop
operation, as follows:
-
First, if the user is indicating a different immediate
user selection than during the last iteration (or if this
is the first iteration), and if this immediate user
selection is not the same as the current target
element, then the current target element must
be updated, as follows:
-
If the new immediate user selection is null, or
is in a non-DOM document or application, then set the
current target element to the same value.
-
Otherwise, the user agent must fire a dragenter event at the
immediate user selection.
-
If the event is canceled, then the current target
element must be set to the immediate user
selection.
-
Otherwise, if the current target element is
not the body element, the user agent must fire a
dragenter event at
the body element, and the current target
element must be set to the body element,
regardless of whether that event was canceled or not. (If
the body element is null, then the current
target element would be set to null too in this case,
it wouldn't be set to the Document object.)
-
If the previous step caused the current target
element to change, and if the previous target element was
not null or a part of a non-DOM document, the user agent must fire
a dragleave event at the
previous target element.
-
If the current target element is a DOM element,
the user agent must fire a dragover event at this current
target element.
If the dragover event is
not canceled, the current drag operation must be
reset to "none".
Otherwise, the current drag operation must be
set based on the values the effectAllowed and
dropEffect
attributes of the dataTransfer object
had after the event was handled, as per the following table:
effectAllowed |
dropEffect |
Drag operation |
|---|
uninitialized, copy, copyLink, copyMove, or all |
copy |
"copy" |
uninitialized, link, copyLink, linkMove, or all |
link |
"link" |
uninitialized, move, copyMove, linkMove, or all |
move |
"move" |
| Any other case |
"none" |
Then, regardless of whether the dragover event was canceled or
not, the drag feedback (e.g. the mouse cursor) must be updated
to match the current drag operation, as
follows:
| Drag operation |
Feedback |
|---|
| "copy" |
Data will be copied if dropped here. |
| "link" |
Data will be linked if dropped here. |
| "move" |
Data will be moved if dropped here. |
| "none" |
No operation allowed, dropping here will cancel the drag-and-drop operation. |
-
Otherwise, if the current target element is not a
DOM element, the user agent must use platform-specific mechanisms
to determine what drag operation is being performed (none, copy,
link, or move). This sets the current drag operation.
-
Otherwise, if the user ended the drag-and-drop operation (e.g.
by releasing the mouse button in a mouse-driven drag-and-drop
interface), or if the drag event
was canceled, then this will be the last iteration. The user agent
must execute the following steps, then stop looping.
-
If the current drag operation is none (no drag
operation), or, if the user ended the drag-and-drop operation by
canceling it (e.g. by hitting the Escape key), or if
the current target element is null, then the drag
operation failed. If the current target element is
a DOM element, the user agent must fire a dragleave event at it; otherwise,
if it is not null, it must use platform-specific conventions for
drag cancellation.
-
Otherwise, the drag operation was as success. If the
current target element is a DOM element, the user
agent must fire a drop event at
it; otherwise, it must use platform-specific conventions for
indicating a drop.
When the target is a DOM element, the dropEffect attribute
of the event's dataTransfer object
must be given the value representing the current drag
operation (copy, link, or move), and the
object must be set up so that the getData() method will
return the data that was added during the dragstart event.
If the event is canceled, the current drag
operation must be set to the value of the dropEffect attribute
of the event's dataTransfer object as
it stood after the event was handled.
Otherwise, the event is not canceled, and the user agent must
perform the event's default action, which depends on the exact
target as follows:
- If the current target element is a text field
(e.g.
textarea, or an input element
whose type attribute is in
the Text state)
- The user agent must insert the data associated with the
text/plain format, if any, into the text field in
a manner consistent with platform-specific conventions
(e.g. inserting it at the current mouse cursor position, or
inserting it at the end of the field).
- Otherwiseそれ以外の場合
- Reset the current drag operation to
"none".
-
Finally, the user agent must fire a dragend event at the source
node, with the dropEffect attribute
of the event's dataTransfer object
being set to the value corresponding to the current drag
operation.
The current drag operation can
change during the processing of the drop event, if one was fired.
The event is not cancelable. After the event has been
handled, the user agent must act as follows:
- If the current target element is a text field
(e.g.
textarea, or an input element
whose type attribute is in
the Text state), and
a drop event was fired in the
previous step, and the current drag operation is
"move", and the source of the drag-and-drop operation is a
selection in the DOM
- The user agent should delete the range representing the
dragged selection from the DOM.
- If the current target element is a text field
(e.g.
textarea, or an input element
whose type attribute is in
the Text state), and
a drop event was fired in the
previous step, and the current drag operation is
"move", and the source of the drag-and-drop operation is a
selection in a text field
- The user agent should delete the dragged selection from the
relevant text field.
- Otherwiseそれ以外の場合
- The event has no default action.
6.8.4.1 When the drag-and-drop operation starts or ends in another
document
The model described above is independent of which
Document object the nodes involved are from; the events
must be fired as described above and the rest of the processing
model must be followed as described above, irrespective of how many
documents are involved in the operation.
6.8.4.2 When the drag-and-drop operation starts or ends in another
application
If the drag is initiated in another application, the source
node is not a DOM node, and the user agent must use
platform-specific conventions instead when the requirements above
involve the source node. User agents in this situation must act as
if the dragged data had been added to the DataTransfer
object when the drag started, even though no dragstart event was actually fired;
user agents must similarly use platform-specific conventions when
deciding on what drag feedback to use.
If a drag is started in a document but ends in another
application, then the user agent must instead replace the parts of
the processing model relating to handling the target
according to platform-specific conventions.
In any case, scripts running in the context of the document must
not be able to distinguish the case of a drag-and-drop operation
being started or ended in another application from the case of a
drag-and-drop operation being started or ended in another document
from another domain.
6.8.5 The draggable attribute6.8.5 draggable 属性
All elements may have the draggable content attribute set. The
draggable attribute is an
enumerated attribute. It has three states. The first
state is true and it has the keyword true. The second state is false and it has
the keyword false. The third state is
auto; it has no keywords but it is the missing value
default.
The draggable DOM
attribute, whose value depends on the content attribute's in the way
described below, controls whether or not the element is
draggable. Generally, only text selections are draggable, but
elements whose draggable DOM
attribute is true become draggable as well.
If an element's draggable
content attribute has the state true, the draggable DOM attribute must return
true.
Otherwise, if the element's draggable content attribute has the
state false, the draggable DOM attribute must return
false.
Otherwise, the element's draggable content attribute has the
state auto. If the element is an img element,
or, if the element is an a element with an href content attribute, the draggable DOM attribute must return
true.
Otherwise, the draggable DOM
must return false.
If the draggable DOM attribute
is set to the value false, the draggable content attribute must be
set to the literal value false. If the draggable DOM attribute is set to the
value true, the draggable
content attribute must be set to the literal value true.
6.8.6 Copy and paste
Copy-and-paste is a form of drag-and-drop: the "copy" part is
equivalent to dragging content to another application (the
"clipboard"), and the "paste" part is equivalent to dragging content
from another application.
Select-and-paste (a model used by mouse operations in the X
Window System) is equivalent to a drag-and-drop operation where the
source is the selection.
6.8.6.1 Copy to clipboard
When the user invokes a copy operation, the user agent must act
as if the user had invoked a drag on the current selection. If the
drag-and-drop operation initiates, then the user agent must act as
if the user had indicated (as the immediate user
selection) a hypothetical application representing the
clipboard. Then, the user agent must act as if the user had ended
the drag-and-drop operation without canceling it. If the
drag-and-drop operation didn't get canceled, the user agent should
then follow the relevant platform-specific conventions for copy
operations (e.g. updating the clipboard).
6.8.6.2 Cut to clipboard
When the user invokes a cut operation, the user agent must act as
if the user had invoked a copy operation (see the previous section),
followed, if the copy was completed successfully, by a selection delete operation.
6.8.6.3 Paste from clipboard
When the user invokes a clipboard paste operation, the user agent
must act as if the user had invoked a drag on a hypothetical
application representing the clipboard, setting the data associated
with the drag as the content on the clipboard (in whatever formats
are available).
Then, the user agent must act as if the user had indicated (as
the immediate user selection) the element with the
keyboard focus, and then ended the drag-and-drop operation without
canceling it.
6.8.6.4 Paste from selection
When the user invokes a selection paste operation, the user agent
must act as if the user had invoked a drag on the current selection,
then indicated (as the immediate user selection) the
element with the keyboard focus, and then ended the drag-and-drop
operation without canceling it.
6.8.7 Security risks in the drag-and-drop model
User agents must not make the data added to the
DataTransfer object during the dragstart event available to scripts
until the drop event, because
otherwise, if a user were to drag sensitive information from one
document to a second document, crossing a hostile third document in
the process, the hostile document could intercept the data.
For the same reason, user agents must consider a drop to be
successful only if the user specifically ended the drag operation
— if any scripts end the drag operation, it must be considered
unsuccessful (canceled) and the drop
event must not be fired.
User agents should take care to not start drag-and-drop
operations in response to script actions. For example, in a
mouse-and-window environment, if a script moves a window while the
user has his mouse button depressed, the UA would not consider that
to start a drag. This is important because otherwise UAs could cause
data to be dragged from sensitive sources and dropped into hostile
documents without the user's consent.
6.9 Undo history
There has got to be a better way of doing this, surely.
The user agent must associate an undo transaction
history with each HTMLDocument object.
The undo transaction history is a list of
entries. The entries are of two type: DOM changes and
undo objects.
Each DOM changes entry in the undo transaction
history consists of batches of one or more of the
following:
Undo object entries consist of objects representing
state that scripts running in the document are managing. For
example, a Web mail application could use an undo
object to keep track of the fact that a user has moved an
e-mail to a particular folder, so that the user can undo the
action and have the e-mail return to its former location.
Broadly speaking, DOM changes entries are handled by
the UA in response to user edits of form controls and editing
hosts on the page, and undo object entries are
handled by script in response to higher-level user actions (such as
interactions with server-side state, or in the implementation of a
drawing tool).
This API sucks. Seriously. It's a terrible API. Really bad. I
hate it. Here are the requirements:
Has to cope with cases where the server has undo state already
when the page is loaded, that can be stuffed into the undo buffer
onload.
Has to support undo/redo.
Has to cope with the "undo" action being "contact the server
and tell it to undo", rather than it being the opposite of the
"redo" action.
Has to cope with some undo states expiring from the undo
history (e.g. server can only remember one undelete action) but
other states not expiring (e.g. client can undo arbitrary amounts
of local edits).
To manage undo object entries in the undo
transaction history, the UndoManager
interface can be used:
interface UndoManager {
unsigned long add(in DOMObject data, in DOMString title);
[XXX] void remove(in unsigned long index);
void clearUndo();
void clearRedo();
[IndexGetter] DOMObject item(in unsigned long index);
readonly attribute unsigned long length;
readonly attribute unsigned long position;
};
The undoManager
attribute of the Window interface must return the
object implementing the UndoManager interface for that
Window object's associated
HTMLDocument object.
UndoManager objects represent their document's
undo transaction history. Only undo object
entries are visible with this API, but this does not mean that
DOM changes entries are absent from the undo
transaction history.
The length
attribute must return the number of undo object entries
in the undo transaction history.
The item(n) method must return the nth undo object entry in the undo
transaction history.
The undo transaction history has a current position. This is the position between two
entries in the undo transaction history's list where
the previous entry represents what needs to happen if the user
invokes the "undo" command (the "undo" side, lower numbers), and the
next entry represents what needs to happen if the user invokes the
"redo" command (the "redo" side, higher numbers).
The position
attribute must return the index of the undo object
entry nearest to the undo position, on the "redo"
side. If there are no undo object entries on the "redo"
side, then the attribute must return the same as the length attribute. If there are
no undo object entries on the "undo" side of the
undo position, the position attribute returns
zero.
Since the undo transaction history
contains both undo object entries and DOM
changes entries, but the position attribute only
returns indices relative to undo object entries, it is
possible for several "undo" or "redo" actions to be performed
without the value of the position attribute
changing.
The add(data,
title) method's behavior depends on the
current state. Normally, it must insert the data object
passed as an argument into the undo transaction history
immediately before the undo position, optionally
remembering the given title to use in the UI. If the
method is called during an undo
operation, however, the object must instead be added
immediately after the undo position.
If the method is called and there is neither an undo operation in progress nor a redo operation in progress then any entries
in the undo transaction history after the undo
position must be removed (as if clearRedo() had been
called).
We could fire events when someone adds
something to the undo history -- one event per undo object entry
before the position (or after, during redo addition), allowing the
script to decide if that entry should remain or not. Or
something. Would make it potentially easier to expire server-held
state when the server limitations come into play.
The remove(index) method must remove the undo
object entry with the specified index. If
the index is less than zero or greater than or equal to length then the method must
raise an INDEX_SIZE_ERR exception. DOM
changes entries are unaffected by this method.
The clearUndo()
method must remove all entries in the undo transaction
history before the undo position, be they
DOM changes entries or undo object
entries.
The clearRedo()
method must remove all entries in the undo transaction
history after the undo position, be they
DOM changes entries or undo object
entries.
Another idea is to have a way for scripts to
say "startBatchingDOMChangesForUndo()" and after that the changes to
the DOM go in as if the user had done them.
6.9.2 Undo: moving back in the undo transaction history
When the user invokes an undo operation, or when the execCommand() method is
called with the undo command, the
user agent must perform an undo operation.
If the undo position is at the start of the
undo transaction history, then the user agent must do
nothing.
If the entry immediately before the undo position is
a DOM changes entry, then the user agent must remove
that DOM changes entry, reverse the DOM changes that
were listed in that entry, and, if the changes were reversed with no
problems, add a new DOM changes entry (consisting of
the opposite of those DOM changes) to the undo transaction
history on the other side of the undo
position.
If the DOM changes cannot be undone (e.g. because the DOM state
is no longer consistent with the changes represented in the entry),
then the user agent must simply remove the DOM changes
entry, without doing anything else.
If the entry immediately before the undo position is
an undo object entry, then the user agent must first
remove that undo object entry from the undo
transaction history, and then must fire an undo event on the Document
object, using the undo object entry's associated undo
object as the event's data.
Any calls to add() while
the event is being handled will be used to populate the redo
history, and will then be used if the user invokes the "redo"
command to undo his undo.
6.9.3 Redo: moving forward in the undo transaction history
When the user invokes a redo operation, or when the execCommand() method is
called with the redo command, the
user agent must perform a redo operation.
This is mostly the opposite of an undo
operation, but the full definition is included here for
completeness.
If the undo position is at the end of the undo
transaction history, then the user agent must do nothing.
If the entry immediately after the undo position is
a DOM changes entry, then the user agent must remove
that DOM changes entry, reverse the DOM changes that
were listed in that entry, and, if the changes were reversed with no
problems, add a new DOM changes entry (consisting of
the opposite of those DOM changes) to the undo transaction
history on the other side of the undo
position.
If the DOM changes cannot be redone (e.g. because the DOM state
is no longer consistent with the changes represented in the entry),
then the user agent must simply remove the DOM changes
entry, without doing anything else.
If the entry immediately after the undo position is
an undo object entry, then the user agent must first
remove that undo object entry from the undo
transaction history, and then must fire a redo event on the Document
object, using the undo object entry's associated undo
object as the event's data.
interface UndoManagerEvent : Event {
readonly attribute DOMObject data;
void initUndoManagerEvent(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMObject dataArg);
void initUndoManagerEventNS(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMObject dataArg);
};
The initUndoManagerEvent()
and initUndoManagerEventNS()
methods must initialize the event in a manner analogous to the
similarly-named methods in the DOM3 Events interfaces. [DOM3EVENTS]
The data
attribute represents the undo object for the event.
The undo and redo events do not bubble,
cannot be canceled, and have no default action. When the user agent
fires one of these events it must use the
UndoManagerEvent interface, with the data field containing the
relevant undo object.
6.9.5 Implementation notes
How user agents present the above conceptual model to the user is
not defined. The undo interface could be a filtered view of the
undo transaction history, it could manipulate the
undo transaction history in ways not described above,
and so forth. For example, it is possible to design a UA that
appears to have separate undo
transaction histories for each form control; similarly, it is
possible to design systems where the user has access to more undo
information than is present in the official (as described above)
undo transaction history (such as providing a
tree-based approach to document state). Such UI models should be
based upon the single undo transaction history
described in this section, however, such that to a script there is
no detectable difference.
6.10 Command APIs
The execCommand(commandId, showUI, value) method on the
HTMLDocument interface allows scripts to perform
actions on the current selection
or at the current caret position. Generally, these commands would be
used to implement editor UI, for example having a "delete" button on
a toolbar.
There are three variants to this method, with one, two, and three
arguments respectively. The showUI and value parameters, even if specified, are ignored
unless otherwise stated.
When execCommand()
is invoked, the user agent must follow the following steps:
If the given commandId maps to an entry in
the list below whose "Enabled When" entry has a condition that is
currently false, do nothing; abort these steps.
Otherwise, execute the "Action" listed below for the given commandId.
A document is ready for editing host commands if it
has a selection that is entirely within an editing
host, or if it has no selection but its caret is inside an
editing host.
The queryCommandEnabled(commandId) method, when invoked, must
return true if the condition listed below under "Enabled When" for
the given commandId is true, and false
otherwise.
The queryCommandIndeterm(commandId) method, when invoked, must
return true if the condition listed below under "Indeterminate When"
for the given commandId is true, and false
otherwise.
The queryCommandState(commandId) method, when invoked, must
return the value expressed below under "State" for the given commandId.
The queryCommandSupported(commandId) method, when invoked, must
return true if the given commandId is in the
list below, and false otherwise.
The queryCommandValue(commandId) method, when invoked, must
return the value expressed below under "Value" for the given commandId.
The possible values for commandId, and their
corresponding meanings, are as follows. These values must be
compared to the argument in an ASCII case-insensitive
manner.
bold- Action: The user agent must act as if the user
had requested that the selection be wrapped in the
semantics of the
b element (or, again,
unwrapped, or have that semantic inserted or removed, as defined by
the UA).
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: True if the selection, or the caret, if
there is no selection, is, or is contained within, a
b element. False otherwise.
- Value: The string "
true"
if the expression given for the "State" above is true, the string
"false" otherwise.
createLink- Action: The user agent must act as if the user
had requested that the selection be wrapped in the
semantics of the
a element (or, again,
unwrapped, or have that semantic inserted or removed, as defined by
the UA). If the user agent creates an a element or
modifies an existing a element, then if the showUI argument is present and has the value false,
then the value of the value argument must be
used as the URL of the link. Otherwise, the user agent
should prompt the user for the URL of the link.
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
delete- Action: The user agent must act as if the user
had performed a backspace
operation.
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
formatBlock-
Action: The user agent must run the following
steps:
If the value argument wasn't
specified, abort these steps without doing anything.
If the value argument has a leading
U+003C LESS-THAN SIGN character ('<') and a trailing U+003E
GREATER-THAN SIGN character ('>'), then remove the first and last
characters from value.
-
If value is (now) an ASCII
case-insensitive match for the tag name of an element
defined by this specification that is defined to be a
prose element but not a phrasing
element, then, for every position in the selection, take
the furthest flow content ancestor element of that
position that contains only phrasing content, and,
if that element is editable, and has a content
model that allows it to contain prose content other
than phrasing content, and has a parent element
whose content model allows that parent to contain any
prose content, rename the element (as if the Element.renameNode() method had been used) to
value, using the HTML namespace.
If
there is no selection, then, where in the description above
refers to the selection, the user agent must act as if the
selection was an empty range (with just one position) at the
caret position.
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
forwardDelete- Action: The user agent must act as if the user
had performed a forward delete
operation.
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
insertImage- Action: The user agent must act as if the user
had requested that the selection be wrapped in the
semantics of the
img element (or, again,
unwrapped, or have that semantic inserted or removed, as defined by
the UA). If the user agent creates an img element or
modifies an existing img element, then if the showUI argument is present and has the value false,
then the value of the value argument must be
used as the URL of the image. Otherwise, the user
agent should prompt the user for the URL of the image.
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
insertHTML-
Action: The user agent must run the following
steps:
If the document is an XML document, then
throw an INVALID_ACCESS_ERR exception and abort
these steps.
If the value argument wasn't
specified, abort these steps without doing anything.
If there is a selection, act as if the user had requested
that the selection be
deleted.
Invoke the HTML fragment parsing algorithm
with an arbitrary orphan body element as the
context element and with the value
argument as input.
Insert the nodes returned by the previous step into the
document at the location of the caret.
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
insertLineBreak- Action: The user agent must act as if the user
had requested a line
separator.
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
insertOrderedList- Action: The user agent must act as if the user
had requested that the selection be wrapped in the
semantics of the
ol element (or unwrapped, or, if
there is no selection, have that semantic inserted or removed
— the exact behavior is UA-defined).
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
insertUnorderedList- Action: The user agent must act as if the user
had requested that the selection be wrapped in the
semantics of the
ul element (or unwrapped, or, if
there is no selection, have that semantic inserted or removed
— the exact behavior is UA-defined).
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
insertParagraph- Action: The user agent must act as if the user
had performed a break
block editing action.
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
insertText- Action: The user agent must act as if the user
had inserted text
corresponding to the value parameter.
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
italic- Action: The user agent must act as if the user
had requested that the selection be wrapped in the
semantics of the
i element (or, again,
unwrapped, or have that semantic inserted or removed, as defined by
the UA).
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: True if the selection, or the caret, if
there is no selection, is, or is contained within, a
i element. False otherwise.
- Value: The string "
true"
if the expression given for the "State" above is true, the string
"false" otherwise.
redo- Action: The user agent must move forward one step in its undo
transaction history, restoring the associated state. If the
undo position is at the end of the undo
transaction history, the user agent must do nothing. See the
undo history.
- Enabled When: The undo position
is not at the end of the undo transaction
history.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
selectAll- Action: The user agent must change the
selection so that all the content in the currently focused
editing host is selected. If no editing
host is focused, then the content of the entire document
must be selected.
- Enabled When: Always.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
subscript- Action: The user agent must act as if the user
had requested that the selection be wrapped in the
semantics of the
sub element (or, again,
unwrapped, or have that semantic inserted or removed, as defined by
the UA).
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: True if the selection, or the caret, if
there is no selection, is, or is contained within, a
sub element. False otherwise.
- Value: The string "
true"
if the expression given for the "State" above is true, the string
"false" otherwise.
superscript- Action: The user agent must act as if the user
had requested that the selection be wrapped in the
semantics of the
sup element (or unwrapped, or, if
there is no selection, have that semantic inserted or removed
— the exact behavior is UA-defined).
- Enabled When: The document is ready for
editing host commands.
- Indeterminate When: Never.
- State: True if the selection, or the caret, if
there is no selection, is, or is contained within, a
sup element. False otherwise.
- Value: The string "
true"
if the expression given for the "State" above is true, the string
"false" otherwise.
undo- Action: The user agent must move back one step in its undo
transaction history, restoring the associated state. If the
undo position is at the start of the undo
transaction history, the user agent must do nothing. See the
undo history.
- Enabled When: The undo position
is not at the start of the undo transaction
history.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
unlink- Action: The user agent must remove all
a elements that have href attributes and that are partially
or completely included in the current selection.
- Enabled When: The document has a selection
that is entirely within an editing host and that
contains (either partially or completely) at least one
a element that has an href attribute.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
unselect- Action: The user agent must change the
selection so that nothing is selected.
- Enabled When: Always.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
vendorID-customCommandID- Action: User agents may implement
vendor-specific extensions to this API. Vendor-specific extensions
to the list of commands should use the syntax
vendorID-customCommandID
so as to prevent clashes between extensions from different vendors
and future additions to this specification.
- Enabled When: UA-defined.
- Indeterminate When: UA-defined.
- State: UA-defined.
- Value: UA-defined.
- Anything elseその他のもの
- Action: User agents must do nothing.
- Enabled When: Never.
- Indeterminate When: Never.
- State: Always false.
- Value: Always the string "
false".
7 Communication7 通信
7.1 Event definitions7.1 事象定義
Messages in server-sent events, Web
sockets, cross-document messaging, and
channel messaging use the message event.鯖送信事象、Web ソケット、文書間メッセージ交換、通信路メッセージ交換のメッセージは
message 事象を使います。
The following interface is defined for this event:この事象のために、次の界面を定義します。
interface MessageEvent : Event {
readonly attribute DOMString data;
readonly attribute DOMString origin;
readonly attribute DOMString lastEventId;
readonly attribute Window source;
readonly attribute MessagePort messagePort;
void initMessageEvent(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMString dataArg, in DOMString originArg, in DOMString lastEventIdArg, in Window sourceArg, in MessagePort messagePortArg);
void initMessageEventNS(in DOMString namespaceURI, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMString dataArg, in DOMString originArg, in DOMString lastEventIdArg, in Window sourceArg, in MessagePort messagePortArg);
};
The initMessageEvent()
and initMessageEventNS()
methods must initialize the event in a manner analogous to the
similarly-named methods in the DOM3 Events interfaces. [DOM3EVENTS]initMessageEvent()
メソッドと initMessageEventNS()
メソッドは、 DOM3 事象界面の似たような名前のメソッドと同じような方法で事象を初期化しなければなりません。
[DOM3EVENTS]
The data
attribute represents the message being sent.data
属性は送信されたメッセージを表します。
The origin attribute
represents, in server-sent events and
cross-document messaging, the origin of
the document that sent the message (typically the scheme, hostname,
and port of the document, but not its path or fragment
identifier).origin
属性は、 鯖送信事象と文書間メッセージ交換において、メッセージを送信した文書の起源
(普通は当該文書の scheme と hostname と port で、 path や素片識別子は含みません。)
を表します。
The lastEventId
attribute represents, in server-sent events, the
last event ID string of the event source.lastEventId
属性は、鯖送信事象において、
事象源の最終事象識別子文字列を表します。
The source attribute
represents, in cross-document messaging, the
Window from which the message came.source 属性は、
文書間メッセージ交換において、
メッセージが送られて来た元の
Window を表します。
The messagePort
attribute represents, in cross-document messaging and
channel messaging the MessagePort being
sent, if any.messagePort
属性は、文書間メッセージ交換と通信路メッセージ交換において、
送信された MessagePort があれば、
それを表します。
Unless otherwise specified, when the user agent creates and
dispatches a message event in the
algorithms described in the following sections, the lastEventId attribute
must be the empty string, the origin attribute must be the
empty string, the source attribute must be
null, and the messagePort
attribute must be null.特に規定がない場合、利用者エージェントが以後の節で説明する算法の中で
message
事象を作成して発送する時に、 lastEventId 属性は空文字列でなければならず、
origin 属性は空文字列でなければならず、
source
属性は null でなければならず、 messagePort
属性は null でなければなりません。
Tasks in server-sent
events and Web Sockets use their own task sources, but the task
source for the tasks in
cross-document messaging and channel
messaging is the posted message task source.
7.2 Server-sent events
This section describes a mechanism for allowing servers to
dispatch DOM events into documents that expect it. The
eventsource element provides a simple interface to
this mechanism.この節は、鯖が事象を待ち受けている文書の中に DOM
事象を発送できるようにする仕組みを説明します。
eventsource
要素はこの仕組みに対する単純な界面を提供しています。
Any object that implements the EventTarget interface
must also implement the RemoteEventTarget
interface.EventTarget 界面を実装するオブジェクトは、 RemoteEventTarget
界面も実装しなければなりません。
interface RemoteEventTarget {
void addEventSource(in DOMString src);
void removeEventSource(in DOMString src);
};
When the addEventSource(src) method is invoked, the user agent
must resolve the URL
specified in src, and if that succeeds, add the resulting absolute URL
to the list of event
sources for that object. The same URL can be registered
multiple times. If the URL fails to resolve, then the user agent
must raise a SYNTAX_ERR exception.
When the removeEventSource(src) method is invoked, the user agent
must resolve the URL
specified in src, and if that succeeds, remove
the resulting absolute URL from the list of event sources for
that object. If the same URL has been registered multiple times,
removing it must remove only one instance of that URL for each
invocation of the removeEventSource() method. If the
URL fails to resolve, the user agent does nothing.
7.2.2 Connecting to an event stream7.2.2 事象ストリームへの接続
Each object implementing the EventTarget and
RemoteEventTarget interfaces has a list of event sources that
are registered for that object.
When a new absolute URL is added to this list, the
user agent should queue a task to run the following
steps with the new absolute URL:
If the entry for the new absolute URL has been
removed from the list, then abort these steps.
-
Fetch the resource identified by that
absolute URL.
As data is received, the tasks queued by the networking
task source to handle the data must consist of following
the rules given in the following sections.
When an event source is removed from the list of event sources
for an object, if that resource is still being fetched, then the
relevant connection must be closed.
Since connections established to remote servers for such
resources are expected to be long-lived, UAs should ensure that
appropriate buffering is used. In particular, while line buffering
may be safe if lines are defined to end with a single U+000A LINE
FEED character, block buffering or line buffering with different
expected line endings can cause delays in event dispatch.
Each event source in the list must have associated with it the
following:
The reconnection
time, in milliseconds. This must initially be a
user-agent-defined value, probably in the region of a few
seconds.
The last event
ID string. This must initially be the empty string.
In general, the semantics of the transport protocol specified by
the URLs for the event sources must be followed, including HTTP
caching rules.
For HTTP connections, the Accept header may
be included; if included, it must contain only formats of event
framing that are supported by the user agent (one of which must be
text/event-stream, as described below).
Other formats of event framing may also be supported in addition
to text/event-stream, but this specification does not
define how they are to be parsed or processed.
Such formats could include systems like SMS-push;
for example servers could use Accept headers
and HTTP redirects to an SMS-push mechanism as a kind of protocol
negotiation to reduce network load in GSM environments.
User agents should use the Cache-Control: no-cache
header in requests to bypass any caches for requests of event
sources.
If the event source's last event ID string is not the empty
string, then a Last-Event-ID HTTP header must
be included with the request, whose value is the value of the event
source's last event ID string.
For connections to domains other than the document's
domain, the semantics of the Access-Control HTTP header must
be followed. [ACCESSCONTROL]
HTTP 200 OK responses with a Content-Type header
specifying the type text/event-stream that are either
from the document's domain or explicitly allowed by the
Access-Control HTTP headers must be processed line by line as described below.
For the purposes of such successfully opened event streams only,
user agents should ignore HTTP cache headers, and instead assume
that the resource indicates that it does not wish to be cached.
If such a resource (with the correct MIME type) completes loading
(i.e. the entire HTTP response body is received or the connection
itself closes), the user agent should request the event source
resource again after a delay equal to the reconnection time of the
event source. This doesn't apply for the error cases that are listed
below.
HTTP 200 OK responses that have a Content-Type other
than text/event-stream (or some other supported type),
and HTTP responses whose Access-Control headers indicate that the
resource are not to be used, must be ignored.
HTTP 204 No Content, and 205 Reset Content responses must be
treated as if they were 200 OK responses with the right MIME type
but no content, and should therefore cause the user agent to refetch
the resource after a delay equal to the reconnection time of the
event source.
Other HTTP response codes in the 2xx range must be treated like HTTP 200 OK responses for the
purposes of reopening event source resources. They are, however,
likely to indicate an error has occurred somewhere and may cause the
user agent to emit a warning.
HTTP 300 Multiple Choices responses should be handled
automatically if possible (treating the responses as if they were
302 Found responses pointing to the appropriate resource), and
otherwise must be treated as HTTP 404 responses.
HTTP 301 Moved Permanently responses must cause the user agent to
reconnect using the new server specified URL instead of the
previously specified URL for all subsequent requests for this event
source. (It doesn't affect other event sources with the same URL
unless they also receive 301 responses, and it doesn't affect future
sessions, e.g. if the page is reloaded.)
HTTP 302 Found, 303 See Other, and 307 Temporary Redirect
responses must cause the user agent to connect to the new
server-specified URL, but if the user agent needs to again request
the resource at a later point, it must return to the previously
specified URL for this event source.
HTTP 304 Not Modified responses should be handled like HTTP 200
OK responses, with the content coming from the user agent cache. A
new request should then be made after a delay equal to the
reconnection time of the event source.
HTTP 305 Use Proxy, HTTP 401 Unauthorized, and 407 Proxy
Authentication Required should be treated transparently as for any
other subresource.
Any other HTTP response code not listed here or network error
(e.g. DNS errors) must be ignored.
For non-HTTP protocols, UAs should act in equivalent ways.
7.2.3 Parsing an event stream
This event stream format's MIME type is
text/event-stream.
The event stream format is (in pseudo-BNF):
<stream> ::= <bom>? <event>*
<event> ::= [ <comment> | <field> ]* <newline>
<comment> ::= <colon> <any-char>* <newline>
<field> ::= <name-char>+ [ <colon> <space>? <any-char>* ]? <newline>
# characters:
<bom> ::= a single U+FEFF BYTE ORDER MARK character
<space> ::= a single U+0020 SPACE character (' ')
<newline> ::= a U+000D CARRIAGE RETURN character
followed by a U+000A LINE FEED character
| a single U+000D CARRIAGE RETURN character
| a single U+000A LINE FEED character
| the end of the file
<colon> ::= a single U+003A COLON character (':')
<name-char> ::= a single Unicode character other than
U+003A COLON, U+000D CARRIAGE RETURN and U+000A LINE FEED
<any-char> ::= a single Unicode character other than
U+000D CARRIAGE RETURN and U+000A LINE FEED
Event streams in this format must always be encoded as
UTF-8.
Lines must be separated by either a U+000D CARRIAGE RETURN U+000A
LINE FEED (CRLF) character pair, a single U+000A LINE FEED (LF)
character, or a single U+000D CARRIAGE RETURN (CR) character.
7.2.4 Interpreting an event stream
Bytes or sequences of bytes that are not valid UTF-8 sequences
must be interpreted as the U+FFFD REPLACEMENT CHARACTER.
One leading U+FEFF BYTE ORDER MARK character must be ignored if
any are present.
The stream must then be parsed by reading everything line by
line, with a U+000D CARRIAGE RETURN U+000A LINE FEED (CRLF)
character pair, a single U+000A LINE FEED (LF) character, a single
U+000D CARRIAGE RETURN (CR) character, and the end of the file being
the four ways in which a line can end.
When a stream is parsed, a data buffer and an
event name buffer must be associated with
it. They must be initialized to the empty string
Lines must be processed, in the order they are received, as
follows:
- If the line is empty (a blank line)
Dispatch the event, as
defined below.
- If the line starts with a U+003A COLON character (':')
Ignore the line.
- If the line contains a U+003A COLON character (':') character
-
Collect the characters on the line before the first U+003A
COLON character (':'), and let field be that
string.
Collect the characters on the line after the first U+003A COLON
character (':'), and let value be that
string. If value starts with a single U+0020
SPACE character, remove it from value.
Process the field using the steps
described below, using field as the field name
and value as the field value.
- Otherwise, the string is not empty but does not contain a U+003A COLON character (':') character
-
Process the field using the steps
described below, using the whole line as the field name, and
the empty string as the field value.
Once the end of the file is reached, the user agent must dispatch the event one final time, as
defined below.
The steps to process the
field given a field name and a field value depend on the field
name, as given in the following list. Field names must be compared
literally, with no case folding performed.
- If the field name is "event"
Set the event name buffer the to field
value.
- If the field name is "data"
If the data buffer is not the empty
string, then append a single U+000A LINE FEED character to the data buffer. Append the field value to the data buffer.
- If the field name is "id"
Set the event stream's last event ID to
the field value.
- If the field name is "retry"
If the field value consists of only characters in the range
U+0030 DIGIT ZERO ('0') U+0039 DIGIT NINE ('9'), then interpret the
field value as an integer in base ten, and set the event stream's
reconnection
time to that integer. Otherwise, ignore the field.
- Otherwiseそれ以外の場合
The field is ignored.
When the user agent is required to dispatch the event, then the user agent must act as
follows:
If the data buffer is an empty string,
set the data buffer and the event
name buffer to the empty string and abort these
steps.
If the event name buffer is not the
empty string but is also not a valid NCName,
set the data buffer and the event
name buffer to the empty string and abort these
steps.
Otherwise, create an event that uses the
MessageEvent interface, with the event name message, which does not bubble, is
cancelable, and has no default action. The data attribute must be set to
the value of the data buffer, the origin attribute must be set
to the Unicode
serialization of the origin of the event
stream's URL, and the lastEventId attribute
must be set to the last event ID string of the event
source.
If the event name buffer has a value
other than the empty string, change the type of the newly created
event to equal the value of the event name
buffer.
Set the data buffer and the event name buffer to the empty string.
Queue a task to dispatch the newly created
event at the RemoteEventTarget object to which the
event stream is registered. The task source for this
task is the remote event
task source.
If an event doesn't have an "id" field, but an
earlier event did set the event source's last event ID
string, then the event's lastEventId field will
be set to the value of whatever the last seen "id" field was.
The following event stream, once followed by a blank line:
data: YHOO
data: -2
data: 10
...would cause an event message with the interface
MessageEvent to be dispatched on the
eventsource element, whose data attribute would contain
the string YHOO\n-2\n10 (where \n
represents a newline).
This could be used as follows:
<eventsource src="http://stocks.example.com/ticker.php"
onmessage="var data = event.data.split('\n'); updateStocks(data[0], data[1], data[2]);">
...where updateStocks() is a function defined as:
function updateStocks(symbol, delta, value) { ... }
...or some such.
The following stream contains four blocks. The first block has
just a comment, and will fire nothing. The second block has two
fields with names "data" and "id" respectively; an event will be
fired for this block, with the data "first event", and will then
set the last event ID to "1" so that if the connection died between
this block and the next, the server would be sent a Last-Event-ID header with the value "1". The third
block fires an event with data "second event", and also has an "id"
field, this time with no value, which resets the last event ID to
the empty string (meaning no Last-Event-ID
header will now be sent in the event of a reconnection being
attempted). Finally the last block just fires an event with the
data "third event". Note that the last block doesn't have to end
with a blank line, the end of the stream is enough to trigger the
dispatch of the last event.
: test stream
data: first event
id: 1
data: second event
id
data: third event
The following stream fires just one event:
data
data
data
data:
The first and last blocks do nothing, since they do not contain
any actual data (the data buffer remains at the
empty string, and so nothing gets dispatched). The middle block
fires an event with the data set to a single newline character.
The following stream fires two identical events:
data:test
data: test
This is because the space after the colon is ignored if
present.
7.2.5 Notes7.2.5 メモ
Legacy proxy servers are known to, in certain cases, drop HTTP
connections after a short timeout. To protect against such proxy
servers, authors can include a comment line (one starting with a ':'
character) every 15 seconds or so.
Authors wishing to relate event source connections to each other
or to specific documents previously served might find that relying
on IP addresses doesn't work, as individual clients can have
multiple IP addresses (due to having multiple proxy servers) and
individual IP addresses can have multiple clients (due to sharing a
proxy server). It is better to include a unique identifier in the
document when it is served and then pass that identifier as part of
the URL in the src
attribute of the eventsource element.
Implementations that support HTTP's per-server connection
limitation might run into trouble when opening multiple pages from a
site if each page has an eventsource to the same
domain. Authors can avoid this using the relatively complex
mechanism of using unique domain names per connection, or by
allowing the user to enable or disable the eventsource
functionality on a per-page basis.
7.3 Web sockets7.3 Web ソケット
To enable Web applications to maintain bidirectional
communications with server-side processes, this specification
introduces the WebSocket interface.
This interface does not allow for raw access to the
underlying network. For example, this interface could not be used to
implement an IRC client without proxying messages through a custom
server.
7.3.1 Introduction7.3.1 はじめに
This section is non-normative.この節は規定の一部ではありません。
An introduction to the client-side and
server-side of using the direct connection APIs.
[Constructor(in DOMString url)]
interface WebSocket {
readonly attribute DOMString URL;
// ready state
const unsigned short CONNECTING = 0;
const unsigned short OPEN = 1;
const unsigned short CLOSED = 2;
readonly attribute long readyState;
// networking
attribute EventListener onopen;
attribute EventListener onmessage;
attribute EventListener onclosed;
void postMessage(in DOMString data);
void disconnect();
};
WebSocket objects must also implement the
EventTarget interface. [DOM3EVENTS]
The WebSocket(url) constructor takes one argument,
url, which specifies the URL to
which to connect. When a WebSocket object is created,
the UA must parse this argument and
verify that the URL parses without failure and has a <scheme> component whose value is
either "ws" or "wss",
when compared in an ASCII case-insensitive manner. If
it does, it has, and it is, then the user agent must asynchronously
establish a Web Socket connection to url. Otherwise, the constructor must raise a
SYNTAX_ERR exception.
The URL
attribute must return the value that was passed to the
constructor.
The readyState
attribute represents the state of the connection. It can have the
following values:
CONNECTING (numeric value 0)CONNECTING (数値 0)- The connection has not yet been established.
OPEN (numeric value 1)OPEN (数値 1)- The Web Socket connection is established and communication is possible.
CLOSED (numeric value 2)CLOSED (数値 2)- The connection has been closed or could not be opened.
When the object is created its readyState must be set to
CONNECTING (0).
The postMessage(data) method transmits data using the
connection. If the connection is not established (readyState is not OPEN), it must raise an
INVALID_STATE_ERR exception. If the connection
is established, then the user agent must send data using the Web Socket.
The disconnect()
method must close the Web Socket connection or
connection attempt, if any. If the connection is already closed, it
must do nothing. Closing the connection causes a close event to be fired and
the readyState
attribute's value to change, as described
below.
7.3.3 WebSocket Events
The open
event is fired when the Web Socket connection is
established.
The close
event is fired when the connection is closed (whether by the author,
calling the disconnect() method, or by
the server, or by a network error).
No information regarding why the connection was
closed is passed to the application in this version of this
specification.
The message event is fired
when when data is received for a connection.
The following are the event handler DOM attributes
that must be supported by objects implementing the
WebSocket interface:
onopenMust be invoked whenever an open event is targeted at or
bubbles through the WebSocket object.
onmessageMust be invoked whenever a message event is targeted at or
bubbles through the WebSocket object.message 事象が当該 WebSocket オブジェクトを対象としているか、泡立って当該オブジェクトを通過する時に、
呼び出されなければなりません。
onclosedMust be invoked whenever an closed event is targeted at or
bubbles through the WebSocket object.
7.3.4 The Web Socket protocol
The task source for all tasks queued by algorithms in this section and its
subsections is the Web Socket task source.
7.3.4.1 Client-side requirements
This section only applies to user agents.
This specification doesn't currently define a limit
to the number of simultaneous connections that a client can
establish to a server.
7.3.4.1.1 Handshake
When the user agent is to establish a Web Socket
connection to url, it must run the
following steps, in the background (without blocking scripts or
anything like that):
Resolve the
URL url.
If the <scheme>
component of the resulting absolute URL is "ws", set secure to false;
otherwise, the <scheme>
component is "wss", set secure to true.
Let host be the value of the <host> component in the resulting
absolute URL.
If the resulting absolute URL has a <port> component, then let port be that component's value; otherwise, if secure is false, let port be 81,
otherwise let port be 815.
Let resource name be the value of the
<path> component (which might
be empty) in the resulting absolute URL.
If resource name is the empty string,
set it to a single character U+002F SOLIDUS (/).
If the resulting absolute URL has a <query> component, then append a
single 003F QUESTION MARK (?) character to resource
name, followed by the value of the <query> component.
-
If the user agent is configured to use a proxy to connect to
port port, then connect to that proxy and ask
it to open a TCP/IP connection to the host given by host and the port given by port.
For example, if the user agent uses an HTTP proxy, then if it
was to try to connect to port 80 on server example.com, it might
send the following lines to the proxy server:
CONNECT example.com HTTP/1.1
If there was a password, the connection might look like:
CONNECT example.com HTTP/1.1
Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=
Otherwise, if the user agent is not configured to use a proxy,
then open a TCP/IP connection to the host given by host and the port given by port.
If the connection could not be opened, then fail the
Web Socket connection and abort these steps.
If secure is true, perform a TLS
handshake over the connection. If this fails (e.g. the server's
certificate could not be verified), then fail the Web Socket
connection and abort these steps. Otherwise, all further
communication on this channel must run through the encrypted
tunnel. [RFC2246]
-
Send the following bytes to the remote side (the server):
47 45 54 20
Send the resource name value, encoded as
US-ASCII.
Send the following bytes:
20 48 54 54 50 2f 31 2e 31 0d 0a 55 70 67 72 61
64 65 3a 20 57 65 62 53 6f 63 6b 65 74 0d 0a 43
6f 6e 6e 65 63 74 69 6f 6e 3a 20 55 70 67 72 61
64 65 0d 0a
The string "GET ", the path,
" HTTP/1.1", CRLF, the string "Upgrade: WebSocket",
CRLF, and the string "Connection: Upgrade", CRLF.
-
Send the following bytes:
48 6f 73 74 3a 20
Send the host value, encoded as US-ASCII,
if it represents a host name (and not an IP address).
Send the following bytes:
0d 0a
The string "Host: ", the host, and CRLF.
-
Send the following bytes:
4f 72 69 67 69 6e 3a 20
Send the ASCII
serialization of the origin of the script that
invoked the WebSocket()
constructor.
Send the following bytes:
0d 0a
The string "Origin: ", the origin, and CRLF.
-
If the client has any authentication information or cookies
that would be relevant to a resource with a URL that
has a scheme of http if secure is false and https if
secure is true and is otherwise identical to
url, then HTTP headers that would be
appropriate for that information should be sent at this point. [RFC2616] [RFC2109] [RFC2965]
Each header must be on a line of its own (each ending with a CR
LF sequence). For the purposes of this step, each header must not
be split into multiple lines (despite HTTP otherwise allowing this
with continuation lines).
For example, if the server had a username and password that
applied to that URL, it could send:
Authorization: Basic d2FsbGU6ZXZl
-
Send the following bytes:
0d 0a
Just a CRLF (a blank line).
-
Read the first 85 bytes from the server. If the connection
closes before 85 bytes are received, or if the first 85 bytes
aren't exactly equal to the following bytes, then fail the
Web Socket connection and abort these steps.
48 54 54 50 2f 31 2e 31 20 31 30 31 20 57 65 62
20 53 6f 63 6b 65 74 20 50 72 6f 74 6f 63 6f 6c
20 48 61 6e 64 73 68 61 6b 65 0d 0a 55 70 67 72
61 64 65 3a 20 57 65 62 53 6f 63 6b 65 74 0d 0a
43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 55 70 67 72
61 64 65 0d 0a
The string
"HTTP/1.1 101 Web Socket Protocol Handshake", CRLF, the
string "Upgrade: WebSocket", CRLF, the string
"Connection: Upgrade", CRLF.
What if the response is a 401 asking for
credentials?
Let headers be a list of name-value
pairs, initially empty.
-
Read a byte from the server.
If the connection closes before this byte is received, then
fail the Web Socket connection and abort these
steps.
Otherwise, handle the byte as described in the appropriate
entry below:
- If the byte is 0x0d (ASCII CR)
- If the name byte array is empty, then
jump to the headers
processing step. Otherwise, fail the Web Socket
connection and abort these steps.
- If the byte is 0x0a (ASCII LF)
- Fail the Web Socket connection and abort these
steps.
- If the byte is 0x3a (ASCII ":")
- Move on to the next step.
- If the byte is in the range 0x41 .. 0x5a (ASCII "A" .. "Z")
- Append a byte whose value is the byte's value plus 0x20 to
the name byte array and redo this step for
the next byte.
- Otherwiseそれ以外の場合
- Append the byte to the name byte
array and redo this step for the next byte.
This reads a header name, terminated by a colon,
converting upper-case ASCII letters to lowercase, and aborting if
a stray CR or LF is found.
-
Read a byte from the server.
If the connection closes before this byte is received, then
fail the Web Socket connection and abort these
steps.
Otherwise, handle the byte as described in the appropriate
entry below:
- If the byte is 0x20 (ASCII space)
- Ignore the byte and move on to the next step.
- Otherwiseそれ以外の場合
- Treat the byte as described by the list in the next step,
then move on to that next step for real.
This skips past a space character after the colon,
if necessary.
-
Read a byte from the server.
If the connection closes before this byte is received, then
fail the Web Socket connection and abort these
steps.
Otherwise, handle the byte as described in the appropriate
entry below:
- If the byte is 0x0d (ASCII CR)
- Move on to the next step.
- If the byte is 0x0a (ASCII LF)
- Fail the Web Socket connection and abort these
steps.
- Otherwiseそれ以外の場合
- Append the byte to the name byte array
and redo this step for the next byte.
This reads a header value, terminated by a
CRLF.
-
Read a byte from the server.
If the connection closes before this byte is received, or if
the byte is not a 0x0a byte (ASCII LF), then fail the Web
Socket connection and abort these steps.
This skips past the LF byte of the CRLF after the
header.
-
Append an entry to the headers list that
has the name given by the string obtained by interpreting the name byte array as a UTF-8 byte stream and the
value given by the string obtained by interpreting the value byte array as a UTF-8 byte stream.
-
Return to the header step
above.
-
Handle each entry in the headers list as
follows:
- If the entry's name is "
websocket-origin"
- If the value is not exactly equal to the ASCII serialization of the
origin of the script that invoked the
WebSocket() constructor, then
fail the Web Socket connection and abort these
steps.
- If the entry's name is "
websocket-location"
- If the value is not exactly equal to the absolute
URL that resulted from the first
step of ths algorithm, then fail the Web Socket
connection and abort these steps.
- If the entry's name is "
set-cookie" or
"set-cookie2" or another cookie-related
header name
- Handle the cookie as defined by the appropriate spec, except
pretend that the resource's URL actually has a
scheme of
http if secure is false and https if
secure is true and is otherwise identical to
url. [RFC2109] [RFC2965]
- Any other name
- Ignore it.
-
Change the readyState attribute's value
to OPEN (1).
-
Queue a task to fire a simple event
named open at the
WebSocket object.
-
The Web Socket connection is established. Now the
user agent must send and receive to and from the connection as
described in the next section.
To fail the Web Socket connection, the user agent must
close the Web Socket connection, and may report the
problem to the user (which would be especially useful for
developers). However, user agents must not convey the failure
information to the script in a way distinguishable from the Web
Socket being closed normally.
7.3.4.1.2 Data framing
Once a Web Socket connection is established, the
user agent must run through the following state machine for the
bytes sent by the server.
-
Try to read a byte from the server. Let frame
type be that byte.
If no byte could be read because the Web Socket
connection is closed, then abort.
-
Handle the frame type byte as follows:
- If the high-order bit of the frame type
byte is set (i.e. if frame type anded with 0x80 returns 0x80)
-
Run these steps. If at any point during these steps a read is
attempted but fails because the Web Socket connection is
closed, then abort.
Let length be zero.
Length: Read a byte, let b be that byte.
Let bv be
integer corresponding to the low 7 bits of b
(the value you would get by anding b
with 0x7f).
Multiply length by 128, add bv to that result, and store
the final result in length.
If the high-order bit of b is set
(i.e. if b anded with 0x80
returns 0x80), then return to the step above labeled length.
Read length bytes.
Discard the read bytes.
- If the high-order bit of the frame type
byte is not set (i.e. if frame type
anded with 0x80 returns 0x00)
-
Run these steps. If at any point during these steps a read is
attempted but fails because the Web Socket connection is
closed, then abort.
Let raw data be an empty byte array.
Data: Read a byte, let b be that byte.
If b is not 0xff, then append b to raw data and return to
the previous step (labeled data).
Interpret raw data as a UTF-8
string, and store that string in data.
If frame type is 0x00, create an
event that uses the MessageEvent interface, with
the event name message,
which does not bubble, is cancelable, has no default action,
and whose data
attribute is set to data, and queue a
task to dispatch it at the WebSocket
object. Otherwise, discard the data.
Return to the first step to read the next byte.
If the user agent is faced with content that is too large to be
handled appropriately, then it must fail the Web Socket
connection.
Once a Web Socket connection is established, the
user agent must use the following steps to send data using the Web Socket:
Send a 0x00 byte to the server.
Encode data using UTF-8 and send the
resulting byte stream to the server.
Send a 0xff byte to the server.
People often request the ability to send binary
blobs over this API; also, once the other postMessage() methods
support it, we should look into allowing name/value pairs, arrays,
and numbers using postMessage() instead of just strings and binary
data.
7.3.4.2 Server-side requirements
This section only applies to servers.
7.3.4.2.1 Minimal handshake
This section describes the minimal requirements for
a server-side implementation of Web Sockets.
Listen on a port for TCP/IP. Upon receiving a connection request,
open a connection and send the following bytes back to the
client:
48 54 54 50 2f 31 2e 31 20 31 30 31 20 57 65 62
20 53 6f 63 6b 65 74 20 50 72 6f 74 6f 63 6f 6c
20 48 61 6e 64 73 68 61 6b 65 0d 0a 55 70 67 72
61 64 65 3a 20 57 65 62 53 6f 63 6b 65 74 0d 0a
43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 55 70 67 72
61 64 65 0d 0a
Send the string "WebSocket-Origin" followed
by a U+003A COLON (":") followed by the ASCII serialization of the origin
from which the server is willing to accept connections, followed by
a CRLF pair (0x0d 0x0a).
For instance:
WebSocket-Origin: http://example.com
Send the string "WebSocket-Location"
followed by a U+003A COLON (":") followed by the URL of
the Web Socket script, followed by a CRLF pair (0x0d 0x0a).
For instance:
WebSocket-Location: ws://example.com:80/demo
Send another CRLF pair (0x0d 0x0a).
Read (and discard) data from the client until four bytes 0x0d
0x0a 0x0d 0x0a are read.
If the connection isn't dropped at this point, go to the data framing section.
7.3.4.2.2 Handshake details
The previous section ignores the data that is transmitted by the
client during the handshake.
The data sent by the client consists of a number of fields
separated by CR LF pairs (bytes 0x0d 0x0a).
The first field consists of three tokens separated by space
characters (byte 0x20). The middle token is the path being
opened. If the server supports multiple paths, then the server
should echo the value of this field in the initial handshake, as
part of the URL given on the WebSocket-Location line (after the appropriate
scheme and host).
The remaining fields consist of name-value pairs, with the name
part separated from the value part by a colon and a space (bytes
0x3a 0x20). Of these, several are interesting:
- Host (bytes 48 6f 73 74)
-
The value gives the hostname that the client intended to use
when opening the Web Socket. It would be of interest in particular
to virtual hosting environments, where one server might serve
multiple hosts, and might therefore want to return different
data.
The right host has to be output as part of the URL
given on the WebSocket-Location line of the
handshake described above, to verify that the server knows that it
is really representing that host.
- Origin (bytes 4f 72 69 67 69 6e)
-
The value gives the scheme, hostname, and port (if it's not the
default port for the given scheme) of the page that asked the
client to open the Web Socket. It would be interesting if the
server's operator had deals with operators of other sites, since
the server could then decide how to respond (or indeed,
whether to respond) based on which site was requesting a
connection.
If the server supports connections from more than one origin,
then the server should echo the value of this field in the initial
handshake, on the WebSocket-Origin line.
- Other fields
-
Other fields can be used, such as "Cookie" or "Authorization", for
authentication purposes.
7.3.4.2.3 Data framing
This section only describes how to handle content
that this specification allows user agents to send (text). It
doesn't handle any arbitrary content in the same way that the
requirements on user agents defined earlier handle any content
including possible future extensions to the protocols.
The server should run through the following steps to process the
bytes sent by the client:
Read a byte from the client. Assuming everything is going
according to plan, it will be a 0x00 byte. Behaviour for the server
is undefined if the byte is not 0x00.
Let raw data be an empty byte
array.
Data: Read a byte, let b be that byte.
If b is not 0xff, then append b to raw data and return to the
previous step (labeled data).
Interpret raw data as a UTF-8 string,
and apply whatever server-specific processing should occur for the
resulting string.
Return to the first step to read the next byte.
The server should run through the followin steps to send strings
to the client:
Send a 0x00 byte to the client to indicate the start of a
string.
Encode data using UTF-8 and send the
resulting byte stream to the client.
Send a 0xff byte to the client to indicate the end of the
message.
7.3.4.3 Closing the connection
To close the Web Socket connection, either the user
agent or the server closes the TCP/IP connection. There is no
closing handshake. Whether the user agent or the server closes the
connection, it is said that the Web Socket connection is
closed.
Servers may close the Web Socket connection whenever
desired.
User agents should not close the Web Socket
connection arbitrarily.
When the Web Socket connection is
closed, the readyState attribute's value
must be changed to CLOSED
(2), and the user agent must queue a task to fire
a simple event named close at the
WebSocket object.
7.4 Cross-document messaging
Web browsers, for security and privacy reasons, prevent documents
in different domains from affecting each other; that is, cross-site
scripting is disallowed.
While this is an important security feature, it prevents pages
from different domains from communicating even when those pages are
not hostile. This section introduces a messaging system that allows
documents to communicate with each other regardless of their source
domain, in a way designed to not enable cross-site scripting
attacks.
7.4.1 Introduction7.4.1 はじめに
This section is non-normative.この節は規定の一部ではありません。
For example, if document A contains an iframe
element that contains document B, and script in document A calls
postMessage() on the
Window object of document B, then a message event will
be fired on that object, marked as originating from the
Window of document A. The script in document A might
look like:
var o = document.getElementsByTagName('iframe')[0];
o.contentWindow.postMessage('Hello world', 'http://b.example.org/');
To register an event handler for incoming events, the script
would use addEventListener() (or similar
mechanisms). For example, the script in document B might look
like:
window.addEventListener('message', receiver, false);
function receiver(e) {
if (e.origin == 'http://example.com') {
if (e.data == 'Hello world') {
e.source.postMessage('Hello', e.origin);
} else {
alert(e.data);
}
}
}
This script first checks the domain is the expected domain, and
then looks at the message, which it either displays to the user, or
responds to by sending a message back to the document which sent
the message in the first place.
7.4.2 Security7.4.2 保安性
7.4.2.1 Authors
Use of this API requires extra care to protect
users from hostile entities abusing a site for their own
purposes.
Authors should check the origin attribute to ensure
that messages are only accepted from domains that they expect to
receive messages from. Otherwise, bugs in the author's message
handling code could be exploited by hostile sites.
Authors should not use the wildcard keyword ("*") in the targetOrigin argument in messages that contain any
confidential information, as otherwise there is no way to guarantee
that the message is only delivered to the recipient to which it was
intended.
7.4.2.2 User agents
The integrity of this API is based on the inability for scripts
of one origin to post arbitrary events (using dispatchEvent() or otherwise) to objects in other
origins (those that are not the same).
Implementors are urged to take extra care in the
implementation of this feature. It allows authors to transmit
information from one domain to another domain, which is normally
disallowed for security reasons. It also requires that UAs be
careful to allow access to certain properties but not others.
7.4.3 Posting text
When a script invokes the postMessage(message, targetOrigin) method (with only two
arguments) on a Window object, the user agent must
follow these steps:
-
If the value of the targetOrigin argument
is not a single U+002A ASTERISK character ("*"), and either parsing it as a URL fails,
or resolving it results in a
URL with a <host-specific> component
that is neither empty nor a single U+002F SOLIDUS character (/),
then throw a SYNTAX_ERR exception and abort the
overall set of steps.
-
Return from the postMessage() method, but
asynchronously continue running these steps.
-
If the targetOrigin argument has a value
other than a single literal U+002A ASTERISK character ("*"), and
the active document of the browsing
context of the Window object on which the
method was invoked does not have the same origin as
targetOrigin, then abort these steps
silently.
-
Create an event that uses the MessageEvent
interface, with the event name message, which does not bubble, is
cancelable, and has no default action. The data attribute must be set to
the value passed as the message argument to
the postMessage()
method, the origin
attribute must be set to the Unicode serialization of the origin
of the script that invoked the method, and the source attribute must be
set to the Window object of the default
view of the browsing context for which the
Document object with which the script is associated
is the active document.
-
Queue a task to dispatch the event created in the
previous step at the Window object on which the
method was invoked. The task source for this task is the posted message task
source.
7.4.4 Posting message ports
When a script invokes the postMessage(message, messagePort, targetOrigin) method (with three
arguments) on a Window object, the user agent must
follow these steps:
-
If the value of the targetOrigin argument
is not a single U+002A ASTERISK character ("*"), and either parsing it as a URL fails,
or resolving it results in a
URL with a <host-specific> component
that is neither empty nor a single U+002F SOLIDUS character (/),
then throw a SYNTAX_ERR exception and abort the
overall set of steps.
-
If the messagePort argument is null, then
act as if the method had just been called with two arguments,
message and targetOrigin.
-
Try to obtain a new port by cloning the messagePort argument with the Window
object on which the method was invoked as the owner of the
clone. If this returns an exception, then throw that exception and
abort these steps.
-
Return from the postMessage() method, but
asynchronously continue running these steps.
-
If the targetOrigin argument has a value
other than a single literal U+002A ASTERISK character ("*"), and
the active document of the browsing
context of the Window object on which the
method was invoked does not have the same origin as
targetOrigin, then abort these steps
silently.
-
Create an event that uses the MessageEvent
interface, with the event name message, which does not bubble, is
cancelable, and has no default action. The data attribute must be set to
the value passed as the message argument to
the postMessage()
method, the origin
attribute must be set to the Unicode serialization of the origin
of the script that invoked the method, and the source attribute must be
set to the Window object of the default
view of the browsing context for which the
Document object with which the script is associated
is the active document.
-
Let the messagePort attribute
of the event be the new port.
-
Queue a task to dispatch the event created in the
previous step at the Window object on which the
method was invoked. The task source for this task is the posted message task
source.
These steps, with the exception of the second and
third steps and the penultimate step, are identical to those in the
previous section.
7.4.5 Posting structured data
People often request the ability to send
name/value pairs, arrays, and numbers using postMessage() instead of
just strings.
7.5 Channel messaging
7.5.1 Introduction7.5.1 はじめに
This section is non-normative.この節は規定の一部ではありません。
An introduction to the channel and port
APIs.
7.5.2 Message channels
[Constructor]
interface MessageChannel {
readonly attribute MessagePort port1;
readonly attribute MessagePort port2;
};
When the MessageChannel()
constructor is called, it must run the following algorithm:
Create a new MessagePort object
owned by the script execution context, and let port1 be that object.
Create a new MessagePort object
owned by the script execution context, and let port2 be that object.
Entangle the port1 and port2 objects.
Instantiate a new MessageChannel object, and
let channel be that object.
Let the port1
attribute of the channel object be port1.
Let the port2
attribute of the channel object be port2.
Return channel.channel を返します。
The port1 and
port2 attributes
must return the values they were assigned when the
MessageChannel object was created.
7.5.3 Message ports
Each channel has two message ports. Data sent through one port is
received by the other port, and vice versa.
interface MessagePort {
readonly attribute boolean active;
void postMessage(in DOMString message);
void postMessage(in DOMString message, in MessagePort messagePort);
void start();
void close();
// event handler attributes
attribute EventListener onmessage;
attribute EventListener onclose;
};
Objects implementing the MessagePort interface must
also implement the EventTarget interface.
Each MessagePort object can be entangled with
another (a symmetric relationship). Each MessagePort
object also has a port message queue, initial empty. A
port message queue can be open or closed, and is
initially closed.
When the user agent is to create a new
MessagePort object owned by a script
execution context object owner, it must
instantiate a new MessagePort object, and let its owner
be owner.
When the user agent is to entangle two
MessagePort objects, it must run the following
steps:
-
If one of the ports is already entangled, then unentangle it
and the port that it was entangled with.
If those two previously entangled ports were the
two ports of a MessageChannel object, then that
MessageChannel object no longer represents an actual
channel: the two ports in that object are no longer entangled.
Associate the two ports to be entangled, so that they form
the two parts of a new channel. (There is no
MessageChannel object that represents this
channel.)
When the user agent is to clone a port original port, with the clone being owned by owner, it must run the following steps, which return
either a new MessagePort object or an exception for the
caller to raise:
If the original port is not entangled
without another port, then return an INVALID_STATE_ERR
exception and abort all these steps.
Let the remote port be the port with
which the original port is entangled.
Create a new MessagePort object
owned by owner, and let new
port be that object.
Move all the events in the port message queue
of original port to the port message
queue of new port, if any, leaving the
new port's port message queue in
its initial closed state.
Entangle the remote port
and new port objects. The original port object will be unentangled by this
process.
Return new port. It is the
clone.
The active
attribute must return true if the port is entangled, and false
otherwise.
The postMessage()
method, when called on a port source port, must
cause the user agent to run the following steps:
Let message be the method's first
argument.
Let data port be the method's second
argument, if any.
If the source port is not entangled with
another port, then return and abort these steps.
Let target port be the port with which
source port is entangled.
Create an event that uses the MessageEvent
interface, with the name message, which does not bubble, is
cancelable, and has no default action.
Let the data
attribute of the event have the value of message, the method's first argument.
If the method was called with a second argument data port and that argument isn't null, then run the
following substeps:
If the data port is the source port or the target
port, then throw an INVALID_ACCESS_ERR
exception and abort all these steps.
Try to obtain a new data port by cloning the data
port with the owner of the target port
as the owner of the clone. If this returns an exception, then
throw that exception and abort these steps.
Let the messagePort attribute
of the event be the new data port.
Return from the method, but continue with these
steps.
Add the event to the port message queue of target port.
People often request the ability to send
name/value pairs, arrays, and numbers using postMessage() instead of
just strings.
The start()
method must open its port's port message queue, if it
is not already open.
When a port's port message queue is open, contains
an event, and its owner is available, the user agent must queue a
task in the event loop to dispatch the first
event in the queue on the MessagePort object, and
remove the event from the queue. The task source for
this task is the posted
message task source.
A MessagePort's owner is available if the MessagePort is owned
by an object other than a Window object, or if it is
owned by a Window object and the Document
that was the active document in that browsing
context when the MessagePort was created is
fully active. If that Document is
discarded before the port's owner becomes available, then the events
are lost.
The close()
method, when called on a port local port that is
entangled with another port, must cause the user agents to run the
following steps:
Unentangle the two ports.2つのポートをほどきます。
Queue a task to fire a simple
event called close at the
port on which the method was called.
Queue a task to fire a simple
event called close at the
other port.
The task source for the two tasks above is the posted message
task source.
If the method is called on a port that is not entangled, then the
method must do nothing.
The following are the event handler DOM attributes
that must be supported by objects implementing the
MessagePort interface:
onmessage-
Must be invoked whenever a message event is targeted
at or bubbles through the MessagePort object.message 事象が当該 MessagePort オブジェクトを対象としているか、泡立って当該オブジェクトを通過する時に、
呼び出されなければなりません。
The first time a MessagePort object's onmessage attribute
is set, the port's port message queue must be opened,
as if the start()
method had been called.
oncloseMust be invoked whenever an close event is targeted at or bubbles
through the MessagePort object.
7.5.3.1 Ports and browsing contexts
When a Document is discarded, if there are any
MessagePort objects that:
...then the user agent must run the following steps for each such
port:
Let surviving port be the port with
which the MessagePort object in question is
entangled.
Unentangle the two ports.2つのポートをほどきます。
Queue a task to fire a simple
event called close at
surviving port. The task source
for this task is the posted
message task source.
7.5.3.2 Ports and garbage collection
User agents must act as if MessagePort objects have
a strong reference to their entangled MessagePort
object.
Thus, a message port can be received, given an event listener,
and then forgotten, and so long as that event listener could
receive a message, the channel will be maintained.
Of course, if this was to occur on both sides of the channel,
then both ports would be garbage collected, since they would not be
reachable from live code, despite having a strong reference to each
other.
Furthermore, a MessagePort object must not be
garbage collected while there exists a message in a task
queue that is to be dispatched on that
MessagePort object, or while the
MessagePort object's port message queue is
open and there exists a message
event in that queue.
8 The HTML syntax8 HTML 構文
8.1 Writing HTML documents8.1 HTML 文書を書く
This section only applies to documents, authoring tools, and
markup generators. In particular, it does not apply to conformance
checkers; conformance checkers must use the requirements given in
the next section ("parsing HTML documents").この節は文書、著述ツール、マーク付け生成器にのみ適用されます。
特に、適合性検査器には適用されません。
適合性検査器は次の節 (「HTML 文書の構文解析」) で与えられる要件を用いなければなりません。
Documents must consist of the following parts, in the given
order:文書は、次に示す部分により、次の順序で構成されなければなりません。
Optionally, a single U+FEFF BYTE ORDER MARK (BOM) character.任意選択で、1つの U+FEFF BYTE ORDER MARK (BOM) 文字。
Any number of comments and
space characters.任意の個数の注釈と間隔文字。
A DOCTYPE.
DOCTYPE。
Any number of comments and
space characters.任意の個数の注釈と間隔文字。
The root element, in the form of an html element.根要素を、 html 要素として。
Any number of comments and
space characters.任意の個数の注釈と間隔文字。
The various types of content mentioned above are described in the
next few sections.前述の各種の内容は、次の数個の節で説明します。
In addition, there are some restrictions on how character
encoding declarations are to be serialized, as discussed in
the section on that topic.加えて、文字符号化宣言をどう直列化するかについても、
それに関する節で説明した通り、いくつかの制限があります。
Space characters before the root html element, and
space characters at the start of the html element and
before the head element, will be dropped when the
document is parsed; space characters after the root
html element will be parsed as if they were at the end
of the body element. Thus, space characters around the
root element do not round-trip.根 html 要素の前の間隔文字や、
html 要素のはじめで head 要素の前の間隔文字は、
文書が構文解析される時に除去されます。根 html 要素の後の間隔文字は、
body 要素の終わりにあったものとして構文解析されます。
従って、根要素の近辺の間隔文字は往復しません。
It is suggested that newlines be inserted after the DOCTYPE,
after any comments that are before the root element, after the
html element's start tag (if it is not omitted), and after any comments
that are inside the html element but before the
head element.DOCTYPE の後、
根要素の前の注釈がある場合はその後、
html 要素の開始タグの後
(省略しない場合)、
html 要素中で
head 要素の前に注釈がある場合にはその後には、
改行を挿入することをおすすめします。
Many strings in the HTML syntax (e.g. the names of elements and
their attributes) are case-insensitive, but only for characters in
the ranges U+0041 .. U+005A (LATIN CAPITAL LETTER A to LATIN CAPITAL
LETTER Z) and U+0061 .. U+007A (LATIN SMALL LETTER A to LATIN SMALL
LETTER Z). For convenience, in this section this is just referred to
as "case-insensitive".HTML 構文中の多くの文字列 (例えば要素や属性の名前) は大文字と小文字を区別しませんが、
区別しないのは範囲
U+0041 ～ U+005A (LATIN CAPITAL LETTER A ～ LATIN CAPITAL LETTER Z) と
範囲 U+0061 ～ U+007A (LATIN SMALL LETTER A ～ LATIN SMALL LETTER Z)
の文字についてのみです。便宜上、この節ではこれを単に「大文字・小文字を区別しない」と呼びます。
8.1.1 The DOCTYPE8.1.1 DOCTYPE
A DOCTYPE is a mostly useless,
but required, header.DOCTYPE はほとんど無意味ですが、
必須の頭部です。
DOCTYPEs are required for legacy reasons. When
omitted, browsers tend to use a different rendering mode that is
incompatible with some specifications. Including the DOCTYPE in a
document ensures that the browser makes a best-effort attempt at
following the relevant specifications.DOCTYPE は遺物的な理由で必須です。
省略すると、ブラウザはいくつかの仕様書と非互換な異なるレンダリング・モードを使おうとします。
DOCTYPE を文書に含めることによってブラウザに関係する仕様書に従うよう最善の努力を試みさせるようにします。
A DOCTYPE must consist of the following characters, in this
order:DOCTYPE は、次の文字により次の順序で構成されなければなりません。
A U+003C LESS-THAN SIGN (<) character.U+003C LESS-THAN SIGN (<) 文字。
A U+0021 EXCLAMATION MARK (!) character.U+0021 EXCLAMATION MARK (!) 文字。
A string that is an ASCII case-insensitive match for the string "DOCTYPE".
One or more space characters.1つ以上の間隔文字。
A string that is an ASCII case-insensitive match for the string "HTML".
Optionally, a DOCTYPE legacy string (defined below).任意選択で、 DOCTYPE 遺物文字列 (後で定義します)。
Zero or more space characters.零個以上の間隔文字。
A U+003E GREATER-THAN SIGN (>) character.U+003E GREATER-THAN SIGN (>) 文字。
In other words, <!DOCTYPE HTML>,
case-insensitively.すなわち、大文字または小文字の <!DOCTYPE HTML>。
For the purposes of XSLT generators that cannot output HTML
markup without a DOCTYPE, a DOCTYPE legacy string may be
inserted into the DOCTYPE (in the position defined above). This
string must consist of:DOCTYPE なしの HTML マーク付けを出力できない XSLT 生成器のため、
DOCTYPE 遺物文字列を
DOCTYPE (の前述の位置) に挿入して構いません。
この文字列は次のものから構成されなければなりません。
One or more space characters.1つ以上の間隔文字。
A string that is an ASCII case-insensitive match for the string "PUBLIC".
One or more space characters.1つ以上の間隔文字。
A U+0022 QUOTATION MARK or U+0027 APOSTROPHE character (the quote mark).
The literal string "XSLT-compat".生の文字列「XSLT-compat」。
A matching U+0022 QUOTATION MARK or U+0027 APOSTROPHE character (i.e. the same character as in the earlier step marked quote mark).
In other words, <!DOCTYPE HTML PUBLIC
"XSLT-compat"> or <!DOCTYPE HTML PUBLIC
'XSLT-compat'>, case-insensitively except for the bit in
quotes.すなわち、引用符内以外は大文字か小文字の <!DOCTYPE HTML PUBLIC
"XSLT-compat"> または <!DOCTYPE HTML PUBLIC
'XSLT-compat'>。
The DOCTYPE legacy string should not be used unless
the document is generated from XSLT.DOCTYPE 遺物文字列は XSLT
で生成された文書を除き使用するべきではありません。
8.1.2 Elements8.1.2 要素
There are five different kinds of elements: void elements, CDATA
elements, RCDATA elements, foreign elements, and normal
elements.要素には、
空隙要素、 CDATA 要素、 RCDATA 要素、外来要素、通常要素の5つの異なる種類があります。
- Void elements空隙要素
base, command,
eventsource, link, meta,
hr, br, img,
embed, param, area,
col, input, source- CDATA elementsCDATA 要素
style, script- RCDATA elementsRCDATA 要素
title, textarea- Foreign elements外来要素
- Elements from the MathML namespace
MathML 名前空間の要素
- Normal elements通常要素
- All other allowed HTML elements are normal
elements.他の全ての認められているHTML 要素は通常要素です。
Tags are used to delimit the start
and end of elements in the markup. CDATA, RCDATA, and normal
elements have a start tag to
indicate where they begin, and an end
tag to indicate where they end. The start and end tags of
certain normal elements can be omitted, as described
later. Those that cannot be omitted must not be omitted. Void
elements only have a start tag; end tags must not be
specified for void elements. Foreign elements must either have a
start tag and an end tag, or a start tag that is marked as
self-closing, in which case they must not have an end tag.
The contents of the element must be placed between just after the
start tag (which might be implied,
in certain cases) and just before the end tag (which again,
might be implied in certain
cases). The exact allowed contents of each individual element
depends on the content model of that element, as described earlier
in this specification. Elements must not contain content that their
content model disallows. In addition to the restrictions placed on
the contents by those content models, however, the five types of
elements have additional syntactic requirements.要素の内容は開始タグ (これは場合によっては暗示的なものかもしれません。)
の直後と終了タグ (これも場合によっては暗示的なものかもしれません。)
の直前の間に配置しなければなりません。
各要素それぞれで認められる内容は正確には、この仕様書の先の方で説明した当該要素の内容モデルに依存します。
要素はその内容モデルが禁じた内容を含んではなりません。しかも、
各要素の内容モデルによって内容に課した制約に加えて、5種類の要素には追加の構文的要件があります。
Void elements can't have any contents (since there's
no end tag, no content can be put between the start tag and the end
tag).空隙要素は内容を持つことができません
(終了タグがないので、内容を開始タグと終了タグの間に置くことができません)。
CDATA elements can have text,
though it has restrictions
described below.CDATA 要素はテキストを持つことができますが、
後述の制約があります。
RCDATA elements can have text
and character references, but
the text must not contain an ambiguous ampersand.
There are also further
restrictions described below.RCDATA 要素はテキストと文字参照を持つことができますが、
テキストは曖昧アンド記号を含んではなりません。
後述の追加制約もあります。
Foreign elements whose start tag is marked as self-closing can't
have any contents (since, again, as there's no end tag, no content
can be put between the start tag and the end tag). Foreign elements
whose start tag is not marked as self-closing can have
text, character references, CDATA sections, other elements, and comments, but the text must not
contain the character U+003C LESS-THAN SIGN (<) or
an ambiguous
ampersand.開始タグが自己閉塞と印付けされた外来要素は内容を持つことができません
(やはり、終了タグがないため、内容を開始タグと終了タグの間に置くことができないからです)。
開始タグが自己閉塞と印付けされていない外来要素はテキスト、
文字参照、
CDATA 区間、
他の要素、
注釈を持つことができますが、
テキストは文字 U+003C LESS-THAN SIGN (<)
や曖昧アンド記号を含んではなりません。
Normal elements can have text,
character references, other
elements, and comments, but the text must not
contain the character U+003C LESS-THAN SIGN (<) or
an ambiguous
ampersand. Some normal elements also have yet more restrictions on what
content they are allowed to hold, beyond the restrictions imposed by
the content model and those described in this paragraph. Those
restrictions are described below.通常要素はテキスト、
文字参照、
他の要素、
注釈を持つことができますが、
テキストは文字 U+003C LESS-THAN SIGN (<)
や曖昧アンド記号を含んではなりません。
いくつかの通常要素は、保持することが認められる内容に関して、
内容モデルにより課される制約やこの段落で説明した制約に加え、
更に追加の制約をも有します。
その制約については後述します。
Tags contain a tag name,
giving the element's name. HTML elements all have names that only
use characters in the range U+0030 DIGIT ZERO .. U+0039 DIGIT NINE,
U+0061 LATIN SMALL LETTER A .. U+007A LATIN SMALL LETTER Z, U+0041
LATIN CAPITAL LETTER A .. U+005A LATIN CAPITAL LETTER Z, and U+002D
HYPHEN-MINUS (-). In the HTML syntax, tag names may be
written with any mix of lower- and uppercase letters that, when
converted to all-lowercase, matches the element's tag name; tag
names are case-insensitive.タグはタグ名を持ち、
これが要素の名前を与えます。
HTML 要素はすべて、範囲 U+0030 DIGIT ZERO ～ U+0039 DIGIT NINE、
U+0061 LATIN SMALL LETTER A ～ U+007A LATIN SMALL LETTER Z、U+0041
LATIN CAPITAL LETTER A ～ U+005A LATIN CAPITAL LETTER Z、 U+002D
HYPHEN-MINUS (-) の文字のみを使った名前を持ちます。
HTML 構文では、タグ名はすべて小文字に変換した時に要素のタグ名に一致するような任意の小文字と大文字の組み合わせで書いて構いません。
つまり、タグ名は大文字・小文字を区別しません。
Start tags must have the
following format:
The first character of a start tag must be a U+003C LESS-THAN
SIGN (<).開始タグの最初の文字は U+003C LESS-THAN
SIGN (<) でなければなりません。
The next few characters of a start tag must be the element's
tag name.開始タグの次の数文字は要素のタグ名でなければなりません。
If there are to be any attributes in the next step, there must
first be one or more space
characters.次の段階で属性が存在する場合には、まず1文字以上の間隔文字がなければなりません。
Then, the start tag may have a number of attributes, the syntax for which is described
below. Attributes may be separated from each other by one or more
space characters.その後、開始タグは後述の構文に沿った数々の属性を持って構いません。
属性は1つ以上の間隔文字で互いに分離して構いません。
After the attributes, there may be one or more space characters. (Some attributes
are required to be followed by a space. See the attributes section below.)属性の後に、1文字以上の間隔文字があって構いません。
(いくつかの属性の後には間隔が必須です。後述の属性の節をご覧ください。)
Then, if the element is one of the void elements,
or if the element is a foreign element, then there may be a single
U+002F SOLIDUS (/) character. This character has no
effect on void elements, but on foreign elements it marks the start
tag as self-closing.要素が空隙要素の1つである場合や、
要素が外来要素である場合、 U+002F SOLIDUS (/) 文字が1つあっても構いません。
この文字は空隙要素にあっては何の効果もありませんが、
外来要素にあっては開始タグを自己閉塞と印付けします。
Finally, start tags must be closed by a U+003E GREATER-THAN
SIGN (>) character.最後に、開始タグは U+003E GREATER-THAN
SIGN (>) もjいで閉じなければなりません。
End tags must have the
following format:
The first character of an end tag must be a U+003C LESS-THAN
SIGN (<).終了タグの最初の文字は U+003C LESS-THAN
SIGN (<) でなければなりません。
The second character of an end tag must be a U+002F SOLIDUS
(/).終了タグの2番目の文字は U+002F SOLIDUS
(/) でなければなりません。
The next few characters of an end tag must be the element's
tag name.終了タグの次の数文字は要素のタグ名でなければなりません。
After the tag name, there may be one or more space characters.タグ名の後、1文字以上の間隔文字があって構いません。
Finally, end tags must be closed by a U+003E GREATER-THAN
SIGN (>) character.最後に、終了タグは U+003E GREATER-THAN
SIGN (>) 文字により閉じなければなりません。
8.1.2.3 Attributes8.1.2.3 属性
Attributes for an element
are expressed inside the element's start tag.要素の属性は、
当該要素の開始タグの内側で表現されます。
Attributes have a name and a value. Attribute names must consist of
one or more characters other than the space characters, U+0000 NULL, U+0022 QUOTATION
MARK ("), U+0027 APOSTROPHE ('), U+003E GREATER-THAN SIGN
(>), U+002F SOLIDUS (/), and U+003D EQUALS SIGN (=) characters,
the control characters, and any characters that are not defined by
Unicode. In the HTML syntax, attribute names may be written with any
mix of lower- and uppercase letters that are an ASCII
case-insensitive match for the attribute's name.属性は名前と値を持ちます。
属性名は、
間隔文字、U+0000 NULL、U+0022 QUOTATION
MARK (")、U+0027 APOSTROPHE (')、U+003E GREATER-THAN SIGN
(>)、U+002F SOLIDUS (/)、U+003D EQUALS SIGN (=) のいずれかの文字、
制御文字、 Unicode で定義されていない文字以外の文字1文字以上で構成されなければなりません。
HTML 構文では、属性名は当該属性の名前に
ASCII
大文字・小文字不区別で一致する任意の小文字・大文字の組み合わせで書いて構いません。
Attribute values are a
mixture of text and character references, except with the
additional restriction that the text cannot contain an ambiguous ampersand.属性値はテキストと文字参照の混合ですが、テキストが曖昧アンド記号を含むことができないとの追加の制限があります。
Attributes can be specified in four different ways:属性は4種類の方法で指定できます。
- Empty attribute syntax空属性構文
-
Just the attribute
name.属性名のみです。
In the following example, the disabled attribute is given with
the empty attribute syntax:次の例では、disabled
属性が空属性構文により与えられています。
<input disabled>
If an attribute using the empty attribute syntax is to be
followed by another attribute, then there must be a space
character separating the two.空属性構文を用いる属性の後に別の属性が続く場合、
両者を分離する間隔文字がなければなりません。
- Unquoted attribute value syntax非引用属性値構文
-
The attribute name,
followed by zero or more space
characters, followed by a single U+003D EQUALS SIGN
character, followed by zero or more space characters, followed by the attribute value, which, in
addition to the requirements given above for attribute values,
must not contain any literal space
characters, any U+0022 QUOTATION MARK (")
characters, U+0027 APOSTROPHE (') characters,
U+003D EQUALS SIGN (=) characters, or U+003E
GREATER-THAN SIGN (>) characters, and must not be
the empty string.属性名の後に零文字以上の間隔文字があり、
その後に1文字の U+003D EQUALS SIGN 文字があり、その後に零文字以上の間隔文字があり、
その後に属性値があるもので、
その属性値については前述の属性値に関する要件に加え、
生の間隔文字、
U+0022 QUOTATION MARK (") 文字、
U+0027 APOSTROPHE (') 文字、
U+003D EQUALS SIGN (=) 文字、
U+003E
GREATER-THAN SIGN (>) 文字を含んではならず、
空文字列であってはなりません。
In the following example, the value attribute is given
with the unquoted attribute value syntax:次の例では、
value
属性が非引用属性値構文により与えられています。
<input value=yes>
If an attribute using the unquoted attribute syntax is to be
followed by another attribute or by one of the optional U+002F
SOLIDUS (/) characters allowed in step 6 of the start tag syntax above, then there
must be a space character separating the two.
- Single-quoted attribute value syntax単一引用符属性値構文
-
The attribute name,
followed by zero or more space
characters, followed by a single U+003D EQUALS SIGN
character, followed by zero or more space characters, followed by a single U+0027
APOSTROPHE (') character, followed by the attribute value, which, in
addition to the requirements given above for attribute values,
must not contain any literal U+0027 APOSTROPHE (')
characters, and finally followed by a second single U+0027
APOSTROPHE (') character.属性名の後、
零文字以上の間隔文字が続き、
その後1文字の U+003D EQUALS SIGN
文字が続き、零文字以上の間隔文字が続き、1文字の U+0027
APOSTROPHE (') 文字が続き、属性値が続き、
この属性値については先述の属性値に関する要件に加えて生の U+0027 APOSTROPHE (')
文字を含んではならず、その後に2つ目の1文字の
U+0027
APOSTROPHE (') 文字が続くもの。
In the following example, the type attribute is given with the
single-quoted attribute value syntax:次の例では、
type
属性が単一引用符属性値構文により与えられます。
<input type='checkbox'>
If an attribute using the single-quoted attribute syntax is to
be followed by another attribute, then there must be a space
character separating the two.単一引用符属性構文を使った属性に他の属性が続く場合、両者を間隔文字によって分離しなければなりません。
- Double-quoted attribute value syntax二重引用符属性値構文
-
The attribute name,
followed by zero or more space
characters, followed by a single U+003D EQUALS SIGN
character, followed by zero or more space characters, followed by a single U+0022
QUOTATION MARK (") character, followed by the attribute value, which, in
addition to the requirements given above for attribute values,
must not contain any literal U+0022 QUOTATION MARK
(") characters, and finally followed by a second
single U+0022 QUOTATION MARK (") character.属性名の後に零文字以上の間隔文字が続き、
その後に1文字の U+003D EQUALS SIGN
文字が続き、その後に零文字以上の間隔文字が続き、その後に1文字の U+0022
QUOTATION MARK (") 文字が続き、その後に属性値が続くところ、
前述の属性値に関する要件に加えて生の U+0022 QUOTATION MARK
(") 文字を含んではならず、
最後に2つ目の1文字の U+0022 QUOTATION MARK (") 文字が続くもの。
In the following example, the name attribute is given with the
double-quoted attribute value syntax:次の例では、 name
属性が二重引用符属性値構文で与えられます。
<input name="be evil">
If an attribute using the double-quoted attribute syntax is to
be followed by another attribute, then there must be a space
character separating the two.二重引用符属性構文を使った属性の後に他の属性が続く場合、両者を間隔文字により分離しなければなりません。
There must never be two or more attributes on the same start tag
whose names are an ASCII case-insensitive match for
each other.同じ開始タグに名前が ASCII 大文字・小文字不区別で一致する属性が2つ以上あってはなりません。
Certain tags can be omitted.タグの中には省略できるものがあります。
An html element's start tag may be omitted if the
first thing inside the html element is not a comment.
An html element's end
tag may be omitted if the html element is not
immediately followed by a comment.
A head element's start tag may be omitted if the
first thing inside the head element is an element.
A head element's end
tag may be omitted if the head element is not
immediately followed by a space character or a comment.
A body element's start tag may be omitted if the
first thing inside the body element is not a
space character or a comment, except if the first thing
inside the body element is a script or
style element.
A body element's end
tag may be omitted if the body element is not
immediately followed by a comment.
A li element's end
tag may be omitted if the li element is
immediately followed by another li element or if there
is no more content in the parent element.
A dt element's end
tag may be omitted if the dt element is
immediately followed by another dt element or a
dd element.
A dd element's end
tag may be omitted if the dd element is
immediately followed by another dd element or a
dt element, or if there is no more content in the
parent element.
A p element's end
tag may be omitted if the p element is
immediately followed by an address,
article, aside, blockquote,
datagrid, dialog, dir,
div, dl, fieldset,
footer, form, h1,
h2, h3, h4, h5,
h6, header, hr,
menu, nav, ol,
p, pre, section,
table, or ul, element, or if there is no
more content in the parent element and the parent element is not an
a element.
An rt element's end
tag may be omitted if the rt element is
immediately followed by an rt or rp
element, or if there is no more content in the parent element.
An rp element's end
tag may be omitted if the rp element is
immediately followed by an rt or rp
element, or if there is no more content in the parent element.
An optgroup element's end tag may be omitted if the
optgroup element is immediately followed by
another optgroup element, or if there is no
more content in the parent element.
An option element's end
tag may be omitted if the option element is
immediately followed by another option element, or if
it is immediately followed by an optgroup element, or
if there is no more content in the parent element.
A colgroup element's start tag may be omitted if the
first thing inside the colgroup element is a
col element, and if the element is not immediately
preceded by another colgroup element whose end tag has been omitted.
A colgroup element's end tag may be omitted if the
colgroup element is not immediately followed by a
space character or a comment.
A thead element's end
tag may be omitted if the thead element is
immediately followed by a tbody or tfoot
element.
A tbody element's start tag may be omitted if the
first thing inside the tbody element is a
tr element, and if the element is not immediately
preceded by a tbody, thead, or
tfoot element whose end
tag has been omitted.
A tbody element's end
tag may be omitted if the tbody element is
immediately followed by a tbody or tfoot
element, or if there is no more content in the parent element.
A tfoot element's end
tag may be omitted if the tfoot element is
immediately followed by a tbody element, or if there is
no more content in the parent element.
A tr element's end
tag may be omitted if the tr element is
immediately followed by another tr element, or if there
is no more content in the parent element.
A td element's end
tag may be omitted if the td element is
immediately followed by a td or th
element, or if there is no more content in the parent element.
A th element's end
tag may be omitted if the th element is
immediately followed by a td or th
element, or if there is no more content in the parent element.
However, a start
tag must never be omitted if it has any attributes.
8.1.2.5 Restrictions on content models8.1.2.5 内容モデルの制限
For historical reasons, certain elements have extra restrictions
beyond even the restrictions given by their content model.歴史的理由により、内容モデルによる制限以上の追加の制限を持つ要素がいくつかあります。
A table element must not contain tr
elements, even though these elements are technically allowed inside
table elements according to the content models
described in this specification. (If a tr element is
put inside a table in the markup, it will in fact imply
a tbody start tag before it.)table
要素はこの仕様書で述べた内容モデルに従えば技術的には内側で
tr 要素が認められていますが、
table
要素は tr 要素を含んではなりません。
(tr 要素がマーク付け中で
table 要素の内側に置かれた場合、
実際には前に tbody 開始タグが暗示的に存在するものとみなされます。)
A single U+000A LINE FEED (LF) character may be placed
immediately after the start
tag of pre and textarea
elements. This does not affect the processing of the element. The
otherwise optional U+000A LINE FEED (LF) character must be
included if the element's contents start with that character
(because otherwise the leading newline in the contents would be
treated like the optional newline, and ignored).
The following two pre blocks are equivalent:次の2つの pre
ブロックは等価です。
<pre>Hello</pre><pre>こんにちは</pre>
<pre>
Hello</pre><pre>
こんにちは</pre>
8.1.2.6 Restrictions on the contents of CDATA and RCDATA elements8.1.2.6 CDATA 要素と RCDATA 要素の内容の制限
The text in CDATA and RCDATA elements must not contain any
occurrences of the string "</" (U+003C
LESS-THAN SIGN, U+002F SOLIDUS) followed by characters that
case-insensitively match the tag name of the element followed by one
of U+0009 CHARACTER TABULATION, U+000A LINE FEED (LF), U+000C FORM
FEED (FF), U+0020 SPACE, U+003E GREATER-THAN SIGN (>), or U+002F
SOLIDUS (/), unless that string is part of an escaping text span.CDATA 要素や RCDATA 要素のテキストは文字列「</」 (U+003C
LESS-THAN SIGN、U+002F SOLIDUS) の後に要素のタグ名と大文字・小文字を区別しない場合に一致する文字が続き、
その後に U+0009 CHARACTER TABULATION、U+000A LINE FEED (LF)、U+000C FORM
FEED (FF)、U+0020 SPACE、U+003E GREATER-THAN SIGN (>)、U+002F
SOLIDUS (/)
のいずれかが続くような列を、その文字列が逃避テキスト径間の一部である場合を除き、
含んではなりません。
An escaping text span is a span
of text that starts with an escaping text span start that is
not itself in an escaping text
span, and ends at the next escaping text span end. There
cannot be any character
references inside an escaping
text span — sequences of characters that would look
like character references do not
have special meaning.
An escaping text span
start is a part of text that
consists of the four character sequence "<!--" (U+003C LESS-THAN SIGN, U+0021 EXCLAMATION
MARK, U+002D HYPHEN-MINUS, U+002D HYPHEN-MINUS).逃避テキスト径間開始は、
テキストの一部で、
4文字の列「<!--」(U+003C LESS-THAN SIGN、U+0021 EXCLAMATION
MARK、U+002D HYPHEN-MINUS、U+002D HYPHEN-MINUS) です。
An escaping text span end is
a part of text that consists of the
three character sequence "-->" (U+002D
HYPHEN-MINUS, U+002D HYPHEN-MINUS, U+003E GREATER-THAN SIGN) whose
U+003E GREATER-THAN SIGN (>).
An escaping text span
start may share its U+002D HYPHEN-MINUS characters with its
corresponding escaping text span
end.逃避テキスト径間開始は、
その U+002D HYPHEN-MINUS 文字を対応する逃避テキスト径間終了と共有して構いません。
The text in CDATA and RCDATA elements must not have an escaping text span start that is
not followed by an escaping text
span end.CDATA 要素と RCDATA 要素のテキストは逃避テキスト径間終了が後に続かない逃避テキスト径間開始を含んではなりません。
8.1.3 Text8.1.3 テキスト
Text is allowed inside elements,
attributes, and comments. Text must consist of Unicode characters.
Text must not contain U+0000 characters. Text must not contain
permanently undefined Unicode characters. Text must not contain
control characters other than space
characters. Extra constraints are placed on what is and what
is not allowed in text based on where the text is to be put, as
described in the other sections.テキストは要素、
属性、注釈の内側で認められています。
テキストは Unicode 文字で構成されなければなりません。
テキストは U+0000 文字を含んではなりません。
テキストは恒久的に未定義の Unicode 文字を含んではなりません。
テキストは間隔文字以外の制御文字を含んではなりません。
他の節で述べた通り、テキストが配置される場所によって、テキスト中で何が認められ、
何が認められないかの追加の制約があります。
8.1.3.1 Newlines8.1.3.1 改行
Newlines in HTML may be
represented either as U+000D CARRIAGE RETURN (CR) characters, U+000A
LINE FEED (LF) characters, or pairs of U+000D CARRIAGE RETURN (CR),
U+000A LINE FEED (LF) characters in that order.HTML の改行は
U+000D CARRIAGE RETURN (CR) 文字か、U+000A
LINE FEED (LF) 文字か、U+000D CARRIAGE RETURN (CR) 文字と
U+000A LINE FEED (LF) 文字の組をこの順序で用いるかのいずれかによって表現して構いません。
8.1.4 Character references8.1.4 文字参照
In certain cases described in other sections, text may be mixed with character references. These can be used
to escape characters that couldn't otherwise legally be included in
text.他の節で述べたいくつかの場合において、テキストには
文字参照を混在させて構いません。
文字参照は、通常合法的にテキストに含めることができない文字を逃避するために使うことができます。
Character references must start with a U+0026 AMPERSAND
(&). Following this, there are three possible kinds
of character references:文字参照は、U+0026 AMPERSAND
(&) により始まらなければなりません。
この文字に続けて、3種類の文字参照があります。
- Named character references名前付き文字参照
- The ampersand must be followed by one of the names given in the
named character references section, using the same
case. The name must be one that is terminated by a U+003B SEMICOLON
(
;) character.アンド記号の後には、
名前付き文字参照の節にある名前のいずれかを、
同じ大文字・小文字の組み合わせによって続けなければなりません。
名前は U+003B SEMICOLON
(;) 文字で終わるものでなければなりません。
- Decimal numeric character reference十進数値文字参照
- The ampersand must be followed by a U+0023 NUMBER SIGN
(
#) character, followed by one or more digits in the
range U+0030 DIGIT ZERO .. U+0039 DIGIT NINE, representing a
base-ten integer that itself is a Unicode code point that is
not U+0000, U+000D, in the range U+0080 .. U+009F, or in the range
0xD800 .. 0xDFFF (surrogates). The digits must then be followed by
a U+003B SEMICOLON character (;).アンド記号の後には、 U+0023 NUMBER SIGN
(#) 文字が続き、 Unicode 符号位置であって
U+0000、U+000D、範囲 U+0080 ～ U+009F、範囲 0xD800～0xDFFF (代理)
でない十進整数を表す1文字以上の範囲 U+0030 DIGIT ZERO ～ U+0039 DIGIT NINE
の数字が続かなければなりません。
数字の後には U+003B SEMICOLON 文字 (;)
が続かなければなりません。
- Hexadecimal numeric character reference十六進数値文字参照
- The ampersand must be followed by a U+0023 NUMBER SIGN
(
#) character, which must be followed by either a
U+0078 LATIN SMALL LETTER X or a U+0058 LATIN CAPITAL LETTER X
character, which must then be followed by one or more digits in the
range U+0030 DIGIT ZERO .. U+0039 DIGIT NINE, U+0061 LATIN SMALL
LETTER A .. U+0066 LATIN SMALL LETTER F, and U+0041 LATIN CAPITAL
LETTER A .. U+0046 LATIN CAPITAL LETTER F, representing a
base-sixteen integer that itself is a Unicode code point that is
not U+0000, U+000D, in the range U+0080 .. U+009F, or in the range
0xD800 .. 0xDFFF (surrogates). The digits must then be followed by
a U+003B SEMICOLON character (;).アンド記号の後には、 U+0023 NUMBER SIGN
(#) 文字が続き、その後に U+0078 LATIN SMALL LETTER X 文字か
U+0058 LATIN CAPITAL LETTER X 文字が続き、その後に
Unicode 符号位置であって
U+0000、U+000D、範囲 U+0080 ～ U+009F、
範囲 0xD800 .. 0xDFFF (代理)
でない十六進整数を表す1文字以上の範囲
U+0030 DIGIT ZERO ～ U+0039 DIGIT NINE、U+0061 LATIN SMALL
LETTER A ～ U+0066 LATIN SMALL LETTER F、 U+0041 LATIN CAPITAL
LETTER A ～ U+0046 LATIN CAPITAL LETTER F
の数字が続かなければなりません。
数字の後には U+003B SEMICOLON 文字 (;)
が続かなければなりません。
An ambiguous
ampersand is a U+0026 AMPERSAND (&) character
that is followed by some text other
than a space character, a U+003C LESS-THAN SIGN
character ('<'), or another U+0026 AMPERSAND (&)
character.曖昧アンド記号は、
間隔文字、U+003C LESS-THAN SIGN
文字 ('<')、別の U+0026 AMPERSAND (&) 文字以外の
テキストが続く
U+0026 AMPERSAND (&) 文字です。
8.1.5 CDATA sections8.1.5 CDATA 区間
CDATA sections must start with
the character sequence U+003C LESS-THAN SIGN, U+0021 EXCLAMATION
MARK, U+005B LEFT SQUARE BRACKET, U+0043 LATIN CAPITAL LETTER C,
U+0044 LATIN CAPITAL LETTER D, U+0041 LATIN CAPITAL LETTER A, U+0054
LATIN CAPITAL LETTER T, U+0041 LATIN CAPITAL LETTER A, U+005B LEFT
SQUARE BRACKET (<![CDATA[). Following this
sequence, the CDATA section may have text, with the additional restriction
that the text must not contain the three character sequence U+005D
RIGHT SQUARE BRACKET, U+005D RIGHT SQUARE BRACKET, U+003E
GREATER-THAN SIGN (]]>). Finally, the CDATA
section must be ended by the three character sequence U+005D RIGHT
SQUARE BRACKET, U+005D RIGHT SQUARE BRACKET, U+003E GREATER-THAN
SIGN (]]>).CDATA 区間は、
文字列 U+003C LESS-THAN SIGN、U+0021 EXCLAMATION
MARK、U+005B LEFT SQUARE BRACKET、U+0043 LATIN CAPITAL LETTER C、
U+0044 LATIN CAPITAL LETTER D、U+0041 LATIN CAPITAL LETTER A、U+0054
LATIN CAPITAL LETTER T、U+0041 LATIN CAPITAL LETTER A、U+005B LEFT
SQUARE BRACKET (<![CDATA[) で始まらなければなりません。
CDATA 区間は、この文字列に続けて、
テキストを持って構いません。
ただし、追加の制限として、このテキストは3文字の列 U+005D
RIGHT SQUARE BRACKET、U+005D RIGHT SQUARE BRACKET、U+003E
GREATER-THAN SIGN (]]>) を含んではなりません。
最後に、CDATA 区間は、3文字の列 U+005D RIGHT
SQUARE BRACKET、U+005D RIGHT SQUARE BRACKET、U+003E GREATER-THAN
SIGN (]]>) で終わらなければなりません。
must start with the
four character sequence U+003C LESS-THAN SIGN, U+0021 EXCLAMATION
MARK, U+002D HYPHEN-MINUS, U+002D HYPHEN-MINUS (<!--). Following this sequence, the comment may
have text, with the additional
restriction that the text must not start with a single U+003E
GREATER-THAN SIGN ('>') character, nor start with a U+002D
HYPHEN-MINUS (-) character followed by a
U+003E GREATER-THAN SIGN ('>') character, nor contain two
consecutive U+002D HYPHEN-MINUS (-)
characters, nor end with a U+002D HYPHEN-MINUS (-) character. Finally, the comment must be ended by
the three character sequence U+002D HYPHEN-MINUS, U+002D
HYPHEN-MINUS, U+003E GREATER-THAN SIGN (-->).は、
4文字の列 U+003C LESS-THAN SIGN、U+0021 EXCLAMATION
MARK、U+002D HYPHEN-MINUS、U+002D HYPHEN-MINUS (<!--)
で始まらなければなりません。
注釈は、この文字列に続けて、
テキストを持って構いません。
ただし、追加の制限として、このテキストは U+003E
GREATER-THAN SIGN ('>') 文字1文字から始まったり、 U+002D
HYPHEN-MINUS (-) 文字の後に
U+003E GREATER-THAN SIGN ('>') 文字が続く列から始まったり、
2つの連続する U+002D HYPHEN-MINUS (-)
文字を含んだり、 U+002D HYPHEN-MINUS (-) 文字で終わったりしてはなりません。
最後に、注釈は3文字の列 U+002D HYPHEN-MINUS、U+002D
HYPHEN-MINUS、U+003E GREATER-THAN SIGN (-->)
で終わらなければなりません。
8.2 Parsing HTML documents8.2 HTML 文書の構文解析
This section only applies to user agents, data mining tools,
and conformance checkers.この節は利用者エージェント、データ・マイニング・ツール、
適合性検査器のみに適用されます。
The rules for parsing XML documents (and thus
XHTML documents) into DOM trees are covered by the XML
and Namespaces in XML specifications, and are out of scope of this
specification. [XML] [XMLNS]
For HTML documents, user agents must use the parsing
rules described in this section to generate the DOM trees. Together,
these rules define what is referred to as the HTML
parser.HTML 文書については、利用者エージェントは、 DOM
木を生成するためにこの節で説明する構文解析規則を使用しなければなりません。
また、この規則はHTML 構文解析器と呼ばれるものを定義します。
While the HTML form of HTML5 bears a close resemblance to SGML
and XML, it is a separate language with its own parsing rules.HTML5 の HTML 形式は SGML や XML によく似ていますが、
独自の構文解析規則を持つ別の言語です。
Some earlier versions of HTML (in particular from HTML2 to
HTML4) were based on SGML and used SGML parsing rules. However, few
(if any) web browsers ever implemented true SGML parsing for HTML
documents; the only user agents to strictly handle HTML as an SGML
application have historically been validators. The resulting
confusion — with validators claiming documents to have one
representation while widely deployed Web browsers interoperably
implemented a different representation — has wasted decades
of productivity. This version of HTML thus returns to a non-SGML
basis.以前のいくつかの版の HTML (特に HTML2 から HTML4 まで) は SGML
に基づき、 SGML の構文解析規則を用いていました。しかし、 HTML
文書用に真の SGML 構文解析を実装していたウェブ・ブラウザは (あったとしても)
皆無に近い数でした。 HTML を厳密に SGML 応用として扱う唯一の利用者エージェントは歴史的に妥当性検証器だけでした。
その結果、妥当性検査器は文書がある形式であることを要求し、
一方で広く実用されている Web ブラウザはそれとは異なる形式を相互運用可能な形で実装するという混乱が生じ、
生産性を大きく低下させています。
ですので、この版の HTML は非 SGML ベースに回帰します。
Authors interested in using SGML tools in their authoring
pipeline are encouraged to use XML tools and the XML serialization
of HTML5.文書準備の過程で SGML ツールを使いたいと考える著者には、
XML ツールと HTML5 の XML 直列化を用いることをお勧めします。
This specification defines the parsing rules for HTML documents,
whether they are syntactically correct or not. Certain points in the
parsing algorithm are said to be parse
errors. The error handling for parse errors is well-defined:
user agents must either act as described below when encountering
such problems, or must abort processing at the first error that they
encounter for which they do not wish to apply the rules described
below.この仕様書は、 HTML 文書を、それが構文的に正しいか否かによらず、その構文解析を行うための規則を定義します。
この構文解析算法のいくつかの地点は構文解析誤りであるといいます。
構文解析誤りの誤りの取り扱いは明確に定義するところであり、
利用者エージェントは、
そのような問題に遭遇した時に後述の通りに作用するか、
または後述の規則を適用したくないような最初の誤りの時点で処理を停止するかのいずれかでなければなりません。
Conformance checkers must report at least one parse error
condition to the user if one or more parse error conditions exist in
the document and must not report parse error conditions if none
exist in the document. Conformance checkers may report more than one
parse error condition if more than one parse error conditions exist
in the document. Conformance checkers are not required to recover
from parse errors.適合性検査器は、文書中に1つ以上の構文解析誤り条件が存在する場合、利用者に最低1つの構文解析誤り条件を報告しなければならず、
文書に誤りが存在しない場合、構文解析誤り条件を報告してはなりません。
適合性検査器は、文書中に複数の構文解析誤り条件が存在する場合、
複数の構文解析誤り条件を報告して構いません。
適合性検査器は構文解析誤りから回復することを要求されません。
Parse errors are only errors with the
syntax of HTML. In addition to checking for parse errors,
conformance checkers will also verify that the document obeys all
the other conformance requirements described in this
specification.構文解析誤りは、 HTML の構文の誤りに過ぎません。
適合性検査器は、構文解析誤りの検査に加え、
文書がこの仕様書で説明されている他の適合性要件に従っているかも検査することになります。
8.2.1 Overview of the parsing model8.2.1 構文解析モデルの概要
The input to the HTML parsing process consists of a stream of
Unicode characters, which is passed through a
tokenization stage (lexical analysis) followed by a
tree construction stage (semantic analysis). The output
is a Document object.HTML 構文解析処理への入力は、Unicode 文字の列によって構成され、
まずは字句化段階 (字句解析)
に渡され、その後に木構築 段階 (意味解析)
に渡されます。
出力は、 Document オブジェクトです。
Implementations that do not
support scripting do not have to actually create a DOM
Document object, but the DOM tree in such cases is
still used as the model for the rest of the specification.スクリプティングに対応しない実装は実際に DOM
Document オブジェクトを作る必要はありませんが、
その場合であっても、この仕様書の残りの部分のモデルとしてはやはり DOM 木を使います。
In the common case, the data handled by the tokenization stage
comes from the network, but it can also come from script, e.g. using the document.write() API.多くの場合は字句化段階が取り扱うデータはネットワークから来るものですが、
スクリプトからも、例えば document.write() API
によって来ることがあります。
There is only one set of state for the
tokeniser stage and the tree construction stage, but the tree
construction stage is reentrant, meaning that while the tree
construction stage is handling one token, the tokeniser might be
resumed, causing further tokens to be emitted and processed before
the first token's processing is complete.字句化器段階と木構築段階の状態は一揃いしかありませんが、
木構築段階は再入可能であり、木構築段階がある字句を処理している間に字句化器が再開して更に字句を放出し、
最初の字句の処理が完了する前に新しい字句が処理されることがあります。
In the following example, the tree construction stage will be
called upon to handle a "p" start tag token while handling the
"script" start tag token:次の例では、 "script" 開始タグ字句を処理している間に木構築段階が "p" 開始タグ字句を処理するために呼び出されることとなります。
...
<script>
document.write('<p>');
</script>
...
To handle these cases, parsers have a script nesting
level, which must be initially set to zero, and a parser
pause flag, which must be initially set to false.
The stream of Unicode characters that consists the input to the
tokenization stage will be initially seen by the user agent as a
stream of bytes (typically coming over the network or from the local
file system). The bytes encode the actual characters according to a
particular character encoding, which the user agent must
use to decode the bytes into characters.字句か段階への入力を構成する Unicode 文字のストリームは、はじめ利用者エージェントに
(普通はネットワークか局所ファイル・システムから来た) バイトのストリームとして見えます。
バイトは特定の文字符号化に従って実際の文字を符号化しており、
利用者エージェントはその文字符号化を使ってバイトを文字に復号しなければなりません。
For XML documents, the algorithm user agents must
use to determine the character encoding is given by the XML
specification. This section does not apply to XML documents. [XML]XML 文書に関しては、文字符号化を決定するために利用者エージェントが使わなければならない算法は
XML 仕様書で与えられています。この節は XML 文書には適用しません。 [XML]
8.2.2.1 Determining the character encoding8.2.2.1 文字符号化の決定
In some cases, it might be impractical to unambiguously determine
the encoding before parsing the document. Because of this, this
specification provides for a two-pass mechanism with an optional
pre-scan. Implementations are allowed, as described below, to apply
a simplified parsing algorithm to whatever bytes they have available
before beginning to parse the document. Then, the real parser is
started, using a tentative encoding derived from this pre-parse and
other out-of-band metadata. If, while the document is being loaded,
the user agent discovers an encoding declaration that conflicts with
this information, then the parser can get reinvoked to perform a
parse of the document with the real encoding.場合によっては、文書の構文解析の前に符号化を曖昧なく決定することが非現実的かもしれません。
このため、この仕様書は任意選択の前走査を伴う2パス機構を提供します。
実装は、後述の通り、文書の構文解析を始める前に、利用可能になっているバイトに対して単純化した構文解析算法を適用することが認められています。
その後、実際の構文解析器が、この前構文解析やその他の外部メタデータによって得られた暫定符号化を用いて開始します。
文書が読み込まれる間に利用者エージェントがその情報と矛盾する符号化宣言を発見した場合、
構文解析器は、実際の符号化によって文書の構文解析を行うために再呼び出しされることがあります。
User agents must use the following
algorithm (the encoding sniffing algorithm) to determine
the character encoding to use when decoding a document in the first
pass. This algorithm takes as input any out-of-band metadata
available to the user agent (e.g. the Content-Type metadata of the document)
and all the bytes available so far, and returns an encoding and a
confidence. The
confidence is either tentative or certain. The
encoding used, and whether the confidence in that encoding is
tentative or confident, is used during the parsing to
determine whether to change the encoding.
If the transport layer specifies an encoding, and it is
supported, return that encoding with the confidence
certain, and abort these steps.
The user agent may wait for more bytes of the resource to be
available, either in this step or at any later step in this
algorithm. For instance, a user agent might wait 500ms or 512
bytes, whichever came first. In general preparsing the source to
find the encoding improves performance, as it reduces the need to
throw away the data structures used when parsing upon finding the
encoding information. However, if the user agent delays too long to
obtain data to determine the encoding, then the cost of the delay
could outweigh any performance improvements from the
preparse.
For each of the rows in the following table, starting with
the first one and going down, if there are as many or more bytes
available than the number of bytes in the first column, and the
first bytes of the file match the bytes given in the first column,
then return the encoding given in the cell in the second column of
that row, with the confidence
certain, and abort these steps:
| Bytes in Hexadecimal
バイトの十六進数表現 | Encoding
符号化 |
|---|
| FE FF
| UTF-16BE
|
| FF FE
| UTF-16LE
|
| EF BB BF
| UTF-8
|
This step looks for Unicode Byte Order Marks
(BOMs).
Otherwise, the user agent will have to search for explicit
character encoding information in the file itself. This should
proceed as follows:
Let position be a pointer to a byte in the
input stream, initially pointing at the first byte. If at any
point during these substeps the user agent either runs out of
bytes or decides that scanning further bytes would not be
efficient, then skip to the next step of the overall character
encoding detection algorithm. User agents may decide that scanning
any bytes is not efficient, in which case these substeps
are entirely skipped.
Now, repeat the following "two" steps until the algorithm
aborts (either because user agent aborts, as described above, or
because a character encoding is found):
If position points to:
- A sequence of bytes starting with: 0x3C 0x21 0x2D 0x2D (ASCII '<!--')0x3C 0x21 0x2D 0x2D (ASCII '<!--') で始まるバイト列
-
Advance the position pointer so that it
points at the first 0x3E byte which is preceded by two 0x2D
bytes (i.e. at the end of an ASCII '-->' sequence) and comes
after the 0x3C byte that was found. (The two 0x2D bytes can be
the same as the those in the '<!--' sequence.)
- A sequence of bytes starting with: 0x3C, 0x4D or 0x6D, 0x45 or 0x65, 0x54 or 0x74, 0x41 or 0x61, and finally one of 0x09, 0x0A, 0x0C, 0x0D, 0x20, 0x2F (case-insensitive ASCII '<meta' followed by a space or slash)0x3C, 0x4D or 0x6D, 0x45 or 0x65, 0x54 or 0x74, 0x41 or 0x61, and finally one of 0x09, 0x0A, 0x0C, 0x0D, 0x20, 0x2F (case-insensitive ASCII '<meta' followed by a space or slash) で始まるバイト列
-
Advance the position pointer so
that it points at the next 0x09, 0x0A, 0x0C, 0x0D, 0x20, or
0x2F byte (the one in sequence of characters matched
above).
Get
an attribute and its value. If no attribute was
sniffed, then skip this inner set of steps, and jump to the
second step in the overall "two step" algorithm.
If the attribute's name is neither "charset" nor "content",
then return to step 2 in these inner steps.
If the attribute's name is "charset", let charset be
the attribute's value, interpreted as a character
encoding.
Otherwise, the attribute's name is "content": apply the algorithm for
extracting an encoding from a Content-Type, giving the
attribute's value as the string to parse. If an encoding is
returned, let charset be that
encoding. Otherwise, return to step 2 in these inner
steps.
If charset is a UTF-16 encoding,
change it to UTF-8.
If charset is a supported
character encoding, then return the given encoding, with
confidence
tentative, and abort all these steps.
Otherwise, return to step 2 in these inner
steps.
- A sequence of bytes starting with a 0x3C byte (ASCII '<'), optionally a 0x2F byte (ASCII '/'), and finally a byte in the range 0x41-0x5A or 0x61-0x7A (an ASCII letter)
-
Advance the position pointer so
that it points at the next 0x09 (ASCII TAB), 0x0A (ASCII LF),
0x0C (ASCII FF), 0x0D (ASCII CR), 0x20 (ASCII space), or 0x3E
(ASCII '>') byte.
Repeatedly get an
attribute until no further attributes can be found,
then jump to the second step in the overall "two step"
algorithm.
- A sequence of bytes starting with: 0x3C 0x21 (ASCII '<!')0x3C 0x21 (ASCII '<!') で始まるバイト列
- A sequence of bytes starting with: 0x3C 0x2F (ASCII '</')0x3C 0x2F (ASCII '</') で始まるバイト列
- A sequence of bytes starting with: 0x3C 0x3F (ASCII '<?')0x3C 0x3F (ASCII '<?') で始まるバイト列
-
Advance the position pointer so that it
points at the first 0x3E byte (ASCII '>') that comes after the
0x3C byte that was found.
- Any other byteその他のバイト
-
Do nothing with that byte.
Move position so it points at the next
byte in the input stream, and return to the first step of this
"two step" algorithm.
When the above "two step" algorithm says to get an
attribute, it means doing this:
If the byte at position is one of 0x09
(ASCII TAB), 0x0A (ASCII LF), 0x0C (ASCII FF), 0x0D (ASCII CR),
0x20 (ASCII space), or 0x2F (ASCII '/') then advance position to the next byte and redo this
substep.
If the byte at position is 0x3E (ASCII
'>'), then abort the "get an attribute" algorithm. There isn't
one.
Otherwise, the byte at position is the
start of the attribute name. Let attribute
name and attribute value be the empty
string.
Attribute name: Process the byte at position as follows:
- If it is 0x3D (ASCII '='), and the attribute
name is longer than the empty string
- Advance position to the next byte and
jump to the step below labeled value.
- If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0C (ASCII
FF), 0x0D (ASCII CR), or 0x20 (ASCII space)
- Jump to the step below labeled spaces.
- If it is 0x2F (ASCII '/') or 0x3E (ASCII '>')
- Abort the "get an attribute" algorithm. The attribute's
name is the value of attribute name, its
value is the empty string.
- If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII
'Z')
- Append the Unicode character with codepoint b+0x20 to attribute
name (where b is the value of the
byte at position).
- Anything elseその他のもの
- Append the Unicode character with the same codepoint as the
value of the byte at position) to attribute name. (It doesn't actually matter how
bytes outside the ASCII range are handled here, since only
ASCII characters can contribute to the detection of a character
encoding.)
Advance position to the next byte and
return to the previous step.
Spaces. If the byte at position is one of 0x09 (ASCII TAB), 0x0A (ASCII
LF), 0x0C (ASCII FF), 0x0D (ASCII CR), or 0x20 (ASCII space) then
advance position to the next byte, then,
repeat this step.
If the byte at position is
not 0x3D (ASCII '='), abort the "get an attribute"
algorithm. The attribute's name is the value of attribute name, its value is the empty
string.
Advance position past the 0x3D (ASCII
'=') byte.
Value. If the byte at position is one of 0x09 (ASCII TAB), 0x0A (ASCII
LF), 0x0C (ASCII FF), 0x0D (ASCII CR), or 0x20 (ASCII space) then
advance position to the next byte, then,
repeat this step.
Process the byte at position as
follows:
- If it is 0x22 (ASCII '"') or 0x27 ("'")
-
Let b be the value of the byte at
position.
Advance position to the next
byte.
If the value of the byte at position
is the value of b, then advance position to the next byte and abort the "get
an attribute" algorithm. The attribute's name is the value of
attribute name, and its value is the
value of attribute value.
Otherwise, if the value of the byte at position is in the range 0x41 (ASCII 'A') to
0x5A (ASCII 'Z'), then append a Unicode character to attribute value whose codepoint is 0x20 more
than the value of the byte at position.
Otherwise, append a Unicode character to attribute value whose codepoint is the same as
the value of the byte at position.
Return to the second step in these substeps.
- If it is 0x3E (ASCII '>')
- Abort the "get an attribute" algorithm. The attribute's
name is the value of attribute name, its
value is the empty string.
- If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII
'Z')
- Append the Unicode character with codepoint b+0x20 to attribute
value (where b is the value of the
byte at position). Advance position to the next byte.
- Anything elseその他のもの
- Append the Unicode character with the same codepoint as the
value of the byte at position) to attribute value. Advance position to the next byte.
Process the byte at position as
follows:
- If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0C (ASCII
FF), 0x0D (ASCII CR), 0x20 (ASCII space), or 0x3E (ASCII
'>')
- Abort the "get an attribute" algorithm. The attribute's
name is the value of attribute name and its
value is the value of attribute value.
- If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII
'Z')
- Append the Unicode character with codepoint b+0x20 to attribute
value (where b is the value of the
byte at position).
- Anything elseその他のもの
- Append the Unicode character with the same codepoint as the
value of the byte at position) to attribute value.
Advance position to the next byte and
return to the previous step.
For the sake of interoperability, user agents should not use a
pre-scan algorithm that returns different results than the one
described above. (But, if you do, please at least let us know, so
that we can improve this algorithm and benefit everyone...)
If the user agent has information on the likely encoding for
this page, e.g. based on the encoding of the page when it was last
visited, then return that encoding, with the confidence
tentative, and abort these steps.
The user agent may attempt to autodetect the character
encoding from applying frequency analysis or other algorithms to
the data stream. If autodetection succeeds in determining a
character encoding, then return that encoding, with the confidence
tentative, and abort these steps. [UNIVCHARDET]
Otherwise, return an implementation-defined or
user-specified default character encoding, with the confidence
tentative. In non-legacy environments, the more
comprehensive UTF-8 encoding is
recommended. Due to its use in legacy content, windows-1252 is recommended as a default in
predominantly Western demographics instead. Since these encodings
can in many cases be distinguished by inspection, a user agent may
heuristically decide which to use as a default.
The document's character encoding must immediately
be set to the value returned from this algorithm, at the same time
as the user agent uses the returned value to select the decoder to
use for the input stream.
8.2.2.2 Character encoding requirements
User agents must at a minimum support the UTF-8 and Windows-1252
encodings, but may support more.
It is not unusual for Web browsers to support dozens
if not upwards of a hundred distinct character encodings.
User agents must support the preferred MIME name of every
character encoding they support that has a preferred MIME name, and
should support all the IANA-registered aliases. [IANACHARSET]
When comparing a string specifying a character encoding with the
name or alias of a character encoding to determine if they are
equal, user agents must ignore all characters in the ranges U+0009
to U+000D, U+0020 to U+002F, U+003A to U+0040, U+005B to U+0060, and
U+007B to U+007E (all whitespace and punctuation characters in
ASCII) in both names, and then perform the comparison in an
ASCII case-insensitive manner.
For instance, "GB_2312-80" and "g.b.2312(80)" are
considered equivalent names.
When a user agent would otherwise use an encoding given in the
first column of the following table, it must instead use the
encoding given in the cell in the second column of the same row. Any
bytes that are treated differently due to this encoding aliasing
must be considered parse
errors.
The requirement to treat certain encodings as other
encodings according to the table above is a willful violation of the
W3C Character Model specification. [CHARMOD]
User agents must not support the CESU-8, UTF-7, BOCU-1 and SCSU
encodings. [CESU8] [UTF7] [BOCU1] [SCSU]
Support for encodings based on EBCDIC is not recommended. This
encoding is rarely used for publicly-facing Web content.
Support for UTF-32 is not recommended. This encoding is rarely
used, and frequently misimplemented.
This specification does not make any attempt to
support EBCDIC-based encodings and UTF-32 in its algorithms; support
and use of these encodings can thus lead to unexpected behavior in
implementations of this specification.
Given an encoding, the bytes in the input stream must be
converted to Unicode characters for the tokeniser, as described by
the rules for that encoding, except that the leading U+FEFF BYTE
ORDER MARK character, if any, must not be stripped by the encoding
layer (it is stripped by the rule below).
Bytes or sequences of bytes in the original byte stream that
could not be converted to Unicode characters must be converted to
U+FFFD REPLACEMENT CHARACTER code points.
Bytes or sequences of bytes in the original byte
stream that did not conform to the encoding specification
(e.g. invalid UTF-8 byte sequences in a UTF-8 input stream) are
errors that conformance checkers are expected to report.
One leading U+FEFF BYTE ORDER MARK character must be ignored if
any are present.
All U+0000 NULL characters in the input must be replaced by
U+FFFD REPLACEMENT CHARACTERs. Any occurrences of such characters is
a parse error.
Any occurrences of any characters in the ranges U+0001 to U+0008,
U+000B, U+000E to
U+001F, U+007F to U+009F, U+D800 to U+DFFF , U+FDD0 to U+FDDF, and characters U+FFFE, U+FFFF,
U+1FFFE, U+1FFFF, U+2FFFE, U+2FFFF, U+3FFFE, U+3FFFF, U+4FFFE,
U+4FFFF, U+5FFFE, U+5FFFF, U+6FFFE, U+6FFFF, U+7FFFE, U+7FFFF,
U+8FFFE, U+8FFFF, U+9FFFE, U+9FFFF, U+AFFFE, U+AFFFF, U+BFFFE,
U+BFFFF, U+CFFFE, U+CFFFF, U+DFFFE, U+DFFFF, U+EFFFE, U+EFFFF,
U+FFFFE, U+FFFFF, U+10FFFE, and U+10FFFF are parse errors. (These are all control characters or
permanently undefined Unicode characters.)
U+000D CARRIAGE RETURN (CR) characters and U+000A LINE FEED (LF)
characters are treated specially. Any CR characters that are
followed by LF characters must be removed, and any CR characters not
followed by LF characters must be converted to LF characters. Thus,
newlines in HTML DOMs are represented by LF characters, and there
are never any CR characters in the input to the
tokenization stage.
The next input character is the first character in the
input stream that has not yet been consumed. Initially,
the next input character is the first character in the
input.
The insertion point is the position (just before a
character or just before the end of the input stream) where content
inserted using document.write() is actually
inserted. The insertion point is relative to the position of the
character immediately after it, it is not an absolute offset into
the input stream. Initially, the insertion point is
uninitialized.
The "EOF" character in the tables below is a conceptual character
representing the end of the input stream. If the parser
is a script-created parser, then the end of the
input stream is reached when an explicit "EOF"
character (inserted by the document.close() method) is
consumed. Otherwise, the "EOF" character is not a real character in
the stream, but rather the lack of any further characters.
8.2.2.4 Changing the encoding while parsing
When the parser requires the user agent to change the
encoding, it must run the following steps. This might happen
if the encoding sniffing algorithm described above
failed to find an encoding, or if it found an encoding that was not
the actual encoding of the file.
If the new encoding is a UTF-16 encoding, change it to
UTF-8.
If the new encoding is identical or equivalent to the encoding
that is already being used to interpret the input stream, then set
the confidence to
confident and abort these steps. This happens when the
encoding information found in the file matches what the
encoding sniffing algorithm determined to be the
encoding, and in the second pass through the parser if the first
pass found that the encoding sniffing algorithm described in the
earlier section failed to find the right encoding.
If all the bytes up to the last byte converted by the current
decoder have the same Unicode interpretations in both the current
encoding and the new encoding, and if the user agent supports
changing the converter on the fly, then the user agent may change
to the new converter for the encoding on the fly. Set the
document's character encoding and the encoding used to
convert the input stream to the new encoding, set the confidence to
confident, and abort these steps.
Otherwise, navigate to the document again, with
replacement enabled, and using the same source
browsing context, but this time skip the encoding
sniffing algorithm and instead just set the encoding to the
new encoding and the confidence to
confident. Whenever possible, this should be done without
actually contacting the network layer (the bytes should be
re-parsed from memory), even if, e.g., the document is marked as
not being cacheable.
8.2.3 Parse state8.2.3 構文解析状態
8.2.3.1 The insertion mode8.2.3.1 挿入モード
The insertion mode is a flag that controls the primary
operation of the tree construction stage.
Initially the insertion mode is "initial". It can change to
"before html",
"before head",
"in head", "in head noscript",
"after head", "in body", "in CDATA/RCDATA",
"in table", "in caption", "in column group",
"in table body",
"in row", "in cell", "in select", "in select in
table", "in
foreign content", "after body", "in frameset", "after frameset", "after after body", and "after after
frameset" during the course of the parsing, as described in
the tree construction stage. The insertion mode affects
how tokens are processed and whether CDATA sections are
supported.
Seven of these modes, namely "in head", "in
body", "in
CDATA/RCDATA", "in
table", "in table
body", "in row",
"in cell", and "in select", are special, in
that the other modes defer to them at various times. When the
algorithm below says that the user agent is to do something
"using the rules for the m insertion
mode", where m is one of these modes, the user
agent must use the rules described under the m
insertion mode's section, but must leave the
insertion mode unchanged unless the rules in m themselves switch the insertion mode
to a new value.
When the insertion mode is switched to "in CDATA/RCDATA", the original
insertion mode is also set. This is the insertion mode to
which the tree construction stage will return when the corresponding
end tag is parsed.
When the insertion mode is switched to "in foreign content", the
secondary insertion mode is also set. This secondary mode
is used within the rules for the "in foreign content" mode to handle HTML
(i.e. not foreign) content.挿入モードが「in foreign content」
に切り替えられる時には、二次挿入モードも設定されます。
この二次モードは、「in foreign content」
モードの規則の中で HTML の (つまり、異言語でない) 内容を取り扱う際に使用します。
When the steps below require the UA to reset the insertion
mode appropriately, it means the UA must follow these
steps:
Let last be false.last を、偽とします。
Let node be the last node in the
stack of open elements.node を、開いている要素のスタックの最後の節点とします。
If node is the first node in the stack of
open elements, then set last to true and set
node to the context
element. (fragment case)node が開いている要素のスタックの最初の節点の場合、
last を真に設定し、 node を context 要素に設定します。
(素片の場合)
If node is a select element,
then switch the insertion mode to "in select" and abort these
steps. (fragment case)
If node is a td or
th element and last is false, then
switch the insertion mode to "in cell" and abort these steps.
If node is a tr element, then
switch the insertion mode to "in row" and abort these steps.
If node is a tbody,
thead, or tfoot element, then switch the
insertion mode to "in table body" and abort these steps.
If node is a caption element,
then switch the insertion mode to "in caption" and abort
these steps.
If node is a colgroup element,
then switch the insertion mode to "in column group" and
abort these steps. (fragment case)
If node is a table element,
then switch the insertion mode to "in table" and abort these
steps.
If node is an element from the MathML
namespace,
then switch the insertion mode to "in foreign
content", let the secondary insertion mode be
"in body", and abort
these steps.
If node is a head element,
then switch the insertion mode to "in body" ("in body"! not "in head"!) and abort
these steps. (fragment case)
If node is a body element,
then switch the insertion mode to "in body" and abort these
steps.
If node is a frameset element,
then switch the insertion mode to "in frameset" and abort
these steps. (fragment case)
If node is an html element,
then: if the head element
pointer is null, switch the insertion mode to
"before head",
otherwise, switch the insertion mode to "after head". In either
case, abort these steps. (fragment case)
If last is true, then switch the
insertion mode to "in body" and abort these steps. (fragment
case)
Let node now be the node before node in the stack of open
elements.新たな node を開いている要素のスタックで node の前にある節点とします。
Return to step 3.手順 3 に戻ります。
8.2.3.2 The stack of open elements
Initially the stack of open elements is empty. The
stack grows downwards; the topmost node on the stack is the first
one added to the stack, and the bottommost node of the stack is the
most recently added node in the stack (notwithstanding when the
stack is manipulated in a random access fashion as part of the handling for misnested tags).
The "before
html" insertion mode creates the
html root element node, which is then added to the
stack.
In the fragment case, the stack of open
elements is initialized to contain an html
element that is created as part of that algorithm. (The fragment
case skips the "before html" insertion mode.)
The html node, however it is created, is the topmost
node of the stack. It never gets popped off the stack.
The current node is the bottommost node in this
stack.
The current table is the last table
element in the stack of open elements, if there is
one. If there is no table element in the stack of
open elements (fragment case), then the
current table is the first element in the stack
of open elements (the html element).
Elements in the stack fall into the following categories:
- Special特殊
The following HTML elements have varying levels of special
parsing rules: address, area,
article, aside, base,
basefont, bgsound,
blockquote, body, br,
center, col, colgroup,
command, datagrid, dd,
details, dialog, dir,
div, dl, dt,
embed, eventsource fieldset,
figure, footer, form,
frame, frameset, h1,
h2, h3, h4, h5,
h6, head, header,
hr, iframe, img,
input, isindex, li,
link, listing, menu,
meta, nav, noembed,
noframes, noscript, ol,
p, param, plaintext,
pre, script, section,
select, spacer, style,
tbody, textarea, tfoot,
thead, title, tr,
ul, and wbr.
- Scoping
The following HTML elements introduce new scopes for various parts of the
parsing: applet, button,
caption, html, marquee,
object, table, td,
th.
- Formatting
The following HTML elements are those that end up in the
list of active formatting elements: a,
b, big, code,
em, font, i,
nobr, s, small,
strike, strong, tt, and
u.
- Phrasing
All other elements found while parsing an HTML
document.
The stack of open elements is said to have an element in scope when
the following algorithm terminates in a match state:
Initialize node to be the current
node (the bottommost node of the stack).
If node is the target node, terminate in
a match state.
Otherwise, if node is one of the
following elements, terminate in a failure state:
applet in the HTML namespace
caption in the HTML namespace
html in the HTML namespace
table in the HTML namespace
td in the HTML namespace
th in the HTML namespace
button in the HTML namespace
marquee in the HTML namespace
object in the HTML namespace
Otherwise, set node to the previous
entry in the stack of open elements and return to step
2. (This will never fail, since the loop will always terminate in
the previous step if the top of the stack — an
html element — is reached.)
The stack of open elements is said to have an element in table
scope when the following algorithm terminates in a match
state:
Initialize node to be the current
node (the bottommost node of the stack).
If node is the target node, terminate in
a match state.
Otherwise, if node is one of the
following elements, terminate in a failure state:
Otherwise, set node to the previous
entry in the stack of open elements and return to step
2. (This will never fail, since the loop will always terminate in
the previous step if the top of the stack — an
html element — is reached.)
Nothing happens if at any time any of the elements in the
stack of open elements are moved to a new location in,
or removed from, the Document tree. In particular, the
stack is not changed in this situation. This can cause, amongst
other strange effects, content to be appended to nodes that are no
longer in the DOM.
In some cases (namely, when closing misnested formatting elements),
the stack is manipulated in a random-access fashion.
Initially the list of active formatting elements is
empty. It is used to handle mis-nested formatting element tags.
The list contains elements in the formatting
category, and scope markers. The scope markers are inserted when
entering applet elements, buttons, object
elements, marquees, table cells, and table captions, and are used to
prevent formatting from "leaking" into applet elements,
buttons, object elements, marquees, and tables.
When the steps below require the UA to reconstruct the
active formatting elements, the UA must perform the following
steps:
If there are no entries in the list of active formatting
elements, then there is nothing to reconstruct; stop this
algorithm.
If the last (most recently added) entry in the list of
active formatting elements is a marker, or if it is an
element that is in the stack of open elements, then
there is nothing to reconstruct; stop this algorithm.
Let entry be the last (most recently added)
element in the list of active formatting
elements.
If there are no entries before entry in the
list of active formatting elements, then jump to step
8.
Let entry be the entry one earlier than
entry in the list of active formatting
elements.
If entry is neither a marker nor an element
that is also in the stack of open elements, go to step
4.
Let entry be the element one later than
entry in the list of active formatting
elements.
Perform a shallow clone of the element entry to
obtain clone. [DOM3CORE]
Append clone to the current
node and push it onto the stack of open
elements so that it is the new current
node.
Replace the entry for entry in the list
with an entry for clone.
If the entry for clone in the list of
active formatting elements is not the last entry in the
list, return to step 7.
This has the effect of reopening all the formatting elements that
were opened in the current body, cell, or caption (whichever is
youngest) that haven't been explicitly closed.
The way this specification is written, the
list of active formatting elements always consists of
elements in chronological order with the least recently added
element first and the most recently added element last (except for
while steps 8 to 11 of the above algorithm are being executed, of
course).
When the steps below require the UA to clear the list of
active formatting elements up to the last marker, the UA must
perform the following steps:
Let entry be the last (most recently added)
entry in the list of active formatting elements.
Remove entry from the list of active
formatting elements.
If entry was a marker, then stop the
algorithm at this point. The list has been cleared up to the last
marker.
Go to step 1.段階 1 へ行きます。
8.2.3.4 The element pointers
Initially the head element
pointer and the form element
pointer are both null.
Once a head element has been parsed (whether
implicitly or explicitly) the head
element pointer gets set to point to this node.
The form element pointer
points to the last form element that was opened and
whose end tag has not yet been seen. It is used to make form
controls associate with forms in the face of dramatically bad
markup, for historical reasons.
8.2.3.5 The scripting state8.2.3.5 スクリプティング状態
The scripting flag is set to "enabled" if the
Document with which the parser is associated was
with script when the parser was created, and "disabled"
otherwise.
8.2.4 Tokenization
Implementations must act as if they used the following state
machine to tokenise HTML. The state machine must start in the
data state. Most states consume a single character,
which may have various side-effects, and either switches the state
machine to a new state to reconsume the same character, or
switches it to a new state (to consume the next character), or
repeats the same state (to consume the next character). Some states
have more complicated behavior and can consume several characters
before switching to another state.実装は、次の状態機械を HTML の字句化に用いているかのように作用しなければなりません。
状態機械は、データ状態で開始しなければなりません。
ほとんどの状態は1文字消費しますが、
この時様々な副作用を持っても構わない他、
状態機械が新しい状態に切り替えられて同じ文字を再消費するか、
(次の文字を消費するために) 新しい状態に切り替えられるか、
(次の文字を消費するために) 同じ状態を繰り返すかのいずれかとなります。
より複雑な動作を持っていて、他の状態に切り替える前に複数の文字を消費することがある状態もあります。
The exact behavior of certain states depends on a content
model flag that is set after certain tokens are emitted. The
flag has several states: PCDATA, RCDATA, CDATA, and PLAINTEXT. Initially it must be in the PCDATA
state. In the RCDATA and CDATA states, a further escape
flag is used to control the behavior of the tokeniser. It is
either true or false, and initially must be set to the false
state. The insertion mode and the stack of open
elements also affects tokenization.
The output of the tokenization step is a series of zero or more
of the following tokens: DOCTYPE, start tag, end tag, comment,
character, end-of-file. DOCTYPE tokens have a name, a public
identifier, a system identifier, and a force-quirks
flag. When a DOCTYPE token is created, its name, public
identifier, and system identifier must be marked as missing (which
is a distinct state from the empty string), and the force-quirks
flag must be set to off (its other state is
on). Start and end tag tokens have a tag name, a
self-closing flag, and a list of attributes, each of which
has a name and a value. When a start or end tag token is created,
its self-closing flag must be unset (its other state is that
it be set), and its attributes list must be empty. Comment and
character tokens have data.字句化期の出力は、 DOCTYPE、開始タグ、終了タグ、注釈、文字、ファイル末のいずれかの字句の零個以上の系列です。
DOCTYPE 字句は名前、公開識別子、システム識別子、奇癖強制旗を持ちます。
When a DOCTYPE token is
created, its name, public identifier, and system identifier must be marked
as missing (which is a distinct state from the empty string), and the
force-quirks flag must be set to off (its other state is
on). Start and end tag tokens have a tag name, a self-closing
flag, and a list of attributes, each of which has a name and a value.
When a start or end tag token is created, its self-closing flag
must be unset (its other state is that it be set), and its attributes list
must be empty. Comment and character tokens have data.
When a token is emitted, it must immediately be handled by the
tree construction stage. The tree construction stage
can affect the state of the content model flag, and can
insert additional characters into the stream. (For example, the
script element can result in scripts executing and
using the dynamic markup insertion APIs to insert
characters into the stream being tokenised.)
When a start tag token is emitted with its self-closing
flag set, if the flag is not acknowledged when it is processed by the
tree construction stage, that is a parse error.
When an end tag token is emitted, the content model
flag must be switched to the PCDATA state.
When an end tag token is emitted with attributes, that is a
parse error.
When an end tag token is emitted with its self-closing
flag set, that is a parse error.
Before each step of the tokeniser, the user agent must first
check the parser pause flag. If it is true, then the
tokeniser must abort the processing of any nested invocations of the
tokeniser, yielding control back to the caller. If it is false, then
the user agent may then check to see if either one of the scripts in
the list of scripts that will execute as soon as
possible or the first script in the list of scripts
that will execute asynchronously, has completed
loading. If one has, then it must be executed and removed from its list.
The tokeniser state machine consists of the states defined in the
following subsections.
8.2.4.1 Data state8.2.4.1 Data 状態
Consume the next input character:次入力文字を消費します。
- U+0026 AMPERSAND (&)
- When the content model flag is set to one of the
PCDATA or RCDATA states and the escape flag is
false: switch to the character reference data
state.
- Otherwise: treat it as per the "anything
else" entry below.
- U+002D HYPHEN-MINUS (-)
-
If the content model flag is set to either the
RCDATA state or the CDATA state, and the escape flag
is false, and there are at least three characters before this
one in the input stream, and the last four characters in the
input stream, including this one, are U+003C LESS-THAN SIGN,
U+0021 EXCLAMATION MARK, U+002D HYPHEN-MINUS, and U+002D
HYPHEN-MINUS ("<!--"), then set the escape flag
to true.
In any case, emit the input character as a character
token. Stay in the data state.
- U+003C LESS-THAN SIGN (<)
- When the content model flag is set to the PCDATA
state: switch to the tag open state.
- When the content model flag is set to either the
RCDATA state or the CDATA state and the escape flag
is false: switch to the tag open state.
- Otherwise: treat it as per the "anything else" entry
below.
- U+003E GREATER-THAN SIGN (>)
-
If the content model flag is set to either the
RCDATA state or the CDATA state, and the escape
flag is true, and the last three characters in the input
stream including this one are U+002D HYPHEN-MINUS, U+002D
HYPHEN-MINUS, U+003E GREATER-THAN SIGN ("-->"), set the
escape flag to false.
In any case, emit the input character as a character
token. Stay in the data state.
- EOF
- Emit an end-of-file token.
- Anything elseその他のもの
- Emit the input character as a character token. Stay in the
data state.
8.2.4.2 Character reference data state8.2.4.2 Character reference data 状態
(This cannot happen if the content model flag
is set to the CDATA state.)
Attempt to consume a character reference, with no
additional allowed character.
If nothing is returned, emit a U+0026 AMPERSAND character
token.
Otherwise, emit the character token that was returned.
Finally, switch to the data state.
8.2.4.3 Tag open state8.2.4.3 Tag open 状態
The behavior of this state depends on the content model
flag.
- If the content model flag is set to the RCDATA
or CDATA states
-
Consume the next input character. If it is a
U+002F SOLIDUS (/) character, switch to the close tag open
state. Otherwise, emit a U+003C LESS-THAN SIGN character
token and reconsume the current input character in the
data state.
- If the content model flag is set to the PCDATA
state
-
Consume the next input character:次入力文字を消費します。
- U+0021 EXCLAMATION MARK (!)
- Switch to the markup declaration open state.markup declaration open 状態に切り替えます。
- U+002F SOLIDUS (/)
- Switch to the close tag open state.close tag open 状態に切り替えます。
- U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z
- Create a new start tag token, set its tag name to the
lowercase version of the input character (add 0x0020 to the
character's code point), then switch to the tag name
state. (Don't emit the token yet; further details will
be filled in before it is emitted.)
- U+0061 LATIN SMALL LETTER A through to U+007A LATIN SMALL LETTER Z
- Create a new start tag token, set its tag name to the input
character, then switch to the tag name
state. (Don't emit the token yet; further details will
be filled in before it is emitted.)
- U+003E GREATER-THAN SIGN (>)
- Parse error. Emit a U+003C LESS-THAN SIGN
character token and a U+003E GREATER-THAN SIGN character
token. Switch to the data state.
- U+003F QUESTION MARK (?)
- Parse error. Switch to the bogus
comment state.構文解析誤り。
* 状態に切り替えます。
- Anything elseその他のもの
- Parse error. Emit a U+003C LESS-THAN SIGN
character token and reconsume the current input character in the
data state.
8.2.4.4 Close tag open state8.2.4.4 Close tag open 状態
If the content model flag is set to the RCDATA or
CDATA states but no start tag token has ever been emitted by this
instance of the tokeniser (fragment case), or, if the
content model flag is set to the RCDATA or CDATA states
and the next few characters do not match the tag name of the last
start tag token emitted (compared in an ASCII case
insensitive manner), or if they do but they are not
immediately followed by one of the following characters:
...then emit a U+003C LESS-THAN SIGN character token, a U+002F
SOLIDUS character token, and switch to the data state
to process the next input character.
Otherwise, if the content model flag is set to the
PCDATA state, or if the next few characters do match that tag
name, consume the next input character:
- U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z
- Create a new end tag token, set its tag name to the lowercase
version of the input character (add 0x0020 to the character's
code point), then switch to the tag name
state. (Don't emit the token yet; further details will be
filled in before it is emitted.)
- U+0061 LATIN SMALL LETTER A through to U+007A LATIN SMALL LETTER Z
- Create a new end tag token, set its tag name to the input
character, then switch to the tag name state. (Don't
emit the token yet; further details will be filled in before it
is emitted.)
- U+003E GREATER-THAN SIGN (>)
- Parse error. Switch to the data
state.構文解析誤り。
* 状態に切り替えます。
- EOF
- Parse error. Emit a U+003C LESS-THAN SIGN
character token and a U+002F SOLIDUS character token. Reconsume
the EOF character in the data state.
- Anything elseその他のもの
- Parse error. Switch to the bogus
comment state.構文解析誤り。
* 状態に切り替えます。
8.2.4.5 Tag name state8.2.4.5 Tag name 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Switch to the before attribute name state.before attribute name 状態に切り替えます。
- U+002F SOLIDUS (/)
- Switch to the self-closing start tag state.self-closing start tag 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Emit the current tag token. Switch to the data
state.
- U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z
- Append the lowercase version of the current input character
(add 0x0020 to the character's code point) to the current tag
token's tag name. Stay in the tag name state.
- EOF
- Parse error. Emit the current tag
token. Reconsume the EOF character in the data
state.
- Anything elseその他のもの
- Append the current input character to the current tag token's
tag name. Stay in the tag name state.
8.2.4.6 Before attribute name state8.2.4.6 Before attribute name 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Stay in the before attribute name state.
- U+002F SOLIDUS (/)
- Switch to the self-closing start tag state.self-closing start tag 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Emit the current tag token. Switch to the data
state.
- U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z
- Start a new attribute in the current tag token. Set that
attribute's name to the lowercase version of the current input
character (add 0x0020 to the character's code point), and its
value to the empty string. Switch to the attribute name
state.
- U+0022 QUOTATION MARK (")
- U+0027 APOSTROPHE (')
- U+003D EQUALS SIGN (=)
- Parse error. Treat it as per the "anything else"
entry below.
- EOF
- Parse error. Emit the current tag
token. Reconsume the EOF character in the data
state.
- Anything elseその他のもの
- Start a new attribute in the current tag token. Set that
attribute's name to the current input character, and its value to
the empty string. Switch to the attribute name
state.
8.2.4.7 Attribute name state8.2.4.7 Attribute name 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Switch to the after attribute name state.after attribute name 状態に切り替えます。
- U+002F SOLIDUS (/)
- Switch to the self-closing start tag state.self-closing start tag 状態に切り替えます。
- U+003D EQUALS SIGN (=)
- Switch to the before attribute value state.before attribute value 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Emit the current tag token. Switch to the data
state.
- U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z
- Append the lowercase version of the current input character
(add 0x0020 to the character's code point) to the current
attribute's name. Stay in the attribute name
state.
- U+0022 QUOTATION MARK (")
- U+0027 APOSTROPHE (')
- Parse error. Treat it as per the "anything else"
entry below.
- EOF
- Parse error. Emit the current tag
token. Reconsume the EOF character in the data
state.
- Anything elseその他のもの
- Append the current input character to the current attribute's
name. Stay in the attribute name state.
When the user agent leaves the attribute name state (and before
emitting the tag token, if appropriate), the complete attribute's
name must be compared to the other attributes on the same token;
if there is already an attribute on the token with the exact same
name, then this is a parse error and the new
attribute must be dropped, along with the value that gets
associated with it (if any).
8.2.4.8 After attribute name state8.2.4.8 After attribute name 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Stay in the after attribute name state.
- U+002F SOLIDUS (/)
- Switch to the self-closing start tag state.self-closing start tag 状態に切り替えます。
- U+003D EQUALS SIGN (=)
- Switch to the before attribute value state.before attribute value 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Emit the current tag token. Switch to the data
state.
- U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z
- Start a new attribute in the current tag token. Set that
attribute's name to the lowercase version of the current input character
(add 0x0020 to the character's code point), and its value to
the empty string. Switch to the attribute name
state.
- U+0022 QUOTATION MARK (")
- U+0027 APOSTROPHE (')
- Parse error. Treat it as per the "anything else"
entry below.
- EOF
- Parse error. Emit the current tag
token. Reconsume the EOF character in the data
state.
- Anything elseその他のもの
- Start a new attribute in the current tag token. Set that
attribute's name to the current input character, and its value to
the empty string. Switch to the attribute name
state.
8.2.4.9 Before attribute value state8.2.4.9 Before attribute value 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Stay in the before attribute value state.
- U+0022 QUOTATION MARK (")
- Switch to the attribute value (double-quoted) state.attribute value (double-quoted) 状態に切り替えます。
- U+0026 AMPERSAND (&)
- Switch to the attribute value (unquoted) state
and reconsume this input character.
- U+0027 APOSTROPHE (')
- Switch to the attribute value (single-quoted) state.attribute value (single-quoted) 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Parse error. Emit the current tag token. Switch to
the data state.
- U+003D EQUALS SIGN (=)
- Parse error. Treat it as per the "anything else"
entry below.
- EOF
- Parse error. Emit the current tag
token. Reconsume the character in the data
state.
- Anything elseその他のもの
- Append the current input character to the current attribute's
value. Switch to the attribute value (unquoted)
state.
8.2.4.10 Attribute value (double-quoted) state8.2.4.10 Attribute value (double-quoted) 状態
Consume the next input character:次入力文字を消費します。
- U+0022 QUOTATION MARK (")
- Switch to the after attribute value (quoted)
state.after attribute value (quoted) 状態に切り替えます。
- U+0026 AMPERSAND (&)
- Switch to the character reference in attribute value
state, with the additional allowed character
being U+0022 QUOTATION MARK (").
- EOF
- Parse error. Emit the current tag
token. Reconsume the character in the data
state.
- Anything elseその他のもの
- Append the current input character to the current attribute's
value. Stay in the attribute value (double-quoted)
state.
8.2.4.11 Attribute value (single-quoted) state8.2.4.11 Attribute value (single-quoted) 状態
Consume the next input character:次入力文字を消費します。
- U+0027 APOSTROPHE (')
- Switch to the after attribute value (quoted)
state.after attribute value (quoted) 状態に切り替えます。
- U+0026 AMPERSAND (&)
- Switch to the character reference in attribute value
state, with the additional allowed character
being U+0027 APOSTROPHE (').
- EOF
- Parse error. Emit the current tag
token. Reconsume the character in the data
state.
- Anything elseその他のもの
- Append the current input character to the current attribute's
value. Stay in the attribute value (single-quoted)
state.
8.2.4.12 Attribute value (unquoted) state8.2.4.12 Attribute value (unquoted) 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Switch to the before attribute name state.before attribute name 状態に切り替えます。
- U+0026 AMPERSAND (&)
- Switch to the character reference in attribute value
state, with no additional allowed
character.
- U+003E GREATER-THAN SIGN (>)
- Emit the current tag token. Switch to the data
state.
- U+0022 QUOTATION MARK (")
- U+0027 APOSTROPHE (')
- U+003D EQUALS SIGN (=)
- Parse error. Treat it as per the "anything else"
entry below.
- EOF
- Parse error. Emit the current tag
token. Reconsume the character in the data
state.
- Anything elseその他のもの
- Append the current input character to the current attribute's
value. Stay in the attribute value (unquoted)
state.
8.2.4.13 Character reference in attribute value state8.2.4.13 Character reference in attribute value 状態
Attempt to consume a character reference.文字参照を消費しようと試みます。
If nothing is returned, append a U+0026 AMPERSAND character to
the current attribute's value.何も返されなかった場合、 U+0026 AMPERSAND 文字を現在の属性の値の末尾に追加します。
Otherwise, append the returned character token to the current
attribute's value.そうでない場合、返された文字字句を現在の属性の値の末尾に追加します。
Finally, switch back to the attribute value state that you were
in when were switched into this state.最後に、この状態に切り替わる時の attribute value 状態に切り替え戻します。
8.2.4.14 After attribute value (quoted) state8.2.4.14 After attribute value (quoted) 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Switch to the before attribute name state.before attribute name 状態に切り替えます。
- U+002F SOLIDUS (/)
- Switch to the self-closing start tag state.self-closing start tag 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Emit the current tag token. Switch to the data
state.
- EOF
- Parse error. Emit the current tag
token. Reconsume the EOF character in the data
state.
- Anything elseその他のもの
- Parse error. Reconsume the character in
the before attribute name state.構文解析誤り。
文字を * 状態で再消費します。
8.2.4.15 Self-closing start tag state8.2.4.15 Self-closing start tag 状態
Consume the next input character:次入力文字を消費します。
- U+003E GREATER-THAN SIGN (>)
- Set the self-closing flag of the current tag
token. Emit the current tag token. Switch to the data
state.
- EOF
- Parse error. Emit the current tag
token. Reconsume the EOF character in the data
state.
- Anything elseその他のもの
- Parse error. Reconsume the character in
the before attribute name state.構文解析誤り。
文字を * 状態で再消費します。
(This can only happen if the content model
flag is set to the PCDATA state.)
Consume every character up to and including the first U+003E
GREATER-THAN SIGN character (>) or the end of the file (EOF),
whichever comes first. Emit a comment token whose data is the
concatenation of all the characters starting from and including
the character that caused the state machine to switch into the
bogus comment state, up to and including the character immediately
before the last consumed character (i.e. up to the character just
before the U+003E or EOF character). (If the comment was started
by the end of the file (EOF), the token is empty.)
Switch to the data state.data 状態に切り替えます。
If the end of the file was reached, reconsume the EOF
character.
8.2.4.17 Markup declaration open state8.2.4.17 Markup declaration open 状態
(This can only happen if the content model
flag is set to the PCDATA state.)
If the next two characters are both U+002D HYPHEN-MINUS (-)
characters, consume those two characters, create a comment token
whose data is the empty string, and switch to the comment
start state.
Otherwise, if the next seven characters are an ASCII
case-insensitive match for the word "DOCTYPE", then consume
those characters and switch to the DOCTYPE state.
Otherwise, if the insertion mode is "in foreign
content" and the current node is not an element
in the HTML namespace and the next seven characters are
an ASCII case-sensitive match for the string "[CDATA["
(the five uppercase letters "CDATA" with a U+005B LEFT SQUARE
BRACKET character before and after), then consume those characters
and switch to the CDATA section state (which is
unrelated to the content model flag's CDATA state).
Otherwise, this is a parse error. Switch to the
bogus comment state. The next character that is
consumed, if any, is the first character that will be in the
comment.
Consume the next input character:次入力文字を消費します。
- U+002D HYPHEN-MINUS (-)
- Switch to the comment start dash state.comment start dash 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Parse error. Emit the comment token. Switch to
the data state.
- EOF
- Parse error. Emit the comment token. Reconsume
the EOF character in the data state.
- Anything elseその他のもの
- Append the input character to the comment token's
data. Switch to the comment state.
Consume the next input character:次入力文字を消費します。
- U+002D HYPHEN-MINUS (-)
- Switch to the comment end state
- U+003E GREATER-THAN SIGN (>)
- Parse error. Emit the comment token. Switch to
the data state.
- EOF
- Parse error. Emit the comment token. Reconsume
the EOF character in the data state.
- Anything elseその他のもの
- Append a U+002D HYPHEN-MINUS (-) character and the input
character to the comment token's data. Switch to the
comment state.
Consume the next input character:次入力文字を消費します。
- U+002D HYPHEN-MINUS (-)
- Switch to the comment end dash state
- EOF
- Parse error. Emit the comment token. Reconsume
the EOF character in the data state.
- Anything elseその他のもの
- Append the input character to the comment token's data. Stay
in the comment state.
Consume the next input character:次入力文字を消費します。
- U+002D HYPHEN-MINUS (-)
- Switch to the comment end state
- EOF
- Parse error. Emit the comment token. Reconsume
the EOF character in the data state.
- Anything elseその他のもの
- Append a U+002D HYPHEN-MINUS (-) character and the input
character to the comment token's data. Switch to the
comment state.
Consume the next input character:次入力文字を消費します。
- U+003E GREATER-THAN SIGN (>)
- Emit the comment token. Switch to the data
state.
- U+002D HYPHEN-MINUS (-)
- Parse error. Append a U+002D HYPHEN-MINUS
(-) character to the comment token's data. Stay in the
comment end state.
- EOF
- Parse error. Emit the comment token. Reconsume
the EOF character in the data state.
- Anything elseその他のもの
- Parse error. Append two U+002D HYPHEN-MINUS (-)
characters and the input character to the comment token's
data. Switch to the comment state.
8.2.4.23 DOCTYPE state8.2.4.23 DOCTYPE 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Switch to the before DOCTYPE name state.before DOCTYPE name 状態に切り替えます。
- Anything elseその他のもの
- Parse error. Reconsume the current
character in the before DOCTYPE name state.
8.2.4.24 Before DOCTYPE name state8.2.4.24 Before DOCTYPE name 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Stay in the before DOCTYPE name state.
- U+003E GREATER-THAN SIGN (>)
- Parse error. Create a new DOCTYPE token. Set its
force-quirks flag to on. Emit the token. Switch to
the data state.
- U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z
- Create a new DOCTYPE token. Set the token's name to the
lowercase version of the input character (add 0x0020 to the
character's code point). Switch to the DOCTYPE name
state.
- EOF
- Parse error. Create a new DOCTYPE token. Set its
force-quirks flag to on. Emit the token. Reconsume
the EOF character in the data state.
- Anything elseその他のもの
- Create a new DOCTYPE token. Set the token's name to the
current input character. Switch to the DOCTYPE name
state.
8.2.4.25 DOCTYPE name state8.2.4.25 DOCTYPE name 状態
First, consume the next input character:
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Switch to the after DOCTYPE name state.after DOCTYPE name 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Emit the current DOCTYPE token. Switch to the data
state.
- U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z
- Append the lowercase version of the input character (add 0x0020
to the character's code point) to the current DOCTYPE token's
name. Stay in the DOCTYPE name state.
- EOF
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE token.
Reconsume the EOF character in the data state.
- Anything elseその他のもの
- Append the current input character to the current DOCTYPE
token's name. Stay in the DOCTYPE name state.
8.2.4.26 After DOCTYPE name state8.2.4.26 After DOCTYPE name 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Stay in the after DOCTYPE name state.
- U+003E GREATER-THAN SIGN (>)
- Emit the current DOCTYPE token. Switch to the data
state.
- EOF
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE token.
Reconsume the EOF character in the data state.
- Anything elseその他のもの
-
If the next six characters are an ASCII
case-insensitive match for the word "PUBLIC", then consume
those characters and switch to the before DOCTYPE public
identifier state.
Otherwise, if the next six characters are an ASCII
case-insensitive match for the word "SYSTEM", then consume
those characters and switch to the before DOCTYPE system
identifier state.
Otherwise, this is the parse error. Set the
DOCTYPE token's force-quirks flag to on. Switch to
the bogus DOCTYPE state.
8.2.4.27 Before DOCTYPE public identifier state8.2.4.27 Before DOCTYPE public identifier 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Stay in the before DOCTYPE public identifier state.
- U+0022 QUOTATION MARK (")
- Set the DOCTYPE token's public identifier to the empty string
(not missing), then switch to the DOCTYPE public identifier
(double-quoted) state.
- U+0027 APOSTROPHE (')
- Set the DOCTYPE token's public identifier to the empty string
(not missing), then switch to the DOCTYPE public identifier
(single-quoted) state.
- U+003E GREATER-THAN SIGN (>)
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE
token. Switch to the data state.
- EOF
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE token.
Reconsume the EOF character in the data state.
- Anything elseその他のもの
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Switch to the bogus
DOCTYPE state.
8.2.4.28 DOCTYPE public identifier (double-quoted) state8.2.4.28 DOCTYPE public identifier (double-quoted) 状態
Consume the next input character:次入力文字を消費します。
- U+0022 QUOTATION MARK (")
- Switch to the after DOCTYPE public identifier state.after DOCTYPE public identifier 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE
token. Switch to the data state.
- EOF
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE token.
Reconsume the EOF character in the data state.
- Anything elseその他のもの
- Append the current input character to the current DOCTYPE
token's public identifier. Stay in the DOCTYPE public
identifier (double-quoted) state.
8.2.4.29 DOCTYPE public identifier (single-quoted) state8.2.4.29 DOCTYPE public identifier (single-quoted) 状態
Consume the next input character:次入力文字を消費します。
- U+0027 APOSTROPHE (')
- Switch to the after DOCTYPE public identifier state.after DOCTYPE public identifier 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE
token. Switch to the data state.
- EOF
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE token.
Reconsume the EOF character in the data state.
- Anything elseその他のもの
- Append the current input character to the current DOCTYPE
token's public identifier. Stay in the DOCTYPE public
identifier (single-quoted) state.
8.2.4.30 After DOCTYPE public identifier state8.2.4.30 After DOCTYPE public identifier 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Stay in the after DOCTYPE public identifier state.
- U+0022 QUOTATION MARK (")
- Set the DOCTYPE token's system identifier to the empty string
(not missing), then switch to the DOCTYPE system identifier
(double-quoted) state.
- U+0027 APOSTROPHE (')
- Set the DOCTYPE token's system identifier to the empty string
(not missing), then switch to the DOCTYPE system identifier
(single-quoted) state.
- U+003E GREATER-THAN SIGN (>)
- Emit the current DOCTYPE token. Switch to the data
state.
- EOF
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE token.
Reconsume the EOF character in the data state.
- Anything elseその他のもの
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Switch to the bogus
DOCTYPE state.
8.2.4.31 Before DOCTYPE system identifier state8.2.4.31 Before DOCTYPE system identifier 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Stay in the before DOCTYPE system identifier state.
- U+0022 QUOTATION MARK (")
- Set the DOCTYPE token's system identifier to the empty string
(not missing), then switch to the DOCTYPE system identifier
(double-quoted) state.
- U+0027 APOSTROPHE (')
- Set the DOCTYPE token's system identifier to the empty string
(not missing), then switch to the DOCTYPE system identifier
(single-quoted) state.
- U+003E GREATER-THAN SIGN (>)
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE
token. Switch to the data state.
- EOF
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE token.
Reconsume the EOF character in the data state.
- Anything elseその他のもの
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Switch to the bogus
DOCTYPE state.
8.2.4.32 DOCTYPE system identifier (double-quoted) state8.2.4.32 DOCTYPE system identifier (double-quoted) 状態
Consume the next input character:次入力文字を消費します。
- U+0022 QUOTATION MARK (")
- Switch to the after DOCTYPE system identifier state.after DOCTYPE system identifier 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE
token. Switch to the data state.
- EOF
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE token.
Reconsume the EOF character in the data state.
- Anything elseその他のもの
- Append the current input character to the current DOCTYPE
token's system identifier. Stay in the DOCTYPE system
identifier (double-quoted) state.
8.2.4.33 DOCTYPE system identifier (single-quoted) state8.2.4.33 DOCTYPE system identifier (single-quoted) 状態
Consume the next input character:次入力文字を消費します。
- U+0027 APOSTROPHE (')
- Switch to the after DOCTYPE system identifier state.after DOCTYPE system identifier 状態に切り替えます。
- U+003E GREATER-THAN SIGN (>)
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE
token. Switch to the data state.
- EOF
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE token.
Reconsume the EOF character in the data state.
- Anything elseその他のもの
- Append the current input character to the current DOCTYPE
token's system identifier. Stay in the DOCTYPE system
identifier (single-quoted) state.
8.2.4.34 After DOCTYPE system identifier state8.2.4.34 After DOCTYPE system identifier 状態
Consume the next input character:次入力文字を消費します。
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- Stay in the after DOCTYPE system identifier state.
- U+003E GREATER-THAN SIGN (>)
- Emit the current DOCTYPE token. Switch to the data
state.
- EOF
- Parse error. Set the DOCTYPE token's
force-quirks flag to on. Emit that DOCTYPE token.
Reconsume the EOF character in the data state.
- Anything elseその他のもの
- Parse error. Switch to the bogus DOCTYPE
state. (This does not set the DOCTYPE token's
force-quirks flag to on.)
8.2.4.35 Bogus DOCTYPE state8.2.4.35 Bogus DOCTYPE 状態
Consume the next input character:次入力文字を消費します。
- U+003E GREATER-THAN SIGN (>)
- Emit the DOCTYPE token. Switch to the data
state.
- EOF
- Emit the DOCTYPE token. Reconsume the EOF character in the
data state.
- Anything elseその他のもの
- Stay in the bogus DOCTYPE state.
8.2.4.36 CDATA section state8.2.4.36 CDATA section 状態
(This can only happen if the content model
flag is set to the PCDATA state, and is unrelated to the
content model flag's CDATA state.)
Consume every character up to the next occurrence of the three
character sequence U+005D RIGHT SQUARE BRACKET U+005D RIGHT SQUARE
BRACKET U+003E GREATER-THAN SIGN (]]>), or
the end of the file (EOF), whichever comes first. Emit a series of
text tokens consisting of all the characters consumed except the
matching three character sequence at the end (if one was found
before the end of the file).
Switch to the data state.data 状態に切り替えます。
If the end of the file was reached, reconsume the EOF
character.
8.2.4.37 Tokenizing character references
This section defines how to consume a character
reference. This definition is used when parsing character
references in
text and in attributes.
The behavior depends on the identity of the next character (the
one immediately after the U+0026 AMPERSAND character):
- U+0009 CHARACTER TABULATION
- U+000A LINE FEED (LF)
- U+000C FORM FEED (FF)
- U+0020 SPACE
- U+003C LESS-THAN SIGN
- U+0026 AMPERSAND
- EOF
- The additional allowed character, if there is one
- Not a character reference. No characters are consumed, and
nothing is returned. (This is not an error, either.)
- U+0023 NUMBER SIGN (#)
-
Consume the U+0023 NUMBER SIGN.U+0023 NUMBER SIGN を消費します。
The behavior further depends on the character after the U+0023
NUMBER SIGN:動作は更に U+0023 NUMBER
SIGN の次の文字によって決まります。
- U+0078 LATIN SMALL LETTER X
- U+0058 LATIN CAPITAL LETTER X
-
Consume the X.X を消費します。
Follow the steps below, but using the range of characters
U+0030 DIGIT ZERO through to U+0039 DIGIT NINE, U+0061 LATIN
SMALL LETTER A through to U+0066 LATIN SMALL LETTER F, and
U+0041 LATIN CAPITAL LETTER A, through to U+0046 LATIN CAPITAL
LETTER F (in other words, 0-9, A-F, a-f).次の段階に従いますが、文字の範囲 U+0030
DIGIT ZERO ～ U+0039 DIGIT NINE、U+0061 LATIN SMALL LETTER A
～ U+0066 LATIN SMALL LETTER F、 U+0041 LATIN CAPITAL
LETTER A ～ U+0046 LATIN CAPITAL LETTER F (つまり
0-9、A-F、a-f) を使います。
When it comes to interpreting the number, interpret it as a
hexadecimal number.数を解釈する折には、十六進数として解釈します。
- Anything elseその他のもの
-
Follow the steps below, but using the range of characters
U+0030 DIGIT ZERO through to U+0039 DIGIT NINE (i.e. just
0-9).次の段階に従いますが、文字の範囲 U+0030
DIGIT ZERO ～ U+0039 DIGIT NINE (つまり 0-9 だけ) を使います。
When it comes to interpreting the number, interpret it as a
decimal number.数を解釈する折には、十進数として解釈します。
Consume as many characters as match the range of characters
given above.前述の文字の範囲に一致する文字を、一致するだけすべて消費します。
If no characters match the range, then don't consume any
characters (and unconsume the U+0023 NUMBER SIGN character and, if
appropriate, the X character). This is a parse
error; nothing is returned.
Otherwise, if the next character is a U+003B SEMICOLON, consume
that too. If it isn't, there is a parse
error.
If one or more characters match the range, then take them all
and interpret the string of characters as a number (either
hexadecimal or decimal as appropriate).1文字以上が一致した場合は、それらすべてによる文字列を数 (十六進数または十進数の適切な方)
として解釈します。
If that number is one of the numbers in the first column of the
following table, then this is a parse error. Find the
row with that number in the first column, and return a character
token for the Unicode character given in the second column of that
row.
| Number 数 | Unicode character
Unicode 文字 |
|---|
| 0x0D | U+000A | LINE FEED (LF)
|
| 0x80 | U+20AC | EURO SIGN ('€')
|
| 0x81 | U+FFFD | REPLACEMENT CHARACTER
|
| 0x82 | U+201A | SINGLE LOW-9 QUOTATION MARK ('‚')
|
| 0x83 | U+0192 | LATIN SMALL LETTER F WITH HOOK ('ƒ')
|
| 0x84 | U+201E | DOUBLE LOW-9 QUOTATION MARK ('„')
|
| 0x85 | U+2026 | HORIZONTAL ELLIPSIS ('…')
|
| 0x86 | U+2020 | DAGGER ('†')
|
| 0x87 | U+2021 | DOUBLE DAGGER ('‡')
|
| 0x88 | U+02C6 | MODIFIER LETTER CIRCUMFLEX ACCENT ('ˆ')
|
| 0x89 | U+2030 | PER MILLE SIGN ('‰')
|
| 0x8A | U+0160 | LATIN CAPITAL LETTER S WITH CARON ('Š')
|
| 0x8B | U+2039 | SINGLE LEFT-POINTING ANGLE QUOTATION MARK ('‹')
|
| 0x8C | U+0152 | LATIN CAPITAL LIGATURE OE ('Œ')
|
| 0x8D | U+FFFD | REPLACEMENT CHARACTER
|
| 0x8E | U+017D | LATIN CAPITAL LETTER Z WITH CARON ('Ž')
|
| 0x8F | U+FFFD | REPLACEMENT CHARACTER
|
| 0x90 | U+FFFD | REPLACEMENT CHARACTER
|
| 0x91 | U+2018 | LEFT SINGLE QUOTATION MARK ('‘')
|
| 0x92 | U+2019 | RIGHT SINGLE QUOTATION MARK ('’')
|
| 0x93 | U+201C | LEFT DOUBLE QUOTATION MARK ('“')
|
| 0x94 | U+201D | RIGHT DOUBLE QUOTATION MARK ('”')
|
| 0x95 | U+2022 | BULLET ('•')
|
| 0x96 | U+2013 | EN DASH ('–')
|
| 0x97 | U+2014 | EM DASH ('—')
|
| 0x98 | U+02DC | SMALL TILDE ('˜')
|
| 0x99 | U+2122 | TRADE MARK SIGN ('™')
|
| 0x9A | U+0161 | LATIN SMALL LETTER S WITH CARON ('š')
|
| 0x9B | U+203A | SINGLE RIGHT-POINTING ANGLE QUOTATION MARK ('›')
|
| 0x9C | U+0153 | LATIN SMALL LIGATURE OE ('œ')
|
| 0x9D | U+FFFD | REPLACEMENT CHARACTER
|
| 0x9E | U+017E | LATIN SMALL LETTER Z WITH CARON ('ž')
|
| 0x9F | U+0178 | LATIN CAPITAL LETTER Y WITH DIAERESIS ('Ÿ')
|
Otherwise, if the number is in the range 0x0000 to 0x0008, U+000B, U+000E to
0x001F, 0x007F to 0x009F, 0xD800 to 0xDFFF , 0xFDD0 to 0xFDDF, or is one of 0xFFFE,
0xFFFF, 0x1FFFE, 0x1FFFF, 0x2FFFE, 0x2FFFF, 0x3FFFE, 0x3FFFF,
0x4FFFE, 0x4FFFF, 0x5FFFE, 0x5FFFF, 0x6FFFE, 0x6FFFF, 0x7FFFE,
0x7FFFF, 0x8FFFE, 0x8FFFF, 0x9FFFE, 0x9FFFF, 0xAFFFE, 0xAFFFF,
0xBFFFE, 0xBFFFF, 0xCFFFE, 0xCFFFF, 0xDFFFE, 0xDFFFF, 0xEFFFE,
0xEFFFF, 0xFFFFE, 0xFFFFF, 0x10FFFE, or 0x10FFFF, or is higher
than 0x10FFFF, then this is a parse error; return a
character token for the U+FFFD REPLACEMENT CHARACTER character
instead.
Otherwise, return a character token for the Unicode character
whose code point is that number.それ以外の場合、符号位置がその数である Unicode 文字の文字字句を返します。
- Anything elseその他のもの
-
Consume the maximum number of characters possible, with the
consumed characters matching one of the identifiers in the first
column of the named character references table (in a
case-sensitive manner).名前付き文字参照の表の最初の列にある識別子のいずれかと一致するような、
可能な最大数の文字を消費します。
If no match can be made, then this is a parse
error. No characters are consumed, and nothing is
returned.
If the last character matched is not a U+003B SEMICOLON (;), there is a parse error.
If the character reference is being consumed as part of an
attribute, and the last character matched is not a U+003B
SEMICOLON (;), and the next character is in
the range U+0030 DIGIT ZERO to U+0039 DIGIT NINE, U+0041 LATIN
CAPITAL LETTER A to U+005A LATIN CAPITAL LETTER Z, or U+0061 LATIN
SMALL LETTER A to U+007A LATIN SMALL LETTER Z, then, for
historical reasons, all the characters that were matched after the
U+0026 AMPERSAND (&) must be unconsumed, and nothing is
returned.
Otherwise, return a character token for the character
corresponding to the character reference name (as given by the
second column of the named character references
table).
If the markup contains I'm ¬it; I tell
you, the character reference is parsed as "not", as in,
I'm ¬it; I tell you. But if the markup
was I'm ∉ I tell you, the
character reference would be parsed as "notin;", resulting in
I'm ∉ I tell you.
8.2.5 Tree construction
The input to the tree construction stage is a sequence of tokens
from the tokenization stage. The tree construction
stage is associated with a DOM Document object when a
parser is created. The "output" of this stage consists of
dynamically modifying or extending that document's DOM tree.
This specification does not define when an interactive user agent
has to render the Document so that it is available to
the user, or when it has to begin accepting user input.
As each token is emitted from the tokeniser, the user agent must
process the token according to the rules given in the section
corresponding to the current insertion mode.
When the steps below require the UA to insert a
character into a node, if that node has a child immediately
before where the character is to be inserted, and that child is a
Text node, and that Text node was the last
node that the parser inserted into the document, then the character
must be appended to that Text node; otherwise, a new
Text node whose data is just that character must be
inserted in the appropriate place.
DOM mutation events must not fire
for changes caused by the UA parsing the document. (Conceptually,
the parser is not mutating the DOM, it is constructing it.) This
includes the parsing of any content inserted using document.write() and document.writeln() calls. [DOM3EVENTS]
Not all of the tag names mentioned below are
conformant tag names in this specification; many are included to
handle legacy content. They still form part of the algorithm that
implementations are required to implement to claim conformance.
The algorithm described below places no limit on the
depth of the DOM tree generated, or on the length of tag names,
attribute names, attribute values, text nodes, etc. While
implementors are encouraged to avoid arbitrary limits, it is
recognized that practical
concerns will likely force user agents to impose nesting
depths.
8.2.5.1 Creating and inserting elements
When the steps below require the UA to create an element for a token in a
particular namespace, the UA must create a node implementing the
interface appropriate for the element type corresponding to the tag
name of the token in the given namespace (as given in the
specification that defines that element, e.g. for an a
element in the HTML namespace, this specification
defines it to be the HTMLAnchorElement interface), with
the tag name being the name of that element, with the node being in
the given namespace, and with the attributes on the node being those
given in the given token.
The interface appropriate for an element in the HTML
namespace that is not defined in this specification is
HTMLElement. The interface appropriate for an element
in another namespace that is not defined by that namespace's
specification is Element.
When a resettable element is
created in this manner, its reset algorithm must be
invoked once the attributes are set. (This initializes the element's
value and checkedness based on the element's
attributes.)
When the steps below require the UA to insert an HTML
element for a token, the UA must first create an element
for the token in the HTML namespace, and then
append this node to the current node, and push it onto
the stack of open elements so that it is the new
current node.
The steps below may also require that the UA insert an HTML
element in a particular place, in which case the UA must follow the
same steps except that it must insert or append the new node in the
location specified instead of appending it to the current
node. (This happens in particular during the parsing of
tables with invalid content.)
If an element created by the insert an HTML element
algorithm is a form-associated element, and the
form element pointer is not null,
and the newly created element doesn't have a form attribute, the user agent must
associate the newly
created element with the form element pointed to by the
form element pointer before
inserting it wherever it is to be inserted.
When the steps below require the UA to insert a foreign
element for a token, the UA must first create an element
for the token in the given namespace, and then append this
node to the current node, and push it onto the
stack of open elements so that it is the new
current node. If the newly created element has an xmlns attribute in the XMLNS namespace
whose value is not exactly the same as the element's namespace, that
is a parse error.
When the steps below require the user agent to adjust MathML
attributes for a token, then, if the token has an attribute
named definitionurl, change its name to definitionURL (note the case difference).
When the steps below require the user agent to adjust
foreign attributes for a token, then, if any of the attributes
on the token match the strings given in the first column of the
following table, let the attribute be a namespaced attribute, with
the prefix being the string given in the corresponding cell in the
second column, the local name being the string given in the
corresponding cell in the third column, and the namespace being the
namespace given in the corresponding cell in the fourth
column. (This fixes the use of namespaced attributes, in particular
xml:lang.)
The generic CDATA element parsing algorithm and the
generic RCDATA element parsing algorithm consist of the
following steps. These algorithms are always invoked in response to
a start tag token.
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
If the algorithm that was invoked is the generic CDATA
element parsing algorithm, switch the tokeniser's
content model flag to the CDATA state; otherwise the
algorithm invoked was the generic RCDATA element parsing
algorithm, switch the tokeniser's content model
flag to the RCDATA state.
Let the original insertion mode be the current
insertion mode.
Then, switch the insertion mode to "in
CDATA/RCDATA".
When the steps below require the UA to generate implied end
tags, then, while the current node is a
dd element, a dt element, an
li element, an option element, an
optgroup element, a p element, an
rp element, or an rt element, the UA must
pop the current node off the stack of open
elements.
If a step requires the UA to generate implied end tags but lists
an element to exclude from the process, then the UA must perform the
above steps as if that element was not in the above list.
8.2.5.3 Foster parenting
Foster parenting happens when content is misnested in tables.
When a node node is to be foster parented, the node node
must be inserted into the foster parent element, and the
current table must be marked as
tainted. (Once the current table has been
tainted, whitespace characters are inserted into the
foster parent element instead of the current
node.)
The foster parent element is the parent element of the
last table element in the stack of open
elements, if there is a table element and it has
such a parent element. If there is no table element in
the stack of open elements (fragment
case), then the foster parent element is the first
element in the stack of open elements (the
html element). Otherwise, if there is a
table element in the stack of open
elements, but the last table element in the
stack of open elements has no parent, or its parent
node is not an element, then the foster parent element is
the element before the last table element in the
stack of open elements.
If the foster parent element is the parent element of the
last table element in the stack of open
elements, then node must be inserted
immediately before the last table element in
the stack of open elements in the foster parent
element; otherwise, node must be
appended to the foster parent element.
8.2.5.4 The "initial" insertion mode8.2.5.4 「initial」挿入モード
When the insertion mode is "initial", tokens must be handled as follows:挿入モードが「initial」の時は、字句を次のように処理しなければなりません。
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
-
Ignore the token.字句を無視します。
- A comment token注釈字句
-
Append a Comment node to the Document
object with the data attribute set to the
data given in the comment token.data 属性を注釈字句に与えられたデータに設定した Comment
節点を Document オブジェクトの末尾に追加します。
- A DOCTYPE tokenDOCTYPE 字句
-
If the DOCTYPE token's name is not a
case-sensitive match for the string "html", or if the token's public identifier is
neither missing nor a case-sensitive match for the
string "XSLT-compat", or if the token's system
identifier is not missing, then there is a parse
error (this is the DOCTYPE parse
error). Conformance checkers may, instead of reporting this
error, switch to a conformance checking mode for another language
(e.g. based on the DOCTYPE token a conformance checker could
recognize that the document is an HTML4-era document, and defer to
an HTML4 conformance checker.)
Append a DocumentType node to the
Document node, with the name
attribute set to the name given in the DOCTYPE token; the publicId attribute set to the public identifier
given in the DOCTYPE token, or the empty string if the public
identifier was missing; the systemId
attribute set to the system identifier given in the DOCTYPE token,
or the empty string if the system identifier was missing; and the
other attributes specific to DocumentType objects set
to null and empty lists as appropriate. Associate the
DocumentType node with the Document
object so that it is returned as the value of the doctype attribute of the Document
object.DocumentType 節点を
Document の末尾に追加します。
この時、
name 属性は DOCTYPE 字句に与えられた名前に設定し、
publicId 属性は DOCTYPE 字句に与えられた公開識別子か、
公開識別子が欠けている場合は空文字列に設定し、
systemId 属性は DOCTYPE 字句に与えられたシステム識別子か、
システム識別子が欠けている場合は空文字列に設定し、他の
DocumentType オブジェクトに固有なすべての属性は、
null か空のリストに適切に設定します。
DocumentType 節点を Document
オブジェクトに関連付け、 Document オブジェクトの doctype 属性の値として返されるようにします。
Then, if the DOCTYPE
token matches one of the conditions in the following list, then
set the document to quirks mode:そして、DOCTYPE 字句が次のリストの条件のいずれかに一致する場合、
文書を奇癖モードに設定します。
The force-quirks flag is set to on. 奇癖強制旗が入に設定されている
The name is set to anything other than "HTML". 名前が「HTML」以外に設定されている
The public identifier starts with: "+//Silmaril//dtd html Pro v0r11 19970101//" 公開識別子が「+//Silmaril//dtd html Pro v0r11 19970101//」から始まる
The public identifier starts with: "-//AdvaSoft Ltd//DTD HTML 3.0 asWedit + extensions//" 公開識別子が「-//AdvaSoft Ltd//DTD HTML 3.0 asWedit + extensions//」から始まる
The public identifier starts with: "-//AS//DTD HTML 3.0 asWedit + extensions//" 公開識別子が「-//AS//DTD HTML 3.0 asWedit + extensions//」から始まる
The public identifier starts with: "-//IETF//DTD HTML 2.0 Level 1//" 公開識別子が「-//IETF//DTD HTML 2.0 Level 1//」から始まる
The public identifier starts with: "-//IETF//DTD HTML 2.0 Level 2//" 公開識別子が「-//IETF//DTD HTML 2.0 Level 2//」から始まる
The public identifier starts with: "-//IETF//DTD HTML 2.0 Strict Level 1//" 公開識別子が「-//IETF//DTD HTML 2.0 Strict Level 1//」から始まる
The public identifier starts with: "-//IETF//DTD HTML 2.0 Strict Level 2//" 公開識別子が「-//IETF//DTD HTML 2.0 Strict Level 2//」から始まる
The public identifier starts with: "-//IETF//DTD HTML 2.0 Strict//" 公開識別子が「-//IETF//DTD HTML 2.0 Strict//」から始まる
The public identifier starts with: "-//IETF//DTD HTML 2.0//" 公開識別子が「-//IETF//DTD HTML 2.0//」から始まる
The public identifier starts with: "-//IETF//DTD HTML 2.1E//" 公開識別子が「-//IETF//DTD HTML 2.1E//」から始まる
The public identifier starts with: "-//IETF//DTD HTML 3.0//" 公開識別子が「-//IETF//DTD HTML 3.0//」から始まる
The public identifier starts with: "-//IETF//DTD HTML 3.2 Final//" 公開識別子が「-//IETF//DTD HTML 3.2 Final//」から始まる
The public identifier starts with: "-//IETF//DTD HTML 3.2//" 公開識別子が「-//IETF//DTD HTML 3.2//」から始まる
The public identifier starts with: "-//IETF//DTD HTML 3//" 公開識別子が「-//IETF//DTD HTML 3//」から始まる
The public identifier starts with: "-//IETF//DTD HTML Level 0//" 公開識別子が「-//IETF//DTD HTML Level 0//」から始まる
The public identifier starts with: "-//IETF//DTD HTML Level 1//" 公開識別子が「-//IETF//DTD HTML Level 1//」から始まる
The public identifier starts with: "-//IETF//DTD HTML Level 2//" 公開識別子が「-//IETF//DTD HTML Level 2//」から始まる
The public identifier starts with: "-//IETF//DTD HTML Level 3//" 公開識別子が「-//IETF//DTD HTML Level 3//」から始まる
The public identifier starts with: "-//IETF//DTD HTML Strict Level 0//" 公開識別子が「-//IETF//DTD HTML Strict Level 0//」から始まる
The public identifier starts with: "-//IETF//DTD HTML Strict Level 1//" 公開識別子が「-//IETF//DTD HTML Strict Level 1//」から始まる
The public identifier starts with: "-//IETF//DTD HTML Strict Level 2//" 公開識別子が「-//IETF//DTD HTML Strict Level 2//」から始まる
The public identifier starts with: "-//IETF//DTD HTML Strict Level 3//" 公開識別子が「-//IETF//DTD HTML Strict Level 3//」から始まる
The public identifier starts with: "-//IETF//DTD HTML Strict//" 公開識別子が「-//IETF//DTD HTML Strict//」から始まる
The public identifier starts with: "-//IETF//DTD HTML//" 公開識別子が「-//IETF//DTD HTML//」から始まる
The public identifier starts with: "-//Metrius//DTD Metrius Presentational//" 公開識別子が「-//Metrius//DTD Metrius Presentational//」から始まる
The public identifier starts with: "-//Microsoft//DTD Internet Explorer 2.0 HTML Strict//" 公開識別子が「-//Microsoft//DTD Internet Explorer 2.0 HTML Strict//」から始まる
The public identifier starts with: "-//Microsoft//DTD Internet Explorer 2.0 HTML//" 公開識別子が「-//Microsoft//DTD Internet Explorer 2.0 HTML//」から始まる
The public identifier starts with: "-//Microsoft//DTD Internet Explorer 2.0 Tables//" 公開識別子が「-//Microsoft//DTD Internet Explorer 2.0 Tables//」から始まる
The public identifier starts with: "-//Microsoft//DTD Internet Explorer 3.0 HTML Strict//" 公開識別子が「-//Microsoft//DTD Internet Explorer 3.0 HTML Strict//」から始まる
The public identifier starts with: "-//Microsoft//DTD Internet Explorer 3.0 HTML//" 公開識別子が「-//Microsoft//DTD Internet Explorer 3.0 HTML//」から始まる
The public identifier starts with: "-//Microsoft//DTD Internet Explorer 3.0 Tables//" 公開識別子が「-//Microsoft//DTD Internet Explorer 3.0 Tables//」から始まる
The public identifier starts with: "-//Netscape Comm. Corp.//DTD HTML//" 公開識別子が「-//Netscape Comm. Corp.//DTD HTML//」から始まる
The public identifier starts with: "-//Netscape Comm. Corp.//DTD Strict HTML//" 公開識別子が「-//Netscape Comm. Corp.//DTD Strict HTML//」から始まる
The public identifier starts with: "-//O'Reilly and Associates//DTD HTML 2.0//" 公開識別子が「-//O'Reilly and Associates//DTD HTML 2.0//」から始まる
The public identifier starts with: "-//O'Reilly and Associates//DTD HTML Extended 1.0//" 公開識別子が「-//O'Reilly and Associates//DTD HTML Extended 1.0//」から始まる
The public identifier starts with: "-//O'Reilly and Associates//DTD HTML Extended Relaxed 1.0//" 公開識別子が「-//O'Reilly and Associates//DTD HTML Extended Relaxed 1.0//」から始まる
The public identifier starts with: "-//SoftQuad Software//DTD HoTMetaL PRO 6.0::19990601::extensions to HTML 4.0//" 公開識別子が「-//SoftQuad Software//DTD HoTMetaL PRO 6.0::19990601::extensions to HTML 4.0//」から始まる
The public identifier starts with: "-//SoftQuad//DTD HoTMetaL PRO 4.0::19971010::extensions to HTML 4.0//" 公開識別子が「-//SoftQuad//DTD HoTMetaL PRO 4.0::19971010::extensions to HTML 4.0//」から始まる
The public identifier starts with: "-//Spyglass//DTD HTML 2.0 Extended//" 公開識別子が「-//Spyglass//DTD HTML 2.0 Extended//」から始まる
The public identifier starts with: "-//SQ//DTD HTML 2.0 HoTMetaL + extensions//" 公開識別子が「-//SQ//DTD HTML 2.0 HoTMetaL + extensions//」から始まる
The public identifier starts with: "-//Sun Microsystems Corp.//DTD HotJava HTML//" 公開識別子が「-//Sun Microsystems Corp.//DTD HotJava HTML//」から始まる
The public identifier starts with: "-//Sun Microsystems Corp.//DTD HotJava Strict HTML//" 公開識別子が「-//Sun Microsystems Corp.//DTD HotJava Strict HTML//」から始まる
The public identifier starts with: "-//W3C//DTD HTML 3 1995-03-24//" 公開識別子が「-//W3C//DTD HTML 3 1995-03-24//」から始まる
The public identifier starts with: "-//W3C//DTD HTML 3.2 Draft//" 公開識別子が「-//W3C//DTD HTML 3.2 Draft//」から始まる
The public identifier starts with: "-//W3C//DTD HTML 3.2 Final//" 公開識別子が「-//W3C//DTD HTML 3.2 Final//」から始まる
The public identifier starts with: "-//W3C//DTD HTML 3.2//" 公開識別子が「-//W3C//DTD HTML 3.2//」から始まる
The public identifier starts with: "-//W3C//DTD HTML 3.2S Draft//" 公開識別子が「-//W3C//DTD HTML 3.2S Draft//」から始まる
The public identifier starts with: "-//W3C//DTD HTML 4.0 Frameset//" 公開識別子が「-//W3C//DTD HTML 4.0 Frameset//」から始まる
The public identifier starts with: "-//W3C//DTD HTML 4.0 Transitional//" 公開識別子が「-//W3C//DTD HTML 4.0 Transitional//」から始まる
The public identifier starts with: "-//W3C//DTD HTML Experimental 19960712//" 公開識別子が「-//W3C//DTD HTML Experimental 19960712//」から始まる
The public identifier starts with: "-//W3C//DTD HTML Experimental 970421//" 公開識別子が「-//W3C//DTD HTML Experimental 970421//」から始まる
The public identifier starts with: "-//W3C//DTD W3 HTML//" 公開識別子が「-//W3C//DTD W3 HTML//」から始まる
The public identifier starts with: "-//W3O//DTD W3 HTML 3.0//" 公開識別子が「-//W3O//DTD W3 HTML 3.0//」から始まる
The public identifier is set to: "-//W3O//DTD W3 HTML Strict 3.0//EN//" 公開識別子が「-//W3O//DTD W3 HTML Strict 3.0//EN//」に設定されている
The public identifier starts with: "-//WebTechs//DTD Mozilla HTML 2.0//" 公開識別子が「-//WebTechs//DTD Mozilla HTML 2.0//」から始まる
The public identifier starts with: "-//WebTechs//DTD Mozilla HTML//" 公開識別子が「-//WebTechs//DTD Mozilla HTML//」から始まる
The public identifier is set to: "-/W3C/DTD HTML 4.0 Transitional/EN" 公開識別子が「-/W3C/DTD HTML 4.0 Transitional/EN」に設定されている
The public identifier is set to: "HTML" 公開識別子が「HTML」に設定されている
The system identifier is set to: "http://www.ibm.com/data/dtd/v11/ibmxhtml1-transitional.dtd" システム識別子が「http://www.ibm.com/data/dtd/v11/ibmxhtml1-transitional.dtd」に設定されている
The system identifier is missing and the public identifier starts with: "-//W3C//DTD HTML 4.01 Frameset//" システム識別子が欠けており、公開識別子が「-//W3C//DTD HTML 4.01 Frameset//」から始まる
The system identifier is missing and the public identifier starts with: "-//W3C//DTD HTML 4.01 Transitional//" システム識別子が欠けており、公開識別子が「-//W3C//DTD HTML 4.01 Transitional//」から始まる
Otherwise, if the DOCTYPE
token matches one of the conditions in the following list, then
set the document to limited quirks mode:そうでない場合、 DOCTYPE 字句が次のリストの条件のいずれかに一致する場合、
文書を限定奇癖モードに設定します。
The public identifier starts with: "-//W3C//DTD XHTML 1.0 Frameset//" 公開識別子が「-//W3C//DTD XHTML 1.0 Frameset//」から始まる
The public identifier starts with: "-//W3C//DTD XHTML 1.0 Transitional//" 公開識別子が「-//W3C//DTD XHTML 1.0 Transitional//」から始まる
The system identifier is not missing and the public identifier starts with: "-//W3C//DTD HTML 4.01 Frameset//" システム識別子が欠けておらず、公開識別子が「-//W3C//DTD HTML 4.01 Frameset//」から始まる
The system identifier is not missing and the public identifier starts with: "-//W3C//DTD HTML 4.01 Transitional//" システム識別子が欠けておらず、公開識別子が「-//W3C//DTD HTML 4.01 Transitional//」から始まる
The name, system identifier, and public identifier strings must
be compared to the values given in the lists above in an
ASCII case-insensitive manner. A system identifier
whose value is the empty string is not considered missing for the
purposes of the conditions above.名前、システム識別子、公開識別子の文字列は、以上のリストの値と
ASCII 大文字・小文字不区別な形で比較しなければなりません。
前記の条件に関する限り、システム識別子の値が空文字列の場合は欠けているとはみなしません。
Then, switch the insertion mode to "before html".その後、挿入モードを「before html」
に切り替えます。
- Anything elseその他のもの
-
Parse error.構文解析誤り。
Set the document to quirks mode.文書を奇癖モードに設定します。
Switch the insertion mode to "before html", then
reprocess the current token.挿入モードを「before html」
に切り替えてから、現在の字句を再処理します。
8.2.5.5 The "before html" insertion mode8.2.5.5 「before html」挿入モード
When the insertion mode is "before html", tokens must be handled as follows:挿入モードが「before html」の時は、字句を次のように処理しなければなりません。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A comment token注釈字句
-
Append a Comment node to the Document
object with the data attribute set to the
data given in the comment token.data 属性を注釈字句に与えられたデータに設定した Comment
節点を Document オブジェクトの末尾に追加します。
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
-
Ignore the token.字句を無視します。
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Create an element for the token in the HTML
namespace. Append it to the Document
object. Put this element in the stack of open
elements.
If the token has an attribute "manifest",
then resolve the value of that
attribute to an absolute URL, and if that is
successful, run the application cache
selection algorithm with the resulting absolute
URL. Otherwise, if there is no such attribute or resolving
it fails, run the application cache
selection algorithm with no manifest.
Switch the insertion mode to "before head".
- Anything elseその他のもの
-
Create an HTMLElement node with the tag name
html, in the HTML namespace. Append it
to the Document object. Put this element in the
stack of open elements.
Run the application cache
selection algorithm with no manifest.
Switch the insertion mode to "before head", then
reprocess the current token.挿入モードを「before head」
に切り替えてから、現在の字句を再処理します。
Should probably make end tags be ignored, so
that "</head><!-- --><html>" puts the comment before the
root node (or should we?)
The root element can end up being removed from the
Document object, e.g. by scripts; nothing in particular
happens in such cases, content continues being appended to the nodes
as described in the next section.
8.2.5.6 The "before head" insertion mode8.2.5.6 「before head」挿入モード
When the insertion mode is "before head", tokens must be handled as follows:
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
-
Ignore the token.字句を無視します。
- A comment token注釈字句
-
Append a Comment node to the current
node with the data attribute set to
the data given in the comment token.現在節点の末尾に data
属性を注釈字句で与えられたデータに設定した Comment
節点を追加します。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- A start tag whose tag name is "head"タグ名が "head" の開始タグ
-
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
Set the head element pointer
to the newly created head element.head
要素指示子を新たに作られた head
要素に設定します。
Switch the insertion mode to "in head".
- An end tag whose tag name is one of: "head", "br"タグ名が "head", "br" のいずれかの終了タグ
-
Act as if a start tag token with the tag name "head" and no
attributes had been seen, then reprocess the current token.タグ名 "head" で属性のない開始タグ字句を見たかのように作用した後、
現在の字句を再処理します。
- Any other end tagその他の終了タグ
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- Anything elseその他のもの
-
Act as if a start tag token with the tag name "head" and no
attributes had been seen, then reprocess the current
token.タグ名 "head" で属性のない開始タグ字句を見たかのように作用した後、
現在の字句を再処理します。
This will result in an empty head
element being generated, with the current token being
reprocessed in the "after head" insertion mode.
8.2.5.7 The "in head" insertion mode8.2.5.7 「in head」挿入モード
When the insertion mode is "in head", tokens must be handled as follows:挿入モードが「in head」の時は、字句を次のように処理しなければなりません。
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
-
Insert the character into
the current node.現在節点に文字を挿入します。
- A comment token注釈字句
-
Append a Comment node to the current
node with the data attribute set to
the data given in the comment token.現在節点の末尾に data
属性を注釈字句で与えられたデータに設定した Comment
節点を追加します。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- A start tag whose tag name is one of: "base", "command",
"eventsource", "link"タグ名が "base", "command", "eventsource", "link" のいずれかの開始タグ
-
Insert an HTML element for the token. Immediately
pop the current node off the stack of open
elements.
Acknowledge the
token's self-closing flag, if it is set.
- A start tag whose tag name is "meta"タグ名が "meta" の開始タグ
-
Insert an HTML element for the token. Immediately
pop the current node off the stack of open
elements.
Acknowledge the
token's self-closing flag, if it is set.
If the element has a charset attribute, and its
value is a supported encoding, and the confidence is
currently tentative, then change the
encoding to the encoding given by the value of the
charset attribute.
Otherwise, if the element has a content attribute, and
applying the algorithm for extracting an encoding from a
Content-Type to its value returns a supported encoding
encoding, and the confidence is
currently tentative, then change the
encoding to the encoding encoding.
- A start tag whose tag name is "title"タグ名が "title" の開始タグ
-
Follow the generic RCDATA element parsing algorithm.
- A start tag whose tag name is "noscript", if the scripting flag is enabled
- A start tag whose tag name is one of: "noframes", "style"タグ名が "noframes", "style" のいずれかの開始タグ
-
Follow the generic CDATA element parsing algorithm.
- A start tag whose tag name is "noscript", if the scripting flag is disabled
-
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
Switch the insertion mode to "in head
noscript".
- A start tag whose tag name is "script"タグ名が "script" の開始タグ
-
Create an element for the token in the
HTML namespace.
-
Mark the element as being "parser-inserted".
This ensures that, if the script is external, any
document.write()
calls in the script will execute in-line, instead of blowing the
document away, as would happen in most other cases. It also
prevents the script from executing until the end tag is seen.
If the parser was originally created for the HTML
fragment parsing algorithm, then mark the
script element as "already
executed". (fragment case)
Append the new element to the current
node.
Switch the tokeniser's content model flag to
the CDATA state.
Let the original insertion mode be the current
insertion mode.
Switch the insertion mode to "in
CDATA/RCDATA".
- An end tag whose tag name is "head"タグ名が "head" の終了タグ
-
Pop the current node (which will be the
head element) off the stack of open
elements.
Switch the insertion mode to "after head".
- An end tag whose tag name is "br"タグ名が "br" の終了タグ
-
Act as described in the "anything else" entry below.
- A start tag whose tag name is "head"タグ名が "head" の開始タグ
- Any other end tagその他の終了タグ
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- Anything elseその他のもの
-
Act as if an end tag token with the tag name "head" had
been seen, and reprocess the current token.
In certain UAs, some
elements don't trigger the "in body" mode straight away,
but instead get put into the head. Do we want to copy
that?
8.2.5.8 The "in head noscript" insertion mode8.2.5.8 「in head noscript」挿入モード
When the insertion mode is "in head noscript", tokens must be handled as follows:挿入モードが「in head noscript」の時は、字句を次のように処理しなければなりません。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- An end tag whose tag name is "noscript"タグ名が "noscript" の終了タグ
-
Pop the current node (which will be a
noscript element) from the stack of open
elements; the new current node will be a
head element.
Switch the insertion mode to "in head".
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
- A comment token注釈字句
- A start tag whose tag name is one of: "link", "meta", "noframes", "style"タグ名が "link", "meta", "noframes", "style" のいずれかの開始タグ
-
Process the token using the rules for the "in head" insertion
mode.字句を、「in head」挿入モードの規則を使って処理します。
- An end tag whose tag name is one of: "br"タグ名が "br" のいずれかの終了タグ
-
Act as described in the "anything else" entry below.
- A start tag whose tag name is one of: "head", "noscript"タグ名が "head", "noscript" のいずれかの開始タグ
- Any other end tagその他の終了タグ
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- Anything elseその他のもの
-
Parse error. Act as if an end tag with the tag
name "noscript" had been seen and reprocess the current
token.
8.2.5.9 The "after head" insertion mode8.2.5.9 「after head」挿入モード
When the insertion mode is "after head", tokens must be handled as follows:挿入モードが「after head」の時は、字句を次のように処理しなければなりません。
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
-
Insert the character into
the current node.現在節点に文字を挿入します。
- A comment token注釈字句
-
Append a Comment node to the current
node with the data attribute set to
the data given in the comment token.現在節点の末尾に data
属性を注釈字句で与えられたデータに設定した Comment
節点を追加します。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- A start tag whose tag name is "body"タグ名が "body" の開始タグ
-
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
Switch the insertion mode to "in body".挿入モードを「in body」に切り替えます。
- A start tag whose tag name is "frameset"タグ名が "frameset" の開始タグ
-
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
Switch the insertion mode to "in frameset".挿入モードを「in frameset」に切り替えます。
- A start tag token whose tag name is one of: "base", "link",
"meta", "noframes", "script", "style", "title"タグ名が "base", "link", "meta", "noframes", "script", "style", "title" のいずれかの開始タグ字句
-
Parse error.構文解析誤り。
Push the node pointed to by the head element pointer onto the
stack of open elements.head 要素指示子が指す節点を開いている要素のスタック上に push します。
Process the token using the rules for the "in head" insertion
mode.字句を、「in head」挿入モードの規則を使って処理します。
Remove the node pointed to by the head element pointer from the stack
of open elements.
- A start tag whose tag name is "head"タグ名が "head" の開始タグ
- Any end tag終了タグ
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- Anything elseその他のもの
-
Act as if a start tag token with the tag name "body" and no
attributes had been seen, and then reprocess the current
token.タグ名が "body" で属性がない開始タグ字句があるかのように作用した後、
現在の字句を再処理します。
8.2.5.10 The "in body" insertion mode8.2.5.10 「in body」挿入モード
When the insertion mode is "in body", tokens must be handled as follows:挿入モードが「in body」の時は、字句を次のように処理しなければなりません。
- A character token文字字句
-
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
Insert the token's
character into the current node.現在節点に字句の文字を挿入します。
- A comment token注釈字句
-
Append a Comment node to the current
node with the data attribute set to
the data given in the comment token.現在節点の末尾に data
属性を注釈字句で与えられたデータに設定した Comment
節点を追加します。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Parse error. For each attribute on the token,
check to see if the attribute is already present on the top
element of the stack of open elements. If it is not,
add the attribute and its corresponding value to that element.構文解析誤り。字句の各属性について、
その属性が開いている要素のスタックの最上の要素に既に存在しているか検査します。
存在していない場合、属性とそれに対応する値をその要素に追加します。
- A start tag token whose tag name is one of: "base", "command",
"eventsource", "link", "meta", "noframes", "script", "style",
"title"タグ名が "base", "command", "eventsource", "link", "meta", "noframes", "script", "style", "title" のいずれかの開始タグ字句
-
Process the token using the rules for the "in head" insertion
mode.字句を、「in head」挿入モードの規則を使って処理します。
- A start tag whose tag name is "body"タグ名が "body" の開始タグ
-
Parse error.構文解析誤り。
If the second element on the stack of open
elements is not a body element, or, if the
stack of open elements has only one node on it,
then ignore the token. (fragment case)開いている要素のスタックの2番目の要素が body
要素でない場合や、開いている要素のスタック上に節点が1つだけしかない場合、
字句を無視します。
(素片の場合)
Otherwise, for each attribute on the token, check to see if
the attribute is already present on the body
element (the second element) on the stack of open
elements. If it is not, add the attribute and its
corresponding value to that element.そうでない場合、字句の各属性について、その属性が開いている要素のスタック上の body
要素 (2番目の要素) に既に存在しているか検査します。
存在していない場合、属性とそれに対応する値をその要素に追加します。
- An end-of-file tokenファイル末字句
-
If there is a node in the stack of open elements
that is not either a dd element, a dt
element, an li element, a p element, a
tbody element, a td element, a
tfoot element, a th element, a
thead element, a tr element, the
body element, or the html element, then
this is a parse error.
Stop parsing.構文解析を停止します。
- An end tag whose tag name is "body"タグ名が "body" の終了タグ
-
If the stack of open elements does not have a body element
in scope, this is a parse error; ignore the
token.
Otherwise, if there is a node in the stack of open
elements that is not either a dd element, a
dt element, an li element, a
p element, a tbody element, a
td element, a tfoot element, a
th element, a thead element, a
tr element, the body element, or the
html element, then this is a parse
error.
Switch the insertion mode to "after body".
- An end tag whose tag name is "html"タグ名が "html" の終了タグ
-
Act as if an end tag with tag name "body" had been seen,
then, if that token wasn't ignored, reprocess the current
token.
The fake end tag token here can only be
ignored in the fragment case.
- A start tag whose tag name is one of: "address", "article",
"aside", "blockquote", "center", "datagrid", "details", "dialog",
"dir", "div", "dl", "fieldset", "figure", "footer", "header",
"menu", "nav", "ol", "p", "section", "ul"タグ名が "address", "article", "aside", "blockquote", "center", "datagrid", "details", "dialog", "dir", "div", "dl", "fieldset", "figure", "footer", "header", "menu", "nav", "ol", "p", "section", "ul" のいずれかの開始タグ
-
If the stack of open elements has a p element in
scope, then act as if an end tag with the tag name
"p" had been seen.
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
- A start tag whose tag name is one of: "h1", "h2", "h3", "h4",
"h5", "h6"タグ名が "h1", "h2", "h3", "h4", "h5", "h6" のいずれかの開始タグ
-
If the stack of open elements has a p element in
scope, then act as if an end tag with the tag name
"p" had been seen.
If the current node is an element whose tag name
is one of "h1", "h2", "h3", "h4", "h5", or "h6", then this is a
parse error; pop the current node off
the stack of open elements.
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
- A start tag whose tag name is one of: "pre", "listing"タグ名が "pre", "listing" のいずれかの開始タグ
-
If the stack of open elements has a p element in
scope, then act as if an end tag with the tag name
"p" had been seen.
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
If the next token is a U+000A LINE FEED (LF) character
token, then ignore that token and move on to the next
one. (Newlines at the start of pre blocks are
ignored as an authoring convenience.)
- A start tag whose tag name is "form"タグ名が "form" の開始タグ
-
If the form element
pointer is not null, then this is a parse
error; ignore the token.
Otherwise:それ以外の場合:
If the stack of open elements has a p element in
scope, then act as if an end tag with the tag name
"p" had been seen.
Insert an HTML element for the token, and set the
form element pointer to
point to the element created.
- A start tag whose tag name is "li"タグ名が "li" の開始タグ
-
Run the following algorithm:次の算法を実行します:
Initialize node to be the current
node (the bottommost node of the stack).
If node is an li element,
then act as if an end tag with the tag name "li" had
been seen, then jump to the last step.
If node is not in the
formatting category, and is not in the
phrasing category, and is not an
address, div, or p
element, then jump to the last step.
Otherwise, set node to the previous
entry in the stack of open elements and return to
step 2.
-
This is the last step.
If the stack of open elements has a p element in
scope, then act as if an end tag with the tag name
"p" had been seen.
Finally, insert an HTML element for the
token.
- A start tag whose tag name is one of: "dd", "dt"タグ名が "dd", "dt" のいずれかの開始タグ
-
Run the following algorithm:次の算法を実行します:
Initialize node to be the current
node (the bottommost node of the stack).
If node is a dd or
dt element, then act as if an end tag with the same
tag name as node had been seen, then jump to
the last step.
If node is not in the
formatting category, and is not in the
phrasing category, and is not an
address, div, or p
element, then jump to the last step.
Otherwise, set node to the previous
entry in the stack of open elements and return to
step 2.
-
This is the last step.
If the stack of open elements has a p element in
scope, then act as if an end tag with the tag name
"p" had been seen.
Finally, insert an HTML element for the
token.
- A start tag whose tag name is "plaintext"タグ名が "plaintext" の開始タグ
-
If the stack of open elements has a p element in
scope, then act as if an end tag with the tag name
"p" had been seen.
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
Switch the content model flag to the PLAINTEXT
state.
Once a start tag with the tag name "plaintext"
has been seen, that will be the last token ever seen other
than character tokens (and the end-of-file token), because
there is no way to switch the content model flag
out of the PLAINTEXT state.
- An end tag whose tag name is one of: "address", "article",
"aside", "blockquote", "center", "datagrid", "details", "dialog",
"dir", "div", "dl", "fieldset", "figure", "footer", "header",
"listing", "menu", "nav", "ol", "pre", "section", "ul"タグ名が "address", "article", "aside", "blockquote", "center", "datagrid", "details", "dialog", "dir", "div", "dl", "fieldset", "figure", "footer", "header", "listing", "menu", "nav", "ol", "pre", "section", "ul" のいずれかの終了タグ
-
If the stack of open elements does not have an element in scope
with the same tag name as that of the token, then this is a
parse error; ignore the token.
Otherwise, run these steps:そうでない場合、次の段階群を走らせます。
Generate implied end tags.暗示終了タグを生成します。
If the current node is not an element with
the same tag name as that of the token, then this is a
parse error.
Pop elements from the stack of open elements
until an element with the same tag name as the token has been
popped from the stack.
- An end tag whose tag name is "form"タグ名が "form" の終了タグ
-
Let node be the element that the
form element pointer is set
to.
Set the form element pointer
to null.
If node is null or the stack of open
elements does not have node in scope, then this is
a parse error; ignore the token.
Otherwise, run these steps:そうでない場合、次の段階群を走らせます。
Generate implied end tags.暗示終了タグを生成します。
If the current node is not node, then this is a parse
error.
Remove node from the stack of
open elements.
- An end tag whose tag name is "p"タグ名が "p" の終了タグ
-
If the stack of open elements does not have an element in scope
with the same tag name as that of the token, then this is a
parse error; act as if a start tag with the tag name
p had been seen, then reprocess the current
token.
Otherwise, run these steps:そうでない場合、次の段階群を走らせます。
Generate implied end tags, except
for elements with the same tag name as the token.
If the current node is not an element with
the same tag name as that of the token, then this is a
parse error.
Pop elements from the stack of open elements
until an element with the same tag name as the token has been
popped from the stack.
- An end tag whose tag name is one of: "dd", "dt", "li"タグ名が "dd", "dt", "li" のいずれかの終了タグ
-
If the stack of open elements does not have an element in scope
with the same tag name as that of the token, then this is a
parse error; ignore the token.
Otherwise, run these steps:そうでない場合、次の段階群を走らせます。
Generate implied end tags, except
for elements with the same tag name as the token.
If the current node is not an element with
the same tag name as that of the token, then this is a
parse error.
Pop elements from the stack of open elements
until an element with the same tag name as the token has been
popped from the stack.
- An end tag whose tag name is one of: "h1", "h2", "h3", "h4", "h5", "h6"タグ名が "h1", "h2", "h3", "h4", "h5", "h6" のいずれかの終了タグ
-
If the stack of open elements does not have an element in scope
whose tag name is one of "h1", "h2", "h3", "h4", "h5", or "h6",
then this is a parse error; ignore the token.
Otherwise, run these steps:そうでない場合、次の段階群を走らせます。
Generate implied end tags.暗示終了タグを生成します。
If the current node is not an element with
the same tag name as that of the token, then this is a
parse error.
Pop elements from the stack of open elements
until an element whose tag name is one of "h1", "h2", "h3", "h4",
"h5", or "h6" has been popped from the stack.
- An end tag whose tag name is "sarcasm"タグ名が "sarcasm" の終了タグ
-
Take a deep breath, then act as described in the "any other end
tag" entry below.深呼吸をして、後述の「その他の終了タグ」の項で説明されているように作用します。
- A start tag whose tag name is "a"タグ名が "a" の開始タグ
-
If the list of active formatting elements
contains an element whose tag name is "a" between the end of
the list and the last marker on the list (or the start of the
list if there is no marker on the list), then this is a
parse error; act as if an end tag with the tag
name "a" had been seen, then remove that element from the
list of active formatting elements and the
stack of open elements if the end tag didn't
already remove it (it might not have if the element is not
in table
scope).
In the non-conforming stream
<a href="a">a<table><a href="b">b</table>x,
the first a element would be closed upon seeing
the second one, and the "x" character would be inside a link
to "b", not to "a". This is despite the fact that the outer
a element is not in table scope (meaning that a
regular </a> end tag at the start of the table
wouldn't close the outer a element).
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
Insert an HTML element for the token. Add that
element to the list of active formatting
elements.
- A start tag whose tag name is one of: "b", "big", "em",
"font", "i", "s", "small", "strike", "strong", "tt", "u"タグ名が "b", "big", "em", "font", "i", "s", "small", "strike", "strong", "tt", "u" のいずれかの開始タグ
-
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
Insert an HTML element for the token. Add that
element to the list of active formatting
elements.
- A start tag whose tag name is "nobr"タグ名が "nobr" の開始タグ
-
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
If the stack of open elements has a nobr element in scope,
then this is a parse error; act as if an end tag with
the tag name "nobr" had been seen, then once again
reconstruct the active formatting elements, if
any.
Insert an HTML element for the token. Add that
element to the list of active formatting
elements.
- An end tag whose tag name is one of:
"a", "b", "big", "em", "font", "i", "nobr", "s", "small",
"strike", "strong", "tt", "u"タグ名が "a", "b", "big", "em", "font", "i", "nobr", "s", "small", "strike", "strong", "tt", "u" のいずれかの終了タグ
-
Follow these steps:次の段階群に従います。
-
Let the formatting element be the
last element in the list of active formatting
elements that:
is between the end of the list and the last scope
marker in the list, if any, or the start of the list
otherwise, and
has the same tag name as the token.
If there is no such node, or, if that node is also in the
stack of open elements but the element is not in scope, then this is a
parse error; ignore the token, and abort these
steps.
Otherwise, if there is such a node, but that node is not
in the stack of open elements, then this is a
parse error; remove the element from the list,
and abort these steps.
Otherwise, there is a formatting
element and that element is in the stack and is in scope. If the element is not the
current node, this is a parse
error. In any case, proceed with the algorithm as
written in the following steps.
Let the furthest block be the
topmost node in the stack of open elements that
is lower in the stack than the formatting
element, and is not an element in the
phrasing or formatting
categories. There might not be one.
If there is no furthest block,
then the UA must skip the subsequent steps and instead just
pop all the nodes from the bottom of the stack of open
elements, from the current node up to and
including the formatting element, and
remove the formatting element from the
list of active formatting elements.
Let the common ancestor be the element
immediately above the formatting element in the
stack of open elements.
If the furthest block has a parent node,
then remove the furthest block from its parent
node.
Let a bookmark note the position of the formatting element in the list of active
formatting elements relative to the elements on either
side of it in the list.
-
Let node and last node be the
furthest block. Follow these steps:
Let node be the element immediately
above node in the stack of open
elements.
If node is not in the list of
active formatting elements, then remove node from the stack of open
elements and then go back to step 1.
Otherwise, if node is the formatting element, then go to the next step
in the overall algorithm.
Otherwise, if last node is the furthest block, then move the aforementioned
bookmark to be immediately after the node in the list of active formatting
elements.
If node has any children, perform a shallow
clone of node, replace the entry for
node in the list of active formatting
elements with an entry for the clone, replace the
entry for node in the stack of open
elements with an entry for the clone, and let
node be the clone.
Insert last node into node, first removing it from its previous
parent node if any.
Let last node be node.
Return to step 1 of this inner set of steps.手順 1 of this inner set of steps に戻ります。
-
If the common ancestor node is a
table, tbody, tfoot,
thead, or tr element, then,
foster parent whatever last
node ended up being in the previous step.
Otherwise, append whatever last node
ended up being in the previous step to the common
ancestor node, first removing it from its previous parent
node if any.
Perform a shallow clone of the formatting
element.
Take all of the child nodes of the furthest
block and append them to the clone created in the last
step.
Append that clone to the furthest
block.
Remove the formatting element from the
list of active formatting elements, and insert
the clone into the list of active formatting
elements at the position of the aforementioned
bookmark.
Remove the formatting element from the
stack of open elements, and insert the clone into
the stack of open elements immediately below the
position of the furthest block in that
stack.
Jump back to step 1 in this series of steps.
The way these steps are defined, only elements
in the formatting category ever get cloned by
this algorithm.
Because of the way this algorithm causes elements to
change parents, it has been dubbed the "adoption agency algorithm"
(in contrast with other possibly algorithms for dealing with
misnested content, which included the "incest algorithm", the
"secret affair algorithm", and the "Heisenberg algorithm").
- A start tag whose tag name is "button"タグ名が "button" の開始タグ
-
If the stack of open elements has a button element in
scope, then this is a parse error;
act as if an end tag with the tag name "button" had been seen,
then reprocess the token.
Otherwise:それ以外の場合:
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
Insert a marker at the end of the list of active
formatting elements.
- A start tag token whose tag name is one of: "applet",
"marquee", "object"タグ名が "applet", "marquee", "object" のいずれかの開始タグ字句
-
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
Insert a marker at the end of the list of active
formatting elements.
- An end tag token whose tag name is one of: "applet", "button",
"marquee", "object"
-
If the stack of open elements does not have an element in scope
with the same tag name as that of the token, then this is a
parse error; ignore the token.
Otherwise, run these steps:そうでない場合、次の段階群を走らせます。
Generate implied end tags.暗示終了タグを生成します。
If the current node is not an element with
the same tag name as that of the token, then this is a
parse error.
Pop elements from the stack of open elements
until an element with the same tag name as the token has been
popped from the stack.
Clear the list of active formatting elements up to the
last marker.
- A start tag whose tag name is "xmp"タグ名が "xmp" の開始タグ
-
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
Follow the generic CDATA element parsing algorithm.
- A start tag whose tag name is "table"タグ名が "table" の開始タグ
-
If the stack of open elements has a p element in
scope, then act as if an end tag with the tag name
"p" had been seen.
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
Switch the insertion mode to "in table".
- A start tag whose tag name is one of: "area", "basefont",
"bgsound", "br", "embed", "img", "input", "spacer", "wbr"タグ名が "area", "basefont", "bgsound", "br", "embed", "img", "input", "spacer", "wbr" のいずれかの開始タグ
-
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
Insert an HTML element for the token. Immediately
pop the current node off the stack of open
elements.
Acknowledge the
token's self-closing flag, if it is set.
- A start tag whose tag name is one of: "param", "source"タグ名が "param", "source" のいずれかの開始タグ
-
Insert an HTML element for the token. Immediately
pop the current node off the stack of open
elements.
Acknowledge the
token's self-closing flag, if it is set.
- A start tag whose tag name is "hr"タグ名が "hr" の開始タグ
-
If the stack of open elements has a p element in
scope, then act as if an end tag with the tag name
"p" had been seen.
Insert an HTML element for the token. Immediately
pop the current node off the stack of open
elements.
Acknowledge the
token's self-closing flag, if it is set.
- A start tag whose tag name is "image"タグ名が "image" の開始タグ
-
Parse error. Change the token's tag name
to "img" and reprocess it. (Don't ask.)
- A start tag whose tag name is "isindex"タグ名が "isindex" の開始タグ
-
Parse error.構文解析誤り。
If the form element
pointer is not null, then ignore the token.
Otherwise:それ以外の場合:
Acknowledge the
token's self-closing flag, if it is set.
Act as if a start tag token with the tag name "form" had been seen.
If the token has an attribute called "action", set the
action attribute on the
resulting form element to the value of the
"action" attribute of the token.
Act as if a start tag token with the tag name "hr" had been
seen.
Act as if a start tag token with the tag name "p" had been
seen.
Act as if a start tag token with the tag name "label" had been
seen.
Act as if a stream of character tokens had been seen (see below
for what they should say).
Act as if a start tag token with the tag name "input" had been
seen, with all the attributes from the "isindex" token except
"name", "action", and "prompt". Set the name attribute of the resulting
input element to the value "isindex".
Act as if a stream of character tokens had been seen (see
below for what they should say).
Act as if an end tag token with the tag name "label" had been
seen.
Act as if an end tag token with the tag name "p" had been
seen.
Act as if a start tag token with the tag name "hr" had been
seen.
Act as if an end tag token with the tag name "form" had been
seen.
If the token has an attribute with the name "prompt", then the
first stream of characters must be the same string as given in
that attribute, and the second stream of characters must be
empty. Otherwise, the two streams of character tokens together
should, together with the input element, express the
equivalent of "This is a searchable index. Insert your search
keywords here: (input field)" in the user's preferred
language.
- A start tag whose tag name is "textarea"タグ名が "textarea" の開始タグ
-
Insert an HTML element for the
token.当該字句について HTML
要素を挿入します。
If the next token is a U+000A LINE FEED (LF) character
token, then ignore that token and move on to the next
one. (Newlines at the start of textarea elements are
ignored as an authoring convenience.)
Append the new element to the current
node.
Switch the tokeniser's content model flag to
the RCDATA state.
Let the original insertion mode be the
current insertion mode.
Switch the insertion mode to "in
CDATA/RCDATA".
- A start tag whose tag name is one of: "iframe", "noembed"タグ名が "iframe", "noembed" のいずれかの開始タグ
- A start tag whose tag name is "noscript", if the scripting flag is enabled
-
Follow the generic CDATA element parsing algorithm.
- A start tag whose tag name is "select"タグ名が "select" の開始タグ
-
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
If the insertion mode is one of in table", "in caption", "in column group",
"in table
body", "in
row", or "in
cell", then switch the insertion mode to
"in select in
table". Otherwise, switch the insertion mode
to "in select".
- A start tag whose tag name is one of: "optgroup", "option"タグ名が "optgroup", "option" のいずれかの開始タグ
-
If the stack of open elements has an option element in
scope, then act as if an end tag with the tag name "option"
had been seen.
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
- A start tag whose tag name is one of: "rp", "rt"タグ名が "rp", "rt" のいずれかの開始タグ
If the stack of open elements has a ruby element in scope,
then generate implied end tags. If the current
node is not then a ruby element, this is a
parse error; pop all the nodes from the current
node up to the node immediately before the bottommost
ruby element on the stack of open
elements.
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
- An end tag whose tag name is "br"タグ名が "br" の終了タグ
-
Parse error. Act as if a start tag token with
the tag name "br" had been seen. Ignore the end tag token.
- A start tag whose tag name is "math"タグ名が "math" の開始タグ
-
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
Adjust MathML attributes for the token. (This
fixes the case of MathML attributes that are not all
lowercase.)
Adjust foreign attributes for the token. (This
fixes the use of namespaced attributes, in particular XLink.)
Insert a foreign element for the token, in the
MathML namespace.
If the token has its self-closing flag set, pop the
current node off the stack of open
elements and acknowledge the token's self-closing flag.
Otherwise, let the secondary insertion mode be the
current insertion mode, and then switch the
insertion mode to "in foreign content".
- A start tag whose tag name is one of: "caption",
"col", "colgroup", "frame", "frameset", "head", "tbody", "td",
"tfoot", "th", "thead", "tr"
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- Any other start tagその他の開始タグ
-
Reconstruct the active formatting elements, if
any.活性書式付け要素を再構築できれば、します。
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
This element will be a phrasing
element.
- Any other end tagその他の終了タグ
-
Run the following steps:次の段階群を走らせます。
Initialize node to be the current
node (the bottommost node of the stack).
If node has the same tag name as
the end tag token, then:
Generate implied end tags.暗示終了タグを生成します。
If the tag name of the end tag token does not match
the tag name of the current node, this is a
parse error.
Pop all the nodes from the current node up
to node, including node, then stop these steps.
Otherwise, if node is in neither the
formatting category nor the phrasing
category, then this is a parse error; ignore the
token, and abort these steps.
Set node to the previous entry in the
stack of open elements.
Return to step 2.手順 2 に戻ります。
8.2.5.11 The "in CDATA/RCDATA" insertion mode8.2.5.11 「in CDATA/RCDATA」挿入モード
When the insertion mode is "in CDATA/RCDATA", tokens must be
handled as follows:挿入モードが「in CDATA/RCDATA」の時は、字句を次のように処理しなければなりません。
- A character token文字字句
-
Insert the token's
character into the current node.現在節点に字句の文字を挿入します。
- An end-of-file tokenファイル末字句
-
Parse error.構文解析誤り。
If the current node is a script
element, mark the script element as "already
executed".
Pop the current node off the stack of open
elements.
Switch the insertion mode to the original
insertion mode and reprocess the current token.
- An end tag whose tag name is "script"タグ名が "script" の終了タグ
-
Let script be the current node
(which will be a script element).
Pop the current node off the stack of open
elements.
Switch the insertion mode to the original
insertion mode.
Let the old insertion point have the
same value as the current insertion point. Let
the insertion point be just before the next
input character.
Increment the parser's script nesting level by
one.
Run the script. This might cause some script to execute,
which might cause new
characters to be inserted into the tokeniser, and might
cause the tokeniser to output more tokens, resulting in a reentrant invocation of the parser.
Decrement the parser's script nesting level by
one. If the parser's script nesting level is zero,
then set the parser pause flag to false.
Let the insertion point have the value of the
old insertion point. (In other words,
restore the insertion point to the value it had
before the previous paragraph. This value might be the
"undefined" value.)
At this stage, if there is a
pending external script, then:
- If the tree construction stage is being called reentrantly, say from a
call to
document.write():
Set the parser pause flag to true, and abort
the processing of any nested invocations of the tokeniser,
yielding control back to the caller. (Tokenization will resume
when the caller returns to the "outer" tree construction
stage.)
- Otherwise:それ以外の場合:
-
Follow these steps:次の段階群に従います。
Let the script be the pending
external script. There is no longer a pending
external script.
Pause until the script has completed
loading.
Let the insertion point be just before the
next input character.
Execute the
script.
Let the insertion point be undefined
again.
If there is once again a pending external
script, then repeat these steps from step 1.
- Any other end tagその他の終了タグ
-
Pop the current node off the stack of open
elements.
Switch the insertion mode to the original
insertion mode.
8.2.5.12 The "in table" insertion mode8.2.5.12 「in table」挿入モード
When the insertion mode is "in table", tokens must be handled as follows:挿入モードが「in table」の時は、字句を次のように処理しなければなりません。
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
-
If the current table is tainted, then
act as described in the "anything else" entry below.
Otherwise, insert the
character into the current node.
- A comment token注釈字句
-
Append a Comment node to the current
node with the data attribute set to
the data given in the comment token.現在節点の末尾に data
属性を注釈字句で与えられたデータに設定した Comment
節点を追加します。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is "caption"タグ名が "caption" の開始タグ
-
Clear the stack back to a table context. (See
below.)
Insert a marker at the end of the list of active
formatting elements.
Insert an HTML element for the token, then
switch the insertion mode to "in caption".
- A start tag whose tag name is "colgroup"タグ名が "colgroup" の開始タグ
-
Clear the stack back to a table context. (See
below.)
Insert an HTML element for the token, then
switch the insertion mode to "in column
group".
- A start tag whose tag name is "col"タグ名が "col" の開始タグ
-
Act as if a start tag token with the tag name "colgroup"
had been seen, then reprocess the current token.タグ名が "colgroup" の開始タグ字句を見たかのように動作してから、
現在字句を再処理します。
- A start tag whose tag name is one of: "tbody", "tfoot", "thead"タグ名が "tbody", "tfoot", "thead" のいずれかの開始タグ
-
Clear the stack back to a table context. (See
below.)
Insert an HTML element for the token, then
switch the insertion mode to "in table
body".
- A start tag whose tag name is one of: "td", "th", "tr"タグ名が "td", "th", "tr" のいずれかの開始タグ
-
Act as if a start tag token with the tag name "tbody" had
been seen, then reprocess the current token.タグ名が "tbody" の開始タグ字句を見たかのように動作してから、
現在字句を再処理します。
- A start tag whose tag name is "table"タグ名が "table" の開始タグ
-
Parse error. Act as if an end tag token with
the tag name "table" had been seen, then, if that token wasn't
ignored, reprocess the current token.
The fake end tag token here can only be
ignored in the fragment case.
- An end tag whose tag name is "table"タグ名が "table" の終了タグ
-
If the stack of open elements does not have an element in table
scope with the same tag name as the token, this is a
parse error. Ignore the token. (fragment
case)
Otherwise:それ以外の場合:
Pop elements from this stack until a table
element has been popped from the stack.
Reset the insertion mode appropriately.挿入モードを適切に再設定します。
- An end tag whose tag name is one of: "body", "caption",
"col", "colgroup", "html", "tbody", "td", "tfoot", "th",
"thead", "tr"タグ名が "body", "caption", "col", "colgroup", "html", "tbody", "td", "tfoot", "th", "thead", "tr" のいずれかの終了タグ
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is one of: "style", "script"タグ名が "style", "script" のいずれかの開始タグ
-
If the current table is tainted then
act as described in the "anything else" entry below.
Otherwise, process the token using the rules for
the "in
head" insertion mode.
- A start tag whose tag name is "input"タグ名が "input" の開始タグ
-
If the token does not have an attribute with the name "type",
or if it does, but that attribute's value is not an ASCII
case-insensitive match for the string "hidden", or, if the current table is
tainted, then: act as described in the "anything
else" entry below.
Otherwise:それ以外の場合:
Parse error.構文解析誤り。
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
Pop that input element off the stack of
open elements.
- An end-of-file tokenファイル末字句
-
If the current node is not the root
html element, then this is a parse
error.
It can only be the current node in
the fragment case.
Stop parsing.構文解析を停止します。
- Anything elseその他のもの
-
Parse error. Process the token using the
rules for the "in
body" insertion mode, except that if the
current node is a table,
tbody, tfoot, thead, or
tr element, then, whenever a node would be inserted
into the current node, it must instead be foster parented.
When the steps above require the UA to clear the stack
back to a table context, it means that the UA must, while
the current node is not a table
element or an html element, pop elements from the
stack of open elements.
The current node being an
html element after this process is a fragment
case.
8.2.5.13 The "in caption" insertion mode8.2.5.13 「in caption」挿入モード
When the insertion mode is "in caption", tokens must be handled as follows:挿入モードが「in caption」の時は、字句を次のように処理しなければなりません。
- An end tag whose tag name is "caption"タグ名が "caption" の終了タグ
-
If the stack of open elements does not have an element in table
scope with the same tag name as the token, this is a
parse error. Ignore the token. (fragment
case)
Otherwise:それ以外の場合:
Generate implied end tags.暗示終了タグを生成します。
Now, if the current node is not a
caption element, then this is a parse
error.
Pop elements from this stack until a caption
element has been popped from the stack.
Clear the list of active formatting elements up to
the last marker.
Switch the insertion mode to "in table".
- A start tag whose tag name is one of: "caption", "col",
"colgroup", "tbody", "td", "tfoot", "th", "thead", "tr"タグ名が "caption", "col", "colgroup", "tbody", "td", "tfoot", "th", "thead", "tr" のいずれかの開始タグ
- An end tag whose tag name is "table"タグ名が "table" の終了タグ
-
Parse error. Act as if an end tag with the tag
name "caption" had been seen, then, if that token wasn't
ignored, reprocess the current token.
The fake end tag token here can only be
ignored in the fragment case.
- An end tag whose tag name is one of: "body", "col",
"colgroup", "html", "tbody", "td", "tfoot", "th", "thead",
"tr"タグ名が "body", "col", "colgroup", "html", "tbody", "td", "tfoot", "th", "thead", "tr" のいずれかの終了タグ
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- Anything elseその他のもの
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
8.2.5.14 The "in column group" insertion mode8.2.5.14 「in column group」挿入モード
When the insertion mode is "in column group", tokens must be handled as follows:挿入モードが「in column group」の時は、字句を次のように処理しなければなりません。
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
-
Insert the character into
the current node.現在節点に文字を挿入します。
- A comment token注釈字句
-
Append a Comment node to the current
node with the data attribute set to
the data given in the comment token.現在節点の末尾に data
属性を注釈字句で与えられたデータに設定した Comment
節点を追加します。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- A start tag whose tag name is "col"タグ名が "col" の開始タグ
-
Insert an HTML element for the token. Immediately
pop the current node off the stack of open
elements.
Acknowledge the
token's self-closing flag, if it is set.
- An end tag whose tag name is "colgroup"タグ名が "colgroup" の終了タグ
-
If the current node is the root
html element, then this is a parse
error; ignore the token. (fragment
case)
Otherwise, pop the current node (which will be
a colgroup element) from the stack of open
elements. Switch the insertion mode to
"in table".
- An end tag whose tag name is "col"タグ名が "col" の終了タグ
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- An end-of-file tokenファイル末字句
-
If the current node is the root html
element, then stop parsing. (fragment
case)
Otherwise, act as described in the "anything else" entry
below.
- Anything elseその他のもの
-
Act as if an end tag with the tag name "colgroup" had been
seen, and then, if that token wasn't ignored, reprocess the
current token.
The fake end tag token here can only be
ignored in the fragment case.
8.2.5.15 The "in table body" insertion mode8.2.5.15 「in table body」挿入モード
When the insertion mode is "in table body", tokens must be handled as follows:挿入モードが「in table body」の時は、字句を次のように処理しなければなりません。
- A start tag whose tag name is "tr"タグ名が "tr" の開始タグ
-
Clear the stack back to a table body
context. (See below.)
Insert an HTML element for the token, then switch
the insertion mode to "in row".
- A start tag whose tag name is one of: "th", "td"タグ名が "th", "td" のいずれかの開始タグ
-
Parse error. Act as if a start tag with
the tag name "tr" had been seen, then reprocess the current
token.
- An end tag whose tag name is one of: "tbody", "tfoot",
"thead"タグ名が "tbody", "tfoot", "thead" のいずれかの終了タグ
-
If the stack of open elements does not have an element in table
scope with the same tag name as the token, this is a
parse error. Ignore the token.
Otherwise:それ以外の場合:
Clear the stack back to a table body
context. (See below.)
Pop the current node from the stack of
open elements. Switch the insertion mode
to "in table".
- A start tag whose tag name is one of: "caption", "col",
"colgroup", "tbody", "tfoot", "thead"タグ名が "caption", "col", "colgroup", "tbody", "tfoot", "thead" のいずれかの開始タグ
- An end tag whose tag name is "table"タグ名が "table" の終了タグ
-
If the stack of open elements does not have a
tbody, thead, or tfoot
element in table scope, this is a parse
error. Ignore the token. (fragment
case)
Otherwise:それ以外の場合:
Clear the stack back to a table body
context. (See below.)
Act as if an end tag with the same tag name as the
current node ("tbody", "tfoot", or "thead") had
been seen, then reprocess the current token.
- An end tag whose tag name is one of: "body", "caption",
"col", "colgroup", "html", "td", "th", "tr"タグ名が "body", "caption", "col", "colgroup", "html", "td", "th", "tr" のいずれかの終了タグ
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- Anything elseその他のもの
-
Process the token using the rules for the "in table" insertion
mode.
When the steps above require the UA to clear the stack
back to a table body context, it means that the UA must,
while the current node is not a tbody,
tfoot, thead, or html
element, pop elements from the stack of open
elements.
The current node being an
html element after this process is a fragment
case.
8.2.5.16 The "in row" insertion mode8.2.5.16 「in row」挿入モード
When the insertion mode is "in row", tokens must be handled as follows:挿入モードが「in row」の時は、字句を次のように処理しなければなりません。
- A start tag whose tag name is one of: "th", "td"タグ名が "th", "td" のいずれかの開始タグ
-
Clear the stack back to a table row
context. (See below.)
Insert an HTML element for the token, then switch
the insertion mode to "in cell".
Insert a marker at the end of the list of active
formatting elements.
- An end tag whose tag name is "tr"タグ名が "tr" の終了タグ
-
If the stack of open elements does not have an element in table
scope with the same tag name as the token, this is a
parse error. Ignore the token. (fragment
case)
Otherwise:それ以外の場合:
Clear the stack back to a table row
context. (See below.)
Pop the current node (which will be a
tr element) from the stack of open
elements. Switch the insertion mode to
"in table
body".
- A start tag whose tag name is one of: "caption", "col",
"colgroup", "tbody", "tfoot", "thead", "tr"タグ名が "caption", "col", "colgroup", "tbody", "tfoot", "thead", "tr" のいずれかの開始タグ
- An end tag whose tag name is "table"タグ名が "table" の終了タグ
-
Act as if an end tag with the tag name "tr" had been seen,
then, if that token wasn't ignored, reprocess the current
token.
The fake end tag token here can only be
ignored in the fragment case.
- An end tag whose tag name is one of: "tbody", "tfoot",
"thead"タグ名が "tbody", "tfoot", "thead" のいずれかの終了タグ
-
If the stack of open elements does not have an element in table
scope with the same tag name as the token, this is a
parse error. Ignore the token.
Otherwise, act as if an end tag with the tag name "tr" had
been seen, then reprocess the current token.
- An end tag whose tag name is one of: "body", "caption",
"col", "colgroup", "html", "td", "th"タグ名が "body", "caption", "col", "colgroup", "html", "td", "th" のいずれかの終了タグ
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- Anything elseその他のもの
-
Process the token using the rules for the "in table" insertion
mode.
When the steps above require the UA to clear the stack
back to a table row context, it means that the UA must,
while the current node is not a tr
element or an html element, pop elements from the
stack of open elements.
The current node being an
html element after this process is a fragment
case.
8.2.5.17 The "in cell" insertion mode8.2.5.17 「in cell」挿入モード
When the insertion mode is "in cell", tokens must be handled as follows:挿入モードが「in cell」の時は、字句を次のように処理しなければなりません。
- An end tag whose tag name is one of: "td", "th"タグ名が "td", "th" のいずれかの終了タグ
-
If the stack of open elements does not have an element in table
scope with the same tag name as that of the token, then
this is a parse error and the token must be
ignored.
Otherwise:それ以外の場合:
Generate implied end tags.暗示終了タグを生成します。
Now, if the current node is not an element
with the same tag name as the token, then this is a
parse error.ここで、現在節点が字句と同じタグ名の要素でない場合、
これは構文解析誤りです。
Pop elements from this stack until an element with the same
tag name as the token has been popped from the stack.字句と同じタグ名の要素がこのスタックからポップされるまで、要素をスタックからポップします。
Clear the list of active formatting elements up to
the last marker.
Switch the insertion mode to "in row". (The
current node will be a tr element at
this point.)挿入モードを「in row」に切り替えます。
(この時点で現在節点は tr
要素になるはずです。)
- A start tag whose tag name is one of: "caption", "col",
"colgroup", "tbody", "td", "tfoot", "th", "thead", "tr"タグ名が "caption", "col", "colgroup", "tbody", "td", "tfoot", "th", "thead", "tr" のいずれかの開始タグ
-
If the stack of open elements does
not have
a td or th element in table
scope, then this is a parse error; ignore
the token. (fragment case)
Otherwise, close the cell (see below) and
reprocess the current token.
- An end tag whose tag name is one of: "body", "caption",
"col", "colgroup", "html"タグ名が "body", "caption", "col", "colgroup", "html" のいずれかの終了タグ
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- An end tag whose tag name is one of: "table", "tbody",
"tfoot", "thead", "tr"タグ名が "table", "tbody", "tfoot", "thead", "tr" のいずれかの終了タグ
-
If the stack of open elements does not have an element in table
scope with the same tag name as that of the token
(which can only happen for "tbody", "tfoot" and "thead", or,
in the fragment case), then this is a parse
error and the token must be ignored.
Otherwise, close the cell (see below) and
reprocess the current token.
- Anything elseその他のもの
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
Where the steps above say to close the cell, they
mean to run the following algorithm:
If the stack of open elements has a td
element in table scope, then act as if an end tag token
with the tag name "td" had been seen.
Otherwise, the stack of open elements will
have a
th element in table scope; act as if an end
tag token with the tag name "th" had been seen.
The stack of open elements cannot
have both a td and a th element in table scope at
the same time, nor can it have neither when the insertion
mode is "in
cell".
8.2.5.18 The "in select" insertion mode8.2.5.18 「in select」挿入モード
When the insertion mode is "in select", tokens must be handled as follows:挿入モードが「in select」の時は、字句を次のように処理しなければなりません。
- A character token文字字句
-
Insert the token's
character into the current node.現在節点に字句の文字を挿入します。
- A comment token注釈字句
-
Append a Comment node to the current
node with the data attribute set to
the data given in the comment token.現在節点の末尾に data
属性を注釈字句で与えられたデータに設定した Comment
節点を追加します。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- A start tag whose tag name is "option"タグ名が "option" の開始タグ
-
If the current node is an option
element, act as if an end tag with the tag name "option" had
been seen.現在節点が option
要素の場合、タグ名 "option" の終了タグを見たかのように作用します。
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
- A start tag whose tag name is "optgroup"タグ名が "optgroup" の開始タグ
-
If the current node is an option
element, act as if an end tag with the tag name "option" had
been seen.現在節点が option
要素の場合、タグ名 "option" の終了タグを見たかのように作用します。
If the current node is an
optgroup element, act as if an end tag with the
tag name "optgroup" had been seen.現在字句が optgroup
要素の場合、タグ名 "optgroup" の終了タグを見たかのように作用します。
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
- An end tag whose tag name is "optgroup"タグ名が "optgroup" の終了タグ
-
First, if the current node is an
option element, and the node immediately before
it in the stack of open elements is an
optgroup element, then act as if an end tag with
the tag name "option" had been seen.
If the current node is an
optgroup element, then pop that node from the
stack of open elements. Otherwise, this is a
parse error; ignore the token.
- An end tag whose tag name is "option"タグ名が "option" の終了タグ
-
If the current node is an option
element, then pop that node from the stack of open
elements. Otherwise, this is a parse
error; ignore the token.
- An end tag whose tag name is "select"タグ名が "select" の終了タグ
-
If the stack of open elements does not have an element in table
scope with the same tag name as the token, this is a
parse error. Ignore the token. (fragment
case)
Otherwise:それ以外の場合:
Pop elements from the stack of open elements
until a select element has been popped from the
stack.
Reset the insertion mode appropriately.挿入モードを適切に再設定します。
- A start tag whose tag name is "select"タグ名が "select" の開始タグ
-
Parse error. Act as if the token had been
an end tag with the tag name "select" instead.
- A start tag whose tag name is one of: "input", "textarea"タグ名が "input", "textarea" のいずれかの開始タグ
-
Parse error. Act as if an end tag with the tag
name "select" had been seen, and reprocess the token.
- A start tag token whose tag name is "script"
-
Process the token using the rules for the "in head" insertion
mode.字句を、「in head」挿入モードの規則を使って処理します。
- An end-of-file tokenファイル末字句
-
If the current node is not the root
html element, then this is a parse
error.
It can only be the current node in
the fragment case.
Stop parsing.構文解析を停止します。
- Anything elseその他のもの
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
8.2.5.19 The "in select in table" insertion mode8.2.5.19 「in select in table」挿入モード
When the insertion mode is "in select in table", tokens must be handled as follows:挿入モードが「in select in table」の時は、字句を次のように処理しなければなりません。
- A start tag whose tag name is one of: "caption", "table",
"tbody", "tfoot", "thead", "tr", "td", "th"タグ名が "caption", "table", "tbody", "tfoot", "thead", "tr", "td", "th" のいずれかの開始タグ
-
Parse error. Act as if an end tag with the tag
name "select" had been seen, and reprocess the token.
- An end tag whose tag name is one of: "caption", "table",
"tbody", "tfoot", "thead", "tr", "td", "th"タグ名が "caption", "table", "tbody", "tfoot", "thead", "tr", "td", "th" のいずれかの終了タグ
-
Parse error.構文解析誤り。
If the stack of open elements has an
element in table scope with the same tag name as that
of the token, then act as if an end tag with the tag name
"select" had been seen, and reprocess the token. Otherwise,
ignore the token.
- Anything elseその他のもの
-
Process the token using the rules for the "in select" insertion
mode.
8.2.5.20 The "in foreign content" insertion mode8.2.5.20 「in foreign content」挿入モード
When the insertion mode is "in foreign content", tokens must be
handled as follows:挿入モードが「in foreign content」の時は、字句を次のように処理しなければなりません。
- A character token文字字句
-
Insert the token's
character into the current node.現在節点に字句の文字を挿入します。
- A comment token注釈字句
-
Append a Comment node to the current
node with the data attribute set to
the data given in the comment token.現在節点の末尾に data
属性を注釈字句で与えられたデータに設定した Comment
節点を追加します。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is neither "mglyph" nor "malignmark", if the current node is an
mi element in the MathML namespace.
- A start tag whose tag name is neither "mglyph" nor "malignmark", if the current node is an
mo element in the MathML namespace.
- A start tag whose tag name is neither "mglyph" nor "malignmark", if the current node is an
mn element in the MathML namespace.
- A start tag whose tag name is neither "mglyph" nor "malignmark", if the current node is an
ms element in the MathML namespace.
- A start tag whose tag name is neither "mglyph" nor "malignmark", if the current node is an
mtext element in the MathML namespace.
- A start tag, if the current node is an element in the HTML namespace.
- An end tag
-
Process the token using the rules for the
secondary insertion mode.
If, after doing so, the insertion mode is still
"in foreign
content", but there is no element in scope that has a
namespace other than the HTML namespace, switch the insertion
mode to the secondary insertion mode.
- A start tag whose tag name is one of: "b", "big",
"blockquote", "body", "br", "center", "code",
"dd", "div", "dl", "dt", "em", "embed", "font", "h1",
"h2", "h3", "h4", "h5", "h6", "head", "hr", "i", "img",
"li", "listing", "menu", "meta", "nobr",
"ol", "p", "pre", "ruby", "s", "small",
"span", "strong", "strike", "sub", "sup",
"table", "tt", "u", "ul", "var"タグ名が "b", "big", "blockquote", "body", "br", "center", "code", "dd", "div", "dl", "dt", "em", "embed", "font", "h1", "h2", "h3", "h4", "h5", "h6", "head", "hr", "i", "img", "li", "listing", "menu", "meta", "nobr", "ol", "p", "pre", "ruby", "s", "small", "span", "strong", "strike", "sub", "sup", "table", "tt", "u", "ul", "var" のいずれかの開始タグ
- An end-of-file tokenファイル末字句
-
Parse error.構文解析誤り。
Pop elements from the stack of open elements until
the current node is in the HTML
namespace.
Switch the insertion mode to the secondary
insertion mode, and reprocess the token.
- Any other start tagその他の開始タグ
-
If the current node is an element in the
MathML namespace, adjust MathML
attributes for the token. (This fixes the case of MathML
attributes that are not all lowercase.)
Adjust foreign attributes for the token. (This
fixes the use of namespaced attributes, in particular XLink in
SVG.)
Insert a foreign element for the token, in the
same namespace as the current node.
If the token has its self-closing flag set, pop the
current node off the stack of open
elements and acknowledge the token's self-closing flag.
8.2.5.21 The "after body" insertion mode8.2.5.21 「after body」挿入モード
When the insertion mode is "after body", tokens must be handled as follows:挿入モードが「after body」の時は、字句を次のように処理しなければなりません。
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- A comment token注釈字句
-
Append a Comment node to the first element in
the stack of open elements (the html
element), with the data attribute set to
the data given in the comment token.
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- An end tag whose tag name is "html"タグ名が "html" の終了タグ
-
If the parser was originally created as part of the HTML
fragment parsing algorithm, this is a parse
error; ignore the token. (fragment case)
Otherwise, switch the insertion mode to "after after
body".
- An end-of-file tokenファイル末字句
-
Stop parsing.構文解析を停止します。
- Anything elseその他のもの
-
Parse error. Switch the insertion
mode to "in
body" and reprocess the token.
8.2.5.22 The "in frameset" insertion mode8.2.5.22 「in frameset」挿入モード
When the insertion mode is "in frameset", tokens must be handled as follows:挿入モードが「in frameset」の時は、字句を次のように処理しなければなりません。
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
-
Insert the character into
the current node.現在節点に文字を挿入します。
- A comment token注釈字句
-
Append a Comment node to the current
node with the data attribute set to
the data given in the comment token.現在節点の末尾に data
属性を注釈字句で与えられたデータに設定した Comment
節点を追加します。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- A start tag whose tag name is "frameset"タグ名が "frameset" の開始タグ
-
Insert an HTML element for the token.当該字句について HTML
要素を挿入します。
- An end tag whose tag name is "frameset"タグ名が "frameset" の終了タグ
-
If the current node is the root
html element, then this is a parse
error; ignore the token. (fragment
case)
Otherwise, pop the current node from the
stack of open elements.
If the parser was not originally created as part
of the HTML fragment parsing algorithm
(fragment case), and the current
node is no longer a frameset element, then
switch the insertion mode to "after
frameset".
- A start tag whose tag name is "frame"タグ名が "frame" の開始タグ
-
Insert an HTML element for the token.
Immediately pop the current node off the
stack of open elements.
Acknowledge the
token's self-closing flag, if it is set.
- A start tag whose tag name is "noframes"タグ名が "noframes" の開始タグ
-
Process the token using the rules for the "in head" insertion
mode.字句を、「in head」挿入モードの規則を使って処理します。
- An end-of-file tokenファイル末字句
-
If the current node is not the root
html element, then this is a parse
error.
It can only be the current node in
the fragment case.
Stop parsing.構文解析を停止します。
- Anything elseその他のもの
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
8.2.5.23 The "after frameset" insertion mode8.2.5.23 「after frameset」挿入モード
When the insertion mode is "after frameset", tokens must be handled as follows:挿入モードが「after frameset」の時は、字句を次のように処理しなければなりません。
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
-
Insert the character into
the current node.現在節点に文字を挿入します。
- A comment token注釈字句
-
Append a Comment node to the current
node with the data attribute set to
the data given in the comment token.現在節点の末尾に data
属性を注釈字句で与えられたデータに設定した Comment
節点を追加します。
- A DOCTYPE tokenDOCTYPE 字句
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- An end tag whose tag name is "html"タグ名が "html" の終了タグ
-
Switch the insertion mode to "after after
frameset".
- A start tag whose tag name is "noframes"タグ名が "noframes" の開始タグ
-
Process the token using the rules for the "in head" insertion
mode.字句を、「in head」挿入モードの規則を使って処理します。
- An end-of-file tokenファイル末字句
-
Stop parsing.構文解析を停止します。
- Anything elseその他のもの
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
This doesn't handle UAs that don't support
frames, or that do support frames but want to show the NOFRAMES
content. Supporting the former is easy; supporting the latter is
harder.
8.2.5.24 The "after after body" insertion mode8.2.5.24 「after after body」挿入モード
When the insertion mode is "after after body", tokens must be handled as follows:
- A comment token注釈字句
-
Append a Comment node to the Document
object with the data attribute set to the
data given in the comment token.data 属性を注釈字句に与えられたデータに設定した Comment
節点を Document オブジェクトの末尾に追加します。
- A DOCTYPE tokenDOCTYPE 字句
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- An end-of-file tokenファイル末字句
-
Stop parsing.構文解析を停止します。
- Anything elseその他のもの
-
Parse error. Switch the insertion mode
to "in body" and
reprocess the token.
8.2.5.25 The "after after frameset" insertion mode8.2.5.25 「after after frameset」挿入モード
When the insertion mode is "after after frameset", tokens must be handled as follows:
- A comment token注釈字句
-
Append a Comment node to the Document
object with the data attribute set to the
data given in the comment token.data 属性を注釈字句に与えられたデータに設定した Comment
節点を Document オブジェクトの末尾に追加します。
- A DOCTYPE tokenDOCTYPE 字句
- A character token that is one of one of U+0009 CHARACTER
TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
or U+0020 SPACEU+0009 CHARACTER
TABULATION、U+000A LINE FEED (LF)、U+000C FORM FEED (FF)、
U+0020 SPACE
のいずれかの文字字句
- A start tag whose tag name is "html"タグ名が "html" の開始タグ
-
Process the token using the rules for the "in body" insertion
mode.字句を、「in body」挿入モードの規則を使って処理します。
- An end-of-file tokenファイル末字句
-
Stop parsing.構文解析を停止します。
- A start tag whose tag name is "noframes"タグ名が "noframes" の開始タグ
-
Process the token using the rules for the "in head" insertion
mode.字句を、「in head」挿入モードの規則を使って処理します。
- Anything elseその他のもの
-
Parse error. Ignore the token.構文解析誤り。字句を無視します。
8.2.6 The end8.2.6 終わり
Once the user agent stops parsing
the document, the user agent must follow the steps in this
section.ひとたび利用者エージェントが文書の構文解析を停止した際には、
利用者エージェントはこの節の段階群に従わなければなりません。
First, the current document readiness must be set to
"interactive".
Then, the rules for when a script completes loading
start applying (script execution is no longer managed by the
parser).
If any of the scripts in the list of scripts that will
execute as soon as possible have completed
loading, or if the list of scripts that will execute
asynchronously is not empty and the first script in that list
has completed loading, then the user agent must act as
if those scripts just completed loading, following the rules given
for that in the script element definition.
Then, if the list of scripts that will execute when the
document has finished parsing is not empty, and the first
item in this list has already completed loading, then
the user agent must act as if that script just finished loading.
By this point, there will be no scripts that have loaded but have
not yet been executed.
The user agent must then fire a simple event called
DOMContentLoaded at the
Document.
Once everything that delays the
load event has completed, the user agent must set the
current document readiness to "complete", and then
fire a load event at the
body element.
delaying the load event for things like image
loads allows for intranet port scans (even without
javascript!). Should we really encode that into the spec?
8.2.7 Coercing an HTML DOM into an infoset
When an application uses an HTML parser in
conjunction with an XML pipeline, it is possible that the
constructed DOM is not compatible with the XML tool chain in certain
subtle ways. For example, an XML toolchain might not be able to
represent attributes with the name xmlns,
since they conflict with the Namespaces in XML syntax. There is also
some data that the HTML parser generates that isn't
included in the DOM itself. This section specifies some rules for
handling these issues.
If the XML API being used doesn't support DOCTYPEs, the tool may
drop DOCTYPEs altogether.
If the XML API doesn't support attributes in no namespace that
are named "xmlns", attributes whose names
start with "xmlns:", or attributes in the
XMLNS namespace, then the tool may drop such
attributes.
The tool may annotate the output with any namespace declarations
required for proper operation.
If the XML API being used restricts the allowable characters in
the local names of elements and attributes, then the tool may map
all element and attribute local names that the API wouldn't support
to a set of names that are allowed, by replacing any
character that isn't supported with the uppercase letter U and the
five digits of the character's Unicode codepoint when expressed in
hexadecimal, using digits 0-9 and capital letters A-F as the
symbols, in increasing numeric order.
For example, the element name foo<bar, which can be output by the HTML
parser, though it is neither a legal HTML element name nor a
well-formed XML element name, would be converted into fooU0003Cbar, which is a well-formed
XML element name (though it's still not legal in HTML by any
means).
As another example, consider the attribute
xlink:href. Used on a MathML element, it becomes, after
being adjusted, an
attribute with a prefix "xlink" and a local
name "href". However, used on an HTML element,
it becomes an attribute with no prefix and the local name "xlink:href", which is not a valid NCName, and thus
might not be accepted by an XML API. It could thus get converted,
becoming "xlinkU0003Ahref".
The resulting names from this conversion
conveniently can't clash with any attribute generated by the
HTML parser, since those are all either lowercase or
those listed in the adjust foreign attributes
algorithm's table.
If the XML API restricts comments from having two consecutive
U+002D HYPHEN-MINUS characters (--), the tool may insert a single
U+0020 SPACE character between any such offending characters.
If the XML API restricts comments from ending in a
U+002D HYPHEN-MINUS character (-), the tool may insert a single
U+0020 SPACE character at the end of such comments.
If the XML API restricts allowed characters in character data,
the tool may replace any U+000C FORM FEED (FF) character with a
U+0020 SPACE character, and any other literal non-XML character with
a U+FFFD REPLACEMENT CHARACTER.
If the tool has no way to convey out-of-band information, then
the tool may drop the following information:
The mutations allowed by this section apply
after the HTML parser's rules have been
applied. For example, a <a::> start tag
will be closed by a </a::> end tag, and
never by a </aU0003AU0003A> end tag, even
if the user agent is using the rules above to then generate an
actual element in the DOM with the name aU0003AU0003A for that start tag.
8.3 Namespaces8.3 名前空間
The HTML namespace is: http://www.w3.org/1999/xhtmlHTML 名前空間は http://www.w3.org/1999/xhtml です。
The MathML namespace is: http://www.w3.org/1998/Math/MathMLMathML 名前空間 は http://www.w3.org/1998/Math/MathML です。
The SVG namespace is: http://www.w3.org/2000/svgSVG 名前空間は http://www.w3.org/2000/svg
です。
The XLink namespace is: http://www.w3.org/1999/xlinkXLink 名前空間は http://www.w3.org/1999/xlink
です。
The XML namespace is: http://www.w3.org/XML/1998/namespaceXML 名前空間は http://www.w3.org/XML/1998/namespace
です。
The XMLNS namespace is: http://www.w3.org/2000/xmlns/XMLNS 名前空間は http://www.w3.org/2000/xmlns/
です。
8.4 Serializing HTML fragments8.4 HTML 素片の直列化
The following steps form the HTML fragment serialization
algorithm. The algorithm takes as input a DOM
Element or Document, referred to as the node, and either returns a string or raises an
exception.
This algorithm serializes the children of
the node being serialized, not the node itself.この算法は、節点そのものではなく、直列化される節点の子供を直列化します。
Let s be a string, and initialize it to
the empty string.
-
For each child node of the node, in
tree order, run the following steps:
Let current node be the child node
being processed.
-
Append the appropriate string from the following list to
s:
- If current node is an
Element
-
Append a U+003C LESS-THAN SIGN (<)
character, followed by the element's tag name. (For nodes
created by the HTML parser, Document.createElement(), or Document.renameNode(), the tag name will be
lowercase.)
For each attribute that the element has, append a U+0020
SPACE character, the attribute's name (which, for attributes
set by the HTML parser or by Element.setAttributeNode() or Element.setAttribute(), will be lowercase), a
U+003D EQUALS SIGN (=) character, a
U+0022 QUOTATION MARK (")
character, the attribute's value, escaped as described below in attribute
mode, and a second U+0022 QUOTATION MARK (") character.
While the exact order of attributes is UA-defined, and may
depend on factors such as the order that the attributes were
given in the original markup, the sort order must be stable,
such that consecutive invocations of this algorithm serialize an
element's attributes in the same order.
Append a U+003E GREATER-THAN SIGN (>)
character.
If current node is an
area, base, basefont,
bgsound, br, col,
embed, frame, hr,
img, input, link,
meta, param, spacer, or
wbr element, then continue on to the next child
node at this point.
If current node is a pre
textarea, or listing element, append
a U+000A LINE FEED (LF) character.
Append the value of running the HTML fragment
serialization algorithm on the current
node element (thus recursing into this algorithm for
that element), followed by a U+003C LESS-THAN SIGN (<) character, a U+002F SOLIDUS (/) character, the element's tag name again,
and finally a U+003E GREATER-THAN SIGN (>) character.
- If current node is a
Text or CDATASection
node
-
If one of the ancestors of current node
is a style, script,
xmp, iframe, noembed,
noframes, noscript, or
plaintext element, then append the value of current node's data DOM
attribute literally.
Otherwise, append the value of current
node's data DOM attribute, escaped as described
below.
- If current node is a
Comment
-
Append the literal string <!-- (U+003C
LESS-THAN SIGN, U+0021 EXCLAMATION MARK, U+002D HYPHEN-MINUS,
U+002D HYPHEN-MINUS), followed by the value of current node's data DOM
attribute, followed by the literal string -->
(U+002D HYPHEN-MINUS, U+002D HYPHEN-MINUS, U+003E GREATER-THAN
SIGN).
- If current node is a
ProcessingInstruction
-
Append the literal string <? (U+003C
LESS-THAN SIGN, U+003F QUESTION MARK), followed by the value
of current node's target DOM attribute, followed by a single
U+0020 SPACE character, followed by the value of current node's data DOM
attribute, followed by a single U+003E GREATER-THAN SIGN
character ('>').
- If current node is a
DocumentType
-
Append the literal string <!DOCTYPE (U+003C
LESS-THAN SIGN, U+0021 EXCLAMATION MARK, U+0044 LATIN CAPITAL
LETTER D, U+004F LATIN CAPITAL LETTER O, U+0043 LATIN CAPITAL
LETTER C, U+0054 LATIN CAPITAL LETTER T, U+0059 LATIN CAPITAL
LETTER Y, U+0050 LATIN CAPITAL LETTER P, U+0045 LATIN CAPITAL
LETTER E), followed by a space (U+0020 SPACE), followed by the
value of current node's name DOM attribute, followed by the literal
string > (U+003E GREATER-THAN SIGN).
Other node types (e.g. Attr) cannot
occur as children of elements. If, despite this, they somehow do
occur, this algorithm must raise an
INVALID_STATE_ERR exception.
The result of the algorithm is the string s.
Escaping a string (for the
purposes of the algorithm above) consists of replacing any
occurrences of the "&" character by the
string "&", any occurrences of the
U+00A0 NO-BREAK SPACE character by the string " ", and, if the algorithm was invoked in
the attribute mode, any occurrences of the """ character by the string """, or if it was not, any occurrences of
the "<" character by the string "<", any occurrences of the ">" character by the string ">".
Entity reference nodes are assumed to be expanded by the user
agent, and are therefore not covered in the algorithm above.
It is possible that the output of this algorithm, if
parsed with an HTML parser, will not return the
original tree structure. For instance, if a textarea
element to which a Comment node has been
appended is serialized and the output is then reparsed, the comment
will end up being displayed in the text field. Similarly, if, as a
result of DOM manipulation, an element contains a comment that
contains the literal string "-->", then
when the result of serializing the element is parsed, the comment
will be truncated at that point and the rest of the comment will be
interpreted as markup. More examples would be making a
script element contain a text node with the text string
"</script>", or having a p element that
contains a ul element (as the ul element's
start tag would imply the end
tag for the p).
8.5 Parsing HTML fragments8.5 HTML 素片の構文解析
The following steps form the HTML fragment parsing
algorithm. The algorithm takes as input a DOM
Element, referred to as the context
element, which gives the context for the parser, as well as input, a string to parse, and returns a list of zero
or more nodes.
Parts marked fragment case in algorithms
in the parser section are parts that only occur if the parser was
created for the purposes of this algorithm. The algorithms have been
annotated with such markings for informational purposes only; such
markings have no normative weight. If it is possible for a condition
described as a fragment case to occur even when the
parser wasn't created for the purposes of handling this algorithm,
then that is an error in the specification.
-
Create a new Document node, and mark it as being
an HTML document.
-
Create a new HTML parser, and associate it with
the just created Document node.
-
Set the HTML parser's tokenization
stage's content model flag according to the context element, as follows:
- If it is a
title or textarea
element
- Set the content model flag to
the RCDATA state.
- If it is a
style, script,
xmp, iframe, noembed, or
noframes element
- Set the content model flag to
the CDATA state.
- If it is a
noscript element
- If the scripting flag is enabled, set the
content model flag to the CDATA
state. Otherwise, set the content model flag to the
PCDATA state.
- If it is a
plaintext element
- Set the content model flag to
PLAINTEXT.
- Otherwiseそれ以外の場合
- Set the content model flag to the PCDATA
state.
-
Let root be a new html element
with no attributes.
-
Append the element root to the
Document node created above.
-
Set up the parser's stack of open elements so that
it contains just the single element root.
-
Reset the
parser's insertion mode appropriately.
The parser will reference the context element as part of that algorithm.
-
Set the parser's form element pointer
to the nearest node to the context element
that is a form element (going straight up the
ancestor chain, and including the element itself, if it is a
form element), or, if there is no such
form element, to null.
-
Place into the input stream for the HTML
parser just created the input.
-
Start the parser and let it run until it has consumed all the
characters just inserted into the input stream.
-
Return all the child nodes of root,
preserving the document order.
8.6 Named character references8.6 名前付き文字参照
This table lists the character reference names that are supported
by HTML, and the code points to which they refer. It is referenced
by the previous sections.この表は、 HTML が対応している文字参照の名前と、その参照する符号位置を列挙しています。
この表は前の節から参照されています。
| Name 名前 | Character 文字 |
|---|
AElig; | U+000C6 |
AElig | U+000C6 |
AMP; | U+00026 |
AMP | U+00026 |
Aacute; | U+000C1 |
Aacute | U+000C1 |
Abreve; | U+00102 |
Acirc; | U+000C2 |
Acirc | U+000C2 |
Acy; | U+00410 |
Afr; | U+1D504 |
Agrave; | U+000C0 |
Agrave | U+000C0 |
Alpha; | U+00391 |
Amacr; | U+00100 |
And; | U+02A53 |
Aogon; | U+00104 |
Aopf; | U+1D538 |
ApplyFunction; | U+02061 |
Aring; | U+000C5 |
Aring | U+000C5 |
Ascr; | U+1D49C |
Assign; | U+02254 |
Atilde; | U+000C3 |
Atilde | U+000C3 |
Auml; | U+000C4 |
Auml | U+000C4 |
Backslash; | U+02216 |
Barv; | U+02AE7 |
Barwed; | U+02306 |
Bcy; | U+00411 |
Because; | U+02235 |
Bernoullis; | U+0212C |
Beta; | U+00392 |
Bfr; | U+1D505 |
Bopf; | U+1D539 |
Breve; | U+002D8 |
Bscr; | U+0212C |
Bumpeq; | U+0224E |
CHcy; | U+00427 |
COPY; | U+000A9 |
COPY | U+000A9 |
Cacute; | U+00106 |
Cap; | U+022D2 |
CapitalDifferentialD; | U+02145 |
Cayleys; | U+0212D |
Ccaron; | U+0010C |
Ccedil; | U+000C7 |
Ccedil | U+000C7 |
Ccirc; | U+00108 |
Cconint; | U+02230 |
Cdot; | U+0010A |
Cedilla; | U+000B8 |
CenterDot; | U+000B7 |
Cfr; | U+0212D |
Chi; | U+003A7 |
CircleDot; | U+02299 |
CircleMinus; | U+02296 |
CirclePlus; | U+02295 |
CircleTimes; | U+02297 |
ClockwiseContourIntegral; | U+02232 |
CloseCurlyDoubleQuote; | U+0201D |
CloseCurlyQuote; | U+02019 |
Colon; | U+02237 |
Colone; | U+02A74 |
Congruent; | U+02261 |
Conint; | U+0222F |
ContourIntegral; | U+0222E |
Copf; | U+02102 |
Coproduct; | U+02210 |
CounterClockwiseContourIntegral; | U+02233 |
Cross; | U+02A2F |
Cscr; | U+1D49E |
Cup; | U+022D3 |
CupCap; | U+0224D |
DD; | U+02145 |
DDotrahd; | U+02911 |
DJcy; | U+00402 |
DScy; | U+00405 |
DZcy; | U+0040F |
Dagger; | U+02021 |
Darr; | U+021A1 |
Dashv; | U+02AE4 |
Dcaron; | U+0010E |
Dcy; | U+00414 |
Del; | U+02207 |
Delta; | U+00394 |
Dfr; | U+1D507 |
DiacriticalAcute; | U+000B4 |
DiacriticalDot; | U+002D9 |
DiacriticalDoubleAcute; | U+002DD |
DiacriticalGrave; | U+00060 |
DiacriticalTilde; | U+002DC |
Diamond; | U+022C4 |
DifferentialD; | U+02146 |
Dopf; | U+1D53B |
Dot; | U+000A8 |
DotDot; | U+020DC |
DotEqual; | U+02250 |
DoubleContourIntegral; | U+0222F |
DoubleDot; | U+000A8 |
DoubleDownArrow; | U+021D3 |
DoubleLeftArrow; | U+021D0 |
DoubleLeftRightArrow; | U+021D4 |
DoubleLeftTee; | U+02AE4 |
DoubleLongLeftArrow; | U+027F8 |
DoubleLongLeftRightArrow; | U+027FA |
DoubleLongRightArrow; | U+027F9 |
DoubleRightArrow; | U+021D2 |
DoubleRightTee; | U+022A8 |
DoubleUpArrow; | U+021D1 |
DoubleUpDownArrow; | U+021D5 |
DoubleVerticalBar; | U+02225 |
DownArrow; | U+02193 |
DownArrowBar; | U+02913 |
DownArrowUpArrow; | U+021F5 |
DownBreve; | U+00311 |
DownLeftRightVector; | U+02950 |
DownLeftTeeVector; | U+0295E |
DownLeftVector; | U+021BD |
DownLeftVectorBar; | U+02956 |
DownRightTeeVector; | U+0295F |
DownRightVector; | U+021C1 |
DownRightVectorBar; | U+02957 |
DownTee; | U+022A4 |
DownTeeArrow; | U+021A7 |
Downarrow; | U+021D3 |
Dscr; | U+1D49F |
Dstrok; | U+00110 |
ENG; | U+0014A |
ETH; | U+000D0 |
ETH | U+000D0 |
Eacute; | U+000C9 |
Eacute | U+000C9 |
Ecaron; | U+0011A |
Ecirc; | U+000CA |
Ecirc | U+000CA |
Ecy; | U+0042D |
Edot; | U+00116 |
Efr; | U+1D508 |
Egrave; | U+000C8 |
Egrave | U+000C8 |
Element; | U+02208 |
Emacr; | U+00112 |
EmptySmallSquare; | U+025FB |
EmptyVerySmallSquare; | U+025AB |
Eogon; | U+00118 |
Eopf; | U+1D53C |
Epsilon; | U+00395 |
Equal; | U+02A75 |
EqualTilde; | U+02242 |
Equilibrium; | U+021CC |
Escr; | U+02130 |
Esim; | U+02A73 |
Eta; | U+00397 |
Euml; | U+000CB |
Euml | U+000CB |
Exists; | U+02203 |
ExponentialE; | U+02147 |
Fcy; | U+00424 |
Ffr; | U+1D509 |
FilledSmallSquare; | U+025FC |
FilledVerySmallSquare; | U+025AA |
Fopf; | U+1D53D |
ForAll; | U+02200 |
Fouriertrf; | U+02131 |
Fscr; | U+02131 |
GJcy; | U+00403 |
GT; | U+0003E |
GT | U+0003E |
Gamma; | U+00393 |
Gammad; | U+003DC |
Gbreve; | U+0011E |
Gcedil; | U+00122 |
Gcirc; | U+0011C |
Gcy; | U+00413 |
Gdot; | U+00120 |
Gfr; | U+1D50A |
Gg; | U+022D9 |
Gopf; | U+1D53E |
GreaterEqual; | U+02265 |
GreaterEqualLess; | U+022DB |
GreaterFullEqual; | U+02267 |
GreaterGreater; | U+02AA2 |
GreaterLess; | U+02277 |
GreaterSlantEqual; | U+02A7E |
GreaterTilde; | U+02273 |
Gscr; | U+1D4A2 |
Gt; | U+0226B |
HARDcy; | U+0042A |
Hacek; | U+002C7 |
Hat; | U+0005E |
Hcirc; | U+00124 |
Hfr; | U+0210C |
HilbertSpace; | U+0210B |
Hopf; | U+0210D |
HorizontalLine; | U+02500 |
Hscr; | U+0210B |
Hstrok; | U+00126 |
HumpDownHump; | U+0224E |
HumpEqual; | U+0224F |
IEcy; | U+00415 |
IJlig; | U+00132 |
IOcy; | U+00401 |
Iacute; | U+000CD |
Iacute | U+000CD |
Icirc; | U+000CE |
Icirc | U+000CE |
Icy; | U+00418 |
Idot; | U+00130 |
Ifr; | U+02111 |
Igrave; | U+000CC |
Igrave | U+000CC |
Im; | U+02111 |
Imacr; | U+0012A |
ImaginaryI; | U+02148 |
Implies; | U+021D2 |
Int; | U+0222C |
Integral; | U+0222B |
Intersection; | U+022C2 |
InvisibleComma; | U+02063 |
InvisibleTimes; | U+02062 |
Iogon; | U+0012E |
Iopf; | U+1D540 |
Iota; | U+00399 |
Iscr; | U+02110 |
Itilde; | U+00128 |
Iukcy; | U+00406 |
Iuml; | U+000CF |
Iuml | U+000CF |
Jcirc; | U+00134 |
Jcy; | U+00419 |
Jfr; | U+1D50D |
Jopf; | U+1D541 |
Jscr; | U+1D4A5 |
Jsercy; | U+00408 |
Jukcy; | U+00404 |
KHcy; | U+00425 |
KJcy; | U+0040C |
Kappa; | U+0039A |
Kcedil; | U+00136 |
Kcy; | U+0041A |
Kfr; | U+1D50E |
Kopf; | U+1D542 |
Kscr; | U+1D4A6 |
LJcy; | U+00409 |
LT; | U+0003C |
LT | U+0003C |
Lacute; | U+00139 |
Lambda; | U+0039B |
Lang; | U+027EA |
Laplacetrf; | U+02112 |
Larr; | U+0219E |
Lcaron; | U+0013D |
Lcedil; | U+0013B |
Lcy; | U+0041B |
LeftAngleBracket; | U+027E8 |
LeftArrow; | U+02190 |
LeftArrowBar; | U+021E4 |
LeftArrowRightArrow; | U+021C6 |
LeftCeiling; | U+02308 |
LeftDoubleBracket; | U+027E6 |
LeftDownTeeVector; | U+02961 |
LeftDownVector; | U+021C3 |
LeftDownVectorBar; | U+02959 |
LeftFloor; | U+0230A |
LeftRightArrow; | U+02194 |
LeftRightVector; | U+0294E |
LeftTee; | U+022A3 |
LeftTeeArrow; | U+021A4 |
LeftTeeVector; | U+0295A |
LeftTriangle; | U+022B2 |
LeftTriangleBar; | U+029CF |
LeftTriangleEqual; | U+022B4 |
LeftUpDownVector; | U+02951 |
LeftUpTeeVector; | U+02960 |
LeftUpVector; | U+021BF |
LeftUpVectorBar; | U+02958 |
LeftVector; | U+021BC |
LeftVectorBar; | U+02952 |
Leftarrow; | U+021D0 |
Leftrightarrow; | U+021D4 |
LessEqualGreater; | U+022DA |
LessFullEqual; | U+02266 |
LessGreater; | U+02276 |
LessLess; | U+02AA1 |
LessSlantEqual; | U+02A7D |
LessTilde; | U+02272 |
Lfr; | U+1D50F |
Ll; | U+022D8 |
Lleftarrow; | U+021DA |
Lmidot; | U+0013F |
LongLeftArrow; | U+027F5 |
LongLeftRightArrow; | U+027F7 |
LongRightArrow; | U+027F6 |
Longleftarrow; | U+027F8 |
Longleftrightarrow; | U+027FA |
Longrightarrow; | U+027F9 |
Lopf; | U+1D543 |
LowerLeftArrow; | U+02199 |
LowerRightArrow; | U+02198 |
Lscr; | U+02112 |
Lsh; | U+021B0 |
Lstrok; | U+00141 |
Lt; | U+0226A |
Map; | U+02905 |
Mcy; | U+0041C |
MediumSpace; | U+0205F |
Mellintrf; | U+02133 |
Mfr; | U+1D510 |
MinusPlus; | U+02213 |
Mopf; | U+1D544 |
Mscr; | U+02133 |
Mu; | U+0039C |
NJcy; | U+0040A |
Nacute; | U+00143 |
Ncaron; | U+00147 |
Ncedil; | U+00145 |
Ncy; | U+0041D |
NegativeMediumSpace; | U+0200B |
NegativeThickSpace; | U+0200B |
NegativeThinSpace; | U+0200B |
NegativeVeryThinSpace; | U+0200B |
NestedGreaterGreater; | U+0226B |
NestedLessLess; | U+0226A |
NewLine; | U+0000A |
Nfr; | U+1D511 |
NoBreak; | U+02060 |
NonBreakingSpace; | U+000A0 |
Nopf; | U+02115 |
Not; | U+02AEC |
NotCongruent; | U+02262 |
NotCupCap; | U+0226D |
NotDoubleVerticalBar; | U+02226 |
NotElement; | U+02209 |
NotEqual; | U+02260 |
NotExists; | U+02204 |
NotGreater; | U+0226F |
NotGreaterEqual; | U+02271 |
NotGreaterLess; | U+02279 |
NotGreaterTilde; | U+02275 |
NotLeftTriangle; | U+022EA |
NotLeftTriangleEqual; | U+022EC |
NotLess; | U+0226E |
NotLessEqual; | U+02270 |
NotLessGreater; | U+02278 |
NotLessTilde; | U+02274 |
NotPrecedes; | U+02280 |
NotPrecedesSlantEqual; | U+022E0 |
NotReverseElement; | U+0220C |
NotRightTriangle; | U+022EB |
NotRightTriangleEqual; | U+022ED |
NotSquareSubsetEqual; | U+022E2 |
NotSquareSupersetEqual; | U+022E3 |
NotSubsetEqual; | U+02288 |
NotSucceeds; | U+02281 |
NotSucceedsSlantEqual; | U+022E1 |
NotSupersetEqual; | U+02289 |
NotTilde; | U+02241 |
NotTildeEqual; | U+02244 |
NotTildeFullEqual; | U+02247 |
NotTildeTilde; | U+02249 |
NotVerticalBar; | U+02224 |
Nscr; | U+1D4A9 |
Ntilde; | U+000D1 |
Ntilde | U+000D1 |
Nu; | U+0039D |
OElig; | U+00152 |
Oacute; | U+000D3 |
Oacute | U+000D3 |
Ocirc; | U+000D4 |
Ocirc | U+000D4 |
Ocy; | U+0041E |
Odblac; | U+00150 |
Ofr; | U+1D512 |
Ograve; | U+000D2 |
Ograve | U+000D2 |
Omacr; | U+0014C |
Omega; | U+003A9 |
Omicron; | U+0039F |
Oopf; | U+1D546 |
OpenCurlyDoubleQuote; | U+0201C |
OpenCurlyQuote; | U+02018 |
Or; | U+02A54 |
Oscr; | U+1D4AA |
Oslash; | U+000D8 |
Oslash | U+000D8 |
Otilde; | U+000D5 |
Otilde | U+000D5 |
Otimes; | U+02A37 |
Ouml; | U+000D6 |
Ouml | U+000D6 |
OverBar; | U+000AF |
OverBrace; | U+023DE |
OverBracket; | U+023B4 |
OverParenthesis; | U+023DC |
PartialD; | U+02202 |
Pcy; | U+0041F |
Pfr; | U+1D513 |
Phi; | U+003A6 |
Pi; | U+003A0 |
PlusMinus; | U+000B1 |
Poincareplane; | U+0210C |
Popf; | U+02119 |
Pr; | U+02ABB |
Precedes; | U+0227A |
PrecedesEqual; | U+02AAF |
PrecedesSlantEqual; | U+0227C |
PrecedesTilde; | U+0227E |
Prime; | U+02033 |
Product; | U+0220F |
Proportion; | U+02237 |
Proportional; | U+0221D |
Pscr; | U+1D4AB |
Psi; | U+003A8 |
QUOT; | U+00022 |
QUOT | U+00022 |
Qfr; | U+1D514 |
Qopf; | U+0211A |
Qscr; | U+1D4AC |
RBarr; | U+02910 |
REG; | U+000AE |
REG | U+000AE |
Racute; | U+00154 |
Rang; | U+027EB |
Rarr; | U+021A0 |
Rarrtl; | U+02916 |
Rcaron; | U+00158 |
Rcedil; | U+00156 |
Rcy; | U+00420 |
Re; | U+0211C |
ReverseElement; | U+0220B |
ReverseEquilibrium; | U+021CB |
ReverseUpEquilibrium; | U+0296F |
Rfr; | U+0211C |
Rho; | U+003A1 |
RightAngleBracket; | U+027E9 |
RightArrow; | U+02192 |
RightArrowBar; | U+021E5 |
RightArrowLeftArrow; | U+021C4 |
RightCeiling; | U+02309 |
RightDoubleBracket; | U+027E7 |
RightDownTeeVector; | U+0295D |
RightDownVector; | U+021C2 |
RightDownVectorBar; | U+02955 |
RightFloor; | U+0230B |
RightTee; | U+022A2 |
RightTeeArrow; | U+021A6 |
RightTeeVector; | U+0295B |
RightTriangle; | U+022B3 |
RightTriangleBar; | U+029D0 |
RightTriangleEqual; | U+022B5 |
RightUpDownVector; | U+0294F |
RightUpTeeVector; | U+0295C |
RightUpVector; | U+021BE |
RightUpVectorBar; | U+02954 |
RightVector; | U+021C0 |
RightVectorBar; | U+02953 |
Rightarrow; | U+021D2 |
Ropf; | U+0211D |
RoundImplies; | U+02970 |
Rrightarrow; | U+021DB |
Rscr; | U+0211B |
Rsh; | U+021B1 |
RuleDelayed; | U+029F4 |
SHCHcy; | U+00429 |
SHcy; | U+00428 |
SOFTcy; | U+0042C |
Sacute; | U+0015A |
Sc; | U+02ABC |
Scaron; | U+00160 |
Scedil; | U+0015E |
Scirc; | U+0015C |
Scy; | U+00421 |
Sfr; | U+1D516 |
ShortDownArrow; | U+02193 |
ShortLeftArrow; | U+02190 |
ShortRightArrow; | U+02192 |
ShortUpArrow; | U+02191 |
Sigma; | U+003A3 |
SmallCircle; | U+02218 |
Sopf; | U+1D54A |
Sqrt; | U+0221A |
Square; | U+025A1 |
SquareIntersection; | U+02293 |
SquareSubset; | U+0228F |
SquareSubsetEqual; | U+02291 |
SquareSuperset; | U+02290 |
SquareSupersetEqual; | U+02292 |
SquareUnion; | U+02294 |
Sscr; | U+1D4AE |
Star; | U+022C6 |
Sub; | U+022D0 |
Subset; | U+022D0 |
SubsetEqual; | U+02286 |
Succeeds; | U+0227B |
SucceedsEqual; | U+02AB0 |
SucceedsSlantEqual; | U+0227D |
SucceedsTilde; | U+0227F |
SuchThat; | U+0220B |
Sum; | U+02211 |
Sup; | U+022D1 |
Superset; | U+02283 |
SupersetEqual; | U+02287 |
Supset; | U+022D1 |
THORN; | U+000DE |
THORN | U+000DE |
TRADE; | U+02122 |
TSHcy; | U+0040B |
TScy; | U+00426 |
Tab; | U+00009 |
Tau; | U+003A4 |
Tcaron; | U+00164 |
Tcedil; | U+00162 |
Tcy; | U+00422 |
Tfr; | U+1D517 |
Therefore; | U+02234 |
Theta; | U+00398 |
ThinSpace; | U+02009 |
Tilde; | U+0223C |
TildeEqual; | U+02243 |
TildeFullEqual; | U+02245 |
TildeTilde; | U+02248 |
Topf; | U+1D54B |
TripleDot; | U+020DB |
Tscr; | U+1D4AF |
Tstrok; | U+00166 |
Uacute; | U+000DA |
Uacute | U+000DA |
Uarr; | U+0219F |
Uarrocir; | U+02949 |
Ubrcy; | U+0040E |
Ubreve; | U+0016C |
Ucirc; | U+000DB |
Ucirc | U+000DB |
Ucy; | U+00423 |
Udblac; | U+00170 |
Ufr; | U+1D518 |
Ugrave; | U+000D9 |
Ugrave | U+000D9 |
Umacr; | U+0016A |
UnderBar; | U+00332 |
UnderBrace; | U+023DF |
UnderBracket; | U+023B5 |
UnderParenthesis; | U+023DD |
Union; | U+022C3 |
UnionPlus; | U+0228E |
Uogon; | U+00172 |
Uopf; | U+1D54C |
UpArrow; | U+02191 |
UpArrowBar; | U+02912 |
UpArrowDownArrow; | U+021C5 |
UpDownArrow; | U+02195 |
UpEquilibrium; | U+0296E |
UpTee; | U+022A5 |
UpTeeArrow; | U+021A5 |
Uparrow; | U+021D1 |
Updownarrow; | U+021D5 |
UpperLeftArrow; | U+02196 |
UpperRightArrow; | U+02197 |
Upsi; | U+003D2 |
Upsilon; | U+003A5 |
Uring; | U+0016E |
Uscr; | U+1D4B0 |
Utilde; | U+00168 |
Uuml; | U+000DC |
Uuml | U+000DC |
VDash; | U+022AB |
Vbar; | U+02AEB |
Vcy; | U+00412 |
Vdash; | U+022A9 |
Vdashl; | U+02AE6 |
Vee; | U+022C1 |
Verbar; | U+02016 |
Vert; | U+02016 |
VerticalBar; | U+02223 |
VerticalLine; | U+0007C |
VerticalSeparator; | U+02758 |
VerticalTilde; | U+02240 |
VeryThinSpace; | U+0200A |
Vfr; | U+1D519 |
Vopf; | U+1D54D |
Vscr; | U+1D4B1 |
Vvdash; | U+022AA |
Wcirc; | U+00174 |
Wedge; | U+022C0 |
Wfr; | U+1D51A |
Wopf; | U+1D54E |
Wscr; | U+1D4B2 |
Xfr; | U+1D51B |
Xi; | U+0039E |
Xopf; | U+1D54F |
Xscr; | U+1D4B3 |
YAcy; | U+0042F |
YIcy; | U+00407 |
YUcy; | U+0042E |
Yacute; | U+000DD |
Yacute | U+000DD |
Ycirc; | U+00176 |
Ycy; | U+0042B |
Yfr; | U+1D51C |
Yopf; | U+1D550 |
Yscr; | U+1D4B4 |
Yuml; | U+00178 |
ZHcy; | U+00416 |
Zacute; | U+00179 |
Zcaron; | U+0017D |
Zcy; | U+00417 |
Zdot; | U+0017B |
ZeroWidthSpace; | U+0200B |
Zeta; | U+00396 |
Zfr; | U+02128 |
Zopf; | U+02124 |
Zscr; | U+1D4B5 |
aacute; | U+000E1 |
aacute | U+000E1 |
abreve; | U+00103 |
ac; | U+0223E |
acd; | U+0223F |
acirc; | U+000E2 |
acirc | U+000E2 |
acute; | U+000B4 |
acute | U+000B4 |
acy; | U+00430 |
aelig; | U+000E6 |
aelig | U+000E6 |
af; | U+02061 |
afr; | U+1D51E |
agrave; | U+000E0 |
agrave | U+000E0 |
alefsym; | U+02135 |
aleph; | U+02135 |
alpha; | U+003B1 |
amacr; | U+00101 |
amalg; | U+02A3F |
amp; | U+00026 |
amp | U+00026 |
and; | U+02227 |
andand; | U+02A55 |
andd; | U+02A5C |
andslope; | U+02A58 |
andv; | U+02A5A |
ang; | U+02220 |
ange; | U+029A4 |
angle; | U+02220 |
angmsd; | U+02221 |
angmsdaa; | U+029A8 |
angmsdab; | U+029A9 |
angmsdac; | U+029AA |
angmsdad; | U+029AB |
angmsdae; | U+029AC |
angmsdaf; | U+029AD |
angmsdag; | U+029AE |
angmsdah; | U+029AF |
angrt; | U+0221F |
angrtvb; | U+022BE |
angrtvbd; | U+0299D |
angsph; | U+02222 |
angst; | U+0212B |
angzarr; | U+0237C |
aogon; | U+00105 |
aopf; | U+1D552 |
ap; | U+02248 |
apE; | U+02A70 |
apacir; | U+02A6F |
ape; | U+0224A |
apid; | U+0224B |
apos; | U+00027 |
approx; | U+02248 |
approxeq; | U+0224A |
aring; | U+000E5 |
aring | U+000E5 |
ascr; | U+1D4B6 |
ast; | U+0002A |
asymp; | U+02248 |
asympeq; | U+0224D |
atilde; | U+000E3 |
atilde | U+000E3 |
auml; | U+000E4 |
auml | U+000E4 |
awconint; | U+02233 |
awint; | U+02A11 |
bNot; | U+02AED |
backcong; | U+0224C |
backepsilon; | U+003F6 |
backprime; | U+02035 |
backsim; | U+0223D |
backsimeq; | U+022CD |
barvee; | U+022BD |
barwed; | U+02305 |
barwedge; | U+02305 |
bbrk; | U+023B5 |
bbrktbrk; | U+023B6 |
bcong; | U+0224C |
bcy; | U+00431 |
bdquo; | U+0201E |
becaus; | U+02235 |
because; | U+02235 |
bemptyv; | U+029B0 |
bepsi; | U+003F6 |
bernou; | U+0212C |
beta; | U+003B2 |
beth; | U+02136 |
between; | U+0226C |
bfr; | U+1D51F |
bigcap; | U+022C2 |
bigcirc; | U+025EF |
bigcup; | U+022C3 |
bigodot; | U+02A00 |
bigoplus; | U+02A01 |
bigotimes; | U+02A02 |
bigsqcup; | U+02A06 |
bigstar; | U+02605 |
bigtriangledown; | U+025BD |
bigtriangleup; | U+025B3 |
biguplus; | U+02A04 |
bigvee; | U+022C1 |
bigwedge; | U+022C0 |
bkarow; | U+0290D |
blacklozenge; | U+029EB |
blacksquare; | U+025AA |
blacktriangle; | U+025B4 |
blacktriangledown; | U+025BE |
blacktriangleleft; | U+025C2 |
blacktriangleright; | U+025B8 |
blank; | U+02423 |
blk12; | U+02592 |
blk14; | U+02591 |
blk34; | U+02593 |
block; | U+02588 |
bnot; | U+02310 |
bopf; | U+1D553 |
bot; | U+022A5 |
bottom; | U+022A5 |
bowtie; | U+022C8 |
boxDL; | U+02557 |
boxDR; | U+02554 |
boxDl; | U+02556 |
boxDr; | U+02553 |
boxH; | U+02550 |
boxHD; | U+02566 |
boxHU; | U+02569 |
boxHd; | U+02564 |
boxHu; | U+02567 |
boxUL; | U+0255D |
boxUR; | U+0255A |
boxUl; | U+0255C |
boxUr; | U+02559 |
boxV; | U+02551 |
boxVH; | U+0256C |
boxVL; | U+02563 |
boxVR; | U+02560 |
boxVh; | U+0256B |
boxVl; | U+02562 |
boxVr; | U+0255F |
boxbox; | U+029C9 |
boxdL; | U+02555 |
boxdR; | U+02552 |
boxdl; | U+02510 |
boxdr; | U+0250C |
boxh; | U+02500 |
boxhD; | U+02565 |
boxhU; | U+02568 |
boxhd; | U+0252C |
boxhu; | U+02534 |
boxminus; | U+0229F |
boxplus; | U+0229E |
boxtimes; | U+022A0 |
boxuL; | U+0255B |
boxuR; | U+02558 |
boxul; | U+02518 |
boxur; | U+02514 |
boxv; | U+02502 |
boxvH; | U+0256A |
boxvL; | U+02561 |
boxvR; | U+0255E |
boxvh; | U+0253C |
boxvl; | U+02524 |
boxvr; | U+0251C |
bprime; | U+02035 |
breve; | U+002D8 |
brvbar; | U+000A6 |
brvbar | U+000A6 |
bscr; | U+1D4B7 |
bsemi; | U+0204F |
bsim; | U+0223D |
bsime; | U+022CD |
bsol; | U+0005C |
bsolb; | U+029C5 |
bull; | U+02022 |
bullet; | U+02022 |
bump; | U+0224E |
bumpE; | U+02AAE |
bumpe; | U+0224F |
bumpeq; | U+0224F |
cacute; | U+00107 |
cap; | U+02229 |
capand; | U+02A44 |
capbrcup; | U+02A49 |
capcap; | U+02A4B |
capcup; | U+02A47 |
capdot; | U+02A40 |
caret; | U+02041 |
caron; | U+002C7 |
ccaps; | U+02A4D |
ccaron; | U+0010D |
ccedil; | U+000E7 |
ccedil | U+000E7 |
ccirc; | U+00109 |
ccups; | U+02A4C |
ccupssm; | U+02A50 |
cdot; | U+0010B |
cedil; | U+000B8 |
cedil | U+000B8 |
cemptyv; | U+029B2 |
cent; | U+000A2 |
cent | U+000A2 |
centerdot; | U+000B7 |
cfr; | U+1D520 |
chcy; | U+00447 |
check; | U+02713 |
checkmark; | U+02713 |
chi; | U+003C7 |
cir; | U+025CB |
cirE; | U+029C3 |
circ; | U+002C6 |
circeq; | U+02257 |
circlearrowleft; | U+021BA |
circlearrowright; | U+021BB |
circledR; | U+000AE |
circledS; | U+024C8 |
circledast; | U+0229B |
circledcirc; | U+0229A |
circleddash; | U+0229D |
cire; | U+02257 |
cirfnint; | U+02A10 |
cirmid; | U+02AEF |
cirscir; | U+029C2 |
clubs; | U+02663 |
clubsuit; | U+02663 |
colon; | U+0003A |
colone; | U+02254 |
coloneq; | U+02254 |
comma; | U+0002C |
commat; | U+00040 |
comp; | U+02201 |
compfn; | U+02218 |
complement; | U+02201 |
complexes; | U+02102 |
cong; | U+02245 |
congdot; | U+02A6D |
conint; | U+0222E |
copf; | U+1D554 |
coprod; | U+02210 |
copy; | U+000A9 |
copy | U+000A9 |
copysr; | U+02117 |
crarr; | U+021B5 |
cross; | U+02717 |
cscr; | U+1D4B8 |
csub; | U+02ACF |
csube; | U+02AD1 |
csup; | U+02AD0 |
csupe; | U+02AD2 |
ctdot; | U+022EF |
cudarrl; | U+02938 |
cudarrr; | U+02935 |
cuepr; | U+022DE |
cuesc; | U+022DF |
cularr; | U+021B6 |
cularrp; | U+0293D |
cup; | U+0222A |
cupbrcap; | U+02A48 |
cupcap; | U+02A46 |
cupcup; | U+02A4A |
cupdot; | U+0228D |
cupor; | U+02A45 |
curarr; | U+021B7 |
curarrm; | U+0293C |
curlyeqprec; | U+022DE |
curlyeqsucc; | U+022DF |
curlyvee; | U+022CE |
curlywedge; | U+022CF |
curren; | U+000A4 |
curren | U+000A4 |
curvearrowleft; | U+021B6 |
curvearrowright; | U+021B7 |
cuvee; | U+022CE |
cuwed; | U+022CF |
cwconint; | U+02232 |
cwint; | U+02231 |
cylcty; | U+0232D |
dArr; | U+021D3 |
dHar; | U+02965 |
dagger; | U+02020 |
daleth; | U+02138 |
darr; | U+02193 |
dash; | U+02010 |
dashv; | U+022A3 |
dbkarow; | U+0290F |
dblac; | U+002DD |
dcaron; | U+0010F |
dcy; | U+00434 |
dd; | U+02146 |
ddagger; | U+02021 |
ddarr; | U+021CA |
ddotseq; | U+02A77 |
deg; | U+000B0 |
deg | U+000B0 |
delta; | U+003B4 |
demptyv; | U+029B1 |
dfisht; | U+0297F |
dfr; | U+1D521 |
dharl; | U+021C3 |
dharr; | U+021C2 |
diam; | U+022C4 |
diamond; | U+022C4 |
diamondsuit; | U+02666 |
diams; | U+02666 |
die; | U+000A8 |
digamma; | U+003DD |
disin; | U+022F2 |
div; | U+000F7 |
divide; | U+000F7 |
divide | U+000F7 |
divideontimes; | U+022C7 |
divonx; | U+022C7 |
djcy; | U+00452 |
dlcorn; | U+0231E |
dlcrop; | U+0230D |
dollar; | U+00024 |
dopf; | U+1D555 |
dot; | U+002D9 |
doteq; | U+02250 |
doteqdot; | U+02251 |
dotminus; | U+02238 |
dotplus; | U+02214 |
dotsquare; | U+022A1 |
doublebarwedge; | U+02306 |
downarrow; | U+02193 |
downdownarrows; | U+021CA |
downharpoonleft; | U+021C3 |
downharpoonright; | U+021C2 |
drbkarow; | U+02910 |
drcorn; | U+0231F |
drcrop; | U+0230C |
dscr; | U+1D4B9 |
dscy; | U+00455 |
dsol; | U+029F6 |
dstrok; | U+00111 |
dtdot; | U+022F1 |
dtri; | U+025BF |
dtrif; | U+025BE |
duarr; | U+021F5 |
duhar; | U+0296F |
dwangle; | U+029A6 |
dzcy; | U+0045F |
dzigrarr; | U+027FF |
eDDot; | U+02A77 |
eDot; | U+02251 |
eacute; | U+000E9 |
eacute | U+000E9 |
easter; | U+02A6E |
ecaron; | U+0011B |
ecir; | U+02256 |
ecirc; | U+000EA |
ecirc | U+000EA |
ecolon; | U+02255 |
ecy; | U+0044D |
edot; | U+00117 |
ee; | U+02147 |
efDot; | U+02252 |
efr; | U+1D522 |
eg; | U+02A9A |
egrave; | U+000E8 |
egrave | U+000E8 |
egs; | U+02A96 |
egsdot; | U+02A98 |
el; | U+02A99 |
elinters; | U+023E7 |
ell; | U+02113 |
els; | U+02A95 |
elsdot; | U+02A97 |
emacr; | U+00113 |
empty; | U+02205 |
emptyset; | U+02205 |
emptyv; | U+02205 |
emsp13; | U+02004 |
emsp14; | U+02005 |
emsp; | U+02003 |
eng; | U+0014B |
ensp; | U+02002 |
eogon; | U+00119 |
eopf; | U+1D556 |
epar; | U+022D5 |
eparsl; | U+029E3 |
eplus; | U+02A71 |
epsi; | U+003F5 |
epsilon; | U+003B5 |
epsiv; | U+003B5 |
eqcirc; | U+02256 |
eqcolon; | U+02255 |
eqsim; | U+02242 |
eqslantgtr; | U+02A96 |
eqslantless; | U+02A95 |
equals; | U+0003D |
equest; | U+0225F |
equiv; | U+02261 |
equivDD; | U+02A78 |
eqvparsl; | U+029E5 |
erDot; | U+02253 |
erarr; | U+02971 |
escr; | U+0212F |
esdot; | U+02250 |
esim; | U+02242 |
eta; | U+003B7 |
eth; | U+000F0 |
eth | U+000F0 |
euml; | U+000EB |
euml | U+000EB |
euro; | U+020AC |
excl; | U+00021 |
exist; | U+02203 |
expectation; | U+02130 |
exponentiale; | U+02147 |
fallingdotseq; | U+02252 |
fcy; | U+00444 |
female; | U+02640 |
ffilig; | U+0FB03 |
fflig; | U+0FB00 |
ffllig; | U+0FB04 |
ffr; | U+1D523 |
filig; | U+0FB01 |
flat; | U+0266D |
fllig; | U+0FB02 |
fltns; | U+025B1 |
fnof; | U+00192 |
fopf; | U+1D557 |
forall; | U+02200 |
fork; | U+022D4 |
forkv; | U+02AD9 |
fpartint; | U+02A0D |
frac12; | U+000BD |
frac12 | U+000BD |
frac13; | U+02153 |
frac14; | U+000BC |
frac14 | U+000BC |
frac15; | U+02155 |
frac16; | U+02159 |
frac18; | U+0215B |
frac23; | U+02154 |
frac25; | U+02156 |
frac34; | U+000BE |
frac34 | U+000BE |
frac35; | U+02157 |
frac38; | U+0215C |
frac45; | U+02158 |
frac56; | U+0215A |
frac58; | U+0215D |
frac78; | U+0215E |
frasl; | U+02044 |
frown; | U+02322 |
fscr; | U+1D4BB |
gE; | U+02267 |
gEl; | U+02A8C |
gacute; | U+001F5 |
gamma; | U+003B3 |
gammad; | U+003DD |
gap; | U+02A86 |
gbreve; | U+0011F |
gcirc; | U+0011D |
gcy; | U+00433 |
gdot; | U+00121 |
ge; | U+02265 |
gel; | U+022DB |
geq; | U+02265 |
geqq; | U+02267 |
geqslant; | U+02A7E |
ges; | U+02A7E |
gescc; | U+02AA9 |
gesdot; | U+02A80 |
gesdoto; | U+02A82 |
gesdotol; | U+02A84 |
gesles; | U+02A94 |
gfr; | U+1D524 |
gg; | U+0226B |
ggg; | U+022D9 |
gimel; | U+02137 |
gjcy; | U+00453 |
gl; | U+02277 |
glE; | U+02A92 |
gla; | U+02AA5 |
glj; | U+02AA4 |
gnE; | U+02269 |
gnap; | U+02A8A |
gnapprox; | U+02A8A |
gne; | U+02A88 |
gneq; | U+02A88 |
gneqq; | U+02269 |
gnsim; | U+022E7 |
gopf; | U+1D558 |
grave; | U+00060 |
gscr; | U+0210A |
gsim; | U+02273 |
gsime; | U+02A8E |
gsiml; | U+02A90 |
gt; | U+0003E |
gt | U+0003E |
gtcc; | U+02AA7 |
gtcir; | U+02A7A |
gtdot; | U+022D7 |
gtlPar; | U+02995 |
gtquest; | U+02A7C |
gtrapprox; | U+02A86 |
gtrarr; | U+02978 |
gtrdot; | U+022D7 |
gtreqless; | U+022DB |
gtreqqless; | U+02A8C |
gtrless; | U+02277 |
gtrsim; | U+02273 |
hArr; | U+021D4 |
hairsp; | U+0200A |
half; | U+000BD |
hamilt; | U+0210B |
hardcy; | U+0044A |
harr; | U+02194 |
harrcir; | U+02948 |
harrw; | U+021AD |
hbar; | U+0210F |
hcirc; | U+00125 |
hearts; | U+02665 |
heartsuit; | U+02665 |
hellip; | U+02026 |
hercon; | U+022B9 |
hfr; | U+1D525 |
hksearow; | U+02925 |
hkswarow; | U+02926 |
hoarr; | U+021FF |
homtht; | U+0223B |
hookleftarrow; | U+021A9 |
hookrightarrow; | U+021AA |
hopf; | U+1D559 |
horbar; | U+02015 |
hscr; | U+1D4BD |
hslash; | U+0210F |
hstrok; | U+00127 |
hybull; | U+02043 |
hyphen; | U+02010 |
iacute; | U+000ED |
iacute | U+000ED |
ic; | U+02063 |
icirc; | U+000EE |
icirc | U+000EE |
icy; | U+00438 |
iecy; | U+00435 |
iexcl; | U+000A1 |
iexcl | U+000A1 |
iff; | U+021D4 |
ifr; | U+1D526 |
igrave; | U+000EC |
igrave | U+000EC |
ii; | U+02148 |
iiiint; | U+02A0C |
iiint; | U+0222D |
iinfin; | U+029DC |
iiota; | U+02129 |
ijlig; | U+00133 |
imacr; | U+0012B |
image; | U+02111 |
imagline; | U+02110 |
imagpart; | U+02111 |
imath; | U+00131 |
imof; | U+022B7 |
imped; | U+001B5 |
in; | U+02208 |
incare; | U+02105 |
infin; | U+0221E |
infintie; | U+029DD |
inodot; | U+00131 |
int; | U+0222B |
intcal; | U+022BA |
integers; | U+02124 |
intercal; | U+022BA |
intlarhk; | U+02A17 |
intprod; | U+02A3C |
iocy; | U+00451 |
iogon; | U+0012F |
iopf; | U+1D55A |
iota; | U+003B9 |
iprod; | U+02A3C |
iquest; | U+000BF |
iquest | U+000BF |
iscr; | U+1D4BE |
isin; | U+02208 |
isinE; | U+022F9 |
isindot; | U+022F5 |
isins; | U+022F4 |
isinsv; | U+022F3 |
isinv; | U+02208 |
it; | U+02062 |
itilde; | U+00129 |
iukcy; | U+00456 |
iuml; | U+000EF |
iuml | U+000EF |
jcirc; | U+00135 |
jcy; | U+00439 |
jfr; | U+1D527 |
jmath; | U+00237 |
jopf; | U+1D55B |
jscr; | U+1D4BF |
jsercy; | U+00458 |
jukcy; | U+00454 |
kappa; | U+003BA |
kappav; | U+003F0 |
kcedil; | U+00137 |
kcy; | U+0043A |
kfr; | U+1D528 |
kgreen; | U+00138 |
khcy; | U+00445 |
kjcy; | U+0045C |
kopf; | U+1D55C |
kscr; | U+1D4C0 |
lAarr; | U+021DA |
lArr; | U+021D0 |
lAtail; | U+0291B |
lBarr; | U+0290E |
lE; | U+02266 |
lEg; | U+02A8B |
lHar; | U+02962 |
lacute; | U+0013A |
laemptyv; | U+029B4 |
lagran; | U+02112 |
lambda; | U+003BB |
lang; | U+027E8 |
langd; | U+02991 |
langle; | U+027E8 |
lap; | U+02A85 |
laquo; | U+000AB |
laquo | U+000AB |
larr; | U+02190 |
larrb; | U+021E4 |
larrbfs; | U+0291F |
larrfs; | U+0291D |
larrhk; | U+021A9 |
larrlp; | U+021AB |
larrpl; | U+02939 |
larrsim; | U+02973 |
larrtl; | U+021A2 |
lat; | U+02AAB |
latail; | U+02919 |
late; | U+02AAD |
lbarr; | U+0290C |
lbbrk; | U+02772 |
lbrace; | U+0007B |
lbrack; | U+0005B |
lbrke; | U+0298B |
lbrksld; | U+0298F |
lbrkslu; | U+0298D |
lcaron; | U+0013E |
lcedil; | U+0013C |
lceil; | U+02308 |
lcub; | U+0007B |
lcy; | U+0043B |
ldca; | U+02936 |
ldquo; | U+0201C |
ldquor; | U+0201E |
ldrdhar; | U+02967 |
ldrushar; | U+0294B |
ldsh; | U+021B2 |
le; | U+02264 |
leftarrow; | U+02190 |
leftarrowtail; | U+021A2 |
leftharpoondown; | U+021BD |
leftharpoonup; | U+021BC |
leftleftarrows; | U+021C7 |
leftrightarrow; | U+02194 |
leftrightarrows; | U+021C6 |
leftrightharpoons; | U+021CB |
leftrightsquigarrow; | U+021AD |
leftthreetimes; | U+022CB |
leg; | U+022DA |
leq; | U+02264 |
leqq; | U+02266 |
leqslant; | U+02A7D |
les; | U+02A7D |
lescc; | U+02AA8 |
lesdot; | U+02A7F |
lesdoto; | U+02A81 |
lesdotor; | U+02A83 |
lesges; | U+02A93 |
lessapprox; | U+02A85 |
lessdot; | U+022D6 |
lesseqgtr; | U+022DA |
lesseqqgtr; | U+02A8B |
lessgtr; | U+02276 |
lesssim; | U+02272 |
lfisht; | U+0297C |
lfloor; | U+0230A |
lfr; | U+1D529 |
lg; | U+02276 |
lgE; | U+02A91 |
lhard; | U+021BD |
lharu; | U+021BC |
lharul; | U+0296A |
lhblk; | U+02584 |
ljcy; | U+00459 |
ll; | U+0226A |
llarr; | U+021C7 |
llcorner; | U+0231E |
llhard; | U+0296B |
lltri; | U+025FA |
lmidot; | U+00140 |
lmoust; | U+023B0 |
lmoustache; | U+023B0 |
lnE; | U+02268 |
lnap; | U+02A89 |
lnapprox; | U+02A89 |
lne; | U+02A87 |
lneq; | U+02A87 |
lneqq; | U+02268 |
lnsim; | U+022E6 |
loang; | U+027EC |
loarr; | U+021FD |
lobrk; | U+027E6 |
longleftarrow; | U+027F5 |
longleftrightarrow; | U+027F7 |
longmapsto; | U+027FC |
longrightarrow; | U+027F6 |
looparrowleft; | U+021AB |
looparrowright; | U+021AC |
lopar; | U+02985 |
lopf; | U+1D55D |
loplus; | U+02A2D |
lotimes; | U+02A34 |
lowast; | U+02217 |
lowbar; | U+0005F |
loz; | U+025CA |
lozenge; | U+025CA |
lozf; | U+029EB |
lpar; | U+00028 |
lparlt; | U+02993 |
lrarr; | U+021C6 |
lrcorner; | U+0231F |
lrhar; | U+021CB |
lrhard; | U+0296D |
lrm; | U+0200E |
lrtri; | U+022BF |
lsaquo; | U+02039 |
lscr; | U+1D4C1 |
lsh; | U+021B0 |
lsim; | U+02272 |
lsime; | U+02A8D |
lsimg; | U+02A8F |
lsqb; | U+0005B |
lsquo; | U+02018 |
lsquor; | U+0201A |
lstrok; | U+00142 |
lt; | U+0003C |
lt | U+0003C |
ltcc; | U+02AA6 |
ltcir; | U+02A79 |
ltdot; | U+022D6 |
lthree; | U+022CB |
ltimes; | U+022C9 |
ltlarr; | U+02976 |
ltquest; | U+02A7B |
ltrPar; | U+02996 |
ltri; | U+025C3 |
ltrie; | U+022B4 |
ltrif; | U+025C2 |
lurdshar; | U+0294A |
luruhar; | U+02966 |
mDDot; | U+0223A |
macr; | U+000AF |
macr | U+000AF |
male; | U+02642 |
malt; | U+02720 |
maltese; | U+02720 |
map; | U+021A6 |
mapsto; | U+021A6 |
mapstodown; | U+021A7 |
mapstoleft; | U+021A4 |
mapstoup; | U+021A5 |
marker; | U+025AE |
mcomma; | U+02A29 |
mcy; | U+0043C |
mdash; | U+02014 |
measuredangle; | U+02221 |
mfr; | U+1D52A |
mho; | U+02127 |
micro; | U+000B5 |
micro | U+000B5 |
mid; | U+02223 |
midast; | U+0002A |
midcir; | U+02AF0 |
middot; | U+000B7 |
middot | U+000B7 |
minus; | U+02212 |
minusb; | U+0229F |
minusd; | U+02238 |
minusdu; | U+02A2A |
mlcp; | U+02ADB |
mldr; | U+02026 |
mnplus; | U+02213 |
models; | U+022A7 |
mopf; | U+1D55E |
mp; | U+02213 |
mscr; | U+1D4C2 |
mstpos; | U+0223E |
mu; | U+003BC |
multimap; | U+022B8 |
mumap; | U+022B8 |
nLeftarrow; | U+021CD |
nLeftrightarrow; | U+021CE |
nRightarrow; | U+021CF |
nVDash; | U+022AF |
nVdash; | U+022AE |
nabla; | U+02207 |
nacute; | U+00144 |
nap; | U+02249 |
napos; | U+00149 |
napprox; | U+02249 |
natur; | U+0266E |
natural; | U+0266E |
naturals; | U+02115 |
nbsp; | U+000A0 |
nbsp | U+000A0 |
ncap; | U+02A43 |
ncaron; | U+00148 |
ncedil; | U+00146 |
ncong; | U+02247 |
ncup; | U+02A42 |
ncy; | U+0043D |
ndash; | U+02013 |
ne; | U+02260 |
neArr; | U+021D7 |
nearhk; | U+02924 |
nearr; | U+02197 |
nearrow; | U+02197 |
nequiv; | U+02262 |
nesear; | U+02928 |
nexist; | U+02204 |
nexists; | U+02204 |
nfr; | U+1D52B |
nge; | U+02271 |
ngeq; | U+02271 |
ngsim; | U+02275 |
ngt; | U+0226F |
ngtr; | U+0226F |
nhArr; | U+021CE |
nharr; | U+021AE |
nhpar; | U+02AF2 |
ni; | U+0220B |
nis; | U+022FC |
nisd; | U+022FA |
niv; | U+0220B |
njcy; | U+0045A |
nlArr; | U+021CD |
nlarr; | U+0219A |
nldr; | U+02025 |
nle; | U+02270 |
nleftarrow; | U+0219A |
nleftrightarrow; | U+021AE |
nleq; | U+02270 |
nless; | U+0226E |
nlsim; | U+02274 |
nlt; | U+0226E |
nltri; | U+022EA |
nltrie; | U+022EC |
nmid; | U+02224 |
nopf; | U+1D55F |
not; | U+000AC |
not | U+000AC |
notin; | U+02209 |
notinva; | U+02209 |
notinvb; | U+022F7 |
notinvc; | U+022F6 |
notni; | U+0220C |
notniva; | U+0220C |
notnivb; | U+022FE |
notnivc; | U+022FD |
npar; | U+02226 |
nparallel; | U+02226 |
npolint; | U+02A14 |
npr; | U+02280 |
nprcue; | U+022E0 |
nprec; | U+02280 |
nrArr; | U+021CF |
nrarr; | U+0219B |
nrightarrow; | U+0219B |
nrtri; | U+022EB |
nrtrie; | U+022ED |
nsc; | U+02281 |
nsccue; | U+022E1 |
nscr; | U+1D4C3 |
nshortmid; | U+02224 |
nshortparallel; | U+02226 |
nsim; | U+02241 |
nsime; | U+02244 |
nsimeq; | U+02244 |
nsmid; | U+02224 |
nspar; | U+02226 |
nsqsube; | U+022E2 |
nsqsupe; | U+022E3 |
nsub; | U+02284 |
nsube; | U+02288 |
nsubseteq; | U+02288 |
nsucc; | U+02281 |
nsup; | U+02285 |
nsupe; | U+02289 |
nsupseteq; | U+02289 |
ntgl; | U+02279 |
ntilde; | U+000F1 |
ntilde | U+000F1 |
ntlg; | U+02278 |
ntriangleleft; | U+022EA |
ntrianglelefteq; | U+022EC |
ntriangleright; | U+022EB |
ntrianglerighteq; | U+022ED |
nu; | U+003BD |
num; | U+00023 |
numero; | U+02116 |
numsp; | U+02007 |
nvDash; | U+022AD |
nvHarr; | U+02904 |
nvdash; | U+022AC |
nvinfin; | U+029DE |
nvlArr; | U+02902 |
nvrArr; | U+02903 |
nwArr; | U+021D6 |
nwarhk; | U+02923 |
nwarr; | U+02196 |
nwarrow; | U+02196 |
nwnear; | U+02927 |
oS; | U+024C8 |
oacute; | U+000F3 |
oacute | U+000F3 |
oast; | U+0229B |
ocir; | U+0229A |
ocirc; | U+000F4 |
ocirc | U+000F4 |
ocy; | U+0043E |
odash; | U+0229D |
odblac; | U+00151 |
odiv; | U+02A38 |
odot; | U+02299 |
odsold; | U+029BC |
oelig; | U+00153 |
ofcir; | U+029BF |
ofr; | U+1D52C |
ogon; | U+002DB |
ograve; | U+000F2 |
ograve | U+000F2 |
ogt; | U+029C1 |
ohbar; | U+029B5 |
ohm; | U+02126 |
oint; | U+0222E |
olarr; | U+021BA |
olcir; | U+029BE |
olcross; | U+029BB |
oline; | U+0203E |
olt; | U+029C0 |
omacr; | U+0014D |
omega; | U+003C9 |
omicron; | U+003BF |
omid; | U+029B6 |
ominus; | U+02296 |
oopf; | U+1D560 |
opar; | U+029B7 |
operp; | U+029B9 |
oplus; | U+02295 |
or; | U+02228 |
orarr; | U+021BB |
ord; | U+02A5D |
order; | U+02134 |
orderof; | U+02134 |
ordf; | U+000AA |
ordf | U+000AA |
ordm; | U+000BA |
ordm | U+000BA |
origof; | U+022B6 |
oror; | U+02A56 |
orslope; | U+02A57 |
orv; | U+02A5B |
oscr; | U+02134 |
oslash; | U+000F8 |
oslash | U+000F8 |
osol; | U+02298 |
otilde; | U+000F5 |
otilde | U+000F5 |
otimes; | U+02297 |
otimesas; | U+02A36 |
ouml; | U+000F6 |
ouml | U+000F6 |
ovbar; | U+0233D |
par; | U+02225 |
para; | U+000B6 |
para | U+000B6 |
parallel; | U+02225 |
parsim; | U+02AF3 |
parsl; | U+02AFD |
part; | U+02202 |
pcy; | U+0043F |
percnt; | U+00025 |
period; | U+0002E |
permil; | U+02030 |
perp; | U+022A5 |
pertenk; | U+02031 |
pfr; | U+1D52D |
phi; | U+003C6 |
phiv; | U+003C6 |
phmmat; | U+02133 |
phone; | U+0260E |
pi; | U+003C0 |
pitchfork; | U+022D4 |
piv; | U+003D6 |
planck; | U+0210F |
planckh; | U+0210E |
plankv; | U+0210F |
plus; | U+0002B |
plusacir; | U+02A23 |
plusb; | U+0229E |
pluscir; | U+02A22 |
plusdo; | U+02214 |
plusdu; | U+02A25 |
pluse; | U+02A72 |
plusmn; | U+000B1 |
plusmn | U+000B1 |
plussim; | U+02A26 |
plustwo; | U+02A27 |
pm; | U+000B1 |
pointint; | U+02A15 |
popf; | U+1D561 |
pound; | U+000A3 |
pound | U+000A3 |
pr; | U+0227A |
prE; | U+02AB3 |
prap; | U+02AB7 |
prcue; | U+0227C |
pre; | U+02AAF |
prec; | U+0227A |
precapprox; | U+02AB7 |
preccurlyeq; | U+0227C |
preceq; | U+02AAF |
precnapprox; | U+02AB9 |
precneqq; | U+02AB5 |
precnsim; | U+022E8 |
precsim; | U+0227E |
prime; | U+02032 |
primes; | U+02119 |
prnE; | U+02AB5 |
prnap; | U+02AB9 |
prnsim; | U+022E8 |
prod; | U+0220F |
profalar; | U+0232E |
profline; | U+02312 |
profsurf; | U+02313 |
prop; | U+0221D |
propto; | U+0221D |
prsim; | U+0227E |
prurel; | U+022B0 |
pscr; | U+1D4C5 |
psi; | U+003C8 |
puncsp; | U+02008 |
qfr; | U+1D52E |
qint; | U+02A0C |
qopf; | U+1D562 |
qprime; | U+02057 |
qscr; | U+1D4C6 |
quaternions; | U+0210D |
quatint; | U+02A16 |
quest; | U+0003F |
questeq; | U+0225F |
quot; | U+00022 |
quot | U+00022 |
rAarr; | U+021DB |
rArr; | U+021D2 |
rAtail; | U+0291C |
rBarr; | U+0290F |
rHar; | U+02964 |
race; | U+029DA |
racute; | U+00155 |
radic; | U+0221A |
raemptyv; | U+029B3 |
rang; | U+027E9 |
rangd; | U+02992 |
range; | U+029A5 |
rangle; | U+027E9 |
raquo; | U+000BB |
raquo | U+000BB |
rarr; | U+02192 |
rarrap; | U+02975 |
rarrb; | U+021E5 |
rarrbfs; | U+02920 |
rarrc; | U+02933 |
rarrfs; | U+0291E |
rarrhk; | U+021AA |
rarrlp; | U+021AC |
rarrpl; | U+02945 |
rarrsim; | U+02974 |
rarrtl; | U+021A3 |
rarrw; | U+0219D |
ratail; | U+0291A |
ratio; | U+02236 |
rationals; | U+0211A |
rbarr; | U+0290D |
rbbrk; | U+02773 |
rbrace; | U+0007D |
rbrack; | U+0005D |
rbrke; | U+0298C |
rbrksld; | U+0298E |
rbrkslu; | U+02990 |
rcaron; | U+00159 |
rcedil; | U+00157 |
rceil; | U+02309 |
rcub; | U+0007D |
rcy; | U+00440 |
rdca; | U+02937 |
rdldhar; | U+02969 |
rdquo; | U+0201D |
rdquor; | U+0201D |
rdsh; | U+021B3 |
real; | U+0211C |
realine; | U+0211B |
realpart; | U+0211C |
reals; | U+0211D |
rect; | U+025AD |
reg; | U+000AE |
reg | U+000AE |
rfisht; | U+0297D |
rfloor; | U+0230B |
rfr; | U+1D52F |
rhard; | U+021C1 |
rharu; | U+021C0 |
rharul; | U+0296C |
rho; | U+003C1 |
rhov; | U+003F1 |
rightarrow; | U+02192 |
rightarrowtail; | U+021A3 |
rightharpoondown; | U+021C1 |
rightharpoonup; | U+021C0 |
rightleftarrows; | U+021C4 |
rightleftharpoons; | U+021CC |
rightrightarrows; | U+021C9 |
rightsquigarrow; | U+0219D |
rightthreetimes; | U+022CC |
ring; | U+002DA |
risingdotseq; | U+02253 |
rlarr; | U+021C4 |
rlhar; | U+021CC |
rlm; | U+0200F |
rmoust; | U+023B1 |
rmoustache; | U+023B1 |
rnmid; | U+02AEE |
roang; | U+027ED |
roarr; | U+021FE |
robrk; | U+027E7 |
ropar; | U+02986 |
ropf; | U+1D563 |
roplus; | U+02A2E |
rotimes; | U+02A35 |
rpar; | U+00029 |
rpargt; | U+02994 |
rppolint; | U+02A12 |
rrarr; | U+021C9 |
rsaquo; | U+0203A |
rscr; | U+1D4C7 |
rsh; | U+021B1 |
rsqb; | U+0005D |
rsquo; | U+02019 |
rsquor; | U+02019 |
rthree; | U+022CC |
rtimes; | U+022CA |
rtri; | U+025B9 |
rtrie; | U+022B5 |
rtrif; | U+025B8 |
rtriltri; | U+029CE |
ruluhar; | U+02968 |
rx; | U+0211E |
sacute; | U+0015B |
sbquo; | U+0201A |
sc; | U+0227B |
scE; | U+02AB4 |
scap; | U+02AB8 |
scaron; | U+00161 |
sccue; | U+0227D |
sce; | U+02AB0 |
scedil; | U+0015F |
scirc; | U+0015D |
scnE; | U+02AB6 |
scnap; | U+02ABA |
scnsim; | U+022E9 |
scpolint; | U+02A13 |
scsim; | U+0227F |
scy; | U+00441 |
sdot; | U+022C5 |
sdotb; | U+022A1 |
sdote; | U+02A66 |
seArr; | U+021D8 |
searhk; | U+02925 |
searr; | U+02198 |
searrow; | U+02198 |
sect; | U+000A7 |
sect | U+000A7 |
semi; | U+0003B |
seswar; | U+02929 |
setminus; | U+02216 |
setmn; | U+02216 |
sext; | U+02736 |
sfr; | U+1D530 |
sfrown; | U+02322 |
sharp; | U+0266F |
shchcy; | U+00449 |
shcy; | U+00448 |
shortmid; | U+02223 |
shortparallel; | U+02225 |
shy; | U+000AD |
shy | U+000AD |
sigma; | U+003C3 |
sigmaf; | U+003C2 |
sigmav; | U+003C2 |
sim; | U+0223C |
simdot; | U+02A6A |
sime; | U+02243 |
simeq; | U+02243 |
simg; | U+02A9E |
simgE; | U+02AA0 |
siml; | U+02A9D |
simlE; | U+02A9F |
simne; | U+02246 |
simplus; | U+02A24 |
simrarr; | U+02972 |
slarr; | U+02190 |
smallsetminus; | U+02216 |
smashp; | U+02A33 |
smeparsl; | U+029E4 |
smid; | U+02223 |
smile; | U+02323 |
smt; | U+02AAA |
smte; | U+02AAC |
softcy; | U+0044C |
sol; | U+0002F |
solb; | U+029C4 |
solbar; | U+0233F |
sopf; | U+1D564 |
spades; | U+02660 |
spadesuit; | U+02660 |
spar; | U+02225 |
sqcap; | U+02293 |
sqcup; | U+02294 |
sqsub; | U+0228F |
sqsube; | U+02291 |
sqsubset; | U+0228F |
sqsubseteq; | U+02291 |
sqsup; | U+02290 |
sqsupe; | U+02292 |
sqsupset; | U+02290 |
sqsupseteq; | U+02292 |
squ; | U+025A1 |
square; | U+025A1 |
squarf; | U+025AA |
squf; | U+025AA |
srarr; | U+02192 |
sscr; | U+1D4C8 |
ssetmn; | U+02216 |
ssmile; | U+02323 |
sstarf; | U+022C6 |
star; | U+02606 |
starf; | U+02605 |
straightepsilon; | U+003F5 |
straightphi; | U+003D5 |
strns; | U+000AF |
sub; | U+02282 |
subE; | U+02AC5 |
subdot; | U+02ABD |
sube; | U+02286 |
subedot; | U+02AC3 |
submult; | U+02AC1 |
subnE; | U+02ACB |
subne; | U+0228A |
subplus; | U+02ABF |
subrarr; | U+02979 |
subset; | U+02282 |
subseteq; | U+02286 |
subseteqq; | U+02AC5 |
subsetneq; | U+0228A |
subsetneqq; | U+02ACB |
subsim; | U+02AC7 |
subsub; | U+02AD5 |
subsup; | U+02AD3 |
succ; | U+0227B |
succapprox; | U+02AB8 |
succcurlyeq; | U+0227D |
succeq; | U+02AB0 |
succnapprox; | U+02ABA |
succneqq; | U+02AB6 |
succnsim; | U+022E9 |
succsim; | U+0227F |
sum; | U+02211 |
sung; | U+0266A |
sup1; | U+000B9 |
sup1 | U+000B9 |
sup2; | U+000B2 |
sup2 | U+000B2 |
sup3; | U+000B3 |
sup3 | U+000B3 |
sup; | U+02283 |
supE; | U+02AC6 |
supdot; | U+02ABE |
supdsub; | U+02AD8 |
supe; | U+02287 |
supedot; | U+02AC4 |
suphsub; | U+02AD7 |
suplarr; | U+0297B |
supmult; | U+02AC2 |
supnE; | U+02ACC |
supne; | U+0228B |
supplus; | U+02AC0 |
supset; | U+02283 |
supseteq; | U+02287 |
supseteqq; | U+02AC6 |
supsetneq; | U+0228B |
supsetneqq; | U+02ACC |
supsim; | U+02AC8 |
supsub; | U+02AD4 |
supsup; | U+02AD6 |
swArr; | U+021D9 |
swarhk; | U+02926 |
swarr; | U+02199 |
swarrow; | U+02199 |
swnwar; | U+0292A |
szlig; | U+000DF |
szlig | U+000DF |
target; | U+02316 |
tau; | U+003C4 |
tbrk; | U+023B4 |
tcaron; | U+00165 |
tcedil; | U+00163 |
tcy; | U+00442 |
tdot; | U+020DB |
telrec; | U+02315 |
tfr; | U+1D531 |
there4; | U+02234 |
therefore; | U+02234 |
theta; | U+003B8 |
thetasym; | U+003D1 |
thetav; | U+003D1 |
thickapprox; | U+02248 |
thicksim; | U+0223C |
thinsp; | U+02009 |
thkap; | U+02248 |
thksim; | U+0223C |
thorn; | U+000FE |
thorn | U+000FE |
tilde; | U+002DC |
times; | U+000D7 |
times | U+000D7 |
timesb; | U+022A0 |
timesbar; | U+02A31 |
timesd; | U+02A30 |
tint; | U+0222D |
toea; | U+02928 |
top; | U+022A4 |
topbot; | U+02336 |
topcir; | U+02AF1 |
topf; | U+1D565 |
topfork; | U+02ADA |
tosa; | U+02929 |
tprime; | U+02034 |
trade; | U+02122 |
triangle; | U+025B5 |
triangledown; | U+025BF |
triangleleft; | U+025C3 |
trianglelefteq; | U+022B4 |
triangleq; | U+0225C |
triangleright; | U+025B9 |
trianglerighteq; | U+022B5 |
tridot; | U+025EC |
trie; | U+0225C |
triminus; | U+02A3A |
triplus; | U+02A39 |
trisb; | U+029CD |
tritime; | U+02A3B |
trpezium; | U+023E2 |
tscr; | U+1D4C9 |
tscy; | U+00446 |
tshcy; | U+0045B |
tstrok; | U+00167 |
twixt; | U+0226C |
twoheadleftarrow; | U+0219E |
twoheadrightarrow; | U+021A0 |
uArr; | U+021D1 |
uHar; | U+02963 |
uacute; | U+000FA |
uacute | U+000FA |
uarr; | U+02191 |
ubrcy; | U+0045E |
ubreve; | U+0016D |
ucirc; | U+000FB |
ucirc | U+000FB |
ucy; | U+00443 |
udarr; | U+021C5 |
udblac; | U+00171 |
udhar; | U+0296E |
ufisht; | U+0297E |
ufr; | U+1D532 |
ugrave; | U+000F9 |
ugrave | U+000F9 |
uharl; | U+021BF |
uharr; | U+021BE |
uhblk; | U+02580 |
ulcorn; | U+0231C |
ulcorner; | U+0231C |
ulcrop; | U+0230F |
ultri; | U+025F8 |
umacr; | U+0016B |
uml; | U+000A8 |
uml | U+000A8 |
uogon; | U+00173 |
uopf; | U+1D566 |
uparrow; | U+02191 |
updownarrow; | U+02195 |
upharpoonleft; | U+021BF |
upharpoonright; | U+021BE |
uplus; | U+0228E |
upsi; | U+003C5 |
upsih; | U+003D2 |
upsilon; | U+003C5 |
upuparrows; | U+021C8 |
urcorn; | U+0231D |
urcorner; | U+0231D |
urcrop; | U+0230E |
uring; | U+0016F |
urtri; | U+025F9 |
uscr; | U+1D4CA |
utdot; | U+022F0 |
utilde; | U+00169 |
utri; | U+025B5 |
utrif; | U+025B4 |
uuarr; | U+021C8 |
uuml; | U+000FC |
uuml | U+000FC |
uwangle; | U+029A7 |
vArr; | U+021D5 |
vBar; | U+02AE8 |
vBarv; | U+02AE9 |
vDash; | U+022A8 |
vangrt; | U+0299C |
varepsilon; | U+003B5 |
varkappa; | U+003F0 |
varnothing; | U+02205 |
varphi; | U+003C6 |
varpi; | U+003D6 |
varpropto; | U+0221D |
varr; | U+02195 |
varrho; | U+003F1 |
varsigma; | U+003C2 |
vartheta; | U+003D1 |
vartriangleleft; | U+022B2 |
vartriangleright; | U+022B3 |
vcy; | U+00432 |
vdash; | U+022A2 |
vee; | U+02228 |
veebar; | U+022BB |
veeeq; | U+0225A |
vellip; | U+022EE |
verbar; | U+0007C |
vert; | U+0007C |
vfr; | U+1D533 |
vltri; | U+022B2 |
vopf; | U+1D567 |
vprop; | U+0221D |
vrtri; | U+022B3 |
vscr; | U+1D4CB |
vzigzag; | U+0299A |
wcirc; | U+00175 |
wedbar; | U+02A5F |
wedge; | U+02227 |
wedgeq; | U+02259 |
weierp; | U+02118 |
wfr; | U+1D534 |
wopf; | U+1D568 |
wp; | U+02118 |
wr; | U+02240 |
wreath; | U+02240 |
wscr; | U+1D4CC |
xcap; | U+022C2 |
xcirc; | U+025EF |
xcup; | U+022C3 |
xdtri; | U+025BD |
xfr; | U+1D535 |
xhArr; | U+027FA |
xharr; | U+027F7 |
xi; | U+003BE |
xlArr; | U+027F8 |
xlarr; | U+027F5 |
xmap; | U+027FC |
xnis; | U+022FB |
xodot; | U+02A00 |
xopf; | U+1D569 |
xoplus; | U+02A01 |
xotime; | U+02A02 |
xrArr; | U+027F9 |
xrarr; | U+027F6 |
xscr; | U+1D4CD |
xsqcup; | U+02A06 |
xuplus; | U+02A04 |
xutri; | U+025B3 |
xvee; | U+022C1 |
xwedge; | U+022C0 |
yacute; | U+000FD |
yacute | U+000FD |
yacy; | U+0044F |
ycirc; | U+00177 |
ycy; | U+0044B |
yen; | U+000A5 |
yen | U+000A5 |
yfr; | U+1D536 |
yicy; | U+00457 |
yopf; | U+1D56A |
yscr; | U+1D4CE |
yucy; | U+0044E |
yuml; | U+000FF |
yuml | U+000FF |
zacute; | U+0017A |
zcaron; | U+0017E |
zcy; | U+00437 |
zdot; | U+0017C |
zeetrf; | U+02128 |
zeta; | U+003B6 |
zfr; | U+1D537 |
zhcy; | U+00436 |
zigrarr; | U+021DD |
zopf; | U+1D56B |
zscr; | U+1D4CF |
zwj; | U+0200D |
zwnj; | U+0200C |
9 Rendering
This section will probably include details on
how to render DATAGRID (including its
pseudo-elements), drag-and-drop, etc, in a visual medium, in
concert with CSS. Terms that need to be defined include: sizing
of embedded content
CSS UAs in visual media must, when scrolling a page to a fragment
identifier, align the top of the viewport with the target element's
top border edge.視覚的媒体の CSS 利用者エージェントは、頁を素片識別子までスクロールする時、
閲覧領域の上辺に対象要素の境界線上辺を揃えなければなりません。
must define letting the user "obtain a
physical form (or a representation of a physical form)" of a
document (printing) and what this means for the UA, in particular
creating a new view for the print media.
Must define that in CSS, tag and attribute
names in HTML documents, and class names in quirks mode documents,
are case-insensitive, as well as saying which attribute values must
be compared case-insensitively.
Need to define the content attributes of BODY in
terms of CSS or something.
9.1.1 The 'icon' property9.1.1 'icon' 特性
UAs should use the command's Icon as the default generic icon
provided by the user agent when the 'icon' property computes to
'auto' on an element that either defines a command or refers to one
using the command attribute,
but when the property computes to an actual image, it should use
that image instead.
10 Obsolete features
Authors and documents must not use the features listed in this
section. They are documented to enable user agents to support legacy
content in an interoperable fashion.
10.1 Obsolete elements
10.1.1 The body element10.1.1 body 要素
[XXX] interface HTMLDocument {
attribute DOMString fgColor;
attribute DOMString bgColor;
attribute DOMString linkColor;
attribute DOMString vlinkColor;
attribute DOMString alinkColor;
};
The fgColor
attribute on the Document object must
reflect the text
attribute on the body element.Document オブジェクトの fgColor 属性は、文書 body 要素の text
属性を反映しなければなりません。
The bgColor
attribute on the Document object must
reflect the bgcolor
attribute on the body element.Document オブジェクトの bgColor 属性は、文書 body 要素の bgcolor
属性を反映しなければなりません。
The linkColor
attribute on the Document object must
reflect the link
attribute on the body element.Document オブジェクトの linkColor 属性は、文書 body 要素の link
属性を反映しなければなりません。
The vLinkColor
attribute on the Document object must
reflect the vlink
attribute on the body element.Document オブジェクトの vLinkColor 属性は、文書 body 要素の vlink
属性を反映しなければなりません。
The aLinkColor
attribute on the Document object must
reflect the alink
attribute on the body element.Document オブジェクトの aLinkColor 属性は、文書 body 要素の alink
属性を反映しなければなりません。
[XXX] interface HTMLBodyElement {
attribute DOMString text;
attribute DOMString bgColor;
attribute DOMString background;
attribute DOMString link;
attribute DOMString vLink;
attribute DOMString aLink;
};
The text DOM
attribute of the body element must reflect
the element's text content
attribute.body 要素の text DOM 属性は、
その要素の text
内容属性を反映しなければなりません。
The bgColor DOM
attribute of the body element must reflect
the element's bgcolor content
attribute.body 要素の bgColor DOM 属性は、
その要素の bgcolor
内容属性を反映しなければなりません。
The background DOM
attribute of the body element must reflect
the element's background content
attribute.body 要素の background DOM 属性は、
その要素の background
内容属性を反映しなければなりません。
The link DOM
attribute of the body element must reflect
the element's link content
attribute.body 要素の link DOM 属性は、
その要素の link
内容属性を反映しなければなりません。
The aLink DOM
attribute of the body element must reflect
the element's alink content
attribute.body 要素の aLink DOM 属性は、
その要素の alink
内容属性を反映しなければなりません。
The vLink DOM
attribute of the body element must reflect
the element's vlink content
attribute.body 要素の vLink DOM 属性は、
その要素の vlink
内容属性を反映しなければなりません。
10.1.2 The applet element10.1.2 applet 要素
The applet element is a Java-specific variant of the
embed element. In HTML5 the applet element
is obsoleted so that all extension frameworks (Java, .NET, Flash,
etc) are handled in a consistent manner.applet 要素は、
embed 要素の Java
専用の異形です。 HTML5 では
applet 要素は廃止されており、
すべての拡張の枠組み (Java、.NET、Flash など) は一貫した方法で扱われます。
If the sandboxed plugins browsing
context flag is set on the browsing context for
which the applet element's document is the active
document, then the element must be ignored (it represents
nothing).applet 要素の文書が活性文書である閲覧文脈において砂箱化プラグイン閲覧文脈旗が設定されている場合、
要素は無視されなければなりません (何も表しません)。
Otherwise, define how the element works,
if supported.
[XXX] interface HTMLDocument {
readonly attribute HTMLCollection applets;
};
The applets
attribute must return an HTMLCollection rooted at the
Document node, whose filter matches only
applet elements.applets 属性は、
Document 節点を根とし、濾過器が applet
要素にのみ一致するような HTMLCollection
を返さなければなりません。
To ease the transition from HTML4 Transitional documents to the
language defined in this specification, conformance
checkers are encouraged to categorise errors that represent usage of
old obsolete features that generally have no effect (as defined
below) into a separate part of their report, to allow authors to
distinguish between likely mistakes and mere vestigial markup.
The following errors may be categorised as described above:
-
The DOCTYPE parse error, if the DOCTYPE token's
name is an ASCII
case-insensitive match for the string "HTML", and either:
the token's public identifier is the
case-sensitive string "-//W3C//DTD HTML 4.0//EN" and the
token's system identifier is either missing or the
case-sensitive string "http://www.w3.org/TR/REC-html40/strict.dtd", or
the token's public identifier is the
case-sensitive string "-//W3C//DTD HTML 4.01//EN" and the
token's system identifier is either missing or the
case-sensitive string "http://www.w3.org/TR/html4/strict.dtd", or
the token's public identifier is the
case-sensitive string "-//W3C//DTD XHTML 1.0 Strict//EN"
and the token's system identifier is either missing or the
case-sensitive string "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd",
or
the token's public identifier is the
case-sensitive string "-//W3C//DTD XHTML 1.1//EN"
and the token's system identifier is either missing or the
case-sensitive string "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd".
The presence of a border attribute on an
img element if its value is the string "0".
The presence of a language attribute on a
script element if its value is an ASCII
case-insensitive match for the string "JavaScript".
11 Things that you can't do with this specification because
they are better handled using other technologies that are further
described herein11 ここで詳しく説明する他の技術を使う方がよりうまく取り扱えるのでこの仕様書では行うことができない事柄
This section is non-normative.この節は規定の一部ではありません。
There are certain features that are not handled by this
specification because a client side markup language is not the right
level for them, or because the features exist in other languages
that can be integrated into this one. This section covers some of
the more common requests.この仕様書では、
クライアント側マーク付け言語が適当な水準ではないため、
あるいはこの言語と統合できる別の言語に機能が存在するため、
取り扱わない機能があります。この章ではとてもよくある要求のいくつかに触れます。
11.1 Localization11.1 局所化
If you wish to create localized versions of an HTML application,
the best solution is to preprocess the files on the server, and then
use HTTP content negotiation to serve the appropriate language.HTML アプリケーションの局所化した版を作成したいという場合、
ファイルを鯖で前処理した上で、 HTTP 内容折衝を使って適当な言語で供給するのが最も良い解決策です。
11.2 Declarative 2D vector graphics and animation11.2 宣言的2次元ベクトル画像・アニメーション
Embedding vector graphics into XHTML documents is the domain of
SVG.ベクトル画像の XHTML 文書への埋め込みは、 SVG の範囲です。
11.3 Declarative 3D scenes11.3 宣言的3次元場面
Embedding 3D imagery into XHTML documents is the domain of X3D,
or technologies based on X3D that are namespace-aware.3次元画像の XHTML 文書への埋め込みは、 X3D や X3D に基づく名前空間に対応した技術の範囲です。
11.4 Timers11.4 タイマー
This section is expected to be moved to its own
specification in due course. It needs a lot of work to actually make
it into a semi-decent spec.
Objects that implement the Window interface must
also implement the WindowTimers interface:Window 界面を実装するオブジェクトは、
WindowTimers
界面も実装しなければなりません。
[NoInterfaceObject] interface WindowTimers {
// timers
long setTimeout(in TimeoutHandler handler, in long timeout);
long setTimeout(in TimeoutHandler handler, in long timeout, arguments...);
long setTimeout(in DOMString code, in long timeout);
long setTimeout(in DOMString code, in long timeout, in DOMString language);
void clearTimeout(in long handle);
long setInterval(in TimeoutHandler handler, in long timeout);
long setInterval(in TimeoutHandler handler, in long timeout, arguments...);
long setInterval(in DOMString code, in long timeout);
long setInterval(in DOMString code, in long timeout, in DOMString language);
void clearInterval(in long handle);
};
interface TimeoutHandler {
void handleEvent([Variadic] in any args);
};
The setTimeout
and setInterval
methods allow authors to schedule timer-based events.
The setTimeout(handler, timeout[, arguments...]) method takes a reference
to a TimeoutHandler object and a length of time in
milliseconds. It must return a handle to the timeout created, and
then asynchronously wait timeout milliseconds
and then queue a task to invoke
handleEvent() on the handler
object. If any arguments... were provided, they
must be passed to the handler as arguments to
the handleEvent() function.
Alternatively, setTimeout(code, timeout[, language]) may be used. This variant
takes a string instead of a TimeoutHandler
object. define the actual requirements for
this method, as with the previous one. That string must be
parsed using the specified language (defaulting
to ECMAScript if the third argument is omitted) and executed in the
scope of the browsing context associated with the
Window object on which the setTimeout() method was invoked.
Need to define language
values.
The setInterval(...)
variants must work in the same way as the setTimeout
variants except that if timeout is a value
greater than zero, the task that
invokes the handler or code must be
queued again every timeout milliseconds, not just the once.
The clearTimeout()
and clearInterval()
methods take one integer (the value returned by setTimeout() and setInterval()
respectively) and must cancel the specified timeout. When called
with a value that does not correspond to an active timeout or
interval, the methods must return without doing anything.
11.5 Rendering and the DOM
This section is expected to be moved to its own
specification in due course. It needs a lot of work to actually make
it into a semi-decent spec.
Any object implement the AbstractView interface must
also implement the MediaModeAbstractView interface.
interface MediaModeAbstractView {
readonly attribute DOMString mediaMode;
};
The mediaMode attribute on objects
implementing the MediaModeAbstractView interface must
return the string that represents the canvas' current rendering mode
(screen, print, etc). This is a lowercase
string, as defined by
the CSS specification. [CSS21]
Some user agents may support multiple media, in which case there
will exist multiple objects implementing the
AbstractView interface. Only the default view
implements the Window interface. The other views can be
reached using the view attribute of the
UIEvent interface, during event propagation. There is no
way currently to enumerate all the views.
Index索引
This section is non-normative.この節は規定の一部ではありません。
List of elements
List of attributes
List of interfaces
List of events
References参照
This section will be written in a future draft.
Acknowledgements謝辞
Thanks to Aankhen, Aaron Boodman, Aaron Leventhal, Adam Barth,
Adam Roben, Addison Phillips, Adele Peterson, Adrian Sutton,
Agustín Fernández, Ajai Tirumali, Alastair Campbell,
Alex Nicolaou, Alexey Feldgendler, Anders Carlsson, Andrew Gove,
Andrew Sidwell, Anne van Kesteren, Anthony Hickson, Anthony Ricaud,
Antti Koivisto, Arphen Lin, Asbjørn Ulsberg, Ashley Sheridan,
Aurelien Levy, Ben Boyle, Ben Godfrey, Ben Meadowcroft, Ben Millard,
Benjamin Hawkes-Lewis, Bert Bos, Bill Mason, Billy Wong, Bjoern
Hoehrmann, Boris Zbarsky, Brad Fults, Brad Neuberg, Brady Eidson,
Brendan Eich, Brett Wilson, Brian Campbell, Brian Smith, Bruce
Miller, Cameron McCormack, Cao Yipeng, Carlos Perelló
Marín, Chao Cai, 윤석찬 (Channy Yun), Charl
van Niekerk, Charles Iliya Krempeaux, Charles McCathieNevile,
Christian Biesinger, Christian Johansen, Christian Schmidt, Chriswa,
Cole Robison, Collin Jackson, Daniel Barclay, Daniel Brumbaugh
Keeney, Daniel Glazman, Daniel Peng, Daniel Spång, Daniel
Steinberg, Danny Sullivan, Darin Adler, Darin Fisher, Dave Camp,
Dave Singer, Dave Townsend, David Baron,
David Bloom, David Carlisle, David Flanagan, David
Håsäther, David Hyatt, David Smith, David Woolley, Dean
Edridge, Debi Orton, Derek Featherstone, DeWitt Clinton, Dimitri
Glazkov, dolphinling, Doron Rosenberg, Doug Kramer, Edward O'Connor,
Eira Monstad, Elliotte Harold, Eric Carlson, Eric Law, Erik
Arvidsson, Evan Martin, Evan Prodromou, fantasai, Felix Sasaki,
Franck 'Shift' Quélain, Garrett Smith, Geoffrey Garen,
Geoffrey Sneddon, George Lund, Håkon Wium Lie, Henri Sivonen,
Henrik Lied, Henry Mason, Hugh Winkler, Ignacio Javier, Ivo Emanuel
Gonçalves, J. King, Jacques Distler, James Graham, James
Justin Harrell, James M Snell, James Perrett, Jan-Klaas Kollhof,
Jason White, Jasper Bryant-Greene, Jeff Cutsinger, Jeff Schiller,
Jeff Walden, Jens Bannmann, Jens Fendler, Jeroen van der Meer, Jim
Jewett, Jim Meehan, Joe Clark, John Fallows, Joseph Kesselman, Jjgod
Jiang, Joel Spolsky, Johan Herland, John Boyer, John Bussjaeger,
John Harding, Johnny Stenback, Jon Gibbins, Jon Perlow, Jonathan
Worent, Jorgen Horstink, Josh Levenberg, Joshua Randall, Jukka
K. Korpela, Jules Clément-Ripoche, Julian Reschke, Kai
Hendry, Kornel Lesinski,
黒澤剛志 (KUROSAWA Takeshi), Kristof
Zelechovski, Lachlan Hunt, Larry Page, Lars Gunther, Laura
L. Carlson, Laura Wisewell, Laurens Holst, Lee Kowalkowski, Leif
Halvard Silli, Lenny Domnitser, Léonard Bouchet, Leons
Petrazickis, Logan, Loune, Maciej Stachowiak,
Magnus Kristiansen, Maik Merten, Malcolm Rowe, Mark
Nottingham, Mark Rowe, Mark Schenk, Martijn Wargers,
Martin Atkins, Martin Dürst, Martin Honnen, Masataka Yakura,
Mathieu Henri, Matthew Gregan, Matthew Mastracci, Matthew Raymond,
Matthew Thomas, Mattias Waldau, Max Romantschuk, Michael 'Ratt'
Iannarelli, Michael A. Nachbaur, Michael A. Puls
II, Michael Carter, Michael Gratton, Michael
Nordman, Michael Powers, Michael(tm) Smith, Michel Fortin, Michiel
van der Blonk, Mihai Şucan, Mike
Brown, Mike Dierken, Mike Dixon, Mike
Schinkel, Mike Shaver, Mikko Rantalainen, Neil Deakin, Neil Soiffer,
Olaf Hoffmann, Olav Junker Kjær, Oliver Hunt, Peter Karlsson,
Peter Kasting, Philip Jägenstedt, Philip Taylor, Philip
TAYLOR, Rachid Finge, Rajas Moonka, Ralf
Stoltze, Ralph Giles, Raphael Champeimont, Rene Saarsoo, Richard
Ishida, Rimantas Liubertas, Robert Blaut, Robert O'Callahan, Robert
Sayre, Roman Ivanov, Ryan King, S. Mike Dierken, Sam Kuper, Sam
Ruby, Sam Weinig, Scott Hess, Sean Knapp, Shaun Inman, Silvia
Pfeiffer, Simon Pieters, Stefan Haustein, Steffen Meschkat, Stephen
Ma, Steve Faulkner, Steve Runyon, Steven Garrity, Stewart Brodie,
Stuart Parmenter, Sunava Dutta, Tantek Çelik, Terrence Wood,
Thomas Broyer, Thomas O'Connor, Tim Altman, Tim Johansson, Tommy
Thorsen, Travis Leithead, Tyler Close, Vladimir
Vukićević, Wakaba, Wayne Pollock, Wellington Fernando
de Macedo, William Swanson, Wolfram Kriesing, Yi-An Huang, and
Øistein E. Andersen, for their useful and substantial
comments.Aankhen, Aaron Boodman, Aaron Leventhal, Adam Barth, Adam Roben, Addison Phillips, Adele Peterson, Adrian Sutton, Agustín Fernández, Ajai Tirumali, Alastair Campbell, Alex Nicolaou, Alexey Feldgendler, Anders Carlsson, Andrew Gove, Andrew Sidwell, Anne van Kesteren, Anthony Hickson, Anthony Ricaud, Antti Koivisto, Arphen Lin, Asbjørn Ulsberg, Ashley Sheridan, Aurelien Levy, Ben Boyle, Ben Godfrey, Ben Meadowcroft, Ben Millard, Benjamin Hawkes-Lewis, Bert Bos, Bill Mason, Billy Wong, Bjoern Hoehrmann, Boris Zbarsky, Brad Fults, Brad Neuberg, Brady Eidson, Brendan Eich, Brett Wilson, Brian Campbell, Brian Smith, Bruce Miller, Cameron McCormack, Cao Yipeng, Carlos Perelló Marín, Chao Cai, 윤석찬 (Channy Yun), Charl van Niekerk, Charles Iliya Krempeaux, Charles McCathieNevile, Christian Biesinger, Christian Johansen, Christian Schmidt, Chriswa, Cole Robison, Collin Jackson, Daniel Barclay, Daniel Brumbaugh Keeney, Daniel Glazman, Daniel Peng, Daniel Spång, Daniel Steinberg, Danny Sullivan, Darin Adler, Darin Fisher, Dave Camp, Dave Singer, Dave Townsend, David Baron, David Bloom, David Carlisle, David Flanagan, David Håsäther, David Hyatt, David Smith, David Woolley, Dean Edridge, Debi Orton, Derek Featherstone, DeWitt Clinton, Dimitri Glazkov, dolphinling, Doron Rosenberg, Doug Kramer, Edward O'Connor, Eira Monstad, Elliotte Harold, Eric Carlson, Eric Law, Erik Arvidsson, Evan Martin, Evan Prodromou, fantasai, Felix Sasaki, Franck 'Shift' Quélain, Garrett Smith, Geoffrey Garen, Geoffrey Sneddon, George Lund, Håkon Wium Lie, Henri Sivonen, Henrik Lied, Henry Mason, Hugh Winkler, Ignacio Javier, Ivo Emanuel Gonçalves, J. King, Jacques Distler, James Graham, James Justin Harrell, James M Snell, James Perrett, Jan-Klaas Kollhof, Jason White, Jasper Bryant-Greene, Jeff Cutsinger, Jeff Schiller, Jeff Walden, Jens Bannmann, Jens Fendler, Jeroen van der Meer, Jim Jewett, Jim Meehan, Joe Clark, John Fallows, Joseph Kesselman, Jjgod Jiang, Joel Spolsky, Johan Herland, John Boyer, John Bussjaeger, John Harding, Johnny Stenback, Jon Gibbins, Jon Perlow, Jonathan Worent, Jorgen Horstink, Josh Levenberg, Joshua Randall, Jukka K. Korpela, Jules Clément-Ripoche, Julian Reschke, Kai Hendry, Kornel Lesinski, 黒澤剛志 (KUROSAWA Takeshi), Kristof Zelechovski, Lachlan Hunt, Larry Page, Lars Gunther, Laura L. Carlson, Laura Wisewell, Laurens Holst, Lee Kowalkowski, Leif Halvard Silli, Lenny Domnitser, Léonard Bouchet, Leons Petrazickis, Logan, Loune, Maciej Stachowiak, Magnus Kristiansen, Maik Merten, Malcolm Rowe, Mark Nottingham, Mark Rowe, Mark Schenk, Martijn Wargers, Martin Atkins, Martin Dürst, Martin Honnen, Masataka Yakura, Mathieu Henri, Matthew Gregan, Matthew Mastracci, Matthew Raymond, Matthew Thomas, Mattias Waldau, Max Romantschuk, Michael 'Ratt' Iannarelli, Michael A. Nachbaur, Michael A. Puls II, Michael Carter, Michael Gratton, Michael Nordman, Michael Powers, Michael(tm) Smith, Michel Fortin, Michiel van der Blonk, Mihai Şucan, Mike Brown, Mike Dierken, Mike Dixon, Mike Schinkel, Mike Shaver, Mikko Rantalainen, Neil Deakin, Neil Soiffer, Olaf Hoffmann, Olav Junker Kjær, Oliver Hunt, Peter Karlsson, Peter Kasting, Philip Jägenstedt, Philip Taylor, Philip TAYLOR, Rachid Finge, Rajas Moonka, Ralf Stoltze, Ralph Giles, Raphael Champeimont, Rene Saarsoo, Richard Ishida, Rimantas Liubertas, Robert Blaut, Robert O'Callahan, Robert Sayre, Roman Ivanov, Ryan King, S. Mike Dierken, Sam Kuper, Sam Ruby, Sam Weinig, Scott Hess, Sean Knapp, Shaun Inman, Silvia Pfeiffer, Simon Pieters, Stefan Haustein, Steffen Meschkat, Stephen Ma, Steve Faulkner, Steve Runyon, Steven Garrity, Stewart Brodie, Stuart Parmenter, Sunava Dutta, Tantek Çelik, Terrence Wood, Thomas Broyer, Thomas O'Connor, Tim Altman, Tim Johansson, Tommy Thorsen, Travis Leithead, Tyler Close, Vladimir Vukićević, Wakaba, Wayne Pollock, Wellington Fernando de Macedo, William Swanson, Wolfram Kriesing, Yi-An Huang, Øistein E. Andersen の有用かつ重要なコメントに感謝します。
Thanks also to everyone who has ever posted about HTML5 to their
blogs, public mailing lists, or forums, including the W3C
public-html list and the various WHATWG lists.
HTML5 についてブログや公開メイリング・リストや掲示板 (W3C public-html
メイリング・リストやWHATWG
各種メイリング・リストなど) に投稿したすべての方々にも感謝します。
Special thanks to Richard Williamson for creating the first
implementation of canvas in Safari, from which the
canvas feature was designed.canvas を Safari
に最初に実装した Richard Williamson に特に感謝します。
画布機能はそれを元に設計しました。
Special thanks also to the Microsoft employees who first
implemented the event-based drag-and-drop mechanism, contenteditable, and other
features first widely deployed by the Windows Internet Explorer
browser.事象に基づくドラッグ・アンド・ドロップ機構、contenteditable、
その他 Windows Internet Explorer ブラウザではじめて広く採用された機能を最初に実装した
Microsoft の従業員のみなさまにも特に感謝します。
Special thanks and $10,000 to David Hyatt who came up with a
broken implementation of the adoption
agency algorithm that the editor had to reverse engineer and fix
before using it in the parsing section.構文解析の章に採用するために編集者が逆行分析して不具合を修正せざるを得なかった、養子代理人算法の壊れた実装を考案した David Hyatt
に特に感謝し、賞金100万円を贈ります。
Thanks to the many sources that provided inspiration for the
examples used in the specification.この仕様書中で使用した例文の着想を得た多くの出典に感謝します。
Thanks also to the Microsoft blogging community for some ideas,
to the attendees of the W3C Workshop on Web Applications and
Compound Documents for inspiration, to the #mrt crew, the #mrt.no
crew, and the #whatwg crew, and to Pillar and Hedral for their ideas
and support.いくつものアイディアを与えてくださった Microsoft ブログ・コミュニティのみなさま、
刺激を与えてくださった W3C Web アプリケーションと複合文書に関する研究会の参加者のみなさま、
#mrt の団員、 #mrt.no の団員、 #whatwg の団員のみなさま、
アイディアと支援を与えてくださった Pillar と Hedral
にも、感謝します。
