While we're on the topic of commonizing things at Element - can we introduce
an 'inner' property on Element? This would map to innerHTML for
HTMLElements. Other languages could introduce parsing rules for
getting/setting that property. Presumably XML grammars would use the rules
at http://dev.w3
Neil, I would say "exporting" is half of "round-tripping"...so I think
that's covered.
Ian,
Here's another use case:
5. The ability to animate elements in a web page (hypertext, vector
graphics) without using script.
* sizes, positions, opacities, colors, transforms (basically most
attributes
n an error or
throw an exception?). Then, add a load() method to the interface
(which would produce a load event just as the construction with an
argument would). This also allows me to reuse the Audio object
instead of creating an Audio object for each different sound...
Thanks,
Jeff
On 9/2
Opera 9 implements the Audio interface proposed in HTML5:
http://whatwg.org/specs/web-apps/current-work/#scs-sound
I'm having trouble with it. My first attempt was:
var soundClip = new Audio("blah.wav");
if(soundClip) { soundClip.play(); }
This doesn't work on the first attempt, but on the seco
at least make them valid XML elements :P
Regards,
Jeff
On 4/24/06, Vladimir Vukicevic <[EMAIL PROTECTED]> wrote:
> On 4/21/06, Jeff Schiller <[EMAIL PROTECTED]> wrote:
> > 2) Can you clarify the mechanism to determine if a user agent supports
> > a particular content typ
I have some questions/suggestions to the Web Apps 1.0 Audio Interface
(http://whatwg.org/specs/web-apps/current-work/#scs-sound) before it
takes off in too many browsers:
1) "The Audio() constructor takes a single argument, a URI (or IRI),
... which returns an Audio object that will, at the comple
