It's been a while since I read the spec, but I can say that the behavior in
jQuery UI is in line with Hixie's response. We do nothing to adjust the
user-specified min/max/step, but never allow changing to a value that
doesn't fit in the specified range. If you specify a max lower than the
min, any
Ping --- I thought that there was sufficient agreement in this thread,
around the fact that supportsContext, as currently spec'd and currently
implementable, is a feature without a valid use case, that removing it from
the spec is the right thing to do at this point.
Benoit
2013/7/18 Benoit
On Wed, Jul 31, 2013 at 4:26 PM, Benoit Jacob jacob.benoi...@gmail.com wrote:
Ping --- I thought that there was sufficient agreement in this thread,
around the fact that supportsContext, as currently spec'd and currently
implementable, is a feature without a valid use case, that removing it
On Wed, 31 Jul 2013, Benoit Jacob wrote:
Ping --- I thought that there was sufficient agreement in this thread,
around the fact that supportsContext, as currently spec'd and currently
implementable, is a feature without a valid use case, that removing it
from the spec is the right thing to
On Fri, 18 Jan 2013, David Carlisle wrote:
On 17/01/2013 23:31, Ian Hickson wrote:
On Thu, 17 Jan 2013, David Carlisle wrote:
http://www.w3.org/2003/entities/2007doc/xhtmlpubid.html
But basically it solves the problem that the existing list leads to
a situation where data
Hi
Is there work going on on a Splash screen specification ?
There is an attempt at
https://dvcs.w3.org/hg/nativeapps/raw-file/tip/splashscreen/Overview.htmlbut
no user agent implementation.
Apple chose a link rel=apple-touch-startup-image but
On Wed, 31 Jul 2013, Laurent Perez wrote:
Is there work going on on a Splash screen specification ?
What's the use case?
Generally speaking, Web pages load incrementally, so by the time you've
downloaded an image, you should be able to just show the Web page itself,
at least in a state good
On Wed, Jul 31, 2013 at 11:05 AM, Ian Hickson i...@hixie.ch wrote:
(Note that decisions for WHATWG specs aren't made based on consensus. Even
if everyone agrees on something, if there's one more compelling argument
to the contrary, that's the one that's going to win.)
Though of course, what's
On Mon, 1 Jul 2013, Ian Hickson wrote:
One option would be to remove from the stack of open elements any
elements that we are skipping when we bail out of the AAA.
Can anyone see a problem with doing that?
Since nobody raised any problems with this, I've now done this.
For background,
On Mon, 1 Jul 2013, Glenn Maynard wrote:
On Mon, Jul 1, 2013 at 6:16 PM, Ian Hickson i...@hixie.ch wrote:
It seems bad, and maybe rather full of hubris, to make it conforming
to use a label that we know will be interpreted in a manner that is a
willful violation of its spec (that is,
On Thu, 4 Jul 2013, Michael Day wrote:
The problem is that we can't do (2) in _all_ cases, e.g. innerHTML on
an svg can't possibly break out of the svg if it sees one of these
tags, since that's the root of what is being parsed.
Yes, HTML has already lost the composability of parsing
The CSS WG has published a Last Call Working Draft of the
CSS Cascading and Inheritance Module Level 3:
http://www.w3.org/TR/css-cascade-3/
This CSS module describes how to collate style rules and assign
values to all properties on all elements by way of cascading
(choosing a winning
On Thu, 1 Aug 2013, Martin Janecke wrote:
I don't see any sense in making a document that is declared as
ISO-8859-1 and encoded as ISO-8859-1 non-conforming. Just because the
ISO-8859-1 code points are a subset of windows-1252? So is US-ASCII.
Should an US-ASCII declaration also be
13 matches
Mail list logo
