| 03:27 | <Hixie> | what's with all the bugs that the htmlwg is just marking invalid without even the boilerplate "how to reopen this bug" thing? |
| 03:27 | <Hixie> | anyone know anything about that? |
| 03:27 | <Hixie> | e.g. https://www.w3.org/Bugs/Public/show_bug.cgi?id=18223 https://www.w3.org/Bugs/Public/show_bug.cgi?id=16512 https://www.w3.org/Bugs/Public/show_bug.cgi?id=16022 |
| 03:57 | <cabanier> | that's an error on the editor's part. |
| 03:59 | <cabanier> | we've been told to always add the boilerplate |
| 04:09 | <Hixie> | k |
| 06:44 | <annevk> | I thought for obviously bogus bugs that was not required |
| 07:12 | <nessy> | I thought so, too - but I would have still added the boilerplate ;-) |
| 09:15 | <annevk> | I wish git and such had a thing similar to a "this is a minor edit" as seen on wikis |
| 09:17 | <jgraham> | git commit --fiuxup (revision) |
| 09:17 | <jgraham> | *--fixup |
| 09:18 | <jgraham> | typically git commit --fixup HEAD |
| 09:18 | <jgraham> | and then git rebase -i --autosquash rev_of_branch_base |
| 09:18 | <jgraham> | before you push to remove the fixups from the history entirely |
| 09:20 | <jgraham> | e.g. if you have the existing history A-B-C and you write new commits D-E-E1 so the history is A-B-C-D-E-E1, and E1 is a fixup of E (so you wrote git commit --fixup E to make that revision) |
| 09:21 | <jgraham> | You would git rebase -i --autosquash C |
| 09:21 | <jgraham> | Which would leave you with new history A-B-C-D-E' |
| 09:21 | <jgraham> | With E' = E + E1 |
| 10:01 | <annevk> | karlcow: is splitting on ":" not simple enough? |
| 10:01 | <karlcow> | see the PS :) |
| 10:01 | <annevk> | heh |
| 10:02 | <annevk> | jgraham: I guess I should learn git |
| 10:02 | <annevk> | jgraham: I've been using github's tool for Mac, but it allows no such things |
| 10:14 | <annevk> | Is http://url.spec.whatwg.org/#goals clear enough? |
| 11:06 | <annevk> | have to hand it to Hixie, these new URLs are growing on me |
| 11:12 | <jgraham> | annevk: "Call them URLs" doesn't seem like a goal. |
| 11:13 | <jgraham> | That seems like something that you either do or you don't |
| 11:13 | <jgraham> | "standardize on the term URL" sounds more like a goal |
| 13:30 | karlcow | not replying to something which is about URL syntax only. |
| 14:03 | <adlwalrus> | Hixie: do you have any thoughts on http://coding.smashingmagazine.com/2011/11/11/our-pointless-pursuit-of-semantic-value/ ? |
| 15:44 | <Ms2ger> | krijn, seems like http://krijnhoetmer.nl/irc-logs/ isn't updating |
| 15:56 | <krijn> | That bastard! |
| 16:36 | <dglazkov> | good morning, Whatwg! |
| 16:39 | <espadrine> | dglazkov: good morning to you too! ☺ |
| 18:34 | <Hixie> | annevk: none of those three were "obviously bogus", though |
| 19:31 | <Hixie> | any test suite people around? jgraham? |
| 19:31 | <Hixie> | not sure what to do about https://www.w3.org/Bugs/Public/show_bug.cgi?id=15042 |
| 19:31 | <Hixie> | the W3C test suite is now intentionally actively testing something that is contrary to the good of the web and what browsers want to implement |
| 20:00 | <jgraham> | Hixie: bugger |
| 20:00 | <jgraham> | OK, I guess this is the point at which I propose doing something like branching the testsuite |
| 20:03 | <Hixie> | jgraham: where is it canonically hosted currently? github? |
| 20:08 | <jgraham> | dvcs.w3.org |
| 20:09 | <jgraham> | But this is Yet Another Reason to move to git, because branches in mercurial seem to be harder to use |
| 20:09 | <jgraham> | Or at least they have about three types of branch rather than one |
| 20:09 | <jgraham> | and the most useful of those three is a non-default extension |
| 20:10 | <Hixie> | you gonna need somewhere to host the fork? or? |
| 20:10 | <Hixie> | i can set up tests.whatwg.org or something if you want to manage it |
| 20:11 | <Hixie> | just say the word |
| 20:11 | <jgraham> | I think we are OK for now |
| 20:12 | <jgraham> | I am hopeful that we can end up with a single git repo with two branches rather than multiple repos |
| 20:12 | <Hixie> | jgraham: k |
| 20:12 | <Hixie> | jgraham: well, let me know what you want, if you need anything. |
| 20:12 | <Hixie> | off to lunch now |
| 20:12 | <jgraham> | Sure. Thanks |
| 21:07 | <chaotixx> | hi |
| 21:09 | <chaotixx> | is anyone here? i am petty novice at web develoment, and could really use help with something.... on the page http://www.firestonecompleteautocare.com/maintenance/schedule.jsp i am trying to copy the blue box contained on the page and its functions... i am able to coy and recreate the box, but i dont know what i will need to do what it does |
| 22:19 | <SamB_MacG5> | well, it is certainly simple |
| 22:22 | <zewt_> | it should have been a lot simpler, heh |
| 22:26 | SamB_MacG5 | supposes Python doesn't have any such facility for arrays either, come to think of it ... |
| 22:42 | <annevk_> | http://lists.w3.org/Archives/Public/uri/2012Sep/0002.html kind of an IETF-centric definition of obsolete there |
| 22:42 | <annevk_> | I was using it in the broad sense, in case anyone cares |
| 22:42 | <annevk_> | And is someone still subscribed to www-tag? |
| 22:42 | <annevk_> | It appears they are confused about where the URL Standard is located... |
| 22:44 | <SamB_MacG5> | zewt: on the other hand, if it was more complicated that might mean less bikeshedding ;-P |
| 22:48 | <zewt> | don't know that there's much bikeshedding on that api (though i havn't been following webgl-dev for a couple months) |
| 23:51 | <jamesr_> | Hixie_, so you've decided to let the UA pick a resolution however it likes for canvas 2d? |
| 23:51 | <TabAtkins> | That was the intent all along. |
| 23:51 | <jamesr_> | fwiw my thinking is that we'll always set this to 1 regardless of the display's properties. setting it to anything else is too problematic |
| 23:53 | <zewt> | jamesr: what problems are there that the addition of toDataURLHD and toBlobHD don't fix? |
| 23:53 | <jamesr_> | weird that it's tied to a task |
| 23:53 | <jamesr_> | and not the element (although all options here are weird) |
| 23:53 | <Hixie_> | jamesr_: webkit already picks higher res backing resolutions, at least for safari |
| 23:53 | <Hixie_> | jamesr_: are there any new problems that aren't handled? |
| 23:53 | <jamesr_> | safari on desktop does. chrome and mobilesafari don't |
| 23:55 | <Hixie_> | jamesr_: well not ever using higher res backing stores is a non-starter. |
| 23:55 | <Hixie_> | jamesr_: but if there are problems not currently addressed, please do mention them on the list |
| 23:55 | <jamesr_> | how do you mean? |
| 23:55 | <TabAtkins> | Hixie_: I'll be separately encouraging our implementation to name the function ellipseTo when we implement it. |
| 23:56 | <jamesr_> | Hixie_, we currently set the backing store to whatever the width/height attributes are set to. seems to work out fine |
| 23:56 | <Hixie_> | jamesr_: i mean, retina macbook pros look ugly as hell on chrome |
| 23:56 | <jamesr_> | depends on the content |
| 23:56 | <Hixie_> | when they have canvases |
| 23:57 | <Hixie_> | TabAtkins: i'll be encouraging us not to implement the more complicated path syntax too :-P |
| 23:58 | Hixie_ | really does think it's a terrible design choice to be doing this |