- From: Markku Savela <msa@msa.tte.vtt.fi>
- Date: Mon, 4 Feb 2002 16:28:18 +0200
- To: www-voice@w3.org
In description of "5.2.2 Catch", the count attribute The occurrence of the event (default is 1). The count allows you to handle different occurrences of the same event differently. Each <form>, <menu> and form item maintains a counter for each event that occurs while it is being visited; these counters are reset each time the <menu> or form item's <form> is re-entered. The form-level counters are used in the selection of an event handler for events thrown in a form-level <filled>. Counters are incremented against the full event name and every prefix matching event name; for example, occurrence of the event "event.foo.1" increments the counters associated with handlers for "event.foo.1" plus "event.foo" and "event". For example <catch event="nomatch noinput" count="3"> ... </catch> A sensible interpretation would be that this catch fires after any combination of "nomatch" or "noinput" (eg. "nomatch,noinput,nomatch"). However, the 5.2.2 description seems to lead to case where "nomatch" and "noinput" counters are done independently and the example catch would fire only after there has been at least 3 "noinput" or 3 "nomatch" (a sequence of "nomatch, noinput, nomatch, noinput" would not fire the catch? To me it looks like the counters should be kept per active catch element, and counter incremented once when event specification of the catch matches? (regardless whether the catch fires or not).
Received on Monday, 4 February 2002 09:26:20 UTC