| 00:01 | <metron> | annevk: hmm, .oO(…she mean Xing too?) ;) |
| 00:01 | <TabAtkins> | (Btw, annevk's a dude.) |
| 00:01 | <TabAtkins> | (He's dutch, where "anne" is a common male name.) |
| 00:02 | <metron> | ups |
| 00:02 | <metron> | annevk: sry, wasn't know that |
| 00:03 | <TabAtkins> | Don't worry, I'm pretty sure everyone makes that mistake once, unless they see him in person first or catch someone using a gendered pronoun on him. |
| 00:04 | <metron> | its late, I think, I'll have to go off |
| 00:04 | <metron> | thx for helping me out |
| 00:04 | <metron> | cya guys |
| 00:08 | <annevk> | at the airports they typically look from me to my passport and back again etc. |
| 00:09 | <annevk> | some of these people even ask, "is this really you?" |
| 00:09 | <annevk> | wtf are passports for... |
| 00:10 | <Philip`> | You could have mixed up your passport with your identical other-gendered twin |
| 00:10 | <zewt> | (the Usual Internet Ratio just red-flagged it for me to begin with, so I checked, heh) |
| 00:10 | <Philip`> | Presumably if they thought you were really trying to trick them, they'd have to interrogate you more thoroughly than asking "is this really you?" |
| 00:16 | <Dashiva> | Nah |
| 00:16 | <Dashiva> | They're just waiting for someone to answer "No" sarcastically, so they can arrest you |
| 07:23 | <Hixie> | can anyone think of anything that would make a browsing context navigation do something other than change the document, other than: |
| 07:23 | <Hixie> | - content-disposition: attachment |
| 07:23 | <Hixie> | - unrecognised content-type triggering a download |
| 07:23 | <Hixie> | - http 204 or 205 response |
| 07:24 | <Hixie> | - network error in a browser that displays a dialog instead of an inline page for network errors |
| 07:24 | <Hixie> | - a scheme being one that triggers a helper app (e.g. mailto:) |
| 07:24 | <Hixie> | ...? |
| 07:24 | <wirepair> | security validation error (certs) |
| 07:24 | <Hixie> | ooh, good call |
| 07:25 | <wirepair> | other than that... hmm |
| 07:26 | <wirepair> | maybe plugins taking over the context, like flash or something? |
| 07:26 | <Hixie> | that changes the document |
| 07:27 | <Hixie> | i can't think of others any either, fwiw |
| 07:27 | <Hixie> | didn't even think of the crypto one :-) |
| 07:27 | <wirepair> | right. then yeah that should be it hehe |
| 07:35 | Hixie | adds yet another reference |
| 07:38 | <JennaBerry> | Any W3C people around? |
| 07:39 | <JennaBerry> | I have a question about CSS |
| 07:39 | <Hixie> | you probably don't want w3c people then, more css people :-) |
| 07:39 | <smaug____> | JennaBerry: just ask and someone may answer |
| 07:40 | <JennaBerry> | I'd like to submit a section into CSS that deals with CSS-based image sprites and multiple backgrounds, so that you can reduce code and not work with extra images/libraries/scripts/styles |
| 07:40 | <Hixie> | already exists and supported in several browsers |
| 07:41 | <JennaBerry> | Oh? |
| 07:41 | <Hixie> | http://dev.w3.org/csswg/css3-background/ |
| 07:44 | <JennaBerry> | Can't find the exact thing I'm looking for. |
| 07:44 | <JennaBerry> | I'd like something that places images, repeats or stretches them and does all sorts of things, but not to the whole object, so that you can create a button-element with a single image, cut into three parts (left, middle, right) and positioned accordingly as the background |
| 07:45 | <JennaBerry> | even with the current multiple backgrounds, repeat goes from one side to the other, instead of stopping at, say, 10px off the edge |
| 07:46 | <Hixie> | http://dev.w3.org/csswg/css3-background/#border-images |
| 07:47 | <JennaBerry> | The elements should also have contents |
| 07:48 | <Hixie> | the elements can have contents |
| 07:49 | <JennaBerry> | Does the border image also allow for backgrounds? |
| 07:49 | <Hixie> | the border image also allows for backgrounds |
| 07:49 | <JennaBerry> | I mean, without using a second image |
| 07:49 | <Hixie> | without using a second image |
| 07:49 | <Hixie> | (or with, both work) |
| 07:49 | <JennaBerry> | Interesting... |
| 07:50 | <Hixie> | this is already implemented in at least chrome |
| 07:50 | <JennaBerry> | Does it always stretch? |
| 07:50 | <Hixie> | dude just read the spec :-) |
| 07:50 | <JennaBerry> | Sorry... I've been working all night :P |
| 07:50 | <JennaBerry> | It's easier to ask, but yeah... I will |
| 07:51 | <Hixie> | sorry, kinda busy here :-) |
| 07:51 | <Hixie> | there's probably some tutorials you can google for |
| 07:51 | <Hixie> | the spec isn't the easiest thing to read |
| 07:51 | <JennaBerry> | I can read spec :) |
| 07:51 | <JennaBerry> | I did that for SVG, yesterday |
| 07:51 | <JennaBerry> | And then found out WebKit doesn't have effects :| |
| 07:53 | <smaug____> | use gecko :p |
| 07:54 | <JennaBerry> | I'm building a Safari Extension's configuration page... so it's not really possible to use Gecko |
| 09:16 | <jgraham> | Hmm, isn't overloading functions based on number of arguments rather common in non-DOM js? |
| 09:16 | <jgraham> | Like in jQuery? |
| 11:31 | <annevk> | holy shit |
| 11:32 | <annevk> | ALT+left directional key works in Terminal.app |
| 11:32 | <annevk> | *happy* |
| 11:33 | <jgraham> | Have they fixed it yet so you can enter characters not on your keyboard when you have the alt-sends-meta option selected? |
| 11:33 | jgraham | thinks not being able to type ä or whatever into terminals is a bit ridiculous |
| 11:33 | <smaug____> | Does Terminal.app not hang anymore when using gdb? |
| 11:34 | <jgraham> | In general is terminal.app no longer crappy? :) |
| 11:34 | <annevk> | jgraham, smaug____, no idea |
| 11:34 | <annevk> | it does what I need :) |
| 11:50 | <smaug____> | AryehGregor: seems like the range draft doesn't handle ReplaceData nor AppendData cases |
| 11:52 | <jgraham> | Firefox has disabled typing javascript: URIs into the address bar? |
| 11:53 | <smaug____> | there is a pref to enable it |
| 11:53 | <smaug____> | though, IIRC, even then it is run in a sandbox |
| 11:53 | <jgraham> | Is there some announcement about the change? |
| 11:55 | <smaug____> | looking... |
| 11:55 | <jgraham> | (or a bug number) |
| 11:59 | <annevk> | we should really define following/preceding |
| 11:59 | <smaug____> | jgraham: https://bugzilla.mozilla.org/show_bug.cgi?id=527530 is the meta bug |
| 12:04 | <jgraham> | smaug____: Thanks |
| 12:39 | <foolip_> | Hixie, ping? |
| 13:06 | <smaug____> | AryehGregor: also, I wonder how you ended up with the splitText handling |
| 13:22 | <Ms2ger> | <!-- bring it on jgraham --> |
| 13:32 | <jgraham> | Ms2ger: Huh? |
| 13:32 | <Ms2ger> | http://dvcs.w3.org/hg/domcore/file/9a02cfae1bdb/Overview.src.html#l3873 |
| 13:33 | <jgraham> | Oh. Clearly payman_ is insane |
| 13:34 | <jgraham> | Sorry annevk |
| 13:34 | <jgraham> | +, |
| 13:35 | <jgraham> | Although payman_ is probably also insane |
| 13:48 | <bga_> | <a download="foo.txt" href="data:...">Download generated data</a> |
| 13:48 | <bga_> | new attr is very good idea |
| 13:48 | <jgraham> | annevk: "Let sibling be the preceding sibling of node" doesn't account for node not having a preceding sibling. I assume sibling is supposed to be null or something there |
| 13:56 | <jgraham> | Also, I am missing simething about 3.2.3 in the previouNode algorithm |
| 13:56 | <jgraham> | *something |
| 13:56 | <jgraham> | Oh wait |
| 13:58 | <jgraham> | It's fine |
| 13:58 | <jgraham> | (I really wish you made "return" imply "and terminate these steps" |
| 13:58 | <jgraham> | we don't have coroutines) |
| 14:20 | <annevk> | jgraham, it does not always mean that |
| 14:20 | <annevk> | though maybe in DOM Core it does |
| 14:26 | <jgraham> | annevk: "return" meaning multiple differrnt thigns seems like a bug that should be fixed |
| 14:28 | <annevk> | it does not mean multiple things |
| 14:28 | <annevk> | but e.g. XMLHttpRequest.send() can return and still continue running |
| 14:28 | <linclark> | so the HTML WG used a lot of data about how people were using classes to create the new semantic elements, right? |
| 14:29 | <linclark> | if that is right, does anyone have a link to the data? |
| 14:29 | <linclark> | I remember adactio talking about it I think, but can't find link |
| 14:29 | <annevk> | the raw data is not available |
| 14:29 | <annevk> | a summary is available here: http://code.google.com/webstats/ |
| 14:29 | <linclark> | ahhhhh, awesome |
| 14:29 | <linclark> | thanks! |
| 14:29 | <annevk> | it is from 2005 though, hopefully at some point a new study is done |
| 14:30 | <adactio> | linclark: Note though, that the research was done *after* the new structural elements had already been named (if I recall correctly). So the data provided *justification* but wasn't necessarily the origin of the element names. |
| 14:31 | <linclark> | oh, ok, didn't realize that. thanks for the clarifications |
| 14:31 | <adactio> | John Allsopp also did some research 'round about the same time (2005), if I recall. |
| 14:32 | <adactio> | Here's John's study (a smaller sample than Google's, obviously): http://westciv.typepad.com/dog_or_higher/2005/11/real_world_sema.html |
| 14:41 | <Hixie> | foolip_: pong |
| 14:41 | <foolip_> | Hixie, I filed two bugs instead |
| 14:41 | <Hixie> | k thanks |
| 14:41 | <foolip_> | was just going to ask if putting defaultMuted on HTMLMediaElement was intentional |
| 14:41 | annevk | wonders if Hixie is in California |
| 14:42 | <Hixie> | btw the way that the IETF leaves obsolete specs on the web instead of replacing specs when they're updated makes the RFC space _even worse than the TR page_ |
| 14:42 | <Hixie> | it's like the W3C and the IETF compete for how badly they can do web standards |
| 14:42 | <Hixie> | annevk: yes |
| 14:42 | <Hixie> | foolip_: yes |
| 14:42 | <Hixie> | foolip_: why would it not be? |
| 14:42 | <annevk> | so is it morning for you or just late? :) |
| 14:42 | <foolip_> | Hixie, like poster="", muted="" does nothing for <audio> |
| 14:42 | <Hixie> | morning |
| 14:43 | <Hixie> | foolip_: i thought i made muted="" do something on audio? |
| 14:43 | <foolip_> | oh, wait a second |
| 14:43 | <foolip_> | it says "When a media element is created, if it has a muted attribute specified, the user agent must set the muted IDL attribute to true, overriding any user preference." |
| 14:44 | <foolip_> | sloppy reading on my part, I'll close the bug as invalid and just implement the spec |
| 14:44 | <Hixie> | k :-) |
| 14:44 | <Hixie> | i don't really mind, we can make it video-only, but it seemed simpler to just make things the same everywhere where possible |
| 14:45 | <foolip_> | this is what confused me: "The muted attribute on the video element controls" |
| 14:45 | <foolip_> | but it's actually defined on both audio and video |
| 14:46 | <foolip_> | do you want a bug on that? |
| 14:47 | <hsivonen> | hmm. Microdata may get corrupted if someone does <script itemprop=foo> and a sanizer zaps scripts |
| 14:47 | <hsivonen> | I guess I'll worry about that if it becomes a Real Problem |
| 14:47 | <foolip_> | hsivonen, same thing for <object>, right? |
| 14:47 | <hsivonen> | foolip_: oh, good point |
| 14:47 | <foolip_> | and attribute whitelists... |
| 14:47 | <hsivonen> | foolip_: I'm whitelisting Microdata |
| 14:48 | <foolip_> | hsivonen, you're writing a sanitizer? |
| 14:48 | <hsivonen> | foolip_: yes |
| 14:48 | <hsivonen> | foolip_: well, it's mostly written. I'm just fixing the obvious problem that <link itemprop> and <meta itemprop> got dropped |
| 14:48 | <hsivonen> | and now I see further problems |
| 14:49 | <foolip_> | hsivonen, what would you expect <script itemprop> to do? |
| 14:50 | <hsivonen> | foolip_: make the textContent of the element be the value of the property |
| 14:50 | <foolip_> | <script src="foo" itemprop="prop"> isn't reflected by itemValue the way you might expect, though |
| 14:50 | <foolip_> | that inconsistency would be a bit iffy, IMO |
| 14:50 | <Hixie> | foolip_: sure |
| 14:51 | Philip` | thought the IETF deleting specs after 6 months was a worse problem than them keeping specs around for too long, since it forces you to look in less-official places to find archived copies |
| 14:51 | <Hixie> | sanitizers corrupt pages, that's what they're for :-) |
| 14:51 | <hsivonen> | dropping <object> worries me now more than dropping <script> |
| 14:51 | <Hixie> | Philip`: yeah that's pretty messed up too |
| 14:51 | <annevk> | that's fixed by just using tools.ietf.org |
| 14:51 | <hsivonen> | Hixie: I could make non-whitelisted elements that have Microdata turn into spans |
| 14:52 | <jgraham> | hsivonen: or <meta> |
| 14:52 | <jgraham> | Oh, but that doesn't work I guess |
| 14:52 | <Philip`> | tools.ietf.org links to updated versions of obsoleted drafts so I suppose it helps with both problems |
| 14:52 | <Philip`> | ...as long as you find your way to an HTML version, not a text version |
| 14:52 | <hsivonen> | Hixie: but I guess this patch has been in bz's review queue for long enough that I'll leave that kind of feature creep for another bug |
| 14:53 | <Hixie> | hsivonen: what's the use case for round-tripping microdata through a sanitizer? |
| 14:53 | <Hixie> | annevk: in case you're planning on replying to Takeshi, note that i've already said on public-webapps that i don't care if we force the extension on or off, so long as we force it one way or the other |
| 14:57 | <hsivonen> | Hixie: the same as round-tripping Content MathML: Not destroying invisible data that doesn't need to be destroyed when someone pastes it into contenteditable |
| 14:58 | <Hixie> | that doesn't seem like a realistic use case |
| 14:58 | <Hixie> | it's just gonna cause the data to be corrupted when the user fiddles with the content |
| 15:01 | <hsivonen> | is switching the twitter avatar into a monkey face a new fad or a twitter bug? I think I've seen two people now use the same monkey face. |
| 15:08 | <hsivonen> | hmm. maybe it's just a coincidence that two people have chosen a face of a monkey as their avatars instead of their own face |
| 15:11 | <heedly> | What error does the video tag fire when it can't find the requested media? |
| 15:16 | <manu`> | Any Opera folks in Oslo, Norway? Everyone okay there? |
| 15:18 | <manu`> | Reason I ask is because a bomb has just gone off there - targetting the PM's government office: https://plus.google.com/102122664946994504971/posts/HRjA3xr8wXy |
| 15:19 | <jgraham> | That's not good… |
| 15:21 | <hsivonen> | BBC is running the story, so I guess the tweets are for real |
| 15:21 | <Hixie> | hsivonen, MikeSmith: apologies, i forgot to mark the download="" revision as affecting conformance checkers |
| 15:22 | <scor> | http://chatlogs.planetrdf.com/swig/2011-07-22.html#T13-45-08 |
| 15:22 | <wilhelm> | hsivonen: Yes, there was a blast: http://www.nrk.no/nyheter/norge/1.7722919 |
| 15:22 | <Hixie> | bbl |
| 15:23 | <wilhelm> | Lots of glass, but little structural damage, it seems. |
| 15:24 | <hsivonen> | wilhelm: I saw a tweet saying than "An entire block has exploded" |
| 15:24 | <manu`> | Opera HQ is 2km away from the bombing location |
| 15:24 | <hsivonen> | *that |
| 15:24 | <manu`> | Prime Minister's government HQ was attacked - PM is okay. |
| 15:28 | <wilhelm> | hsivonen: Well, this is where it hit: http://static01.vg.no/drfront/images/2011-07/22/88-0c8d07aa-11a997f9.jpeg |
| 15:28 | <wilhelm> | There are windows blown out more than a kilometer away. |
| 15:28 | <wilhelm> | Same building: http://gfx.dagbladet.no/labrador/174/174138/17413824/jpg/active/978x_13197743.jpg |
| 15:29 | <AryehGregor> | smaug____ (who isn't here): the draft doesn't have to special-case replaceData/appendData because when it was written, those just called insertData/deleteData. Now annevk has rewritten that in DOM Core at my request, and I'll rewrite the Range stuff soon to work with the new wording. As for splitText, see the comments in the spec's HTML source. IIRC, I copied the behavior from WebKit, who made it up; it makes a lot of sense, and IIRC roc t |
| 15:29 | <AryehGregor> | hought it was a good idea. Without that special-case I'd have to add a bunch of different execCommand() special-cases, so it's no simpler, and authors don't get the improved behavior. |
| 15:32 | <foolip_> | heedly, that would be MEDIA_ERR_NETWORK |
| 15:33 | <foolip_> | well, it doesn't "fire" MEDIA_ERR_NETWORK, it fires an error event and video.error.code is MEDIA_ERR_NETWORK |
| 15:40 | <annevk> | jgraham, defined next/previous sibling now and they include null; thanks! |
| 15:41 | <annevk> | jgraham, btw, it actually got worse from that bring it on comment |
| 15:41 | <annevk> | jgraham, search for "innermost" o_O |
| 15:44 | <jgraham> | annevk: I saw that. You are insane |
| 15:45 | <foolip_> | hsivonen, http://www.w3.org/Bugs/Public/show_bug.cgi?id=13329 |
| 15:45 | <annevk> | I just try to get things done until I have a better way to say things |
| 15:46 | <foolip_> | right now validator.nu is saying "Attribute muted not allowed on element audio at this point." |
| 15:46 | <foolip_> | where should I file a bug? |
| 15:46 | <jgraham> | Well I think it is good that you defined this stuff :) |
| 15:48 | <hsivonen> | foolip_: bugzilla.validator.nu is the place, but no need to file a bug, since I can just go ahead and fix it now |
| 15:48 | <foolip_> | hsivonen, much appreciated |
| 15:49 | <foolip_> | you might want to double-check the spec so that I'm not confused again |
| 15:49 | <foolip_> | I'm not 100% sure what the normative part is, but the intention is fairly clear |
| 15:56 | <annevk> | http://www.w3.org/TR/from-origin/ WD'd |
| 15:58 | <Ms2ger> | annevk++ |
| 15:59 | <hsivonen> | ouch. looks like my ISP has changed my IP address so now my servers don't let me in |
| 15:59 | <hsivonen> | good thing I have alternative permitted IP addresses to connect from |
| 16:02 | <annevk> | Ms2ger, back at you for fixing the date :) |
| 16:02 | <jgraham> | hsivonen: That sounds like quite an odd security measure. Was it opt-in? |
| 16:04 | <hsivonen> | jgraham: it's self-configured |
| 16:04 | <hsivonen> | jgraham: maybe my tin-foil hat is too thick |
| 16:04 | <hsivonen> | jgraham: but seems potentially useful in case sshd has vulnerabilities |
| 16:07 | <Ms2ger> | annevk, so, when do we obsolete it for a fetching spec? :) |
| 16:08 | <AryehGregor> | Hmm, so when you share a post on G+ it looks like it's designed so as to encourage people to comment on your share instead of the original post? That's not what I want. |
| 16:09 | <hsivonen> | heh: "The problem is RDFa is horrifically badly designed for those use cases (either because it'd badly designed, or because it wasn't intended for those use cases — I've always thought the latter, but Manu insists it's the former), and has only been getting worse." (Hixie on G+) |
| 16:09 | <annevk> | Ms2ger, when I forget why I hate working on networking specs |
| 16:09 | <Ms2ger> | :) |
| 16:10 | <AryehGregor> | Anyway, this is a potentially interesting discussion: https://plus.google.com/u/0/112095156983892490612/posts/EMADdvHSRbH |
| 16:10 | <annevk> | AryehGregor, yeah, people comment on your version of the share, but clicking on share, shares the original share |
| 16:11 | <annevk> | I think that is really confusing, but whatever |
| 16:11 | <annevk> | euh, shares what is shared |
| 16:11 | <AryehGregor> | I'd like something that just copies the original discussion to everyone who's following me. |
| 16:11 | <AryehGregor> | Without giving them any new place to leave comments. |
| 16:11 | <AryehGregor> | Like "hey, look at this interesting discussion, go and comment there". |
| 16:12 | <hsivonen> | AryehGregor: whoa. I thought the comments went onto the original |
| 16:12 | <annevk> | just close comments on your share |
| 16:12 | <hsivonen> | but now that I checked, it's not the case |
| 16:12 | <annevk> | and mention that people should go to the original |
| 16:12 | <AryehGregor> | Ah, you can close comments. |
| 16:12 | <hsivonen> | for whatever reason, the RDFa discussion is happening on my share instead of Craig Kellog's original |
| 16:12 | <AryehGregor> | Is there a link to the original post? I didn't actually see one. |
| 16:13 | <hsivonen> | I don't see a link |
| 16:14 | <annevk> | https://plus.google.com/u/0/112095156983892490612/posts/EMADdvHSRbH |
| 16:14 | <AryehGregor> | Can I add links to comments somehow? |
| 16:14 | <annevk> | oh the RDFa one |
| 16:15 | <dylangluck> | Hey guys, I'm new to the group. My name is Dylan Gluck and I am a Front-End Developer at Mars Design in NYC. I am a big fan of what you guys are doing, and would like to support in any way I can |
| 16:16 | <annevk> | be careful now ;) |
| 16:16 | <annevk> | http://wiki.whatwg.org/wiki/Specifications_TODO |
| 16:16 | <annevk> | dylangluck, there is also http://wiki.whatwg.org/wiki/What_you_can_do |
| 16:17 | <dylangluck> | Awesome! thanks annevk. I will definitely look over everything |
| 16:17 | <foolip_> | hsivonen, it's too bad that you can comment on a share at all, as opposed to commenting on the original... |
| 16:17 | <foolip_> | they seem to have optimized for the edge case where you reshare to exclude some people from the original post |
| 16:18 | <annevk> | hmm the wiki just went down? Hixie |
| 16:18 | <dylangluck> | yes I am getting no response |
| 16:18 | <annevk> | "Using an outdated version of a specification isn't comparable to using the old version of bash that ships with the enterprise Linux distro you use, it's more like planning your vacation using a decades-old globe that still has the USSR on it. You're using something that's known to be wrong, and your only hope is that the errors happen not to affect whatever part of the spec you're relying on." |
| 16:19 | <annevk> | I like that one AryehGregor :) |
| 16:19 | <Ms2ger> | AryehGregor++ |
| 16:19 | <hsivonen> | foolip_: having a "Share" function on non-Public posts is questionable in the first place |
| 16:19 | <foolip_> | hsivonen, indeed, it's too pad it's not more like retweet on twitter |
| 16:19 | <dylangluck> | back up after db error |
| 16:19 | <AryehGregor> | Yeah, seems weird to me. |
| 16:19 | <foolip_> | bad |
| 16:20 | Philip` | wonders if you could write an actual science fiction novel in the form of a specification |
| 16:20 | <dylangluck> | haha ^ |
| 16:20 | <hsivonen> | new-style retweets are also nicer, because they collapse |
| 16:20 | <dylangluck> | Thanks for the info guys, I will definitely be back |
| 16:20 | <MacTed> | encouraging background image watermarks that proclaim "obsolete" on relevant pages, and perhaps encouraging (creating?) <link @rel="obsoleted by"> and/or <link rel="obsoletes">, could go far with IETF, W3C, and others who want to preserve historical docs at their original URIs... |
| 16:20 | <MacTed> | unfortunately, <link rel="canonical"> requires starting from the position that "this doc will change" and few standards are created with their evolution in mind. |
| 16:20 | <annevk> | dylangluck, sorry about that; most people typically start out by giving feedback on specs |
| 16:20 | <hober> | We MUST niuke it from orbit. It MAY be the only way to be sure. |
| 16:20 | <dylangluck> | absolutely |
| 16:21 | <hsivonen> | when 5 people reshare a post in my stream, I'd like their commentary to stack onto one item instead of having 5 items |
| 16:21 | <dylangluck> | i am not a preogrammer |
| 16:21 | <annevk> | dylangluck, but there's also writing tests (which involves giving feedback), and writing specs if you're up for it |
| 16:21 | <foolip_> | Philip`, I'd read it! |
| 16:21 | <Ms2ger> | Writing tests would be awesome |
| 16:21 | <annevk> | hsivonen, you want RT |
| 16:21 | <Philip`> | You could hint at lots of background through examples and references and implicit assumptions about what's implementable, so I imagine it wouldn't be impossible to tell a story |
| 16:21 | <Ms2ger> | foolip_, more than a page of it? :) |
| 16:22 | <scor> | AryehGregor, hsivonen: is that the url you are looking for (original post)? https://plus.google.com/u/0/115239936584020095918/posts/KPNTayJ3eNW but the fact remains, I had to go to Gregg's profile and look for his post (no link from Henri's profile) |
| 16:22 | <dylangluck> | just a developer who loves the idea of expanding on what the WHATWG has done and giving some feedback |
| 16:22 | <Philip`> | Also you can use deprecated features or weird quirks to indicate the history of your story world |
| 16:22 | <scor> | in any case, this is where the conversation is happening, on hsivonen's profile: https://plus.google.com/u/0/115203359751471044302/posts/92VKitpppB4 |
| 16:22 | <annevk> | dylangluck, sounds good |
| 16:23 | <foolip_> | Ms2ger, that depends on how well it manages to incorporate obscure references to spec discussions/wars that make me feel clever by recognizing them |
| 16:23 | <AryehGregor> | scor, I was talking about the post on Jeni Tennison's profile. |
| 16:23 | <Ms2ger> | Heh |
| 16:23 | <AryehGregor> | I wound up posting a link in my share, and disabling comments. |
| 16:24 | <foolip_> | is it just me, or is it very difficult to get from a Google+ share to the original post? |
| 16:24 | <AryehGregor> | It is. |
| 16:24 | <AryehGregor> | We were just saying. |
| 16:24 | <AryehGregor> | You have to go to the profile and scroll down until you find it. |
| 16:24 | <foolip_> | yeah, that's what I'm doing |
| 16:24 | <Ms2ger> | "Note: This requirement is not present in the Foo version of this specification due to a flame war in the 4th century" |
| 16:24 | <hsivonen> | s/Craig/Gregg/ |
| 16:24 | <AryehGregor> | That's why I posted a link: https://plus.google.com/100662365103380396132/posts |
| 16:25 | <annevk> | the number of times I type "hg make"... |
| 16:33 | <hsivonen> | hmm. looks like Safari 5.1 isn't available for Leopard |
| 16:33 | <hsivonen> | I guess that's going to slow down MathML and inline SVG adoption |
| 16:34 | <AryehGregor> | Safari 5.1 has MathML support? How good is it? |
| 16:34 | <AryehGregor> | Does Chrome also have it? |
| 16:34 | <hsivonen> | AryehGregor: based on hearsay, Chrome doesn't |
| 16:34 | <Rik`> | hsivonen: I don't really think so, Apple users are quickly using the latest version |
| 16:35 | <hsivonen> | Rik`: do you have Leopard vs. Snow Leopard stats? |
| 16:35 | <hsivonen> | I assumed that some users hadn't bothered to update because of "no new features" |
| 16:36 | <hober> | which is too bad, since SL is way better than leopard |
| 16:36 | <Rik`> | hsivonen: I don't at the moment but I think Leopard users are quite irrelevant |
| 16:36 | <Rik`> | maybe less than 1% of all web users |
| 16:37 | <Rik`> | and mostly it's PPC users since Snow Leopard is not compatible |
| 16:37 | <AryehGregor> | hsivonen, http://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm |
| 16:38 | <hsivonen> | Rik`: http://stats.wikimedia.org/wikimedia/squids/SquidReportOperatingSystems.htm suggests that the numbers for Intel Leopard are quite high relative to Intel Snow Leopard |
| 16:38 | <AryehGregor> | If you want OS: http://stats.wikimedia.org/wikimedia/squids/SquidReportOperatingSystems.htm |
| 16:38 | <AryehGregor> | Yeah. |
| 16:38 | <hsivonen> | Rik`: also, Intel Leopard much higher than PPC Leopard |
| 16:39 | <AryehGregor> | Leopard is at 1.78% of total OS market share, Snow Leopard is 5.04%, so Leopard is a really big chunk. |
| 16:39 | <Rik`> | oh right |
| 16:39 | <AryehGregor> | 10.4 is 0.31%. |
| 16:39 | <AryehGregor> | Which is to say, apparently, Tiger. |
| 16:39 | <hsivonen> | I wonder what the security patch situation for Leopard is now that Leopard + 2 is out |
| 16:41 | <Rik`> | there is no security update for Snow Leopard yet |
| 16:43 | <hsivonen> | Rik`: security update for what holes? |
| 16:43 | <Rik`> | I don't know but it's usual to launch a security update for the n -1 version when you launch the n version |
| 16:44 | <hsivonen> | Rik`: they did release a point release of 10.6.x a bit earlier, though |
| 16:44 | <Rik`> | oh ok, haven't seen it |
| 16:45 | <hsivonen> | anyway, StatCounter's stats suggest that Safari 5.0 users on Snow Leopard aren't applying the 5.1 update immediately |
| 16:46 | <miketaylr> | hsivonen: i just tried software update and 5.1 is available to snow leopard, it seems |
| 16:46 | <Rik`> | hsivonen: http://support.apple.com/kb/HT1222 |
| 16:46 | <Rik`> | looks like they launched Safari 5.0.6 for Leopard http://support.apple.com/kb/HT4808 |
| 16:48 | <AryehGregor> | Why is it not called Safari 6? Is there a full update of WebKit to something recentish? |
| 16:48 | AryehGregor | hopes there's a full WebKit update and they just didn't change enough UI to call it a major version bump |
| 16:48 | <TabAtkins> | hsivonen: I think that shares are separated so that ACLs don't collide. But I agree that if you sent it to public, and other people reshare it to public, it would be niuce to collapse them. |
| 16:50 | <hober> | AryehGregor: http://svn.webkit.org/repository/webkit/branches/ |
| 16:58 | <annevk> | emailed WebApps about Traversal |
| 16:58 | <annevk> | first draft done |
| 16:59 | <AryehGregor> | Fun discovery: default link color in WebKit (at least Chrome) is -webkit-link, which appears to compute to rgb(0, 0, 238). |
| 16:59 | <AryehGregor> | Not, um, blue? |
| 16:59 | <AryehGregor> | Yay interop? |
| 17:00 | <AryehGregor> | A.k.a. #00e, I guess. |
| 17:01 | <AryehGregor> | This kind of thing does affect interop in some cases . . . grumble grumble. |
| 17:01 | <Ms2ger> | Does anybody use actual blue? |
| 17:02 | <AryehGregor> | HTML5 says to . . . |
| 17:02 | AryehGregor | tests |
| 17:02 | <hsivonen> | foolip_: I deployed <audio muted> to validator.nu |
| 17:02 | <AryehGregor> | Hmm. |
| 17:02 | <AryehGregor> | Ms2ger, good point, this looks like a spec bug. |
| 17:02 | <foolip_> | hsivonen, confirmed working, thanks! |
| 17:03 | <AryehGregor> | So Gecko and WebKit are #00e. |
| 17:06 | <AryehGregor> | IE10PP2 is rgb(0, 102, 204), which is what? #06c. And Opera 11.50 is #00c. |
| 17:06 | <AryehGregor> | Oh, wait. |
| 17:06 | <AryehGregor> | No, it's fine, that's not visited. |
| 17:06 | AryehGregor | tests :visited, although Gecko will lie about it |
| 17:06 | <Philip`> | (Can't you test it trivially with a screenshot and Gimp/etc's colour picker tool?) |
| 17:06 | <AryehGregor> | Yes, if I wanted to do that much work. :) |
| 17:07 | <AryehGregor> | For visited, Gecko lies. Opera is #800080. IE10PP2 seems to be still reporting #06c, is it lying too? |
| 17:07 | AryehGregor | uses dev tools |
| 17:07 | <AryehGregor> | I'd use dev tools for Firefox too, except you know, Firebug doesn't work on Aurora. |
| 17:07 | <AryehGregor> | (or are there basic built-in DOM inspection things these days?) |
| 17:08 | <AryehGregor> | #551A8B in Chrome, it looks like. |
| 17:09 | <AryehGregor> | There's an Inspect tool somewhere, but it doesn't seem to do anything very useful . . . |
| 17:10 | <Philip`> | Firefox's about:config says browser.visited_color = #551A8B |
| 17:10 | <Rik`> | AryehGregor: I think Firebug 1.8 works |
| 17:10 | <AryehGregor> | Rik`, not unless they updated it in the last few days. |
| 17:10 | <AryehGregor> | It works with current beta, but not Aurora. |
| 17:11 | <AryehGregor> | Ah, they did update it. |
| 17:11 | AryehGregor | tries |
| 17:11 | <AryehGregor> | Yay, works again! |
| 17:12 | AryehGregor | makes a mental note never to upgrade Aurora again without checking Firebug compat |
| 17:12 | <AryehGregor> | Firebug lies about visited link color too, though. |
| 17:12 | <AryehGregor> | So I'll rely on Philip` here. |
| 17:12 | AryehGregor | doesn't bother trying to figure out IE |
| 17:12 | Rik` | makes a mental note never to use Firebug until https://bugzilla.mozilla.org/show_bug.cgi?id=669730 is fixed |
| 17:12 | <Philip`> | I might be lying too, of course |
| 17:13 | <AryehGregor> | Rik`, I don't use Firefox for anything other than testing, so it can leak all it wants. |
| 17:13 | <AryehGregor> | Also, that's why my new laptop has 8G of RAM. |
| 17:13 | <Rik`> | I do use Firefox so I do my debugging in other browsers |
| 17:15 | <AryehGregor> | http://www.w3.org/Bugs/Public/show_bug.cgi?id=13330 |
| 17:18 | <AryehGregor> | Links that are actually blue do look noticeably bright. |
| 17:45 | <david_carlisle> | AryehGregor: Chrome doesn't have MathML, presumably they could pick it up, as it's implemented in the webkit base |
| 17:53 | <AryehGregor> | :( |
| 18:03 | <dglazkov|away> | MathML --> splosion. |
| 18:03 | <dglazkov> | good morning, Whatwg |
| 18:03 | <Ms2ger> | Evening, dglazkov |
| 18:07 | <dglazkov> | Ms2ger: :) |
| 18:13 | <annevk> | used to be that dglazkov checked in in the afternoon |
| 18:14 | <annevk> | :p |
| 18:14 | <dglazkov> | had to run an errand this morning. |
| 18:30 | <sicking> | Hixie: would you mind updating the EventSource spec to add the {withCrededentials: true} syntax? So that we can avoid prefixing it |
| 18:33 | <annevk> | just adding it to the spec doesn't exactly make it a done deal |
| 18:34 | <annevk> | do we know if WebKit agrees? |
| 18:37 | <AryehGregor> | sicking, isn't the theory that standard but experimental stuff is prefixed too? Or is that only CSS for some reason? |
| 18:44 | <TabAtkins> | CSS has a firm policy that everyone voluntarily follows. JS is pretty loosy-goosy about it. |
| 18:46 | <dglazkov> | JS is pretty loosy-goosy about _everything_. |
| 19:06 | <AryehGregor> | Wow, it's 102 degrees outside. |
| 19:07 | <AryehGregor> | (For those of you who like sane temperature scales, that would be 312 K.) |
| 19:07 | <TabAtkins> | Ah, thank you, I can never think in F. |
| 19:07 | <TabAtkins> | Or C. |
| 19:08 | <Philip`> | I prefer to think of it as 1.78 radians |
| 19:08 | <Ms2ger> | Well played |
| 19:09 | <scor> | AryehGregor: where is that? |
| 19:09 | <AryehGregor> | scor, Manhattan. |
| 19:10 | <scor> | only 4 degrees cooler up here in Boston |
| 19:46 | <scor> | was there ever a time where the content attribute was allowed in tags other than meta to override textContent in microdata? or has @content always been only allowed in <meta>? |
| 19:47 | <annevk> | always |
| 19:49 | <scor> | annevk: thanks |
| 19:58 | <Hixie> | sicking: are other browsers in agreement? |
| 20:01 | <annevk> | http://www.w3.org/2001/tag/2011/07/21-minutes.html#item04 lol the task force conclusions are not in line with what i want, please do it again! |
| 20:03 | <Hixie> | i don't even understand those minutes |
| 20:04 | <annevk> | armchair troublemakers |
| 20:16 | annevk | replies to an email from November 2009 |
| 20:37 | <annevk> | Would be pretty nifty if ij updates older specifications in this simple process manner |
| 20:38 | <annevk> | HTML4 could use a note :) |
| 20:40 | Ms2ger | lacks context |
| 20:41 | <annevk> | public-webapps |
| 20:47 | <annevk> | where is mike? |
| 20:47 | <annevk> | should remove DOM Traversal from http://platform.html5.org/ |
| 20:49 | <Ms2ger> | Could try... |
| 20:49 | <Ms2ger> | Aww |
| 20:57 | <annevk> | Ms2ger, you mean the reply from ij? |
| 20:57 | <annevk> | I guess I should not have gotten my hopes up |
| 21:03 | <annevk> | oh hey |
| 21:03 | <annevk> | Opera invented INVALID_STATE_ERR for recursive traversal invocations |
| 21:03 | <annevk> | and Gecko copied it |
| 21:03 | <annevk> | you don't see that very often |
| 21:04 | <annevk> | thanks for the pointer sicking :) |
| 21:07 | <jamesr> | annevk: i thought opera invented everything |
| 21:08 | <karlcow> | http://elie.im/blog/security/tracking-users-that-block-cookies-with-a-http-redirect/ |
| 21:08 | <karlcow> | jamesr: this is a truism |
| 21:08 | <annevk> | jamesr, I think that particular rhetoric typically only applies to UI stuff |
| 21:09 | <annevk> | jamesr, assuming you are referring to the pointless debates on who did tabs / speed dial / mouse gestures / whatnot first |
| 21:09 | <karlcow> | it applies to love, joy, tears, emotions, etc. I mean how could not feel anything at Carmen |
| 21:10 | <Ms2ger> | Don't you know that we all use "Opera did it first" to laugh at you guys? :) |
| 21:11 | <annevk> | Ms2ger, heh, I didn't |
| 21:11 | <annevk> | Ms2ger, but I can certainly see the fun in that :) |
| 22:08 | <annevk> | I wonder how Page Visibility went to Last Call |
| 22:08 | <annevk> | prolly because all these new WGs have like zero oversight |
| 22:10 | <Ms2ger> | The Process only applies to relevant WGs |
| 22:10 | <Yuhong> | So, on https://plus.google.com/112095156983892490612/posts/EMADdvHSRbH, describe the "substantial changes" that would be needed in detail. |
| 22:10 | Ms2ger | yawns |
| 22:11 | <annevk> | Ms2ger, curb your enthusiasm is back |
| 22:11 | <Yuhong> | And won't the substantial changes be limited by compatibility with existing content and implementations? |
| 22:12 | <annevk> | I searched for "substantial changes" in that link and it yielded nothing |
| 22:12 | Ms2ger | throws a PARSE_ERR at annevk |
| 22:12 | <annevk> | Ms2ger, search for the first three words and watch it :) |
| 22:12 | <jamesr> | i didn't know the w3 had a process to rescind a recommendation |
| 22:12 | <Yuhong> | Sorry, look at the mailing list post linked. |
| 22:13 | <Ms2ger> | I did! :) |
| 22:13 | <Ms2ger> | I also know the history of boolean attributes |
| 22:13 | <Ms2ger> | Both pieces of knowledge are equally useless |
| 22:13 | <Yuhong> | Sorry, substantive changes . |
| 22:14 | <AryehGregor> | Yuhong, Maciej's post starting the thread there is pretty clear about what qualifies as a substantive change. |
| 22:14 | <AryehGregor> | It's very broad. |
| 22:14 | <AryehGregor> | Basically, any change that anyone other than a bike-shedder has reason to care about. |
| 22:14 | <annevk> | Ms2ger, for when your children ask you to tell them once more the story about boolean attributes |
| 22:15 | <Yuhong> | BTW, I just recently learned the history of HTML 3.0 and Netscape too. |
| 22:15 | <Ms2ger> | "Daddy, what's SGML"? |
| 22:15 | <annevk> | Ms2ger, zcorpan meanwhile tells his about SHORTTAG NET and how things were before he figured out legacy color parsing |
| 22:15 | <Ms2ger> | Hah |
| 22:16 | <TabAtkins> | I'm very glad I didn't have to figure out legacy color parsing myself. |
| 22:16 | <TabAtkins> | That shit's crazy. |
| 22:16 | <Ms2ger> | TabAtkins, how about trying to figure out CSS parsing in quirks mode? :) |
| 22:16 | <TabAtkins> | I'm gonna... I'm gonna not do that. |
| 22:16 | <annevk> | Yuhong, you want to read the W3C Process document for a definition of that term |
| 22:17 | <annevk> | Yuhong, if you are after "substantive changes" |
| 22:20 | <Ms2ger> | Notes, notes, notes |
| 22:20 | <Ms2ger> | One for CSS2.1 too? :) |
| 22:20 | <TabAtkins> | 2.1 is the most recent and accurate reference! |
| 22:20 | <Ms2ger> | Still a disaster :) |
| 22:21 | <TabAtkins> | And we have a note on CSS2 along those lines. |
| 22:21 | <Ms2ger> | But less of a disaster than the rest of CSS, I'll grant you that |
| 22:22 | <TabAtkins> | Relatively speaking, 2.1 is one of the best specs the W3C has produced. We actually have a large (though still not large enough) test suite. |
| 22:23 | <Yuhong> | In fact, I learned that the history of CSS1 is related to the history of HTML 3.0. |
| 22:23 | <annevk> | XSLT and XML are pretty watertight (and way simpler) |
| 22:23 | <Yuhong> | More history: http://www.reddit.com/r/web_design/comments/exnr8/on_netscape_and_css_history_heres_the_history/ |
| 22:23 | <annevk> | CSS 2.1 has a lot of handwaving still :( |
| 22:24 | <TabAtkins> | annevk: I said "relatively" ^_^ |
| 22:30 | <annevk> | I wonder why you need a whole WG for something like page visiblity |
| 22:30 | <annevk> | two new attributes on Document |
| 22:33 | <Hixie> | beats me |
| 22:39 | <annevk> | jgraham, you look sad on your G+ photo |
| 22:39 | <annevk> | well, more disinterested, which might be accurate I suppose :p |
| 22:40 | <Yuhong> | So what are examples of "substantive changes" that might be needed in the future? |
| 22:41 | <annevk> | Yuhong, http://www.w3.org/2005/10/Process-20051014/tr.html#substantive-change |
| 22:42 | <Yuhong> | Sorry, there was no Glossary, making it hard to find. |
| 22:43 | <annevk> | glad you looked at least |
| 22:43 | <annevk> | :) |
| 22:44 | <Ms2ger> | annevk, want to tell them they need a reference to WebIDL as well? |
| 22:44 | <annevk> | Ms2ger, can do |
| 22:45 | <Yuhong> | So what are examples of "substantive changes" that might be needed in the future, or the HTML5 spec quickly becomes inaccurate? |
| 22:45 | <Yuhong> | I am looking for specific examples. |
| 22:46 | <Hixie> | how can we know...? |
| 22:46 | <annevk> | we might have to remove an attribute that's not implemented |
| 22:46 | <annevk> | we might have to change an attribute because it's implemented incorrectly |
| 22:46 | Ms2ger | stays out of this |
| 22:47 | <annevk> | good idea |
| 22:47 | <annevk> | if Ms2ger is still reading the logs: http://lists.w3.org/Archives/Public/public-web-perf/2011Jul/0080.html |
| 22:47 | <Yuhong> | Candidate Recommendation is exactly the place to prove everything is implemented. |
| 22:47 | <Yuhong> | If it is not, it will be removed. |
| 22:48 | <annevk> | hey man, if you already know, don't ask |
| 22:49 | <Yuhong> | My point is that it is an already solved problem. |
| 22:50 | <Yuhong> | I mean, the W3C process already solves this problem. |
| 22:51 | <Yuhong> | With Candidate Recommendation and the tests etc. |
| 22:51 | <annevk> | yes, you have to revert to WD after a substantive change |
| 22:51 | <Yuhong> | Yes, but why would it loop forever? |
| 22:53 | <Yuhong> | Yes, I am well aware of CSS 2.1, and how it looped several times. |
| 22:53 | <annevk> | because with a spec this size you are bound to find something |
| 22:53 | <annevk> | CSS 2.1 would have looped way more if the WG fixed all outstanding issues |
| 22:53 | <TabAtkins> | 2.1 stopped looping because we made several things undefined. |
| 22:53 | <TabAtkins> | Unrelated: This is ridiculously good - http://research.microsoft.com/en-us/um/people/kopf/pixelart/supplementary/multi_comparison.html |
| 22:54 | <TabAtkins> | The "Ours" scaling algo |
| 22:56 | <Yuhong> | Yep, I know. In contrast, CSS3 is modularized and so far it loops less I think. |
| 22:57 | <TabAtkins> | Indeed, but that brings its own problems. |
| 22:57 | <AryehGregor> | The whole issue of looping is only because the W3C Process demands that specs progress as a unit. |
| 22:57 | <AryehGregor> | WHATWG HTML has per-section annotations and it works fine. |
| 22:57 | <AryehGregor> | It would be really nice if we could get a usable subset spec that only includes things that are known to be followed more or less completely by at least two major browsers, though, or something like that. |
| 22:58 | <AryehGregor> | Or at least leaving out the stuff that's really speculative or cutting-edge. |
| 22:58 | <AryehGregor> | (maybe leaving in the stuff that's implemented by everyone but not interoperably) |
| 22:59 | <AryehGregor> | Hmm, Maciej never got back to me about innerText yet, did he? |
| 22:59 | <AryehGregor> | I'll have to poke him again. |
| 23:00 | <Yuhong> | I think being implemented by at least two implementations interoperably is part of the W3C process already. |
| 23:01 | <Hixie> | css3 is older than css2.1 :-) |
| 23:01 | <Hixie> | so clearly it doesn't loop less :-) |
| 23:01 | <TabAtkins> | I don't acknowledge the existince of pre-2.1 css3. |
| 23:02 | <Yuhong> | The year-long gap in CSS3 working drafts that existed since 1999 I think is partly because there was no point in doing it when IE6 had a monopoly and did not implement much of CSS2. |
| 23:03 | <Yuhong> | And remember that CSS2.1 did not exist when IE6 was released. |
| 23:06 | <dglazkov> | TabAtkins: this page made we want to play Mario |
| 23:06 | <TabAtkins> | I know! |
| 23:07 | <Hixie> | Yuhong: from being in the wg, i assure you your assumptions are wrong |
| 23:07 | <Hixie> | Yuhong: it was more because we were focusing on css2.1 and had insufficient editors |
| 23:07 | <Hixie> | a problem the wg still has |
| 23:08 | <Hixie> | TabAtkins: amazing how some of those pictures scale amazingly well with their algorithm and others look really dumb |
| 23:08 | <Hixie> | TabAtkins: does seem to be almost always the best or second-best algo though |
| 23:09 | <TabAtkins> | Hixie: Yeah. It looks like it does worst on the ones that had the most care given to them. Lost Vikings, frex. |
| 23:09 | <TabAtkins> | Lesson: Don't make your sprites too pretty. Future higher-rez generations will appreciate your highly-contrasting colors. |
| 23:10 | <Hixie> | TabAtkins: yeah, or the icons that were meant to have hard edges, like the Setup icon which turns into a clay cartoon |
| 23:10 | <Hixie> | kinda funny how bicubic is really just squinting for you |
| 23:10 | <Hixie> | i hadn't realised that before |
| 23:11 | <Yuhong> | That is why I say partly. |
| 23:11 | <TabAtkins> | Yeah, it's very overtly a blur. |
| 23:12 | <Hixie> | Yuhong: it wasn't even partly. there was no relationship to IE. |
| 23:12 | <Hixie> | hq4x seems to not actually work beyond 4x zoom? |
| 23:13 | <TabAtkins> | That would be the origin of the name, yes. |
| 23:13 | <Hixie> | aah |
| 23:13 | <Hixie> | ok |
| 23:13 | <Hixie> | seems unfair to show that one for the higher zooms then |
| 23:13 | <TabAtkins> | (There's an hq2x and 3x too.) |
| 23:13 | <Hixie> | for 4x it's better than theirs for some of them |
| 23:13 | <Hixie> | e.g. setup |
| 23:13 | <Hixie> | and control panel |
| 23:14 | <Hixie> | basically this algorithm does really well when the underlying graphic has curves, and not so well when it has straights |
| 23:15 | <Hixie> | makes sense that one algorithm wouldn't be able to distinguish the two cases, of course |
| 23:15 | <Hixie> | bbiab. |
| 23:16 | <zewt> | it looks identical to "EPX" (whatever that is), but with some kind of smoothing applied |
| 23:16 | <TabAtkins> | Yeah, looks like the two make pretty similar coloring decisions. |
| 23:16 | <zewt> | and you can sort of intuitively see what EPX is doing, though i havn't squinted at it hard enough to know exactly |
| 23:17 | <TabAtkins> | It's a really easy algorithm. Wikipedia has details. |
| 23:18 | <Yuhong> | Fun fact: One of the modules dates back to a proposal from 1996: http://www.w3.org/Style/CSS/multi-column.html |
| 23:18 | <Yuhong> | Also see: http://lists.w3.org/Archives/Public/www-html/1996Jun/0234.html |
| 23:19 | <Yuhong> | And consider the fact it will be IE10 before that module will finally get implemented. |
| 23:22 | <zewt> | the scaling might not actually work well for animated sprites, though, since the interpolation would probably wobble around, lacking any cohesion across frames |
| 23:23 | <TabAtkins> | zewt: I wonder if I can find the algo and implement it myself. |
| 23:23 | <zewt> | it looks like it's using EPX in vertex form and just applying some standard smoothing algorithm |
| 23:23 | <TabAtkins> | zewt: I think you're right that it's identical to EPX except for the region-shaping algorithm. |
| 23:25 | <jamesr> | there's a siggraph paper, i believe |
| 23:31 | <annevk> | when are these hangouts coming without plugins? |
| 23:34 | <sephr> | What's the reasoning behind limiting crypto.getRandomValues() to integers only? It introduces an extra unnecessary step when you want random floats: var nums = new Float64Array(10); crypto.getRandomValues(new Uint8Array(nums.buffer)); |
| 23:35 | <sephr> | I don't see the point of having to do new Uint8Array(floats.buffer) |
| 23:35 | <Hixie> | annevk: at a minimum, browsers would have to support PeerConnection and getUserMedia() (or their equivalents in other proposals) before that can happen |
| 23:36 | <sephr> | and not to mention that it doesn't make sense to not allow crypto.getRandomValues() on an plain ArrayBuffer acting as a binary blob that you don't need indexes on |
| 23:42 | <TabAtkins> | zewt: As for animation, http://www.youtube.com/watch?v=o2Fd-4NzB0w |
| 23:59 | <fishd> | Hixie: i'm curious why you restricted a@download to require a user gesture |
