Hi Brian,
I quite don't see the point of yet another media element; we've got
enaugh of 'em already. IMO we should recommend only object. Weither
it's 1D (eg a song), 2D (eg an image) or 3D (eg a model), visual or
audio and interactive or not is defined by the type attribute. The UA
simply uses
Bjartur,
Great contribution, greatly appreciated. I am in partial agreement with
you, and an XHTML2 approach was certainly something I pondered. A new tag,
however, makes more sense in the HTML5 way of doing things, in which native
media types are getting their own semantic tags:
audio/
On Oct 30, 2009, at 6:09 PM, Brian Blakely wrote:
To ensure HTML remains semantic as the web makes its gradual
transition to 3D rich interfaces and content, I am submitting a
proposal for WHATWG's consideration. The below examples contain
HTML as it exists now, the current working
Perfectly aware Simon, hence the proposition; a 3D model element is not an
attempt to erase, but complement current efforts.
Let me take this opportunity to clarify. model/ is neither redundant nor
trampling current efforts, but filling an essential gap in the spec.
This is why:
1) O3D and
In section 6.10.2:
The pushState(data, title, url) method adds a state object to the
history. perhaps should be ... adds a state object *entry* to the
history.
The replaceState(data, title, url) method updates the current entry
in the history to have a state object. perhaps should be
The
