Options:
- # Session Start: Thu Feb 14 00:00:00 2008
- # Session Ident: #html-wg
- # [00:08] * Quits: hober (ted@68.101.220.172) (Quit: ERC Version 5.3 (IRC client for Emacs))
- # [00:11] * Joins: gsnedders (gsnedders@86.151.228.75)
- # [00:29] * Joins: hober (ted@68.101.220.172)
- # [01:07] * Quits: aroben (aroben@76.111.161.30) (Quit: aroben)
- # [01:21] * Quits: billmason (billmason@69.30.57.129) (Connection reset by peer)
- # [01:47] * Quits: jgraham (james@81.86.211.105) (Quit: I get eaten by the worms)
- # [01:47] * Quits: hober (ted@68.101.220.172) (Quit: ERC Version 5.3 (IRC client for Emacs))
- # [02:17] * Quits: ryan (ryan@66.92.219.50) (Ping timeout)
- # [02:39] * Quits: dbaron (dbaron@63.245.220.228) (Quit: 8403864 bytes have been tenured, next gc will be global.)
- # [02:42] * RRSAgent excuses himself; his presence no longer seems to be needed
- # [02:42] * Parts: RRSAgent (rrs-loggee@128.30.52.30)
- # [02:42] * Joins: DanC_lap (connolly@128.30.52.30)
- # [02:48] * Joins: dbaron (dbaron@63.245.220.241)
- # [03:07] * Joins: rking3 (rking3@66.92.2.56)
- # [03:09] * Quits: rking3 (rking3@66.92.2.56) (Quit: rking3)
- # [03:17] * Quits: adele (adele@17.255.111.236) (Quit: adele)
- # [03:50] * Quits: tH (Rob@87.102.19.166) (Quit: ChatZilla 0.9.80-rdmsoft [XULRunner 1.8.0.9/2006120508])
- # [04:06] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
- # [05:48] * Joins: aaronlev (chatzilla@65.78.0.149)
- # [06:30] * Joins: adele (adele@67.170.232.64)
- # [07:28] * Quits: dbaron (dbaron@63.245.220.241) (Quit: 8403864 bytes have been tenured, next gc will be global.)
- # [07:55] * Quits: gavin (gavin@99.253.193.147) (Quit: gavin)
- # [08:01] * Joins: gavin (gavin@99.253.193.147)
- # [08:23] * Quits: sbuluf (iva@200.49.132.83) (Quit: sbuluf)
- # [08:43] * Quits: shepazu (schepers@128.30.52.30) (Quit: shepazu)
- # [08:44] * Quits: heycam (cam@125.255.47.56) (Quit: bye)
- # [09:15] <hsivonen> Hixie: ok (rel value thing)
- # [09:41] * Quits: adele (adele@67.170.232.64) (Quit: adele)
- # [10:15] * Quits: paullewis (paullewis@82.242.109.217) (Quit: paullewis)
- # [10:21] * Joins: ROBOd (robod@89.122.216.38)
- # [10:33] * Joins: jgraham (james@81.86.211.105)
- # [10:51] * Quits: Lachy (Lachlan@84.215.54.100) (Quit: This computer has gone to sleep)
- # [11:02] * Joins: paullewis (paullewis@81.255.115.137)
- # [11:05] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Quit: Less talk, more pimp walk.)
- # [11:24] * Joins: Lachy (Lachlan@213.236.208.22)
- # [11:32] <hsivonen> SMIL Timesheets aren't attracting comments http://lists.w3.org/Archives/Public/www-smil/2008JanMar/
- # [11:41] <anne> hopefully they do something with that information
- # [11:43] <hsivonen> btw, failure to adhere to the principle of least suprise is bad. I get a steady stream of incoming links from people who have had their design broken by the PNG gamma stuff and who have then googled and found my page.
- # [12:08] * Joins: shepazu (schepers@128.30.52.30)
- # [12:27] * Joins: Julian (chatzilla@217.91.35.233)
- # [12:30] * Joins: myakura (myakura@123.224.247.98)
- # [12:30] * Joins: tH_ (Rob@87.102.19.166)
- # [12:31] * tH_ is now known as tH
- # [13:27] * Joins: kwijibo (kwijibo@87.113.10.93)
- # [14:03] * Joins: olivier (ot@128.30.52.30)
- # [14:23] * Quits: DanC_lap (connolly@128.30.52.30) (Quit: bath an nap for this machine)
- # [14:36] * Quits: kwijibo (kwijibo@87.113.10.93) (Quit: kwijibo)
- # [14:41] * Quits: aaronlev (chatzilla@65.78.0.149) (Client exited)
- # [14:50] * Quits: Shunsuke (Shunsuke@123.176.107.50) (Connection reset by peer)
- # [14:52] * Joins: Shunsuke (Shunsuke@123.176.107.50)
- # [15:10] <anne> Julian, http://nedbatchelder.com/blog/200704/xss_with_utf7.html
- # [15:10] <anne> (through Google)
- # [15:12] * Joins: matt (matt@128.30.52.30)
- # [15:12] * Quits: olivier (ot@128.30.52.30) (Quit: This computer has gone to sleep)
- # [15:13] * Joins: olivier (ot@128.30.52.30)
- # [15:16] <Julian> Anne, thanks. Ironically, none of the four major UAs I tried seem to be vulnerable (tried with http://nedbatchelder.com/utf7.html)
- # [15:16] <anne> Well, they have probably been patched
- # [15:17] <anne> well, IE
- # [15:17] <anne> we should probably drop support for UTF-7 altogether for Web content if that's feasible
- # [15:17] <hsivonen> Julian: Minefield is vulnerable when combined with social engineering
- # [15:18] <Julian> Henri, is that also related to UTF-7?
- # [15:18] <hsivonen> social engineering being: "To view these scandalous images, please select View > Character Encoding > More Encodings > Unicode > UTF-7
- # [15:18] <anne> Opera is too, it seems
- # [15:19] * Quits: olivier (ot@128.30.52.30) (Quit: Leaving)
- # [15:19] <gsnedders> Julian: Mosaic was the UA that ignored ;charset=, but everything else has copied it, as content depends upon it, so effectively it's 100% of modern UAs
- # [15:20] <gsnedders> (I'll send a proper reply to ietf-http-wg later)
- # [15:21] <Julian> I think we need test cases.
- # [15:21] <Julian> Does the UTF-7 issue in Mozilla (the encoding available through the UI as override) have an issue#?
- # [15:23] <hsivonen> IIRC, it does
- # [15:23] <hsivonen> let's see
- # [15:24] <hsivonen> https://bugzilla.mozilla.org/show_bug.cgi?id=406777
- # [15:24] <hsivonen> see also https://bugzilla.mozilla.org/show_bug.cgi?id=408457
- # [15:24] <hsivonen> and https://bugzilla.mozilla.org/show_bug.cgi?id=414064
- # [15:25] <anne> that's not a problem with HTTP though
- # [15:25] <anne> which may be what Julian is after
- # [15:26] <anne> that's more a UI issue or an issue with supporting UTF-7 in the first place (HTML5 forbids it)
- # [15:26] <Julian> Well, it's not HTTP's problem, except for servers apparently labeling content as ISO-8859-1 to prevent content sniffing to happen; so working around UA bugs.
- # [15:27] <anne> no
- # [15:27] <anne> UI override always works
- # [15:27] <hsivonen> UTF-7 is not a bug. it's a misfeature
- # [15:27] <anne> and there are no UA bugs as you verified yourself with regards to sniffing
- # [15:27] * Joins: kwijibo (kwijibo@87.113.10.93)
- # [15:31] <Lachy> I wonder if there are any legitimate sites that use UTF-7, which would break if UAs dropped support for it?
- # [15:31] <Lachy> although, it's a really pointless encoding to use
- # [15:33] <Philip> There's a number of emails with utf-7 attachments, so any web-based mail reader with direct links to attachments would break
- # [15:35] <hsivonen> Philip: there are already other reasons to sanitize attachments in webmail
- # [15:37] * Joins: aaronlev (chatzilla@65.78.0.149)
- # [15:44] * Quits: myakura (myakura@123.224.247.98) (Quit: Leaving...)
- # [15:48] * Joins: aroben (aroben@76.111.161.4)
- # [15:56] * Quits: Lachy (Lachlan@213.236.208.22) (Quit: Leaving)
- # [16:00] * Joins: Lachy (Lachlan@213.236.208.22)
- # [16:02] * Joins: tH_ (Rob@87.102.19.166)
- # [16:02] * Quits: tH (Rob@87.102.19.166) (Connection reset by peer)
- # [16:02] * tH_ is now known as tH
- # [16:31] * Joins: billmason (billmason@69.30.57.129)
- # [16:40] * Quits: Philip (philip@80.177.163.133) (Ping timeout)
- # [16:42] * Joins: Philip (philip@80.177.163.133)
- # [16:56] * Quits: Lachy (Lachlan@213.236.208.22) (Quit: This computer has gone to sleep)
- # [17:08] * Joins: Lachy (Lachlan@84.215.54.100)
- # [17:16] * Quits: kwijibo (kwijibo@87.113.10.93) (Quit: kwijibo)
- # [17:35] * Joins: kwijibo (kwijibo@87.113.10.93)
- # [17:42] * Joins: Sander (svl@86.87.68.167)
- # [17:57] * Joins: MattRaymond (mraymond@70.147.81.16)
- # [17:59] <MattRaymond> Can someone remind me how this phone + IRC thing works?
- # [18:00] <anne> the meeting today is in six hours or so, fwiw
- # [18:01] <anne> but typically you do "Zakim, passcode?" and it gives you a list of phone numbers and the conference code
- # [18:01] <MattRaymond> Oh, okay. I didn't see where it said it was at 7pm EST.
- # [18:02] * Quits: MattRaymond (mraymond@70.147.81.16) (Quit: ChatZilla 0.9.80 [Firefox 2.0.0.12/2008020121])
- # [18:04] * Quits: paullewis (paullewis@81.255.115.137) (Quit: paullewis)
- # [18:38] * Joins: paullewis (paullewis@82.242.109.217)
- # [18:48] * Quits: Julian (chatzilla@217.91.35.233) (Quit: ChatZilla 0.9.80 [Firefox 2.0.0.12/2008020121])
- # [19:13] * Joins: timbl (timbl@128.30.6.254)
- # [19:14] * Joins: dbaron (dbaron@67.160.251.228)
- # [19:25] * Joins: adele (adele@17.203.15.207)
- # [19:31] * Joins: alexf (alejandro@85.152.42.1)
- # [19:32] * Parts: alexf (alejandro@85.152.42.1)
- # [19:34] * Joins: alexf (alejandro@85.152.42.1)
- # [19:34] * Parts: alexf (alejandro@85.152.42.1)
- # [19:47] * Quits: matt (matt@128.30.52.30) (Quit: matt)
- # [19:56] * Joins: hober (ted@68.101.220.172)
- # [19:57] * Joins: matt (matt@128.30.52.30)
- # [20:17] * Quits: aaronlev (chatzilla@65.78.0.149) (Ping timeout)
- # [20:40] * Joins: DanC_lap (connolly@128.30.52.30)
- # [20:41] * DanC_lap tunes in briefly...
- # [20:41] <DanC_lap> hixie? did you see a question about why the sniffing rules are a MUST?
- # [20:41] * DanC_lap hunts for pointer...
- # [20:43] <DanC_lap> http://lists.w3.org/Archives/Public/public-html/2008Jan/0214.html Mark Baker asking "what is accomplished by making it normative exactly?"
- # [20:44] <DanC_lap> JR cites that in his investigation in collaboration with the IETF HTTP WG http://lists.w3.org/Archives/Public/public-html/2008Feb/0099.html
- # [20:44] <DanC_lap> hmm... quiet around here.
- # [20:53] * Parts: timbl (timbl@128.30.6.254)
- # [21:02] * Quits: hober (ted@68.101.220.172) (Quit: ERC Version 5.3 (IRC client for Emacs))
- # [21:42] * Quits: dbaron (dbaron@67.160.251.228) (Quit: 8403864 bytes have been tenured, next gc will be global.)
- # [21:50] * Quits: shepazu (schepers@128.30.52.30) (Quit: shepazu)
- # [22:00] * Quits: ROBOd (robod@89.122.216.38) (Quit: http://www.robodesign.ro )
- # [22:00] * Joins: Julian (chatzilla@80.143.156.62)
- # [22:16] <Hixie> DanC_lap: yeah, i thought maciej and boris had answered that satisfactorily so i figured i'd rather not add to the noise (e.g. http://lists.w3.org/Archives/Public/public-html/2008Jan/0264.html )
- # [22:18] <DanC_lap> ah, well, an answer from the editor is different. but now I have one; thanks.
- # [22:20] <Julian> I don't think the security argument works -- not doing sniffing should be at least as secure as doing sniffing.
- # [22:21] <Hixie> right, the security argument is that _if_ sniffing happens, then it must happen as per the spec
- # [22:21] <Julian> I think I agree with the desire that everybody who *does* implement sniffing does it the same way, though.
- # [22:21] <anne> is sniffing optional, but if implemented it MUST be done in a certain way currently?
- # [22:22] <Hixie> right now i think it is just a must
- # [22:22] <anne> might be good to change
- # [22:22] <Julian> But, as far as I recall (and as pointed out by Frank E. I think), the spec doesn't guarentee that anyway because it doesn't say excatly how many octets need to be considered.
- # [22:22] <Julian> Anne: exactly.
- # [22:22] <Julian> Anne: that would allow recipients how *want* to stick to mime-respect can do that.
- # [22:23] <Julian> Anne: it would also make UAs compliant that allow disabling sniffing.
- # [22:23] <Hixie> sadly we can't define how many bytes must be considered
- # [22:23] <gsnedders> Hixie: why not?
- # [22:23] <Julian> Hixie: well, unless you specify a really small amount, right?
- # [22:23] <Hixie> the really small amount would have to be 1 byte
- # [22:23] <Julian> Why 1?
- # [22:23] <Hixie> gsnedders: imagine a server that sends one byte then waits a minute
- # [22:24] <gsnedders> ah.
- # [22:24] <Julian> Hixie: that's a problem anyway; no matter whether you do sniffing or not, right?
- # [22:24] <Hixie> depends what the context is
- # [22:25] <anne> that behavior also makes encoding sniffing non-deterministic at the moment
- # [22:25] <anne> i don't really like that
- # [22:25] <Hixie> i don't like sniffing full stop
- # [22:25] <Hixie> sadly it's not really about what we like
- # [22:25] <Julian> I think that's why RoyF has proposed a concrete number of octets.
- # [22:25] <Hixie> the spec used to require 512
- # [22:25] <Julian> (for charset sniffing in HTTP)
- # [22:25] <Hixie> that doesn't work
- # [22:26] <Hixie> there are pages that have the encoding declaration far further down the document, and we have to support them (or else browsers will support them anyway and the spec will be ignored)
- # [22:26] <Hixie> one thing to note btw is that there are many "sniffing" things in the spec
- # [22:26] <Hixie> many
- # [22:27] <Hixie> some make sense to be optional, some don't (e.g. <img>, <script>)
- # [22:27] <Julian> Wait a second; I thought *this* discussion was about content type sniffing.
- # [22:27] <Hixie> there are many places where html5 requires content-type sniffing of one sort or another
- # [22:27] <Hixie> different resources can even end up being sniffed differently based on context
- # [22:28] <Hixie> e.g. <img> vs <script> vs <object> vs top-level browsing context resource
- # [22:28] <anne> (I sort of like sniffing, <meta charset=utf-8> is convenient)
- # [22:28] <Julian> Back to the question: why is sniffing a MUST?
- # [22:29] <Hixie> i answered that above
- # [22:29] <Hixie> but if you want a more specific answer, please indicate which "must" you are referring to
- # [22:29] <Hixie> do you mean the one at the top of section 4.9?
- # [22:29] <Hixie> for top-level browsing context navigation?
- # [22:30] <Julian> http://www.w3.org/html/wg/tracker/issues/28
- # [22:30] <Julian> http://www.w3.org/html/wg/html5/#content-type-sniffing
- # [22:30] <Julian> "The sniffed type of a resource must be found as follows:"
- # [22:31] <Hixie> so yes, you mean the one at the top of section 4.9, defining sniffing for top-level browsing context navigation
- # [22:31] <Julian> And I didn't see any justification for that.
- # [22:31] <Hixie> the reason for that is given immediately above the sentence with the must, in red text, with the word "warning" before it
- # [22:31] <Julian> No.
- # [22:31] <Hixie> you might not agree with the reason
- # [22:31] <Hixie> but that's the reason for the must
- # [22:31] <Hixie> (that, and predictable interoperability)
- # [22:31] <Julian> That's a reason why it would be dangerous to have *different* types of sniffing.
- # [22:31] <anne> Hixie, I think Julian is asking about making sniffing optional, but if implemented it must be done as described
- # [22:32] <Julian> It doesn't state why not doing sniffing at all would be a problem.
- # [22:32] <anne> Hixie, so that UAs can provide an option to disable sniffing without violating HTML5 and that UAs are also allowed to be stricter if desired
- # [22:32] <Hixie> oh, yeah, we could consider making that sniffing optional
- # [22:32] <Hixie> let's see
- # [22:38] <Hixie> there, it's now permissible to just use the provided type without sniffing
- # [22:38] <Hixie> i don't expect any browsers or tools intended for wide consumption to ever implement that, but who knows
- # [22:40] <Julian> Sounds good so far. Looking forward to the change.
- # [22:40] <Hixie> it's up
- # [22:41] <Julian> Great.
- # [22:42] <gsnedders> Hixie: on a slightly related note to spec-changes, can we have the whatwg-commit-watches not receive the diff of both source and index?
- # [22:43] <Hixie> no :-)
- # [22:43] <gsnedders> why not?
- # [22:43] <Hixie> it's useful to be able to compare them to make sure no cross-refs broke, etc
- # [22:43] <gsnedders> ah
- # [22:43] <Hixie> just read the one you want to read :-P
- # [22:43] <Hixie> or use the web site interface
- # [22:43] <gsnedders> I already do :P
- # [22:43] <Hixie> it sends them in the same e-mail anyway
- # [22:44] <Hixie> it shouldn't really be a big deal
- # [22:44] <Julian> Tracker, this is relevant to ISSUE-28.
- # [22:44] * gsnedders ponders which to ignore :)
- # [22:44] <Philip> Could you make it put source before index, so one doesn't have to scroll down so far to read the interesting bit? Maybe rename it to 'aaasource' or something :-)
- # [22:44] <gsnedders> Hixie: we need cross references that don't break
- # [22:44] <gsnedders> oh, wait, I'm the guy who more likely has to deal with the IDs not changing :)
- # [22:45] <Hixie> http://damowmow.com/temp/commit-email.pl - patches welcome
- # [22:46] <gsnedders> Perl… eww.
- # [22:46] <Philip> Indented braces, eww :-(
- # [22:46] <Hixie> i didn't write it
- # [22:46] <gsnedders> well, if you wrote it'd be perfect :)
- # [22:47] <Hixie> uh huh
- # [22:47] * gsnedders waits to be quoted out of context
- # [22:47] <gsnedders> (No, I don't blindingly believe anything Hixie says, really)
- # [22:51] * jgraham drops the word cabal in whilst looking away and whistling
- # [22:52] <gsnedders> jgraham: you see the latest email on whatwg-cabal BTW? *whistles*
- # [22:55] <Dashiva> I'm only subscribed to whawg-secret-treehouse, what did I miss?
- # [22:55] <gsnedders> Dashiva: I could tell you, but I'd have to kill you.
- # [22:56] <Dashiva> -9?
- # [22:57] <Hixie> lordy
- # [22:57] * Hixie goes back to quiet old #whatwg
- # [22:57] <gsnedders> not #whatwg-cabal? :P
- # [23:02] * Joins: shepazu (schepers@128.30.52.30)
- # [23:12] <DanC_lap> shepazu, hi! did you happen to check logs from last week? if not, see http://www.w3.org/html/wg/tracker/actions/50
- # [23:12] <DanC_lap> ACTION-50
- # [23:12] <DanC_lap> Investigate separate mailing list on cavas/2d-graphics API with Doug S. and Chris W.
- # [23:12] <shepazu> hi, DanC_lap, thanks for the pointer
- # [23:13] <DanC_lap> could I hand that action to you?
- # [23:13] <shepazu> we discussed canvas in the SVG F2F yesterday
- # [23:13] <DanC_lap> I'm trying to get out of the office for valentine's day
- # [23:13] <shepazu> heh
- # [23:13] <shepazu> sure, I'll investigate separate mailing list on cavas/2d-graphics API with Doug S. and Chris W.
- # [23:13] <shepazu> assign it to me
- # [23:14] <DanC_lap> hmm... you're not in the action tracking group. I suppose that's appropriate.
- # [23:14] <shepazu> can you switch which group it's assigned to?
- # [23:14] <DanC_lap> doubt it.
- # [23:14] <anne> can I object against an additional mailing list?
- # [23:14] <DanC_lap> anyway... you wanna pick a name?
- # [23:14] <shepazu> or I could just duplicate it elsewhere
- # [23:14] <DanC_lap> yes, you may object, anne
- # [23:14] <shepazu> anne, you can object, sure
- # [23:15] <shepazu> anne, what's your rationale?
- # [23:15] <anne> having even more places people have to go through to find what they're looking for
- # [23:15] <shepazu> anne, can I object to a separate mailing list for WHATWG as opposed to HTML WG? ;P
- # [23:15] <anne> you can raise that concern with the WHATWG, certainly
- # [23:16] <Philip> The WHATWG list is needed for legacy compatibility
- # [23:16] <shepazu> lol
- # [23:16] <anne> though I think we've dealt with that already
- # [23:16] * Hixie encourages the htmlwg to have as many mailing lists as possible
- # [23:16] <shepazu> I think it makes sense to have a separate Canvas list
- # [23:16] <Hixie> (though i don't guarentee that i'll remember to mail the right one)
- # [23:17] <anne> with every list the W3C adds it becomes easier for contributors to simply join the WHATWG
- # [23:17] <Lachy> I don't like the idea of even more mailing lists. I still haven't figured out the difference between public-html and public-html-comments, except that one gets more traffic than the other
- # [23:17] <Hixie> anne: shhhhhh
- # [23:17] <anne> Hixie, don't be evil ;) :p
- # [23:18] <jgraham> anne: I think it's "organising the world's information" now
- # [23:18] <Lachy> The 5 existing public-html-* mailing lists is enough.
- # [23:18] <shepazu> DanC_lap, why not just "public-canvas-api@w3.org"?
- # [23:18] <jgraham> which you could argue more lists achieve
- # [23:18] <jgraham> :)
- # [23:18] <Hixie> jgraham: google hasn't especially found that siloing information into categories is especially useful
- # [23:19] <Hixie> jgraham: good search algorithms seem far more effective
- # [23:19] <jgraham> Hixie: Well I tend to agree.
- # [23:19] * Joins: smedero (smedero@192.223.6.57)
- # [23:19] <anne> public-...-wtf@w3.org versus whatwg@whatwg.org hmm what should I pick?
- # [23:19] <DanC_lap> can't think of any argument against that name, shepazu ... though other buzzwords to mix in might be 2d and graphics
- # [23:19] * jgraham is very bad at filing
- # [23:20] <shepazu> DanC_lap, best not make it too long, and opera already has a 3d api they might put forth
- # [23:20] <Philip> (Mozilla has a 3D API too)
- # [23:20] <Hixie> so does mozilla
- # [23:20] <anne> DanC_lap, please note my objection based on that I think it makes it harder for people to contribute to the W3C than it already is and also that it makes it harder for existing contributors; in addition, it makes it harder for people to locate stuff related to the HTML WG, etc.
- # [23:20] <DanC_lap> I like short names. public-gapi@w3.org works for me
- # [23:20] <shepazu> and "canvas" as much as says "graphics"
- # [23:21] <Hixie> anne: my impression is that the idea is to reduce the amount of feedback, for which a new mailing list would be an effective solution
- # [23:21] <anne> DanC_lap, also please provide rationale for why you're going to overturn that objection as it seems like
- # [23:21] <Philip> With more lists, it would be more confusing about e.g. whether canvas tests should go in the 'canvas' list or the 'tests' list
- # [23:21] <jgraham> Can someone explain to me what the criteria for getting a special list of one's own is?
- # [23:21] <DanC_lap> your argument is noted, anne; I think it makes it easier for people to contribute; I have talked with several such people.
- # [23:21] * Lachy votes for public-html-graphics-api-mailing-list@w3.org
- # [23:21] <jgraham> Why <canvas> but not <datagrid> for example
- # [23:22] <DanC_lap> I don't particularly want people to go via the HTML WG to find work on 2d graphics APIs.
- # [23:22] <Hixie> jgraham: presumably because <canvas> is less likely to receive feedback than datagrid, what with it being mostly interoperably implemented already, with many tests already written.
- # [23:22] <anne> DanC_lap, it's part of HTML
- # [23:22] <shepazu> Hixie, no, it's not to reduce the amount of feedback, it's to allow those only interested in the graphics bit to follow feedback without wading though everything else
- # [23:22] <Lachy> but canvas is in the HTML spec, so it makes sense to got there
- # [23:22] <jgraham> Is there a plan to use <canvas> outside HTML?
- # [23:22] <anne> DanC_lap, oh well, i'll just submit my feedback elsewhere
- # [23:22] <DanC_lap> it's not clear to me that a 2d graphics API is or should be part of HTML... any more than it's part of SVG or MathMl
- # [23:23] <Hixie> that reminds me, i really should look at the requests for putting math markup in html5
- # [23:23] <Lachy> <canvas> is an HTML element. It has it's own API, just like many other HTML elements do. Why shouldn't it be?
- # [23:23] <Philip> I don't see any reason to use <canvas> outside HTML, because it's not like it's a particularly good API and nobody else has the constraints of being compatible with the existing <canvas> implementations
- # [23:23] <DanC_lap> fair point, Philip
- # [23:24] <shepazu> Philip, the SVG WG also wants to use Canvas
- # [23:24] <shepazu> canvas API, that is
- # [23:24] <hsivonen> multiple lists are easier only if the result is that people subscribe to a proper subset of the set of lists
- # [23:24] <hsivonen> so far, I have ended up subscribing to all HTML5 lists
- # [23:25] <DanC_lap> I subscribe to a proper subset.
- # [23:25] * Quits: kwijibo (kwijibo@87.113.10.93) (Quit: kwijibo)
- # [23:25] <shepazu> maybe the HTML WG home page could summarize each list for potential audiences
- # [23:26] <DanC_lap> and I don't read all of what I subscribe to; I hope to get stuff organized to the point where I read most of the mail to the lists that I subscribe to.
- # [23:26] <DanC_lap> yes, the HTML WG homepage should orient people who are interested to help
- # [23:27] <Philip> shepazu: Hmm, is that mainly because several SVG implementors already have canvas implementations (and hence it's useful to be compatible with those implementations)? Or is it because it's the most well-specified 2D graphics API (since most other APIs are just a single library and don't care about interoperability)? or something else?
- # [23:27] <jgraham> After a while you just encounter the paradox of choice
- # [23:27] <anne> i'm also subscribed to all html lists though the s/n ratio is still best on whatwg@whatwg.org :(
- # [23:27] <Sander> For what it's worth, as an only minutely involved participant, I find the many lists confusing, and if/when I have feedback on <canvas>, I'll likely just send it to the main list, except if I remember the existence of the new list, then I'll send it to the whatwg.
- # [23:28] <shepazu> Philip, the former... it's easiest to go with the flow
- # [23:28] <Philip> shepazu: Okay, makes sense
- # [23:44] * Joins: hober (ted@68.101.220.172)
- # [23:44] * Quits: Julian (chatzilla@80.143.156.62) (Quit: ChatZilla 0.9.80 [Firefox 2.0.0.12/2008020121])
- # [23:47] * Joins: heycam|sydney (cam@125.255.47.56)
- # [23:47] * heycam|sydney is now known as heycam
- # [23:52] * Joins: ed (ed@125.255.47.56)
- # [23:54] * Joins: ChrisWilson (cwilso@131.107.0.106)
- # [23:57] * Joins: kwijibo (kwijibo@87.113.10.93)
- # Session Close: Fri Feb 15 00:00:00 2008
The end :)