Options:
- # Session Start: Sun Apr 15 00:00:00 2007
- # Session Ident: #whatwg
- # [00:00] <jdandrea> othermaciej: "oh my" the entire transcript @ http://krijnhoetmer.nl/irc-logs/xhtml/20070413
- # [00:00] <jdandrea> Just finished it. Wow. Interesting times ...
- # [00:00] <othermaciej> oh, right
- # [00:00] <othermaciej> yeah
- # [00:01] <othermaciej> well, all Gecko-based browsers total used to have less market share than Safari does now
- # [00:01] <othermaciej> and Safari's is growing
- # [00:01] <othermaciej> anyway, that guy is a tool
- # [00:06] <zcorpan> interesting view though. "i don't care about the existing content on the web, if it stops working then who cares? it was invalid anyway. let's make up a new perfect language with no defined error handling, which isn't a problem because there will be tools that produce perfect code and UAs won't accept non-compliant code."
- # [00:07] <zcorpan> "and this is handled with a new doctype."
- # [00:07] <zcorpan> (that's how i interpreted it, anyway)
- # [00:08] <jdandrea> I'm a (relatively) late arrival to the WHAT-WG myself, but I've been reading the docs backwards and forwards and taking it all in. I like what I see!
- # [00:08] <hsivonen> what's the business interest of ApTest in XHTML 2.0?
- # [00:08] <jdandrea> I wonder what the ratio of real-world HTML-to-CSS concerns is for MS. Even a ballpark figure.
- # [00:09] <othermaciej> I think IE7 has made them scared to change anything ever
- # [00:09] <jdandrea> hmm
- # [00:09] <jdandrea> Someone warn Molly.
- # [00:10] <othermaciej> I wonder how she would feel about Chris's stance on versioning
- # [00:10] <jdandrea> Bingo.
- # [00:10] <Dashiva> Frustrated?
- # [00:11] <zcorpan> perhaps cwilso is afraid of losing his job
- # [00:13] <zcorpan> (just speculating)
- # [00:14] <jdandrea> Has anyone read his "Albatross!" blog posts?
- # [00:14] <zcorpan> pointer?
- # [00:14] <jdandrea> "I should be really clear here – I don’t really want to be the chair of the HTML Working Group." http://blogs.msdn.com/cwilso/archive/2007/01/10/you-me-and-the-w3c-aka-reinventing-html.aspx
- # [00:14] <Dashiva> zcorpan: He did say he thought he was close after IE7
- # [00:14] <jdandrea> Though I may be quoting out of context. There's more to it ...
- # [00:15] <zcorpan> Dashiva: yeah, i meant that it might be the reason he wants versioning in ie
- # [00:15] <othermaciej> it's getting increasingly clear that he is not doing any actual chairing
- # [00:15] <zcorpan> jdandrea: yes i read it before
- # [00:15] <jdandrea> zcorpan: ahh, ok
- # [00:16] * jdandrea answers the clarion call of din-din - bbl ...
- # [00:16] * Quits: met_ (n=Hassman@r5bx220.net.upc.cz) ("Leaving")
- # [00:16] <Dashiva> He still hasn't explained how versioning is supposed to help when browser releases don't coincide with standard changes
- # [00:18] <othermaciej> if you think XHTML2 WG is crazy: http://news.yahoo.com/s/ap/20070413/ap_on_hi_te/rebuilding_the_internet
- # [00:18] * Parts: hasather_ (n=hasather@81-235-209-174-no62.tbcn.telia.com)
- # [00:19] <zcorpan> ha
- # [00:19] <othermaciej> forget replacing the web, how about replacing the whole internet?
- # [00:20] <zcorpan> why don't we move to another planet altogether?
- # [00:20] <othermaciej> a lot of Earth does not use proper semantic geography
- # [00:20] <othermaciej> so you have a good point there
- # [00:20] <othermaciej> we need a solar system that refuses to process planets which are not well-formed
- # [00:20] <zcorpan> i mean, the earth sucks, the only way to address security and mobility is to start from a clean slate
- # [00:21] <zcorpan> exactly
- # [00:23] * othermaciej is now known as om_errands
- # [01:24] <zcorpan> could we say that class names in html are case insensitive? (so that they match case insensitively in css) would it break any documents? (it is required for quirks mode, i'd presume)
- # [01:25] <zcorpan> or is that just considered a css quirk not in html's domain to fix?
- # [01:27] * om_errands is now known as othermaciej
- # [01:29] <othermaciej> zcorpan: they are case insensitive in quirks mode, but making them CI in quirks mode would likely break things
- # [01:29] <othermaciej> zcorpan: I don't know what non-CSS use of classes would be relevant here though
- # [01:30] <zcorpan> getElementsByClassName, getElementsBySelector
- # [01:30] <othermaciej> neither of those would be used in old content
- # [01:30] <othermaciej> so there's no need for compatibility workarounds
- # [01:31] <zcorpan> indeed
- # [01:31] <zcorpan> you said "but making them CI in quirks mode would likely break things" -- i don't follow, they already are CI in quirks mode
- # [01:31] <othermaciej> er
- # [01:31] <othermaciej> in strict mode I meant
- # [01:31] <zcorpan> ah
- # [01:32] <zcorpan> ok
- # [01:32] <zcorpan> so it's considered a css quirk then
- # [01:32] <othermaciej> you could make those APIs switch on quirks vs. strict mode, but I think that would be unhelpful
- # [01:33] <zcorpan> yeah
- # [01:34] <zcorpan> i'm just interested in having quirks mode specced...
- # [01:34] <zcorpan> most of the web rely on quirks
- # [01:35] <zcorpan> not speccing them means new vendors would have to reverse engineer others anyway
- # [01:36] <zcorpan> (implementing html5 and css21 would only work with standards mode content)
- # [01:38] <othermaciej> yes, although most quirks mode issues are CSS issues, not HTML
- # [01:38] <othermaciej> there are a few exceptions, mostly parsing issues
- # [01:38] <othermaciej> but I think many parsing quirks could safely be put in both modes
- # [01:40] <zcorpan> if not all, though that would perhaps also include <p><table> (could content rely on it being a child? how?)
- # [01:41] <zcorpan> why can't <p><table> parsing be dropped from quirks mode? is there an example page that relies on it?
- # [01:42] * Quits: hendry (n=hendry@91.84.53.136) ("leaving")
- # [01:42] <zcorpan> (either way, i'd like it to be parsed the same in both modes...)
- # [01:51] * Parts: hasather (n=hasather@81-235-209-174-no62.tbcn.telia.com)
- # [02:01] * Quits: Toolskyn (n=toolskyn@adsl-dc-266ef.adsl.wanadoo.nl) (Read error: 104 (Connection reset by peer))
- # [02:11] * Parts: Philip`` (n=philip@host86-137-69-141.range86-137.btcentralplus.com)
- # [02:14] * Quits: finnbo (n=finn@cpe-74-64-9-27.nyc.res.rr.com)
- # [02:26] * Joins: aroben (n=adamrobe@adsl-70-231-246-66.dsl.snfc21.sbcglobal.net)
- # [02:26] * Quits: aroben (n=adamrobe@adsl-70-231-246-66.dsl.snfc21.sbcglobal.net) (Remote closed the connection)
- # [02:27] * Joins: aroben (n=adamrobe@adsl-70-231-246-66.dsl.snfc21.sbcglobal.net)
- # [02:41] <zcorpan> so ms don't actually want to implement the spec. just use it as a guide and implement something near it. how depressing. and they are introducing more rendering modes that all other browsers will be forced to implement.
- # [02:43] <zcorpan> ...unless they become a minority vendor
- # [02:44] <zcorpan> in which case it's just a problem for them
- # [02:44] <jdandrea> ... and we instigate that by ... :)
- # [02:44] <jdandrea> I hear ya.
- # [02:45] <Lachy> I wonder if Chris would be willing to compromise on the versioning switch...
- # [02:45] <Lachy> Let the authors decide if they want the page to render according to IE[n] bugs when they write the page, or if they want to always render in the latest standards mode
- # [02:46] <zcorpan> that could work
- # [02:46] <Lachy> e.g. so <!DOCTYPE html> would always trigger the latest standards mode, but if the author adds some version switch, they get that versions
- # [02:46] <Dashiva> He would agree to that, I think. However, he argues that most/many/some authors would opt in without meaning to
- # [02:46] <Lachy> it's the lesser of two evils
- # [02:47] <Dashiva> After all, standards mode was supposed to be for standards, but now it's a frozen bug state
- # [02:48] <zcorpan> we should remember what standards are for... to foster interop
- # [02:50] <zcorpan> or a shortcut to get interop, if you will. without standards vendors could still reverse engineer each other to get interoperable
- # [02:50] <Lachy> ha! "Huh? Wrong about what, exactly?" -- Chris Wilson :-)
- # [02:56] * Parts: zcorpan (n=zcorpan@84-216-41-224.sprayadsl.telenor.se)
- # [03:11] * moeffju is now known as moeffju[ZzZz]
- # [03:18] * Quits: jdandrea (n=jdandrea@pool-72-79-33-202.nwrknj.east.verizon.net) ("ciao")
- # [03:45] * Quits: bzed (n=bzed@dslb-084-059-120-061.pools.arcor-ip.net) ("n8n8")
- # [04:02] * Joins: jdandrea (n=jdandrea@ool-44c0a1fe.dyn.optonline.net)
- # [04:44] * Quits: aroben (n=adamrobe@adsl-70-231-246-66.dsl.snfc21.sbcglobal.net)
- # [04:52] * Joins: aroben (n=adamrobe@adsl-70-231-246-66.dsl.snfc21.sbcglobal.net)
- # [04:52] * Quits: aroben (n=adamrobe@adsl-70-231-246-66.dsl.snfc21.sbcglobal.net) (Remote closed the connection)
- # [05:12] * Quits: jdandrea (n=jdandrea@ool-44c0a1fe.dyn.optonline.net) ("ciao")
- # [05:30] * Joins: droob (n=droob@24-107-20-80.dhcp.stls.mo.charter.com)
- # [05:39] * Quits: droob (n=droob@24-107-20-80.dhcp.stls.mo.charter.com)
- # [05:49] * Joins: polin8 (n=brian@ool-18b8cc06.dyn.optonline.net)
- # [05:53] * Joins: tantek (n=tantek@pool-71-105-209-8.lsanca.dsl-w.verizon.net)
- # [05:56] * mpt_ is now known as mpt
- # [06:02] * Joins: aroben (n=adamrobe@adsl-70-231-246-66.dsl.snfc21.sbcglobal.net)
- # [06:10] * Quits: csarven (n=nevrasc@modemcable081.152-201-24.mc.videotron.ca)
- # [06:19] * Joins: paulproteus (i=paulprot@29.145.221.202.bf.2iij.net)
- # [06:24] * Quits: polin8 (n=brian@ool-18b8cc06.dyn.optonline.net)
- # [07:13] * Quits: aroben (n=adamrobe@adsl-70-231-246-66.dsl.snfc21.sbcglobal.net)
- # [07:29] * Quits: tantek (n=tantek@pool-71-105-209-8.lsanca.dsl-w.verizon.net)
- # [07:30] * Joins: tantek (n=tantek@pool-71-105-209-8.lsanca.dsl-w.verizon.net)
- # [08:23] * Joins: hendry (n=hendry@91.84.53.136)
- # [09:08] * Quits: Lachy (n=Lachlan@124-168-27-56.dyn.iinet.net.au) (Read error: 104 (Connection reset by peer))
- # [09:15] * Joins: peepo (n=Jay@host86-129-174-162.range86-129.btcentralplus.com)
- # [09:19] * Joins: zcorpan (n=zcorpan@84-216-41-161.sprayadsl.telenor.se)
- # [09:20] * Joins: Lachy (n=Lachlan@124-168-27-56.dyn.iinet.net.au)
- # [09:54] * Joins: Toolskyn (n=toolskyn@adsl-dc-266ef.adsl.wanadoo.nl)
- # [10:01] <hsivonen> Lachy: do we have a mechanism for blacklisting commenter URLs on the WHATWG blog?
- # [10:01] * hsivonen deals with yet another einemillioneurohomepage spam
- # [10:04] * hsivonen finds the Akismet blacklist
- # [10:06] <hsivonen> hmm. I guess it is called Spam Karma 2
- # [10:06] <hsivonen> Lachy: how do Akismet and Spam Karma 2 interact?
- # [10:06] * Quits: Toolskyn (n=toolskyn@adsl-dc-266ef.adsl.wanadoo.nl) (Remote closed the connection)
- # [10:09] * Quits: zcorpan (n=zcorpan@84-216-41-161.sprayadsl.telenor.se) (Read error: 110 (Connection timed out))
- # [10:12] * Joins: Toolskyn (n=toolskyn@adsl-dc-266ef.adsl.wanadoo.nl)
- # [10:20] <gavins> Lachy: yt?
- # [10:22] <gavins> nm :)
- # [10:24] * Joins: ROBOd (n=robod@86.34.246.154)
- # [10:25] * Quits: peepo (n=Jay@host86-129-174-162.range86-129.btcentralplus.com) ("later")
- # [10:30] * gavins is now known as gavin
- # [10:43] <Lachy> hey
- # [10:45] <Lachy> hsivonen, those plugins seem to work well together. I'm not sure of the details, but if one doesn't catch the spam, the other generally does
- # [10:45] <Lachy> gavins, yes?
- # [10:45] <gavin> Lachy: I was going to ask where I could find "Lachy's #xhtml log", but I found it
- # [10:50] <Hixie> hsivonen: ask lachy
- # [10:54] * Quits: Toolskyn (n=toolskyn@adsl-dc-266ef.adsl.wanadoo.nl) (Remote closed the connection)
- # [10:55] * Joins: Toolskyn (n=toolskyn@adsl-dc-266ef.adsl.wanadoo.nl)
- # [11:16] * Joins: ravenn (n=ravenn@203-206-240-219.dyn.iinet.net.au)
- # [11:45] <hsivonen> Hixie: ask Lachy about spam?
- # [11:54] <Hixie> about the blog, yeah
- # [11:54] <Hixie> i don't admin it
- # [12:01] * Joins: met_ (n=Hassman@r5bx220.net.upc.cz)
- # [12:08] * Quits: ravenn (n=ravenn@203-206-240-219.dyn.iinet.net.au)
- # [13:42] * Joins: hasather (n=hasather@81-235-209-174-no62.tbcn.telia.com)
- # [15:29] * Joins: webben (n=benjamin@82.152.236.225)
- # [16:11] * Joins: hasather_ (n=hasather@81-235-209-174-no62.tbcn.telia.com)
- # [17:01] * Joins: briansuda (n=briansud@dsl-219-147.hive.is)
- # [17:04] * Quits: mw22 (n=chatzill@209.79.152.188) (Read error: 60 (Operation timed out))
- # [17:11] * Parts: hasather_ (n=hasather@81-235-209-174-no62.tbcn.telia.com)
- # [17:36] * Quits: briansuda (n=briansud@dsl-219-147.hive.is)
- # [17:50] * Joins: bzed (n=bzed@dslb-084-059-097-195.pools.arcor-ip.net)
- # [18:06] <gsnedders> what would be a good way to mark up a list of aims, and justifications behind those aims? a <dl>?
- # [18:09] <hsivonen> gsnedders: depends on the presentation you want
- # [18:09] * hsivonen hides
- # [18:11] <gsnedders> a numbered list of aims (so <ol>), with the justifications set off in a box out of line from the content (an <i>?)
- # [18:14] <gsnedders> I think really what I'm unsure about is how to mark up the justification… just another paragraph?
- # [18:19] * gsnedders settles on nested ol elements, combined with headers for each aim, with a paragraph(s) for the justification
- # [18:20] * Joins: mw22__ (n=chatzill@user-64-9-237-30.googlewifi.com)
- # [18:20] * mw22__ is now known as mw22
- # [18:35] * Joins: briansuda (n=briansud@dsl-219-147.hive.is)
- # [18:36] * Joins: csarven (n=nevrasc@modemcable081.152-201-24.mc.videotron.ca)
- # [18:37] * Quits: webben (n=benjamin@82.152.236.225) (Read error: 110 (Connection timed out))
- # [18:38] * Joins: webben (n=benjamin@82.152.236.225)
- # [18:47] * Quits: mw22 (n=chatzill@user-64-9-237-30.googlewifi.com) (Read error: 110 (Connection timed out))
- # [18:50] * Joins: Toolskyn88 (n=toolskyn@adsl-dc-266ef.adsl.wanadoo.nl)
- # [19:05] * Quits: Toolskyn (n=toolskyn@adsl-dc-266ef.adsl.wanadoo.nl) (Read error: 110 (Connection timed out))
- # [19:26] * Quits: briansuda (n=briansud@dsl-219-147.hive.is)
- # [20:17] * Joins: aroben (n=adamrobe@adsl-70-231-246-66.dsl.snfc21.sbcglobal.net)
- # [20:34] <hsivonen> http://seo.has.no.com/2007/04/seo-tip-for-html5/
- # [20:37] * Joins: polin8 (n=brian@ool-18b8cc06.dyn.optonline.net)
- # [20:49] * Joins: briansuda (n=briansud@dsl-219-147.hive.is)
- # [21:32] * Quits: aroben (n=adamrobe@adsl-70-231-246-66.dsl.snfc21.sbcglobal.net)
- # [21:36] * Quits: briansuda (n=briansud@dsl-219-147.hive.is)
- # [22:02] * Joins: peepo (n=Jay@host86-129-174-162.range86-129.btcentralplus.com)
- # [22:07] * othermaciej is now known as om_brunch
- # [22:07] * Quits: ROBOd (n=robod@86.34.246.154) ("http://www.robodesign.ro")
- # [22:10] * Joins: zcorpan (n=zcorpan@84-216-42-144.sprayadsl.telenor.se)
- # [22:36] * Quits: peepo (n=Jay@host86-129-174-162.range86-129.btcentralplus.com) ("later")
- # [22:40] * moeffju[ZzZz] is now known as moeffju
- # [22:44] * Joins: bewest (n=bewest@httpcraft/bewest)
- # [22:49] * bewest is wondering where to find the appropriate venue for feedback regarding http://www.w3.org/TR/2006/WD-web-forms-2-20060821/#form-submission
- # [22:50] * zcorpan points out that bewest isn't reading the most resent version of the spec
- # [22:51] * Joins: Philip`` (n=philip@host86-136-163-217.range86-136.btcentralplus.com)
- # [22:51] <zcorpan> but, since the html-wg haven't decided yet about adopting wf2 (might be mistaken here, still have 45 emails to read), -> whatwg list
- # [22:52] <bewest> that seems to be the most recent version
- # [22:52] <bewest> erm
- # [22:52] <zcorpan> it's the most resent WD
- # [22:52] <bewest> oh
- # [22:52] <bewest> should I be looking somewhere else?
- # [22:53] <zcorpan> http://whatwg.org/wf2
- # [22:53] <bewest> great
- # [22:54] <bewest> so whatwg mailing list is good?
- # [22:54] <hsivonen> would be nice to get the decision in the HTML WG...
- # [22:54] <hsivonen> bewest: yes
- # [22:54] <zcorpan> bewest: yes
- # [22:55] <bewest> hmm I should probably do some homework before posting
- # [22:56] <bewest> I'll do some searching as well, but can anyone recall any discussion around using some protocol to allow the application to communicate it's input expectations to the user agent, instead of doing strict type checking of input on the client side?
- # [22:57] <bewest> AFAICT the application will have to perform the validation routines again, anyway, since I don't see any mechanism for ensuring that incoming input has already been checked
- # [22:58] <hsivonen> bewest: yes, the server has to do it again, because it would be dangerous to trust stuff arriving over HTTP
- # [22:58] <bewest> right
- # [22:59] <bewest> and in addition, the format/type of input is probably some subset of requirements for validity for many applications, I would suspect
- # [23:30] * Joins: jdandrea (n=jdandrea@ool-44c0a1fe.dyn.optonline.net)
- # [23:42] * Joins: hasather_ (n=hasather@81-235-209-174-no62.tbcn.telia.com)
- # [23:57] * Quits: Toolskyn88 (n=toolskyn@adsl-dc-266ef.adsl.wanadoo.nl) (Read error: 104 (Connection reset by peer))
- # Session Close: Mon Apr 16 00:00:00 2007
The end :)