Re: [whatwg] HTML6 Doctype

2010-08-29 Thread Julian Reschke
On 29.08.2010 05:15, David John Burrowes wrote: Hello all, I wanted to chime in on this discussion. Let me say up front that clearly the w3c and the browser vendors all are on the same page as you, Ian. I'm not in the position to be challenging your collective wisdom! ... With respect to t

Re: [whatwg] [html5] r4949 - [giow] (0) The CSS rules need to do attribute value matching consistently across [...]

2010-08-29 Thread L. David Baron
On Wednesday 2010-08-25 10:28 +0200, Anne van Kesteren wrote: > On Wed, 25 Aug 2010 09:44:34 +0200, Christoph Päper > wrote: > >I for one would expect that selector to match that element, > >although I would never write HTML like that. Imagine a browser or > >user stylesheet where you would effect

Re: [whatwg] HTML6 Doctype

2010-08-29 Thread Tab Atkins Jr.
On Sat, Aug 28, 2010 at 8:15 PM, David John Burrowes wrote: > I agree that they don't have access to versioning info from within the > languages. > > But, CSS has some sense of versions (CSS, CSS2, and CSS3).  This gives me > some ability to say "ah, SurfBrowser 1.0 and 2.0 supported CSS1, but w

Re: [whatwg] HTML6 Doctype

2010-08-29 Thread David John Burrowes
On 2010/8/28, at 下午8:52, Scott González wrote: > What percentage of all versions of all browsers do you think fully > support any version of any spec? Saying that browser X supports some > part of CSS2 is no more or less useful than saying browser X supports > some part of CSS as it is defined to

Re: [whatwg] HTML6 Doctype

2010-08-29 Thread Joshua Cranmer
On 08/29/2010 11:33 AM, David John Burrowes wrote: As I see it, if I'm developing for other major platforms (java, osx, windows, ...) I have a fair degree of certainty which versions of those platforms support what features, and that's really useful in situations where I'm targeting (either f

Re: [whatwg] HTML6 Doctype

2010-08-29 Thread Boris Zbarsky
On 8/29/10 1:53 PM, Joshua Cranmer wrote: Most authors don't care about whether or not an implementation supports an entire, full specification; they just want to know "Can I use this feature in this browser?" So saying that all major implementations support much of CSS 2 to a high degree of corr

Re: [whatwg] Have tabstrip / tab elements been discussed?

2010-08-29 Thread E.J. Zufelt
On 2010-08-28, at 7:00 PM, Benjamin Hawkes-Lewis wrote: > > On 28 Aug 2010, at 23:39, E.J. Zufelt wrote: >> I am suggesting that a different tab page would not be "navigation" in the >> common sense, as the user is not leaving the current page, just switching >> contexts within the application.