W3C home > Mailing lists > Public > public-webtiming@w3.org > February 2016

[timingobject] Need another event type for the Timing Object?

From: Ingar Arntzen via GitHub <sysbot+gh@w3.org>
Date: Mon, 29 Feb 2016 12:33:55 +0000
To: public-webtiming@w3.org
Message-ID: <issues.opened-137241831-1456749235-sysbot+gh@w3.org>
ingararntzen has just created a new issue for 

== Need another event type for the Timing Object? ==
The timing object spec defines the following [event 

- change
- readystatechange
- timeupdate
- error

There are still other state changes that may not be reflected by these
 event types.

For example, if access restrictions (see issue #21) are changed from 
"rw" to "ro", e.g. due to credentials timing out, the application 
might need to know about this. Or, if a timing converter (see issue 
#13) is modified so that it has a new parent (.timingsrc), it will 
need to reflect the properties of its new parent (e.g. range or 
access) instead of the properties of its previous parent.

Maybe there should be an extra event expressing state changes other 
than vector changes? I still think the change event is special and I 
don't think it would be a good idea to abuse this for the 
communication of other types of state changes.

Please view or discuss this issue at 
https://github.com/webtiming/timingobject/issues/24 using your GitHub 
Received on Monday, 29 February 2016 12:33:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:25:15 UTC