On Aug 14, 2008, at 11:14, timeless wrote:
We'd probably be forced to lie and claim every codec imaginable.
[including ogg (or rather vorbis, theora, speex, ...), as these are
all imaginable]
On Thu, Aug 14, 2008 at 12:41 PM, Henri Sivonen [EMAIL PROTECTED] wrote:
Would the situation be any
On Fri, Aug 15, 2008 at 12:45 AM, Greg Houston
[EMAIL PROTECTED] wrote:
I would like to propose a disabled attribute for iframes.
things like this inevitably are used for copy protection.
and they aren't going to work quite the way you expect on mobile devices
(we're probably going to have a
On Wed, 14 Mar 2007, Lachlan Hunt wrote:
The spec currently defines most embedding elements (img, iframe,
embed, object, video and canvas) as strictly inline level and thus only
allows them to be used in contexts where strictly inline level content
may be used.
I think these elements
On Aug 20, 2008, at 12:39, timeless wrote:
On Thu, Aug 14, 2008 at 12:41 PM, Henri Sivonen [EMAIL PROTECTED]
wrote:
Would the situation be any different for the source element
fallback?
yes. people wouldn't try to ask us questions we can't answer. instead
they'd be giving gecko lots of
On Aug 20, 2008, at 12:49, Ian Hickson wrote:
On Sun, 8 Apr 2007, Henri Sivonen wrote:
It might make sense to allow figure as struct inline. The
interaction
with p parsing in text/html would require research.
On Sun, 8 Apr 2007, Henri Sivonen wrote:
Anne says figure should work as a
On Wed, Aug 20, 2008 at 12:06 AM, Ian Hickson [EMAIL PROTECTED] wrote:
When you control the software used to read the data, it doesn't matter
what the data format is.
i kinda object to this. By this argument, video isn't necessary
because youtube controlled the software (flash) used to read
On Wed, 20 Aug 2008, Henri Sivonen wrote:
On Aug 20, 2008, at 12:49, Ian Hickson wrote:
On Sun, 8 Apr 2007, Henri Sivonen wrote:
It might make sense to allow figure as struct inline. The
interaction with p parsing in text/html would require research.
I'm not convinced that this
Only the user that actually encounters a Web site deficiency should report
it to the creator/owner (assuming they provided a reverse link). Otherwise
such a report should be ignored as a supposition.
Why should browser vendors bother that some pages do not display correctly
in other browsers?
I am very disappointed. onhashchange intuitively means that the content
hash changes (which is more or less equivalent to modifying the content, of
course). I would call this event onreveal to be in line with the primary
bookmark semantics. The name is inspired by the Finder AppleScript
A load error occurs when the document cannot be loaded.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Garrett Smith
Sent: Wednesday, August 20, 2008 4:08 AM
To: Ian Hickson
Cc: [EMAIL PROTECTED]
Subject: Re: [whatwg] window.onerror -ancient
Publishers who publish commercial content on physical media are rarely
interested in having their content repackaged by someone else as they see
fit. This is not very pleasant of course; however, you could possibly try
to solve your problem by asking the vendor for a license to repackage their
I admit XSLT is heavy and it causes a significant rendering slowdown in the
browser. This is not a problem because the XSLT processor runs on the
publisher's machine once each time new content gets published - authoring
that content would probably take much more time than publishing it anyway.
I
2008/8/20 Křištof Želechovski :
I am very disappointed. onhashchange intuitively means that the content
hash changes (which is more or less equivalent to modifying the content, of
course).
onlocationhashchange?
...because it's fired when location.hash changes...
(I have personally no problem
On Wed, Aug 20, 2008 at 1:52 PM, Kristof Zelechovski
[EMAIL PROTECTED] wrote:
Only the user that actually encounters a Web site deficiency should report
it to the creator/owner (assuming they provided a reverse link).
Otherwise such a report should be ignored as a supposition.
mass complaints
No, no, and no.
Author's POV:
Mass complaints about _supposedly_ incompatible Web content from incompetent
end users would only cause me, as the author, to file a complaint with the
browser vendor. The browser should not pretend it is omniscient and it can
teach everyone around.
Vendor's POV:
I am not sure what Ian means. M.S.'s description at
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-March/010043.html
he seems to be opposing is definitive, exhaustive and that is what Internet
Explorer 7 does. Scripts attached to elements included in supported objects
do not run. An
Ian Hickson wrote:
On Tue, 19 Aug 2008, Elliotte Harold wrote:
In the case of non-Web content, the use of HTML is an academic point,
since any format would work as well.
Really? Why? and how? That's certainly not self-evident.
When you control the software used to read the data, it doesn't
On Tue, Aug 19, 2008 at 6:13 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Wed, 15 Aug 2007, Leons Petrazickis wrote:
On 8/15/07, Michael A. Puls II [EMAIL PROTECTED] wrote:
On 8/14/07, Ian Hickson [EMAIL PROTECTED] wrote:
On Sat, 11 Aug 2007, Michael A. Puls II wrote:
We ended up using
On Thu, Aug 14, 2008 at 1:18 AM, timeless [EMAIL PROTECTED] wrote:
On Tue, Aug 12, 2008 at 12:53 AM, Kristof Zelechovski
[EMAIL PROTECTED] wrote:
I have considered inline response. I have two options: do it by hand (I am
rather busy) and do it for every reply (which makes business people
On Wed, Aug 20, 2008 at 9:53 PM, Henri Sivonen [EMAIL PROTECTED] wrote:
Do you mean trying to download each video, giving it to GStreaming and
seeing if an error code comes back?
That might be what we have to do, yes.
But at least that can be done asynchronously. You couldn't implement a
Hola,
I see that the Creative Commons has proposed additions to HTML
to support licenses (ccREL):
http://www.w3.org/Submission/2008/SUBM-ccREL-20080501/
As an example, they offer:
div about=http://lessig.org/blog/;
xmlns:cc=http://creativecommons.org/ns#;
This page, by
a
On Wed, 20 Aug 2008, Křištof Želechovski wrote:
I am not sure what Ian means. M.S.'s description at
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-March/010043.html
he seems to be opposing is definitive, exhaustive and that is what
Internet Explorer 7 does. Scripts attached to
On Wed, 20 Aug 2008, Tab Atkins Jr. wrote:
Unless I missed something in the HTML5 spec, at the least this would
add the property attribute to a. Wouldn't ccREL be expressed
better using link instead of a?
The whole thing would be best expressed as a microformat, as the entire
thing
Le 21 août 2008 à 07:22, Bonner, Matt a écrit :
I see that the Creative Commons has proposed additions to HTML
to support licenses (ccREL):
http://www.w3.org/Submission/2008/SUBM-ccREL-20080501/
And as a practical implementation of it. Click at the logo at the
bottom, and it returns the
I've received feedback from a number of people requesting a rethink to the
API for creating and communicating with workers.
Here is a skeleton of a new proposal. It makes the following changes:
* Shared workers and dedicated workers get their own interfaces,
inheriting from a common base
Ian Hickson wrote:
On Wed, 20 Aug 2008, Tab Atkins Jr. wrote:
Unless I missed something in the HTML5 spec, at the least this would
add the property attribute to a. Wouldn't ccREL be expressed
better using link instead of a?
The whole thing would be best expressed as a microformat, as the
On Wed, Aug 20, 2008 at 5:36 PM, Ian Hickson [EMAIL PROTECTED] wrote:
I've received feedback from a number of people requesting a rethink to the
API for creating and communicating with workers.
Here is a skeleton of a new proposal. It makes the following changes:
* Shared workers and
This is looking great. A few comments though (of course :) )
Do we really need the SharedWorker interface. I.e. couldn't we just
return a MessagePort? This would probably require that we use a factory
function rather than a constructor, like getPortForSharedWorker or
some such. In other
28 matches
Mail list logo
