| 08:46 | <annevk> | hmm, e-mails from the geolocation list are detected as spam |
| 09:21 | <MikeSmith> | annevk: do those geolocation e-mails have some header added (be spamassassin or whatever) to indicate why they are getting flagged? |
| 09:22 | <annevk> | haven't checked |
| 10:05 | <zcorpan> | hsivonen: i see you've changed the preset names to include "HTML", which is good |
| 10:05 | <zcorpan> | hsivonen: but the message still says "Info: HTML 4.01 Transitional doctype seen. Using the schema for XHTML 1.0 Transitional." which is confusing |
| 10:06 | <hsivonen> | oh. I guess I've forgotten where all the strings are |
| 10:06 | <hsivonen> | zcorpan: thanks |
| 10:14 | <zcorpan> | hsivonen: xmlns doesn't cause an error under an html4 doctype |
| 10:14 | zcorpan | files a bug |
| 10:15 | <zcorpan> | in fact <br/> doesn't either |
| 10:35 | <hsivonen> | hmm. <br/> is a regression from when the spec moved /> checking to the tree builder |
| 10:52 | <hsivonen> | zcorpan: the info messages now pull the UI strings from the same place as the preset popup. thanks |
| 12:06 | <Hixie> | man i sure haven't been doing a good job of getting these numbers down recently |
| 12:10 | <hsivonen> | hmm. I've managed to miss keygen from my list of element names |
| 12:29 | annevk | would like to see <keygen> specified one day; hasn't figured out how it works |
| 12:30 | <Lachy> | there must be someone who understands how keygen works, since it's been implemented in a few browsers already. |
| 12:33 | <annevk> | reported in Nov 2005 by Hallvord: http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2005-November/005092.html |
| 12:33 | <annevk> | the specification that everyone uses: http://wp.netscape.com/eng/security/comm4-keygen.html |
| 12:35 | <annevk> | it would actually be interesting to know what is not detailed enough about that |
| 12:35 | <annevk> | (well, it seems that spec-like requirements can be inferred from the text easily enough) |
| 12:39 | <Lachy> | I understand how the key is generated and submitted. But I don't understand how to make use of the key in responses. |
| 14:52 | <zcorpan> | hmm, webkit parses <video> as a block-level element it seems |
| 14:54 | <zcorpan> | http://simon.html5.org/test/html/parsing/video/008.htm |
| 14:57 | <annevk> | maybe similar to <object> ? |
| 15:03 | <zcorpan> | no, similar to <div> |
| 15:03 | <zcorpan> | object is scoped and doesn't do aaa |
| 15:03 | <annevk> | <p><video> ? |
| 15:04 | <zcorpan> | good point |
| 15:04 | <annevk> | sounds like a bug to me anyway |
| 15:05 | <zcorpan> | similar to <b> i guess |
| 15:05 | <zcorpan> | uh no not that eiether |
| 15:05 | <zcorpan> | either |
| 15:50 | <zcorpan> | Hixie: "Still need to add these new elements to the lists: event-source, section, nav, article, aside, header, footer, datagrid, command" |
| 15:52 | <annevk> | zcorpan, that happened, no? |
| 15:52 | <zcorpan> | annevk: i quoted from the spec |
| 15:52 | <zcorpan> | they should all go in the Special category, i think |
| 16:56 | <gsnedders> | Time to try and implement 3.7.10.1 Creating an outline |
| 17:28 | <gsnedders> | Hixie: s/which which/with which/ |
| 17:40 | <hsivonen> | Hixie: do you have test cases for MathML-in-text/html and SVG-in-text/html |
| 17:40 | <hsivonen> | ? |
| 22:18 | gsnedders | joins #whatwg-emo |
| 23:04 | <Dashiva> | gsnedders: #emo-wg seems like a better bet |
| 23:15 | <hober> | Dashiva: what would such a WG's deliverables be? |
| 23:16 | <Dashiva> | The emo specification, for one. I see lots of uses for MUST and SHOULD in correct behavior designation :) |
| 23:19 | <gsnedders> | Dashiva: Emos SHOULD be bisexual. Emos SHOULD self-harm. Emos SHOULD wear black. Emos SHOULD listen to depressing music. |
| 23:20 | <gsnedders> | (regarding the first of those, according to a friend of mine (jokingly, though): "Bisexuals are people who are desperate") |
| 23:21 | <Dashiva> | I'd say the last one is a MUST. |
| 23:22 | Dashiva | adds a "/me MUST go to sleep" to that list. |
| 23:22 | <jgraham_> | You should do proper research e.g. http://www.google.com/search?q=emos%20SHOULD |
| 23:25 | <jgraham_> | The last result on page 2 is particularly nasty: "emos SHOULD just kill themselves". Having a spec with that in seems to be a bad idea though |
| 23:30 | <jgraham_> | gsnedders: FWIW I think I had exactly the same issue as you about the dual meanings of the word "section" in the outline spec |
| 23:37 | <jgraham_> | gsnedders: I _think_ you should end up with a different outline for each outline root element and I _think_ that if you feed the document root in, you should be able to construct a set of all outlines in a single pass of the algorithm (but that is from reading my code, not the spec) |