Skip to main content

/ Treasa Ní Chonchúir

Posts tagged 'HTML5'

Posts tagged 'HTML5'
TitlePublished
Formal Objection to advancing the HTML Image Description document along the REC track
Support for the formation of the Web Hypertext Application Technology Community Group (was Re: HTML Working Group Changes)
@mattmay the real tragedy is that @hixie was required to make such a change in the first place. #a11ytheater #html5 (Twitter)
#nymwars, #html5 edition: http://t.co/TpnCrFj @ms2ger (Twitter)
On <ruby>: "[S]uggesting people use DocBook [to] 'write a web page for kids that includes the word "Tokyo"' is ridiculous." - @bz_moz #html5 (Twitter)
Loved, loved, loved @SickingJ's latest public-html email! Let's *actually* improve things, people. #longdesc #accessibilitytheater #html5 (Twitter)
EPUB & XHTML
Really happy about the HTML WG's ISSUE-41 decision: http://hbr.me/1W7pDn I guess all that work on the change proposal paid off! #html5 #w3c (Twitter)
@jreschke I think the answer is mu: HTML is a more durable format than that accepted by either of those tools. #html5 #ietf (Twitter)
@tabatkins agreed. Please help improve the reasonable/crazy ratio, @james_clark. #html5 (Twitter)
@shelleypowers which is to say: there is no vast, browser-wing conspiracy. /cc @glazou #html5 (Twitter)
Working on my ISSUE-27 change proposal: the HTML5 spec should defer to the @microformats wiki for rel values. #html5 #microformats (Twitter)
Many thanks to Aryeh Gregor and @hsivonen for your excellent replies to the #HTML5 ISSUE-41 poll! http://hbr.me/4sGioj (Twitter)
For a moment today, I thought "Wow! I agree with @shelleypowers about something!" Then she said she was being facetious. #html5 (Twitter)
RT @mattur: #longdesc is accessibility theatre not accessibility. It should have been (officially) buried years ago. #a11y #axs #html5 (Twitter)
The problem is the spec
In @miketaylr's talk at @jqcon. #html5 #jqcon (Twitter)
HTML captioning
Thoughts on converting HTML to Atom
ARIA’s role (class 2: Electric Boogaloo)
RT @jon_neal: Now you can print #html5 in #ie too! http://www.iecss.com/print-protector/ (Twitter)
Wearing my long-awaited #ufdevcamp @microformats shirt. Thanks for getting these out, @t! I'm looking forward to checking out #HTML5 NOW. (Twitter)
Heh, http://isgeolocationpartofhtml5.com is a great single-serving site from @pepelsbey. (via @patrick_h_lauke) #html5 (Twitter)
HTML5: No Joel-in-a-box required
Awesome! Web Worker API implemented for @nodejs: http://groups.google.com/group/nodejs/msg/155aba1eed3b9b86 #html5 (Twitter)
RDFa and the DOM
@diveintomark indeed, I found @cyns' CP to be anti-climactic at best. #html5 (Twitter)
I don't see how one can say that itemprop="" is out of scope while simultaneously saying class="" is in scope. #html5 #microdata (Twitter)
HTML has always been a conversation…
HTML 5 in Last Call at @WHATWG. Viva la revolution! (via @gsnedders) #html5 (Twitter)
Blog templates: a case study in using HTML5’s sectioning elements
Wow, http://bit.ly/Yaue8 is crazypants. #html5 Repeat after me: there is no vast, browser-wing conspiracy. (Twitter)
HTML5: normativity & authoring guides
2 of the #html5 super friends, @zeldman & @meyerweb, point to @sideshowbarker's H:TML draft as an authoring guide. I reply http://tr.im/yg27 (Twitter)
Marking up a slideshow in HTML5
Might skip writing up my rant on prefix-based indirection & ISSUE-41, as @Hixie nailed it: http://tr.im/prefix_antipattern #html5 #rdfa #w3c (Twitter)
Offered without comment
Worldviews of the Web
@sideshowbarker, great slides! Do you have them online in a format with links to the various quote sources etc.? #html5 #xhtml2 #w3c #whatwg (Twitter)
The Web platform: what it is
BarCamp San Diego 5
The Web platform: what it’s not
Microdata, Microformats, and RDF
DOM Consistency
Monolith
Data longevity
Oh noes! 2022 reference at @merbcamp! #html5 (Twitter)
San Diego Web Standards Group
…I find I don’t care any more.
HTML versioning
The Third Dáil
POSH subtitle markup
Interoperability
BlogDay 2007
Re: Neutrality in "HTML 5 differences from HTML 4"
Browser vendors in the HTML Working Group
HTML 5
What to expect from HTML5
Geek from A to Z
Re: Support Existing Content
Re: Support Existing Content
Volume