03:04
<MikeSmith>
AryehGregor: is there a way to contact the Wikimedia Language Committee by e-mail?
03:06
<MikeSmith>
ah, found it
03:30
<MikeSmith>
AryehGregor: see http://www.alvestrand.no/pipermail/ietf-languages/2006-November/005199.html
03:33
<MikeSmith>
Amorphous: from Doug Ewell, who's closely involved with the language-tag registry
03:34
<MikeSmith>
in reply to Gerard Meijssen asking about what WMF should do about language tags
03:34
<MikeSmith>
Doug replied that they should do the "x-" thing
03:35
<MikeSmith>
so I guess the change you made to the home page aligns with that
06:30
<hsivonen>
I've landed the </script> tokenization change on mozilla-central.
06:30
<hsivonen>
should be in the next batch of nightlies
06:36
<hsivonen>
in fact, trunk should now be in sync with the spec except for <spacer>
10:22
<Philip`>
<span sandbox="random_token"><plaintext>...user-generated content...</span sandbox="same_token">
10:23
<Philip`>
That should solve Michal Zalewski's point 2.2, assuming the sandbox parser is properly sandboxing
10:23
Philip`
doesn't really want to imagine how such a parser would be implemented
14:58
<theMadness>
How is the attribute "required" supposed to work in html5 when applied to only one radio input if the others don't have it?
14:59
<Hixie>
you only need to set it on one of the radio buttons
14:59
<Hixie>
basically
14:59
<theMadness>
And it doesn't matter which. Any suggestion as per what would constitute "elegant coding"?
15:00
<theMadness>
AKA What Would Xhtml2 Do?
15:01
<Hixie>
xhtml2 would use xforms, so i don't know if that's what i'd do :-)
15:01
<Hixie>
i'd recommend putting required on all the radio buttons if they're supposed to be required
15:01
<theMadness>
I see.
15:02
<Hixie>
but really a required radio button set is a bit dubious -- you're only need it if you hadn't checked a radio button to start with
15:02
<Hixie>
and generally speaking it's better to check a radio button first
15:02
<Hixie>
instead of having none et
15:02
<Hixie>
set, even
15:03
<theMadness>
By the way, how does that compare to <select>? Does required fail in a <select> dropdown? (the first element is always selected, at least in most UA)
15:06
<theMadness>
Ah, there's no such thing as required for select.
15:06
<theMadness>
Funny.
15:07
<Hixie>
yeah there's no way to not have something selected
15:08
<Hixie>
gotta go, reffing an fll regional
15:08
<Hixie>
back later
15:08
<theMadness>
Thanks Ian.
15:08
<theMadness>
Have fun.
15:54
<Dashiva>
http://www.codinghorror.com/blog/
15:54
<Dashiva>
"We're overloading the class attribute with two meanings. Is "adr" the name of a class that contains styling information, or the name of a data field? (...) the semantics of the class attribute have been permanently altered."
15:55
<Dashiva>
Class is for CSS, it seems
16:01
<theMadness>
Yeah I'm puzzled too, "css class" means nothing.
16:02
<theMadness>
This attribute assigns a class name or set of class names to an element. Any number of elements may be assigned the same class name or names. Multiple class names must be separated by white space characters.
16:02
<theMadness>
Nothing about css in http://www.w3.org/TR/html4/struct/global.html#h-7.5.2
22:32
<Dashiva>
>Mozilla’s new offices have conference rooms named after memes! Had to take a shot of All Your Base room.