This may already be in the spec, but I couldn't find it.
I think the spec should explicity require UAs to provide a mehanism to
mute audio and to pause video, even if the controls attribute is not set.
This will be of great benefit to screenreader users, as well as to people
who work in shared
Bruce Lawson wrote:
This may already be in the spec, but I couldn't find it.
I think the spec should explicity require UAs to provide a mehanism to
mute audio and to pause video, even if the controls attribute is not set.
This would not make sense in some situations e.g. for a UA designed to
On Thu, May 7, 2009 at 5:15 PM, Bruce Lawson bru...@opera.com wrote:
I'm struggling to understand the reasons for hgroup: wouldn't one or
more h1..h6 elements wrapped in the same header imply just such a
grouping without the need for such an element?
No longer, as header is not a sectioning
On Thu, 07 May 2009 16:34:21 +0100, James Graham jgra...@opera.com wrote:
So, in the first example A new era of loveliness is a real section
heading and the navigation becomes a subsection of that section. In the
second example the hgroup element tells us that the h1 and h2
elements form a
Hi all,
I've been hashing through a bunch of the design issues around using
MessagePorts within Workers with IanH and the Chrome/WebKit teams and I
wanted to follow up with the list with my progress.
The problems we've encountered are all solveable, but I've been surprised at
the amount of work
The main problem with prefixes is that the meaning of prefixes is not
preserved when a code fragment is pasted elsewhere, so that prefixed names
can end up meaningless or having an entirely different meaning from what the
author had intended. A similar problem arises with DTD entities (indeed,
The rel=license example in
http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#li
nk-type-license
looks like:
body
h1Kissat/h1
nav a href=../Return to photo index/a /nav
img src=/pix/39627052_fd8dcd98b5.jpg
pOne of them has six toes!/p
...
/body
I would say that
On Thu, 7 May 2009, Drew Wilson wrote:
Having MessagePorts in worker context means that Workers can outlive
their parent window(s) - I can create a worker, pass off an entangled
MessagePort to another window (say, to a different domain), then close
the original window, and the worker
On May 7, 2009, at 2:47 PM, Ian Hickson wrote:
On Thu, 7 May 2009, Drew Wilson wrote:
Having MessagePorts in worker context means that Workers can outlive
their parent window(s) - I can create a worker, pass off an entangled
MessagePort to another window (say, to a different domain), then
It looks like WebKit binds the XMLHttpRequest object to its parent document
at instantiation time, so the source of the constructor doesn't make a
difference. And it looks like that binding is cleared when the document is
closed so invoking xhr.send() on an XHR object whose parent document is no
I agree with Drew's assessment that MessagePorts in combination with
Workers are extremely complicated to implement correctly, as currently
specified. In fact, the design seems to push towards having lockable
shared state, even though one potential advantage of the message
passing design
On Thu, May 7, 2009 at 3:34 PM, jgra...@opera.com wrote:
Quoting Smylers smyl...@stripey.com:
James Graham writes:
Bruce Lawson wrote:
I'm struggling to understand the reasons for hgroup: wouldn't one
or more h1..h6 elements wrapped in the same header imply just such
a grouping
H.264 was advocated here for the video element as higher quality
than competing codecs such as Theora could ever manage.
The Thusnelda coder is outdoing H.,264 in current tests:
http://web.mit.edu/xiphmont/Public/theora/demo7.html
This is of course developmental work. I'm sure the advocates of
On Thu, May 7, 2009 at 5:51 PM, David Gerard dger...@gmail.com wrote:
The Thusnelda coder is outdoing H.,264 in current tests:
Be careful how glowing you make this sound -- this is on a particular
objective test (not subjective, and thus perversely less accurate in
reflecting how good do
I don't know how far you have gotten with keygen.
You may be interested in knowing what the competition is doing :-)
From a provisioning point of view smart cards have a long way to go. From
the SKS paper:
even if you buy a $100 card; it still doesn't enable an on-line issuer
to
15 matches
Mail list logo
