Slow Week in Web Standards
Scanning through my twitter timeline, realized that it had been another week in web standards devoid of progress, passion and humour…
#HTML5 #HTML5DE Die deutsche Übersetzung der HTML5-Spezifikation beginnt. http://t.co/by4ZMerr4a
— Stefan Schumacher (@HTML5_Deutsch) November 16, 2014
EARLY after5 drafts https://t.co/ep1EiH0dLD https://t.co/bP2QEBUyEn /cc @marcosc
— Steve Faulkner (@stevefaulkner) November 19, 2014
Added some info to chrome bug: support ability for users to pause/stop animated gifs https://t.co/H8v3gxvs2J cc @mikewest @iheni @JibberJim
— Steve Faulkner (@stevefaulkner) November 17, 2014
Device APIs Working Group starts Web Sensor API unification effort. @anssik’s post: http://t.co/os9Fbme32x Repo: https://t.co/Q1Ut8Ys4rz
— Web Platform Daily (@openwebdaily) November 17, 2014
Concerning the upcoming TAG election: http://t.co/mjZkpuI714 Nominations open until 30 November.
— W3C TAG (@w3ctag) November 17, 2014
@shepazu suggested I join on IRC, within 5 minutes @LeonieWatson works her magic. I am a member of @w3c @svgwg #JFDI
— Steve Faulkner (@stevefaulkner) November 18, 2014
@MichielBijl there a are some test files i use https://t.co/lwuHAhMlS2 and http://t.co/BZfMJrXuh1 not ordered though
— Steve Faulkner (@stevefaulkner) November 18, 2014
Service Workers Draft Published http://t.co/uliqamQkuC
— W3C (@w3c) November 18, 2014
Custom Elements is an emerging web standard that lets developers create their own HTML tags. Learn more https://t.co/BOSiY7bEvp @agektmr
— Google Developers (@googledevs) November 18, 2014
EME/ DRM spec is on Github https://t.co/6z8RmjWE6w
— Bruce Lawson (@brucel) November 18, 2014
Big Beautiful Dropcaps forked and accessibility improved https://t.co/TXw4HN69lQ @sgalineau @dudleystorey
— Steve Faulkner (@stevefaulkner) November 20, 2014
The Group That Rules the Web http://t.co/AWo3VzU8o8 via @erikanavara #HTML5 @W3C
— Steve Faulkner (@stevefaulkner) November 20, 2014
I blame @rogerjohansson (again) for getting me mixed up in the “HTML5 SHIT SHOW!” Back in 2007 I read http://t.co/3x8Qbekqbh
— Steve Faulkner (@stevefaulkner) November 21, 2014
Microsoft engaging on blink-dev again \o/ https://t.co/gApCEdHAga you won’t believe what happened next…
— Domenic Denicola (@domenic) November 18, 2014
Thanks @HTML5Weekly for including “Design like we give a damn!” 4min talk http://t.co/HKRoPNl2fM in this week’s http://t.co/BKWW6zos8p
— Léonie Watson (@LeonieWatson) November 21, 2014
Here is why an increased percentage of W3C work groups have at least two Chairs: https://t.co/AM8mM4MtY7
— W3C (@w3c) November 20, 2014
WHATWG/W3C Collaboration http://t.co/i8izw4zFpo by @samruby
— Steve Faulkner (@stevefaulkner) November 21, 2014
proposed accessibility API mapping for #HTML5 <time> element http://t.co/lsqmLxbOLm
— Steve Faulkner (@stevefaulkner) November 21, 2014
emailed an old webstandardista with an optimistic message about life in community driven HTML development after5 https://t.co/3PqnVxsIxR
— Steve Faulkner (@stevefaulkner) November 18, 2014
bugging @IE about support for exposing semantics of non-interactive HTML semantics http://t.co/2PDBONMSD9 #accessibility /cc @dstorey
— Steve Faulkner (@stevefaulkner) November 21, 2014
This week: Chrome HTML5 features, Service Workers, Net neutrality, etc., by @koalie http://t.co/DhEQd4VmJd
— W3C (@w3c) November 21, 2014
WebKit unprefixing: I forgot to announce that “-webkit-alt” is “alt” since early Nov – alternate text via CSS http://t.co/smhjtXu1P3
— Dean Jackson (@grorgwork) November 20, 2014
W3C Brasil e Ministério Público do Estado de SP divulgam Cartilha de #Acessibilidade na Web http://t.co/YeYsPKrc7Z
— iMasters (@iMasters) November 17, 2014
Lead guitarist of @googlechrome JP @takoratta lets hair down to support @w3c new mission statement, Kick Out the Jams pic.twitter.com/jwXFB1vKSC
— Michael[tm] Smith (@sideshowbarker) November 22, 2014
All it takes is truth in advertising “Note: This #polymer demo is not usable for some people, including keyboard and assistive tech users”
— Steve Faulkner (@stevefaulkner) November 22, 2014
MOBILE FIRST! WHY NOT USABLE FIRST? #accessibility pic.twitter.com/iQL1JeCofM
— Steve Faulkner (@stevefaulkner) November 22, 2014
Good Guy Greg: DEMO’S GOOGLE’S VISION FOR FUTURE OF THE WEB UNUSABLE BY 20% pic.twitter.com/IEFGLpr8rl
— Steve Faulkner (@stevefaulkner) November 22, 2014
hey, but its not all bad vibes at the BIG G http://t.co/jodzESywgo http://t.co/3xg5DmxoVt @googlechrome
— Steve Faulkner (@stevefaulkner) November 22, 2014
After success of #polymer-gmail demo at #chromedevsummit the team turn talents to building the real world http://t.co/PanHraLK5x #satire
— Steve Faulkner (@stevefaulkner) November 22, 2014
Witness @googlechrome‘s @takoratta shredding the living hell out of the fretboard in support of @w3c #KickOutTheJams pic.twitter.com/UFKC46GONU
— Michael[tm] Smith (@sideshowbarker) November 22, 2014
Reminder: I’m writing Understanding ECMAScript 6 in the open. You can file issues and track progress here: https://t.co/H47aTML4TS
— Nicholas C. Zakas (@slicknet) November 22, 2014
https://t.co/2sOdFjAecJ MUST use >= TLS 1.2
— IETF HTTPbis WG (@httpbis) November 22, 2014
tl;dr (1) if (!standards) player pianos no worky; (2) % valid markup == % Catholics who marry as virgins (3) html4 < html5 < Infinite Jest
— Erika Doyle Navara (@erikanavara) November 20, 2014
bugging @googlechrome about HTML tables semantics not being exposed in Accessibility APIs https://t.co/LZFBOzUSOy #accessibility #HTML5
— Steve Faulkner (@stevefaulkner) November 20, 2014
Finally stuck a #HTML5 sticker on my laptop pic.twitter.com/DdUKAHGqMs
— Steve Faulkner (@stevefaulkner) November 18, 2014
Comments
Comments for this post are closed.