Chris wrote:
If more then titles means other uses of the CITE tag, as evidenced
in [1],
they do not form any pattern. They look more like random errors.
I've used the CITE element fairly extensively on my blog, *mostly* for
titles (books, films) but also for people. If it's a proper noun,
Ian Hickson schrieb:
On Thu, 4 Jun 2009, Andrew W. Hagen wrote:
Encouraging use of small print for legalese also encourages this:
h1
a href=continue.html
Welcome to the BigCo web site. Click to continue.
/a
/h1
smallBy clicking above, you agree that BigCo can charge your
credit card $10 per
I'm a bit confused by the conditions set out at the bottom of the rel
extensions wiki page:
http://wiki.whatwg.org/wiki/RelExtensions
For the Status section to be changed to Accepted, the proposed
keyword must either have been through the Microformats process, and
been approved by the
On Wed, 01 Jul 2009 19:01:02 +0200, Philip Jägenstedt phil...@opera.com
wrote:
On Wed, 01 Jul 2009 18:29:17 +0200, Peter Kasting pkast...@google.com
wrote:
On Wed, Jul 1, 2009 at 2:41 AM, Anne van Kesteren ann...@opera.com
wrote:
On Tue, 30 Jun 2009 21:39:05 +0200, Peter Kasting
The text from the current spec is, Small print is typically
legalese describing disclaimers, caveats, legal
restrictions, or copyrights. Small print is also sometimes
used for attribution.
By suggesting it is typical, that implicitly encourages people
to use small print for legal text.
One of
I have addressed all Andrew's points previously. Please forgive my posting
an outline of the arguments here.
1. The specification does not encourage using the SMALL element for legal
notices. It merely allows the SMALL element to contain legal notices.
2. Legal texts are unreadable on their
On Thu, 2 Jul 2009, Kristof Zelechovski wrote:
I have addressed all Andrew's points previously. Please forgive my
posting an outline of the arguments here.
Just as a reminder (and this is especially relevant for the video codecs
discussion!), there is no need to repeat previously stated
Hi all,
copy-pasting an IRC conversation about session history.
Seems like HTML5 isn't compatible with any implementation.
[22:58] smaug Hixie: ping
[22:58] Hixie hey
[22:59] smaug Hixie: about HTML5's session history
[22:59] Hixie yes
[22:59] smaug I'm trying to understand the Each
whatwg-requ...@lists.whatwg.org wrote:
Message: 3
Date: Tue, 30 Jun 2009 04:50:31 + (UTC)
From: Ian Hickson i...@hixie.ch
Subject: [whatwg] Codecs for audio and video
To: WHATWG wha...@whatwg.org
Message-ID: pine.lnx.4.62.0906292331380.1...@hixie.dreamhostps.com
After an inordinate amount
Hi, I just realized that in HTML4.01 spec, DTD doesn't seem to allow
nested OL or UL without LI. See
http://www.w3.org/TR/REC-html40/struct/lists.html#h-10.2 In fact, the
nested list example is marked deprecated. But in practice, all major
user agents produce nested list when
I understand that people are disappointed that we can't require Theora
support. I am disappointed in the lack of progress on this issue also.
On Tue, 30 Jun 2009, Silvia Pfeiffer wrote:
On Tue, Jun 30, 2009 at 2:50 PM, Ian Hicksoni...@hixie.ch wrote:
I considered requiring Ogg Theora
On Fri, Jul 3, 2009 at 9:26 AM, Ian Hicksoni...@hixie.ch wrote:
Going forward, I see several (not mutually exclusive) possibilities, all
of which will take several years:
1. Ogg Theora encoders continue to improve. Off-the-shelf hardware Ogg
Theora decoder chips become available.
On Fri, 3 Jul 2009, Silvia Pfeiffer wrote:
Actually HTML5 is largely built on the idea of speccing the de-facto
standards, either long after they were implemented, or in tandem with
them being implemented. Very little of HTML5 has been ahead of
implementations.
What about Internet
On Fri, Jul 3, 2009 at 10:19 AM, Ian Hicksoni...@hixie.ch wrote:
On Fri, 3 Jul 2009, Silvia Pfeiffer wrote:
That I can understand. But in this case, you should leave the paragraph
in the spec that states the need for a baseline codec, since the
situation hasn't changed and we are still
On Fri, 3 Jul 2009, Silvia Pfeiffer wrote:
That action I can understand. But then I would say we should have a
collection of things that we need to work on for a second version of
HTML5, which obviously includes the baseline codec question and also
audio/video a11y, and probably many more
On Fri, Jul 3, 2009 at 10:36 AM, Ian Hicksoni...@hixie.ch wrote:
On Fri, 3 Jul 2009, Silvia Pfeiffer wrote:
That action I can understand. But then I would say we should have a
collection of things that we need to work on for a second version of
HTML5, which obviously includes the baseline
I'd like to see some progress on these two tags.
I'd like people to consider that Vorbis can be implemented
in virtual machines (Java, Flash) which support raw PCM data.
Theora is no different.
I'd like to see canvas support added to the video tag (it's as
natural as img).
and enable the
Do you have an idea on how to introduce fall back support for browsers that
don't even support canvas, how will they be expected to implement a base64
string when they skip the element's attributes?
Might a img tag work with the src= set to the same string as the base64?
Or would that contradict
Hi
I am concerned by the wording of this section.
There are different systems of week number -- as far as I can work out,
this is the same as ISO 8601 week numbering.
But it nowhere explicitly says that.
I think, the spec should have a normative reference to ISO 8601 for the
definition of week
19 matches
Mail list logo
