On Jun 4, 2012, at 5:12 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 2 Nov 2011, Jer Noble wrote:
I'm currently working on implementing MediaController in WebKit
https://bugs.webkit.org/show_bug.cgi?id=71341, and have a couple
pieces of feedback from an implementor's POV:
*
On Tue, Jun 5, 2012 at 5:57 PM, Jer Noble jer.no...@apple.com wrote:
Actually, in WebKit, we explicitly also message the document from which
the element was removed in that case. I don't see why this behavior
couldn't be standardized.
Did you inform the spec editor(s) when you decided to
On Jun 4, 2012, at 11:23 PM, Robert O'Callahan rob...@ocallahan.org wrote:
If you implemented that proposal as-is then authors would usually need a
listener on the document as well as the element, and as Chris pointed out,
it's simpler to just always listen on the document.
Is that true
On 06/05/2012 09:31 AM, Jer Noble wrote:
On Jun 4, 2012, at 11:23 PM, Robert O'Callahan rob...@ocallahan.org wrote:
If you implemented that proposal as-is then authors would usually need a
listener on the document as well as the element, and as Chris pointed
out, it's simpler to just always
On Mon, Jun 4, 2012 at 11:13 PM, Jer Noble jer.no...@apple.com wrote:
Actually, in WebKit, we explicitly also message the document from which the
element was removed in that case. I don't see why this behavior couldn't be
standardized.
Why should we standardize this if we always notify the
On Tue, Jun 5, 2012 at 1:06 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Jun 4, 2012 at 11:13 PM, Jer Noble jer.no...@apple.com wrote:
Actually, in WebKit, we explicitly also message the document from which the
element was removed in that case. I don't see why this behavior couldn't
On Jun 5, 2012, at 1:06 AM, Anne van Kesteren ann...@annevk.nl wrote:
Why should we standardize this if we always notify the document? Is
there a benefit to notifying both the element and the document?
I think Vincent put forward a reasonable argument. The document is a finite,
shared
On Mon, 14 Nov 2011, crocket wrote:
I know that it's possible to manipulate the volume attribute with
javascript.
Many internet forums allow HTML tags but prohibit javascripts, however.
If I was able to set the initial volume with volume attribute of those
tags, I would be able to set the
Oops, I found more e-mails on the thread to which I just asked for a use
case, which gave a use case:
On Wed, 16 Nov 2011, crocket wrote:
video and audio tags need volume attribute.
I know that it's possible to manipulate the volume attribute with
javascript. But many internet forums
On Thu, 12 Jan 2012, Francis Boumphrey wrote:
A few comments about the video element from the point of view of an
HTML author. Currently it is not particularly useful, and there is
nothing to encourage me to use it rather than embed
Firstly if I use a video with the src attribute
e.g.
On Fri, 13 Jan 2012, Kit Grose wrote:
On 13/01/2012, at 4:46 AM, Francis Boumphrey wrote:
Firstly if I use a video with the src attribute
e.g. video src='myvideo.mp4' controls
and my user agent does not support the format, all I get (in my
versions of Opera and Firefox) is a
On Tue, 21 Feb 2012, Rodger Combs wrote:
I propose that source add a quality, bitrate, or filesize attribute to
allow the UA to decide between multiple streams by choosing the maximum
quality file that it can download within a reasonable amount of time
(e.g. it will download faster than it
On Mon, 4 Jun 2012, Jer Noble wrote:
This too looks good. We already store the results when we report the
controller state, so at a first glance, exposing this property will be
trivial.
Make sure you're setting the attribute at the right time. There's some
careful jumping through hoops
On Jun 5, 2012, at 3:02 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 4 Jun 2012, Jer Noble wrote:
This too looks good. We already store the results when we report the
controller state, so at a first glance, exposing this property will be
trivial.
Make sure you're setting the
On Sat, 21 Jan 2012, Jukka K. Korpela wrote:
2012-01-21 0:30, Ian Hickson wrote:
On Tue, 26 Jul 2011, Jukka K. Korpela wrote:
I don’t think you have clarified whether var is suitable for
physical quantities, but I guess you meant to imply it—even though
there is not a single
On Sat, 21 Jan 2012, Leif Halvard Silli wrote:
Ian Hickson on Fri Jan 20 14:31:01 PST 2012:
On Tue, 26 Jul 2011, Christoph Päper wrote:
Anne van Kesteren:
I'm still trying to get HTML and browsers to change so that attribute
values always match case-sensitively, irrespective of markup
2012-06-06 2:53, Ian Hickson wrote:
I have rather been optimistic about future developments for markup
elements that have been defined exactly enough to warrant meaningful
semantics-based processing. For example, most of the uses mentioned in
current text imply that var element contents should
17 matches
Mail list logo
