| 00:03 | GPHemsley | wonders why nobody but Mozilla updates their Bugzilla installations |
| 00:15 | GPHemsley | gets the sense that Google appends " - WhatWG" to every search result from whatwg.org |
| 00:16 | <GPHemsley> | actually, www.whatwg.org |
| 00:16 | <GPHemsley> | (or else, somewhere the server is serving the crawler a different page than the browser?) |
| 00:18 | <GPHemsley> | it might specifically be only results from the HTML spec |
| 00:18 | <GPHemsley> | (hard to tell) |
| 17:26 | <GPHemsley> | hmm... the WebVTT spec doesn't have the feature of clicking on a definition to find all its uses... :( |
| 17:28 | <GPHemsley> | which makes it difficult for me to determine what happens when the WebVTT parser algorithm fails/aborts |
| 17:35 | GPHemsley | wonders if other specifications define "media elements" that aren't <audio> or <video> |
| 17:41 | <Ms2ger> | svg:video? |
| 18:15 | <GPHemsley> | hmm... IANA registrations in HTML section 16 are inconsistent with how they specify magic numbers |
| 18:16 | <GPHemsley> | including how/whether they specify that a UTF-8 BOM is allowed |
| 18:29 | <ambv> | gsnedders: we should at least offer a migration guide in the docs, I guess. |
| 18:29 | <ambv> | it seems simpletree was in fact used ;-) |
| 19:11 | <GPHemsley> | does anyone know if "text/css" is defined in any modern CSS document? |
| 19:12 | <Ms2ger> | If not CSS2.1, probably now |
| 19:12 | <Ms2ger> | not* |
| 19:14 | <GPHemsley> | such definitions are usually listed in sections entitled "IANA Considerations", of which there are none in CSS2.1 |
| 19:14 | <GPHemsley> | CSSOM mentions "text/css", but I think in a CSS-internal kind of way |
| 19:15 | <Ms2ger> | FWIW, I think "IANA Considerations" may well be a Hixieism |
| 19:17 | <GPHemsley> | not AFAICT |
| 19:17 | <GPHemsley> | I think it actually originates from the IETF |
| 19:18 | <GPHemsley> | BCP 26: http://tools.ietf.org/html/rfc5226 |
| 19:18 | <GPHemsley> | "Guidelines for Writing an IANA Considerations Section in RFCs" |
| 19:19 | <GPHemsley> | And this document is referenced by RFC 6838, which specifies the latest requirements for registering a MIME type: http://tools.ietf.org/html/rfc6838 |
| 19:20 | <GPHemsley> | specifically, in section 3.1: http://tools.ietf.org/html/rfc6838#section-3.1 |
| 19:20 | <Ms2ger> | Ah, interesting |
| 19:20 | <GPHemsley> | given that the text/css registration on file dates from 1998, it seems to me that it might be a good idea to re-register it using the latest RFC |
| 19:20 | <GPHemsley> | on file with IANA, that is |
| 19:21 | <GPHemsley> | specifically, from RFC 2318 |
| 19:21 | <GPHemsley> | probably within css3-syntax or somesuch |
| 19:22 | <GPHemsley> | or css-syntax, I guess it's now called |
| 19:23 | <GPHemsley> | TabAtkins: Thoughts? ^ |
| 19:24 | <Ms2ger> | "XML is great � no doubt! The impact it has had on the Web has been tremendous." |
| 19:24 | <Ms2ger> | Looks like I accidentally ended up in a wormhole that left me in 2001 |
| 19:26 | <GPHemsley> | those wormholes can be fun |
| 19:47 | <Ms2ger> | marcosc: \o/ |
| 20:29 | <GPHemsley> | Hixie: In the "resource selection algorithm", step 9(otherwise)(17) references the "process candidate" step, which is not in the execution chain of 9(otherwise)(17) |
| 20:30 | <Ms2ger> | File a bug, he isn't here :) |
| 20:30 | <GPHemsley> | That is, the "process candidate" step is in step 9(if "mode" is "attribute")(1) |
| 20:30 | <GPHemsley> | meh |
| 20:30 | <GPHemsley> | so formal |
| 20:32 | Ms2ger | imagines a bug in a three-piece suit |
| 20:32 | <GPHemsley> | indeed, that is a very apt visual |
| 20:39 | <GPHemsley> | FTW: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22167 |
| 22:16 | <GPHemsley> | annekv: (Typo?) |
| 22:16 | <GPHemsley> | annevk: Are we moving towards not having "Standard" in the title of our specs? |
| 22:31 | <annevk> | GPHemsley: don't think so, but I'm jetlagged |
| 22:41 | <GPHemsley> | oh, it's zcorpan's fault |
| 22:41 | <GPHemsley> | https://github.com/whatwg/xref/commit/5c4dacc47cfe7748bdf552858b6efa380fef388b |
| 23:51 | <GPHemsley> | Does anyone here happen to know anything about the new (March 29, 2013) MIME type "application/font-sfnt" beyond what is in the IANA registration? |
| 23:52 | <GPHemsley> | (or perhaps have access to the ISO/IEC 14496-22 "Open Font Format" specification |
| 23:52 | <GPHemsley> | ?) |
| 23:54 | <GPHemsley> | Oh, nevermind; it's a Publicly Available Standard |