At the Gadgets TF phone call today, there was a request to restore
onchangePattern, with the following restrictions:
* It is only for use within dynamic mashup scenarios. IDEs would not be
required to instrument the HTML document to support runtime property
changes.
* Only the property name pattern would be supported
* Default would be onchangePattern="on{{propertyUCFirst}} Change"
This is all implemented in the reference implementation and turned out to
be straightforward.
Anyone object to this approach? Let's talk about this at the next phone
call. In the meantime, I will restore onchangePattern but include
red-colored comments to highlight the fact that the IDE WG hasn't reviewed
it yet.
Jon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://openajax.org/pipermail/ide/attachments/20080821/1d221abf/attachment.html