| 00:11 | <daedb> | Philip`: I saw "≤" in the title for like a half a second, then it auto-corrected itself (in Opera)... IE shows it unless I switch to utf-8... |
| 00:12 | <daedb> | Kinda funky, actually :) |
| 00:41 | <boogyman> | can someone please explain the meaning of "dirty value" |
| 00:41 | <Philip`> | In what context? |
| 00:42 | <boogyman> | I am reading the HTML5 spec and the input declaration mentions a dirty value flag, but the description is confusing |
| 00:44 | <boogyman> | reference http://dev.w3.org/html5/spec/Overview.html#concept-input-value-dirty-flag for the description given |
| 00:51 | <AryehGregor> | It's just a flag. The spec says when to set it and unset it, that's all the semantics it has. |
| 00:51 | <AryehGregor> | The general idea is that it's set in some cases when the value of the input is changed, and potentially cleared when the value returns to its default. You have to read the actual spec to get the full details. |
| 00:52 | <boogyman> | so it's User Agent (browser) info? |
| 00:53 | <AryehGregor> | IIRC, it's relevant to scripting as well, but I could be misremembering. |
| 01:00 | <boogyman> | I just re-read the description "Each input element has a boolean dirty value flag. When it is true, the element is said to have a dirty value. The dirty value flag must be initially set to false when the element is created, and must be set to true whenever the user interacts with the control in a way that changes the value." ... does that translate into being any user-defined value... eg... |
| 01:00 | <boogyman> | ...not the defaultValue |
| 01:01 | <Philip`> | This bug reporting system seems a bit inefficient in terms of number of emails |
| 01:02 | <AryehGregor> | What do you mean? |
| 01:02 | <Philip`> | since the most trivial issue will involve at least four separate changes that trigger mail |
| 01:02 | <AryehGregor> | The dirty value flag is a boolean flag, it's not part of the value itself. |
| 01:02 | <AryehGregor> | (I already commented elsewhere that "value" seems to be used for too many things in this part of the spec.) |
| 01:03 | <Philip`> | I don't know who Dave is but he must be getting fed up with all this spam |
| 01:04 | <boogyman> | AryehGregor: it appears to be tied to the "value" of a node |
| 01:04 | <boogyman> | "The dirty value flag must be initially set to false when the element is created, and must be set to true whenever the user interacts with the control in a way that changes the value" |
| 01:04 | <boogyman> | so when the value of the node is "changed" the flag is changed from false to true... |
| 01:05 | <AryehGregor> | Yes. I'm not sure what you're asking now. |
| 01:05 | <AryehGregor> | You mean Bugzilla? |
| 01:05 | <boogyman> | nothing now... was just confirming |
| 01:06 | <AryehGregor> | A threading client is handy. :) |
| 01:06 | AryehGregor | finally finds a site that uses <video> in its blog posts -- hacks.mozilla.org, predictably -- and of course it turns out the videos don't work properly in Chrome, audio is out of sync. Ugh. |
| 01:13 | <nessy> | is it a chrome bug? |
| 01:19 | <AryehGregor> | I have no idea. |
| 01:20 | <AryehGregor> | http://videos.mozilla.org/serv/blizzard/woff/features-screencast-500.ogv |
| 01:20 | <AryehGregor> | The audio only starts a few seconds in, and it's clearly out of sync if you watch for a while. |
| 01:20 | <AryehGregor> | At least for me. |
| 01:20 | <nessy> | yeah, here, too |
| 01:21 | <nessy> | I just downloaded the latest chromium for mac |
| 01:22 | <nessy> | btw: http://blog.gingertech.net/ on my blog there are some <video> s in ogg, too - the second video doesn't seem to be scaled correctly (width/height) |
| 01:23 | <nessy> | also, strangely, a lot of the videos from http://tinyvid.tv don't work |
| 01:24 | <nessy> | I think <video> and Ogg in chrome just isn't quite there yet |
| 01:24 | <nessy> | it's great to see it working though!! |
| 01:25 | <AryehGregor> | I don't know if it's Chrome specifically, or what. It could be there would be some videos that only work in Chrome and not Firefox. |
| 01:51 | <boogyman> | does the <button> element have a default type ? |
| 01:51 | <boogyman> | nevermind |
| 02:17 | AryehGregor | suspects he's going to have to write a small essay in response to that decentralized extensibility thread at some point, time permitting |
| 02:17 | AryehGregor | hasn't looked at it for days |
| 02:55 | <nessy> | funny - http://videos.mozilla.org/serv/blizzard/woff/features-screencast-500.ogv breaks in my vlc |
| 08:48 | <Philip`> | AryehGregor: I do mean Bugzilla, though it doesn't affect me directly since I've reported all the bugs anonymously and never get emailed |
| 08:54 | <Hixie> | i just filter it all out |
| 08:54 | <Hixie> | and hope that someone is checking that reporters are REOPENing bugs they filed when they reply |
| 08:54 | <Hixie> | (i am a little concerned that the default permissions don't allow that) |
| 08:55 | <Hixie> | (i've been spot-checking e-mails that don't look like e-mails caused by me or indicating someone marking a bug CLOSED |
| 08:55 | <Hixie> | in case nobody else is looking...) |
| 09:16 | <Philip`> | Am I right in assuming the float reflection stuff is all new (for <progress> and <meter>) and not already implemented anywhere? |
| 09:18 | <Hixie> | progress, meter, and some <input> stuff |
| 09:18 | <Hixie> | all new though yes |
| 09:19 | <Hixie> | dunno if the input stuff is implemented in opera/webkit yet |
| 09:19 | <Hixie> | it probably needs updating if it is anyway |
| 09:19 | <Hixie> | so it's changeable |
| 11:19 | <Philip`> | zcorpan: Do you have any idea why the '<' of </title> got eaten on lots of pages? |
| 11:20 | <Philip`> | I only looked at one but that seemed to be labelled as shift_jis properly, so I wonder if it's a problem with the decoder |
| 11:20 | <Philip`> | (rather than with the encoding detector) |
| 11:23 | <zcorpan> | Philip`: yeah maybe it's a problem with the decoder |
| 12:14 | <gsnedders> | jgraham: Yeah, html5lib 0.12 will be required for Anolis 1.1, which is the entire reason I've been pushing to get 0.12 out :) |
| 12:32 | <zcorpan> | it would probably be good to make <style><!--</style> invalid |
| 12:39 | <jgraham> | gsnedders: and all this time I thought that you cared :( |
| 12:39 | <gsnedders> | jgraham: No, not really. |
| 12:49 | <erlehmann> | zcorpan, it it such a hardship for parsers? if so, why doesn't that also apply to <script><!--</script> ? |
| 13:02 | <gsnedders> | erlehmann: That already is invalid |
| 13:02 | <erlehmann> | urgs |
| 13:02 | <gsnedders> | erlehmann: I guess the point is to stop the conformance criteria for script and style from diverging |
| 13:03 | <gsnedders> | erlehmann: There's a lot of magic in the parser for script, esp. involving comments. |
| 13:04 | <erlehmann> | curse those SGML inventors |
| 13:05 | <gsnedders> | This has nothing to do with SGML, but with legacy content with all kinds of weird comments in script, and not wanting to reparse |
| 13:07 | <zcorpan> | erlehmann: this sillyness is a result of browsers doing reparsing |
| 13:08 | <Lachy> | erlehmann, SGML actually had relatively sane parsing requirements for CDATA element content, compared with what we have now for <script> |
| 13:14 | <Philip`> | It would have been fine if browsers had all used SGML parsers |
| 16:04 | <jgraham> | gsnedders: Technically the license requires a link back to the flickr page as well |
| 16:05 | <gsnedders> | jgraham: Stop using other people's Facebook accounts. |
| 16:05 | <jgraham> | (since you bothered to get the bit about the link to the license right, I guess you should probably follow its terms :) ) |
| 16:05 | <gsnedders> | jgraham: Where does it require a link back to Flickr? |
| 16:05 | <jgraham> | gsnedders: Other people using their facebook accounts told me about the information displyed therein |
| 16:06 | <gsnedders> | jgraham: AFAIK all I'm required to do is credit the creator of the work, which I do |
| 16:06 | <jgraham> | gsnedders: 4.c |
| 16:06 | <jgraham> | "to the extent reasonably practicable, the Uniform Resource Identifier, if any, that Licensor specifies to be associated with the Work" |
| 16:07 | <jgraham> | which n this cse could reasnably be assumed to be the flickr page and is evidently practical (since you can create links and all) |
| 16:07 | <gsnedders> | jgraham: Ah, I didn't see that before. Fixed now. |
| 16:08 | gsnedders | wonders how his hair manages to look as if it is not up against his head without hanging down |