On Mon, Feb 25, 2008 at 10:29 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 8 Feb 2007, Jorgen Horstink wrote:
On Feb 8, 2007, at 9:00 PM, David Latapie wrote:
On Thu, 8 Feb 2007 19:17:32 +, Nicholas Shanks wrote:
On 6 Feb 2007, at 07:57, Karl Dubost wrote:
On Wed, Feb 27, 2008 at 7:38 PM, Geoff Pack [EMAIL PROTECTED] wrote:
Why does the HTML5 spec say The div element represents nothing at all ?
[http://www.whatwg.org/specs/web-apps/current-work/#the-div]
Div clearly stands for 'division', as was specified in the HTML 3.2 spec:
DIV elements
On Thu, Feb 28, 2008 at 1:44 PM, Paweł Stradomski [EMAIL PROTECTED]
wrote:
W liście Robert O'Rourke z dnia czwartek 28 lutego 2008:
Paweł Stradomski wrote:
div class=steps
input href=/basket.html class=basket-step value=Basket /
input href=/checkout.html class=current
On Thu, Feb 28, 2008 at 5:07 PM, [EMAIL PROTECTED] wrote:
I'm still not clear to me how section/ is anything more than a div/.
HTML4 said: The DIV and SPAN elements, in conjunction with the id and class
attributes, offer a generic mechanism for adding structure to documents (
On Fri, Feb 29, 2008 at 11:39 AM, Nicholas Zakas [EMAIL PROTECTED]
wrote:
I don't think it's as clear as you make it out to be. A section and a
division. I hate to consult a dictionary on this, but one definition for
section is subdivision. The naming alone does not make it clear what the
On Fri, Feb 29, 2008 at 1:04 PM, Dave Hodder [EMAIL PROTECTED] wrote:
Tab Atkins Jr. wrote (with snippage):
In HTML5, the hx hierarchy is explicitly ignored. Instead, they're
all treated the same. The actual heading level is determined by
section nesting.
That doesn't sound correct
On Fri, Feb 29, 2008 at 10:57 PM, Nicholas C. Zakas [EMAIL PROTECTED]
wrote:
From this description, it seems like the section/ element has little
use. If you're talking about writing articles, most authors consider the
start and end of sections as implicitly defined by headings. Making this
TH and TD
* abbr (I think that's supported by screen readers, but need to verify)
I don't really see that these attributes actually help anyone.
I don't have a screen reader to verify, but afaik abbr= is used to provide a
shortened form of the header when it is spoken aloud repeatedly.
On Wed, Mar 26, 2008 at 11:22 AM, Krzysztof Żelechowski
[EMAIL PROTECTED] wrote:
Another example of missing interleave in HTML is
not to be able to interleave list items with table rows
in order to provide numbering.
These are independent sets of elements and they cannot play together.
Sad.
On Fri, Mar 28, 2008 at 12:07 PM, Krzysztof Żelechowski
[EMAIL PROTECTED] wrote:
Dnia 28-03-2008, Pt o godzinie 09:12 -0500, Tab Atkins Jr. pisze:
And the original problem can be solved using CSS2;
I only wanted to bring a similar example:
HTML poorly supports interleaving unrelated
I agree, very insightful post, MPT. You cut to the true issues quicker than
we were doing earlier. ^_^
Nicholas Shanks, you may well be right. ins/del/mark (idm) are a form
of embedded metadata, but how would we extract such out of the html flow?
This isn't metadata about the document, after
On Mon, Apr 21, 2008 at 4:15 AM, Jens Meiert [EMAIL PROTECTED] wrote:
The point of abbr is to expand the acronym, not to just mark up what
is
an acryonym or abbreviation.
Doesn't this claim that the general information that some text is an
abbreviation (w/o an expanded form) is basically
On Mon, Apr 28, 2008 at 2:04 PM, Křištof Želechovski [EMAIL PROTECTED]
wrote:
What is the advantage of cutting an image to parts
and having the browser show them as one by putting them aside?
I would rather use one big image in the first place.
Chris
On my company's web site, our header
On Wed, May 14, 2008 at 3:36 AM, Mikko Rantalainen
[EMAIL PROTECTED] wrote:
If dialog is used instead of dialogue then it should be designed in
a such way that it can be used for dialog box in addition to dialogue
(e.g. chat) in the future.
I severely doubt this is possible or desirable.
2008/5/13 Ian Hickson [EMAIL PROTECTED]:
On Tue, 13 May 2008, Paweł Stradomski wrote:
[...]
Perhaps talk ? Short and simple, although not exactly equal in meaning
to dialog.
That's probably the best suggestion so far, but I'm still not convinced
it's really much better than dialog. I
On Thu, May 15, 2008 at 6:20 PM, Ernest Cline [EMAIL PROTECTED]
wrote:
-Original Message-
From: Mike Wilson [EMAIL PROTECTED]
Sent: May 15, 2008 8:02 AM
To: 'WHATWG' [EMAIL PROTECTED]
Subject: Re: [whatwg] Thoughts on HTML 5 - dialog
Yes, I also quite like the analogy with
On Wed, May 21, 2008 at 5:30 PM, Ian Hickson [EMAIL PROTECTED] wrote:
I'm thinking of introducing a
new attribute. I haven't worked out what to call it yet, but definitely
not src, source, src2, content, value, or data -- maybe
html or doc, though neither of those are great. This attribute
On Fri, May 30, 2008 at 12:45 PM, Shannon [EMAIL PROTECTED] wrote:
There's a lot of focus on use cases. Here is the one that led me to start
this thread:
http://www.duttondirect.com/automotive/for_sale (disclaimer: I am not
responsible for the design of this page)
The table hover effect is
On Tue, Jun 3, 2008 at 7:36 AM, Philip Jägenstedt [EMAIL PROTECTED] wrote:
Hi!
I'm a bit puzzled about how to interpret the poster attribute on
HTMLVideoElement:
The poster attribute gives the address of an image file that the user
agent can show while no video data is available. The
On Wed, Jun 4, 2008 at 8:43 AM, Philip Taylor
[EMAIL PROTECTED][EMAIL PROTECTED]
wrote:
On 04/06/2008, Křištof Želechovski [EMAIL PROTECTED] wrote:
Regarding your page at the URL
http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level.html
#the-embed:
[...]
Element
On Tue, Jul 15, 2008 at 1:30 PM, Gervase Markham [EMAIL PROTECTED] wrote:
Csaba Gabor wrote:
Therefore, it makes sense to float those values to the top of the
select element in a reasonable way. What's reasonable? I would like
to suggest: frequencyLimit=percent
I assume you would want
On Wed, Jul 16, 2008 at 2:44 AM, Thomas Broyer [EMAIL PROTECTED] wrote:
On Tue, Jul 15, 2008 at 8:30 PM, Gervase Markham wrote:
Csaba Gabor wrote:
Therefore, it makes sense to float those values to the top of the
select element in a reasonable way. What's reasonable? I would like
to
I did some searching through the archives, but didn't find anything at all
that talked about this. Out of curiousity, was there a reason that datetime
doesn't store/send it's value as a unix timestamp? True, the standard
unixtime unit is insufficient for representing a useful range of dates, but
On Fri, Aug 1, 2008 at 7:28 AM, Russell Leggett
[EMAIL PROTECTED]wrote:
For what it's worth, Shannon, I totally agree with you. Not only is this
something I have been wanted for a long time, but I think it belongs in the
html. It's one thing if you just want columns, which is being covered
Blarg forward to list.
-- Forwarded message --
From: Tab Atkins Jr. [EMAIL PROTECTED]
Date: Tue, Aug 5, 2008 at 9:15 AM
Subject: Re: [whatwg] Nested lists
To: noclip [EMAIL PROTECTED]
On Mon, Aug 4, 2008 at 8:15 PM, noclip [EMAIL PROTECTED] wrote:
Are there plans to natively
On Fri, Aug 22, 2008 at 6:49 PM, Ben Adida [EMAIL PROTECTED] wrote:
We would need 5 new attributes to become valid and reserved for RDFa
use: @property, @about, @typeof, @resource, and @datatype. It would be
nice if @rev didn't go away, since we use it, and we also use @rel,
which already
On Sun, Aug 24, 2008 at 3:10 PM, Julian Reschke [EMAIL PROTECTED]wrote:
Tab Atkins Jr. wrote:
The point was made before that html5 already has extensive extension
mechanisms in place that can address the particular needs of various
communities without requiring it to be written explicitly
On Fri, Aug 22, 2008 at 2:53 PM, Ben Adida [EMAIL PROTECTED] wrote:
This doesn't allow you to say things about *another* resource, but
that's OK, because out-of-band metadata and data often travel their
separate ways.
It's not okay for us. There are no good ways to embed metadata in media
On Thu, Aug 28, 2008 at 7:13 AM, Eduard Pascual [EMAIL PROTECTED]wrote:
I think some of you got my point quite better than others; and maybe I
should clarify the idea. I see no issue with having some attributes to
embed semantics inline within the HTML, the same way we have style to
embed
On Thu, Aug 28, 2008 at 11:11 AM, Kristof Zelechovski [EMAIL PROTECTED]
wrote:
javascript:goBack(); is a labeled statement in JavaScript and the label
is
javascript. What purpose does it serve in your inline code?
SCRIPT[type=text/xml] can be used for semantics, including RDF.
Inline
On Thu, Aug 28, 2008 at 11:24 AM, Ben Adida [EMAIL PROTECTED] wrote:
Tab Atkins Jr. wrote:
Those folks must *really* hate microformats, then, as they pack *all* of
their semantics into @class.
No, the conflict was about putting URIs and CURIEs into attributes that
were previously free
On Thu, Aug 28, 2008 at 1:59 PM, Kristof Zelechovski
[EMAIL PROTECTED]wrote:
I am not opposing local metadata; I have already explained you can use the
SCRIPT element for the purpose. I only say that metadata should not be
inside content they describe in order to avoid circularity. This is a
On Thu, Aug 28, 2008 at 4:42 PM, Kristof Zelechovski
[EMAIL PROTECTED]wrote:
Ian's question was about what happens when it goes down forever, or gets
taken over, intercepted, squatted, spoofed or redirected because of a
malicious DNS. I should have known better how to ask it. The browser
Manu Sporny wrote:
Tab Atkins Jr. wrote:
On Thu, Aug 28, 2008 at 4:42 PM, Kristof Zelechovski
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Ian's question was about what happens when it goes down forever, or
gets
taken over, intercepted, squatted, spoofed or redirected because
(Note: I've been discussing just such a CSS-like rdf format with Ben
offlist, inspired directly by Eduard's proposal earlier.)
On Fri, Aug 29, 2008 at 1:09 PM, Ben Adida [EMAIL PROTECTED] wrote:
Greg Houston wrote:
My suggestion keeps the metadata code tidy, and more human readable.
On Fri, Aug 29, 2008 at 2:33 PM, Ben Adida [EMAIL PROTECTED] wrote:
I'm going to keep my answer somewhat brief because Manu and I have
privately discussed wrapping up this thread so we don't take up too much
of people's time. I'll focus on simple points.
(Note: I've been discussing just
On Fri, Aug 29, 2008 at 3:10 PM, Ben Adida [EMAIL PROTECTED] wrote:
Tab Atkins Jr. wrote:
Is this approximately your intended message? If so, then how do you
square this with the plain-to-see usefulness and heavy adoption of CSS?
CSS is great: it actually separates semantics
To list.
-- Forwarded message --
From: Tab Atkins Jr. [EMAIL PROTECTED]
Date: Fri, Sep 19, 2008 at 6:23 PM
Subject: Re: [whatwg] Can var possibly work?
To: Ozob the Great [EMAIL PROTECTED]
On Fri, Sep 19, 2008 at 5:41 PM, Ozob the Great [EMAIL PROTECTED] wrote:
I am concerned
On Tue, Sep 30, 2008 at 4:10 AM, Andy Lyttle [EMAIL PROTECTED] wrote:
I do not like this idea at all. That is what LABEL is for, and
disappearing
it's so kewl text is as annoying as BLINK and BGSOUND.
Chris
The label tag is great for labels that are displayed outside the input
box (in
On Tue, Sep 30, 2008 at 11:36 AM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Sep 30, 2008, at 7:57 AM, Garrett Smith wrote:
If and until user enters text, the alternate text is displayed.
The confusing part is that successfully rendered inputs would be
rendered and still use the alt.
The
blarg forward to list.
-- Forwarded message --
From: Tab Atkins Jr. [EMAIL PROTECTED]
Date: Tue, Sep 30, 2008 at 12:39 PM
Subject: Re: [whatwg] Placeholder option for text input boxes
To: Benjamin Hawkes-Lewis [EMAIL PROTECTED]
On Tue, Sep 30, 2008 at 12:25 PM, Benjamin Hawkes
On Tue, Sep 30, 2008 at 12:37 PM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Sep 30, 2008, at 7:00 AM, Tab Atkins Jr. wrote:
Hm. I have a problem with your example. Get local weather forecast
isn't a semantic label for the field - it doesn't describe what the field
is for. It describes what
On Tue, Sep 30, 2008 at 1:46 PM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Sep 30, 2008, at 10:54 AM, Tab Atkins Jr. wrote:
Of course, the aesthetics of splitting the description between the label
and the placeholder text can't always be denied. Semantically, though,
you're still using your
On Thu, Oct 2, 2008 at 6:27 PM, Brenton Strine [EMAIL PROTECTED]wrote:
On Tue, Sep 30, 2008 at 11:36 AM, Andy Lyttle [EMAIL PROTECTED] wrote:
[snip]
4) label (moving label textual content into input as placeholder
text; currently with Javascript to mutate the DOM, in the future with CSS
to
On Fri, Oct 3, 2008 at 9:32 AM, Garrett Smith [EMAIL PROTECTED]wrote:
On Thu, Oct 2, 2008 at 4:34 PM, Tab Atkins Jr. [EMAIL PROTECTED]
wrote:
On Thu, Oct 2, 2008 at 6:27 PM, Brenton Strine
[EMAIL PROTECTED]
wrote:
On Tue, Sep 30, 2008 at 11:36 AM, Andy Lyttle [EMAIL PROTECTED]
wrote
On Fri, Oct 3, 2008 at 10:37 AM, Garrett Smith [EMAIL PROTECTED]wrote:
On Fri, Oct 3, 2008 at 8:05 AM, Tab Atkins Jr. [EMAIL PROTECTED]
wrote:
On Fri, Oct 3, 2008 at 9:32 AM, Garrett Smith [EMAIL PROTECTED]
wrote:
On Thu, Oct 2, 2008 at 4:34 PM, Tab Atkins Jr. [EMAIL PROTECTED]
wrote
On Fri, Oct 3, 2008 at 12:24 PM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Oct 3, 2008, at 10:15 AM, Jonas Sicking wrote:
Russell Leggett wrote:
I've wrestled with this because its something that our designer has
wanted to use all over the place for an application I'm working on. It turns
On Fri, Oct 3, 2008 at 5:04 PM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Oct 3, 2008, at 1:31 PM, Adrian Sutton wrote:
On 03/10/08 20:56, Nils Dagsson Moskopp
[EMAIL PROTECTED] wrote:
Am Freitag, den 03.10.2008, 20:41 +0100 schrieb Adrian Sutton:
label for=dateDate: input type=text
On Sat, Oct 4, 2008 at 9:04 AM, Kristof Zelechovski [EMAIL PROTECTED]
wrote:
TJ Atkins said:
Man, I could *really* see the hint function being viable and quite
useful. It offers up a completely new-and-useful semantic, and there's no
particular place it should already go. I'd accept this as a
On Sat, Oct 4, 2008 at 7:41 PM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Oct 4, 2008, at 3:38 PM, timeless wrote:
On 10/3/08, Adrian Sutton [EMAIL PROTECTED] wrote:
Placeholder ... aids usability
having recently fought with some javascript which tried to enhance my
ability to enter text
On Wed, Oct 15, 2008 at 2:39 PM, Mike Wilson [EMAIL PROTECTED] wrote:
Would it be possible to have HTML5 allow the insertion of
input type=hidden ...
(or something with the same effect) anywhere in the document?
This would f ex relieve cases like server-side templating
wanting to attach
On Thu, Oct 16, 2008 at 4:59 PM, Andy Lyttle [EMAIL PROTECTED] wrote:
table
tr
input type=hidden ...
td/td
/tr
/table
This is something I wanted to do recently. I was building HTML in a Perl
script, adding table rows in a loop, and I wanted some rows to contain text
field with
On Mon, Oct 20, 2008 at 7:32 AM, Julian Reschke [EMAIL PROTECTED]wrote:
Håkon Wium Lie wrote:
I'd like to have a simple way of using button along with a to
create pretty links. This markup works in Opera, Mozilla, and Webkit:
a href=http://www.w3.org/;buttonW3C/button/a
but it's not
On Tue, Oct 21, 2008 at 9:36 AM, Eduard Pascual [EMAIL PROTECTED]wrote:
On Tue, Oct 21, 2008 at 2:16 PM, Aaron Swartz [EMAIL PROTECTED] wrote:
My proposal: add something to HTML5 so that the transaction looks like
this:
Client: GET /login
Server: htmlform method=post
On Wed, Oct 22, 2008 at 10:41 AM, Oldřich Vetešník [EMAIL PROTECTED]wrote:
Hello,
I'd like to throw a question out here, please don't shoot me if it's been
already answered, I'm a full-time coder and don't have an internet at home
so I can't make any deep researches in your archives.
Q: Is
On Thu, Oct 23, 2008 at 12:45 PM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Oct 23, 2008, at 5:31 AM, Ian Hickson wrote:
This use case is definitely something we want to consider, but I don't
think it's about required=. It's about an option in the select being a
non-option (as it were).
On Fri, Oct 24, 2008 at 12:37 AM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Oct 23, 2008, at 12:19 PM, Tab Atkins Jr. wrote:
Ultimately the display of the hint is, and should be, up to the UA, so that
non-full-featured devices can display things in a maximally helpful way to
the user. Within
On Fri, Oct 24, 2008 at 11:57 AM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Oct 24, 2008, at 8:23 AM, Tab Atkins Jr. wrote:
So, pulling it all together, my proposal for a hinting ability on select
is thus:
select can have a @hint attribute, which takes a text value. If there
is no option
On Tue, Oct 28, 2008 at 11:39 AM, Markus Ernst [EMAIL PROTECTED] wrote:
Ian Hickson schrieb:
On Tue, 31 Oct 2006, Lachlan Hunt wrote:
There are workarounds using fieldset and legend for the question, like
this.
fieldset
legendGender:/legend
label for=minput type=radio id=m name=gender
On Wed, Oct 29, 2008 at 11:32 PM, Garrett Smith [EMAIL PROTECTED]wrote:
Ian Hickson wrote:
On Wed, 6 Jun 2007, Sander wrote:
The specs say that for select ...the change event shall be fired when
the selection is completed Does this mean that, when using a keyboard
for navigation, the
On Thu, Oct 30, 2008 at 1:47 PM, Kristof Zelechovski
[EMAIL PROTECTED]wrote:
Indeed, INPUT[type=email] is confusing as well. I would add [type=address]
and [type=address-list] as candidates because an e-mail address is the most
common type of an address on the Web (the e-mail part can be
On Sat, Nov 1, 2008 at 11:13 AM, Pentasis [EMAIL PROTECTED] wrote:
Yes, but this is a theoretical explanation that does not provide a
consistent, practical solution.
I don't understand why these solutions aren't consistent or practical.
First of all, the spec admits it itself:
HTML does
On Sun, Nov 2, 2008 at 3:53 AM, Pentasis [EMAIL PROTECTED] wrote:
* As a style sheet selector (when an author wishes to assign style
information to a set of elements).
* For general purpose processing by user agents.
The first role is clear, it is used for styles (not semantics)
Ian
On Sun, Nov 9, 2008 at 8:10 PM, Eduard Pascual [EMAIL PROTECTED] wrote:
I can't say for sure if this is an issue from the spec document
itself, or just a rendering bug on my browser (FF 3.0.3), but here it
goes:
Within the section 4.3.1 The script element, on the algorythm
labeled Running a
On Tue, Nov 11, 2008 at 5:33 PM, Eduard Pascual [EMAIL PROTECTED]wrote:
It is a quite common practice on current web pages to style the h1..h6
elements to have them blend properly with the overall style of a site.
For HTML4/XHTML1 documents this is quite trivial; but with HTML5 the
number
On Fri, Nov 14, 2008 at 7:40 AM, Pentasis [EMAIL PROTECTED] wrote:
The small element represents small print [...]
The b element represents a span of text to be stylistically offset from
the normal prose without conveying any extra importance [...]
Both definitions seems rather
On Fri, Nov 14, 2008 at 9:38 AM, Pentasis [EMAIL PROTECTED] wrote:
Of course not. You're not intended to. What you *do* get, though, is that
this is a word which is *intentionally* stylistically offset from the rest
of the text. This conveys semantic meaning to a human - it means that the
On Fri, Nov 14, 2008 at 10:44 AM, Pentasis [EMAIL PROTECTED] wrote:
If we wish to communicate that level of semantics, yes. It may not be
useful to us. If you *really* need some metadata/semantics, @class probably
can't convey it with enough granularity. Check out the big discussion from
On Tue, Nov 18, 2008 at 4:09 AM, timeless [EMAIL PROTECTED] wrote:
On Tue, Nov 18, 2008 at 3:15 AM, Tab Atkins Jr. [EMAIL PROTECTED]
wrote:
Keep in mind what we're dealing with here.
dumb web authors. check.
This isn't some trivial Javascript timer firing off events at 60Hz
On Wed, Nov 19, 2008 at 10:09 AM, Martin McEvoy [EMAIL PROTECTED]wrote:
Here is my take on the subject.
There are 1517 instances of @rev
of those:
made occurs 83% of the time (1259 instances)
stylesheet occurs 8.2% of the time (124 instances)
The rest occur 8.9% of the time (135
Ian Hickson wrote:
As can be seen in the feedback below, there is interest in improving the
experience with logging in and out of Web sites.
Currently there are two main mechanisms: HTTP authentication, and
cookie-based authentication with a form login.
Benefits of form authentication
On Tue, Nov 25, 2008 at 7:36 AM, Pentasis [EMAIL PROTECTED] wrote:
Ian Hickson wrote:
While I could see that maybe one day there'd be a use case for time that
would need historical dates, I really think that we'd have to tackle other
calendars in use today before looking at calendars that
On Tue, Nov 25, 2008 at 10:24 AM, Calogero Alex Baldacchino
[EMAIL PROTECTED] wrote:
Smylers wrote:
Asbjørn Ulsberg writes:
On Mon, 17 Nov 2008 15:26:22 +0100, Smylers [EMAIL PROTECTED]
wrote:
In printed material users are typically given no out-of-band
information about the
unexpected effects on existing pages
...
On Thu, 2 Oct 2008, Tab Atkins Jr. wrote:
...
Of course, it's still not in any way semantic. The only difference
between (optional) being displayed near the input and being displayed
*within* the input is one of aesthetics. The meaning of the document
On Tue, Nov 25, 2008 at 3:08 PM, Calogero Alex Baldacchino
[EMAIL PROTECTED] wrote:
Tab Atkins Jr. ha scritto:
On Tue, Nov 25, 2008 at 10:24 AM, Calogero Alex Baldacchino
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Of course that's possible, but, as you noticed too, only
On Sat, Dec 13, 2008 at 1:40 AM, Garrett Smith dhtmlkitc...@gmail.com wrote:
On Thu, Feb 28, 2008 at 10:31 AM, h...@nczonline.net wrote:
We then, as developers, could use that attribute as we see fit and
the document would still validate (for people who care about such
things).
Are people
You're not Nicholas. We don't know if that is what Nicholas expects
his HTML to do or if he is expecting something else. In absence of an
example, I can't do much more than guess. I cannot expect your
assumptions to be correct.
Well, of course, but you sent the message to the entire group, so
On Mon, Dec 15, 2008 at 3:32 PM, Edward Z. Yang
edwardzy...@thewritingpot.com wrote:
Ian Hickson wrote:
I'm not saying don't be standards-compliant; I'm just saying use a subset
of HTML5 that you feel comfortable with (which might also be a subset of
HTML4, for that matter, just with the HTML5
On Mon, Dec 15, 2008 at 4:18 PM, Brenton Strine
brenton.str...@citrix.com wrote:
Maybe after having a few months to think about it some better ideas will pop
up?
I'd like to see a dedicated way to do footnotes as well. I think it would be
worth having the discussion again.
Well, as far as
On Mon, Dec 15, 2008 at 8:36 PM, Garrett Smith dhtmlkitc...@gmail.com wrote:
On Mon, Dec 15, 2008 at 8:02 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
You're not Nicholas. We don't know if that is what Nicholas expects
his HTML to do or if he is expecting something else. In absence
On Mon, Dec 22, 2008 at 2:53 AM, Shital Shah syte...@yahoo.com wrote:
I'm wondering if there are any ideas being discussed to add an ability so
users can embed images in editable areas.
Many modern web applications including blogs and wikis allow users to
visually edit content with rich
On Mon, Dec 22, 2008 at 1:33 PM, Martin Atkins m...@degeneration.co.uk wrote:
However, I'm not sure what the solution is here. If contentEditable was a
real form widget you could imagine it supporting a multipart/form-data
upload of all of its contained images, or something. However, as long as
On Tue, Dec 30, 2008 at 8:50 AM, Maciej Stachowiak m...@apple.com wrote:
On Dec 30, 2008, at 4:55 AM, Anne van Kesteren wrote:
On Tue, 30 Dec 2008 12:38:42 +0100, Ian Hickson i...@hixie.ch wrote:
In 2006 I proposed the following spec for a spellcheck= attribute,
based on requests from the
On Wed, Dec 31, 2008 at 10:41 PM, Charles McCathieNevile
cha...@opera.com wrote:
A standard way to include arbitrary data in a web page and extract it for
machine processing, without having to pre-coordinate their data models.
This isn't a requirement (or in other words, a problem), it's a
On Fri, Jan 2, 2009 at 12:12 AM, Charles McCathieNevile
cha...@opera.com wrote:
On Fri, 02 Jan 2009 05:43:05 +1100, Andi Sidwell a...@takkaria.org wrote:
On 2009-01-01 15:24, Toby A Inkster wrote:
The use cases for RDFa are pretty much the same as those for
Microformats.
Right, but
On Fri, Jan 2, 2009 at 11:55 AM, Julian Reschke julian.resc...@gmx.de wrote:
Tab Atkins Jr. wrote:
...
Solutions for this already exist; embedded N3 in a script tag, just
to name something that Ian already mentioned, allows you to mash RDF
data into a page in a machine-extractable way
On Fri, Jan 2, 2009 at 12:02 PM, Julian Reschke julian.resc...@gmx.de wrote:
Tab Atkins Jr. wrote:
Right, but microformats can be used without any changes to the HTML
language, whereas RDFa requires such changes. If they fulfill the same
use
cases, then there's not much point in adding RDFa
On Fri, Jan 9, 2009 at 5:46 AM, Julian Reschke julian.resc...@gmx.de wrote:
Calogero Alex Baldacchino wrote:
...
This is why I was thinking about somewhat data-rdfa-about,
data-rdfa-property, data-rdfa-content and so on, so that, for the
purposes of an RDFa processor working on top of HTML5
On Fri, Jan 9, 2009 at 1:48 PM, Ben Adida b...@adida.net wrote:
Julian Reschke wrote:
Because the issue is that we don't yet know if we want to support
RDFa. That's the whole point of this thread. Nobody's given a useful
problem statement yet, so we can't evaluate whether there's a problem
On Fri, Jan 9, 2009 at 2:17 PM, Ben Adida b...@adida.net wrote:
Tab Atkins Jr. wrote:
Actually, SearchMonkey is an excellent use case, and provides a
problem statement.
I'm surprised, but very happily so, that you agree.
My confusion stems from the fact that Ian clearly mentioned
On Fri, Jan 9, 2009 at 3:22 PM, Ben Adida b...@adida.net wrote:
Tab Atkins Jr. wrote:
However, Ian has a point in his first paragraph. SearchMonkey does
*not* do auto-discovery; it relies entirely on site owners telling it
precisely what data to extract, where it's allowed to extract it from
On Fri, Jan 9, 2009 at 5:13 PM, Ben Adida b...@adida.net wrote:
Tab Atkins Jr. wrote:
This brings up different issues, however.
Is inherent resistance to spam a condition (even a consideration) for
HTML5? If so, where is the concern around title, which is clearly
featured in search engine
On Sat, Feb 28, 2009 at 4:39 PM, Andy Mabbett a...@pigsonthewing.org.uk wrote:
Do we
really have to illustrate use cases in action, before we can develop the
technology which allows them to be demonstrated exists?
Though I admit it seems ass-backwards until you get it, the answer
is yes, you
On Thu, Mar 5, 2009 at 6:16 AM, Philip Taylor excors+wha...@gmail.com wrote:
But given HTML5's restrictions against BCE years, they'd actually have
to write something more like:
if ($t-getYear() 0) { # (be careful not to write = 0 here)
print time class=time
At this point, I think I'm in strong agreement with two points, that
of allowing negative years and of allowing a range.
Allowing negative years is so trivial on the parsing side as to make
it somewhat ridiculous that it's not supported. The use-cases for a
full year-month-day in BC times are
On Thu, Mar 12, 2009 at 1:04 PM, Kristof Zelechovski
giecr...@stegny.2a.pl wrote:
Notation for negative quantities usually starts with a minus (with
exceptions for bookkeeping). It still does even though ASCII unified the
hyphen with the minus.
We cannot perform interval arithmetic on
On Thu, Mar 12, 2009 at 3:48 PM, Robert J Burns r...@robburns.com wrote:
Hi Tab,
On Mar 12, 2009, at 12:51 PM, Tab Atkins Jr. wrote:
At this point, I think I'm in strong agreement with two points, that
of allowing negative years and of allowing a range.
Allowing negative years is so
On Fri, Mar 27, 2009 at 7:55 PM, Charles Pritchard ch...@jumis.com wrote:
I asked myself the same question, a few minutes after posting my reply.
At this point, I'm really not sure.
My concern is that the string length for a URL may be limited,
somewhere in the platform.
If that's the case,
On Thu, Apr 2, 2009 at 8:37 PM, Robert O'Callahan rob...@ocallahan.org wrote:
I agree it would make sense for new APIs to impose much greater constraints
on consumers, such as requiring them to factor code into transactions,
declare up-front the entire scope of resources that will be accessed,
On Tue, Apr 7, 2009 at 7:24 PM, Brady Eidson beid...@apple.com wrote:
A commonly added feature in browsers these days is private browsing mode
where the intention is that the user's browsing session leaves no footprint
on their machine. Cookies, cache files, history, and other data that the
1 - 100 of 925 matches
Mail list logo
