Ian Hickson wrote:
I used this idea for the window.history.pushState() idea:
http://whatwg.org/specs/web-apps/current-work/#the-session
Let me know if you have any comments.
It doesn't cover the bookmark case, only the back-forward case, so I don't
think this removes the need for a
The 'rev' attribute from prior versions of HTML is missing in WA1,
and I think it deserves not to be left out. 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
# For styling languages that consist of pure text, user agents must use a
# concatenation of the contents of all the text nodes and CDATA nodes that are
# direct children of the style element (ignoring any other nodes such as
# comments or elements), in tree order.
This does not give the
In HTML 4, the 'href' attribute of the base element is #REQUIRED.
Is there a reason why in HTML 5 it is not required?
~fantasai
On Mon, 18 Jul 2005, fantasai wrote:
HTML 4 #REQUIREs the 'content' attribute for meta. It does not require
'name' probably only because the DTD can't express a requirement of
either 'name' or 'http-equiv': as WA1 notes, a meta element without
a 'name' attribute isn't defining any meta
Ian Hickson wrote:
On Mon, 18 Jul 2005, fantasai wrote:
In HTML 4, the 'href' attribute of the base element is #REQUIRED.
Is there a reason why in HTML 5 it is not required?
What's the point in making it required?
What's the point in making the img element's 'src' attribute required?
Ian Hickson wrote:
On Mon, 18 Jul 2005, fantasai wrote:
HTML 4 #REQUIREs the 'content' attribute for meta. It does not require
'name' probably only because the DTD can't express a requirement of
either 'name' or 'http-equiv': as WA1 notes, a meta element without
a 'name' attribute isn't
On Mon, 18 Jul 2005, fantasai wrote:
Ian Hickson wrote:
On Mon, 18 Jul 2005, fantasai wrote:
In HTML 4, the 'href' attribute of the base element is #REQUIRED.
Is there a reason why in HTML 5 it is not required?
What's the point in making it required?
What's the point in making
On Mon, 18 Jul 2005, fantasai wrote:
Ian Hickson wrote:
On Mon, 18 Jul 2005, fantasai wrote:
HTML 4 #REQUIREs the 'content' attribute for meta. It does not
require 'name' probably only because the DTD can't express a
requirement of either 'name' or 'http-equiv': as WA1 notes, a
fantasai wrote:
The 'rev' attribute from prior versions of HTML is missing in WA1,
and I think it deserves not to be left out.
I don't. It's almost entirely useless, and no one really uses it anyways.
Most common link types
out there are used with 'rel', but some 'rev' values can also be
Btw, in HTML5 class name handling is easier through the DOMTokenString
interface, you just write:
element.classNames.add(somethingThatIsOnlyVisibleOnScreen)
/olav
Dean Edwards wrote:
If I set element.style.display = block how do I hide it using a style
sheet when it is printed?
I dont think you should set element.style.display to block, if the
element should be visible only on screen and not in print. It would be
better to dynamically assign it a
[EMAIL PROTECTED] wrote:
The user interface of rel and rev can be exactly the same, only rev under
the heading of reverse.
AFAIK there is no difference between
a href=1.html rel=prev
and
a href=1.html rev=next
So, functionally, you're just breaking a link toolbar into two
On 7/18/05, Ian Hickson [EMAIL PROTECTED] wrote:
Why would you suspend a timer?
(And why would the UA not suspend the timers itself?)
You're saying that when a user print's an HTML5 user agent MUST stop
all setTimeout counters, I don't see that in the spec, nor why it
would be an expectation of
Olav Junker Kjær wrote:
Dean Edwards wrote:
IE has some nice onbeforeprint/onafterprint events. Can we add these too?
Arent these event mostly used to transform the view before printing it?
I think this is better handled by a print-specific style-sheet today.
If I set
On Monday 2005-07-18 08:44 -0400, fantasai wrote:
In HTML 4, the 'href' attribute of the base element is #REQUIRED.
Is there a reason why in HTML 5 it is not required?
base target=foo is pretty common on pages that use frames. Then
again, the web apps spec doesn't seem to mention target at
Ian Hickson wrote:
On Mon, 18 Jul 2005 [EMAIL PROTECTED] wrote:
It would mean that leaving the attribute out violates a conformance
requirement, making the document non-conformant.
...the advantage of which being...?
I don't understand the point in making this code:
// this element will
Jim Ley wrote:
On 7/18/05, Ian Hickson [EMAIL PROTECTED] wrote:
Why would you suspend a timer?
(And why would the UA not suspend the timers itself?)
You're saying that when a user print's an HTML5 user agent MUST stop
all setTimeout counters, I don't see that in the spec, nor why it
would be
On 7/19/05, Matthew Raymond [EMAIL PROTECTED] wrote:
Jim Ley wrote:
You're saying that when a user print's an HTML5 user agent MUST stop
all setTimeout counters, I don't see that in the spec, nor why it
would be an expectation of a scripter.
So wait, we need to add new events because
Ian Hickson wrote:
On Mon, 18 Jul 2005, Dean Edwards wrote:
OK. Forget CSS for a moment (although this is still a consideration for
me). What if I want to suspend a timer while the page is being printed?
Printing is (supposedly) instantaneous. Why would you suspend a timer?
(And why would
Matthew Raymond wrote:
The common use of onbeforeprint/onafterprint is to add content to a
document that is only relevant to printed media, this is something
that cannot be done with CSS, since CSS is optional, so if we just
hide content with CSS, we're stuck with the situation that users
On Tue, 19 Jul 2005, Dean Edwards wrote:
Ian Hickson wrote:
On Mon, 18 Jul 2005, Dean Edwards wrote:
OK. Forget CSS for a moment (although this is still a consideration
for me). What if I want to suspend a timer while the page is being
printed?
Printing is (supposedly)
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. It's quite possible to
Dear WHAT-WG,
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 rendered
L. David Baron wrote:
On Monday 2005-07-18 08:44 -0400, fantasai wrote:
In HTML 4, the 'href' attribute of the base element is #REQUIRED.
Is there a reason why in HTML 5 it is not required?
base target=foo is pretty common on pages that use frames. Then
again, the web apps spec doesn't
Ian Hickson wrote:
On Mon, 18 Jul 2005, fantasai wrote:
Ian Hickson wrote:
On Mon, 18 Jul 2005, fantasai wrote:
HTML 4 #REQUIREs the 'content' attribute for meta. It does not
require 'name' probably only because the DTD can't express a
requirement of either 'name' or 'http-equiv': as WA1
26 matches
Mail list logo
