Re: [whatwg] Is now an official HTML5 element?

Silvia wrote: > Even if the specs differ, in the end what matters is what browsers > implement. Partially agree, it matters what conformance checkers implement and in the case of . the major HTML conformance checker will implement the conformance rules in the W3C HTML spec. This will leave the WH

Re: [whatwg] Is now an official HTML5 element?

On Thu, 14 Feb 2013, Ian Yang wrote: > > There is one thing which makes me confused. You mentioned the is > "mainly serves as a styling hook." If what we need is just a styling > hook, why was introduced? We could just use . Yeah, that was my argument too. But browser vendors added it, and th

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Thu, Feb 14, 2013 at 3:35 PM, Robert O'Callahan wrote: > On Thu, Feb 14, 2013 at 5:16 PM, Rik Cabanier wrote: > >> Looking at the WebKit implementation, I'm unsure how 'opaque' can >> implemented for accelerated canvas. It might work with non-accelerated >> canvas but would have to run some ex

Re: [whatwg] Is now an official HTML5 element?

Hi Hickson, Thanks for the help. There is one thing which makes me confused. You mentioned the is "mainly serves as a styling hook." If what we need is just a styling hook, why was introduced? We could just use . So iiuic, the still has its purpose because it natively has the role "main". Plea

Re: [whatwg] Is now an official HTML5 element?

On Thu, 14 Feb 2013, Ian Yang wrote: > > In the past, I always regarded a sectioning main content area is an > indispensable part in a document. Today, information above tell me that > the main content area seem doesn't need to be a titled section. I'm not sure what you mean. is just there to

Re: [whatwg] Is now an official HTML5 element?

> I will try to determine what topic > belongs to which group in the future. The simple answer is: have your discussion wherever you feel comfortable to have it. Even if the specs differ, in the end what matters is what browsers implement. If a discussion about a topic is more appropriate in a di

Re: [whatwg] Is now an official HTML5 element?

On Thu, Feb 14, 2013 at 12:37 PM, Charles McCathie Nevile < cha...@yandex-team.ru> wrote: > Hi Ian, > > > On Thu, 14 Feb 2013 01:31:36 +0100, Aurelio De Rosa < > aurelioder...@gmail.com> wrote: > > I think this should answer your question: >> >> http://wiki.whatwg.org/wiki/**FAQ#What_is_the_WHATW

Re: [whatwg] Is now an official HTML5 element?

Hi Ian, On Thu, 14 Feb 2013 01:31:36 +0100, Aurelio De Rosa wrote: I think this should answer your question: http://wiki.whatwg.org/wiki/FAQ#What_is_the_WHATWG.3F It doesn't seem to provide much useful information on the differences. According to its charter

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Thu, Feb 14, 2013 at 5:16 PM, Rik Cabanier wrote: > Looking at the WebKit implementation, I'm unsure how 'opaque' can > implemented for accelerated canvas. It might work with non-accelerated > canvas but would have to run some experiments. > I also look at mozilla's Core Graphics implementatio

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Thu, Feb 14, 2013 at 2:27 PM, Robert O'Callahan wrote: > On Thu, Feb 14, 2013 at 4:18 PM, Rik Cabanier wrote: > >> On Thu, Feb 14, 2013 at 2:12 PM, Robert O'Callahan >> wrote: >> >>> On Thu, Feb 14, 2013 at 3:55 PM, Rik Cabanier wrote: >>> What would happen if you set 'opaque' to true an

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Thu, Feb 14, 2013 at 4:18 PM, Rik Cabanier wrote: > On Thu, Feb 14, 2013 at 2:12 PM, Robert O'Callahan > wrote: > >> On Thu, Feb 14, 2013 at 3:55 PM, Rik Cabanier wrote: >> >>> What would happen if you set 'opaque' to true and you draw with alpha and >>> 'copy' compositing? It seems that tha

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Thu, Feb 14, 2013 at 2:12 PM, Robert O'Callahan wrote: > On Thu, Feb 14, 2013 at 3:55 PM, Rik Cabanier wrote: > >> What would happen if you set 'opaque' to true and you draw with alpha and >> 'copy' compositing? It seems that that has the same issue (unless you're >> OK >> with breaking drawin

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Thu, Feb 14, 2013 at 3:55 PM, Rik Cabanier wrote: > What would happen if you set 'opaque' to true and you draw with alpha and > 'copy' compositing? It seems that that has the same issue (unless you're OK > with breaking drawing). > The alpha values of all moz-opaque canvas pixels are simply n

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Thu, Feb 14, 2013 at 12:39 PM, Stephen White wrote: > On Wed, Feb 13, 2013 at 5:31 PM, Rik Cabanier wrote: > >> On Wed, Feb 13, 2013 at 11:25 AM, Stephen White > >wrote: >> >> > On Wed, Feb 13, 2013 at 12:22 PM, Rik Cabanier >> wrote: >> > >> >> For blending optimizations, it might be better

Re: [whatwg] Is now an official HTML5 element?

Sorry, maybe the markup structure still needs some modifications. One thing needs to be figured out is that should be contained within ? Or rather, is a supporting content for the entire document or just for ? If it is the latter, then is fine being within . The spec doesn't look like it has c

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Wed, Feb 13, 2013 at 5:31 PM, Rik Cabanier wrote: > On Wed, Feb 13, 2013 at 11:25 AM, Stephen White >wrote: > > > On Wed, Feb 13, 2013 at 12:22 PM, Rik Cabanier > wrote: > > > >> For blending optimizations, it might be better to introduce a function > >> instead of a boolean attribute like '

Re: [whatwg] Is now an official HTML5 element?

On Thu, Feb 14, 2013 at 1:06 AM, Ian Hickson wrote: > On Wed, 13 Feb 2013, Ian Yang wrote: > > > > I saw the SitePoint article "Introducing the New HTML5 > > Element" yesterday. Does > > that mean element has been approved by all editors of the work

Re: [whatwg] Is now an official HTML5 element?

Hi Aurelio, I see. So whatwg mainly focus on the development of HTML and APIs needed for web applications. Thank you very much. Kind Regards, Ian On Thu, Feb 14, 2013 at 8:31 AM, Aurelio De Rosa wrote: > I think this should answer your question: > > http://wiki.whatwg.org/wiki/FAQ#What_is_the_W

Re: [whatwg] Is now an official HTML5 element?

I think this should answer your question: http://wiki.whatwg.org/wiki/FAQ#What_is_the_WHATWG.3F Best regards 2013/2/14 Ian Yang > Hi Steve, > > Thanks. And sorry, but til now I still don't understand the differences > between whatwg and html wg. Could you please explain? > > Regards, > Ian > >

Re: [whatwg] Is now an official HTML5 element?

Hi Steve, Thanks. And sorry, but til now I still don't understand the differences between whatwg and html wg. Could you please explain? Regards, Ian On Thu, Feb 14, 2013 at 12:59 AM, Steve Faulkner wrote: > Hi Ian, > > I cannot speak for whatwg, but from the W3C HTML spec side the main element

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Wed, Feb 13, 2013 at 11:25 AM, Stephen White wrote: > On Wed, Feb 13, 2013 at 12:22 PM, Rik Cabanier wrote: > >> For blending optimizations, it might be better to introduce a function >> instead of a boolean attribute like 'opaque'. >> What you really want, is to matte [1] the canvas with a so

[whatwg] inputmode feedback

Hi, Mozilla did implement an inputmode attribute for the element a few months ago and the HTML specification has been updated after that to introduce that attribute. Given that the specification and our implementation was not matching, we decided to delay the release of that feature [1] and not a

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Wed, Feb 13, 2013 at 12:22 PM, Rik Cabanier wrote: > For blending optimizations, it might be better to introduce a function > instead of a boolean attribute like 'opaque'. > What you really want, is to matte [1] the canvas with a solid color so you > can optimize compositing. > > How about thi

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

For blending optimizations, it might be better to introduce a function instead of a boolean attribute like 'opaque'. What you really want, is to matte [1] the canvas with a solid color so you can optimize compositing. How about this API: void applyMatte(DOMString color); // color is a CSS rgb col

Re: [whatwg] Is now an official HTML5 element?

On Wed, 13 Feb 2013, Ian Yang wrote: > > I saw the SitePoint article "Introducing the New HTML5 > Element" yesterday. Does > that mean element has been approved by all editors of the working > group? is currently in the HTML standard. That doesn

[whatwg] Is now an official HTML5 element?

Hi Ian, I cannot speak for whatwg, but from the W3C HTML spec side the main element is in the HTML 5.1 spec and has been implemented in browsers and so will be added to HTML5 spec at some point as it likely meets the CR exit criteria. as for it being a sectioning element, there is currently an op

Re: [whatwg] itemtypes from same vocabulary

Sorry if it wasn't clear, at the time that those discussions took place, only one itemtype could be used. Since then, the spec was changed to allow multiple itemtypes from the same vocabulary. However, both discussions also touch on the issue of using multiple vocabularies in itemtype. For example

Re: [whatwg] itemtypes from same vocabulary

Hi Lin, I'm confused because it looks like Microdata currently allows multiple itemtypes to be expressed: """ The itemtype attribute, if specified, must have a value that is an unordered set of unique space-separated tokens that are case-sensitive, each of which is a valid URL that is an absolute

Re: [whatwg] itemtypes from same vocabulary

Itemtype cannot reference different vocabs. Here are two relevant discussions that I know of, one with Hixie and the other with the HTML Data Task Force. http://lists.w3.org/Archives/Public/public-whatwg-archive/2011Jun/0364.html http://lists.w3.org/Archives/Public/public-html-data-tf/2011Oct/0072

[whatwg] itemtypes from same vocabulary

Hi all, I am looking for some guidance about the use of multiple itemtypes in microdata [1], specifically the phrase "defined to use the same vocabulary" in: """ The item types must all be types defined in applicable specifications and must all be defined to use the same vocabulary. """ For exam

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Tue, Feb 12, 2013 at 6:14 PM, Rik Cabanier wrote: > > > On Tue, Feb 12, 2013 at 2:56 PM, Stephen White > wrote: > >> On Fri, Nov 23, 2012 at 6:04 PM, Ian Hickson wrote: >> >> > On Thu, 29 Mar 2012, Jeremy Apthorp wrote: >> > > On Thu, Mar 29, 2012 at 10:25 AM, Jeremy Apthorp < >> jere...@chr

Re: [whatwg] Why do we have and ?

On Tue, Feb 12, 2013 at 11:20 AM, Mounir Lamouri wrote: > Regarding week, I still believe that the use cases are pretty weak but > the most important issue is that there is no good UI for this on Mobile > AFAIK. > There aren't stock widgets, but this isn't a hard UI problem to solve. For exampl

[whatwg] Is now an official HTML5 element?

Hi editors and all other folks, I saw the SitePoint article "Introducing the New HTML5 Element" yesterday. Does that mean element has been approved by all editors of the working group? However, in spec, it still says that element is not a sectionin

[whatwg] Fwd: Re: Why do we have and ?

Original Message Subject: Re: [whatwg] Why do we have and type='week'>? Date: Wed, 13 Feb 2013 08:59:49 +0100 From: Bronislav Klučka To: Jukka K. Korpela On 12.2.2013 18:39, Jukka K. Korpela wrote: 2013-02-12 19:26, Tab Atkins Jr. wrote: The fact that author