| 00:46 | <zewt> | i seem to spend a depressing amount of time on both lists trying to convince people that interop matters |
| 05:03 | <Hixie> | MikeSmith: please don't change the URL field of WHATWG bugs, our pipeline uses that field for the spec annotations |
| 05:06 | <Hixie> | oh nevermind |
| 05:06 | <Hixie> | i was misreading the bugmail |
| 05:06 | <Hixie> | this is old stuff |
| 05:26 | <MikeSmith> | Hixie: ok, well, I'll avoid changing it from now on anyway |
| 08:45 | <zcorpan> | why doesn't ImageBitmap have width/height attributes? |
| 10:05 | <zcorpan> | TabAtkins: yes, maybe. though an escaped character that doesn't need to be escaped maybe shouldn't be escaped in .source? haven't tested that |
| 10:07 | <zcorpan> | TabAtkins: /\n/ is indeed what we want when doing e.g. eval('var re = /' + new RegExp('\n').source + '/'); (instead of getting a literal newline there which would result in an error) |
| 10:09 | <hsivonen> | It's uncool that Google+ has a different URL space for desktop Firefox and for Firefox for Android |
| 10:10 | <hsivonen> | if you use a desktop URL on mobile, you have to tap through an ad for the G+ Android app and then get redirected to the mobile URL |
| 10:10 | <hsivonen> | if you use a mobile URL on desktop, you don't get redirected to desktop UI and URL |
| 10:37 | <zcorpan> | it seems opera/chrome/firefox didn't bother implementing this part of structured clone: |
| 10:37 | <zcorpan> | If input is an Array object |
| 10:37 | <zcorpan> | Let output be a newly constructed empty Array object whose length is equal to the length of input. |
| 10:37 | <zcorpan> | Note: This means that the length of sparse arrays is preserved. |
| 10:37 | <zcorpan> | http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2170 |
| 12:38 | <hsivonen> | I really need to find time for validator stuff. I'm so behind the times. On Encoding Standard and everything else. |
| 12:49 | <hsivonen> | hmm. what's the content population that was analyzed for https://meaningless-stats.appspot.com/global ? |
| 12:50 | <hsivonen> | ooh. it scrapes the DOM in Chrome rather than the source |
| 12:50 | <hsivonen> | and its users probably have Gmail open all the time |
| 12:51 | <hsivonen> | that would explain the differences between the ARIA numbers between slightlyoff's and Steve's stats |
| 12:55 | <hsivonen> | I wonder how much was lost in minuting regarding Jeff Jaffe's juxtapositioning of "security" and "DRM" http://www.w3.org/2013/03/19-tagmem-minutes.html |
| 13:05 | <slightlyoff> | hsivonen: my stats are super skewed right now. Need many more users before they become statistically significant |
| 13:07 | <slightlyoff> | hsivonen: but yes, generally it should turn up quite a bit more than a surface skim (what most crawlers do) will. |
| 13:14 | hsivonen | notes a job title "innovation architect" |
| 13:15 | hsivonen | wonder if the TAG is envious of Innovation Architecture. Seems cooler than mere Technical Architectur. |
| 13:15 | <annevk> | https://meaningless-stats.appspot.com/about wut? |
| 13:16 | darobin | hsivonen: I think that as Architecture Astronauts they're unlikely to be jealous of anyone |
| 13:18 | <darobin> | those stats look like they're considering SVG content as custom elements |
| 13:20 | <hsivonen> | why does this press release append Google Widevine to a list of analytics services? http://www.brightcove.com/en/company/press/brightcove-launches-native-player-solution-premium-video-apps-apple-ios-google-android-devices |
| 13:23 | <hsivonen> | I wonder if it means that Brightcove's SDK contains a DRM component from Widevine but the person writing the press release doesn't bother to categorize name dropping |
| 13:25 | <hsivonen> | how does one get to blog on a community group blog? |
| 13:25 | <hsivonen> | just join the group and post away? |
| 13:26 | <hsivonen> | or is there some more vetting involved? |
| 13:31 | <hsivonen> | whoa. looks like the WordPress posting UI is available to me, too. |
| 13:31 | <manu-db> | hsivonen: yeah, I think you just join the group - I can create a new post for every group I'm a part of. |
| 13:31 | <slightlyoff> | annevk: that's hipster-ipsum |
| 13:31 | <slightlyoff> | annevk: will fix |
| 13:31 | <hsivonen> | manu-db: ok |
| 13:31 | <annevk> | hehe |
| 13:32 | <manu-db> | hsivonen: Actually, you can create a new post for any group - but you can only put it's status as "pending review" |
| 13:32 | <manu-db> | an admin actually has to come along and approve the post for the group (I'm guessing it has to be one of the group chairs) |
| 13:32 | <slightlyoff> | annevk: http://hipsteripsum.me/ |
| 13:33 | <annevk> | this amuses me |
| 13:34 | <slightlyoff> | annevk: which? |
| 13:34 | <manu-db> | hsivonen: Scratch that - I just published something to the RWW main page and I'm just a member of that group... |
| 13:35 | <annevk> | slightlyoff: your link |
| 13:35 | <slightlyoff> | the "beer me" button mad me LOL the first time I saw it |
| 13:35 | <manu-db> | hsivonen: So, basically you can pwn the blog of any group you join... minor security issue there... :) |
| 13:35 | <slightlyoff> | fucking hipsters = ) |
| 13:42 | <darobin> | manu-db: it's not a security issue, CGs are designed to be open |
| 13:42 | <darobin> | obviously, that does open up the possibly of someone going on a stupidity rampage |
| 13:42 | <darobin> | but to date, that hasn't happened |
| 13:42 | <darobin> | (we have mailing lists for that :) |
| 13:46 | <manu-db> | darobin: things tend not to be a security issue until somebody abuses the hell out of it. I can think of an automated attack that would have one wordpress account sign up, join all the W3C groups and (using the XML RPC API or WebDriver) delete every blog post from every community group. :) |
| 13:47 | <SimonSapin> | darobin: is there some kind of revision history on blogs, in case one is vandalized? (although I don’t expect that to happen) |
| 13:47 | <darobin> | yeah, that might indeed be possible |
| 13:47 | <manu-db> | seems like a simple way to prevent that would be to require publication/deletion of any article to be handled by a chair of the group... |
| 13:47 | <darobin> | I'm pretty sure we have at the very least backups of everything |
| 13:47 | <manu-db> | but I don't care enough about it to make a fuss :) |
| 13:47 | <darobin> | manu-db: if you want process, we have CGs for that |
| 13:47 | <darobin> | seriously, CGs are made to be open and built on trust |
| 13:47 | <manu-db> | CGs? or WGs? |
| 13:47 | <darobin> | WGs (above) |
| 13:48 | <SimonSapin> | I don’t think we should worry too much about preventing this, but being able to *revert* it might be good |
| 13:48 | <darobin> | we have means to revert, I don't know how convenient they are, but they exist |
| 13:48 | <manu-db> | darobin: It's not about trusting folks in the CG... it's about trusting everybody on the Web (which is a bad thing to do) |
| 13:48 | <darobin> | in any case, no problem to report in something like 18months |
| 13:48 | <darobin> | which isn't to say that it won't happen, but I like the openness, even at the cost of risk |
| 13:49 | <darobin> | manu-db: but that's the point: people in the CG should be self-selected from everyone on the Web |
| 13:49 | <darobin> | and yes, that includes bad people |
| 13:49 | <karlcow> | sigh "JJ: example 1: in the press, the Chinese governments has been running an operation to go through the web and attack information resources around the web." — http://www.w3.org/2013/03/19-tagmem-minutes.html |
| 13:49 | <manu-db> | darobin: I'm a security guy at heart - I just see an unnecessary security problem here... that's all. :) |
| 13:49 | <darobin> | openness breed good faith |
| 13:49 | <manu-db> | yeah, just look at 4chan! |
| 13:50 | <manu-db> | and chatroulette |
| 13:50 | <darobin> | manu-db: I know, but same as for wikis |
| 13:50 | <darobin> | chatroulette is full of good faith! |
| 13:50 | <manu-db> | most good wikis are heavily watched for spam (which is a constant) |
| 13:50 | <manu-db> | re: chatroulette ... and furries! |
| 13:50 | <darobin> | I think we actually have tools for spam tracking on the CG system |
| 13:51 | <darobin> | W3C has a fairly heavy antispam infrastructure overall — we get A LOT of it |
| 13:52 | <hsivonen> | fwiw, I didn't see anything that should not have been posted. I was just curious if Dale Cruse has some chair-ish powers and if so with what affiliation |
| 13:52 | <karlcow> | Let me guess. US government never never ever hacks other countries systems? |
| 13:52 | <hsivonen> | karlcow: I'd be more curious to hear people who were there clarify the "security" and "DRM" juxtaposition |
| 13:53 | <MikeSmith> | hsivonen: about the validator I have a couple of big patches in need of landing that I hope you can find time to review soon. One is for the message-filtering feature, and the other is for the show-outline feature. |
| 13:54 | <hsivonen> | MikeSmith: do I have requests in my email that I've failed to address? |
| 13:54 | <karlcow> | hsivonen: the thing which bothers is the use of "consent manufacturing" information for justifying something. |
| 13:55 | <karlcow> | talking about validators I wonder who is in charge of feed-validator these days. |
| 13:56 | <hsivonen> | karlcow: is Sam not in charge? |
| 13:56 | <MikeSmith> | hsivonen: no I've not sent them to you for review yet because I didn't want to bomb them on you if you were already deluged with day-job work, and have you feel like you needed to get to them right away |
| 13:56 | <karlcow> | yeah maybe. |
| 13:57 | <MikeSmith> | hsivonen: but I can send them to you and you can just get to them whenever you have time. They're enhancements and nobody else is specifically waiting on them, so there's no rush to land them. |
| 13:58 | <hsivonen> | MikeSmith: please do send them. I'll try not to be terrible about review schedule this time |
| 13:59 | <MikeSmith> | karlcow: I think it's been a very long time since anybody has been working on the feed validator |
| 13:59 | <MikeSmith> | hsivonen: OK, will do |
| 13:59 | <MikeSmith> | karlcow: same for the main W3C validator. Ville was semi-active on it for a while but went quiet a couple years ago. |
| 14:00 | karlcow | found https://github.com/rubys/feedvalidator/issues/7 |
| 14:00 | <hsivonen> | so what are the top validator issues I should look at? 1) Reviews for MikeSmith, 2) Whine about lack of encoding declaration even if everything is ASCII, 3) Encoding Standard-compliant label handling, 4) ??? |
| 14:01 | <karlcow> | MikeSmith: yes. I have seen some commits yesterday though. |
| 14:01 | <hsivonen> | 4) Make a parser release with the XOM null pointer fix in it |
| 14:01 | <karlcow> | https://dvcs.w3.org/hg/markup-validator/summary |
| 14:07 | <hsivonen> | 5) Make HTML4 validation never activate by default |
| 14:09 | <annevk> | hsivonen: complain about Polyglot Markup |
| 14:09 | <annevk> | </troll> |
| 14:09 | <annevk> | hsivonen: Validate HTTP headers? |
| 14:09 | <annevk> | hsivonen: e.g. people seem to misuse CORS headers |
| 14:10 | <hsivonen> | annevk: good idea. that would be dependent on upgrading the Commons HttpClient |
| 14:10 | <hsivonen> | which is a big patch. I should finish it |
| 14:12 | <hsivonen> | MikeSmith: so I see you improved IANA charset stuff 10 days ago. Any objections to ditching the IANA data and using the Encoding Standard? |
| 14:13 | <hsivonen> | did Hixie already edit the spec accordingly? |
| 14:17 | <hsivonen> | annevk: is your build script for munging encoding.json into the table that's in the spec? |
| 14:18 | <hsivonen> | ...open source and available? |
| 14:18 | <annevk> | hsivonen: I run a script and copy and paste |
| 14:19 | <hsivonen> | annevk: is the script open source and available? |
| 14:19 | <annevk> | hsivonen: the label table is https://github.com/whatwg/encoding/blob/master/tools-label-table.py |
| 14:19 | <annevk> | hsivonen: generating the indexes is https://github.com/whatwg/encoding/blob/master/index.py |
| 14:19 | <MikeSmith> | hsivonen: no objections to ditching IANA and using the Encoding standard. Good riddance. That fix I made was just a band-aid to help some people who had run into problems with local installs due to IANA changing the format of the registry from plain-text to XML. |
| 14:20 | <hsivonen> | annevk: thanks |
| 14:20 | <MikeSmith> | I think that's the biggest priority among the items on your list -- #3 |
| 14:20 | <MikeSmith> | after that, I think we should get around to 5) Make HTML4 validation never activate by default |
| 14:20 | <MikeSmith> | as a priority |
| 14:21 | <hsivonen> | MikeSmith: ok |
| 14:55 | <dglazkov> | good morning, Whatwg! |
| 14:57 | <Steve____> | hixie: re http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Feb/0103.html w3c validator now implements <main> validation as per HTML 5.1 |
| 15:06 | <MikeSmith> | dglazkov: did you see my ping yesterday bout the <decorator> spec? |
| 15:15 | <hsivonen> | annevk: hmm. so "replacement" should not be accepted as a valid encoding name by validators, right? |
| 15:17 | <MikeSmith> | wow Kevin Lynch left Adobe |
| 15:18 | <MikeSmith> | and moved to Apple |
| 15:18 | <MikeSmith> | that's pretty big |
| 15:18 | <hsivonen> | CTO? |
| 15:18 | <MikeSmith> | yeah |
| 15:18 | <MikeSmith> | good one, too |
| 15:18 | <MikeSmith> | moved to a VP position at Apple |
| 15:20 | <hsivonen> | what should the validator say when iso-2022-cn or replacement is used where an encoding label is expected? |
| 15:20 | <hsivonen> | same as in the case of an unrecognized label? |
| 15:21 | <hsivonen> | I guess so |
| 15:29 | <annevk> | hsivonen: only utf-8 really... |
| 15:40 | <zewt> | gah, second time i've been bit by this bizarre behavior in ios webkit where having a click handler at all (even one that does nothing) has side-effects |
| 15:40 | <zewt> | confusing as hell |
| 16:01 | <zewt> | uhh, what the hell? |
| 16:02 | <zewt> | i hope i'm going insane, because it seems like in ios webkit, if you click an element, capturing event listeners on the document aren't fired unless a click event handler exists on the actual element you're clicking |
| 16:02 | <zewt> | it's like it's not firing the event at all unless a click handler exists on the element itself |
| 16:18 | <tobie> | zewt: http://www.quirksmode.org/blog/archives/2010/09/click_event_del.html |
| 16:18 | <MikeSmith> | hsivonen: nice work on the encodings support. I'll push it out to the w3c validator today |
| 16:20 | <zewt> | sure is nice to have hours wasted by multiple horrible incompetent hacks inside apple |
| 16:20 | <zewt> | can't work around it by putting an onclick handler on the element since that has side-effects (which, at the most fundamental design level of events, it shouldn't) |
| 16:20 | <zewt> | so i guess i'll have to work around it using touch events directly (which don't seem to have this problem) |
| 16:23 | <zewt> | (which throws the hypothesis of this being an optimization out the window; touchmove is fired orders of magnitude more often) |
| 16:41 | <darobin> | gotta love ppk |
| 16:41 | <darobin> | 's comparison to Netscape 3 |
| 16:45 | <annevk> | MikeSmith: ah cool, what does the encoding support do? |
| 16:47 | <dglazkov> | MikeSmith: no, I didn't! was it awesome? |
| 16:50 | <dglazkov> | MikeSmith: there's no one working on decorators spec now. If someone volunteers to edit, I'd be happy to help. |
| 17:13 | <MikeSmith> | dglazkov: I wonder if Dominic might be interested? |
| 17:14 | <MikeSmith> | dglazkov: I can talk to him about it after I get back home (I'm in Indiana on a personal visit for another week) |
| 17:15 | <MikeSmith> | annevk: the encoding support currently just restricts the recognized charset encoding values to those that the Encoding standard recognizes (instead of to all that's in the IANA registry) |
| 17:15 | <MikeSmith> | it does not yet emit an error message for documents that use a value other than UTF-8 |
| 17:16 | <MikeSmith> | I don't know if hsivonen intentionally avoided having it do that or if it's something we can plan to add |
| 17:23 | <annevk> | sounds good |
| 17:38 | <MikeSmith> | annevk: btw I'm happy to add fonts to platform.html5.org but dunno which spec to add |
| 17:41 | <annevk> | MikeSmith: I meant for http://platform.html5.org/history/ really |
| 17:41 | <annevk> | MikeSmith: I was trying to figure out when we added them to the platform (I still don't know) |
| 17:42 | <dglazkov> | MikeSmith: which Dominic? |
| 17:50 | <MikeSmith> | GPHemsley: clooney |
| 17:50 | <MikeSmith> | dglazkov: ↑ |
| 17:51 | <MikeSmith> | annevk: ah ok. well, there's a lot of stuff missing still from that page. Like, all of CSS3. I been hoping somebody would take an interest in adding that and other stuff |
| 20:17 | <Hixie> | can anyone work out what is wrong with the example that this bug refers to? https://www.w3.org/Bugs/Public/show_bug.cgi?id=19547 |
| 21:32 | <GPHemsley> | Hixie: Could it be that that person expects "row" to apply to the left, as well? |
| 21:32 | <GPHemsley> | Otherwise, I have no idea |
| 21:32 | <Hixie> | hmmmm, could be |
| 21:33 | <Hixie> | well, spec seems clear that that's an incorrect interpretation, so i guess i'll just leave it as NEEDSINFO |
| 21:50 | <Yuhong> | I found an IE9 info leak for ASLR bypass just by looking at this bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=16757#c10 |