| 02:12 | <Lachy> | http://adactio.com/journal/1343 |
| 02:19 | <Lachy> | looks like me misunderstands and misrepresents how the 80-20 rule is applied and then uses that as a straw man to argue why we shouldn't be using it |
| 03:51 | <othermaciej> | Lachy: do you have any suggestions for a "Degrade Gracefully" example I could add to replace the section/block one? |
| 03:52 | <othermaciej> | Lachy: I'd like an example of an element that can be pretty much emulated with CSS styling |
| 03:52 | <Lachy> | maybe <m> |
| 03:52 | <othermaciej> | does HTML5 have any new block-level elements that are only allowed inline contents? |
| 03:53 | <othermaciej> | I'm not sure what the expected presentation of <m> is, if any |
| 03:53 | <Lachy> | I would expect a yellow highlight or something |
| 03:55 | <othermaciej> | it's not totally obvious yet what is expected so I'm not sure I could give a concrete example of the style rule to use |
| 03:56 | <othermaciej> | I'm going through the elements at http://simon.html5.org/html5-elements |
| 03:56 | <Lachy> | that's what I'm looking through too |
| 03:56 | <othermaciej> | hmmm |
| 03:56 | <othermaciej> | can <figure> be handled properly with just display: block? |
| 03:57 | <Lachy> | maybe |
| 03:57 | <othermaciej> | it's not allowed any block children |
| 03:58 | <othermaciej> | the legend doesn't really display in what seems like a useful way by default |
| 03:58 | <Lachy> | unfortunately, <legend> has problems in some browsers. it doesn't appear in the DOM in Firefox |
| 04:00 | <Lachy> | and IE isn't going to play nicely with any new element at all |
| 04:00 | <othermaciej> | the legend element isn't in the DOM in Safari either |
| 04:02 | <othermaciej> | it seems like using a new element for a figure caption instead of <legend> would work better |
| 04:02 | <othermaciej> | seems like <legend> will have the same problem for <details> as well |
| 04:02 | <othermaciej> | I can't figure out how to get this to style reasonably in any browser: |
| 04:03 | <othermaciej> | <figure><img src=chair.jpg><legend>a chair</legend></figure> |
| 04:03 | <Lachy> | http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3E%0Afigure%20%7B%20display%3A%20block%3B%20background%3A%20yellow%3B%20%7D%0Afigure%20legend%2C%20figure%20span%20%7B%20display%3A%20block%3B%20%7D%0A%3C%2Fstyle%3E%0A%3Cfigure%3E%3Cimg%20src%3Dimage%3E%0A%3Clegend%3E%3Cspan%3ECaption%3C%2Fspan%3E%3C%2Flegend%3E%3C%2Ffigure%3E |
| 04:03 | <othermaciej> | (what I'd like to do is make the legend display on its own line horizontally centered) |
| 04:04 | <Lachy> | wrong link... |
| 04:04 | <Lachy> | http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3E%0Afigure%20%7B%20display%3A%20block%3B%20background%3A%20yellow%3B%20%7D%0Afigure%20legend%2C%20figure%20span%20%7B%20display%3A%20block%3B%20background%3A%20lime%3B%20%7D%0A%3C%2Fstyle%3E%0A%3Cfigure%3E%3Cimg%20src%3Dimage%3E%0A%3Clegend%3E%3Cspan%3ECaption%3C%2Fspan%3E%3C%2Flegend%3E%3C%2Ffigure%3E |
| 04:04 | <othermaciej> | I can see that adding a span would work |
| 04:04 | <othermaciej> | I was hoping there might be a better way |
| 04:05 | <othermaciej> | a new element in place of <legend> would make it simpler at least in SafOperFox |
| 04:06 | <Lachy> | is there a reason why browsers need to ignore <legend> outside of a fieldset? Can that handling be changed without breaking anything? |
| 04:06 | <othermaciej> | it probably can be, but a new element would already work in today's browsers, so degrades better |
| 04:06 | <othermaciej> | <legend> is given special rendering behavior in a <fieldset> that can't be expressed with CSS |
| 04:07 | <othermaciej> | browsers probably ignore it in other places as a way to avoid causing problems with that in other places |
| 04:07 | <Lachy> | I know, that may cause some problems if someone tries to use a figure inside a fieldset |
| 04:08 | <othermaciej> | it seems pretty hard to center-align the caption under the image as well |
| 04:08 | <othermaciej> | this is the best I've got: |
| 04:08 | <othermaciej> | figure { display: block; float: left;} |
| 04:08 | <othermaciej> | figure legend, figure span { display: block; text-align: center; } |
| 04:08 | <othermaciej> | but floating by default is probably not desirable |
| 04:09 | othermaciej | tries to remember what else will cause shrink-wrap |
| 04:09 | <Lachy> | no, definately not a good idea to float by default |
| 04:09 | <Lachy> | inline-block; |
| 04:09 | <Lachy> | display: table-cell; |
| 04:09 | <othermaciej> | does mozilla support inline-block yet? |
| 04:09 | <othermaciej> | ah, table-cell |
| 04:09 | <othermaciej> | well, that won't work in IE probably |
| 04:10 | <Lachy> | IE has limited support for inline-block |
| 04:11 | <othermaciej> | this works in Safari and Opera but not Firefox: http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0D%0A%3Cstyle%3E%0D%0Afigure%20%7B%20display%3A%20inline-block%3B%7D%0D%0Afigure%20legend%2C%20figure%20span%20%7B%20display%3A%20block%3B%20text-align%3A%20center%3B%20%7D%0D%0A%3C%2Fstyle%3E%0D%0A%3Cfigure%3E%3Cimg%20src%3Dimage%3E%0D%0A%3Clegend%3E%3Cspan%3ECaption%3C%2Fspan%3E%3C%2Flegend%3E%3C%2Ffigure%3E |
| 04:11 | <othermaciej> | but in general inline-block seems good since it will make the image + caption work basically like a replaced element woud |
| 04:11 | <othermaciej> | *would |
| 04:13 | <othermaciej> | display: table-cell breaks the centering in Opera, but not Safari or Firefox |
| 04:14 | <Lachy> | this works in Firefox and Opera |
| 04:14 | <othermaciej> | ok, here's one that works in all three: |
| 04:14 | <othermaciej> | http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3E%0Afigure%20%7B%20display%3A%20table-cell%3B%20display%3A%20inline-block%3B%20%7D%0Afigure%20legend%2C%20figure%20span%20%7B%20display%3A%20block%3B%20text-align%3A%20center%3B%20%7D%0A%3C%2Fstyle%3E%0A%3Cfigure%3E%3Cimg%20src%3Dimage%3E%0A%3Clegend%3E%3Cspan%3ECaption%3C%2Fspan%3E%3C%2Flegend%3E%3C%2Ffigure%3E |
| 04:14 | <Lachy> | http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3E%0Afigure%20%7B%20display%3A%20table-cell%3B%20display%3A%20inline-block%3B%20background%3A%20yellow%3B%20%7D%0Afigure%20legend%2C%20figure%20span%20%7B%20display%3A%20block%3B%20background%3A%20lime%3B%20text-align%3A%20center%3B%20%7D%0A%3C%2Fstyle%3E%0A%3Cfigure%3E%3Cimg%20src%3Dimage%3E%0A%3Clegend%3E%3Cs |
| 04:14 | <Lachy> | pan%3ECaption%3C%2Fspan%3E%3C%2Flegend%3E%3C%2Ffigure%3E |
| 04:14 | <othermaciej> | yours got split into multiple lines |
| 04:14 | <Lachy> | yeah, that's the same thing :-) |
| 04:14 | <Lachy> | mine has pretty colours! |
| 04:14 | <othermaciej> | I'm not sure if that would work in IE |
| 04:14 | <Lachy> | download it from the clipboard |
| 04:15 | <othermaciej> | I'll fire up Windows |
| 04:15 | <Lachy> | doesn't work well in IE |
| 04:16 | <Lachy> | mostly because it treats "FIGURE", "/FIGURE", "LEGEND" and "/LEGEND" as distinct elements, that are all siblings of each other |
| 04:18 | <Lachy> | Hixie's server is having serious trouble. even is clipboard is generating intermittent HTTP 500 errors |
| 04:19 | <othermaciej> | ick |
| 04:20 | <othermaciej> | Lachy: IE's behavior on unknown elements seems to be a pretty serious impediment to adding new elements |
| 04:20 | <othermaciej> | even what Firefox does is pretty bad in a lot of cases |
| 04:20 | <othermaciej> | it's weird that Safari and Opera seem to be more similar to each other than the top two in a lot of these cases |
| 04:20 | <Lachy> | yeah, but there's nothing we can do about it |
| 04:20 | <Lachy> | unless we want to replace <section>, etc. with <div role=section> |
| 04:21 | <Lachy> | which I don't want to do |
| 04:21 | <othermaciej> | for Firefox we might have a reasonable shot of getting Mozilla to change handling of unknown elements to let them contain blocks |
| 04:22 | <othermaciej> | which seems to be the major issue |
| 04:22 | <othermaciej> | (change it well in advance of broad HTML5 adoption, that is) |
| 04:22 | <Lachy> | IIRC, the HTML5 parsing algorithm says unknown elements need to be treated as inlines |
| 04:23 | <othermaciej> | does that mean it would require that block element open tags terminate them? |
| 04:23 | <othermaciej> | that would (obviously) be a bad requirement |
| 04:23 | <Lachy> | hmm, apparently not http://wordsandpictures.dyndns.org/cgi-bin/parsetree/parsetree.py?source=%3C%21DOCTYPE%20html%3E%0D%0A%3Cbody%3E%0D%0A%3Cfoo%3ETest%3Cp%3Etest%3C%2Fp%3Etest%3C%2Ffoo%3E |
| 04:24 | <othermaciej> | that's good |
| 04:24 | <Lachy> | assuming that implementation is correct, yes |
| 04:24 | <othermaciej> | so anyway, I guess <figure> is not a good example |
| 04:24 | <othermaciej> | given IE's current behavior, I'm not sure any new element can be handled reasonably in existing versions of IE |
| 04:24 | <Lachy> | why not? We got good results in 3 out of 4 |
| 04:25 | <othermaciej> | well, having to add the span is ugly |
| 04:25 | <othermaciej> | and the style rule is kinda complicated |
| 04:26 | <Lachy> | IE's handling could be patched using a script to modify the dom |
| 04:28 | <othermaciej> | true, but that also seems to be the case for <section> in Firefox and IE |
| 04:28 | <othermaciej> | (though the script would be nontrivial) |
| 04:30 | <Lachy> | not too hard. Dean Edwards (I think) has a script somewhere that fixes IE 6's handling of <abbr>, which was treated as an unknown element. |
| 04:30 | <Lachy> | so it's been done before |
| 04:30 | <othermaciej> | well, it's a bit easier in IE because the end tag also ends up as an element in the DOM |
| 04:30 | <Lachy> | yep |
| 04:30 | <othermaciej> | doing the fixup in Firefox would require some marker for the end of the element |
| 04:31 | <othermaciej> | I think I'll take the example out for now |
| 04:31 | <othermaciej> | there doesn't seem to be any element that can be adequately handled just with a CSS rule currently |
| 04:31 | <othermaciej> | except maybe <m>, but I'm not sure what default rendering would be appropriate |
| 04:32 | <Lachy> | m { background: yellow; } |
| 04:32 | <Lachy> | you don't need to demonstrate the default styling, only that it's possible for authors to provide their own |
| 04:33 | <othermaciej> | I think the background: yellow thing wouldn't even work in IE |
| 04:33 | <othermaciej> | though I guess by that standard, I'm not sure if IE supports attribute selectors either |
| 04:35 | <Lachy> | IE7 supports attribute selectors |
| 06:59 | <othermaciej> | just sent email about the Mozilla issue |
| 06:59 | <othermaciej> | apparently there was already a bug filed some time ago (by Hixie) |
| 07:13 | <gavins> | https://bugzilla.mozilla.org/show_bug.cgi?id=311366 |
| 07:14 | <othermaciej> | yes, I cited that in my email |
| 07:15 | <gavins> | email to the list? |
| 07:15 | <gavins> | (sorry, lacking context) |
| 07:17 | <gavin_> | ah, yes |
| 07:19 | <othermaciej> | to public-html |
| 07:19 | <othermaciej> | seems like it would be nice to fix that in Firefox 3, since Firefox, Opera and Safari are all starting to get into HTML5 implementation |
| 07:20 | <gavin_> | yeah |
| 07:26 | <othermaciej> | Lachy: does IE7 still handle <abbr> as an unknown element? |
| 07:27 | <Lachy> | othermaciej, no, IE7 supports it properly |
| 07:27 | <othermaciej> | ok cool |
| 07:53 | <othermaciej> | Lachy: hmm, I think putting text-align: center on <figure> might be about the right thing |
| 07:55 | <Lachy> | othermaciej, show me a demo? |
| 07:59 | <Lachy> | figure { display: table; } figure legend { display: table-caption; } is probably the ideal default presentation, since it also allows the use of 'caption-side' |
| 08:00 | <othermaciej> | I'm not sure if it's right for the figure to shrink to fit the image or not |
| 08:00 | <othermaciej> | it's supposed to represent a paragraph |
| 08:00 | <othermaciej> | so presumably it should be its own block when mixed with paragraphs, and should get the full width of the containing block |
| 08:01 | <othermaciej> | but I don't think there's any way to handle it without adding a span or something inside the <legend> |
| 08:01 | <othermaciej> | hmm |
| 08:02 | <othermaciej> | display: table-caption means you have to control whether the caption appears above or below with separate properties instead of just whether it is before or after the image |
| 08:02 | <Lachy> | is that a bad thing? |
| 08:02 | <othermaciej> | well, yeah |
| 08:03 | <othermaciej> | why allow both <figure><img><legend>...</legend></figure> and <figure><legend>...</legend><img></figure> if they do the same thing? |
| 08:03 | <othermaciej> | whereas other elements that take a <legend> require it to be first |
| 08:05 | <othermaciej> | presumably there are cases where the image or video caption comes logically first, so you'd want it visually first by default as well |
| 08:13 | <Lachy> | I have a solution to that |
| 08:13 | <Lachy> | http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3E%0Afigure%20%7B%20display%3A%20table%3B%20%7D%0Afigure%20legend%2C%20figure%20span%20%7B%20display%3A%20table-caption%3B%20caption-side%3A%20bottom%3B%20text-align%3A%20center%3B%20%7D%0Afigure%20legend%3Afirst-child%2C%20figure%20span%3Afirst-child%20%7B%20caption-side%3A%20top%3B%20%7D%0A%3C%2Fstyle%3E%0A%3 |
| 08:13 | <Lachy> | Cp%3E%3Cfigure%3E%3Cimg%20src%3Dimage%3E%3Clegend%3E%3Cspan%3ECaption%3C%2Fspan%3E%3C%2Flegend%3E%3C%2Ffigure%3E%0A%3Cp%3E%3Cfigure%3E%3Clegend%3E%3Cspan%3ECaption%3C%2Fspan%3E%3C%2Flegend%3E%3Cimg%20src%3Dimage%3E%3C%2Ffigure%3E |
| 08:13 | <Lachy> | (if that split across several lines, download it from the clipboard) |
| 08:15 | <othermaciej> | that's not bad |
| 08:29 | <Lachy> | that doesn't work in Opera because legend is in the DOM as an empty element. |
| 08:30 | <Lachy> | These styles work: |
| 08:30 | <Lachy> | figure { display: table; } |
| 08:30 | <Lachy> | figure legend, figure span { display: table-caption; text-align: center; caption-side: bottom; } |
| 08:30 | <Lachy> | figure legend:first-child, figure legend:first-child+span, figure span:first-child { caption-side: top; } |
| 08:31 | <Lachy> | though I still haven't found anything that will get it working in IE |
| 08:35 | <othermaciej> | I don't think there's any way to make it work in IE without script |
| 08:38 | <othermaciej> | that latest set of rules seems to give consistent and useful rendering in SafOperFox |
| 08:39 | <othermaciej> | hmmm |
| 08:39 | <othermaciej> | Lachy: would there be any problem with using <label> instead of <legend>? |
| 08:41 | <Lachy> | not as far as the DOM is concerned, but I don't know how assistive technology reacts to labels that aren't used for form controls |
| 08:42 | <othermaciej> | http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3E%0Afigure%20%7B%20display%3A%20table%3B%20%7D%0Afigure%20label%20%7B%20display%3A%20table-caption%3B%20text-align%3A%20center%3B%20caption-side%3A%20bottom%3B%20%7D%0Afigure%20label%3Afirst-child%20%7B%20caption-side%3A%20top%3B%20%7D%0A%3C%2Fstyle%3E%0A%0A%3Cfigure%3E%0A%3Cimg%20src%3Dimage%3E%0A%3Clabel%3ECaption%3C%2Flabel%3E%0A%3C%2Ffigure% |
| 08:42 | <Lachy> | would it, for example, interfere with forms mode, or would they be read out when not in forms mode? I have no idea. it may not be a problem at all. |
| 08:42 | <othermaciej> | the DOM for that is right even in IE |
| 08:44 | <othermaciej> | IE doesn't support CSS tables, right? |
| 08:44 | <Lachy> | well, the DOM is as close as we're going to get it without replacing figure too. |
| 08:44 | <Lachy> | no, it doesn't support css tables |
| 08:45 | <othermaciej> | the DOM is real close anyway; required script fallback would be limited to putting the <figure> contents back inside the figure |
| 08:46 | <Lachy> | the problem I would have with reusing label is that authors currently style label a lot for use with forms, and if they wanted to insert a figure into an existing page, those existing styles would interfere |
| 08:46 | <Lachy> | that would create a lot of headaches as they modified their style sheets |
| 08:48 | <othermaciej> | true, but they'd need to add a rule for "figure label", so that can undo changes in that rule |
| 08:49 | <Lachy> | from an authoring perspective, I can tell you that undoing styles from countless styles spread across several stylesheets is a lot harder than you might think |
| 08:52 | <Lachy> | it makes it even more complicated when authors want to copy and paste their figure styles from one site to another, which may have different label styles and thus more to undo |
| 08:53 | <othermaciej> | all you have to do is have "initial" rules for the kind of styles that are likely to be seen on "label" (which I suspect is somewhat limited) |
| 08:53 | <othermaciej> | the problems with <legend> go beyond styling |
| 08:53 | <othermaciej> | you need tricky script-based fixup to be able to even put event listeners on the caption |
| 08:53 | <othermaciej> | or to find figure captions in the DOM |
| 08:54 | <othermaciej> | anyway I'll mention this objection in my email |
| 08:54 | <Lachy> | ok |
| 08:56 | <Lachy> | but I don't think label styles that authors use today are in any way limited. Some use floats, display: block; cursor pointers, font styles, colours, text-align and much more. |
| 09:25 | <Lachy> | hmm. so much for the "No Original Research" policy on the wiki. I wonder where all those suggestions for using type="" for everything came from, and elements like bmark that have never been discussed on the mailing list |
| 09:26 | <Lachy> | http://esw.w3.org/topic/HTML/ThoughtExperimentInGracefulDegradation |
| 09:26 | <Lachy> | none of the <object type=""> suggestions to replace video, audio and canvas will work. I thought the reason for rejecting that idea had already been explained on public-html |
| 09:28 | <othermaciej> | the browser test results on that page are useful though |
| 09:28 | <othermaciej> | wow |
| 09:28 | <Lachy> | @IRC log readers: the main reason is that overloading <object> with APIs for video, audio and canvas will be extremely complex for implementers |
| 09:28 | <othermaciej> | that's some insane use of type="" |
| 09:29 | <othermaciej> | using new elements not only reduces complexity but also improves semantics |
| 09:29 | <othermaciej> | Since in practice "a video" is more meaningful than "an object" |
| 09:29 | <Lachy> | indeed. We need to cure divitis, not encourage it |
| 09:30 | <Lachy> | not only that, but getting authors to understand MIME types enough to use type="video/mp4", "application/ogg", etc. properly, is a non-starter |
| 09:31 | <othermaciej> | application/x-canvas also seems like a bad idea, since it doesn't in fact represent a content type |
| 09:31 | <othermaciej> | and also the <source> element is a significantly better approach than <object>'s fallback model |
| 09:33 | <Lachy> | maybe we should add this to the wiki http://esw.w3.org/topic/HTML/AddedElementVideo |
| 09:33 | <Lachy> | anyway, dinner time |
| 09:33 | <Lachy> | bbl |
| 09:34 | <othermaciej> | later |
| 09:40 | <Lachy> | I'm back (the kitchen's in use and dinner needs to defrost) |
| 09:54 | <Philip`> | About new elements in IE: ExplorerCanvas does the same thing with recognising "CANVAS" and "/CANVAS" elements, then treating everything in between as fallback content |
| 09:55 | <Philip`> | Doesn't work when you have <canvas><canvas>A</canvas>B</canvas>, though |
| 09:55 | <Philip`> | (but that doesn't work in Opera either) |
| 10:02 | <hsivonen> | Philip`: should doc conformance ban nested canvas in your opinion? |
| 10:09 | <Lachy> | hmm. <description> might be a reasonable alternative to <legend> for captions |
| 10:10 | <Lachy> | nested canvas don't make sense, since if a UA doesn't support canvas and thus uses the fallback content, then it won't support the nested canvas either |
| 10:11 | <Lachy> | so, yes, I think it should be banned for conformance |
| 10:11 | <othermaciej> | <description> is not bad |
| 10:12 | <Lachy> | Ben's other suggestion to use <title> won't work, since that would mess with legacy handling of <title> |
| 10:12 | <othermaciej> | but it's a bit wordy and a bit inaccurate |
| 10:12 | <othermaciej> | agreed on <title> |
| 10:12 | <othermaciej> | on <details> especially, it's definitely a label (or perhaps a caption, stretching it), not a description |
| 10:14 | <Lachy> | I'd never heard of "rubric" before, so that's not a good option either. |
| 10:16 | <othermaciej> | it's always possible to add an arbitrary marker of disctionction, like <caption2> |
| 10:17 | <othermaciej> | but that's kind of lame |
| 10:17 | <Lachy> | maybe something like <cap> |
| 10:18 | <othermaciej> | <capt>, <cptn> |
| 10:18 | <othermaciej> | or, just to be silly, <c> |
| 10:18 | <othermaciej> | if we had our names of choice without regard to compatibility, I would say a figure has a caption, but a details section has a label |
| 10:19 | <Lachy> | capt. is generally the abbreviation of captain |
| 10:19 | <Lachy> | yeah, that's the advantage the XHTML2 group has - they don't care about compatibility |
| 10:22 | <othermaciej> | I wouldn't consider that an advantage |
| 10:23 | <Lachy> | not in reality, but it's an advantage because they don't have to spend time thinking about the issues like we do |
| 10:25 | <Lachy> | thesaurus.com lists these synonyms: explanation, head, inscription, legend, rubric, subtitle, title, underline |
| 10:26 | <othermaciej> | yeah, that's where I looked |
| 10:26 | <othermaciej> | I ruled out title, underline, legend and head for various reasons that should be obvious |
| 10:26 | <Lachy> | description, descriptor, headline, label, lemma |
| 10:27 | <Lachy> | descriptor might work |
| 10:27 | <Lachy> | or <desc> |
| 10:29 | <othermaciej> | another possibility is two new elements, say <figcaption> and <detailslabel> |
| 10:29 | <othermaciej> | I'm not sure I like any of these a lot more than <label> |
| 10:30 | <Lachy> | I really don't like <label> for the reasons I gave before |
| 10:31 | <othermaciej> | it's true that one or more new elements would be better for pragmatic reasons |
| 10:31 | <othermaciej> | and would have basically no disadvantage compared to <legend> |
| 10:31 | <othermaciej> | playing off of <label>, another possibility is <tag> |
| 10:31 | <othermaciej> | but that might just confuse people |
| 10:32 | <Lachy> | <tagline> |
| 10:32 | <Lachy> | nah, doesn't quite fit its definition |
| 10:34 | <Lachy> | How about just using <figure><img/><p>Caption</p></figure>? |
| 10:38 | <othermaciej> | I'd guess the default and author styling for p would both interfere with that |
| 10:40 | <Lachy> | yeah, possibly. But I don't think it would be as bad as <label>, since most p styles are just margin and padding - the rest are typically just inherited |
| 10:41 | <Lachy> | but I could be wrong, people do all sorts of crazy things |
| 10:45 | <gsnedders> | is it possible to look up any post on whatwg archives by message-id (or anything else I'd have in my email client)? |
| 10:45 | <Lachy> | gsnedders, the closest you can get is narrowing it down by date, subject and author |
| 10:45 | <gsnedders> | Lachy: that was my fear |
| 10:46 | <gsnedders> | silly othermaciej posting so many things in a single thread… |
| 10:46 | <othermaciej> | gsnedders: it doesn't look like a single thread to me... |
| 10:46 | <Lachy> | the alternative is to download the gzip'd mbox files and search those |
| 10:46 | <gsnedders> | http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-June/011973.html |
| 10:47 | <gsnedders> | that's what I was looking for |
| 10:48 | <othermaciej> | I shouldn't have posted anything on *that* thread |
| 10:48 | <gsnedders> | (I had been looking for it for around five minutes before asking the above question) |
| 10:57 | <Lachy> | othermaciej, why? did that thread turn into a flamewar or something? |
| 10:57 | <othermaciej> | I remember there being a lot of flamage around that topic |
| 10:58 | <gsnedders> | A lot. |
| 10:59 | <Lachy> | yeah, that's what happens when patents, laywers, and free-software advocates get involved |
| 15:26 | <hsivonen> | hmm. validator.nu got killed by the kernel :-( |
| 17:50 | <Philip`> | hsivonen: I don't see any value in forbidding nested canvases - it doesn't seem likely to be a mistake that authors will make, and it's supported in current browsers about as well as plain canvas fallback content is (i.e. it works in Firefox and Safari) |
| 17:51 | <Philip`> | I can only think of minor value in ever using nested canvases, though - I can imagine something like http://canvex.lazyilluminati.com/misc/photos.html where (in Firefox/Safari) the canvas gets replaced with its fallback content via DOM manipulation if certain JS/canvas features are missing, where it would be plausible for that fallback content to contain another canvas, but I don't expect that would be common |
| 17:55 | <Philip`> | Via http://triin.net/2006/06/12/CSS - it seems about 2% of pages style 'label' |
| 17:57 | <Philip`> | (but no idea how many just use "label { ... }" by itself, rather than ".loginform label { ... }" or whatever) |
| 17:58 | Philip` | wonders how easy it would be to collect data about these kinds of things... |
| 18:09 | <hsivonen> | Philip`: ok. I won't suggest making nested canvases non-conforming, then |
| 18:26 | <hsivonen> | I wonder if the intra-paragraph VoiceOver navigation is different from Safare in Kestrel on purpose or if it is a bug |
| 18:27 | <hsivonen> | (I couldn't figure out how to read more than the first line of a para with VoiceOver in Kestrel) |
| 20:58 | <gsnedders> | apparently HTML parsers are SGML parsers as they parse HTML 4.01, an SGML standard. |
| 20:59 | <gsnedders> | Whether they comply with the SGML spec is irrelevant. |
| 20:59 | <Dashiva> | heh |
| 21:18 | <zcorpan> | Hixie: i get a 500 internal server error for http://forums.whatwg.org/ |
| 21:54 | <hsivonen> | http://html4all.org/wiki/index.php/Open_Issues |
| 21:57 | <zcorpan> | hsivonen: looks like a list of solutions |
| 22:07 | <antifuchs> | hi there. the blog.whatwg.org gives me a 500 error. is the web master around? (if not, I'll just write an email) |
| 22:08 | <gavin_> | I think that's known |
| 22:08 | <gavin_> | Lachy mentioned it earlier |
| 22:08 | <antifuchs> | ah, ok |
| 22:09 | <antifuchs> | (so is the wiki, btw) |
| 22:12 | <Philip`> | So is ln.hixie.ch |
| 22:18 | <Lachy> | yeah, it appears that all sites on Hixie's server, especially the ones that aren't just serving static files, are having problems. Sometimes it gives an out of memory error. |
| 22:20 | <Lachy> | I wonder why the axis attribute is listed in their open issues list? It's totally useless for everyone and serves no practical purpose. |
| 23:01 | <grimboy> | Damn you dreamhost, damn you to hell. |
| 23:01 | <grimboy> | Oh no, back to okay. |