| 01:17 | <benschwarz> | Whatup #WHATWG |
| 01:21 | <charlvn> | hi benschwarz |
| 01:25 | <paul_irish> | benschwarz: you see my w3schools doc? |
| 02:09 | <benschwarz> | paul_irish: I saw some mention of it on twitter |
| 02:09 | <benschwarz> | whats the score? |
| 02:09 | <paul_irish> | http://goo.gl/a8Bke it's gotten pretty big. basically a few pages of criticism of w3schools http://goo.gl/a8Bke |
| 02:09 | <paul_irish> | whoops |
| 02:12 | <benschwarz> | paul_irish: It'd be important to push the whole thing through sites like smashing mag, and ajaxian |
| 02:12 | <benschwarz> | importantly, smashing mag, and other bullshit sites |
| 02:12 | <paul_irish> | i will! |
| 02:12 | <paul_irish> | w3fools will debut at the end of next week. |
| 02:12 | <paul_irish> | splash hard. |
| 02:18 | <Philip`> | The current state of that document seems pretty incoherent and full of people overreacting |
| 02:21 | <bga_> | wow live edit |
| 02:28 | <benschwarz> | Hixie: !Ping |
| 02:29 | <benschwarz> | paul_irish: !ping |
| 02:43 | <benschwarz> | Philip`: Is the spec_splitter.py your work? |
| 02:43 | <benschwarz> | I'd like to highlight this issue that I'm seeing for developers.whatwg.org - https://github.com/benschwarz/developers.whatwg.org/issues/issue/4 |
| 05:45 | <MikeSmith> | http://starkravingfinkle.org/blog/2011/01/firefox-mobile-and-window-console-support/ |
| 05:45 | <MikeSmith> | "Desktop Firefox added native support for a subset of the window.console API" |
| 05:45 | <MikeSmith> | pretty cool |
| 09:57 | <MikeSmith> | so Firefox Mobile actually provides access to an error console? |
| 09:57 | <MikeSmith> | http://starkravingfinkle.org/blog/2011/01/firefox-mobile-and-window-console-support/ |
| 09:58 | <MikeSmith> | about newly added window.console support |
| 09:58 | <MikeSmith> | "Last night we turned on basic support in Firefox Mobile too. It’s basic in the sense that the window.console is merely forwarded to the Error Console." |
| 11:24 | <Philip`> | benschwarz: It is |
| 11:25 | <Philip`> | benschwarz: I guess the original document structure isn't quite what it expects when it's extracting elements |
| 11:25 | <Philip`> | (It's not designed to be particularly general-purpose or robust, since usually it's easier just to tweak the source code when the document structure changes) |
| 11:25 | <annevk> | http://www.youtube.com/watch?v=YVmtsErHBbs - "the ayes have it" |
| 11:25 | <annevk> | American politics... |
| 11:26 | <benschwarz> | Philip`: so if I make some fixes, should I send them upstream? |
| 11:26 | <benschwarz> | Or should I expect these things to get fixed magically? |
| 11:27 | <annevk> | lol, only Leif could get my <dl> comparison so backwards |
| 11:28 | <annevk> | I have a copy of spec-splitter somewhere too btw |
| 11:28 | <annevk> | a modified one |
| 11:29 | <annevk> | to generate whatwg.org/C |
| 11:29 | <annevk> | benschwarz, would be nicer if developers.whatwg.org was based on whatwg.org/C I think |
| 11:32 | <Philip`> | benschwarz: If the fixes don't break the non-developer multipage version, I can commit the changes to html5.googlecode.com |
| 11:32 | <Ms2ger> | annevk, apparently non-HTML5 parts of complete.html don't have .impl |
| 11:33 | <MikeSmith> | yeah |
| 11:34 | <MikeSmith> | Hixie said they don't have the domintro stuff yet either |
| 11:34 | <Ms2ger> | And that |
| 11:37 | <MikeSmith> | so I implemented checking of event-handler attributes |
| 11:37 | <MikeSmith> | not checked in yet |
| 11:37 | <MikeSmith> | pending review |
| 11:38 | <MikeSmith> | but at http://www.w3.org/html/check for testing |
| 11:38 | <MikeSmith> | but which I mean this part of the spec: |
| 11:38 | <MikeSmith> | http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#event-handler-content-attributes |
| 11:38 | <MikeSmith> | "Event handler content attributes, when specified, must contain valid JavaScript code matching the FunctionBody production. [ECMA262]" |
| 11:40 | <Ms2ger> | Nice |
| 11:41 | <MikeSmith> | one downside is that that if somebody drops a whole lot of javascript into the value of an event attribute, the error message is not going to be too helpful to that at pinpointing where the error is |
| 11:42 | <MikeSmith> | because it will not show the exact column number for the place in the attribute value where any actual syntax error is |
| 11:43 | <MikeSmith> | but I guess it's not really a best practice to put huge amounts of code into values of event-handler attributes to begin with |
| 11:43 | <MikeSmith> | nor maybe even to use event-handler attributes to begin with |
| 11:44 | <MikeSmith> | is there some benefit to using event-handler attributes rather than just adding listeners within the js code itself? |
| 11:45 | <MikeSmith> | cases where it's preferable/easier to do it that way for some reason? |
| 11:54 | <Ms2ger> | It's almost always easier, no? |
| 11:59 | <MikeSmith> | Ms2ger: I guess |
| 12:00 | <MikeSmith> | though seems like it would not easier in terms of maintenance |
| 12:01 | <Ms2ger> | Yes, but since when have web authors cared about that |
| 12:08 | <MikeSmith> | Ms2ger: yeah, true |
| 16:11 | <hsivonen> | Does Opera have an @-rule for site-specific stuff in user style sheets |
| 16:14 | <bga_> | opera has right click site preferenes view my style |
| 16:17 | <hsivonen> | bga_: thanks |
| 16:20 | hsivonen | wonders how many people have used time to figure out how to make the xkcd title attribute render withou mouseover |
| 16:21 | <hsivonen> | (also, kinda sad that Firefox is less suitable for reading Web comics than Opera due to the lack of Fast Forward) |
| 16:24 | <Ms2ger> | You mean like on http://damowmow.com/portal/? |
| 16:27 | <hsivonen> | Ms2ger: yeah, that's a solution to the problem if you read the Damowmow portal daily |
| 17:43 | <dglazkov> | Hixie: yo |
| 17:43 | <dglazkov> | or annevk |
| 17:43 | <dglazkov> | have a brain puzzler for you |
| 17:43 | <dglazkov> | it's about orientation |
| 17:45 | <dglazkov> | in WebKit, we have this -webkit-appearance property, which basically allows reaching into OS-specific representations of UI elements |
| 17:46 | <dglazkov> | for example, #foo { -webkit-appearance: slider-thumb-horizontal } will make <div id="foo"></div> render as the native OS slider thumb |
| 17:46 | <dglazkov> | (now I'll wait for you to ping back :) |
| 18:21 | <annevk> | dglazkov, don't know too much about it |
| 18:21 | <annevk> | dglazkov, except that I would like to see it standardized |
| 18:22 | <dglazkov> | annevk: me too! :) There's an interesting orientation problem here. I think I'll write an email instead of irc. |
| 18:22 | <dglazkov> | the problem today is that -webkit-appearance _dictates_ orientation |
| 18:22 | <dglazkov> | slider-thumb-horizontal will _always_ show horizontal thumb, and slider-thumb-vertical will _always_ show a vertical |
| 18:23 | <dglazkov> | which is wrong, because now I can't cascade orientation |
| 18:23 | <dglazkov> | but I should |
| 18:23 | <dglazkov> | be able |
| 18:23 | <dglazkov> | to |
| 18:23 | <dglazkov> | I will write email |
| 18:24 | <annevk> | cool |
| 18:38 | <bga_> | http://funkyimg.com/u2/826/670/vim8.png |
