| 06:09 | <zcorpan> | Hixie: the crazy stuff you see in opera with detached iframes could be the popup blocker showing through, maybe |
| 07:01 | <zcorpan> | [tm]: "(with the exception of the HTML-specific APIs defined in the DOM4 specification)" why is DOM4 APIs excluded? why not exclude other APIs that get axed from the HTML spec and get maintained elsewhere? |
| 07:03 | <annevk> | zcorpan: pointer? |
| 07:03 | <zcorpan> | http://www.w3.org/html/wg/charter/2012/ |
| 07:04 | <annevk> | ah yeah |
| 07:04 | <annevk> | it should all be in scope |
| 07:04 | <annevk> | but if it better fits elsewhere and someone can maintain it, the possibility should be there for it to be moved |
| 07:05 | <zcorpan> | hmmm "The updated HTML specification may be modularized into separate documents." |
| 07:40 | <annevk> | XMLHttpRequest now uses ByteString |
| 07:40 | <annevk> | it is so much cleaner |
| 07:47 | <annevk> | odinho: might require changes to some tests |
| 07:47 | <Velmont> | annevk: OKay. |
| 07:47 | <annevk> | odinho: certain input will now throw a TypeError rather than a DOM SyntaxError |
| 07:49 | <Velmont> | So, ByteString only takes [A-Za-z0-9]? |
| 07:50 | <annevk> | no |
| 07:50 | <annevk> | it takes U+0000 up to and including U+00FF |
| 07:50 | <Velmont> | http://dev.w3.org/2006/webapi/WebIDL/#es-ByteString <- saw it now. Kinda slow on the searches ;P |
| 07:50 | <annevk> | anything greater than that will throw |
| 08:06 | <zcorpan> | for whoever is interested in specifying user events, plugins, etc: http://forums.whatwg.org/bb3/viewtopic.php?f=3&t=5018 |
| 10:10 | <MikeSmith> | no annevk :( |
| 10:10 | MikeSmith | was wondering if anne still wants to try to publish LCWD of the Notifications spec this week or not |
| 10:20 | <smaug____> | uh, I need to remind dougt to send his comments about Notifications |
| 10:20 | <smaug____> | apparently NotificationDirection isn't really implementable on all OSes |
| 10:23 | <MikeSmith> | hmm |
| 10:23 | <MikeSmith> | I guess we're not going to LC yet, then |
| 10:23 | <MikeSmith> | which means we probably won't for a couple months yet |
| 10:23 | <MikeSmith> | seeing as anne will be away for a few weeks |
| 12:17 | <matjas> | <script src=>alert('wat')</script> http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=1616 — IE and Opera alert, other browsers don’t |
| 12:27 | <jgraham> | Other browsers are correct. http://www.whatwg.org/specs/web-apps/current-work/#prepare-a-script step 14 |
| 12:28 | <AryehGregor> | Beat me by 20 seconds. :( |
| 12:40 | <annevk> | MikeSmith: I have time to fix minor things |
| 12:40 | <annevk> | MikeSmith: and I plan to work a bit in my free time |
| 12:42 | <annevk> | smaug____: MikeSmith: though I think we should keep NotificationDirection in, even though not implementable everywhere |
| 12:42 | <smaug____> | I don't know the details... |
| 12:42 | <annevk> | smaug____: MikeSmith: we should maybe add some language to the conformance that if there's platform limitations there's going to be some issues |
| 12:43 | <smaug____> | but I was told that for example on Android if the UI is ltr, there isn't any way to show rtl notifications |
| 12:43 | <annevk> | smaug____: right, I think that's a bug we should file on Android then and note that implementations cannot do everything correctly |
| 12:43 | <annevk> | smaug____: although as a workaround you could probably insert the appropriate Unicode override characters |
| 12:44 | <annevk> | smaug____: if he could email those comments today that would be great |
| 12:44 | <smaug____> | ok, I'll ask him |
| 12:44 | <smaug____> | (he is traveling somewhere in Europe ) |
| 12:44 | <annevk> | smaug____: I can then probably fix them tomorrow and we can still publish as planned "without" issues |
| 12:44 | <annevk> | ah okay |
| 12:44 | <annevk> | oh well, if it doesn't work out we'll be delayed a bit |
| 12:44 | <annevk> | no big deal |
| 12:45 | <AryehGregor> | WTF: The website at aryeh.name has been reported as a “phishing” site. Phishing sites trick users into disclosing personal or financial information, often by pretending to represent trusted institutions, such as banks. |
| 12:45 | <AryehGregor> | ?! |
| 12:45 | <annevk> | although I don't want to keep changing it around since I want Apple to implement this and not keep prefix bullshit around forever |
| 12:46 | <annevk> | AryehGregor: hacked? |
| 12:46 | <AryehGregor> | Maybe . . .\ |
| 12:46 | AryehGregor | looks |
| 12:49 | <jgraham> | AryehGregor: I don't see a warning? Als, is firefox nightly totally broken? |
| 12:50 | <AryehGregor> | jgraham, I see it in Chrome dev. |
| 12:50 | <AryehGregor> | Firefox nightly shouldn't be totally broken, but I dunno, I compile my own builds. |
| 12:51 | <jgraham> | Hmm, restarting it seemed to help. The chrome was totally broken; clicking links didn't work and context menus showed all possible options even irrelevant ones |
| 12:52 | <jgraham> | Still no fraud warning in Chrome |
| 12:56 | AryehGregor | reports it as an error |
| 12:56 | <AryehGregor> | I still see it at: http://aryeh.name/tmp/css-test/contributors/aryehgregor/submitted/ |
| 12:56 | <AryehGregor> | Not at the homepage. |
| 14:30 | <Stevef> | Is there any pace in the html spec that lists which elements can have a disabled attribute? |
| 14:36 | <acies> | Limited to form elements, isn't it? |
| 14:36 | <Philip`> | Stevef: http://www.whatwg.org/specs/web-apps/current-work/multipage/section-index.html#attributes-1 may be relevant |
| 14:37 | <Stevef> | Philip: thanks, just the thing. looked for something like that but couldn't find it |
| 15:01 | <Philip`> | Hmm, a new password restriction I've not seen before: "Include one symbol but do not contain "<" and ">" symbols" |
| 15:02 | <Philip`> | That gives me great confidence in their system's security |
| 15:02 | <bzed> | does it exclude = and ; , too? |
| 15:03 | <Philip`> | It doesn't say so |
| 15:03 | Philip` | isn't about to test it in practice |
| 15:45 | <annevk> | did anyone go investigate which specs can be updated with the default dictionary thing? |
| 15:45 | <annevk> | I guess Notifications |
| 15:46 | <annevk> | maybe we should do it for events too |
| 15:46 | <annevk> | now we restricted document.createEvent |
| 15:46 | <dglazkov> | good morning, Whatwg! |
| 17:18 | <Ms2ger> | jgraham, yt? |
| 17:55 | <TabAtkins_> | Morning, everyone! |
| 17:57 | <Ms2ger> | Evening |
| 18:38 | <cgcardona> | delayed good morning TabAtkins. woot |
| 18:57 | <jgraham> | Ms2ger: yes |
| 18:57 | <Ms2ger> | unping :) |
| 18:59 | Ms2ger | fights Philip`'s tests some more |
| 19:57 | <gsnedders> | jwalden: You ever get around to emailing about __proto__? |
| 19:58 | gsnedders | has seen nothing to es-discuss |
| 20:05 | <jwalden> | Hixie: we stopped clearing the properties off dead windows semi-recently, which may affect your detaching-iframes tests |
| 20:06 | <jwalden> | gsnedders: no, I keep getting distracted from it |
| 20:06 | <jwalden> | I should do that now |
| 20:07 | <jwalden> | I did discuss it with dherman last week, and he's so completely wrong about it that somehow in discussion I managed to convince him to just walk away and claim I was ranting/arguing in bad faith/something bad :-\ |
| 20:09 | <gsnedders> | :| |
| 20:11 | <gsnedders> | jwalden: If you don't do it soon I may end up doing so. :P |
| 20:20 | <jwalden> | gsnedders: we should both do it, actually |
| 20:20 | <gsnedders> | jwalden: I'll agree with you on list if you do. |
| 20:21 | <gsnedders> | Just whoever does the first post will likely do the longer one. |
| 20:21 | <jwalden> | gsnedders: sounds good |
| 20:21 | gsnedders | finally has time to actually really do much, going back to working full-time tomorrow |
| 20:21 | <Ms2ger> | The WHATWG cabal... "I'll agree with you on list" |
| 20:22 | <jwalden> | there is no cabal |
| 20:22 | <gsnedders> | jwalden: What, you don't hang out in #whatwg-cabal!? |
| 20:23 | <Ms2ger> | You mean #secrettreehouse? |
| 20:24 | <jwalden> | I am not now, nor have I ever, hung out in #whatwg-cabal or #secrettreehouse |
| 20:24 | <gsnedders> | Wow. What an outsider. WE MUST DISAGREE WITH EVERYTHING HE SAYS. |
| 20:24 | <TabAtkins_> | Good, because they're not real. |
| 20:24 | <pablof> | jwalden: you might need this, http://www.adinnerguest.com/wp-content/uploads/Bill-Clinton.jpg |
| 20:25 | <jwalden> | actually, hmm, I might have joined #secrettreehouse once to see if anyone was in it |
| 20:26 | <jwalden> | I guess it depends on what your definition of the word "joined" is |
| 20:26 | <TabAtkins_> | We use "joined" in the biblical sense. |
| 20:27 | <jwalden> | ugh |
| 20:46 | <oal> | I tried asking this in #html, but didn't really get any response, so: Is it semantically correct to make a table row an <a>? Or would I add an <a> in each cell? Screenshot of my table: http://i.imgur.com/W4ewO.png |
| 20:47 | <oal> | A row turns red on mouse hover, and is clickable. Not sure what's the best way to solve it though |
| 20:48 | <oal> | The only thing I got from #html was it's a bad idea, and you should never do it, but noone could tell me why not. |
| 20:49 | <TabAtkins_> | The parser doesn't allow you to put an <a> where a <tr> would go. |
| 20:50 | <SimonSapin> | what about an <a> with CSS display: table-row? |
| 20:50 | <TabAtkins_> | If it did allow you to do something like <table><a><tr><td>foo</tr></a></table>, though, it would be fien. |
| 20:50 | <TabAtkins_> | The parser doesnt' care about CSS. |
| 20:51 | <oal> | Hmm, how'd you solve it? |
| 20:52 | <TabAtkins_> | You need to use script. You might be able to wrap the <tr> in a <a> with JS and get the layout to still work out. Otherwise, just use an click handler on the <a>. |
| 20:52 | <TabAtkins_> | s/<a>/<tr>/ |
| 20:54 | <oal> | Thanks, I'll try that |
