| 00:24 | <Domenic_> | yeah i had to dig around github to find that |
| 00:24 | <Domenic_> | http://webaudio.github.io/web-midi-api/ |
| 03:27 | <crocket> | How do I test if a web browser supports filename* in Content-Disposition? |
| 07:17 | <Domenic_> | tyoshino: thanks so much for your careful review :). I have to go to sleep very soon, but am happy to reply in the morning. |
| 07:29 | <zcorpan> | looks like blink is on a killing spree |
| 08:05 | <abarth|gardener> | zcorpan: hopefully we'll get back to working on those features once we've fixed some of the other problems we've got |
| 08:06 | <zcorpan> | abarth|gardener: which features do you mean? |
| 08:06 | <abarth|gardener> | oh, maybe I misunderstood your comment above |
| 08:08 | <zcorpan> | i was referring to the flow of intent to remove of legacy things |
| 08:08 | <abarth> | ah, yes. I don't think the Attr node stuff is coming back :) |
| 08:09 | <abarth> | Do you know what a notation Node is/was? |
| 08:09 | <abarth> | I read the spec for it, but it didn't really say anything |
| 08:10 | <zcorpan> | it's for representing an xml Notation, which i've forgotten what it's supposed to be used for |
| 08:11 | <zcorpan> | something that goes in the internal subset of the doctype |
| 08:11 | <abarth> | "A notation is a processing instruction that tells the parser what to do with information of a particular format (binary files, image files, sound files, database files etc.) by assigning an external application to process it." |
| 08:11 | <abarth> | <!NOTATION my_format SYSTEM "http://my_website.com/my_application.exe">; |
| 08:11 | <abarth> | oh man |
| 08:11 | <abarth> | that sounds like a terrible idea |
| 08:11 | <abarth> | from http://pic.dhe.ibm.com/infocenter/rsysarch/v11/index.jsp?topic=%2Fcom.ibm.sa.xml.design.doc%2Ftopics%2Ft_Notation.html |
| 08:11 | <abarth> | please download this EXE to view this content o_O |
| 08:13 | <abarth> | zcorpan: I meant that we're removing things like CSS variables that we'll hopefully get back to working on at some point |
| 08:14 | <zcorpan> | abarth: ok, yep |
| 09:25 | <JakeA> | Anyone got stats on the content types <script src> is served with? |
| 09:26 | <JakeA> | Actually, *.js urls would be good enough |
| 10:07 | <annevk> | JakeA: should get someone of that company that employs you to look into that, I hear they're pretty good at it |
| 10:25 | <JakeA> | annevk: hah, actually, it was easier to use http://www.igvita.com/2013/06/20/http-archive-bigquery-web-performance-answers/ |
| 10:26 | <annevk> | JakeA: oh cool |
| 10:26 | <annevk> | I know about http://webdevdata.org/ but that seems to be mostly HTML pages |
| 10:34 | <JakeA> | 96.7% of *.js urls are served with application/x-javascript, text/javascript, or application/javascript |
| 10:34 | <JakeA> | (in the top 3000 sites) |
| 10:37 | <wilhelm_> | And the remaining? No content-type? |
| 10:37 | <wilhelm_> | text/plain? (c: |
| 10:42 | <JakeA> | Raw data https://docs.google.com/spreadsheet/ccc?key=0Am8BnxIvH5DudFV4dG82WEtveGY5RnJUNXdZNVNnSUE&usp=sharing |
| 10:42 | <JakeA> | the next most popular is no type, then text/html |
| 10:45 | <annevk> | JakeA: I rather not require something different for a service worker compared to a normal worker |
| 10:45 | <annevk> | JakeA: but we could I suppose, note that we still don't really have defined content-type parsing in an interoperable way |
| 10:46 | <annevk> | JakeA: e.g. HTTP says "Content-Type: text/html;" is invalid |
| 10:46 | <JakeA> | annevk: Yeah, I'm not set on requiring a content type for serviceworkers, but it's a possibility if there's a perceived security risk |
| 10:47 | <JakeA> | annevk: Oh, didn't know that |
| 11:08 | <annevk> | https://bugs.freedesktop.org/show_bug.cgi?id=41155#c18 o_O |
| 11:09 | <annevk> | If you've been maintaining a MIME type module for 10 years and have still not realized the way MIME types work (including the whole standards process) is broken, the problem is really with you... |
| 11:30 | <darobin> | "I wrote that bit of spec. So consider it a MUST." |
| 11:30 | <darobin> | I'd buy that on a sticker |
| 11:31 | <JakeA> | Haha |
| 11:35 | <charl> | lol, a bit lower down: "I see a disconnect between your insistance on rejecting a MIME type because it's not registered and your opinion that a "SHOULD" can become a "MUST" on a whim." |
| 11:35 | <charl> | indeed |
| 12:00 | <JakeA> | annevk: Btw, had a catchup with Alex, he's been speaking to http people, apparently having http-style matching in a serviceworker cache would be pretty trivial |
| 12:08 | <annevk-cloud> | Cool. Does feel somewhat dangerous as it's high-level, but hopefully it works out |
| 13:30 | <GPHemsley> | annevk, JakeA: I have defined an algorithm for parsing a MIME type in mimesniff: http://mimesniff.spec.whatwg.org/#parsing-a-mime-type |
| 13:32 | <GPHemsley> | It's somewhat hard to test whether it's implemented, though |
| 13:48 | <annevk> | GPHemsley: you can test it with <script type=> maybe to some extent |
| 13:48 | <annevk> | GPHemsley: whether CSS is applied is another good test |
| 13:48 | <annevk> | GPHemsley: might depend on the exact context for CSS loading |
| 13:49 | <GPHemsley> | ah, hmm, interesting ideas |
| 13:49 | <annevk> | oh, and whether CORS does a preflight or not |
| 13:50 | <annevk> | GPHemsley: http://fetch.spec.whatwg.org/#simple-header |
| 13:51 | <GPHemsley> | alright, I'll have a look at it at some point |
| 13:51 | <GPHemsley> | gotta run now, though |
| 14:30 | <espadrine> | Is document.activeElement going to be deprecated? |
| 14:30 | <espadrine> | cf https://www.w3.org/Bugs/Public/show_bug.cgi?id=23475#c16 |
| 14:49 | <annevk> | espadrine: looks like Ian is proposing that to make focus behavior for <dialog> sane |
| 14:49 | <annevk> | espadrine: he asked people to review his proposal and people haven't really been doing that yet I think |
| 15:29 | <zcorpan> | GPHemsley: canPlayType |
| 15:31 | <zcorpan> | GPHemsley: annevk: <script type> doesn't parse as mime type. http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html#support-the-scripting-language |
| 15:33 | <Ms2ger> | Anyone else have gsoc project ideas for the w3c? We've got https://etherpad.mozilla.org/GBHx8UkC9k so far |
| 15:34 | <zcorpan> | dig into presto-testo |
| 15:36 | <jgraham> | It would have to be something with a significant element of coding though; something purely about moving/rewriting tests would probably not be a valid project |
| 16:17 | <annevk-cloud> | zcorpan: same for <style>? |
| 17:01 | <dglazkov> | good morning, Whatwg! |
| 17:16 | <jcgregorio> | good afternoon dglazkov! |
| 17:50 | <guzzlefry> | quick question, is <div>some text</div> valid HTML? |
| 17:50 | <guzzlefry> | Does that text need to be wrapped in anything? |
| 17:51 | <Ms2ger> | Is fine |
| 17:51 | <guzzlefry> | cool, thank you |
| 19:25 | <annevk> | Is it just me or is the new Twitter site really ugly? |
| 19:30 | <jgraham> | Has it only changed if you sign in? |
| 19:39 | <TabAtkins> | annevk: It's just change aversion. |
| 19:40 | <annevk> | TabAtkins: It just doesn't make sense that the navigation buttons are all the way on the left whereas most everything else is in a column in the center |
| 19:40 | <TabAtkins> | There's not all the way on the left for me. On narrower monitors I suppose the width of the thing spans the screen? |
| 20:07 | <zcorpan> | annevk-cloud: it looks like the spec assumes a real mime type in <style type> but i would be surprised if browsers do that |
| 20:08 | <zcorpan> | http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2803 |
| 21:09 | <Hixie> | annevk-cloud: i don't understand https://www.w3.org/Bugs/Public/show_bug.cgi?id=24599 |
| 21:25 | <Hixie> | "Refused to display 'http://www.trustlogo.com/images/cot_bgf0.gif'; in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'." |
| 21:25 | <Hixie> | that's pretty funny. |
| 21:25 | <Hixie> | doesn't give me great faith in the image though |
| 21:41 | <GPHemsley> | Hmm... some interesting behavior with <style type> |
| 21:42 | <GPHemsley> | If there's a semicolon before "text/css" (or a number of other similar variants), it still works |
| 21:42 | <GPHemsley> | http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2804 |
| 21:43 | <GPHemsley> | oh |
| 21:43 | <GPHemsley> | I guess it's just assuming empty MIME type |
| 21:43 | <GPHemsley> | I guess that makes sense |
| 21:50 | <Hixie> | still works where? |
| 21:55 | <GPHemsley> | Hixie: In Firefox, you mean? |
| 21:55 | <Hixie> | ah, in firefox |
| 21:55 | <Hixie> | doesn't in chrome |
| 21:55 | <GPHemsley> | interesting |
| 21:55 | <GPHemsley> | I think Firefox patterns closely to the "parse a MIME type" algorithm |
| 21:56 | <GPHemsley> | in part because I used Firefox primarily when writing it, but in part because it's the sane thing to do |
| 21:58 | <Hixie> | i don't think chrome parses a mime type at all for <style type> |
| 22:41 | <TabAtkins> | Yeah, wouldn't be surprised if we just do a literal text check. |
