Charles Iliya Krempeaux wrote:
... could become...
For color, you are reinventing Media Queries. For compression, you are
basically reinventing q values for MIME types.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
lename*, a computer program, or any other
string that a computer would recognise.
http://www.whatwg.org/specs/web-apps/current-work/#the-code
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Hi,
The spec currently lists the entity ¬ twice in the table of
entities, as shown in this extract:
...
nopf; U+1D55F
not; U+000AC
notU+000AC
notin; U+02209
...
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Ernest Cline wrote:
-Original Message-
From: Lachlan Hunt <[EMAIL PROTECTED]>
Ernest Cline wrote:
From a practical viewpoint, being able to specify dates before
January 1, 1 BC (Gregorian) would allow for historical dates not
currently available to be specified in markup of doc
implemented. Thus we can safely leave it to to future generations to solve.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
r end tag token is created".
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Ian Hickson wrote:
On Fri, 14 Oct 2005, Lachlan Hunt wrote:
Just a few issues regarding the use of abbr and dfn elements.
*The abbr Element's title Attribute*
I think the title attribute should also be allowed to be omitted from
the abbr element if there is another abbr element with a
ement a feature like this.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
has always done, but if ""
is encountered it turns the preceding "" (but not ") on the
same nesting level from an empty into a start tag.
That's not possible. already has magic processing, at least in
quirks mode. It's treated the same as .
--
Lachlan H
e
default value: 1. It would then count down from there:
1. A
0. B
-1. C
-2. D
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
g.org/specs/web-apps/current-work/#pick-a
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Hi,
There are some examples of the element that use
type="video/ogg", which is not the correct MIME type. Those should be
changed to application/ogg.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Hi,
As discussed in IRC today, the spec should include an example of
marking up pullquotes using aside and blockquote.
blah blah blah...
pullquote...
blah blah blah...
--
Lachlan Hunt
http://lachy.id.au/
CAPTCHA images, you should probably also reference the W3C note about
them [2].
[1] http://html.cita.uiuc.edu/text/
[2] http://www.w3.org/TR/turingtest/
--
Lachlan Hunt
http://lachy.id.au/
Ian Hickson wrote:
On Sat, 4 Nov 2006, Lachlan Hunt wrote:
And, as I mentioned in IRC, I think it should be defined that the value
should resolve to a valid URI for an image, so that
isn't conforming, except in this rare case:
Ok but... what's an image? Do we exclude PD
erver
where the author can't (or doesn't know how to) configure the
Content-Type header properly. It depends entirely on the use case and
environment for which the serialiser is designed and configured.
--
Lachlan Hunt
http://lachy.id.au/
rrent-work/#serialising
--
Lachlan Hunt
http://lachy.id.au/
hey're not
generated automatically - and escape markup examples properly, such as
<ruby> instead of . Using the preview feature is often
helpful to avoid mistakes like that.)
--
Lachlan Hunt
http://lachy.id.au/
nk that such
links are completely redundant anyway.
--
Lachlan Hunt
http://lachy.id.au/
Martin Atkins wrote:
Lachlan Hunt wrote:
http://www.haymespaint.com.au/haymes/colourcentre/
http://www.ficml.org/jemimap/style/color/wheel.html
http://wellstyled.com/tools/colorscheme2/
These are some rather contrived examples.
How can you possibly call them contrived, when they are real
ly do so would help, and a description of how this would
solve the problem better.
Flickr, for example, allows users to drag photos onto a map to indicate
where they were taken, and assigns GPS coordinates to them. How would
that new type improve Flickr? Would you expect them to use this new
y use the first item.
--
Lachlan Hunt
http://lachy.id.au/
checkout~/2006/webapi/Binding4DOM/Overview.html?content-type=text/html;%20charset=utf-8#Overloads
--
Lachlan Hunt
http://lachy.id.au/
Ian Hickson wrote:
On Sat, 24 Feb 2007, Keryx Web wrote:
- A table within a table cell (Has this ever been used for anything but
layout?)
There are valid uses of that, though they are rare.
Really? What are they?
--
Lachlan Hunt
http://lachy.id.au/
ionality to the local cache feature
in Google Gears. It would probably be worth investigating it and
standardising something like it in HTML5.
--
Lachlan Hunt
http://lachy.id.au/
Ian Hickson wrote:
On Sun, 12 Mar 2006, Lachlan Hunt wrote:
Characters in the range from #x01 to #x19 (except for whitespace
characters) are not treated interoperably across platforms...
The use of characters in either of these ranges should be an easy parse
error.
I've made the firs
what errors and
warnings do.
2. A new attribute on to associate it with a related error message.
e.g. Foo
You filled in an incorrect value
The element is more generic and could probably solve other
similar use cases, whereas the the label attribute would only
specifically solve the form error use case.
--
Lachlan Hunt
http://lachy.id.au/
ce checkers wouldn't be required to emit a warning, but they
are free to do if they wish.
--
Lachlan Hunt
http://lachy.id.au/
Smylers wrote:
Lachlan Hunt writes:
You're assuming there is actually a valid use case for the popup in
the first place.
But as you've already pointed out, browsers can offer users who never
want to have links automatically open anywhere than the current window,
so webpages&
ch uses usually indicate broken back end implementations and/or
the complete failure to think about usability.
On Apr 27, 2007, at 8:49 PM, Ian Hickson wrote:
On Thu, 26 Apr 2007, Lachlan Hunt wrote:
Why is _blank still considered a conforming value? On IRC, Hixie
mentioned that there are
That's a use case for _top or _parent, not _blank.
--
Lachlan Hunt
http://lachy.id.au/
d Safari didn't appear to treat it as
such, so maybe it's not needed.
http://www.whatwg.org/specs/web-apps/current-work/#valid8
--
Lachlan Hunt
http://lachy.id.au/
compat with IE.
--
Lachlan Hunt
http://lachy.id.au/
ich is equally unsupported
all browsers?
--
Lachlan Hunt
http://lachy.id.au/
post your message to both public-html
and whatwg, just pick one or the other.
--
Lachlan Hunt
http://lachy.id.au/
vide full screen
capabilities, including at least Firefox (Win) and Opera (Win and Mac).
And last time I used a mobile device, it took the entire screen real
estate by default.
--
Lachlan Hunt
http://lachy.id.au/
as able to enter full screen by double clicking the
video or selecting from the context menu.
--
Lachlan Hunt
http://lachy.id.au/
Daniel Glazman wrote:
On 21/03/2007 04:10, Lachlan Hunt wrote:
... But we can't change the XHTML namespace without breaking backwards
compatibility, so we're stuck with it.
Again, never said the contrary. Being stuck with the xhtml namespace for
html 5 does not mean you cann
n't change the XHTML namespace without
breaking backwards compatibility, so we're stuck with it.
[1] http://www.w3.org/ns/xbl
--
Lachlan Hunt
http://lachy.id.au/
ropping it. It's an unnecessary API for browsers to
support. It adds nothing that can't be done with play()/pause() and an
if statement.
if (video.state == HTMLVideoElement.PAUSED) {
video.play();
} else {
video.pause();
}
--
Lachlan Hunt
http://lachy.id.au/
fects, not streaming audio. Perhaps that is a use case for a
more fully featured element that does that, while keeping
Audio() for simple sound effects.
--
Lachlan Hunt
http://lachy.id.au/
nly inline.
--
Lachlan Hunt
http://lachy.id.au/
e, it doesn't make sense to add an extra or
around the object just to get around the contextual usage restriction.
HTML4 currently allows object and iframe to be used where block level
elements are allowed, and I don't think HTML5 should restrict that.
--
Lachlan Hunt
http://lachy.id.au/
4, application/mp4,
video/quicktime, */*;q=0.1
--
Lachlan Hunt
http://lachy.id.au/
seconds and fire the event with the same content may
be excessive.
This could possibly be done using the :command syntax.
e.g.
Event: click
:retry 6
The browser would then retry the connection in 60,000 milliseconds (1
minute).
--
Lachlan Hunt
http://lachy.id.au/
eciding if it should be allowed
or not
[16:28] Technically, it is an error and I think users should be
notified, but it's practically harmless these days and very common.
[16:30] Yet, doing the same thing in XML doesn't work, since XML
parsers do treat them as control characters
ittle and not simply copying what typical
word processing software has done in the past.
--
Lachlan Hunt
http://lachy.id.au/
human readable
name; although, perhaps we would need the cite attribute as well to link
to a page about the reviewer.
--
Lachlan Hunt
http://lachy.id.au/
that major browser vendors will not be implementing XHTML
2.0, particularly if it reuses the XHTML 1.x namespace and retains all
of its backwards-incompatible changes, and features that are difficult
or impossible to implement.
--
Lachlan Hunt
http://lachy.id.au/
David Latapie wrote:
On Sat, 10 Feb 2007 08:36:25 +1100, Lachlan Hunt wrote:
marks a point of interest for future reference, it does not
denote importance. Everyone seems to be focussing on the definition
of highlight meaning emphasis as their argument that it is the same
as and/or
lining, or whatever, is simply the
mechanism used to identify the item, not the semantic purpose of the
element itself.
[1] http://www.answers.com/mark#Technology
--
Lachlan Hunt
http://lachy.id.au/
ey do highlight.
Highlighting with a yellow highlighter, underlinging, circling or
drawing arrow are all different forms of marking, and could all be
marked up using the element. It is not restricted to just
highlighting, though it may be the default presentation.
--
Lachlan Hunt
http://lachy.id.au/
/current-work/#the-em
Strong provides a strong emphasis, no?
Strong denotes importance (see the spec). This is a change from HTML4,
but HTML4 didn't really define the difference between emphasis and
strong emphasis anyway.
--
Lachlan Hunt
http://lachy.id.au/
Leons, you forgot to CC the list.
Leons Petrazickis wrote:
Lachlan Hunt wrote:
is for highlighting text that is of some interest to the reader, but
it does not alter the meaning of the text itself.
Would you say that is semantic and is presentational, with
the difference from is in
does change the meaning of the text.
is for highlighting text that is of some interest to the reader, but
it does not alter the meaning of the text itself.
--
Lachlan Hunt
http://lachy.id.au/
e case over
to www-style.
[1] http://www.w3.org/TR/css3-values/#keywords
--
Lachlan Hunt
http://lachy.id.au/
Alexey Feldgendler wrote:
The HTML5 spec could somehow officially bless CDATA only when used like
this:
//
It would not harm because it is already interoperable.
It's technically already allowed because script and style elements are
defined to contain CDATA. So basically
l to the web, not to mention
themselves, and not beneficial in any way.
--
Lachlan Hunt
http://lachy.id.au/
Mike Schinkel wrote:
Lachlan Hunt wrote:
It's not up to a specification to specify a conformance requirement
stating which implementations can be used, nor mandating particular
implementation details.
By providing the suggest test I was trying to get people to use a
conforming componen
ing as volatile as a wiki page.
Actually, it's already doing that in another section.
http://www.whatwg.org/specs/web-apps/current-work/#other
--
Lachlan Hunt
http://lachy.id.au/
#objectid:onmousedown
#objectid:onmouseover
#objectid:onmouseout
#objectid:onkeypress
Why? Are you going to try and attach event listeners using CSS? I
think XBL might be what you're looking for. It can do that and more.
http://www.w3.org/TR/xbl/
--
Lachlan Hunt
http://lachy.id.au/
s paragraph contains a pre element
This is some preformatted
text inside a paragraph.
in XHTML only.
That cannot occur in the HTML serialisation because must imply
due to backwards compatibility constraints.
--
Lachlan Hunt
http://lachy.id.au/
an
wreaking havoc on the world, yet it doesn't seem to have particularly
bothered anyone trying to use it, or even promoting it.
You just need to realise that, if you wish to have your documents
reserialised as HTML or even wrongly serve XHTML as text/html, you need
to take care to avoid features which will result in a lossy conversion,
or put up with the minor discrepancies.
--
Lachlan Hunt
http://lachy.id.au/
x27;re done. That took me a whole 3 seconds to do. Does it really
seem like making that final step unnecessary, at the expense of
introducing useless junk into HTML?
--
Lachlan Hunt
http://lachy.id.au/
t benefit is so huge it can't even be easily calculated.
What benefits are there and what makes them so huge?
Lachlan Hunt wrote:
http://www.w3.org/mid/[EMAIL PROTECTED]
In that email you wrote:
"My point is that the whole idea of embedding
XML in HTML is nonsense and sho
Mike Schinkel wrote:
Lachlan Hunt wrote:
(IE's disastrous XML Data Islands and Custom Tags
provide sufficient evidence of that.)
Why are XML Data Islands disasterous?
http://www.w3.org/mid/[EMAIL PROTECTED]
--
Lachlan Hunt
http://lachy.id.au/
Ian Hickson wrote:
On Mon, 4 Dec 2006, Lachlan Hunt wrote:
The spec should mention the additional restriction that table elements
cannot contain child tr elements, because they imply the tbody element
in such cases.
http://www.whatwg.org/specs/web-apps/current-work/#restrictions
On Sun
Hi,
The spec should mention the additional restriction that table
elements cannot contain child tr elements, because they imply the tbody
element in such cases.
http://www.whatwg.org/specs/web-apps/current-work/#restrictions
--
Lachlan Hunt
http://lachy.id.au/
recommend putting it
under the MIT licence as well.
--
Lachlan Hunt
http://lachy.id.au/
Mike Schinkel wrote:
Lachlan Hunt wrote:
Use XHTML, send it with an HTML MIME type, and be happy.
No!
Why not? What's wrong with doing that?
Why do I need to keep repeating myself?
Lachlan Hunt wrote:
In many more cases, an HTML document or even an
XHTML 1.0 as text/html docume
output HTML may
choose to migrate to XHTML5.
--
Lachlan Hunt
http://lachy.id.au/
Lachlan Hunt wrote:
Work is being done on such tools now. A few of us have begun writing a
parser in Python, which will be either public domain (preferably) or
under a free software licence.
We've just set up a project for it in Google Code, and decided to put it
under the MIT li
Elliotte Harold wrote:
Lachlan Hunt wrote:
Because the fact is that when authors try to use XHTML as text/html,
they inevitibly fail to do so properly. It takes considerable
knowledge and skill to be aware of and handle all issues ranging from
parsing, character encodings to scripts and
an XML parser to handle HTML rapidly
hit a wall since most HTML documents were not even close to actually
conformant to the XML spec.
--
Lachlan Hunt
http://lachy.id.au/
Elliotte Harold wrote:
Lachlan Hunt wrote:
HTML and XML have significantly different parsing requirements and
they absolutely must be treated as significantly different file
formats. Any attempt to treat them as the same format is an extremely
bad idea.
That's only true to the extent
IE7 and earlier.
Consequently I and many others choose option 3:
Use XHTML, send it with an HTML MIME type, and be happy.
No!
--
Lachlan Hunt
http://lachy.id.au/
be parsed with XML tools.
The XHTML serialisation exists to make use of XML-only features, like
xmlns syntax. People wishing to use such features *must* use XML.
There has been no reason whatsoever given for wanting to try and use
unsupported XML-only syntax in HTML, most likely because there is no
valid
in. Henri Sivonen has written one in Java for
the HTML5 conformance checker, which is available under a free software
licence. If anyone wishes to contribute or write one in another
language, please do so.
--
Lachlan Hunt
http://lachy.id.au/
Lachlan Hunt wrote:
XML parsing for HTML on the web is totally impractical and I really do
understand the desire to do so.
I meant "I really [not] understand...".
--
Lachlan Hunt
http://lachy.id.au/
ver been a reliable indication of XHTML. There are many
authors that just use that XML syntax regardless of the DOCTYPE,
namespace declaration or MIME type. Many authors just don't have a clue
that it's XML syntax and that it is absolutely meaningless in HTML.
--
Lachlan Hunt
http://lachy.id.au/
clear (HTML: lang; XHTML:
xml:lang), it seems to me that the user agent is asked to always favour
xml:lang even in an HTML context. Is this really what's intended? I
think this ought to be clarified.
http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-April/003652.html
--
La
must be one
or more space characters; otherwise there may be zero or more space
characters after the final attribute.
--
Lachlan Hunt
http://lachy.id.au/
goal for HTML5 and XHTML to slowly
converge, or is the goal for them to diverage?
This issue was explained in detail in this recent blog entry.
http://blog.whatwg.org/html-vs-xhtml
--
Lachlan Hunt
http://lachy.id.au/
Ian Hickson wrote:
On Wed, 29 Nov 2006, Lachlan Hunt wrote:
The spec defines special handling for rel="alternate stylesheet", but
also defines that "alternate" with type="application/atom+xml" or
type="application/rss+xml" implies the "feed"
Julian Reschke wrote:
Lachlan Hunt schrieb:
...
The fact is that authors already try things like , and even
. I've seen all of those examples in the wild. See, for
instance, the source of the XML 1.0 spec (and many others) which claim
to be XHTML as text/html, littered with plen
already use that for autodiscovery.
--
Lachlan Hunt
http://lachy.id.au/
t use string processing to
do silly things like this:
xhtml = "" + html + ""
--
Lachlan Hunt
http://lachy.id.au/
.
No you couldn't, and how would that be a benefit if you could? XHTML 5
requires xmlns, HTML 5 forbids it. HTML 5 requires ,
XHTML 5 doesn't (though it's still well-formed, so you could get away
with it).
[1] http://hsivonen.iki.fi/producing-xml/
--
Lachlan Hunt
http://lachy.id.au/
lesheet, a syndication feed or both?
href="/feed" title="Blog Entries">
Firefox 2 and IE7 recognised it as a feed. Opera 9 and and Safari 2 didn't.
(Though it should be noted that Opera and Safari have trouble with any
other value specified with alternate, not just stylesheet).
--
Lachlan Hunt
http://lachy.id.au/
Ian Hickson wrote:
On Sun, 26 Nov 2006, Lachlan Hunt wrote:
So, given that it already states the conforming content model is the
same as that of its parent element, I don't see how that is an
additional restriction at all.
Consider:
Text
parent element, with the additional restriction that it cannot contain
any descendant noscript elements.
[1] http://www.whatwg.org/specs/web-apps/current-work/#the-noscript
--
Lachlan Hunt
http://lachy.id.au/
r is it a secret?)
Is it related to the whatwg?
It's just an alternative name for the WHATWG, which some people thought
had a better acronym, presumably because it looks like an abbreviation
of "What The F...?"
--
Lachlan Hunt
http://lachy.id.au/
wg.org/
[2] http://del.icio.us/lachlan.hunt/WHATWG
[3] http://lachy.id.au/log/2006/11/future-of-html
[4] http://blog.whatwg.org/faq/
--
Lachlan Hunt
http://lachy.id.au/
Elliotte Harold wrote:
Lachlan Hunt wrote:
At the very least, ISO-8859-1 must be treated as Windows-1252. I'm
not sure about the other ISO-8859 encodings. Numeric and hex
character references from 128 to 159 must also be treated as
Windows-1252 code points.
I understand why you want
I thought it could be condensed to the
other one. Since (a & b) is equivalent to (a, b)|(b, a), aren't both of
those equivalent as well?
--
Lachlan Hunt
http://lachy.id.au/
her before or after tbodys, but
not between them.
,(( thead.elem?, tfoot.elem?, tbody.elem+ )
I think that should be changed to this
( thead.elem?, tfoot.elem? & tbody.elem+ )
If I've done that correctly, that should allow these:
...
...
But disallows thi
it would make more sense for XStandard to replace a
textarea, but there must be implementation issues with that or something.
http://xstandard.com/page.asp?p=A4372B00-8D7F-4166-977C-64E5C4E3708E&ss=C2B75B64-1544-429D-ACDA-07D17E35FB56
--
Lachlan Hunt
http://lachy.id.au/
HTML 4.01 document type declaration.
To be fair, there are at least two. :-)
http://www.damowmow.com/playground/html-or-xml.html
http://www.damowmow.com/playground/html-or-xml.xml
--
Lachlan Hunt
http://lachy.id.au/
Bjoern Hoehrmann wrote:
* Lachlan Hunt wrote:
Yes, never! For one, a conforming HTML 5 (not XHTML 5) document
requires the DOCTYPE to be and that is not well-formed XML.
Yes it is.
Oh, sorry. You're right. I thought it required a PUBLIC or SYSTEM
identifier. I got confused be
Elliotte Harold wrote:
Lachlan Hunt wrote:
Why is the specific syntax so important?
The specific syntax is important because there's a huge, useful
toolchain for processing XML and there's essentially zilch for
processing this strange HTML 5 thing.
In the real world, you cannot
101 - 200 of 388 matches
Mail list logo
