(Please disregard this email if you already received a copy of it)
How should overflow be handled when parsing integers?
Step 8 of the parsing algorithm in both
http://dev.w3.org/html5/spec/Overview.html#rules-for-parsing-integers and
On Sat, 15 Oct 2011 05:27:21 +0100, Anne van Kesteren ann...@opera.com
wrote:
I wrote up a draft:
http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html
(...)
a)
The fullscreen media query is missing (I seriously suggest supporting it)
# @media all and (full-screen) { /* ... */ }
On 10/16/2011 02:17 PM, Daniel Bates wrote:
How should overflow be handled when parsing integers?
Step 8 of the parsing algorithm in
bothhttp://dev.w3.org/html5/spec/Overview.html#rules-for-parsing-integers
andhttp://dev.w3.org/html5/spec/Overview.html#non-negative-integers doesn't
mention
Thanks Tab,
I guess I could have stated myself a little clearer.
The spec says:
DOCTYPEs are required for legacy reasons. When omitted, browsers tend to
use a different rendering mode that is incompatible with some
specifications. Including the DOCTYPE in a document ensures that the browser
makes
This is a great new addition.
However none of the current versions of Browsers provide an easy way to view
cached files when the user is off line. Earlier IE's would give you an
option, but this seems to have been done away with i later versions.
Should not The spec require that compliant browsers
On 10/16/11 2:15 PM, Francis Boumphrey wrote:
My point is, as the only possible use for a DOCTYPE declaration in HTML (any
version) is for including!ENTITYdeclarations
And triggering browsers' standards mode, most importantly.
why bother with an DOCTYPE declaration at all.
To trigger
Boris Zbarsky bzbar...@mit.edu schrieb am Sun, 16 Oct 2011 15:43:26
-0400:
On 10/16/11 2:15 PM, Francis Boumphrey wrote:
My point is, as the only possible use for a DOCTYPE declaration in
HTML (any version) is for including!ENTITYdeclarations
And triggering browsers' standards mode, most
On Sun, 2011-10-16 at 23:10 +0200, Nils Dagsson Moskopp wrote:
Boris Zbarsky bzbar...@mit.edu schrieb am Sun, 16 Oct 2011 15:43:26
-0400:
On 10/16/11 2:15 PM, Francis Boumphrey wrote:
My point is, as the only possible use for a DOCTYPE declaration in
HTML (any version) is for
On Sun, Oct 16, 2011 at 6:06 PM, Ashley Sheridan
a...@ashleysheridan.co.ukwrote:
Surely the html tag would do that? :p
It's optional.
http://www.whatwg.org/specs/web-apps/current-work/multipage/syntax.html#optional-tags
--
Glenn Maynard
On 15/10/2011 5:27 p.m., Anne van Kesteren wrote:
I wrote up a draft:
http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html
Thanks for writing this up.
Comments:
1. We should define what happens when the full-screen element is
removed from a document. Roc and I thought it would be
On 15/10/2011 5:27 p.m., Anne van Kesteren wrote:
http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html
Defining when exactly the fullscreen enabled flag is set for
Document objects I will leave up to HTML. As well as defining the
allowfullscreen attribute. Presumably it should be set
On 17/10/2011 5:31 a.m., João Eiras wrote:
a)
The fullscreen media query is missing (I seriously suggest supporting it)
# @media all and (full-screen) { /* ... */ }
Does it make sense to have on/off as in the Mozilla proposal ? e.g.
and (full-screen:on/ff) ?
We removed this from our
One natural way to represent a collection of structured items is in an
html table. this can coexist with microdata, by using tr itemscope
and td itemprop tags. But by ignoring the structure of the table,
this creates a lot of redundant attribute specification.
It would yield cleaner markup
13 matches
Mail list logo
