W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2013

Memory element

From: chris nuernberger <cnuernber@gmail.com>
Date: Tue, 12 Feb 2013 08:24:53 -0700
Message-ID: <CAG=GWvfpyo2u3H0N3YXmwB-b7uLT8jGAdSOgd=oRa7SzRyLb-g@mail.gmail.com>
To: "VBWG Public (www-voice@w3.org)" <www-voice@w3.org>
A slightly different element that we could perhaps consider would be a
<memory> element.

It would have the same deep/shallow semantics of history but you would have
commands from the scripting system explicitly to store.  Aside from only
storing information if explicitly asked to, it would function just as a
history node.  It would probably be required to have a transition inside it.

On that note, I am somewhat surprised that history nodes are not required
to have a transition inside them for if they are targetted and have no

In any case I think there are use cases for <memory/> that may be
interesting/useful with more complex UI metaphors.


A foolish consistency is the hobgoblin of little minds - Emerson
Received on Tuesday, 12 February 2013 15:25:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:43 UTC