with HTML5. A richer set of tags, along with RDFa, microdata, and microformats, are enabling a more useful, data driven web for both programs and your users.
present rich, device-aware features and experiences. Incredible device access innovations are being developed and implemented, from audio/video input access to microphones and cameras, to local data such as contacts & events, and even tilt orientation.
and better communication. Web Sockets and Server-Sent Events are pushing (pun intended) data between client and server more efficiently than ever before.
enhancing web apps without sacrificing your semantic structure or performance. Additionally Web Open Font Format (WOFF) provides typographic flexibility and control far beyond anything the web has offered before.
It is a collection of features, technologies, and APIs that brings the power of the desktop and the vibrancy of multimedia experience to the web—while amplifying the web’s core strengths of interactivity and connectivity. HTML5 includes the fifth revision of the HTML markup language, CSS3, and a series of JavaScript APIs. Together, these technologies enable you to create complex applications that previously could be created only for desktop platforms. HTML5 ~= HTML + CSS + JS
It is a collection of features, technologies, and APIs that brings the power of the desktop and the vibrancy of multimedia experience to the web—while amplifying the web’s core strengths of interactivity and connectivity. HTML5 includes the fifth revision of the HTML markup language, CSS3, and a series of JavaScript APIs. Together, these technologies enable you to create complex applications that previously could be created only for desktop platforms. Together, these technologies enable you to create complex applications that previously could be created only for desktop platforms. HTML5 ~= HTML + CSS + JS
:OFFLINE & STORAGE :DEVICE ACCESS :CONNECTIVITY :PERFORMANCE :LOOKS AWESOME! “The solution is in your hands: develop Web apps, not apps!” - Tim Berners-Lee WWW2012's keynote
for Nuclear Research (CERN) in October, 1994. It was founded at the Massachusetts Institute of Technology Laboratory for Computer Science (MIT/LCS) with support from the European Commission and the Defense Advanced Research Projects Agency (DARPA), which had pioneered the Internet and its predecessor ARPANET. World Wide Web Consortium (HTMLWG)
for Nuclear Research (CERN) in October, 1994. It was founded at the Massachusetts Institute of Technology Laboratory for Computer Science (MIT/LCS) with support from the European Commission and the Defense Advanced Research Projects Agency (DARPA), which had pioneered the Internet and its predecessor ARPANET. World Wide Web Consortium (HTMLWG) 1994, the internet was called the ‘information super-highway’
members in the adoption of new standards. Prior to its creation, incompatible versions of HTML were offered by different vendors, increasing the potential for inconsistency between web pages. The consortium was created to get all those vendors to agree on a set of core principles and components which would be supported by everyone. World Wide Web Consortium (HTMLWG) <blink> </blink>
interested in evolving HTML and related technologies. The WHATWG was founded by individuals from Apple, the Mozilla Foundation and Opera Software. Web Hypertext Application Technology Working Group (WHATWG) this is not your dad’s HTMLWG
of web standards monitored by the W3C, and its decision to abandon HTML in favor of XHTML 2.0, and HTML!4.01 had not been updated since 2000. The WHATWG mailing list was announced two days after the initiatives of a joint Opera–Mozilla position paper had been voted down by the W3C. Web Hypertext Application Technology Working Group (WHATWG)
of web standards monitored by the W3C, and its decision to abandon HTML in favor of XHTML 2.0, and HTML!4.01 had not been updated since 2000. The WHATWG mailing list was announced two days after the initiatives of a joint Opera–Mozilla position paper had been voted down by the W3C. Web Hypertext Application Technology Working Group (WHATWG)
that the W3C’s new HTMLWG adopt the WHATWG’s HTML5 as the starting point of its work and name its future deliverable "HTML5". On May 9th 2007, the new HTMLWG resolved to do that. Web Hypertext Application Technology Working Group (WHATWG) But, who is really in charge?
will see presentations from all the web standards advocates advocating people to use webkit prefixes. Our job is to solve interoperability. At this point we’re trying to figure out which and how many webkit prefix properties to actually implement support for in Mozilla. If we don’t support webkit prefixes, we are locking ourselves out of parts of the mobile web.“ W3C meeting on February 7, 2012
will see presentations from all the web standards advocates advocating people to use webkit prefixes. Our job is to solve interoperability. At this point we’re trying to figure out which and how many webkit prefix properties to actually implement support for in Mozilla. If we don’t support webkit prefixes, we are locking ourselves out of parts of the mobile web.“ W3C meeting on February 7, 2012 plinss: As soon as we do this, vendor prefixes have failed. tantek: I don't think we need to throw out the baby with the bathwater. plinss: I think the fact that Mozilla is discussing this publicly is harmful. plinss: Nevermind actually doing this. Florian: So what should we do? dbaron: So what should we do, disband the WG? plinss: yes plinss: If we go down this path we have broken standardization.
will see presentations from all the web standards advocates advocating people to use webkit prefixes. Our job is to solve interoperability. At this point we’re trying to figure out which and how many webkit prefix properties to actually implement support for in Mozilla. If we don’t support webkit prefixes, we are locking ourselves out of parts of the mobile web.“ W3C meeting on February 7, 2012 plinss: As soon as we do this, vendor prefixes have failed. tantek: I don't think we need to throw out the baby with the bathwater. plinss: I think the fact that Mozilla is discussing this publicly is harmful. plinss: Nevermind actually doing this. Florian: So what should we do? dbaron: So what should we do, disband the WG? plinss: yes plinss: If we go down this path we have broken standardization.
development platform. Becoming more powerful then anyone has ever imagined. Who is in charge of the spec? That is a fantastic debate. Mobile is a powerful force for change, but at what point is the community superseded by our corporate overlords?
anotheruiguy
yoshifumi_ishikura
kutakutat
up1
niftycorp
javiergs
lamodatech
makihiro
daisukeshinoku
karugamo
wasabeef
datanalyticslabo
andyhume
cromwellryan
shpigford
trallard
davidbonilla
michaelherold
afnizarnur
chriscoyier
colly
notwaldorf
pedronauck
zakiyama
![[CSSWG] Minutes and Resolutions Paris F2F Monday Morning 2012-02-06 http://goo.gl/WICTr](https://files.speakerdeck.com/presentations/4fb142a7206fc500220029fc/slide_36.jpg){kind=link}
![[CSSWG] Minutes and Resolutions Paris F2F Monday Morning 2012-02-06 http://goo.gl/WICTr](https://files.speakerdeck.com/presentations/4fb142a7206fc500220029fc/slide_37.jpg){kind=link}
![NEW <FORM> TYPES <input type="text" required /> <input type="email" value="[email protected]"](https://files.speakerdeck.com/presentations/4fb142a7206fc500220029fc/slide_45.jpg){kind=link}
