Matthew Raymond wrote:
Most common link types
out there are used with 'rel', but some 'rev' values can also be
useful. Here are some use cases:
- rev=footnote for a link back from the footnote or endnote to
the source anchor in the main text
- rev=help for a link to the part of the
Ian Hickson wrote:
On Tue, 19 Jul 2005, Dean Edwards wrote:
The point is, I can do all sorts of things using script. Alter styles,
create elements etc. But when I switch media, I have no programmatic way
to alter those effects. Please specify I means to do this.
You don't switch media.
What kind of input type is the following according to HTML 5:
input type= email
According to the attribute value rules of HTML 4 it should be 'email', but I'm
not sure how that is implemented at the moment. Similar question for:
input type=email value=[EMAIL PROTECTED]
... valid
A couple of questions regarding the Audio,
URL:http://whatwg.org/specs/web-apps/current-work/#sound interface
1. Is it sensible to put a restriction on contnet types?
2. Regarding the loop() method on the Audio interface: Would it be
sensible to add loop points/offsets? See
Dean Edwards wrote:
OK, we don't switch media. But when I press print or invoke the print
method, a copy of the DOM is sent to the printer. If I have altered the
DOM by adding elements or by changing the style property then I would
like to be able to undo those changes before my DOM goes to
Matthew Raymond wrote:
Dean Edwards wrote:
OK, we don't switch media. But when I press print or invoke the print
method, a copy of the DOM is sent to the printer. If I have altered the
DOM by adding elements or by changing the style property then I would
like to be able to undo those changes
Hi,
the section on Audio,
http://whatwg.org/specs/web-apps/current-work/#sound, says:
The Audio() constructor takes a single argument, a URI (or IRI), which
is resolved using the script context's window.location.href
Does this mean that a possible base href should indeed be ignored here?
Kornel Lesinski wrote:
style attribute is supposed to have cascade value like ID selector.
No, style attributes override everything. See
http://www.w3.org/TR/CSS21/cascade.html#specificity
smime.p7s
Description: S/MIME Cryptographic Signature
Matthew Raymond wrote:
I know this isn't how you meant it, but this all seems a bit user
hostile. The user sees something on the screen he/she wants to print,
but an event is called at the last minute that changes the content to
something else
You can already do that with CSS...
@media
Sjoerd Visscher wrote:
Matthew Raymond wrote:
I know this isn't how you meant it, but this all seems a bit user
hostile. The user sees something on the screen he/she wants to print,
but an event is called at the last minute that changes the content to
something else before the user can print.
Quoting Matthew Raymond [EMAIL PROTECTED]:
You can do that with css anyway, what is your point?
That CSS can be overridden by the user stylesheet?
Userbase: 2. (Both are geek.)
--
Anne van Kesteren
http://annevankesteren.nl/
Hi,
http://whatwg.org/specs/web-apps/current-work/#the-dom says:
To ease migration from HTML to XHTML, UAs must assign the
http://www.w3.org/1999/xhtml namespace to elements in that are parsed in
documents labelled as text/html, at least for the purposes of the DOM
and CSS.
This does not
On Tue, 19 Jul 2005, Dimitri Glazkov wrote:
No, I don't believe that is always the case. The user _sometimes_ wants
to print what he/she sees, but my experience tells me that most of the
time, the user wants to print what is considered main content of the
page. For example, I am using my
On 7/19/05, Ian Hickson [EMAIL PROTECTED] wrote:
@media {
navigation { display: none; }
}
Ok, at least we all agree that it's not what the user sees :)
What functionality are you lacking? (Both in screen and print.)
Like, adding contextual content for print. Just like your main content
Ian Hickson wrote:
What functionality are you lacking? (Both in screen and print.)
Suppose I want to add inprint links' full urls in parenteses after
links' text. In CSS I can do;
a[href]:after {
content: attr(href);
}
But it's not enough since href may contain unresolved URL and I want
On Tue, 19 Jul 2005, Anne van Kesteren wrote:
What kind of input type is the following according to HTML 5:
input type= email
WF2 doesn't define this (intentionally). Extrapolating from HTML4 it would
be of type email; which is probably what WA1 will eventually say.
According to the
On Tue, 19 Jul 2005, Anne van Kesteren wrote:
table
tr
thamountthtype
tr id=order repeat=template repeat-start=1
tdfoothbar
/table
... becomes:
table
tr
tdfoothbar
tr
thamountthtype
tr id=order repeat=template repeat-start=1
tdfoothbar
/table
Yes.
Ian Hickson wrote:
You may notice that very few elements and attributes in HTML5 at the
moment are required. This is not entirely coincidental.
I think I know what you are getting at: You want to eradicate invalid
HTML on the web, by declaring everything to be valid!
From the perspective of
On Tue, 19 Jul 2005, fantasai wrote:
Then, please make that exception explicit in the conformance
requirements section. Currently the only normatively allowed exception
is for interpretation of the author's intent -- and checking script
output doesn't fall into that category.
As I
Quoting Ian Hickson [EMAIL PROTECTED]:
input type=email value=[EMAIL PROTECTED]
... valid or invalid?
The form control there would not be valid. There's nothing in either HTML4
or WF2 that says that leading whitespace on the value= attribute should
de stripped, as far as I can tell.
Dimitri Glazkov wrote:
On 7/19/05, Ian Hickson [EMAIL PROTECTED] wrote:
What functionality are you lacking? (Both in screen and print.)
Like, adding contextual content for print. Just like your main content
is not the only thing on the page, same may hold true for the
On Tue, 19 Jul 2005, Dimitri Glazkov wrote:
a) my invoice format requires a timestamp that says something like this:
printed by [person] on [timestamp].
This use case is being dealt with in the CSS paged media and CSS generated
content specifications.
b) To capture the essence of the
On Tue, 19 Jul 2005, Maniac wrote:
Suppose I want to add inprint links' full urls in parenteses after
links' text. In CSS I can do;
a[href]:after {
content: attr(href);
}
But it's not enough since href may contain unresolved URL and I want
them full.
That's a use case for a new
On Tue, 19 Jul 2005 [EMAIL PROTECTED] wrote:
The form control there would not be valid. There's nothing in either
HTML4 or WF2 that says that leading whitespace on the value=
attribute should de stripped, as far as I can tell.
They may be stripped and authors should not include them.
In the Web Applications 1.0 Working Draft 18 July 2005, Section 2.3.8.
The header element (link:
http://whatwg.org/specs/web-apps/current-work/#the-header) there is
an example of code given. The penultimate line in the code is *extremely*
long, causing the browser window to double in width
Ian Hickson wrote:
That's a use case for a new feature in CSS, not in HTML. :-)
It is solvable with events discussed. My point is that authors
traditionally use scripting to solve things that can't be solved with
other means. It's normal.
Quoting Christopher Hester [EMAIL PROTECTED]:
The page also seems amazingly long for a web page. This means it
takes a long time to load (even on broadband). If the user only wants
one section, they still have to load the whole thing. Previewing it
for print in Opera 8 (which takes several
On 7/19/05, Ian Hickson [EMAIL PROTECTED] wrote:
b) To capture the essence of the browsing session, I would like to build
a breadcrumb at the bottom of the printed page, displaying titles and
urls of pages the user have visited on the site during this visit.
That seems like something that
On Tue, 19 Jul 2005, Christopher Hester wrote:
In the Web Applications 1.0 Working Draft 18 July 2005, Section 2.3.8. The
header element (link:
http://whatwg.org/specs/web-apps/current-work/#the-header) there is an example
of code given. The penultimate line in the code is *extremely* long,
On Tue, 19 Jul 2005, Maniac wrote:
Ian Hickson wrote:
That's a use case for a new feature in CSS, not in HTML. :-)
It is solvable with events discussed. My point is that authors
traditionally use scripting to solve things that can't be solved with
other means. It's normal.
Granted. But
On Tue, 19 Jul 2005, Dimitri Glazkov wrote:
However, I think am starting to see what you're seeing. Basically, your
approach is to provide all content in the DOM tree and then flip
switches as needed to present it to various media types. Right?
Right.
Essentially, you are creating
On Tue, 19 Jul 2005, Rob Mientjes wrote:
On 7/19/05, Anne van Kesteren [EMAIL PROTECTED] wrote:
I'm opposed to that. Separate sections in separate documents make reading
the
draft a pain. (I have argued otherwise in the past...)
Agreed, but the code example is ridiculous. I opt for
Christian Biesinger wrote:
http://whatwg.org/specs/web-apps/current-work/#sound, says:
The Audio() constructor takes a single argument, a URI (or IRI), which
is resolved using the script context's window.location.href
Does this mean that a possible base href should indeed be ignored here?
Ian Hickson:
The difficulty is in walking the fine line between useful and
over-constrained. For example, the fact that ol/ol is invalid in HTML4
is a real problem.
Well,
olliThis list item will be replaced by a script./ol
is not invalid. An empty list doesn't make any sense otherwise,
Jim Ley wrote:
This is flawed though, as it requires all the content to be in the
page, including media-specific content. CSS cannot remove content, CSS
is optional, consider:
This page span id=viewedviewed/spanspan
id=printedprinted/span on ...
This is a contrived example of how people
Matthew Raymond wrote:
For instance, such events could be combined with AJAX to force people
into a pay-to-print scenario.
What's wrong with paying to print a high quality version of an image? If
you ask me this is a great example of why we should allow these events.
-dean
Christoph Päper wrote:
both table models, HTML and CSS, are row-centric, i.e. sequential data
is shown horizontally. Sometimes the opposite is desired. Therefore I
wonder if it was feasible to add a boolean 'transpose' attribute to
the 'table' element type? With it set, a table would be
On Tue, 19 Jul 2005, Jim Ley wrote:
Someone will probably suggest CSS background-images as a suitable for
this aswell, yet again ignoring the fact that CSS is _optional_, and
content-images must not be in background images as they simply won't
be seen without CSS or if background images are
On 7/19/05, J. Graham [EMAIL PROTECTED] wrote:
On Tue, 19 Jul 2005, Jim Ley wrote:
Someone will probably suggest CSS background-images as a suitable for
this aswell, yet again ignoring the fact that CSS is _optional_, and
content-images must not be in background images as they simply
On Tue, Jul 19, 2005 at 01:25:51 +, Ian Hickson wrote:
http://www.whatwg.org/demos/date-01/
Which implements input type=datetime
Doesn't conform to ISO 8601 of the datetime attribute in WF2.
It doesn't need to. That's the fallback value.
Don't quite understand this. How can it fall
On Tue, 19 Jul 2005, Anne van Kesteren wrote:
http://annevankesteren.nl/projects/whatwg/spec
Overall the main problem with this spec is the lack of the use of
RFC2119 normative words.
For example:
|The contentEditable applies to all elements with some exceptions: It
|does not apply to
41 matches
Mail list logo
