| 00:33 | <zewt> | rniwa: i just wish that if Japanese authors are going to dig in their heels and keep using SJIS (or EUC-JP or ISO-2022-JP), they'd at least get their charset declarations correct |
| 00:33 | <rniwa> | zewt: I think so. |
| 00:34 | <rniwa> | zewt: although Shift_JIS is never really used |
| 00:34 | <zewt> | instead of the current nonsense where japanese pages very often end up broken on all non-japanese systems |
| 00:34 | <rniwa> | zewt: what we call Shift_JIS is almost always Code Page 932 |
| 00:35 | <zewt> | windows's "extensions"--yet another reason to use utf-8 :P |
| 00:36 | <rniwa> | zewt: the problem is that utf-8 didn't get right either |
| 00:36 | <zewt> | what's frustrating is how the current situation leads to pages working for their authors, and most of their viewers (eg. users in japan see japanese pages OK), but are broken for the rest of the world |
| 00:36 | <rniwa> | zewt: a lot of japanese/chinese scholars are really upset about how UCS-2 assignes the same code point for completely different characters |
| 00:36 | <rniwa> | zewt: right. |
| 00:37 | <rniwa> | zewt: on the other hand, it's pretty insulting to be imposed upon an encoding that can't encode your character properly |
| 00:37 | <zewt> | eh, utf-8 round-trips other encodings, so i don't know how there could be anything sjis (etc) could represent that utf-8 can not |
| 00:37 | <rniwa> | zewt: how would you feel if your bank switched to start using utf-8 text encoding so that it starts using wrong characters for your names? |
| 00:38 | <zewt> | i'm not convinced that's possible :) |
| 00:39 | <zewt> | (with the caveat that you have to get your lang declarations right, to avoid rendering eg. japanese characters with chinese fonts) |
| 00:39 | <gavinc> | rniwa: Eh? UTF-8 got it wrong? You mean Unicode got it wrong? as another encoding for Unicode won't have different characters |
| 00:40 | <zewt> | if there's any character in SJIS that doesn't have a direct round-trip equivalent in utf-8, that'd be a major unicode bug, afaik |
| 00:40 | <rniwa> | gavinc: I meant unicode |
| 00:41 | <zewt> | if there's any character that isn't displayed identically in utf-8 (with the correct language selected) as in sjis, i'd be interested in knowing what it is, and why it's different |
| 00:41 | <gavinc> | so there exist japanese characters for which there is no unicode code point? |
| 00:41 | <gavinc> | Kanji yes? |
| 00:41 | <rniwa> | gavinc: well, they probably have all code points but the problem is that it's shared with chinese characters |
| 00:41 | <rniwa> | gavinc: yes |
| 00:41 | <rniwa> | zewt: even shift_jis doesn't contain all characters we need. |
| 00:42 | <zewt> | rniwa: sharing with chinese characters is okay, again you just have to make sure the browser is picking the right language |
| 00:42 | <gavinc> | rniwa: Ah yes, the character is the same but two cultures define different meanings |
| 00:42 | <zewt> | gavinc: it's the weird clash between "character" and "glyph" |
| 00:42 | <rniwa> | gavinc: they're different chracters |
| 00:42 | <rniwa> | gavinc: do you suppose greek alpha is identical to latin a because they share the same origin? |
| 00:42 | <zewt> | rniwa: again, i'd like an example |
| 00:43 | <gavinc> | sorry, glyph |
| 00:43 | <gavinc> | meant glyph! |
| 00:43 | <rniwa> | anyways, i'm not in a position to discuss about this :) |
| 00:43 | gavinc | puts on encoding unicode brain |
| 00:43 | <zewt> | rniwa: i think you're wrong :) |
| 00:43 | <rniwa> | there are much more qualified people to talk about it |
| 00:43 | <gavinc> | Yeah, pulling bits of it out my memory |
| 00:43 | <gavinc> | Greek has in fact some of the same political issues in unicode :( |
| 00:44 | <zewt> | if you take sjis/euc-jp/iso-2022-jp text, convert to utf-8 and set lang=jp, it should always be rendered the same; if there are examples where this isn't the case, then I'd really like to know what they are |
| 00:44 | <gavinc> | Ah! Wikipedia will help you zewt http://en.wikipedia.org/wiki/Han_unification ;) |
| 00:44 | <zewt> | gavinc: i know what han unification is; my point is that lang is the disambiguator |
| 00:46 | <rniwa> | zewt: http://www.shuiren.org/chuden/teach/code/main8.htm#AdvantageDisadvantage |
| 00:48 | <rniwa> | the problem with unicode is that they assigned characters with different shapes, lines, etc... to the same code point |
| 00:48 | <rniwa> | even though they're not just aesthetic issues |
| 00:49 | <rniwa> | e.g. you can't interchange them in handwriting because they're different characters |
| 00:50 | <zewt> | rniwa: but the language attribute of the content tells it which glyph to use. |
| 00:50 | <rniwa> | zewt: that would mean that you can't mix chinese names and japanese names in the same context |
| 00:50 | <rniwa> | zewt: you have to specify the language to make any sense |
| 00:51 | <zewt> | sure you can: <span lang="jp">text</span> <span lang="zh">text2</span> |
| 00:51 | <zewt> | and besides, you can't do that *at all* with legacy encodings |
| 00:52 | <zewt> | http://zewt.org/~glenn/encoding%20utf-8.html http://zewt.org/~glenn/encoding%20sjis.html http://zewt.org/~glenn/encoding%20big5.html works fine |
| 00:52 | <zewt> | (used zh-TW since the glyph difference is more pronounced) |
| 00:52 | <AryehGregor> | Could we define non-BMP characters that mirror all the BMP CJK glyphs but with the language predetermined? |
| 00:52 | <AryehGregor> | That would probably just confuse everyone even more . . . |
| 00:53 | <rniwa> | zewt: apparently chrome doesn't support it :( it looks all the same |
| 00:53 | rniwa | is annoyed |
| 00:53 | <AryehGregor> | Likewise. |
| 00:53 | <zewt> | that'd be a massive chrome bug, unless I'm specifying something wrong |
| 00:53 | <zewt> | (or both could be true) |
| 00:54 | <zewt> | works fine in IE *8* |
| 00:54 | <rniwa> | zewt: firefox doesn't get it right either |
| 00:54 | <zewt> | (and FF8, which I tested with first) |
| 00:54 | <gavinc> | is there an img reference too? |
| 00:54 | <rniwa> | zewt: this might be a bug on Mac... |
| 00:54 | <zewt> | rniwa: you may not have both Japanese and Chinese fonts installed, in which case it'll probably fall back to the one you do have |
| 00:54 | <zewt> | however, i can confirm it's not working for me in Chrome |
| 00:55 | <zewt> | (windows, with both font sets installed) |
| 00:55 | <rniwa> | zewt: I have both Japanese / Chinese IMEs installed so that's hard to believe |
| 00:55 | <gavinc> | zewt: screen shot of what it -should- look like? |
| 00:55 | <zewt> | one sec |
| 00:55 | <rniwa> | gavinc: the box inside the upper box should be on the different sides |
| 00:56 | <rniwa> | gavinc: see http://www.shuiren.org/chuden/teach/code/main8.htm#AdvantageDisadvantage |
| 00:56 | <zewt> | http://zewt.org/~glenn/encoding%20expected.png |
| 00:56 | <rniwa> | gavinc: in JIS, it should be on the right. |
| 00:56 | <rniwa> | gavinc: in GB, it should be on the left. |
| 00:56 | <rniwa> | gavinc: in BIG5 it should be on the right but the bottom part should be simplified |
| 00:57 | <gavinc> | heh, so anyone else have the box in the top box on the LEFT? and not even on the right at all? |
| 00:57 | <rniwa> | gavinc: need traditional chinese font. |
| 00:57 | <rniwa> | gavinc: and I don't think zewt specified it to be traditional |
| 00:57 | <rniwa> | zewt: he probably used simplified chinese |
| 00:58 | <zewt> | i used zh-TW, because it's easier to distinguish from the JP glyph |
| 00:58 | <rniwa> | zewt, gavinc: see, the problem is that it's so hard to use this thing. |
| 00:58 | <zewt> | rniwa: oddly, I see the JP glyph on all three on the shuiren.org page |
| 00:58 | <rniwa> | zewt, gavinc: if we had a different code point, it just works fine. |
| 00:58 | <gavinc> | rniwa: yeah, I've been convinced. |
| 00:58 | <rniwa> | zewt: hehe, it's probably a browser bug |
| 00:59 | <rniwa> | I feel like this is a simialr issue to bidi |
| 00:59 | <zewt> | rniwa: "see" but you're changing the argument :) these are browser issues (bad ones, to be sure; this should be working reliably years and years ago), but it's not unicode's fault |
| 00:59 | <rniwa> | it's possible in theory but impossible in practice |
| 00:59 | <zewt> | uh, no, not at all |
| 01:00 | <rniwa> | zewt: the fact you're the only one seeing the correct glyph suggests to me that it's not working, is it? |
| 01:00 | <zewt> | for authors there's exactly one step: stick lang=ja (or zh-TW or zh-CN) around your content (probably on <body>) |
| 01:00 | <rniwa> | zewt: but the problem is that it doesn't work in many cases. |
| 01:00 | <zewt> | so it should be fixed; it's always worked for me |
| 01:01 | <rniwa> | zewt: what's the point of a spec. if it doesn't work on most implementations |
| 01:01 | <zewt> | works fine in FF8 and IE |
| 01:01 | <gavinc> | On Windows |
| 01:01 | <rniwa> | zewt: maybe this is an issue with mac then |
| 01:01 | <gavinc> | FF8 does not look right on Linux |
| 01:01 | <zewt> | and Opera |
| 01:03 | <zewt> | hmm, Chrome does render the suiren.org page correctly |
| 01:03 | <rniwa> | zewt, gavinc: similarly, we have the opposite problem as pointed on http://www.shuiren.org/chuden/teach/code/main8.htm#AdvantageDisadvantage |
| 01:03 | <zewt> | i bet that's because of the separate font specifier, though |
| 01:03 | <zewt> | rniwa: executive summary would be helpful; it would take me several minutes to read this :) |
| 01:03 | <rniwa> | gavinc, zewt: 為 and 爲 are just new/old glyphs for the same character but they're assigned to different code points |
| 01:04 | <gavinc> | 骨 does look right on shuiren btw |
| 01:04 | <zewt> | <- can struggle through gradeschool spoken JP, but reading it isn't going to happen |
| 01:04 | <rniwa> | I'll leave the rest to unicode experts from tokyo |
| 01:04 | <rniwa> | but i'm bitter about UCS-2 in general. |
| 01:05 | <zewt> | chrome getting this wrong makes me upset; it's the sort of bug that'll set unicode-in-CJK-countries back by years |
| 01:06 | <rniwa> | zewt: yeah, I should probably file a bug about this. |
| 01:06 | <gavinc> | zewt: Chrome shows the WRONG thing for me on shuiren, where FF does the right thing |
| 01:06 | <rniwa> | it's super annoying |
| 01:07 | <zewt> | rniwa: please do (I would, but I expect a webkit report will get more attention) |
| 01:07 | <zewt> | also I wonder if this is a Chrome problem or a WebKit problem |
| 01:07 | <rniwa> | zewt: are you on windows? |
| 01:07 | <zewt> | yeah |
| 01:07 | <rniwa> | zewt: because it works perfectly fine on mac. |
| 01:07 | <zewt> | in chrome or safari? |
| 01:07 | <rniwa> | zewt: both |
| 01:08 | <rniwa> | zewt: it'll be super helpful if you could check safari as well |
| 01:08 | <zewt> | will need to fire up my VM with safari in it; one sec |
| 01:16 | <zewt> | eh, nothing is working right in my VM, not even the big5-encoded one |
| 01:16 | <zewt> | they're all showing the JP glyph |
| 01:16 | <zewt> | (XP, same on every browser I've tried) |
| 01:16 | <rniwa> | zewt: :( |
| 01:17 | <rniwa> | zewt: sounds like you don't have Eastern Asian language support on your Windows? |
| 01:17 | <zewt> | it looks like XP installs all CJK languages as a unit ("install files for east asian languages"), so installed fonts should be a problem |
| 01:17 | <zewt> | rniwa: if they weren't installed then the JP glyph wouldn't work either |
| 01:17 | <rniwa> | zewt: oh they all defaults to JP font? |
| 01:18 | <zewt> | yeah, even big5 shows the top one in http://zewt.org/~glenn/encoding%20expected.png |
| 01:18 | <zewt> | the fonts are there; i can see one of the ZH ones if I select the NSimSun font in Notepad |
| 01:19 | <zewt> | i guess i'll install safari natively instead of in this old XP VM |
| 01:19 | <zewt> | strange, though |
| 01:20 | <zewt> | (and so nobody's confused, this is unrelated--the problem happens with the legacy encodings, too) |
| 01:21 | <zewt> | this is fascinating: the Safari installer gave me the option to not auto-updated in XP, but that option seems to be mysteriously not present in 7 |
| 01:22 | <zewt> | WHAT THE HELL |
| 01:22 | <zewt> | okay safari is on my software blacklist (it just played loud music when it launched) |
| 01:23 | <zewt> | that is not okay |
| 01:25 | <zewt> | rniwa: safari is showing the JP glyph in all cases, as far as I can see |
| 01:26 | <zewt> | including big5 |
| 01:26 | <rniwa> | zewt: okay, it's probably webkit issue then |
| 01:26 | <zewt> | rniwa: does big5 look wrong to you, too? |
| 01:27 | <zewt> | that is, http://zewt.org/~glenn/encoding%20big5.html, which shows the zh-TW glyph for me |
| 01:27 | <zewt> | (in FF) |
| 01:34 | <rniwa> | zewt: it doesn't properly on mac either |
| 01:34 | <rniwa> | odd. it appears to use simplified font on windows :( |
| 01:35 | <zewt> | looks to use MS Gothic always for me |
| 01:35 | <rniwa> | zewt: filed https://bugs.webkit.org/show_bug.cgi?id=73507 |
| 01:37 | <zewt> | rniwa: fwiw, you can probably remove the lang attribute there |
| 01:37 | <zewt> | since it seems to happen without it |
| 01:39 | <rniwa> | zewt: http://www.shuiren.org/chuden/teach/code/main8.htm renders correctly on Chrome on Windows for me |
| 01:40 | <zewt> | rniwa: it seems to have some xhtml-related problem for me |
| 01:40 | <zewt> | if I s/xml:lang/lang/, it works |
| 01:41 | <zewt> | er, no, that was in FF |
| 01:41 | <zewt> | (overjuggling) |
| 01:42 | <rniwa> | zewt: ? |
| 01:42 | <zewt> | (it renders wrong in FF8 for me, because of something to do with xhtml) |
| 01:43 | <zewt> | rniwa: it renders correctly in Chrome only because of the font-family style |
| 01:43 | <zewt> | <td><span xml:lang="zh-cn" style="font-size: 140%; font-family: SimSun">œ</span></td> |
| 01:43 | <rniwa> | :( |
| 01:43 | <zewt> | it's not actually using the language there |
| 01:43 | <rniwa> | that's quite stupid |
| 01:44 | <zewt> | so i'm guessing it shares whatever safari's problem is with lang |
| 01:47 | <zewt> | rniwa: do you at least agree that, if browsers iron this stuff out (which should have happened long ago), language tagging + UTF-8 is a workable approach for authors to deal with han unification? |
| 01:47 | <zewt> | (that is, all you do is add lang=jp to <body>) |
| 01:47 | <zewt> | (for the vast majority of cases) |
| 01:48 | <rniwa> | zewt: not really. I still think it's broken in many ways. but I'd agree that we should fix it. |
| 01:48 | <zewt> | why? |
| 01:48 | <rniwa> | zewt: so that we can at least get the functionality UCS-2 provides. |
| 01:48 | <rniwa> | zewt: I've already pointed out the code point issues. |
| 01:49 | <zewt> | which language tagging fixes (and that's how CJK unicode rendering was intended to work from the beginning) |
| 01:50 | <rniwa> | zewt: not really |
| 01:50 | <zewt> | ... |
| 01:50 | <rniwa> | zewt: some characters are assinged to two different code points even though they're the same character |
| 01:50 | <rniwa> | of different styles |
| 01:50 | <zewt> | so? |
| 01:50 | <rniwa> | zewt: that would mean that changing fonts don't work |
| 01:50 | <rniwa> | zewt: you need to edit the html to use different styles of characters |
| 01:50 | <rniwa> | etc... |
| 01:51 | <zewt> | there are multiple codepoints for "A" (full-width latin); it's a little weird but not a real problem |
| 01:53 | <zewt> | (when I see it I wish people wouldn't use it, but it's not nearly annoying enough to not use UTF-8 for) |
| 02:18 | <roc> | I assume you guys know about UVS |
| 02:22 | <zewt> | (not off-hand) |
| 02:24 | <roc> | a Unicode feature that uses supplemental codepoints to encode glyph variations |
| 02:25 | <roc> | I believe it's partly intended to address the complaints about Han unification |
| 02:26 | <roc> | language markup works too, although it's confusing because language often affects font choice as well as shaping |
| 02:26 | <zewt> | well, shaping is just part of the font in most systems |
| 02:26 | <roc> | E.g. your language attributes might fix the problem by causing a suitable font to be selected |
| 02:27 | <roc> | but if you explicitly set the "wrong" font (or the user does, maybe), you'd lose |
| 02:27 | <zewt> | japanese fonts generally don't have chinese glyphs in them to begin with (putting aside that ttf fonts probably have no way to express that; don't know) |
| 02:28 | <roc> | right, so if someone forced use of a Japanese font, then your Chinese text won't display properly |
| 02:28 | <roc> | Opentype fonts can use language-specific shaping tables, and Gecko supports that, but I don't know how many fonts do |
| 02:28 | <zewt> | that could be fixed in time, of course, though i suspect mixing japanese and chinese glyphs is too much of an edge case for the cost |
| 02:28 | <roc> | so a font could support both Japanese and Chinese correctly |
| 02:30 | <zewt> | but this isn't actually a problem with the lang markup approach (eg. I doubt encoding it with Unicode features would change it) |
| 02:30 | <zewt> | it's just limitations of the fonts and font engines |
| 02:31 | <roc> | true |
| 02:59 | <dglazkov> | wg what? |
| 03:02 | <divya> | wow thg |
| 03:02 | divya | fails at anagrams |
| 04:02 | <dbaron> | roc, you mean IVS? (Ideographic Variation Sequences) |
| 04:13 | <roc> | yes |
| 06:59 | <hsivonen> | where do I see the system requirements for Opera Next? |
| 07:44 | <hsivonen> | categorizing elliptical arcs and elliptical curves as graphics or crypto could be a CAPTCHA question |
| 07:52 | <annevk> | hsivonen: the same as http://www.opera.com/browser/download/requirements/ prolly |
| 07:52 | <annevk> | hsivonen: not sure if we have that stated somewhere |
| 07:57 | <annevk> | I don't get the XPath thread, why don't the proponents simply write a spec and get it implemented? |
| 07:57 | <zcorpan> | so there's discussion about incremental XHR, but no discussion about incremental HTML/XML parsing APIs |
| 07:58 | <annevk> | Is that even needed though? |
| 08:00 | <annevk> | whatwg.org slow? |
| 08:01 | <zcorpan> | consider a page that inserts new content fetched from xhr |
| 08:01 | <zcorpan> | currently people wait for everything to download, and then assign innerHTML or so |
| 08:02 | <zcorpan> | with chunked XHR, they still need to wait for everything before assigning to innerHTML |
| 08:02 | <annevk> | so some new kind of document.write() API? |
| 08:03 | <zcorpan> | yeah |
| 08:03 | <annevk> | o_O |
| 08:03 | <zcorpan> | element.write() :) |
| 08:07 | <hsivonen> | annevk: ok. Re: requirements |
| 08:08 | <hsivonen> | annevk: Re: XPath: it's not just an issue of the proponents getting it implemented. patches might not be welcome if they are perceived as a slippery slope to having to get on the XPath 2 maintenance treadmill |
| 08:09 | <hsivonen> | annevk: IIRC, some WebKit/Qt hacker tried to contrib XPath 2 (or was it XSLT 2) support, but the wider WebKit stakeholders wisely rejected it |
| 08:09 | <annevk> | Okay, but e.g. EXSLT has been implemented by some browsers... |
| 08:09 | <annevk> | From what I remember anyway, it's been a while |
| 08:10 | <hsivonen> | annevk: yeah, at the time when Mozilla accepted patches for pretty much anything than looked stardardish |
| 08:12 | <hsivonen> | fortunately for math, MathML got in the codebase, too, during that era |
| 08:22 | <annevk> | hsivonen: I asked and our system requirements are so low that nobody has really cared to put that amount of detail into experimental releases |
| 08:22 | <annevk> | hsivonen: runs on => W2K and we only just ditched W9x support if that means anything to you |
| 08:22 | annevk | has a fast Mac, doesn't care |
| 08:26 | <annevk> | 3PM ET == 9PM CET? |
| 08:26 | <annevk> | MikeSmith, ^^ |
| 08:26 | annevk | might not make that |
| 08:27 | <MikeSmith> | annevk: no problem |
| 08:27 | <MikeSmith> | that was the only time it seems we could get everybody on |
| 08:27 | <annevk> | yeah, have fun :) |
| 08:27 | <MikeSmith> | well, not everybody, obviously |
| 08:27 | <MikeSmith> | I honestly don't know what's left to say about that, anyway |
| 08:28 | <MikeSmith> | I thought my last message in the thread made it all pretty clear |
| 08:28 | <annevk> | some people like to talk to talk |
| 08:28 | <annevk> | or something |
| 08:28 | <MikeSmith> | yeah |
| 08:28 | <MikeSmith> | for three years |
| 08:28 | <MikeSmith> | saying the same things without actually doing much of anything concrete |
| 08:29 | <MikeSmith> | anyway, I need to step out for food and drink |
| 08:30 | <MikeSmith> | long evening of late-night telcons to look forward to |
| 08:31 | <annevk> | go to the fancy sushi place :) |
| 08:33 | <jgraham> | annevk: Yeah, someone should write a spec for teh XPath thing. I can't really do it though as either bratell or Katie would kill me. Maybe João should do it. |
| 08:37 | <annevk> | zcorpan: fwiw, until queue a task moves to DOM4, it's the wrong place to spec APIs around it imo |
| 08:38 | <annevk> | jgraham: you should write notifications already :p |
| 08:38 | <jgraham> | annevk: I know :) |
| 08:38 | <annevk> | jgraham: why would Katie kill you though? you'd do it in your free time? |
| 08:38 | <annevk> | jgraham: didn't realize the Xpath-love was so strong with you :p |
| 08:39 | <jgraham> | Well yeah, the two options would be use work time -> death by bratell, use free time -> death by Katie. Both options end in death. I don't like XPath *that* much |
| 08:39 | <annevk> | it would be nice though if there finally was a spec that said how //text() works with DOM-based environments |
| 08:40 | <zcorpan> | annevk: moved the bug |
| 08:41 | <annevk> | thanks |
| 08:41 | <zcorpan> | jgraham: what happens if you use half the time on work time and the other half on free time? |
| 08:42 | <annevk> | coma |
| 08:43 | <jgraham> | Isn't that how you unleash the special 2 v 1 mode that leads to quick, but painful, death? |
| 08:43 | <jgraham> | *unlock |
| 08:44 | <jgraham> | Anyway, seriously, not going to happen at the moment |
| 08:49 | <rniwa> | annevk: so about setAttributeNS / setAttribute difference, |
| 08:49 | <rniwa> | annevk: the problem is that setAttributeNS does more than just setting the value |
| 08:49 | <rniwa> | annevk: it also modifies the namespace prefix |
| 08:50 | <rniwa> | annevk: so I'd have to special-case that :( |
| 08:50 | <zcorpan> | modifying prefix seems annoying |
| 08:51 | <annevk> | rniwa: ideally we remove that |
| 08:51 | <annevk> | rniwa: it currently does not do that in WebKit or Opera |
| 08:51 | <annevk> | rniwa: Gecko does do it, but then mutation observers does not take it into account |
| 08:51 | <rniwa> | annevk: how about IE? |
| 08:52 | <annevk> | I cannot test IE :( |
| 08:52 | <rniwa> | i didn't even know about namespace prefix stuff 'til I read the spec |
| 08:52 | <rniwa> | it's super annoying |
| 08:52 | <annevk> | if you paste http://lists.w3.org/Archives/Public/www-dom/2011OctDec/0214.html in the live dom viewer you can find out what IE does |
| 08:52 | rniwa | boots his windows machine |
| 08:52 | <annevk> | rniwa: say so in the www-dom thread! |
| 08:53 | <annevk> | rniwa: if everyone but sicking finds it annoying, we're just going to not do it |
| 08:53 | <annevk> | as it's a super edge case not worth caring much about |
| 08:53 | <rniwa> | annevk: i'm waiting 'til my spec goes on public-webapps |
| 08:54 | <rniwa> | I highly doubt that any author understands this behavior |
| 08:54 | <rniwa> | but then.. very few people use setAttributeNS anyway |
| 08:54 | <sicking> | annevk: finds what annoying? |
| 08:54 | <rniwa> | so maybe those people get annoyed ? |
| 08:54 | <sicking> | annevk: i find prefixes annoying in all forms :) |
| 08:54 | <annevk> | sicking: setAttributeNS doing more than setting the value |
| 08:54 | <sicking> | node prefixes that is |
| 08:54 | <rniwa> | sicking: namespace prefix changes in setAttributeNS |
| 08:55 | <sicking> | annevk: oh, I don't believe I said anything on that topic at all |
| 08:55 | <rniwa> | sicking: it makes undo manager / DOM4 spec more complicated :( |
| 08:55 | <sicking> | annevk: other than that i'd like to get rid of namespaced attributes |
| 08:55 | <annevk> | am I confusing sicking and bz again |
| 08:55 | <annevk> | :( |
| 08:55 | <annevk> | sorry sicking |
| 08:55 | <sicking> | annevk: bz has a much nicer beard than me |
| 08:56 | <annevk> | heh, I'd love to meet him one day |
| 08:56 | <sicking> | i thought you met him in MV once |
| 08:56 | <sicking> | but maybe you weren't there |
| 08:56 | <annevk> | ooh maybe a long time ago |
| 08:57 | <rniwa> | annevk: as I've suspected, IE supports it |
| 08:57 | <rniwa> | annevk: live DOM viewer shows e:a="b" |
| 08:57 | <annevk> | kk |
| 08:59 | <annevk> | I think http://lists.w3.org/Archives/Public/www-dom/2011OctDec/0222.html is a very compelling argument though and therefore I think I will just remove it |
| 08:59 | <annevk> | and I'll file a bug on Gecko to see if they are willing to match the spec |
| 09:02 | <rniwa> | alright |
| 09:02 | <rniwa> | my spec just got real :D |
| 09:02 | <rniwa> | all pending issues have been resolved |
| 09:03 | <annevk> | you mean the first 80%? |
| 09:03 | <annevk> | the remaining 80% takes half a decade :p |
| 09:03 | <rniwa> | annevk: basically, I don't have anything to add at this point except clarifying details (which is going to take another 2 years to finish) |
| 09:03 | <rniwa> | annevk: yeah, the first 80%. |
| 09:03 | <rniwa> | annevk: the remaining 20% will take 2 years + 10 years for writing tests |
| 09:04 | <rniwa> | well at least in my optimistic estimate |
| 09:04 | <annevk> | congratulations though, still pretty sweet :) |
| 09:04 | <rniwa> | annevk: yeah, i'm super excited about it |
| 09:04 | rniwa | needs to update the date and push it to rniwa.com |
| 09:05 | <jgraham> | You probably also need to get implementations ;) |
| 09:05 | <rniwa> | jgraham: yeah... |
| 09:05 | <rniwa> | jgraham: I was hoping to get an intern do it |
| 09:05 | <rniwa> | jgraham: but apparently people want it before next summer |
| 09:06 | <rniwa> | so i guess i'll do it in Q1 |
| 09:08 | <rniwa> | jgraham: I hear sicking had an intern start implementing it for gecko |
| 09:08 | <sicking> | rniwa: yeah, he got far but didn't finish it. Don't know when we'll be able to do the remaining parts :( |
| 09:09 | <rniwa> | sicking: sounds like he has a full-time offer? |
| 09:09 | <sicking> | rniwa: oh, there's one part that i notcied that you're missing |
| 09:09 | <rniwa> | sicking: ? |
| 09:09 | <sicking> | rniwa: you only have info on how to revert changes |
| 09:09 | <sicking> | rniwa: not how to reapply them |
| 09:09 | <rniwa> | sicking: right |
| 09:09 | <rniwa> | sicking: oh, so reapply will be reverts of reverts |
| 09:10 | <sicking> | rniwa: hmm... is that always true |
| 09:10 | <rniwa> | sicking: I think so. |
| 09:10 | <sicking> | could be |
| 09:11 | <rniwa> | sicking: if there are cases where that's not the case, then let me know |
| 09:11 | <rniwa> | sicking: but I haven't been able to come up with a case yet. |
| 09:11 | <sicking> | still needs to be defined. But if it's that simple i might have missed it. |
| 09:11 | <rniwa> | sicking: so in http://rniwa.com/editing/undomanager.html#automatic-dom-transactions |
| 09:12 | <rniwa> | sicking: I say "When an automatic DOM transaction is reapplied, the user agent must revert DOM changes made inside the undo scope of the the UndoManager while unapplying the transation." |
| 09:12 | <rniwa> | sicking: whereas for unapply, I said "When an automatic DOM transaction is unapplied, the user agent must revert DOM changes made inside the undo scope of the the UndoManager while *applying* the transation" |
| 09:15 | <hsivonen> | What's the best workflow for going from .ttf to a subsetted .woff these days in a way that doesn't break ligatures and contextual alternative glyphs? |
| 09:15 | <hsivonen> | is it Philip`'s subsetter plus a separate .ttf to .woff converter? |
| 09:15 | <rniwa> | sicking: does that make sense? or should I clarify more? |
| 09:19 | <sicking> | rniwa: that means that the implementation must continuously update it's automatic transaction though, is that good? |
| 09:19 | <sicking> | rniwa: currently in gecko we just store information when the transaction is created, and that information remains constant as we apply/unapply |
| 09:20 | <rniwa> | !? |
| 09:20 | <rniwa> | sicking: right. |
| 09:21 | <rniwa> | sicking: I don't really follow your continuously updating part. |
| 09:21 | <sicking> | rniwa: say that you create an automatic transaction which inserts a node |
| 09:21 | <rniwa> | sicking: I'm not saying that you should implement each mutation inside undo/redo as an automatic transaction |
| 09:22 | <sicking> | rniwa: a transaction-object is created which stores a reference to that node (and maybe other information) |
| 09:22 | <sicking> | rniwa: say that the page the removes the node from the DOM |
| 09:22 | <sicking> | rniwa: and then calls unapply |
| 09:22 | <sicking> | rniwa: at this point unapply can't remove the node since it no longer has a parent |
| 09:22 | <rniwa> | sicking: right |
| 09:22 | <sicking> | rniwa: in other words, unapply doesn't do anything |
| 09:22 | <rniwa> | sicking: sure. |
| 09:23 | <rniwa> | sicking: so it didn't make any DOM changes |
| 09:23 | <rniwa> | sicking: if you do reapply at that point, reapply doesn't do anything |
| 09:23 | <sicking> | rniwa: per spec, that means that the transaction has to update it's internal information to now represent nothing |
| 09:23 | <rniwa> | hm.... |
| 09:23 | <rniwa> | sicking: would that be an issue? |
| 09:23 | <sicking> | rniwa: in other words, the transaction doesn't hold constant data |
| 09:23 | <sicking> | rniwa: seems harder implementation wise. To no benefit as far as i can see |
| 09:23 | <hsivonen> | Philip`: do you happen to know of an up-to-date .ttf to .woff converter that runs on Linux? |
| 09:24 | <rniwa> | hm... |
| 09:24 | <sicking> | rniwa: in fact, it's probably good if the implementation holds the data so that it can try to re-insert the node if you reapply |
| 09:24 | <rniwa> | sicking: ok, I think you're right. |
| 09:24 | <rniwa> | sicking: i guess I'll just change the spec then |
| 09:25 | <sicking> | rniwa: thanks. I do think that'll make implementation a good bit simpler |
| 09:25 | <zcorpan> | hsivonen: is fontsquirrel broken? |
| 09:27 | <hsivonen> | zcorpan: do you mean this: http://www.fontsquirrel.com/fontface/generator |
| 09:27 | <hsivonen> | zcorpan: it's not something I can automate on Linux |
| 09:27 | <hsivonen> | zcorpan: is that the best that's available? |
| 09:27 | <zcorpan> | no idea |
| 09:27 | <hsivonen> | (Flash-based file upload. boo.) |
| 09:28 | <zcorpan> | ugh |
| 09:31 | <rniwa> | sicking: yeah, I guess I wasn't thinking through |
| 09:31 | rniwa | replies some random email about Arabizi |
| 09:32 | <rniwa> | I don't quite understand what they're trying to propose though |
| 09:34 | <annevk> | should the DOM specification have these kind of anal definitions: |
| 09:35 | <annevk> | X attribute: An attribute whose local name is X and namespace and namespace prefix are null |
| 09:35 | <annevk> | has an X attribute: An element that has an X attribute in its attribute list |
| 09:36 | <annevk> | s/has an X attribute/has an attribute/ |
| 09:39 | <annevk> | I'm just going to go with it |
| 09:39 | <annevk> | someone can tell me otherwise later |
| 09:41 | <rniwa> | annevk: that sounds fine |
| 09:41 | <rniwa> | annevk: although "has an X attribute: An element that has an X attribute in its attribute list" sounds like a recursive definition |
| 09:48 | <rniwa> | sicking: I suppose there's no sanity check required for reapplying DOM changes? |
| 09:49 | <rniwa> | hm... i guess there's some. |
| 09:49 | <annevk> | if you just say element has an attribute, where do you look? |
| 09:49 | <annevk> | it's commonly assumed you look in its attribute list and in fact it's the only logical thing to do |
| 09:49 | <annevk> | but it's not written down |
| 09:49 | <rniwa> | annevk: right. |
| 09:49 | <annevk> | at least not so far |
| 09:50 | <annevk> | :) |
| 09:50 | <rniwa> | annevk: I'd say that an element E has an attribute A if an attribute A is in E's attribute list. |
| 09:51 | <rniwa> | annevk: we should really kill attribute nodes |
| 09:51 | <annevk> | yeah, that's the definition |
| 09:51 | <annevk> | rniwa: already done spec-wise... |
| 09:51 | <rniwa> | annevk: oh really? |
| 09:51 | <rniwa> | hm... we just need to kill the ones in the wild i guess? |
| 09:51 | <annevk> | rniwa: Gecko is trying that for us |
| 09:52 | <rniwa> | annevk: great! |
| 09:52 | <annevk> | rniwa: they give plenty of warnings if you try to do Attr node related stuff |
| 09:52 | <rniwa> | annevk: I think we can improve the DOM perf. a lot once we get rid of attr nodes |
| 09:52 | <annevk> | made Facebook stop using it |
| 09:52 | <rniwa> | annevk: that's very nice |
| 09:53 | <annevk> | attribute nodes are DTD legacy :( |
| 09:54 | <annevk> | so in a way we can blame Dan Connolly for convincing Tim HTML had to be SGML-based |
| 09:54 | <annevk> | (rather than just inspired, as HTML 1 was) |
| 10:03 | <sicking> | annevk: really? I didn't know that history, that's very interesting |
| 10:10 | <annevk> | sicking: e.g. in http://www.w3.org/People/Raggett/book4/ch02.html search for "July 1994" |
| 10:11 | <annevk> | sicking: or http://infomesh.net/html/history/early/ |
| 10:12 | <annevk> | Dan told me in person, too :) |
| 11:10 | <malydok> | I've got a weird problem with firefox recently: almost everywhere I click appears a blinking vertical text bar. Wut? |
| 11:11 | <jgraham> | Press F7 |
| 11:12 | <malydok> | Wow, thanks. |
| 11:12 | <malydok> | What's that option anyway? |
| 11:12 | <malydok> | Found it, nvm. |
| 11:13 | <jgraham> | It's caret browsing mode; supposed to help keyboard navigate web pages iirc |
| 11:14 | <malydok> | "Allow text to be selected with the keyboard" |
| 11:22 | <opalepatrick> | looking for a place to ask simple questions related to html5 etc. Like "is header img {}" acceptable? |
| 11:23 | <zcorpan> | here might work. or #html5 |
| 11:26 | <opalepatrick> | Cheers - I suppose my question is does <header> respond to normal block level css - so I could center a log iusing margin, etc? |
| 11:26 | <opalepatrick> | logo* |
| 11:27 | <jgraham> | Generally HTML elements are entirely independent of CSS |
| 11:27 | <jgraham> | In the sense that any CSS rule can be applied to any element |
| 11:27 | <jgraham> | The only exception is replaced content including forms |
| 11:29 | <opalepatrick> | thanks jgraham - it is probably just me having difficulty centering a logo in a header. |
| 11:49 | <Philip`> | hsivonen: I know almost precisely nothing about WOFF |
| 12:13 | <zcorpan> | opalepatrick: in browsers that don't support <header>, it's an inline element, so you need to set it to display:block to work as you expect |
| 12:38 | <opalepatrick> | thanks very much for that zcorpan - worked perfectly - I am surprised that firefox 8 doesnt actually support header like that |
| 12:46 | <hsivonen> | I find it a bit unintuitive that overflow: -o-paged-x; is declared inside an @media -o-paged {} at-rule |
| 12:46 | <hsivonen> | so the media is somehow considered paged before paging is enabled |
| 12:47 | <zcorpan> | iirc annevk suggested the at-rule could be dropped |
| 12:52 | <hsivonen> | also, -o-paged-x-controls is uglyish and doesn't work nicely when set on an element that has rounded corners. |
| 12:52 | <hsivonen> | furthermore, on Linux, height: 100% on the root means 100% of the screen height |
| 12:52 | <hsivonen> | which makes no sense when the browser chrome takes part of the screen height |
| 12:53 | <hsivonen> | so I get both paging and a vertical scrollbar |
| 12:53 | <jgraham> | Sounds like a bug |
| 12:53 | <hsivonen> | sure |
| 12:55 | <hsivonen> | in other news, having three consecutive elements two first ones of which have page-break-after:avoid; allows a page break between the first and the second instead of moving all three to the next page |
| 13:04 | <hsivonen> | so I have a floating image with a negative margin right. When it's on a column on the left, it gets clipped by the column to the right |
| 13:05 | <hsivonen> | Opera Reader bug or a CSS multicol feature? |
| 13:05 | <hsivonen> | do I need some z-index trick to make an image that pokes out of its column paint on top of the next column? |
| 13:16 | <hsivonen> | looks like break-inside: avoid-column; is not supported :-( |
| 13:20 | <hsivonen> | even more curious than the Linux case of height: 100% referring to screen height, on Honeycomb, it also refers to the screen height instead of the height left to the app after the system has taken the actionbar space |
| 13:21 | <jgraham> | hsivonen: If you file [a|some] bug[s], can you point me at [it|them] and I will try to make sure they reach the right people |
| 13:26 | <jgraham> | Oh, mailman day again |
| 14:30 | zcorpan | notices that transfer of .nu domain name from loopia costs 2,387.50 SEK |
| 14:30 | <zcorpan> | .mobi is free to transfer |
| 14:51 | <MikeSmith> | heh |
| 14:51 | <MikeSmith> | telnet miku.acm.uiuc.edu |
| 14:55 | zcorpan | has never used telnet |
| 14:55 | <jgraham> | Things that are weird: In Dave Raggett's book he talks about himself in the third person |
| 15:08 | <StewieG> | Hello |
| 15:11 | <StewieG> | maybe someone has experience with Video conferencing and peer-to-peer communication ? |
| 15:13 | <AryehGregor> | StewieG, if you have a question, best to just ask it. |
| 15:13 | <AryehGregor> | Then hang around and wait. |
| 15:13 | <AryehGregor> | Someone might get back to you after a while. |
| 15:14 | <AryehGregor> | There are definitely people here who are familiar with those parts of HTML, yes. |
| 15:32 | <jgraham> | AryehGregor: Not good enough it seems |
| 15:33 | <AryehGregor> | What's not good enough? |
| 15:41 | <Velmont> | I did live video streaming from a "conference" early this morning using html5 et al. :-) |
| 15:45 | <TabAtkins_> | Hixie: How do I upload files to the whatwg wiki? I've got some screenshots for the text-input-mode page. |
| 15:53 | <jgraham> | AryehGregor: Ask a question and wait |
| 16:23 | <zewt> | seem to recall having a discussion about callback-based blobs for providing data sources, but can't remember where... |
| 16:24 | <zewt> | found it, "File API Streaming Blobs" |
| 16:57 | <nick5437> | hi |
| 17:00 | <nick5437> | Philip`: the code you suggested yesteday to emulate the useful "copy" is not working because the "crop" does not consider the width of a single line as a path |
| 17:04 | <nick5437> | anyone here? |
| 17:06 | <nick5437> | Is it possible to change the spec about "copy" of globalCompositeOperation in canvas to make it like the current chrome implementation or to add a new globalCompositeOperation to have the same result? |
| 17:06 | <AryehGregor> | nick5437, you might want to file a spec bug. |
| 17:06 | <AryehGregor> | Noting how all the different browsers behave would be useful. |
| 17:07 | <AryehGregor> | If other major browsers also behave that way, then you could probably make a good case for it. |
| 17:08 | <nick5437> | firefox used to do the "copy" in that way too but they changed idea only to be with spec, not because the spec "copy" is useful in real uses. there is an interesting conversation in the bug fix about that in firefox |
| 17:08 | <Philip`> | nick5437: The compositing behaviour has been discussed several times, about making it only apply to pixels that are drawn and not to any outside the shapes, but it seems unlikely to change unless someone can at least define precisely how to determine what pixels are drawn (in a way that can be interoperably implemented) |
| 17:09 | <Philip`> | (including interaction with shadows etc) |
| 17:13 | <nick5437> | is it possible to add a new globalCompositeOperation that do the same? browsers like firefox already have the code to do both "copy" so it could become real in a realistic time, right? |
| 17:14 | <nick5437> | i think the old firefox copy and current chrome |
| 17:14 | <Philip`> | It's only possible if someone can define precisely how it should work :-) |
| 17:14 | Philip` | doesn't know how well the old implementations matched each other |
| 17:17 | <nick5437> | is it ok for the spec an image with about 5 examples about the way it should work with shadows and opacity? A picture is worth a thousand words sometimes. to avoid browser confusion on implementation like now |
| 17:18 | <AryehGregor> | nick5437, I'm pretty sure a precise definition is needed, not just examples. |
| 17:18 | <Philip`> | Pictures are too ambiguous to specify behaviour, though they can be very useful when trying to figure out what behaviour to write down |
| 17:19 | <nick5437> | the actual specs using text only have generated lots of confusion in my opinion |
| 17:19 | <nick5437> | http://www.rekim.com/2011/02/11/html5-canvas-globalcompositeoperation-browser-handling/ |
| 17:20 | <nick5437> | or the browser creators are not able to read the specs |
| 17:21 | <Philip`> | I believe all implementors agree on the understanding of what the spec specifies |
| 17:21 | <Hixie> | what's the service that runs under the username lhunt on whatwg.org? |
| 17:21 | <Hixie> | the blog? |
| 17:21 | <Philip`> | (though they haven't all got around to implementing it that way) |
| 17:22 | <Hixie> | looks like it's the blog, the forum is under whatforum and the wiki under whatwiki |
| 17:22 | <Hixie> | assuming it's the blog, the blog is getting hit hard at the moment, wtf |
| 17:29 | <nick5437> | My english is not so good to create a detailed spec (I'm not a native). Could I post an image with examples about the "goodcopy" and let others on the review process to formulate a good text spec? |
| 17:34 | <AryehGregor> | nick5437, writing good specs is very hard. It's not just about phrasing it, it's about figuring out all the corner cases. |
| 17:34 | <AryehGregor> | In this case, good performance might be essential too. |
| 17:36 | <nick5437> | the code of what I'm proposing is already there on firefox and chrome. I'm just proposing to call "goodcopy" the actual chrome implementation of "copy" and "copy" the actual implementation of "copy" on firefox |
| 17:36 | <AryehGregor> | Are you assuming they're actually interoperable in corner cases? |
| 17:41 | <nick5437> | i tried it with different opacities and the implementation looks fine. The whole stuff I'm talking about creating lines with different opacities, size and blur in drawing apps using tablet pressure |
| 17:43 | <tantek> | Hixie, I'm iterating on the change proposals for time/data to include responses to issues/alternatives raised and I wanted to get your opinion on a few things |
| 17:44 | <nick5437> | I think tablet pressure + html5 is something interesting and the "goodcopy" an easy way to use it without changing all the line specs or adding a new line type |
| 17:59 | <tantek> | Hixie, in particular, for <time> element, what do you think of allowing the datetime syntax with a space (U+0020) instead of 'T' between the date and time? |
| 17:59 | <tantek> | my opinion is that it would be helpful |
| 18:03 | <tantek> | there has also been a proposal to add a "tz" attribute to the <time> element to provide separate timezone information |
| 18:03 | <tantek> | I have mixed feelings about it |
| 18:04 | <tantek> | on the one hand I appreciate the seemingly cleaner design by separating timezone into a separate attribute |
| 18:04 | <tantek> | on the other hand I think it may actually *worse* data quality |
| 18:05 | <tantek> | and potentially (even worse) cause us to consider incorporating Olsen - which is a huge mistake for any data format (basing on something that is politically in flux over time) |
| 18:05 | <tantek> | e.g. I can see people seeing the "tz" attribute, and instead of writing tz="-0800", writing something like tz="PST" |
| 18:06 | <tantek> | and if enough people make that mistake - we'd have to consider incorporating some sort of named time zone database etc. |
| 18:06 | <tantek> | so since I'm unsure about it - I'd rather leave out a dedicated "tz" attribute for now |
| 18:06 | <tantek> | anybody else have any thoughts on that? |
| 18:07 | <tantek> | btw this is all regarding Marat's alternate time element proposals: http://www.w3.org/wiki/User:Mtanalin/time_element |
| 18:11 | <tantek> | Sam has asked me to address the issues and counter proposals (such as that) that have been raised as part of my time/data element change proposals: http://www.w3.org/wiki/User:Tantekelik#time_element_issues |
| 18:11 | <tantek> | I believe the goal is to reach some sort of consensus with alternatives/issues for the sake of the HTMLWG. |
| 18:15 | <tantek> | Also, I'm opposed to renaming datetime to value/content etc. Given the constrained microsyntax(es), it makes sense to have a specific attribute name. |
| 18:16 | <tantek> | Also, web authors work better with specific attribute names like datetime which provide a hint as to what the attribute is about, rather than abstract attribute names like "value" which seem like they can take anything (which it can't in the time element). |
| 18:16 | <tantek> | Also, "value" collides with the existing semantics of say <input> value |
| 18:16 | <tantek> | defining an attribute with the same name but completely different meaning will only confuse web authors |
| 18:17 | <tantek> | if anyone has any other reasons against renaming datetime to value/content etc. please feel free to chime in |
| 18:22 | <nick5437> | is the timezone considering something related to the daylight saving time too? |
| 18:22 | <nick5437> | or it is not a problem at all |
| 18:33 | <TabAtkins_> | tantek: You're a whatwg wiki admin, right? Do I need special permissions to upload images or something? |
| 18:36 | <Hixie> | tantek: a single space instead of the T? or just any whitespace? |
| 18:37 | <Hixie> | TabAtkins_: we can make you an admin too |
| 18:37 | <tantek> | hixie - just a single space |
| 18:37 | <tantek> | instead of the T |
| 18:38 | <Hixie> | so <time datetime="9901-01-01 00:00:00"></time> would be value, but |
| 18:38 | <Hixie> | so <time datetime="9901-01-01 |
| 18:38 | <Hixie> | 00:00:00"></time> would not? |
| 18:38 | <Hixie> | s/value/value/ |
| 18:38 | <Hixie> | geez |
| 18:38 | <Hixie> | s/value/valid/ |
| 18:38 | <tantek> | right |
| 18:38 | <tantek> | just U+0020 |
| 18:39 | <tantek> | and I would allow that for <ins>/<del> datetime also |
| 18:39 | <Hixie> | seems like a bit of a gratuitous departure from ISO8601... i mean, if the use case is "make it easy to read and write", why stop there? |
| 18:40 | <tantek> | because the use of " " instead is already a common convention |
| 18:40 | <tantek> | basically, we're not innovating, we're only adopting something that's been in use for a while |
| 18:40 | <Hixie> | in <time>, or in general? |
| 18:40 | <tantek> | it's been a mod on ISO8601 in general |
| 18:40 | <Hixie> | i would posit that in general, arbitrary whitespace is the convention |
| 18:40 | <Hixie> | not just a single space |
| 18:41 | <Hixie> | and that there's a bunch of other looseness that's a general convention too |
| 18:41 | <tantek> | not in the docs I've seen |
| 18:41 | <Hixie> | e.g. a space before the timezone, or not using +hh:mm for the timezone but using "PDT" etc |
| 18:41 | <tantek> | it's always been recommended and used as a single space |
| 18:41 | <tantek> | as a replacement for 'T' |
| 18:41 | <tantek> | since datetime with the 'T' is particularly human unfriendly it seems |
| 18:41 | <Hixie> | i guess we should look at data |
| 18:42 | <Hixie> | not sure what the right way to check this one way or another would be |
| 18:42 | tantek | is looking for references |
| 18:42 | <tantek> | I've seen this before, I just can't remember the URLs at the moment. |
| 18:43 | <tantek> | well here's a rough mention: http://en.wikipedia.org/wiki/ISO_8601#Combined_date_and_time_representations |
| 18:43 | <tantek> | "The date and time representations may appear in proximity to each other, often separated by a space or sometimes by other characters." |
| 18:44 | <tantek> | note that "a space" is the only specific alternative separator mentioned |
| 18:44 | <Hixie> | yeah but that says they're two fields, not that it's one U+0020 character in a single field |
| 18:44 | <tantek> | in my opinion that gives it more weight than other hypothetical separators (arbitrary whitespace etc.) |
| 18:44 | <Hixie> | just searching for "date time format" on google doesn't support your thesis. the examples all have widely different forms when you move away from ISO8601, there doesn't seem to be a consistent move from ISO8601 to s/T/ / |
| 18:44 | <tantek> | yeah - not sure how much we can rely on such details in a WIkipedia page anyway |
| 18:45 | <tantek> | Hixie - insufficiently specific search :) |
| 18:45 | <Hixie> | it's not like people are going to be able to use ISO8601-with-space as a human-readable format anyway |
| 18:45 | <Hixie> | different locales need different punctuation, e.g. |
| 18:46 | <Hixie> | even if the order is y-m-d |
| 18:46 | <Hixie> | and some locales need AM/PM, others need 24h clocks |
| 18:46 | <Hixie> | i'd just keep it simple and have one format |
| 18:46 | <Hixie> | our "one format" already has like 8 variants |
| 18:46 | <Hixie> | no need to double it :-) |
| 18:48 | <tantek> | ok I can be convinced of that |
| 18:48 | <tantek> | I will write up your arguments accordingly. |
| 18:48 | <tantek> | does our current datetime permit more than 4 digit years? |
| 18:48 | <Hixie> | yeah |
| 18:48 | <Hixie> | 4+ |
| 18:48 | <tantek> | ok cool |
| 18:48 | <Hixie> | as far as the other things you mentioned, i think i agree with all your comments |
| 18:48 | <Hixie> | for tz="", remember we now allow timezone separately |
| 18:49 | <Hixie> | so they can use two <time> elements |
| 18:49 | <TabAtkins_> | Hixie: If that's what's needed to upload images to the wiki, then yes please. |
| 18:49 | <Hixie> | TabAtkins_: no idea if that's what's needed. if you need somewhere to upload files, though, http://software.hixie.ch/utilities/cgi/uploader/uploader w643kJ6Gv43q3 |
| 18:49 | <tantek> | just noticed this while searching for deviations from ISO: http://www.w3.org/TR/xmlschema-2/#morethan9999years (the more than 4 digits for years thing) |
| 18:50 | <tantek> | I love that in the Y2K update of ISO8601 they decided to fix the Y10K problem in ISO8601. |
| 18:50 | <Hixie> | tantek: what's your username? |
| 18:50 | <tantek> | Hixie re: tz - they can't quite use two timezone elements |
| 18:50 | <Hixie> | er |
| 18:50 | <nick3264> | I'm interested about writing a globalCompositeOperation proposal. is the wiki a good place for it? |
| 18:50 | <Hixie> | TabAtkins_: what's your username |
| 18:50 | <tantek> | because time elements don't combine semantics |
| 18:50 | <Hixie> | tantek: no? |
| 18:51 | <Hixie> | hmm |
| 18:51 | <Hixie> | well |
| 18:51 | <tantek> | that was a separate proposal |
| 18:51 | <tantek> | for which there wasn't sufficient support |
| 18:51 | <Hixie> | the combined semantics thing basically depends on the vocab you're using it with |
| 18:51 | <tantek> | http://wiki.whatwg.org/wiki/Time_element#composite_nested_time_elements |
| 18:51 | <Hixie> | if the vocab says "put time and date here and tz here and combine them like so", then that's what it is |
| 18:51 | <tantek> | sure - you can do that too |
| 18:52 | <tantek> | I meant in a vocab independent way |
| 18:52 | <tantek> | that just worked with the time element |
| 18:52 | <Hixie> | ah yeah i dunno what the use case for that would be |
| 18:52 | <Hixie> | TabAtkins_: nm got it |
| 18:52 | <tantek> | Hixie, no new use cases, just improved data quality of existing use cases |
| 18:52 | <tantek> | but then this is something we can add later |
| 18:52 | <tantek> | so I'm not in a rush to add it now |
| 18:52 | <tantek> | happy to wait until more people are convinced |
| 18:53 | <Hixie> | TabAtkins_: ok you're marked as admin and bureaucrat, whatever that means |
| 18:53 | <Hixie> | tantek: k |
| 18:53 | <tantek> | Tabatkins, remember the saying |
| 18:53 | <Hixie> | afk for a bit, bbl |
| 18:54 | <tantek> | http://en.wikipedia.org/wiki/Uncle_Ben#.22With_great_power_comes_great_responsibility.22 |
| 18:55 | <nick3264> | also http://en.wikipedia.org/wiki/Quis_custodiet_ipsos_custodes%3F :) |
| 19:02 | <tantek> | also afk for a bit, bbl |
| 19:03 | <nick3264> | cya. dinner time |
| 19:04 | <kennyluck> | Hixie, tantek. The date time python module output " " instead of "T" for str(aDatetime). I haven't checked libraries in other languages.Though some ISO8601 parsers don't parse " ". |
| 19:04 | <kennyluck> | But in this case, I think we should optimize for the authors. |
| 19:08 | <tantek> | kennyluck - do you have a URL for that? "date time python module output " " instead of "T" for str(aDatetime)" |
| 19:09 | <kennyluck> | tantek, http://docs.python.org/dev/library/datetime.html#datetime.datetime.__str__ |
| 19:11 | <kennyluck> | my guess is that people would rely more on "%s" % aDatetime than something like aDatetime.isoformat(), which uses "T" as the default separator, though I can't be sure. |
| 19:14 | <kennyluck> | In any case, I hate the "T". It's too machine-like and doesn't look friendly. |
| 19:18 | <mkanat> | All ISO-8601 parsers should parse the space; it's valid. |
| 19:23 | <kennyluck> | Hixie, re. "it's not like people are going to be able to use ISO8601-with-space as a human-readable format anyway". I disagree with you, I think this is the most i18n-wise human-readable format. Everytime I see timezone abbrevs like "PDT" instead of UTC-5, I whine. English months are not so bad but still. |
| 19:25 | <mkanat> | Yeah, I've used that as a human-readable format all the time. |
| 19:27 | <tantek> | mkanat - do you have a URL that explains how it's valid that all ISO-8601 parsers should parse the space? |
| 19:27 | <mkanat> | tantek: I'll see what I can find. |
| 19:27 | <tantek> | thanks, appreciated. |
| 19:28 | <mkanat> | tantek: Ahh, it's not that everybody should accept space--it's that those are two separate representations. |
| 19:28 | <mkanat> | tantek: I'm just so used to parsers accepting a space. |
| 19:29 | <tantek> | mkanat - even URLs to parser documentation that shows that they accept a space there instead of a 'T' would be handy. |
| 19:30 | <tantek> | basically, it's very different if we're just adopting an established precedent / extension to ISO8601 than addressing the general problem of creatively making ISO8601 datetimes more human friendly. |
| 19:33 | <mkanat> | tantek: This isn't perfect, but one example is that MySQL takes and sends all its dates in that format: http://dev.mysql.com/doc/refman/5.1/en/datetime.html |
| 19:33 | <mkanat> | tantek: As does almost every other DBMS I've ever used (with a few exceptions--I believe Sybase doesn't). |
| 19:33 | <kennyluck> | nice! |
| 19:35 | <mkanat> | Perl's Date::Parse also takes dates in that format, although it's not int he documentation. |
| 19:36 | <mkanat> | But we've been relying on it doing so, for years, in Bugzilla. |
| 19:40 | <Velmont> | I also dislike the T. |
| 19:41 | <mkanat> | I believe every Date.parse implementation also supports it in browsers, although I haven't checked and it's not what the standard says. |
| 19:41 | <mkanat> | Or at least, it's not the "subset of ISO 8601" from http://www.w3.org/TR/NOTE-datetime |
| 19:42 | <kennyluck> | mkanat, that's unfortunately wrong, at least for FF8. |
| 19:42 | <mkanat> | kennyluck: Drat. |
| 19:42 | <mkanat> | Well, Chrome can parse it. |
| 19:43 | <mkanat> | Probably the standard should say something about contexts where input is only a datetime. |
| 19:44 | <mkanat> | Since yes, in a string of text, "2011-11-11 11:11:11" could logically be two separate representations, in a call to Date.parse, from the developer's perspective, it's obviously one representation. |
| 19:44 | <Velmont> | Opera handles it as well. |
| 19:46 | <zewt> | as does IE8, at least (would have to load a VM to test 9) |
| 20:13 | <Hixie> | kennyluck: i agree and use the same format myself, but we are in a woefully small minority |
| 20:14 | <Hixie> | tantek: if we can collect evidence e.g. showing that there are common parsers that support a nicer format, i'm certainly all for it, fwiw |
| 20:14 | <Hixie> | tantek: my reluctance is just to forging new ground here |
| 20:21 | <kennyluck> | Hixie, common parsers or generators? |
| 20:23 | <TabAtkins> | tantek: What saying? |
| 20:24 | <Phae> | Hixie: thanks for the link to your microdata usability testing. sorry for not seeing it sooner. |
| 20:24 | <TabAtkins> | tantek: Ah, I see it now. I didn't connect the link following your comment to what you were saying. |
| 20:24 | <TabAtkins> | tantek: Also, I already deleted the entire wiki and devoted it to crochet pornography, so, um, I guess I failed Uncle Ben. |
| 20:24 | <Hixie> | kennyluck: well both, but parsers are more important, since publishers with no parsers is just a waste of time and bandwidth for a lot of people |
| 20:25 | <Hixie> | Phae: no worries |
| 20:29 | <timeless> | zewt: i could test ie9/ie10pp4 if you wanted |
| 20:30 | <kennyluck> | ECMAScript5 pretty much says you could do whatever you want beyond a subset of ISO8601. I would be very surprised if ie changes this behavior, but I guess it's still worth checking. |
| 20:31 | <Hixie> | ES5 doesn't define the parsing? |
| 20:33 | <kennyluck> | Hixie, isn't that the reason why we have → http://wiki.whatwg.org/wiki/Web_ECMAScript#Date_Parsing ? |
| 20:33 | <zewt> | timeless: if they want (not involved in the time stuff, just giving a data point) |
| 20:34 | <Hixie> | kennyluck: hah |
| 20:34 | <Hixie> | kennyluck: i guess so |
| 20:53 | <timeless> | zewt: someone would have to tell me what they want me to do |
| 20:54 | <zewt> | don't know if anyone actually needs it, but i just did javascript:alert(Date.parse("2011-11-11 11:11:11")) |
| 20:55 | <timeless> | NaN in my default ie here in w8 |
| 20:56 | <timeless> | which is some flavor of ie10 |
| 20:58 | <timeless> | ie9:f12 says Date.parse("2011-11-11 11:11:11") = NaN |
| 20:59 | <kennyluck> | wow, that's surprising, given that IE8 supports this. |
| 21:07 | <zewt> | odd--now neither of them are working. not sure what I'm doing differently |
| 21:07 | <zewt> | maybe I switched browser windows before without realizing? dunno. |
| 21:07 | <zewt> | also, fascinating chrome utter braindamage: it strips javascript: when i paste into the address bar. |
| 21:07 | <kennyluck> | oh, my. |
| 21:07 | <zewt> | special thanks to chrome for making the address bar more and more horrible |
| 21:08 | <zewt> | ie8 only seems to be accepting the format it outputs from toString ("Thu Dec 1 16:10:18 EST 2011"). |
| 21:10 | <kennyluck> | zewt, yeah, that's another requirement from ECMAScript, namely, toString and then Date.parse needs go back to the original. |
| 21:11 | <timeless> | zewt: IE seems to do that too |
| 21:11 | <timeless> | my guess is it's a security feature |
| 21:11 | <timeless> | to prevent Facebook attacks |
| 21:11 | <timeless> | and if that's its goal, i'm happy |
| 21:12 | <zewt> | kennyluck: i don't think any implementation does that, since toString loses milliseconds |
| 21:12 | <timeless> | kennyluck: should i ask how dare something require roundtripping? :) |
| 21:13 | <zewt> | timeless: i'm of the stance that if a user is going to follow steps like "please copy this mysterious block of letters and paste it into your address bar", no amount of babysitting is going to protect them :) |
| 21:13 | <kennyluck> | I guess I am just missing the details. |
| 21:13 | <Velmont> | zewt: Maybe data:text/html,<!doctype html><script>alert(Date.parse("2011-11-11 11:11:11"))</script> will work? |
| 21:15 | <timeless> | Velmont: historically, ie's support for data: urls was spotty |
| 21:15 | <timeless> | it doesn't seem to have improved |
| 21:15 | <zewt> | Velmont: nope (after copying to a file to avoid data:) |
| 21:16 | <timeless> | i think the right approach is hixie's kitchen |
| 21:16 | <timeless> | which lets you test out dom results of pages you compose |
| 21:17 | <Velmont> | zewt: huh? Doesn't chromium support data:? |
| 21:17 | <zewt> | talking about IE here |
| 21:17 | <zewt> | (re: formats supported by Date.parse) |
| 21:17 | <Velmont> | 22:10 < zewt> also, fascinating chrome utter braindamage: it strips javascript: when i paste into the address bar. <<< |
| 21:18 | <zewt> | eh, that's a huge amount of typing for pasting things across browsers to test, heh |
| 21:18 | <zewt> | let me try it, out of curiosity |
| 21:18 | <zewt> | heh yeah, so stripping javascript: does absolutely nothing (security-wise) |
| 21:18 | <zewt> | unless there's some weird corner case i'm not thinking of, anyway |
| 21:21 | <timeless> | it does |
| 21:22 | <timeless> | it requires users to be convinced to take 3 extra steps to do something they really shouldn't be doing |
| 21:22 | <timeless> | but yes, facebook has millions of sheep |
| 21:23 | <zewt> | oh, the difference is that data:html is run in a separate page, where javascript: is run in the existing page |
| 21:23 | <miketaylr> | heh, type in j then copy-paste avascript:alert(1) to see a secret message! |
| 21:23 | <timeless> | zewt: yep |
| 21:23 | <zewt> | alt-faxmachine |
| 21:23 | <timeless> | the attacks only work when they're same origin against stupid users in facebook (or similar) |
| 21:24 | <zewt> | "attacks" :P |
| 21:24 | <timeless> | miketaylr: i think it's "copy <avascript,....>; click urlbar, press j, paste, enter" |
| 21:25 | <timeless> | zewt: they happen often enough that my eyes glaze over when i see reports |
| 21:25 | <miketaylr> | timeless: sorry, i'm new at pwning facebook users ;) |
| 21:26 | <timeless> | you're a fast learner, you'll get the hang of it :) |
| 21:26 | <miketaylr> | :D |
| 21:26 | <timeless> | ├──3,360.63 MB (91.95%) -- heap-unclassified |
| 21:26 | timeless | sighs |
| 21:27 | timeless | needs to make an Xgb file to cause firefox to crash already |
| 21:27 | <timeless> | Local Disk (C:) 1.70 GB free |
| 21:27 | <timeless> | Swap (Z:) |
| 21:27 | <zewt> | "view image" on a big canvas is a fun one |
| 21:27 | <timeless> | 2.51 GB free of 4.08 GB |
| 21:28 | <timeless> | zewt: err, the goal is to cause firefox not to have memory to allocate space for the irc client |
| 21:28 | <timeless> | not to just arbitrarily kill firefox |
| 21:29 | timeless | tries to remember how to create a 2.5gb file on windows |
| 21:29 | <timeless> | preferably a sparse file |
| 21:29 | <zewt> | dd from linux over cifs |
| 21:29 | <zewt> | heh |
| 21:29 | <timeless> | ss64.com/nt/fsutil.html |
| 21:30 | <timeless> | fsutil file setvaliddata sparse number-that-means-2.5gb |
| 21:36 | <timeless> | Z:\>fsutil file createnew z:\limitswap3 1073741824 |
| 21:36 | <timeless> | File z:\limitswap3 is created |
| 21:39 | <timeless> | ok, now i have <10mb of swap available |
| 21:39 | timeless | prepares to die |
| 21:40 | <zewt> | timeless.exe |
| 21:50 | <jgraham> | Just saw The Nutcrasked. Had a man in a Fez. Remined me of shepazu. Decided we need a ballet about the W3C. |
| 21:50 | <jgraham> | You might think an opera would be more obvious, but clearly if I propose that people would just think I'm biased. |
| 21:52 | astearns | is shuddering at the thought of a bikeshedding aria |
| 21:56 | <kennyluck> | paul_irish, comment on http://h5bp.github.com/igotmybeanie/ . I think you might want to mention the input box at the bottom of the HTML Living Standard. As far as I can tell, that's the simplest way how you send feedback. |
| 21:58 | <annevk> | I wish someone else could write these emails for me: http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/1312.html |
| 22:00 | <annevk> | I like Adrian, but I also wish I didn't have to do his homework |
| 22:03 | <divya> | kennyluck: thnx will add that in. |
| 22:06 | <annevk> | TabAtkins: you cannot upload images I think, you have to upload them to imgur or some such and link them |
| 22:06 | <annevk> | TabAtkins: see e.g. http://wiki.whatwg.org/wiki/Use_cases_for_timed_tracks_rendered_over_video_by_the_UA |
| 22:07 | <zewt> | depending on free services like imgur long-term always makes me nervous |
| 22:08 | <TabAtkins> | annevk: Ah, ok. |
| 22:09 | <Luck> | hiya , can anybody tell me , do you use the new data element or still keep the <time>? |
| 22:09 | <TabAtkins> | zewt: Yeah, that's why I wanted to upload to the wiki - then the images have a better chance of staying around as long as the page itself. |
| 22:09 | <annevk> | I guess you can use http://junkyard.damowmow.com/ |
| 22:09 | <annevk> | and get the password from Hixie |
| 22:09 | <TabAtkins> | I can just put it on my own site I guess. |
| 22:10 | <TabAtkins> | Luck: What are you using it for? (If you don't already have a data-consumer in mind, don't bother with it.) |
| 22:11 | <annevk> | There's probably some way to upload images, it has file search and things like that... |
| 22:11 | <TabAtkins> | annevk: No, Special:Upload explicitly says that uploading is disabled. |
| 22:11 | <TabAtkins> | I was hoping it would change when I got admin powers. |
| 22:11 | <TabAtkins> | But no luck. |
| 22:12 | <divya> | kennyluck: is this you? https://github.com/kennyluck |
| 22:13 | <annevk> | TabAtkins: aah, maybe Lachy can change that |
| 22:13 | <TabAtkins> | annevk: That would be cool. |
| 22:13 | <divya> | o it is. |
| 22:14 | <Lachy> | TabAtkins, do you know how to change it? |
| 22:14 | <Luck> | k |
| 22:14 | <Lachy> | does it require modifying LocalSettings.php? |
| 22:14 | <kennyluck> | divya, yeah. |
| 22:14 | <AryehGregor> | Lachy, yes. Should be $wgEnableUploads or something. |
| 22:14 | <divya> | added it here kennyluck https://github.com/h5bp/movethewebforward/commit/dd946130fb69ba8d7a0631ba7861f15107a164e4 |
| 22:14 | <kennyluck> | divya, not being a web developer, I am not using github often though. |
| 22:14 | <Lachy> | AryehGregor, can you do it? |
| 22:14 | <AryehGregor> | Lachy, http://www.mediawiki.org/wiki/Manual:$wgEnableUploads |
| 22:14 | AryehGregor | pokes |
| 22:14 | <kennyluck> | divya, OK. |
| 22:15 | <divya> | ha okay :) |
| 22:15 | <divya> | it was easy to ref in the commit tho :D |
| 22:15 | <Lachy> | AryehGregor, btw, did you set up an SVN server for the wiki? I was wondering why I saw some .svn folders in there |
| 22:15 | <AryehGregor> | Lachy, it's an SVN checkout. |
| 22:15 | <kennyluck> | divya, thanks for attributing that to me :p |
| 22:15 | <AryehGregor> | Because I wanted some feature from the trunk version at some point. |
| 22:15 | <AryehGregor> | I can't remember what. |
| 22:15 | <AryehGregor> | It should be safe to overwrite it with a downloaded tarball. |
| 22:15 | <AryehGregor> | (if no one has already) |
| 22:16 | <jgraham> | Didnt you want your html5ified version? |
| 22:16 | <jgraham> | Or am I imagining things? |
| 22:16 | <Lachy> | ok. I thought maybe you'd started maintaining it in SVN. I didn't think that you'd checked it out directly from wikimedia's server |
| 22:16 | <paul_irish> | kennyluck: thank you. will do https://github.com/h5bp/movethewebforward/issues/41 |
| 22:17 | <AryehGregor> | What user does the web server run as? |
| 22:17 | <AryehGregor> | Not whatwikiuser, I guess? |
| 22:17 | <Lachy> | AryehGregor, I haven't overwritten it. But I did make some minor changes to LocalSettings.php to disable user registrations, and to update the ConfirmEdit extension |
| 22:17 | <paul_irish> | kennyluck: oops divya did it already. i see now |
| 22:17 | <AryehGregor> | TabAtkins, try now. |
| 22:17 | <Lachy> | yes, it's whatwikiuser |
| 22:17 | <AryehGregor> | Oh, okay. |
| 22:17 | <AryehGregor> | No need for chmod, then. |
| 22:18 | <Lachy> | oh. wait, maybe it's not. |
| 22:18 | <Lachy> | it's the same server as the blog and all of Hixie's other stuff |
| 22:18 | <TabAtkins> | AryehGregor: Yup, seems to work. Or at least, it brings up an upload form now. |
| 22:19 | <TabAtkins> | The files I want to upload are at home, though, so I'll wait to actually try it out. |
| 22:19 | <TabAtkins> | Thanks, you two. |
| 22:19 | AryehGregor | chmods to 777, so it should theoretically work |
| 22:19 | <AryehGregor> | The reason it's disabled by default is because directory permissions are usually wrong by default, so it will just give an error. |
| 22:21 | <kennyluck> | Nice, I am glad that Mozilla's "mentored bugs" are mentioned on http://movethewebforward.org/ . |
| 22:29 | <kennyluck> | paul_irish, I personally think subscribing to certain HTML5 features of interest in Bugzilla (Mozilla/WebKit) would be something nice if you care about a subset of HTML5 features but not all. Though I am not sure if it's too advanced to put into the "learn" section. (and perhaps voting in Bugizlla, which is supposed to help browser vendors prioritize features, but I am not sure if browser vendors actually look at that) |
| 22:31 | <kennyluck> | I quite like http://en.wikipedia.org/wiki/Comparison_of_layout_engines_%28HTML5%29 for this aspect. |
| 23:01 | <Hixie> | in case anyone tried filing spec bugs and found it didn't work, i've fixed the script |
| 23:10 | <timeless> | AryehGregor: coming in late to an already dead study, i think the key is that poorer people tend to die sooner, so even if families had the same number of children initially, the number of surviving children was probably likely to be higher among the wealthier clans :) |
| 23:11 | <timeless> | you're right in that generally one didn't have control over the birth rate, but the survival rate is a different story :) |
| 23:17 | <reuben_> | I'm trying to understand the reasoning behind http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#dom-media-defaultmuted |
| 23:18 | <reuben_> | isn't it the same thing as the muted attribute itself? |
| 23:19 | <reuben_> | maybe I just don't understand the difference between IDL and content attributes |
| 23:19 | <Hixie> | annevk: ping |
| 23:19 | <Hixie> | reuben_: bar="" is a content attribute in <foo bar=""> |
| 23:19 | <Hixie> | reuben_: or in element.getAttribute('bar') |
| 23:20 | <Hixie> | reuben_: an IDL attribute is something like element.textContent |
| 23:20 | <Hixie> | reuben_: or element.title |
| 23:20 | <reuben_> | Hixie, ah, as I suspected! thanks! |
| 23:20 | reuben_ | continues writing this test |
| 23:21 | <Hixie> | reuben_: often the two are so closely related that you can treat them as the same thing, but in practice the fact that they are distinct is important |
| 23:21 | <Hixie> | reuben_: so e.g. element.className is the idl attribute for <element class=""> |
| 23:21 | <Hixie> | reuben_: but so is element.classList |
| 23:21 | <Hixie> | reuben_: one is a string, but the other is an object with its own members |
| 23:22 | <Hixie> | reuben_: both of these IDL attributes "reflect" the class="" content attribute |
| 23:22 | <Hixie> | reuben_: but they do it in different ways |
| 23:22 | <Hixie> | reuben_: sometimes, a content attribute has no IDL attribute, e.g. <html manifest=""> |
| 23:24 | <reuben_> | Hixie, very interesting. I didn't know about classList by the way. so why do some content attributes lack a IDL attribute? |
| 23:24 | <Hixie> | doesn't make any sense to touch manifest="" from script |
| 23:24 | <Hixie> | so there's no point giving it an IDL attribute |
| 23:25 | <Hixie> | <meta charset=""> similarly has no corresponding IDL attribute |
| 23:25 | <Hixie> | (though Document has a bunch of charset-related stuff) |
| 23:27 | <reuben_> | I see. thanks for the info |
| 23:45 | <paul_irish> | kennyluck: i actually dont know how how to subscribe to a component or area in bugzilla.. are there docs on this? |
| 23:45 | <Hixie> | add a watch for the QA contact of the component |
| 23:45 | <kennyluck> | paul_irish, I am not talking about subscribing a component. I think master bugs are good enough. |
| 23:46 | <kennyluck> | Hixie, good idea! |
| 23:46 | <paul_irish> | Nice. is there a good technique for finding master bugs ? |
| 23:46 | <kennyluck> | Hixie, not something the WebKit bugillza instance supports :( |
| 23:47 | <Hixie> | kennyluck: watching, or qa contacts? |
| 23:47 | <Hixie> | kennyluck: both can be enabled by the admin, if you know who that is |
| 23:47 | <kennyluck> | Hixie, qa contacts. |
| 23:47 | <Hixie> | kennyluck: ah |
| 23:47 | <kennyluck> | paul_irish, the way I did it is find what bugs Peter Beverloo and Paul Rouget are tracing. :) I actually have links for that. |
| 23:48 | <Peter`> | I'm subscribed to pretty much every bug on WebKit :) |
| 23:48 | <Peter`> | Bugs I'm specifically CC'ed one are either ones I'm involved in as part of my job, or ones that really interest me (as these end up in my inbox) |
| 23:49 | <Hixie> | i'm subscribed (through watches) to an ungodly number of bugs in both webkit and mozilla, but with heavy filtering on my end :-) |
| 23:49 | <Peter`> | Dito, filters are the best thing since e-mail |
| 23:51 | <kennyluck> | paul_irish, here you go https://bugs.webkit.org/buglist.cgi?&emailcc1=1&emailtype1=exact&email1=peter%40chromium.org |
| 23:51 | <kennyluck> | https://bugzilla.mozilla.org/buglist.cgi?emailcc1=1&emailtype1=exact&email1=paul%40mozilla.com |
| 23:52 | <kennyluck> | perhaps not something effective, then I guess you just search "implement" or something... |
| 23:56 | <kennyluck> | Hixie, you mean the admin needs to upgrade my privilege so that I can watch components or see who the qa contact is? |
| 23:56 | <Hixie> | kennyluck: no, i mean the admin needs to enable qa contacts for the whole bugzilla instance |
| 23:56 | <kennyluck> | Oh ok. |
