Wireless Markup Language version 1.3 Test Specification
ISSUE : wml12ts_15-01-2002
Copyright © 1999-2002 Wireless Application Forum. Ltd. All Rights Reserved.
Preface
This document contains the assertion specification for the WAP June 2000 release of the: WML technical specification.
The following specifications and SINs were used to generate the assertions:
- WAP-191-WML-20000219-a.pdf
- WAP-191_102-WML-20001213-a.pdf
- WAP-191_104-WML-20010718-a.pdf
The specification is organized such that there is a section for each section
of the WML specification in which assertions can be found. For each
assertion in the WML specification, a corresponding entry in this test
specification contains the following elements:
For each assertion in the specifications, a corresponding entry in this test
specification contains the following elements:
| ID: |
The name by which the test is known |
| Class: |
An assertion Class as defined in IEEE Std 1003.3. These types are: |
| A |
A mandatory, testable assertion. |
| B |
A mandatory, but untestable assertion. |
| C |
An optional, testable assertion. |
| D |
An optional, but untestable assertion. |
|
| Scope: |
If an assertion is type C or D, this entry describes the option that needs
to be supported in order to activate the test. |
| Text: |
The text of the assertion and a reference to the source specification
from which the assertion is derived. |
| Note: |
Any supplementary information associated with the assertion. For example
it may suggest a strategy for the test implementation of the assertion
or it may propose rationale as to why a test is classified as untestable.
|
This specification uses the following conventions for convenience:
- Element and attribute names are in UPPERCASE.
- References to DTD entities are prefixed with percent sign (e.g. %PCDATA).
- Literal text is enclosed in quotation marks.
Assertions for this section are covered in the Wireless Application Environment Specification
There are no testable assertions in this section.
| ID: |
wml/urls/fragment/1 |
| Class: |
A |
| Text: |
When a URL does not include a fragment identifier (a hash mark
followed by a name), the URL references a deck. [WML Specification section 5.2] |
| Note: |
The URL implicitly references the first card in the deck. |
|
| ID: |
wml/urls/fragment/2 |
| Class: |
A |
| Text: |
When a URL contains a fragment identifier (a hash mark followed
by a name), the URL references an individual card within a WML deck. [WML Specification section 5.2] |
|
| ID: |
wml/urls/relative/1 |
| Class: |
A |
| Text: |
When a relative URL is encountered, it is resolved against the Base URL of
the deck. [WML Specification section 5.3] |
|
| ID: |
wml/charset/model/1 |
| Class: |
B |
| Text: |
When the encoding attribute of the XML processing instruction is
specified, AND the charset is not specified elsewhere in the contents of the
document AND the charset parameter of the Content-Type transport header
is not specified, then the charset in the contents defines the character
encoding of the resource. [WML Specification section 6.1] |
|
| ID: |
wml/charset/model/2 |
| Class: |
A |
| Text: |
When no character encoding is specified, the default character
encoding can be assumed (UTF-8). [WML Specification section 6.1] |
|
| ID: |
wml/charset/model/3 |
| Class: |
B |
| Text: |
When documents are encoded in non-Unicode codesets, they shall
be converted into Unicode by the user agent (or behave as if they are
converted). [WML Specification section 6.1] |
|
| ID: |
wml/charset/model/4 |
| Class: |
B |
| Text: |
When documents contain character entities, they shall be
translated using the document character set which is always ISO-10646
regardless of the document's encoding (e.g. Shift_JIS, Latin-4, etc). [WML Specification section 6.1] |
|
| ID: |
wml/charset/entities/1 |
| Class: |
A |
| Text: |
When a named character entity is encountered (e.g. &), its associated element from the document character set replaces the character entity in the text. [WML Specification section 6.2] |
|
| ID: |
wml/charset/entities/2 |
| Class: |
A |
| Text: |
When a decimal numeric character entity is encountered, its associated element from the document character set replaces the character entity in the text. [WML Specification section 6.2] |
|
| ID: |
wml/charset/entities/3 |
| Class: |
A |
| Text: |
When a hexadecimal numeric character entity is encountered, its element from the document character set replaces the character entity in the text. [WML Specification section 6.2] |
|
Assertions for element and attribute syntax are covered within their specific
sections of the specification.
| ID: |
wml/syntax/1 |
| Class: |
A |
| Text: |
When a WML deck is not "well formed" (using the formal XML
definition of the term), the user agent shall not display the deck. [WML Specification section 7.4] |
|
| ID: |
wml/syntax/entities/1 |
| Class: |
A |
| Text: |
When a numeric character entity is enountered, it is translated into the corresponding character in the document character set. [WML Specification section 7.1] |
|
| ID: |
wml/syntax/entities/2 |
| Class: |
A |
| Text: |
When a named character entity is enountered, it is translated into the corresponding character in the document character set. [WML Specification section 7.1] |
|
| ID: |
wml/syntax/elements/1 |
| Class: |
A |
| Text: |
When an element is declared EMPTY in the WML DTD, it may be specified using the shorthand notation <ELEMENT/>. User agents shall treat documents that use this convention and are otherwise conforming as well formed. [WML Specification section 7.2] |
|
| ID: |
wml/syntax/elements/2 |
| Class: |
A |
| Text: |
When an element is not declared EMPTY in the WML DTD, and such
an element has no contents, it may be specified as <ELEMENT/> or as
<ELEMENT></ELEMENT>. User agents shall treat documents that use either convention and are otherwise conforming as well formed. [WML Specification section 7.2] |
|
| ID: |
wml/syntax/elements/3 |
| Class: |
A |
| Text: |
Element names are case-sensitive, and are defined by the WML DTD
as being lower-case. The gateway shall not interpret
upper-case versions of the element names as their lower-case
equivalents. [WML Specification section 7.6] |
|
| ID: |
wml/syntax/attributes/1 |
| Class: |
A |
| Text: |
Element attribute values must be enclosed in quotation marks. When an
attribute value is enclosed in single quotation marks ('), the value
may contain double-quotation marks ("). [WML Specification section 7.3] |
|
| ID: |
wml/syntax/attributes/2 |
| Class: |
A |
| Text: |
Element attribute values must be enclosed in quotation marks. When an
attribute value is enclosed in double quotation marks ("), the value
may contain single quotation marks ('). [WML Specification section 7.3] |
|
| ID: |
wml/syntax/attributes/3 |
| Class: |
A |
| Text: |
Element attribute values may contain character entities. Entity
transformation into the document character set shall not effect the
interpretation of quotation marks enclosing attribute values, nor
shall it effect the parsing of attribute values. [WML Specification section 7.3] |
|
| ID: |
wml/syntax/attributes/4 |
| Class: |
A |
| Text: |
Element attribute names are case sensitive, and are defined to
be lowercase in the WML DTD. The gateway shall not interpret
upper-case versions of the attribute names as their lower-case
equivalents. [WML Specification section 7.3] |
|
| ID: |
wml/syntax/attributes/5 |
| Class: |
A |
| Text: |
Element attribute values that are defined as enumerated lists in
the WML DTD (e.g. the value for the MODE attribute of the P element)
are case sensitive, and are defined to be lower-case.
The gateway shall not interpret upper-case versions of these attribute
values as their lower-case equivalents. [WML Specification section 7.3] |
|
| ID: |
wml/syntax/comments/1 |
| Class: |
A |
| Text: |
When an XML comment (<!-- comment -->) is included in a deck, the contents of that comment
shall not be presented to the user. [WML Specification section 7.4] |
|
| ID: |
wml/syntax/comments/2 |
| Class: |
A |
| Text: |
When nested comments are encountered the gateway must produce an error [WML Specification section 7.4] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 -
Assertion text changed. |
|
| ID: |
wml/syntax/variables/1 |
| Class: |
A |
| Text: |
When the symbol "$", followed by an identifier, is encountered in a %PCDATA
or %vdata context, it is a variable reference. The variable reference is
replaced with the
value of the variable thus named. [WML Specification section 7.5] |
|
| ID: |
wml/syntax/variables/2 |
| Class: |
A |
| Text: |
When the symbol "$", followed by an identifier enclosed in parenthesis,
is encountered in a %PCDATA
or %vdata context, it is a variable reference. The variable reference is
replaced with the
value of the variable thus named. [WML Specification section 7.5] |
|
| ID: |
wml/syntax/variables/3 |
| Class: |
A |
| Text: |
When the symbol "$", followed by an identifier, a colon ":" and a
conversion specifier, enclosed in parenthesis,
is encountered in a %PCDATA
or %vdata context, it is a variable reference and an indicator as to how the
variable value should be converted. The variable reference is
replaced with the
value of the variable thus named, converted as specified. [WML Specification section 7.5] |
|
| ID: |
wml/syntax/variables/4 |
| Class: |
A |
| Text: |
When the symbol "$$"
is encountered in a %PCDATA
or %vdata context, it is an escaped dollar-sign.
The escaped dollar-sign is
replaced with a dollar-sign. [WML Specification section 7.5] |
|
| ID: |
wml/syntax/variables/5 |
| Class: |
B |
| Text: |
When variables are referenced within %CDATA attributes the encoder must
produce an error. [WML Specification section 7.5] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Added
the word attributes. Can't test as a variable reference in %CDATA is interpreted as a
string its self. |
|
Case sensitivity is linked to elements and attributes. It is tested
in those contexts.
| ID: |
wml/syntax/cdata/1 |
| Class: |
A |
| Text: |
When data is enclosed within a CDATA block ( <![CDATA[ data ]] >
), the data is handled as literal text and presented to the user "as is". [WML Specification section 7.7] |
|
| ID: |
wml/syntax/pi/1 |
| Class: |
A |
| Text: |
When a processing instruction ( <? instruction ?> ) is
encountered, it is ignored unless it is defined in the XML 1.0 Recommendation. [WML Specification section 7.8] |
|
Errors can occur in many elements and attributes. They are tested in those
contexts.
There are no testable assertions in this section.
In WML a LENGTH can be specified as either a number (indicating the number of
pixels) or as a percentage (indicating a relative length). Assertions
about LENGTHs are defined in the context of attributes that take LENGTHs
as arguments.
The vdata entity is a string that may contain variable references. Assertions
about the use of variables references in vdata are provided in
context throughout this document.
There are no testable assertions in this section.
There are no testable assertions in this section.
| ID: |
wml/coredata/boolean/1 |
| Class: |
A |
| Text: |
When a boolean value is required the encoder shall only accept the
values "true" or "false". Other values result in an error. [WML Specification section 8.6] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Changed
case of true and false |
|
NOTICE TO REVIEWER...IN THE PREVIOUS VERSION THERE IS A TEST FOR
number/1, HOWEVER THIS TEST IS NOT PRESENT IN THE wapJun00.2 DIRECTORY STRUCTURE
PLEASE INVESTIGATE AND LET ME KNOW...GARY
| ID: |
wml/coredata/xmllang/1 |
| Class: |
B |
| Text: |
An elements language must be established according to the following
precedence (fron highest to lowest): 1) Based on the xml:lang attribute for
the element. 2) Based on the xml:lang attribute specified by the closest
parent element. 3) Based on any language information included in the
transport and document meta data. 4) Based on user agent default preferences. [WML Specification section 8.8] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/coredata/id_class/1 |
| Class: |
B |
| Text: |
When two elements of a deck share a common class name they are
considered as part of the same class. [WML Specification section 9.8] |
| Note: |
Added with wml version 1.3. Ths user agent is not expected to
do anything with the class names. Class names can be used for such tasks
as server-side transformations. |
|
| ID: |
wml/coredata/id_class/2 |
| Class: |
B |
| Text: |
When two elements have the same class name, but differing in case, they
shall be treated as two different classes. [WML Specification section 8.9] |
| Note: |
Added with wml version 1.3. Ths user agent is not expected to
do anything with the class names. Class names can be used for such tasks
as server-side transformations. |
|
Refer to section 9.5.1 The Go Element.
There are no testable assertions in this section.
The WML specification defines various requirements about user agent handling
of history data. Assertions regarding these requirements are provided in the
context of elements that manipulate the history of the user agent.
| ID: |
wml/events/postfield/1 |
| Class: |
A |
| Text: |
The NAME attribute of the POSTFIELD element defines the name of a field,
and the VALUE attribute defines the value to associate with that NAME. When
a GO task is executed the name and value of the field are sent to the server. [WML Specification section 9.3] |
|
| ID: |
wml/events/setvar/1 |
| Class: |
A |
| Text: |
When a SETVAR element contains a NAME attribute that does not evaluate to a
legal variable name, the element is ignored. [WML Specification section 9.4] |
|
| ID: |
wml/events/setvar/2 |
| Class: |
A |
| Text: |
When a SETVAR element contains a NAME attribute that evaluates to a
legal variable name, the value of that variable (in the current browser
context) is set to the value of the VALUE attribute. [WML Specification section 9.4] |
|
| ID: |
wml/events/tasks/go/1 |
| Class: |
A |
| Text: |
When the HREF attribute of the GO element specifies a URL that names a
WML card or deck, prior to displaying the card (or deck), the location of the
current card is pushed onto the history stack. [WML Specification section 9.5.1] |
|
| ID: |
wml/events/tasks/go/2 |
| Class: |
A |
| Text: |
When the SENDREFERER attribute of the GO element is set to true,
the user agent must send the URL of the deck containing this task to
the server. The URL sent must be the smallest relative URL possible if
it can be relative at all. [WML Specification section 9.5.1] |
| Note: |
Check the HTTP_REFERER header for the smallest possible URL. This
will be the deck name. Therefore just test to make sure at least the deck name
is returned. |
|
| ID: |
wml/events/tasks/go/3 |
| Class: |
A |
| Text: |
When the METHOD attribute of the GO element is set to GET,
it defines the submission method for the request. [WML Specification section 9.5.1] |
|
| ID: |
wml/events/tasks/go/4 |
| Class: |
A |
| Text: |
When the METHOD attribute of the GO element is not set,
the submission method for the request defaults to GET. [WML Specification section 9.5.1] |
|
| ID: |
wml/events/tasks/go/5 |
| Class: |
A |
| Text: |
When the SENDREFERER attribute of the GO element is set to "false" or is
not set, the user agent must not send the URL of the deck containing this task
to the server. [WML Specification section 9.5.1] |
|
| ID: |
wml/events/tasks/go/6 |
| Class: |
B |
| Text: |
When the ACCEPT-CHARSET attribute of the GO element is not set,
the character encoding for submissions defaults to the character set of the
enclosing deck. [WML Specification section 9.5.1] |
|
| ID: |
wml/events/tasks/go/7 |
| Class: |
B |
| Text: |
When the ACCEPT-CHARSET attribute of the GO element is specified as a list of
comma- or space-separated character encoding names as specified in RFC 2045
and RFC2048, the server will accept submissions in any of the encodings
specified. [WML Specification section 9.5.1] |
|
| ID: |
wml/events/tasks/go/8 |
| Class: |
A |
| Text: |
When the METHOD attribute of the GO element is set to POST,
it defines the submission method for the request. [WML Specification section 9.5.1] |
|
| ID: |
wml/events/tasks/go/9 |
| Class: |
A |
| Text: |
When the target of a GO element of a card is contained within the
current deck the user agent must ignore all postfield elements. [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/tasks/go/10 |
| Class: |
A |
| Text: |
When the cache-control attribure is present within the GO element and
its value is set to "no-cache" the client must reload the URL from the origin
server. [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/tasks/go/11 |
| Class: |
B |
| Text: |
The encoder should transcode field names and values from the user-agent
to the correct character set specified explicitly by the ACCEPT-CHARSET or
implicitly by the document encoding. [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. How can you tell how the encoder
transcodes? |
|
| ID: |
wml/events/tasks/go/12 |
| Class: |
A |
| Text: |
When the HREF attribute value of a GO element is an HTTP URI, the
METHOD attribute has a value of "post" and the ENCTYPE attribute is
"application/x-www-form-urlencoded" the request must be performed according to
these attributes. [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/tasks/go/13 |
| Class: |
A |
| Text: |
When the METHOD of a GO element is specified as "GET" and the ENCTYPE
attributes value is set to "MULTIPART/FORM-DATA" the encoder shall produce
an error. [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/tasks/go/14 |
| Class: |
A |
| Text: |
When the ENCTYPE attributes value of a GO element is
"APPLICATION/X-WWW-FORM-URLENCODED", the field names and values must be
encoded using URI-escaping, and listed in the order in which the postfields
are presented. [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/tasks/go/15 |
| Class: |
A |
| Text: |
When the ENCTYPE attributes value is "APPLICATION/X-WWW-FORM-URLENCODED",
the field names and values must be encoded by the name seperated from the
value by "=" and name/value pairs seperated from each other by "&". [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Test
added. |
|
| ID: |
wml/events/tasks/go/16 |
| Class: |
C |
| Scope: |
"The client ONLY supports data submission as 'application/x-www-form-urlencoded' content type" |
| Text: |
When the user agent only supports data submission as
"APPLICATION/X-WWW-FORM-URLENCODED" content type, it may ignore the ENCTYPE
attribute. [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/tasks/go/17 |
| Class: |
B |
| Text: |
When the ACCEPT-CHARSET attribute is the reserved string "unknown",
the user agent should use the character encoding that was used to transmit the
WML deck that contains the GO element. [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. How can you tell how the encoder
encodes? |
|
| ID: |
wml/events/tasks/go/18 |
| Class: |
B |
| Text: |
When the ACCEPT-CHARSET attribute is not specified, the user agent
should use the character encoding that was used to transmit the WML deck
that contains the GO element [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. How can you tell how the encoder
encodes? |
|
| ID: |
wml/events/tasks/go/19 |
| Class: |
A |
| Text: |
When the HREF attribute value of a GO element is an HTTP URI, the
METHOD attribute has a value of "get" and the ENCTYPE attribute is
"application/x-www-form-urlencoded" the request must be performed according to
these attributes. [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/tasks/go/20 |
| Class: |
C |
| Scope: |
"The client DOES support the multipart/form-data content type" |
| Text: |
When the HREF attribute value of a GO element is an HTTP URI, the
METHOD attribute has a value of "post" and the ENCTYPE attribute is
"multipart/form-data" the request must be performed according to
these attributes. [WML Specification section 9.5.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/tasks/prev/1 |
| Class: |
A |
| Text: |
When a PREV element is executed, the card referenced by the previous URI in
the history stack is loaded (if necessary) and executed. [WML Specification section 9.5.2] |
|
| ID: |
wml/events/tasks/prev/2 |
| Class: |
A |
| Text: |
When a PREV element is executed, the previous URI on the history stack
is removed from the stack. [WML Specification section 9.5.2] |
|
|
| ID: |
wml/events/tasks/refresh/2 |
| Class: |
A |
| Text: |
When a REFRESH element is executed, any variables specified through enclosed
SETVAR elements are set in the browser context prior to the card being redisplayed. [WML Specification section 9.5.3] |
|
The NOOP element has effect in conjunction with other event handler elements.
It is tested in those contexts.
| ID: |
wml/events/shadowing/1 |
| Class: |
A |
| Text: |
When an event-handling element is specified within a TEMPLATE element,
that event-handler is available in each card of the deck. [WML Specification section 9.6] |
|
| ID: |
wml/events/shadowing/2 |
| Class: |
B |
| Text: |
When an event-handling element is specified within a TEMPLATE element,
and an event-handling element identifying the same event is specified within a
CARD element, the CARD level element overrides the handler within the
TEMPLATE. [WML Specification section 9.6] |
| Note: |
made untestable whilst specfication interpretation resolved - PR2254 |
|
| ID: |
wml/events/shadowing/3 |
| Class: |
A |
| Text: |
When an event-handling element is specified within a TEMPLATE element,
and an event-handling element identifying the same event is specified within a
CARD element, and that handler specifies its task as NOOP, there is no event
handler for the event within the card. The user agent shall not provide a
control for this event in this card. [WML Specification section 9.6] |
|
| ID: |
wml/events/shadowing/4 |
| Class: |
A |
| Text: |
When a card level element binds a noop task and is not shadowed by
another element the event will be masked and ignored. [WML Specification section 9.6] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/do/1 |
| Class: |
A |
| Text: |
When a DO element is specified within a TEMPLATE element, the user agent
shall behave as if the element is specified at the end of the CARD element. [WML Specification section 9.7] |
|
| ID: |
wml/events/do/2 |
| Class: |
A |
| Text: |
When a DO element is specified within a TEMPLATE element,
and a DO element with the same NAME attribute is specified within a
CARD element, the CARD level element overrides the TEMPLATE level element. [WML Specification section 9.7] |
|
|
| ID: |
wml/events/do/4 |
| Class: |
A |
| Text: |
When a DO element has a task other than NOOP, it shall be presented to the
user. [WML Specification section 9.7] |
|
| ID: |
wml/events/do/5 |
| Class: |
A |
| Text: |
When a DO element from a TEMPLATE is overridden by a DO element in a
CARD, the DO elements from the TEMPLATE shall not be presented to the
user. [WML Specification section 9.7] |
|
| ID: |
wml/events/do/6 |
| Class: |
D |
| Scope: |
"The client supports the setting of dynamic labels via the LABEL attribute of the DO element" |
| Text: |
When a LABEL attribute of a DO element specifies a %vdata string, user
agents that support dynamic labelling of widgets shall use the value of the
LABEL attribute to label the widget. [WML Specification section 9.7] |
| Note: |
Made untestable with PR number 2412 |
|
| ID: |
wml/events/do/7 |
| Class: |
A |
| Text: |
When a NAME attribute of a DO element is specified, its value names the
DO element. All uniquely named, active DO elements in a DECK shall be presented to
the user. [WML Specification section 9.7] |
|
| ID: |
wml/events/do/8 |
| Class: |
B |
| Text: |
When a NAME attribute of a DO element is not specified (or is specified
as ""), its value
defaults to the value of the TYPE attribute. [WML Specification section 9.7] |
|
| ID: |
wml/events/do/9 |
| Class: |
B |
| Text: |
When the DO element appears inside a CARD element it should use the
DO elements anchor point as the rendering point. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Changed
to untestable as it is up to the user agent how it renders a particular
element inline. |
|
| ID: |
wml/events/do/10 |
| Class: |
A |
| Text: |
User agents must accept any TYPE, but may treat any unrecognised
type as the equivalent of UNKNOWN. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/do/11 |
| Class: |
A |
| Text: |
When the OPTIONAL attribute of a DO element is set to "false" or is
omitted, the DO event must be presented to the user. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Text
changed. |
|
| ID: |
wml/events/do/12 |
| Class: |
B |
| Text: |
When the OPTIONAL attribute of a DO element is set to TRUE. The user
agent must decide weather to show that DO element. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Can't create a test as it is not known
when a user agent will ignore such elements. |
|
| ID: |
wml/events/do/13 |
| Class: |
B |
| Text: |
Inactive DO elements must not be selectable by the user. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Can't create a test as it is not known
when a user agent will ignore such elements. Revised ref WAG comments 06/00 -
Text changed. |
|
| ID: |
wml/events/do/14 |
| Class: |
A |
| Text: |
When two or more DO elements with the same NAME are specified in
a single CARD element the gateway shall display an error. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/do/15 |
| Class: |
D |
| Scope: |
"The client produces an error when two or more DO elements have the same name within a card or template" |
| Text: |
When two or more DO elements with the same NAME are specified in
a single CARD element the user agent shall display an error along with a means
to continue browser navigation. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Can't be tested as the gateway will capture the
error before it gets to the user agent. |
|
| ID: |
wml/events/do/16 |
| Class: |
A |
| Text: |
When two or more DO elements with the same NAME are specified in
a the TEMPLATE element the gateway shall produce an error. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/do/17 |
| Class: |
D |
| Scope: |
"The client produces an error when two or more DO elements have the same name within a card or template" |
| Text: |
When two or more DO elements with the same NAME are specified in
a the TEMPLATE element the user agent should display an error along with a
means to continue browser navigation. [WML Specification section 9.7] |
| Note: |
Can't be tested as the gateway would catch ther error before it got to the
user agent |
|
| ID: |
wml/events/do/18 |
| Class: |
A |
| Text: |
When the TYPE attribute of the DO element is "ACCEPT" the user agent
must display the event as an option. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Text
changed. |
|
| ID: |
wml/events/do/19 |
| Class: |
A |
| Text: |
When the TYPE attribute of the DO element is "PREV" the user agent
must display the event as an option. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/do/20 |
| Class: |
A |
| Text: |
When the TYPE attribute of the DO element is "HELP" the user agent
must display the event as an option. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/do/21 |
| Class: |
A |
| Text: |
When the TYPE attribute of the DO element is "RESET" the user agent
must display the event as an option. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Text
error changed GO > DO. |
|
| ID: |
wml/events/do/22 |
| Class: |
A |
| Text: |
When the TYPE attribute of the DO element is "DELETE" the user agent
must display the event as an option. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Text
changed. GO > DO. |
|
| ID: |
wml/events/do/23 |
| Class: |
A |
| Text: |
When the TYPE attribute of the DO element is "OPTIONS" the user agent
must display the event as an option. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Added. |
|
| ID: |
wml/events/do/24 |
| Class: |
A |
| Text: |
When the TYPE attribute of the DO element is "UNKNOWN" the user agent
must display the event as an option. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Added. |
|
| ID: |
wml/events/do/25 |
| Class: |
B |
| Text: |
When the TYPE attribute of the DO element is "X-*,x-*" the user agent
must display the event as an option. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Added.
This can't be tested as it is not known what experimental types are being
tested. If they are unknown to the user agent then they will be the same as
the UNKNOWN assertion. |
|
| ID: |
wml/events/do/26 |
| Class: |
B |
| Text: |
When the TYPE attribute of the DO element is "vnd.*,VND.*" the user agent
must display the event as an option. [WML Specification section 9.7] |
| Note: |
Added with wml version 1.3. Revised ref WAG comments 06/00 - Added.
This can't be tested as it is not known what vendor-specific types are being
tested. If they are unknown to the user agent then they will be the same as
the UNKNOWN assertion. |
|
| ID: |
wml/events/anchor/1 |
| Class: |
A |
| Text: |
When an ANCHOR element is specified, its contents define a link (via a task
element such as GO, PREV, or REFRESH) that is activated when the link is selected. [WML Specification section 9.8] |
|
| ID: |
wml/events/anchor/2 |
| Class: |
A |
| Text: |
If more that one task is specified within an ANCHOR element the user
gateway shall produce an error. [WML Specification section 9.8] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/anchor/3 |
| Class: |
D |
| Scope: |
"The client supports the use of ACCESSKEYS" |
| Text: |
When an ACCESSKEY is assigned to an ANCHOR element the user agent shall
respect the requested value or the user agent shall assign available keys to
the remaining elements that request them in the order they are requested in
the card, until all available keys are assigned. [WML Specification section 9.8] |
| Note: |
Added with wml version 1.3. This is impossible to test as it is not
known what accesskeys the user agent may have. |
|
| ID: |
wml/events/anchor/4 |
| Class: |
D |
| Scope: |
"The client supports the use of ACCESSKEYS" |
| Text: |
When an ACCESSKEY is assigned to an ANCHOR element and all of the user
agents access keys have been asigned they should be ignored. [WML Specification section 9.8] |
| Note: |
Added with wml version 1.3. Made class D with reference to PR 2417 |
|
| ID: |
wml/events/a/1 |
| Class: |
A |
| Text: |
When the HREF attribute of the A element is specified, it defines the
URL of a resource to be associated with the items within the A element.
Selecting the contents of the A element causes the resource referenced to be loaded. [WML Specification section 9.9] |
|
| ID: |
wml/events/a/2 |
| Class: |
A |
| Text: |
If A elements are nested the encoder shall produce an error [WML Specification section 9.9] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/a/3 |
| Class: |
D |
| Scope: |
"The client supports the use of ACCESSKEYS" |
| Text: |
User agents should render the value of ACCESSKEYS within an A element
in such a way as to emphasise its role and to distinguish it from other
characters. [WML Specification section 9.9] |
| Note: |
Added with wml version 1.3. Made class D with reference to PR 2417 |
|
| ID: |
wml/events/a/4 |
| Class: |
D |
| Scope: |
"The client supports the use of ACCESSKEYS" |
| Text: |
When an ACCESSKEY is assigned to an A element the user agent shall
respect the requested value, or the user agent shall assign available keys to
the remaining elements that request them in the order they are requested in
the card, until all available keys are assigned. [WML Specification section 9.9] |
| Note: |
Added with wml version 1.3. This is impossible to test as it is not
known what accesskeys the user agent may have. |
|
The intrinsic events are tested in the context of the ONEVENT element.
| ID: |
wml/events/intrinsics/1 |
| Class: |
A |
| Text: |
If the event binding element specifies an intrinsic event type which
applies to its parent element, it must be ignored by the user agent. [WML Specification section 9.10] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/events/intrinsics/2 |
| Class: |
A |
| Text: |
Conflicting event bindings within an element shall result in the
gateway producing an error. [WML Specification section 9.10] |
| Note: |
Added with wml version 1.3. |
|
The ONEVENT element is tested through the testing of each of the defined event
types.
| ID: |
wml/events/intrinsics/onevent/1 |
| Class: |
A |
| Text: |
The user agent must ignore any ONEVENT element specifying a type
that does not correspond to a legal intrinsic event for the immediately
enclosing element. [WML Specification section 9.10.1] |
| Note: |
Added with wml version 1.3. ONPICK is the only intrinsic event
that can not be placed in a card or deck, so that is used for this test. |
|
| ID: |
wml/events/intrinsics/onevent/onenterbackward/1 |
| Class: |
B |
| Text: |
When an ONEVENT element occurs immediately within a TEMPLATE or CARD
element, and the TYPE attribute of the ONEVENT element is specified using the
value "onenterbackward", the ONEVENT element defines a task to be executed when the user
causes the card to be entered via the PREV element (or actions with identical
semantics). [WML Specification section 9.10] |
|
| ID: |
wml/events/intrinsics/onevent/onenterbackward/2 |
| Class: |
A |
| Text: |
When an ONEVENT element occurs NOT immediately within a TEMPLATE or CARD
element, and the TYPE attribute of the ONEVENT element is specified using the
value "onenterbackward", the ONEVENT element is ignored. [WML Specification section 9.10] |
|
| ID: |
wml/events/intrinsics/onevent/onenterbackward/1 |
| Class: |
B |
| Text: |
When an ONEVENT element occurs immediately within a TEMPLATE or CARD
element, and the TYPE attribute of the ONEVENT element is specified using the
value "onenterbackward", the ONEVENT element defines a task to be executed when the user
causes the card to be entered via the PREV element (or actions with identical
semantics). [WML Specification section 9.10] |
|
| ID: |
wml/events/intrinsics/onevent/onenterbackward/2 |
| Class: |
A |
| Text: |
When an ONEVENT element occurs NOT immediately within a TEMPLATE or CARD
element, and the TYPE attribute of the ONEVENT element is specified using the
value "onenterbackward", the ONEVENT element is ignored. [WML Specification section 9.10] |
|
| ID: |
wml/events/intrinsics/onevent/onpick/1 |
| Class: |
A |
| Text: |
When an ONEVENT element occurs immediately within an OPTION
element, and the TYPE attribute of the ONEVENT element is specified using the
value "onpick", the ONEVENT element defines a task to be executed when the
user selects or deselects the item described by the OPTION element. [WML Specification section 9.10] |
|
| ID: |
wml/events/intrinsics/onevent/onpick/2 |
| Class: |
A |
| Text: |
When an ONEVENT element occurs NOT immediately within an OPTION
element, and the TYPE attribute of the ONEVENT element is specified using the
value "onpick", the ONEVENT element is ignored. [WML Specification section 9.10] |
|
| ID: |
wml/events/intrinsics/onevent/ontimer/1 |
| Class: |
A |
| Text: |
When an ONEVENT element occurs immediately within a TEMPLATE or CARD
element, and the TYPE attribute of the ONEVENT element is specified using the
value "ontimer", the ONEVENT element defines a task to be executed when the
TIMER expires. [WML Specification section 9.10] |
|
| ID: |
wml/events/intrinsics/onevent/ontimer/2 |
| Class: |
A |
| Text: |
When an ONEVENT element occurs NOT immediately within a TEMPLATE or CARD
element, and the TYPE attribute of the ONEVENT element is specified using the
value "ontimer", the ONEVENT element is ignored. [WML Specification section 9.10.1] |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
The NEWCONTEXT attribute is tested in the context of the CARD element in
section 11.5.2.
| ID: |
wml/state/variables/substitution/1 |
| Class: |
A |
| Text: |
When an undefined variable is referenced within any element or attribute
with a content type of %vdata, it results in the substitution
of the empty string. [WML Specification section 10.3.1] |
|
|
| ID: |
wml/state/variables/substitution/3 |
| Class: |
A |
| Text: |
When a variable is referenced within any element or attribute
with a content type of %vdata, and that variable reference is enclosed in
parenthesis using the pattern '(' name ':' conversion ')', the value of the
variable is converted before it is substituted. Legal conversion values are
"noesc", "escape", and "unesc" - meaning "no change", "URL-escape the value",
and "URL-unescape the value" respectively. [WML Specification section 10.3.1] |
|
| ID: |
wml/state/variables/substitution/4 |
| Class: |
A |
| Text: |
When a variable is referenced within any element or attribute
with a content type of %vdata, and that variable reference specifies no
conversion suffix, the default conversion is context sensitive. In the case of
ONPICK="onenterforward", ONPICK="onenterbackward", HREF, and SRC attributes the default is escape
conversion. [WML Specification section 10.3.1] |
|
| ID: |
wml/state/variables/substitution/6 |
| Class: |
A |
| Text: |
When variables are placed in the text(#PCDATA)of a card or into %vdata
and %HREF attributes in WML elements they are replaced with the variables
value. [WML Specification section 10.3.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/state/variables/substitution/7 |
| Class: |
A |
| Text: |
When a string substitution occurs, the current value of the variable
must not be altered. [WML Specification section 10.3.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/state/variables/substitution/8 |
| Class: |
A |
| Text: |
WML variable names consist of an US-ASCII letter or underscore
followed by zero or more letters, digits or underscores. Any other
characters are illegal. Any variable containing illegal characters shall
not be processed by the encoder. The remainder of the card should be
processed and displayed. [WML Specification section 10.3.1] |
| Note: |
Added with wml version 1.3. <br /><br />
This test has had a TSD granted against it [http://www.opengroup.org/WAP/PRs/ViewPR?PR_NO=2330] for the circumstances where the encoder behavior is preventing the test conditions being reached in the client under test. If this test is failing and you are convinced that it is the encoder behavior that is causing the problem you may invoke the TSD to resolve the failure. The CA may wish to see evidence supporting your claim, such as test results gathered from a test session with a different gateway in which the test runs to completion and passes. |
|
| ID: |
wml/state/variables/substitution/9 |
| Class: |
A |
| Text: |
When a variable is referenced within any element or attribute
with a content type of %vdata, and that variable reference specifies no
conversion suffix, the default is no conversion. [WML Specification section 10.3.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/state/variables/substitution/10 |
| Class: |
A |
| Text: |
When a variable is referenced within any element or attribute
with a content type of %HREF, and that variable reference specifies no
conversion suffix, the default is ESCAPE conversion. [WML Specification section 10.3.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/state/variables/parsing/1 |
| Class: |
A |
| Text: |
All XML parsing is complete prior to variable substitution. When a
dollar-sign in any form (a character entity, for example) is followed by a
variable name, it is interpreted as a variable reference. [WML Specification section 10.3.2] |
|
| ID: |
wml/state/variables/dollarsign/1 |
| Class: |
A |
| Text: |
When 2 dollar-signs in a row are encountered in a deck, they are
interpreted as a single literal dollar-sign. [WML Specification section 10.3.3] |
|
| ID: |
wml/state/variables/setting/1 |
| Class: |
A |
| Text: |
When a user commits the input in a SELECT element, the
associated variable value is updated. [WML Specification section 10.3.4] |
|
| ID: |
wml/state/variables/setting/2 |
| Class: |
A |
| Text: |
When a user commits the input in an INPUT element, the
associated variable value is updated. [WML Specification section 10.3.4] |
|
Validation assertions are carried out in the sections which contain the
elements and attributes.
| ID: |
wml/state/restrictions/1 |
| Class: |
C |
| Scope: |
"The client provides a means to reference and navigate to resources independent of the current context" |
| Text: |
Whenever a user agent navigates to a resource that was not the result of
an interaction with the content in the currentcontext, the user agent must
establish a fresh context for that navigation. [WML Specification section 10.4] |
| Note: |
Added with wml version 1.3. This requires the user to go to another
url not from a link on the current screen. Revised ref WAG comments 06/00 -
Changed text and test slightly. |
|
| ID: |
wml/struct/prologue/1 |
| Class: |
A |
| Text: |
When there is an error in the prologue the encoder shall produce an
error. [WML Specification section 11.1] |
| Note: |
Added with version 1.3. This test uses files with the prologue
included so that an error can be introduced in to it. |
|
| ID: |
wml/struct/prologue/2 |
| Class: |
A |
| Text: |
When the DTD reference in the prologue is invalid the encoder shall
produce an error. [WML Specification section 11.1] |
| Note: |
Added with version 1.3. This test uses files with the prologue
included so that an error can be introduced in to it. |
|
| ID: |
wml/struct/prologue/3 |
| Class: |
A |
| Text: |
When the prologue is omitted from the deck the encoder shall
produce an error. [WML Specification section 11.1] |
| Note: |
Added with version 1.3. This test uses files with the prologue
included so that an error can be introduced in to it. |
|
There are no testable assertions in this section.
| ID: |
wml/struct/head/access/1 |
| Class: |
A |
| Text: |
When an ACCESS element is in the HEAD element of a deck and that deck is
entered, the user agent checks to ensure that
the new deck can be accessed from the current deck. [WML Specification section 11.3.1] |
|
| ID: |
wml/struct/head/access/2 |
| Class: |
A |
| Text: |
When the DOMAIN attribute of the ACCESS element (of a new deck) is not set, it defaults to the domain of the current deck. [WML Specification section 11.3.1] |
|
| ID: |
wml/struct/head/access/3 |
| Class: |
A |
| Text: |
When the PATH attribute of the ACCESS element (of a new deck) is not set, it defaults to the value "/". [WML Specification section 11.3.1] |
|
| ID: |
wml/struct/head/access/4 |
| Class: |
A |
| Text: |
When the DOMAIN attribute of the ACCESS element (of a new deck)
is set to a period separated domain suffix, the domain of the current deck is
compared to this suffix - where each element specified must match exactly for
access to be granted. [WML Specification section 11.3.1] |
|
| ID: |
wml/struct/head/access/5 |
| Class: |
A |
| Text: |
When the PATH attribute of the ACCESS element (of a new deck) is
specified as an absolute path, it defines the path prefix that is permitted access to the deck -
where each element of the prefix must match that of the current deck exactly
for access to be granted. [WML Specification section 11.3.1] |
|
| ID: |
wml/struct/head/access/6 |
| Class: |
A |
| Text: |
When a deck contains more than one ACCESS element the user agent
shall display an error, along with a means to continue browser navigation. [WML Specification section 11.3.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/head/access/7 |
| Class: |
A |
| Text: |
When a user agent encounters a relative path in an ACCESS element
it shall convert it to an absolute path. Then it should perform prefix
matching against the PATH attribute [WML Specification section 11.3.1] |
| Note: |
Added with wml version 1.3. |
|
There are no testable assertions in this section.
| ID: |
wml/struct/template/1 |
| Class: |
A |
| Text: |
When an event binding (e.g. a DO or ONEVENT element) is specified within
a TEMPLATE element, that specification applies to all cards in the deck. [WML Specification section 11.4] |
|
| ID: |
wml/struct/template/2 |
| Class: |
A |
| Text: |
When a DO element is specified within a TEMPLATE element, and a
DO element with the same NAME attribute value is specified within a CARD
element, the DO element within the CARD element takes precedence. [WML Specification section 11.4] |
|
The intrinsic event attributes are tested within the context of the CARD
element.
| ID: |
wml/struct/card/events/1 |
| Class: |
A |
| Text: |
When the ONENTERFORWARD attribute of the CARD element is specified as a URL,
it defines a resource to navitage to when the CARD is entered via a GO event or the equivalent. [WML Specification section 11.5.1] |
|
| ID: |
wml/struct/card/events/2 |
| Class: |
A |
| Text: |
When the ONENTERBACKWARD attribute of the CARD element is specified as a URL,
it defines a resource to navigate to when the CARD is entered via a PREV event or the equivalent. [WML Specification section 11.5.1] |
|
| ID: |
wml/struct/card/events/3 |
| Class: |
A |
| Text: |
When the ONTIMER attribute of the CARD element is specified as a URL,
it defines a resource to navigate to when the timer for the CARD expires. [WML Specification section 11.5.1] |
|
| ID: |
wml/struct/card/elements/1 |
| Class: |
A |
| Text: |
When the ID attribute of the CARD element is specified as a string,
it defines a name for the card. This name can then be used in the fragment
portion of a URI to access the card directly. [WML Specification section 11.5.2] |
|
| ID: |
wml/struct/card/elements/2 |
| Class: |
A |
| Text: |
When the NEWCONTEXT attribute of the CARD element is specified as "true",
the current browser context is reinitialized when the
card is entered. [WML Specification section 11.5.2] |
|
| ID: |
wml/struct/card/elements/3 |
| Class: |
A |
| Text: |
When the NEWCONTEXT attribute of the CARD element is specified as
"false" or is not specified,
the current browser context is not initialized when the
card is entered. [WML Specification section 11.5.2] |
|
| ID: |
wml/struct/control/tabindex/1 |
| Class: |
C |
| Scope: |
"The client supports navigation via the TABINDEX attribute" |
| Text: |
When the TABINDEX attribute of an element is specified as a number, it defines
the relative position in the "tabbing order" within the card - where
numerically greater
numbers indicate a later position than numerically lesser numbers. [WML Specification section 11.6.1] |
|
| ID: |
wml/struct/control/tabindex/2 |
| Class: |
C |
| Scope: |
"The client supports navigation via the TABINDEX attribute" |
| Text: |
When the TABINDEX attribute of an input element is not specified, the user
agent assigns it a position in the "tabbing order" that is later than all
user-specified TABINDEX attributes within the card. [WML Specification section 11.6.1] |
|
| ID: |
wml/struct/control/select/element/iname/1 |
| Class: |
A |
| Text: |
When the INAME attribute of the SELECT element is specified, it defines
the name of a variable in which the index of the user selected option(s) will
be stored. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/2 |
| Class: |
A |
| Text: |
When the IVALUE attribute of the SELECT element is set, it
defines a default index value with which to select options within the SELECT
element. If the INAME attribute is also specified, and the variable named by
INAME already contains a value, the IVALUE attribute value is ignored. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/3 |
| Class: |
A |
| Text: |
When the INAME attribute of the SELECT element is set to a string, it
defines the name of a variable in which to record the user's selection(s).
When the MULTIPLE attribute of this SELECT element is set to TRUE, and
multiple options are selected, the value of the variable named by INAME is a
semi-colon separated list of selected option indices. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/4 |
| Class: |
A |
| Text: |
When the INAME attribute of the SELECT element is set to a string, it
defines the name of a variable in which to record the user's selection(s).
If the variable named by the INAME attribute is set when the element is
displayed, the value of the variable is used as indices to pre-select option(s) within
the SELECT element. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/5 |
| Class: |
A |
| Text: |
When the INAME attribute of the SELECT element is specified with a
variable name, and the value of that variable is
0, it indicates that no options within the SELECT element are selected. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/6 |
| Class: |
A |
| Text: |
When the INAME attribute of the SELECT element is specified with a
variable name, and that variable is not set, and the VALUE or IVALUE
attribute is not specified, and the MULTIPLE attribute is set to "TRUE",
the selected index defaults to 0. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/7 |
| Class: |
A |
| Text: |
When the INAME attribute of the SELECT element is specified with a
variable name, and that variable is set to a value greater than the largest
index of the enclosed OPTION elements, and the MULTIPLE attribute is set to
"TRUE", no option is selected. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/8 |
| Class: |
A |
| Text: |
When the INAME attribute of the SELECT element is not specified, and the
NAME attribute is specified as a
variable name, and that variable is set, the value of that variable is used to
select option(s). [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/9 |
| Class: |
A |
| Text: |
When the INAME attribute of the SELECT element is not specified, and the
NAME attribute is specified as a
variable name, and that variable is set, but the value to which it is set does
not match the VALUE attribute of an enclosed OPTION element, and the MULTIPLE
attribute is set to "TRUE", no option is
selected. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/10 |
| Class: |
A |
| Text: |
When the INAME attribute of the SELECT element is not specified, and the
NAME attribute is specified as a
variable name, and that variable is not set, and the MULTIPLE attribute is set
to FALSE, the first option is selected. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/11 |
| Class: |
A |
| Text: |
When the INAME attribute of the SELECT element is not specified, and the
NAME attribute is specified as a
variable name, and that variable is set, but the value to which it is set does
not match the VALUE attribute of an enclosed OPTION element, and the MULTIPLE
attribute is set to "FALSE", the first option is selected. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/12 |
| Class: |
A |
| Text: |
When the INAME attribute of the SELECT element is specified with a
variable name, and that variable is set to a value greater than the largest
index of the enclosed OPTION elements, and the MULTIPLE attribute is set to
"FALSE", the first option is selected. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/iname/13 |
| Class: |
A |
| Text: |
When the NAME and INAME variables are updated the user agent must not
display any side effects. [WML Specification section 11.6.2.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/control/select/element/ivalue/1 |
| Class: |
A |
| Text: |
When the IVALUE attribute of the SELECT element is set, it
defines a default value with which to select options within the SELECT
element. If the MULTIPLE attribute of the SELECT element is set to TRUE, this
default value is interpreted as a semi-colon separated list of option indices to
select. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/multiple/1 |
| Class: |
A |
| Text: |
When the MULTIPLE attribute of the SELECT element is set to TRUE, the
user is permitted to select multiple options from within the element. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/multiple/2 |
| Class: |
A |
| Text: |
When the MULTIPLE attribute of the SELECT element is set to FALSE, the
user is permitted to select only a single option from within the element. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/multiple/3 |
| Class: |
A |
| Text: |
When the MULTIPLE attribute of the SELECT element is not specified, the
user is permitted to select only a single option from within the element. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/name/1 |
| Class: |
A |
| Text: |
When the NAME attribute of the SELECT element is set to a legal variable
name, it
defines the name of a variable in which to record the user's selection(s). [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/name/2 |
| Class: |
A |
| Text: |
When the NAME attribute of the SELECT element is set to a string, it
defines the name of a variable in which to record the user's selection(s).
When the MULTIPLE attribute of this SELECT element is set to TRUE, and
multiple options are selected, the value of the variable named by NAME is a
semi-colon separated list of values. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/name/3 |
| Class: |
A |
| Text: |
When the NAME attribute of the SELECT element is set to a string, it
defines the name of a variable in which to record the user's selection(s).
If the variable named by the NAME attribute is set when the element is
displayed, the value of the variable is used to pre-select option(s) within
the SELECT element. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/value/1 |
| Class: |
A |
| Text: |
When the VALUE attribute of the SELECT element is set, it
defines a default value with which to select options within the SELECT
element. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/value/2 |
| Class: |
A |
| Text: |
When the VALUE attribute of the SELECT element is set, it
defines a default value with which to select options within the SELECT
element. If the NAME attribute is also specified, and the variable named by
NAME already contains a value, the VALUE attribute value is ignored. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/element/value/3 |
| Class: |
A |
| Text: |
When the VALUE attribute of the SELECT element is set, it
defines a default value with which to select options within the SELECT
element. If the MULTIPLE attribute of the SELECT element is set to TRUE, this
default value is interpreted as a semi-colon separated list of values to
select. [WML Specification section 11.6.2.1] |
|
| ID: |
wml/struct/control/select/option/1 |
| Class: |
A |
| Text: |
When the VALUE attribute of the OPTION element is set to a string, it
defines the value to be used when setting the variable named by the NAME
attribute of the enclosing SELECT element. [WML Specification section 11.6.2.2] |
|
| ID: |
wml/struct/control/select/option/2 |
| Class: |
A |
| Text: |
When the ONPICK attribute of the OPTION element is set to a URL, and
the MULTIPLE attribute of the enclosing SELECT element is set to TRUE, it
defines a task that is to be executed whenever the option is selected or
deselected. [WML Specification section 11.6.2.2] |
|
| ID: |
wml/struct/control/select/option/3 |
| Class: |
A |
| Text: |
When the ONPICK attribute of the OPTION element is set to a URL, and
the MULTIPLE attribute of the enclosing SELECT element is set to FALSE or not
specified, it
defines a task that is to be executed whenever the option is selected. [WML Specification section 11.6.2.2] |
|
| ID: |
wml/struct/control/select/option/4 |
| Class: |
A |
| Text: |
When the OPTION element contains PCDATA, that data is presented as the
description of the option. [WML Specification section 11.6.2.2] |
|
| ID: |
wml/struct/control/select/option/5 |
| Class: |
A |
| Text: |
When the OPTION element contains a value with a variable reference,
the variable is evaluated before the name variable is set. [WML Specification section 11.6.2.2] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/control/select/optgroup/1 |
| Class: |
C |
| Scope: |
"The client supports the use of OPTION GROUPS" |
| Text: |
When the OPTGROUP element is encountered, the implementation must allow
the elements to be grouped and displayed in a hierarchical manor. [WML Specification section 11.6.2.3] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/control/select/optgroup/2 |
| Class: |
A |
| Text: |
When a user agent encounters an OPTGROUP element it must display
the elements children in readable manner even if OPTGROUP is not supported. [WML Specification section 11.6.2.3] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/control/input/1 |
| Class: |
A |
| Text: |
All INPUT objects that represent the input elements within the card
must be initialized when the card is loaded. [WML Specification section 11.6.3] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/control/input/2 |
| Class: |
B |
| Text: |
All INPUT objects that represent the input elements within the card
must be initialized in the order in which they appear in the card. [WML Specification section 11.6.3] |
| Note: |
Added with wml version 1.3. It is not possible to see how objects
are initalized. |
|
| ID: |
wml/struct/control/input/3 |
| Class: |
A |
| Text: |
When the MAXLENGTH attribute of the INPUT element is specified as a
number, it defines the maximum number of characters that can be entered in the
input field. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/4 |
| Class: |
D |
| Scope: |
"The client supports the use of ACCESSKEYS" |
| Text: |
When the ACCESSKEY attribute of the INPUT element is specified the user
agent shall assign an ACCESSKEY for that element. [WML Specification section 11.6.3] |
| Note: |
Made class D with reference to PR 2417 |
|
| ID: |
wml/struct/control/input/emptyok/1 |
| Class: |
A |
| Text: |
When the EMPTYOK attribute of the INPUT element is specified as "true",
and the FORMAT attribute of the INPUT element is also specified,
the input field may be left blank by the user. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/emptyok/2 |
| Class: |
A |
| Text: |
When EMPTYOK is false, input is required even if the format mask
would otherwise not require it. [WML Specification section 11.6.3] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/control/input/emptyok/3 |
| Class: |
A |
| Text: |
When EMPTYOK is true, input is not required even if the format mask
would otherwise require it. [WML Specification section 11.6.3] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/control/input/format/1 |
| Class: |
A |
| Text: |
When the FORMAT attribute of the INPUT element is specified as "*A",
the text input is limited to upper-case letter, symbol or punctuation
characters. Numeric characters are excluded [WML Specification section 11.6.3] |
| Note: |
Text changed for wml 1.3 to make the tests less ambiguous. |
|
| ID: |
wml/struct/control/input/format/2 |
| Class: |
A |
| Text: |
When the FORMAT attribute of the INPUT element is specified as "*a",
the text input is limited to lower-case letter, symbol or punctuation
characters. [WML Specification section 11.6.3] |
| Note: |
Text changed for wml 1.3 to make the tests less ambiguous. |
|
| ID: |
wml/struct/control/input/format/3 |
| Class: |
A |
| Text: |
When the FORMAT attribute of the INPUT element is specified as "*N",
the text input is limited to numeric characters. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/format/4 |
| Class: |
A |
| Text: |
When the FORMAT attribute of the INPUT element is specified as "*X",
the text input is limited to entry of any uppercase letter, numeric character, symbol, or punctuation character. [WML Specification section 11.6.3] |
| Note: |
Text changed for wml 1.3 to make the tests less ambiguous. |
|
| ID: |
wml/struct/control/input/format/5 |
| Class: |
A |
| Text: |
When the FORMAT attribute of the INPUT element is specified as "*x",
the text input is limited to entry of any lowercase letter, numeric character, symbol, or punctuation character. [WML Specification section 11.6.3] |
| Note: |
Text changed for wml 1.3 to make the tests less ambiguous. |
|
| ID: |
wml/struct/control/input/format/7 |
| Class: |
A |
| Text: |
When the FORMAT attribute of the INPUT element is specified as a
backslash "\" followed by a character c, that character is displayed in the
input field at the position indicated. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/format/8 |
| Class: |
A |
| Text: |
When the FORMAT attribute of the INPUT element is specified as a series
of format characters, the input of each position in the input field is limited
as specified. [WML Specification section 11.6.3] |
| Note: |
Text changed for wml 1.3 to make the tests less ambiguous. |
|
| ID: |
wml/struct/control/input/format/9 |
| Class: |
A |
| Text: |
When the FORMAT attribute of the INPUT element is specified as "*M",
the text input is limited to any characters, but the user-agent may assume
that the input is in upper-case. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/format/10 |
| Class: |
A |
| Text: |
When the FORMAT attribute of the INPUT element is specified as "*m",
the text input is limited to any characters, but the user-agent may assume
that the input is in lower-case. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/format/11 |
| Class: |
A |
| Text: |
When the FORMAT attribute of the INPUT element is specified as "nM",
where n is a digit from 1-9 and f is one of the format characters "aAmMNXx", the
number of input characters is limited to n and the type is limited to f. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/format/12 |
| Class: |
A |
| Text: |
When the FORMAT attribute of the INPUT element is specified as an
invalid mask it must be ignored by the user agent. [WML Specification section 11.6.3] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/control/input/name/1 |
| Class: |
A |
| Text: |
The NAME attribute of the INPUT element specifies the name of a variable
in which the input value is stored. If this variable is set when the INPUT
element is displayed, its value is used to initialize the content of the input
field. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/type/1 |
| Class: |
A |
| Text: |
When the TYPE attribute of the INPUT element is specified as
"text", it indicates that the input field is a text entry box, and that
the input is to be displayed to the user in readable form. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/type/2 |
| Class: |
A |
| Text: |
When the TYPE attribute of the INPUT element is specified as
"password", it indicates that the input field is a password entry box, and that
the input is to be displayed to the user in an illegible form. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/type/3 |
| Class: |
A |
| Text: |
When the TYPE attribute of the INPUT element is not specified, it
defaults to
"text". This indicates that the input field is a text entry box, and that
the input is to be displayed to the user in readable form. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/value/1 |
| Class: |
A |
| Text: |
When the VALUE attribute of the INPUT element is specified, it
defines the default value for the variable named by the NAME attribute. When
the INPUT element is displayed and the variable named by the NAME attribute is
not set, that variable is initialized with the value of the VALUE attribute. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/input/value/2 |
| Class: |
A |
| Text: |
When the VALUE attribute of the INPUT element is specified, it
defines the default value for the variable named by the NAME attribute. When
the INPUT element is displayed and the variable named by the NAME attribute is
already set, the value of the VALUE attribute is ignored. [WML Specification section 11.6.3] |
|
| ID: |
wml/struct/control/fieldset/1 |
| Class: |
A |
| Text: |
When the FIELDSET element is used the user agent shall display
all input fields even if it does not support FIELDSETS. [WML Specification section 11.6.4] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/control/fieldset/2 |
| Class: |
C |
| Scope: |
"The client supports the use of FIELDSET" |
| Text: |
When the FIELDSET element is nested, the user agent must display all
of the fields. [WML Specification section 11.6.4] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/control/fieldset/3 |
| Class: |
B |
| Text: |
When the FIELDSET element is used and there are no fields in that set
the user agent shall display an error. [WML Specification section 11.6.4] |
| Note: |
made untestable whilst specfication interpretation resolved - PR2272 |
|
| ID: |
wml/struct/timer/1 |
| Class: |
A |
| Text: |
When the VALUE attribute of the TIMER element is specified as a positive
integer value and the NAME value is not specified, the VALUE attribute defines the default starting value for the timer.
Upon entering the card, the timer is started with this
value. If the card is not exited prior to the expiration of the timer, the
ONTIMER intrinsic event is delivered. [WML Specification section 11.7] |
|
| ID: |
wml/struct/timer/2 |
| Class: |
A |
| Text: |
When the NAME attribute of the TIMER element is specified as a string, it
defines a variable in which the timer value is to be stored. [WML Specification section 11.7] |
|
| ID: |
wml/struct/timer/3 |
| Class: |
A |
| Text: |
When the NAME attribute of the TIMER element is specified as a string, it
defines a variable name. If that variable is set, the timer is initialized
with the value of the variable. [WML Specification section 11.7] |
|
| ID: |
wml/struct/timer/4 |
| Class: |
A |
| Text: |
When the NAME attribute of the TIMER element is specified as a string, it
defines a variable name. If that variable is not set and the VALUE attribute
of the TIMER element is specified, the variable is set to the value of the
VALUE attribute, and then the variable is used to initialize the timer. [WML Specification section 11.7] |
|
| ID: |
wml/struct/timer/5 |
| Class: |
A |
| Text: |
When the NAME attribute of the TIMER element is specified as a string, it
defines a variable name. If that variable is set to zero, the timer is
disabled. [WML Specification section 11.7] |
|
| ID: |
wml/struct/timer/6 |
| Class: |
A |
| Text: |
When more than one TIMER element is used in a card the encoder shall
produce an error. [WML Specification section 11.7] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/timer/7 |
| Class: |
A |
| Text: |
When the value of the timeout is not a positive integer, the user agent
must ignore the TIMER element. [WML Specification section 11.7] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/text/whitespace/1 |
| Class: |
A |
| Text: |
When the encoder encounters white space in element and attribute
values it should be ignored. [WML Specification section 11.8.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/text/whitespace/2 |
| Class: |
A |
| Text: |
When the user agent encounters white space before or after an element
or attribute it should be ignored. [WML Specification section 11.8.1] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/text/emphasis/b/1 |
| Class: |
C |
| Scope: |
"The client supports the B element and a bold typeface" |
| Text: |
When the B inline element is used, the text enclosed within the
B
element is displayed in a bold typeface. [WML Specification section 11.8.2] |
|
| ID: |
wml/struct/text/emphasis/big/1 |
| Class: |
C |
| Scope: |
"The client supports the BIG element and a bigger typeface" |
| Text: |
When the BIG inline element is used, the text enclosed within the BIG
element is displayed in a larger typeface. [WML Specification section 11.8.2] |
|
| ID: |
wml/struct/text/emphasis/em/1 |
| Class: |
C |
| Scope: |
"The client supports the EM element and an emphasized typeface" |
| Text: |
When the EM inline element is used, the text enclosed within the EM
element is displayed in an alternative typeface to give emphasis to the text. [WML Specification section 11.8.2] |
|
| ID: |
wml/struct/text/emphasis/i/1 |
| Class: |
C |
| Scope: |
"The client supports the I element and an italic typeface" |
| Text: |
When the I inline element is used, the text enclosed within the
I
element is displayed in an italicized typeface. [WML Specification section 11.8.2] |
|
| ID: |
wml/struct/text/emphasis/small/1 |
| Class: |
C |
| Scope: |
"The client supports the SMALL element and a smaller typeface" |
| Text: |
When the SMALL inline element is used, the text enclosed within the
SMALL
element is displayed in a smaller typeface. [WML Specification section 11.8.2] |
|
| ID: |
wml/struct/text/emphasis/strong/1 |
| Class: |
C |
| Scope: |
"The client supports the STRONG element and a strong emphasis typeface" |
| Text: |
When the STRONG inline element is used, the text enclosed within the
STRONG element is displayed in an alternative typeface to give strong
emphasis to the text. [WML Specification section 11.8.2] |
|
| ID: |
wml/struct/text/emphasis/u/1 |
| Class: |
C |
| Scope: |
"The client supports the U element and an underlined typeface" |
| Text: |
When the U inline element is used, the text enclosed within the
U
element is displayed underlined. [WML Specification section 11.8.2] |
|
| ID: |
wml/struct/text/p/1 |
| Class: |
A |
| Text: |
When a non-breaking space entity is encountered, the user agent does not
treat it as an inter-word space. [WML Specification section 11.8.3] |
|
| ID: |
wml/struct/text/p/2 |
| Class: |
D |
| Scope: |
"The client DOES support the soft-hyphen entity for line breaks" |
| Text: |
When a soft-hyphen character entity is encountered, the user agent must
output a hyphen in its place if it is at the end of a line. [WML Specification section 11.8.3] |
| Note: |
Temporarily untestable with reference to PR 2387 |
|
| ID: |
wml/struct/text/p/3 |
| Class: |
D |
| Scope: |
"The client DOES support the soft-hyphen entity for line breaks" |
| Text: |
When a soft-hyphen character entity is encountered, the user agent must
not output a hyphen in its place if it does not occur at the end of a text
line. [WML Specification section 11.8.3] |
| Note: |
Temporarily untestable with reference to PR 2387 |
|
| ID: |
wml/struct/text/p/4 |
| Class: |
D |
| Scope: |
"The client DOES NOT support the soft-hyphen entity for line breaks" |
| Text: |
When a soft-hyphen character entity is encountered, the user agent must
ignore it when not supported [WML Specification section 11.8.3] |
| Note: |
Added with version 1.3. Temporarily untestable with reference to PR 2387 |
|
| ID: |
wml/struct/text/p/5 |
| Class: |
A |
| Text: |
When a P element is empty or contains only insignificant white space, it
must not impact line wrap mode. [WML Specification section 11.8.3] |
| Note: |
The test implements an insignificant paragraph which changes the line-wrap mode. The test then prompts the user to check that the change in line wrap mode was correctly ignored. |
|
| ID: |
wml/struct/text/p/align/1 |
| Class: |
A |
| Text: |
When the ALIGN attribute of the P element is specified as "left", the
text of the line is aligned on the left side of the display. [WML Specification section 11.8.3] |
|
| ID: |
wml/struct/text/p/align/2 |
| Class: |
A |
| Text: |
When the ALIGN attribute of the P element is specified as "center", the
text of the line is centered on the display. [WML Specification section 11.8.3] |
|
| ID: |
wml/struct/text/p/align/3 |
| Class: |
A |
| Text: |
When the ALIGN attribute of the P element is specified as "right", the
text of the line is aligned on the right side of the display. [WML Specification section 11.8.3] |
|
| ID: |
wml/struct/text/p/align/4 |
| Class: |
A |
| Text: |
When the ALIGN attribute of the P element is not specified, text is
aligned with the left side of the display. [WML Specification section 11.8.3] |
|
| ID: |
wml/struct/text/p/mode/1 |
| Class: |
A |
| Text: |
When the MODE attribute of the P element is specified as "wrap", the text
of the line is broken onto multiple display lines at whitespace characters as
needed. [WML Specification section 11.8.3] |
|
| ID: |
wml/struct/text/p/mode/2 |
| Class: |
A |
| Text: |
When the MODE attribute of the P element is specified as "nowrap", the text
of the line is displayed on a single line. [WML Specification section 11.8.3] |
|
| ID: |
wml/struct/text/p/mode/3 |
| Class: |
A |
| Text: |
When the MODE attribute of the P element is not specified, it defaults
to the MODE of the previous paragraph. [WML Specification section 11.8.3] |
|
| ID: |
wml/struct/text/p/mode/4 |
| Class: |
A |
| Text: |
When the MODE attribute of the P element is not specified, and the P
element is the first P element of the CARD, it defaults to "wrap" mode. [WML Specification section 11.8.3] |
|
| ID: |
wml/struct/text/br/1 |
| Class: |
A |
| Text: |
When a BR element is encountered, the user agent breaks the current
line. Subsequent text in the paragraph is continued on the following line. [WML Specification section 11.8.4] |
|
| ID: |
wml/struct/text/table/1 |
| Class: |
A |
| Text: |
When the COLUMNS attribute of the TABLE element is specified as a
non-negative integer, it defines the number of columns that each row of the
table shall contain. Rows with fewer than the specified number of columns have
empty columns added to their ends. [WML Specification section 11.8.5] |
|
| ID: |
wml/struct/text/table/2 |
| Class: |
A |
| Text: |
When the COLUMNS attribute of the TABLE element is specified as a
non-negative integer, it defines the number of columns that each row of the
table shall contain. Rows with more than the specified number of columns have
any additional data collected into the last defined column of the row, with
each column's data separated from the others by a single inter-word space. [WML Specification section 11.8.5] |
|
| ID: |
wml/struct/text/table/3 |
| Class: |
A |
| Text: |
When the ALIGN attribute of the TABLE element is specified as a sequence
of the letters "R", "L", or "C", one for each column in the table,
it defines the default alignment for data in
each column as right, left, or center, respectively. [WML Specification section 11.8.5] |
| Note: |
The table has 3 aligned columns (LCR). The prompt is "Is the table
data aligned as described?".
Revised ref WAG comments 06/00 - Prompts and tests chanced back to less strict
definitions. |
|
| ID: |
wml/struct/text/table/4 |
| Class: |
A |
| Text: |
When the ALIGN attribute of the TABLE element is specified as a sequence
of the letters "R", "L", or "C", but there are fewer letters than columns, the
contents of the unspecified columns get the default alignment (left for
left-to-right languages, right for right-to-left languages). [WML Specification section 11.8.5] |
| Note: |
A table has 3 columns aligned by RC. The prompt is "Is the table
data aligned as described?".
Revised ref WAG comments 06/00 - Prompts and tests chanced back to less strict
definitions. |
|
| ID: |
wml/struct/text/table/5 |
| Class: |
A |
| Text: |
When the ALIGN attribute of the TABLE element is not specified, the
contents of the columns get the
default alignment (left for
left-to-right languages, right for right-to-left languages). [WML Specification section 11.8.5] |
| Note: |
A table with no ALIGN attribute and 3 columns. The prompt is "
Is the table data aligned as described?".
Revised ref WAG comments 06/00 - Prompts and tests chanced back to less strict
definitions. |
|
| ID: |
wml/struct/text/table/6 |
| Class: |
A |
| Text: |
When a gateway encounters nested TABLE elements it must produce an error [WML Specification section 11.8.5] |
| Note: |
A nested table is produced. The prompt is ": Did the browser
indicates that the link could not be loaded or failed to render the new card?" |
|
| ID: |
wml/struct/text/table/7 |
| Class: |
A |
| Text: |
When the ALIGN attribute of the TABLE element is specified as "D" the
contents of that column will be default aligned (left for left-to-right
languages, right for right-to-left languages). All extra designators
should be ignored. [WML Specification section 11.8.5] |
| Note: |
A table with ALIGN attribute set to DDDLRC and 3 columns.
The prompt is "Is the table data aligned as described?".
Revised ref WAG comments 06/00 - Prompts and tests chanced back to less strict
definitions. |
|
| ID: |
wml/struct/text/table/8 |
| Class: |
A |
| Text: |
When the TABLE element is encountered and has zero rows the gateway
must produce an error. [WML Specification section 11.8.5] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/text/table/9 |
| Class: |
A |
| Text: |
When the ALIGN attribute of the TABLE element is specified as an
unknown designator the contents of that column will be default aligned
(left for left-to-right languages, right for right-to-left languages). [WML Specification section 11.8.5] |
| Note: |
Added with version 1.3. A table with the ALIGN attribute set to ZPQ
and 3 columns. The prompt is "Is the table data aligned as described?".
Revised ref WAG comments 06/00 - Prompts and tests chanced back to less strict
definitions. |
|
| ID: |
wml/struct/text/tr/1 |
| Class: |
A |
| Text: |
When a table row is empty it is significant and must not be ignored. [WML Specification section 11.8.6] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/text/td/1 |
| Class: |
A |
| Text: |
When the TD element is specified, it defines the contents of a single
cell of a row of a table. The contents of the element are rendered in the
cell. [WML Specification section 11.8.7] |
| Note: |
A table with 2 columns. Data for each is formatted within its cell.
The prompt is "Is the table data displayed within its cells?". |
|
| ID: |
wml/struct/text/td/2 |
| Class: |
A |
| Text: |
When the TD element is specified and but has no contents, the element
must still be counted as a cell for rendering purposes. [WML Specification section 11.8.7] |
| Note: |
A table has 3 columns. The middle cell of row two is blank. The
prompt is "Is the center cell of the table empty?". |
|
| ID: |
wml/struct/text/pre/1 |
| Class: |
D |
| Scope: |
"The client supports the PRE element" |
| Text: |
When the PRE element is used, the enclosed text is 'preformatted'. The
user agent may leave white space intact, render text with a fixed-pitch font
and may disable automatic word wrap. [WML Specification section 11.8.9] |
| Note: |
Added with wml version 1.3. |
|
| ID: |
wml/struct/images/1 |
| Class: |
A |
| Text: |
When the ALT attribute of the IMG element is specified as a string, it
defines alternate text that is displayed when the image cannot be loaded. [WML Specification section 11.9] |
|
| ID: |
wml/struct/images/2 |
| Class: |
C |
| Scope: |
"The client supports media type image/vnd.wap.wbmp" |
| Text: |
When the SRC attribute of the IMG element is specified as a URL, it
defines the location of the image data. [WML Specification section 11.9] |
|
| ID: |
wml/struct/images/3 |
| Class: |
C |
| Scope: |
"The client supports the vspace attribute in the image element and WBMP-format images" |
| Text: |
When the VSPACE attribute of the IMG element is specified as a length, it
defines the vertical whitespace to be inserted above and below the image. [WML Specification section 11.9] |
| Note: |
The vspace attribute value is tested using two images with two absolute values of 8 and 16 respectively. The test prompt checks that whitespace exists above and below each image with the whitespace visibly greater around the second image. |
|
| ID: |
wml/struct/images/4 |
| Class: |
C |
| Scope: |
"The client supports the hspace attribute in the image element and WBMP-format images" |
| Text: |
When the HSPACE attribute of the IMG element is specified as a length, it
defines the horizontal whitespace to be inserted to the left and right of the image. [WML Specification section 11.9] |
| Note: |
The hspace attribute value is tested using two images with two absolute values of 8 and 16 respectively. The test prompt checks that whitespace exists to the left and right of each image with the whitespace visibly greater around the second image. |
|
| ID: |
wml/struct/images/5 |
| Class: |
C |
| Scope: |
"The client supports the vspace attribute in the image element and WBMP-format images" |
| Text: |
When the VSPACE attribute of the IMG element is not specified, it
defaults to zero length. [WML Specification section 11.9] |
|
| ID: |
wml/struct/images/6 |
| Class: |
C |
| Scope: |
"The client supports the hspace attribute in the image element and WBMP-format images" |
| Text: |
When the HSPACE attribute of the IMG element is not specified, it
defaults to zero length. [WML Specification section 11.9] |
|
| ID: |
wml/struct/images/7 |
| Class: |
C |
| Scope: |
"The client supports the align attribute in the image element and WBMP-format images" |
| Text: |
When the ALIGN attribute of the IMG element is specified as TOP, it
means that the top of the image is aligned vertically with the top of the
current text line. [WML Specification section 11.9] |
|
| ID: |
wml/struct/images/8 |
| Class: |
C |
| Scope: |
"The client supports the align attribute in the image element and WBMP-format images" |
| Text: |
When the ALIGN attribute of the IMG element is specified as BOTTOM, it
means that the bottom of the image is aligned vertically with the current
baseline. [WML Specification section 11.9] |
|
| ID: |
wml/struct/images/9 |
| Class: |
C |
| Scope: |
"The client supports the align attribute in the image element and WBMP-format images" |
| Text: |
When the ALIGN attribute of the IMG element is specified as MIDDLE, it
means that the vertical center of the image is aligned vertically with the
center of the current text line. [WML Specification section 11.9] |
|
| ID: |
wml/struct/images/10 |
| Class: |
B |
| Text: |
When the LOCALSRC attribute is specified the user agent should use
this as the source of the file. LOCALSRC takes precedence over the image
specified in the SRC parameter. [WML Specification section 11.9] |
| Note: |
Test is untestable. It is not possible to determine whether the image specified in the LOCALSRC attribute is already present within the WAP Client at the time of execution. |
|
| ID: |
wml/struct/images/11 |
| Class: |
A |
| Text: |
When the ALT attribute of the IMG element is specified as a string, it
defines alternate text that is displayed when the user agent does not support
the image format. [WML Specification section 11.9] |
|
Deck access control is linked to other elements and attributes.
It is tested in those contexts.
There are no testable assertions in this section.
Error handling is linked to other elements and attributes.
It is tested in those contexts.
| ID: |
wml/semantics/unknown/1 |
| Class: |
A |
| Text: |
When a WML deck is encoded with an alternate DTD that includes elements
or attributes beyond those in the WML 1.3 specification, the user agent will
render the content of the unrecognized elements. [WML Specification section 12.4] |
|
Inter-card navigation is controlled by the GO, PREV, NOOP, REFRESH task.
Assertions for these are covered in section 9.5 Tasks.
Task execution failures are covered in the tasks themselves.
The WML reference information and the Compact binary representation of WML sections
are consise summarys of the previous sections. Hence the assertions for these sections
are in the relevant previous sections.
