02:12 | <ajnewbold> | is it just me or does inline style not work when using the proposed <!DOCTYPE HTML> doctype? |
02:12 | <Dashiva> | Define does not work, and which browser? |
02:13 | <ajnewbold> | I was using firefox at work earlier, and now Safari here at home, and it seems like <div style="whatever"> is just being ignored |
02:13 | <ajnewbold> | the style within the quotes isn't applied to the element |
02:13 | ajnewbold | double-checks |
02:14 | <ajnewbold> | yeah, it's just ignored |
02:15 | <ajnewbold> | I've never used any doctype other than the html4 strict one, but with that the usual behavior was that any inline style overrode everything else |
02:16 | <Dashiva> | I'm not getting any problems at http://folk.ntnu.no/magnusrk/test/inline5.html |
02:16 | <ajnewbold> | hmm damn |
02:16 | <Hixie> | ajnewbold: i doubt it's the doctype doing it |
02:16 | <Hixie> | ajnewbold: do you have a test page we can look at? |
02:16 | <ajnewbold> | yep, http://newbold.name/ |
02:16 | <ajnewbold> | where it says "test" |
02:17 | <Dashiva> | size? |
02:17 | <ajnewbold> | it should be 5em unless I've done something stupid |
02:17 | <ajnewbold> | yeah |
02:17 | <ajnewbold> | I could have sworn I used to be able to do that |
02:17 | <Hixie> | 'size' isn't a css property :-) |
02:17 | <Hixie> | you want font-size i think |
02:17 | <ajnewbold> | oh |
02:17 | <ajnewbold> | OH |
02:17 | <ajnewbold> | BLAST |
02:17 | <ajnewbold> | sorry for the false alarm, then :D |
02:17 | <ajnewbold> | this is what happens when I go away from html for a while :( |
02:17 | <ajnewbold> | I come back thinking things have broken, when it's really just me |
02:18 | <Hixie> | hehe |
02:18 | <Dashiva> | http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fnewbold.name%2F&warning=1&profile=css21&usermedium=all |
02:18 | <Dashiva> | For later |
02:19 | <Dashiva> | I'm postively surprised they support more than just CSS2 now |
02:19 | <ajnewbold> | woo no errors |
02:19 | <ajnewbold> | go me |
02:24 | <ajnewbold> | so what's the future look like for html 5? |
02:24 | <ajnewbold> | will the w3c accept it? |
02:26 | <Hixie> | hasn't really been discussed yet |
02:26 | <ajnewbold> | I know this might sound like the stupidest comment ever, but.. |
02:26 | <ajnewbold> | I just want the w3c's validator to support it, once it's final :) |
02:27 | <Hixie> | yeah |
02:27 | <Hixie> | hsivonen is working on a validator |
02:27 | <ajnewbold> | ah, that takes care of that then |
02:28 | <ajnewbold> | hsivonen: will it do cool things like give helpful suggestions about how to fix problems? |
02:28 | <ajnewbold> | I remember an older version of the w3c's validator that was just downright unhelpful |
02:28 | <ajnewbold> | it'd be all "you forgot to close a tag somewhere, lol, good luck!" |
02:34 | <deltab> | it should check that its suggestions make sense, though |
02:35 | <Dashiva> | Well, if you have a non-closing <em> (automatic closing aside), is the checker supposed to analyze your text and estimate where you'd want to end it? :) |
02:37 | <deltab> | e.g. if you try to put a block in an inline context, it shouldn't say that you can only do that by putting it inside a button element, as the validator has done |
02:40 | <deltab> | nor close the inline context and forget about it, later finding and ignoring the end tag a couple of blocks down |
02:42 | <deltab> | i.e. treating <b><p>...</p><p>...</p></b> as <b></b><p>...</p><p>...</p> |
02:43 | <ajnewbold> | is <b><p>...</p><p>...</p></b> legal? |
02:44 | <deltab> | not in HTML4 |
02:44 | <ajnewbold> | is it in html 5? |
02:44 | <deltab> | I don't know |
02:44 | <ajnewbold> | it should be, because it's effin' cool |
02:44 | <deltab> | I realize the HTML5 parser algorithm tries to handle that sort of thing; it'd be useful for the validator to explain how the parsing went |
02:45 | <ajnewbold> | "Parsing your document went kind of poorly. You write HTML like it'd 1994." |
02:45 | <ajnewbold> | it's* |
02:45 | <deltab> | and, where possible, suggest *useful* (and not just *possible*) fixes |
02:45 | <ajnewbold> | I think it'd be great if it suggested books you could read |
02:45 | <ajnewbold> | or maybe even alternate career choices |
02:45 | <deltab> | heh |
02:46 | <deltab> | ^useful^sensible |
02:47 | <ajnewbold> | "Finished checking document: 782 errors found in 1,092 lines. Have you considered the very rewarding position of Waffle House line cook?" |
02:47 | <Dashiva> | On a scale from 1 to 10, you rate as Dreamweaver |
02:47 | <ajnewbold> | ouch! |
02:48 | <ajnewbold> | well, could be worse |
02:48 | <ajnewbold> | FrontPage. :P |
02:48 | <Lachy> | ajnewbold: <b><p>...</p></b> isn't legal because it wouldn't be completely compatible with the parsing requirements in all cases |
02:49 | <ajnewbold> | Lachy: aww :( |
02:49 | <ajnewbold> | it looked like fun |
02:49 | <ajnewbold> | or rather it reminded me of my first attempts at html, which were fun |
02:49 | <Lachy> | unfortunately, it's because of the way browsers have to handle it when the </p> is omitted |
02:50 | <ajnewbold> | I never understood the whole </p> omission thing |
02:50 | <ajnewbold> | I know it's legal, but damn does it feel weird |
02:50 | <Lachy> | see the adoption agency algorithm in the spec for more detail |
02:50 | <ajnewbold> | I've never brought myself to do it |
02:50 | <Lachy> | why? It's a convenient shorthand |
02:50 | <ajnewbold> | I can't really explain it |
02:50 | <karlUshi> | ajnewbold: in the early history of p semantics it was designed as a separator |
02:50 | <Lachy> | why should authors have to type</p> when its not necessary? |
02:50 | <ajnewbold> | Lachy: I don't know :( |
02:51 | <ajnewbold> | It's just an odd personal feeling of mine |
02:51 | <Lachy> | ajnewbold: it's probably because you've been seduced by the dark side of XHTML |
02:51 | <ajnewbold> | ironically, I haven't! |
02:51 | <karlUshi> | Lachy: it confuses people. :) it's because you are an old HTML cow |
02:51 | <karlUshi> | :p |
02:51 | <ajnewbold> | I despise X* |
02:51 | <Dashiva> | Typing </p> is like saying 'over' on the phone. It clarifies, but usually isn't necessary :) |
02:51 | <ajnewbold> | Dashiva: good analogy |
02:51 | <ajnewbold> | I still feel totally like I've screwed up if I leave it out, though :( |
02:51 | karlUshi | prefers to close his tags also because it helps me to understand my documents. |
02:52 | <karlUshi> | for my personal use, it is really a usability question |
02:52 | <Dashiva> | I always close my tags unless I'm doing a throw-away testcase or somesuch |
02:52 | <Dashiva> | But that's just the neat freak in me |
09:49 | <annevk> | "<b><p>test</p><p>test</p></b>" is handled just fine by HTML5 |
09:54 | <zcorpan> | omitting optional tags might take some getting used to at first, but i find it very effective. :) in particular it's faster to write markup. i've never made friends with auto-close features in editors |
09:55 | <annevk> | whoa, howcome posted an experimental version of Opera with <video> support online |
09:55 | <annevk> | cool |
09:55 | <Hixie> | been up for a while |
09:55 | <Hixie> | since last thursday |
09:55 | <annevk> | oh, didn't know |
09:59 | zcorpan | thinks css, xbl and media queries should cover all use-cases of onbeforeprint |
10:00 | <annevk> | they also cover all use cases for onmouseover |
10:02 | <zcorpan> | could be, but changing things for print is always presentational, is it not? |
10:03 | <zcorpan> | not that i'm strongly opposed to onbeforeprint or anything, though |
10:04 | <annevk> | onmouseover hopefully too |
10:04 | <annevk> | (but it's not) |
10:04 | annevk | doesn't really have a strong opinion either |
10:05 | <hsivonen> | It seems to me that the best realistic initial outcome with <video> is that Opera and Mozilla ship Ogg Theora support, Apple ships a generic QuickTime hook, Microsoft ships a generic hook for the Window Media framework and Xiph ships QuickTime and Windows Media framework extensions for Ogg Theora |
10:07 | <zcorpan> | that could work |
10:07 | hsivonen | doesn't believe that MS and Apple would ship Theora support initially |
10:08 | zcorpan | is off to Robertsfors to visit his mother for the weekend |
10:08 | <annevk> | see you |
10:08 | <zcorpan> | bye |
10:08 | <hsivonen> | bye |
10:21 | <MikeSmith> | hsivonen - would be interesting to hear from other browser vendors and device manufacturers about this |
10:21 | <annevk> | Nokia said no |
10:21 | <MikeSmith> | Access NetFront, Openwave, Teleca Obigo, Infraware |
10:47 | <hsivonen> | MikeSmith: yes. |
10:55 | <MikeSmith> | lots of mobile browsers out there ... |
10:56 | <MikeSmith> | Infraware is on 70 percent of the handsets in Korea |
10:56 | <MikeSmith> | NetFront is in PSP, lots of other devices |
11:03 | <hsivonen> | I was rather unimpressed by the PSP browser |
11:04 | <MikeSmith> | UI compared to Nintendo DS is not so great |
11:04 | <hasather> | I did some testing of the PSP browser when it came out. I was also very unimpressed |
11:05 | <MikeSmith> | because unilike DS, PSP has no pen input/touchscreen |
11:05 | <MikeSmith> | pen makes browsing a lot easier |
11:05 | <MikeSmith> | on that kind of device |
20:22 | <Hixie> | who's running the forums? |
20:23 | <fax_machine> | there are forums? |
20:24 | <fax_machine> | oh, there ARE forums |
20:24 | fax_machine | realizes he's never actually seen the front page of the WHATWG web site before |
20:24 | <Hixie> | heh |
20:25 | <fax_machine> | nice colors, btw |
20:25 | <Hixie> | hehe |
20:25 | <fax_machine> | er |
20:25 | <fax_machine> | is the word "The" supposed to be behind the word "Web"? |
20:26 | <fax_machine> | top-left corner of the front page |
20:26 | <Hixie> | yes |
20:26 | <fax_machine> | ah ok |
20:26 | <fax_machine> | good then :) |
20:26 | <Hixie> | though it's funny how many people ask that |
20:26 | <fax_machine> | well, to us lay people with no design skills, it almost looks like a mistake |
20:26 | <gsnedders> | I mean, no part of how HTML works is a mistake :P |
20:27 | <fax_machine> | and of course the first thought is "omg they made a mistake lol" or "oh crap does my browser suck?" |
20:27 | <fax_machine> | it's interesting |
20:27 | <fax_machine> | in Opera, it looks best |
20:27 | <fax_machine> | there's enough of the "The" poking up above the "Web" that the effect looks really good |
20:28 | <fax_machine> | in Safari and Camino it looks like a mistake :P |
20:28 | <gsnedders> | probably due to Opera rounding down numbers |
20:28 | <fax_machine> | heh, Opera always makes things look better :) |
20:28 | <fax_machine> | I should use it more |
20:34 | <fax_machine> | heh, does Anne van Kesteren ever come here? |
20:34 | <gsnedders> | as annevk |
20:34 | <gsnedders> | often |
20:34 | <fax_machine> | cool |
20:34 | <fax_machine> | I totally need to tell her that I love that pic on her site |
20:34 | <fax_machine> | the "Standards Suck" guy |
20:34 | <gsnedders> | *his site |
20:35 | <gsnedders> | *tell him |
20:35 | <fax_machine> | ah yeah |
20:35 | <fax_machine> | first I have to remove my foot from my mouth |
20:35 | <gsnedders> | he goes as anne on irc.w3.org |
20:35 | <fax_machine> | and become exposed to a bit more global culture, evidently |
20:35 | <gsnedders> | even in en, Anne is a gender neutral name |
20:35 | <fax_machine> | in en, maybe, but not in the USA |
20:36 | <fax_machine> | a man named Anne here wouldn't make it past 1st grade in school :( |
20:36 | <gsnedders> | I mean in the English language |
20:36 | <fax_machine> | I know |
20:36 | <gsnedders> | It's rare, but it exists. |
20:36 | <fax_machine> | but as you surely know, we don't really use the English language over here :P |
20:36 | <gsnedders> | of course :) |
20:36 | <fax_machine> | we speak in vomit-like tongues, a mixture of oblivious richness and SUV exhaust |
20:37 | <gsnedders> | it's most common in North Germanic languages as a male name |
20:38 | <gsnedders> | well, nowadays |
20:38 | <fax_machine> | interesting |
20:38 | <gsnedders> | there've been times when it's been predominantly male in en |
20:38 | <fax_machine> | I believe it |
20:38 | <fax_machine> | there've been times when men were the predominant knitters, as well :) |
20:38 | <fax_machine> | (early 1600s) |
20:39 | <gsnedders> | there've been times when 14 year olds are involved in developing standards… |
20:39 | <gsnedders> | wait, that's now. |
20:40 | <fax_machine> | heh |
20:41 | <fax_machine> | I know of a 12-year old who contributed significantly to PHP's earlier version 4 releases |
20:41 | <gsnedders> | heh |
20:41 | gsnedders | has a strong dislike of PHP |
20:41 | <gsnedders> | parts because of how the developers behave |
20:41 | <fax_machine> | yeah :( |
20:42 | <gsnedders> | I had to report a bug twice to get it fixed, once told that what PHP did following the spec, despite me saying it didn't |
20:42 | <gsnedders> | the second time I cited the specific sections of the spec |
20:42 | <fax_machine> | hehe |
20:42 | <fax_machine> | yeah, you shouldn't have to do that |
20:42 | <gsnedders> | the devs should go look the spec up themselves when they are told it breaks the spec. |
20:42 | <fax_machine> | I hate it when developers get defensive |
20:42 | <gsnedders> | I shouldn't have to. |
20:42 | <fax_machine> | exactly |
20:42 | <fax_machine> | well, they just assumed that they were right |
20:43 | <fax_machine> | it's a very arrogant attitude |
20:43 | <gsnedders> | F/OSS run as a dictatorship only works with a good strong dictator |
20:43 | <fax_machine> | :) |
20:44 | gsnedders | doesn't want to put the current release of SimplePie through all the new unit tests |
20:44 | <gsnedders> | I'd hate to see how badly it does |
20:45 | <fax_machine> | what's SimplePie? |
20:45 | <gsnedders> | <http://simplepie.org/> |
20:45 | <gsnedders> | written in PHP, ironically :) |
20:45 | <fax_machine> | ah |
20:45 | <fax_machine> | that looks neat |
20:47 | <gsnedders> | http://diveintomark.org/archives/2004/08/16/specs – sometimes I think I fall a bit too much into the "Asshole" category |
20:48 | fax_machine | is a "moron" |
20:48 | gsnedders | used to be a total one |
20:49 | <gsnedders> | specs! peh! they make no sense! all too technical! |
20:49 | <gsnedders> | now I can read specs without thinking about it :P |
20:50 | <fax_machine> | I guess I might be a super-moron |
20:50 | <fax_machine> | not only have I traditionally ignored specs, but I've ignored standards too :P |
20:50 | <fax_machine> | only recently have I taken an interest in standards |
20:51 | gsnedders | sadly got caught by those who say XHTML > HTML |
20:51 | <gsnedders> | now as someone who has actually read specs and understood them, it's just wrong. |
20:52 | <fax_machine> | I've only seen maybe one or two sites done in XHTML that (a) used the right content-type, and (b) really actually made use of any of xhtml's features that aren't available in plain old html |
20:52 | gsnedders | sighs… |
20:52 | <fax_machine> | my theory is that 99% of developers who use xhtml do so simply because they think it's the newer, and therefore better, markup |
20:53 | <gsnedders> | I have a whole book of English past paper beside me |
20:53 | <gsnedders> | I'm really tempted to do one of the writing ones |
20:53 | <fax_machine> | does Mark Pilgrim ever chat in here |
20:54 | <Dashiva> | I'm sure some of them just let the editor/cms/whatever add the doctype |
20:54 | <hasather> | fax_machine: it happens |
20:54 | <gsnedders> | as markp |
20:54 | <fax_machine> | hsivonen: is he as clever and funny here as he is on his blog? |
20:55 | <hasather> | fax_machine: I think you meant that for me. Dunno really, haven't seen him talk much |
20:55 | gsnedders | tries not to laugh at one of the tasks – "Television shows such as Pop Idol do more harm than good. Discuss." |
20:55 | <gsnedders> | he barely talks |
20:56 | <gsnedders> | I've talked to him once, but all about rather complex stuff with both of us busy, little time for jokes |
20:56 | <fax_machine> | hasather: heh yes, I did mean that for you :) |
20:58 | <gsnedders> | time to write yet another essay, this time fiction, unlike the last <http://geoffers.uni.cc/archives/2007/04/06/new-people-in-new-surroundings/> |
20:59 | <fax_machine> | "Questioning me as to what colour her bra is, I answer honestly. It’s black, and rather visible through her thin white shirt." |
20:59 | fax_machine | keeps reading :) |
21:00 | <gsnedders> | fax_machine: it's completely true. It's written in the first person with reason. :) |
21:00 | <fax_machine> | hehe |
21:00 | <fax_machine> | dude, you told her no :( |
21:00 | <gsnedders> | I didn't then |
21:00 | <fax_machine> | you could have totally scored |
21:00 | <gsnedders> | too ill then anyway |
21:01 | <fax_machine> | ah :( |
21:01 | <gsnedders> | only really been well enough since Dec |
21:01 | <fax_machine> | well |
21:01 | <gsnedders> | just been too shy and cowardly since |
21:01 | <fax_machine> | what are you waiting for? |
21:01 | <fax_machine> | ah |
21:01 | <fax_machine> | you can fix that |
21:02 | gsnedders | starts writing an essay about a homosexual relationship, non-fiction, this time |
21:02 | <fax_machine> | try very hard to get a glimpse of the sort of live you might envision having that would involve her, and then ask yourself how much more of your life you're going to waste before you make that vision a reality :) |
21:02 | <fax_machine> | s/live/life/ |
21:02 | <gsnedders> | she's so much older than me, though… |
21:02 | <fax_machine> | pfft, meaningless |
21:03 | <fax_machine> | it's only an issue if you make it one |
21:03 | <gsnedders> | if I overheard what her friends were saying once in another class, she's over two years older than me |
21:03 | <fax_machine> | how old are you? |
21:03 | <gsnedders> | 14, 15 in 2 weeks |
21:03 | <fax_machine> | heh :) |
21:03 | <gsnedders> | she's already 17, since Mar |
21:03 | <fax_machine> | My wife and I met in high school |
21:04 | <fax_machine> | and when I was 14, she was 17 (but I turned 15 shortly after that) |
21:04 | <fax_machine> | we're 2 years and 2 months apart in age |
21:04 | <gsnedders> | I've been moved up a year, her, from what I heard, down one (or maybe she started a year late) |
21:04 | <fax_machine> | now I'm 27 and she's 29 and we're as happy as anyone could ever be :) |
21:05 | <fax_machine> | when you're 14/15, 2 years can feel like a really big deal |
21:05 | gsnedders | has been ill for a quarter of his life, missed years of school (literally), and still manages to be moved up a year and do very very well |
21:05 | <fax_machine> | but trust me, with every year that passes, it becomes less significant |
21:05 | <fax_machine> | gsnedders: that's awesome |
21:05 | <fax_machine> | you've definitely got something great going on there |
21:05 | <othermaciej> | the HTML WG is continuing to get less fun |
21:06 | gsnedders | has been in web dev since age… 11 (and I mean by that actually hand coding) |
21:06 | <fax_machine> | now, get the girl and live happily ever after :) |
21:06 | <gsnedders> | othermaciej: totally. |
21:06 | <gsnedders> | othermaciej: codec arguments, questions about <canvas>… ugh. |
21:06 | <fax_machine> | sounds like #web |
21:07 | <gsnedders> | just on a far more technical level |
21:07 | <Dashiva> | othermaciej: Is it reality setting in? |
21:07 | <othermaciej> | Dashiva: it's more of the parties who do not share the WHATWG rough consensus coming to the table |
21:08 | <Dashiva> | I also feel there's an air of "we're at the w3c now, and we do things this way" in some of the dialogue |
21:08 | <gsnedders> | I think the questions about <canvas> are pointless. It already has three stable implementations. |
21:09 | <Hixie> | haven't got to those yet |
21:09 | <Hixie> | i'm still trying to deal with the versioning issue |
21:09 | <Philip`> | There are at least two more (Rhino Canvas and KHTML), though I have no idea whether they count as stable |
21:09 | <Hixie> | ex-canvas, too |
21:10 | <Philip`> | Oh, that too |
21:11 | <gsnedders> | fax_machine: pm? |
21:11 | <fax_machine> | gsnedders: sure, go for it |
21:12 | <Philip`> | though it doesn't seem fair to call it stable either, since most features are buggy or missing (and presumably impossible with the limits of VML) |
21:19 | <Philip`> | Given the lack of extreme enthusiasm for <canvas>, it would seem sensible to avoid bringing up the issue of an OpenGL canvas in the HTML WG - that's probably best left to implementors and the WHATWG for now :-) |
21:20 | <Hixie> | opengl canvas is only missing one thing |
21:20 | <Hixie> | someone who knows opengl, who knows how to write neat simple js apis, and who can write specs |
21:21 | <othermaciej> | I am not sure such a mythical person exists |
21:22 | <Hixie> | well i can do the last one, and i'm not too bad at the middle one when i have people reviewing the apis to point out improvements, the first one is my problem. failing all else, i'll have to go on a 3d/opengl crash course. |
21:23 | <Philip`> | At least all the complicated graphical stuff can be left in the OpenGL spec - probably the only place where the 3D canvas interacts with actual graphics is when loading textures, and the rest is a wrapper API |
21:23 | <Philip`> | (unlike the 2D canvas, where the rendering has to be defined) |
21:24 | <othermaciej> | OpenGL is not a very friendly API to use directly |
21:24 | <othermaciej> | so a very literal-mided wrapper would probably not work so well |
21:25 | <Philip`> | Would it be sensible to leave user-friendly APIs to other non-standards people, where they can just implement wrappers in JavaScript and users can decide which one works best? |
21:28 | <Philip`> | (though I think the canvas should at least provide a way to efficiently load arrays of numbers into GL vertex-arrays, since that was the slowest bit when I tried loading models into the Firefox canvas3d extension some time ago - so that's probably the kind of place where the design gets more complex) |
21:32 | <hsivonen> | I guess it is hard to get people to agree on anything higher-level than OpenGL |
21:32 | <Hixie> | nah |
21:33 | <hsivonen> | Considering that the 2D abstraction is basically filling and stroking bézier paths, I don't think OpenGL is too low-level |
21:33 | <Hixie> | who runs the forums, anyone remember? |
21:33 | <Hixie> | i have a support request from someone |
21:33 | <Hixie> | was it zcorpan? |
21:33 | <hsivonen> | Hixie: it's zcorpan and he left |
21:33 | <hsivonen> | (for the weekend, that is) |
21:33 | <Hixie> | k |
21:34 | <Hixie> | i'll forward it to him |
21:34 | <hsivonen> | fax_machine: Regarding the conformance checker question last night: No, the conformance checker is not helpful in its current version. I do have plans on how to make it more helpful, though. |
21:34 | <fax_machine> | hsivonen: sweet |
21:35 | <othermaciej> | hsivonen: I don't think the basic ideas are too low-level, but some of the details of OpenGL APIs are |
21:35 | <othermaciej> | dunno, it's been a couple of years since I did any OpenGL programming |
21:36 | <hsivonen> | I haven't done OpenGL programming since 2002 |
21:36 | <hsivonen> | I'm assuming that whatever was available on SGI O2 then is now available in OpenGL ES :-) |
21:39 | <othermaciej> | hey KevinMarks |
21:41 | <Philip`> | OpenGL ES has been stripped of lots of the old OpenGL stuff - even basic things like immediate-mode Begin/Vertex/End and display lists - so it's probably not quite like old OpenGL programmers would remember :-) |
21:43 | <KevinMarks> | hi om |
21:47 | <hsivonen> | Philip`: ok. I haven't really taken a close look at OpenGL ES. |
22:26 | <fax_machine> | sheesh |
22:26 | <fax_machine> | my cable company sucks |