| Link roundup, “holy shit, they’ve started yet another war in the Middle East” edition | |
| “Link me up when September ends…” 🎵🎶 | |
| The roller coaster continues: a link roundup | |
| Making standards | |
| Hindsight | |
| @gsnedders @marcosc @WHATWG @w3c I’ll give you a handful this morning, Sam! | |
| @m_ott @mmatuzo I’d add @Hixie, @annevk, @zcorpan. | |
| #iykyk #enamelpin #whatwg | |
| I'm so happy to be able to say that the @webkit team is hiring a second standards engineer. Do you love the web and want to help improve it by collaborating with other engineers at @whatwg, @w3c, @TC39, and elsewhere? Come work with me!
https://t.co/sGXfUYi0zL | |
| @zcorpan @foolip @sundress @soMelanieSaid @Hixie @annevk Yeah, I’m pretty sure I picked up this pronunciation from Anne. | |
| @Lady_Ada_King I always say why-see-gee for @wicg_; “wih-kihg” sounds extremely weird to me.
To be fair, I also say “what wee gee” for @WHATWG. | |
| @eevee There really are! It happens all the time in @WHATWG’s github issue trackers. | |
| If you’ve worked in either @wicg_ or @whatwg before, we hope things will feel familiar and comfortable. And if you’ve never participated in web standards work before, we aim to be a gentle, welcoming space where you can help improve privacy on the web. | |
| Anyone can join & make a proposal! Proposals get worked on in a lightweight incubation process like the @wicg_. When a proposal is ready and has interest from multiple implementers, it may move on to the spec stage, for which we use an efficient, @whatwg inspired process. | |
| RT @WHATWG: A new post from @carmacleod on the blog, about the @htmlstandard's new "Accessibility considerations" section for each element:… | |
| RT @hober: It’s increasingly obvious to me that not including @Hixie’s Baby Steps in the Design Principles doc before it got parked was a b… | |
| @gesa @emilymhorsman @steveklabnik @janl This is also the case for @csswg, @WHATWG, etc. | |
| @fantasai @annevk if public archives are available, import the archive mbox into your mail client & reply from there. that's what I do for @whatwg and @w3c lists I'm not on. | |
| RT @webkit: We're excited to continue collaborating with our colleagues from @ChromiumDev, @MSEdgeDev, & @mozhacks within the @WHATWG's upd… | |
| RT @WHATWG: Blog: Improving interoperability – changes to all our standards will now include tests by default. https://t.co/FRhVJVLKA2 | |
| I should figure out how to get one of those @WHATWG shirts… | |
| @Lachy ok great, see you there! | |
| @Lachy rad! I think I might go to the @SydCSS thing on Thursday. You going? | |
| Whoops, wrong Lachlan. Hey @Lachy, pretty sure @grorg, @smfr and I just walked by you on George St. | |
| @domenic @marcosc @WHATWG a green circle with just a > in it—a nod to “5 > 2” | |
| Formal Objection to advancing the HTML Image Description document along the REC track | |
| Formal Objection to advancing the HTML Image Description document along the REC track | |
| It’s increasingly obvious to me that not including @Hixie’s Baby Steps in the Design Principles doc before it got parked was a big mistake. | |
| Some ideas for new Cards Against Humanity noun cards: “The W3C Process Document,” “CR exit criteria,” “@Lachy & @robinberjon dance contest.” | |
| @stevefaulkner I think it's a stretch to say there have been no objections to it. How do you characterize @hixie's emails as not objecting? | |
| @rwaldron did we read the same email? @Hixie’s mail was measured and dispassionate, unlike your unprofessional tweet just now. | |
| Down to 220 unread in my @whatwg folder! Whoo! | |
| @grigs I originally called it "setec-astronomy=''," but the folk in #secret-treehouse forbid me from doing so. #vbwc #whatwg | |
| [whatwg] <img srcset> for responsive bitmapped content images | |
| [whatwg] <img srcset> for responsive bitmapped content images | |
| Support for the formation of the Web Hypertext Application Technology Community Group (was Re: HTML Working Group Changes) | |
| 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 | |
| [css4-images] The image-set() function (for responsive images) | |
| [css4-images] The image-set() function (for responsive images) | |
| @WHATWG yo dawg, I heard you like commands, so @hixie put a command='' in your <command> so you can reference other commands. | |
| [css4-ui] backdrop for fullscreened elements and modal dialogs/lightboxes | |
| [css4-ui] backdrop for fullscreened elements and modal dialogs/lightboxes | |
| @rmondello you just pulled a @Hixie. | |
| @meyerweb both specs have the same source. @hixie would have to add script to his publishing workflow to s/section/div.section/ in one case. | |
| Not everyone likes @Hixie's spec writing style, but it makes implementing the tokenizer require almost no thought. This is a *good* thing. | |
| Nice. @Hixie paves another cowpath worth writing down somewhere, and we get <select required> as a side effect. http://hbr.me/27FxPN | |
| @djcapelis: you've got it backwards: thank the browser vendors for autocomplete="". @WHATWG specced it for interop. See hbr.me/xt0tL | |
| Several emails from microsoft.com addresses to @WHATWG lists today. Has the fifth major browser vendor decided to get involved with @WHATWG? | |
| Thoughts on converting HTML to Atom | |
| @schwarzwald that varies feature-by-feature. For specifics, see the @WHATWG FAQ: http://tr.im/Po2i | |
|
RDFa
and the DOM
| |
| @cssquirrel: WRT joining the HTMLWG, I think @hixie's writeup makes the most sense: http://bit.ly/3usk4J | |
| HTML 5 in Last Call at @WHATWG. Viva la revolution! (via @gsnedders) #html5 | |
| HTML5: normativity & authoring guides | |
| Might skip writing up my rant on prefix-based indirection & ISSUE-41, as @Hixie nailed it: http://tr.im/prefix_antipattern #html5 #rdfa #w3c | |
| 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 | |
| The Web platform: what it’s not | |
| Microdata, Microformats, and RDF | |
| The Web platform: what it is | |
| @Hixie: hCard has a pattern for that: fn == org and no explicit n specified | |
| DOM Consistency | |
| Saddened by the redundancy of @html5. What was wrong with @WHATWG for commit tweets? | |
| ICANN has .cheezburger? -- @Lachy, in #whatwg | |
| HTML versioning | |
| The Third Dáil | |
| Anglospheric governance for online communities — BarCamp San Diego 2 — Theresa O’Connor | |
| Congrats, @Lachy, and everyone else who helped get the Selectors API published! | |
| Interoperability | |
| Re: Neutrality in "HTML 5 differences from HTML 4" | |
| 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 | |
| Re: Support Existing Content | |
| Re: Support Existing Content | |
| Volume | |
| Data longevity | |
| Roll your own standards body | |