Andy, 2012 is the _Candidate_ Recommendation stage (the third milestone in the timeline you linked to). So after CR there's still the Proposed Recommendation milestone before HTML5 will actually reach the status of a W3C Recommendation. According to WHATWG's sources, the expected W3C Recommendation stage is still 2022.
TBH, when I read the 2022 date, I was pretty shocked and disappointed. But if that's when the browser developers expect the standard to become a full W3C recommendation, then that's what I have to go on. That said, as the WHATWG FAQ explains, you'll be able to use _parts_ of the HTML5 standard long before then. But at this point, only WebKit even has 50% of the standard implemented. It doesn't help that each rendering engine is implementing different parts of the HTML5 specification, so even if every browser had 50% implemented, what you'll realistically be able to use (without using JavaScript to emulate functionality) is going to be far less than that. It would probably speed things up if, throughout the development of a new standard, the W3C lists which parts of the specification are pretty much fixed and should be implemented by browser developers first. That would cut down the time between when browser developers decide to implement a feature and when web developers can actually use it. On Jun 10, 6:55 pm, Andy Dirnberger <[email protected]> wrote: > I realize that they've fallen behind, but you originally said 2022, > which is a bit further away than 2012. > > On Jun 10, 4:40 pm, calvin <[email protected]> wrote: > > > As much as I am grateful for the W3C and believe that an organization > > like theirs is vital to the continued growth of the web, the W3C has > > not had a great track record in keeping to their projected timeline > > for HTML5. And the W3C has long since fallen behind the provisional > > timeline you linked to. For instance, by March 2010, the HTML work > > group still hadn't reached "Last Call", when they were already > > supposed to have reached the Candidate Recommendation > > stage:http://dev.w3.org/html5/status/2010-03.html > > > I have more faith in the WHATWG projections for HTML5's completion > > since they're the ones who have to implement it. At this point, the > > Candidate Recommendation stage isn't expected to be reached until > > 2012:http://wiki.whatwg.org/wiki/FAQ#When_will_HTML5_be_finished.3F > > > On Jun 9, 10:04 pm, Andy Dirnberger <[email protected]> wrote: > > > > According to the W3C, they expect to reach the recommendation > > > milestone for HTML5 in Q3 > > > 2010.http://www.w3.org/2007/03/HTML-WG-charter.html#deliverables > > > > On Jun 9, 11:11 pm, calvin <[email protected]> wrote: > > > > > You can "use" whatever you want, but HTML5 is nowhere near completion. > > > > It's not even expected to become a W3C recommendation until 2022, and > > > > few browsers besides Chrome and Safari even support half of the > > > > specification. > > > > > On Jun 9, 6:40 am, ytbryan <[email protected]> wrote: > > > > > > how do I render html element in cakephp? > > > > > > Thanks! > > > > > > /Bryan Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
