Vendor prefixes for bleeding-edge #Chromium features will soon be gone; to be replaced by flags (similar to Firefox) bit.ly/10wFJ3V
@mnot For the record: I’d have preferred all to use/extend existing standards à la#DublinCoree. But then, there’re proprietary use cases…
@mnot Well, I suspect a strong “not invented here” motivation (but I’ve no inside info). Also check bit.ly/10vaWo1.
@mnot Re: “proprietary extension to HTML”—To be fair, they’ve edited the MetaExtensions Wikbit.ly/10vaB4Ptm (search for “twitter:”).
Great article on media=”print” #CSS: http://t.co/lSe4vxUF9Q by @drublic. Feat. basic #typography support, eg, orphans/widows. (via @mathias)
@afterglowlee Thanks :D xywh.js crops, while #smfplayer highlights. Both are valid use cases. @rtroncy knows the full WG discussion history…
#Twitter adds more #TwitterCards (new: app, product, [photo] gallery; old: summary, photo, video): bit.ly/17ctRZL (via @TwitterAPI)
Welcoming the new #RFC memorandums #JSONpointer bit.ly/17cs7Q6 together w/ #JSONpatch bit.ly/17cs7Q5 for #JSON #HTTP PATCH.