| 00:17 | <zewt> | because mouse events are dumb, and as far as I know you can't (reliably) |
| 00:17 | <zewt> | (other than unreliable hacks, like adding a click listener on mouseup and removing it in a timer) |
| 06:13 | <Hixie_> | zewt: i ended up just not bothering with click and doing all the work in mousedown/mouseup |
| 07:53 | <darobin_> | a browser validated in Coq, that's for jgraham http://goto.ucsd.edu/quark/ |
| 08:01 | <Ms2ger> | MikeSmith, so, actually, I didn't want a keyword for "Indicates that a test case for this bug is included somewhere in the bug report.", I wanted one for "has a test in the test suite" |
| 09:08 | <annevk> | Ms2ger: pong |
| 09:09 | <Ms2ger> | annevk, I was looking at http://dom.spec.whatwg.org/#concept-node-replace-all... |
| 09:10 | <Ms2ger> | Step 5 queues a mutation record with addedNodes and removedNodes set |
| 09:10 | <Ms2ger> | But those seem to be only used if "addedNodes, removedNodes, previousSibling, and nextSibling are given" |
| 09:11 | <annevk> | Also, step 4 sets it to null rather than the empty list, that might be wrong too, no? |
| 09:11 | <Ms2ger> | Well, this was my first issue :) |
| 09:12 | <Ms2ger> | "node's children" in the DocumentFragment case in step 4 is going to be empty after step 3 |
| 09:13 | <Ms2ger> | And "parent's children" in step 5 are the new nodes by that point |
| 09:15 | <annevk> | Ms2ger: so let's see; in http://dom.spec.whatwg.org/#queue-a-mutation-record 4.3 we want to split that up in four distinct steps to set the properties properly |
| 09:16 | <Ms2ger> | So it's supposed to mean "for each that's given, set it"? |
| 09:16 | <Ms2ger> | Makes sense |
| 09:16 | <annevk> | Ms2ger: yeah, maybe word it that way |
| 09:17 | <annevk> | Ms2ger: and then a bunch of variable re-ordering in replace-all |
| 09:17 | <Ms2ger> | Yep |
| 09:17 | <Ms2ger> | And that null thing |
| 09:18 | <annevk> | What a mess |
| 09:47 | <annevk> | Ms2ger: fixed I think |
| 09:47 | <Ms2ger> | Thanks, will check in a bit |
| 10:02 | <jgraham> | Anyone able to contact Lachy? It would be nice to know if there's a reason for /selectors-api/tests/submissions/Opera/level1/* |
| 10:02 | <jgraham> | In web-platform-tests |
| 10:07 | <jgraham> | Well they diff identical so I think I am happy to remove them |
| 10:07 | <jgraham> | (identical to tests not under submission/) |
| 10:08 | <Ms2ger> | r=me |
| 10:18 | <jgraham> | Hmm, I seem to be typing "blink" and wondering why it doesn't launch chrome[ium] |
| 10:48 | <annevk> | So if you have an object that represents a list of name/value pairs. Would you still expose getNames() and getValues() or would you just have an iterator that returns {name, value} objects? |
| 10:49 | <jgraham> | In what context? |
| 10:49 | <annevk> | API design |
| 10:50 | <jgraham> | API Design isn't a single thing |
| 10:50 | <jgraham> | Do you mean web API or some other type of API |
| 10:51 | <annevk> | Seems Map has entries(), keys(), values() |
| 11:04 | <annevk> | So we should have some kind of consistent design between URLQuery and FormData |
| 11:05 | <annevk> | FormData needs to deal with Blob+filename->File/File. URLQuery needs to deal with being created from a string |
| 11:07 | <annevk> | Maybe http://url.spec.whatwg.org/#interface-urlquery should instead have set / setAll / delete / deletaAll |
| 11:07 | <annevk> | The current workings are a bit inconsistent... |
| 11:09 | <annevk> | (setAll would set the first one and remove the rest) |
| 11:11 | <annevk> | Or maybe the API should be simpler... |
| 11:11 | <annevk> | get() returns a sequence always. append() always appends. delete() removes all always. |
| 11:11 | <annevk> | and set() doesn't exist. |
| 11:12 | <annevk> | and if set() would exist it'd do what setAll does |
| 11:35 | <darobin> | jgraham: I spoke to Lachy on Twitter over the weekend, so presumably he's reachable |
| 11:35 | <Lachy> | yo |
| 11:35 | <darobin> | look! he's even here |
| 11:36 | <darobin> | <jgraham> Anyone able to contact Lachy? It would be nice to know if there's a reason for /selectors-api/tests/submissions/Opera/level1/* |
| 11:37 | <darobin> | annevk: entries() is the only one you absolutely need, but having keys() and values() is often nice |
| 11:37 | <darobin> | but it's just sugar that saves you from having to make the list unique |
| 11:37 | <annevk> | darobin: if the object supports iteration you don't even need entries() |
| 11:38 | <darobin> | annevk: I didn't mean as necessarily a distinct method, just the functionality |
| 11:38 | <SimonSapin> | or just use an array? |
| 11:38 | <annevk> | darobin: you mean keys() and values() would be set(keys()) / set(values()) ? |
| 11:38 | <Lachy> | The level1 files were tests that only required selectors api level 1 to be implemented. The level 2 tests are intended to include the additional APIs like matches and find as well, though they are incomplete. |
| 11:39 | <darobin> | annevk: sorry, I'm not sure I get your question |
| 11:39 | <annevk> | darobin: the values returned by keys() and values() would be unique? |
| 11:39 | <darobin> | ah, that Set |
| 11:39 | <darobin> | yeah — otherwise what's the point? |
| 11:40 | <darobin> | a typical case for keys is e.g. when you need to generate a <select> in which people can pick something |
| 11:40 | <darobin> | and if the key maps to multiple values you just show multiple things |
| 11:40 | <darobin> | that sort of usage |
| 11:58 | <Lachy> | jgraham, if you were actually asking why they exist there as well as in the approved dir, it's just because they were put in submissions first before they reached the approved state. I suppose submissions/level1-* can be removed now. |
| 12:03 | <hsivonen> | Hixie_: www.whatwg.org is down |
| 12:04 | <hsivonen> | Is there a mirror of the spec somewhere? |
| 12:04 | <hsivonen> | Without W3C changes, that is. |
| 12:11 | <Ms2ger> | hsivonen, wfm |
| 12:12 | <hsivonen> | weird charset thing of the day: normal navigation in Firefox doesn't inherit charset from previous doc but open in new window tries to inherit |
| 12:12 | <hsivonen> | Ms2ger: weird. considering http://www.downforeveryoneorjustme.com/www.whatwg.org |
| 12:12 | <Ms2ger> | hsivonen, but https://github.com/whatwg/html-mirror should be up-to-date, I think |
| 12:12 | <hsivonen> | Ms2ger: thank |
| 12:12 | <hsivonen> | s |
| 12:12 | <Ms2ger> | Np |
| 12:14 | <hsivonen> | so the spec says not to inherit from the previous doc |
| 12:14 | <hsivonen> | which means that Gecko inheriting on POST and on Open in New Window is bogus |
| 12:15 | <Ms2ger> | I'd agree with that, I think |
| 12:16 | <Ms2ger> | "Two of the top four New York Times Hardcover bestsellers this week were done with CSS." |
| 12:22 | <hsivonen> | Has anyone tested if other browsers inherit from the previous document when clicking normal links within the same origin? |
| 12:23 | <hsivonen> | I didn't want to be writing test cases for this. |
| 12:23 | <hsivonen> | aaargh. so much bogosity in this general area. |
| 12:24 | <hsivonen> | and more magic being proposed. |
| 12:24 | <Ms2ger> | Would be nice to have those test cases, though ;) |
| 12:34 | <jgraham> | Lachy: OK, thanks, I removed the submissions/ files |
| 12:37 | <hsivonen> | awesome. we're inconsistent between new tab and new window |
| 12:48 | <annevk> | hsivonen: I think basically you have to assume that there's no design and that we're responsible for creating a somewhat sensible design taking into account the constraints of deployed content |
| 12:49 | <annevk> | hsivonen: most of the browser engine is like HTML4 spec-era, not actually understood |
| 12:51 | <hsivonen> | Ms2ger: here you go http://hsivonen.iki.fi/test/moz/charset-inheritance/ |
| 12:52 | <hsivonen> | annevk: Safari suggests Firefox is doing too much DWIM |
| 12:52 | <foolip> | annevk, does http://html5.org/tools/web-apps-tracker die together with whatwg.org? |
| 12:52 | <hsivonen> | annevk: I'll test a few IE versions and will come up with suggestions |
| 12:52 | <annevk> | foolip: yeah, queries svn.whatwg.org |
| 12:53 | <foolip> | annevk, does it still have that diff cache that needs to be thrown out periodically? |
| 12:53 | <annevk> | foolip: yeah :/ |
| 12:53 | <annevk> | foolip: https://github.com/whatwg/web-apps-tracker has the code these days |
| 12:53 | <annevk> | foolip: though I suppose you still have direct access |
| 12:54 | <hsivonen> | http://hsivonen.iki.fi/test/moz/charset-inheritance/iframe.htm says utf-8 in IE10 on Windows 8 for me! |
| 12:54 | <foolip> | foolip, actually I've lost that ssh key |
| 12:54 | <annevk> | hsivonen: booting VMWare |
| 12:55 | <foolip> | annevk, I've thought from time to time that web-apps-tracker could be converted to use a local git repo and be faster+smaller |
| 12:55 | <annevk> | foolip: if you want I can set you up again |
| 12:55 | <foolip> | but apparently I've had other things to do |
| 12:56 | <annevk> | hsivonen: windows-1252 on Windows 7 / IE10 |
| 12:56 | <hsivonen> | annevk: that's surprising, too! |
| 12:57 | <hsivonen> | annevk: Safari and Firefox say windows-1251 |
| 12:58 | <annevk> | hsivonen: Chrome on Windows does windows-1251 too |
| 12:58 | <hsivonen> | Chrome agrees with Safari in all those test cases, it seems |
| 12:58 | <hsivonen> | time to boot some XP VMs! |
| 13:00 | <annevk> | Almost seems like IE defaults to their default encoding. But I hope that did not change to utf-8 in Windows 8? |
| 13:03 | <dsheets> | someone knows whatwg.org is down? |
| 13:03 | <annevk> | yeah |
| 13:06 | dsheets | checks logs and sees 1hr downtime... sorry for noise |
| 13:07 | <gsnedders> | jgraham: But we don't use readthedocs for html5lib-tests, only html5lib-python. |
| 13:08 | <hsivonen> | annevk: They didn't change their default on Windows 8 in the general case. |
| 13:08 | <hsivonen> | annevk: Now I have to check if the baseline assumptions hold. Even IE6 doesn't inherit in the iframe case |
| 13:08 | <gsnedders> | jgraham: And under the assumption people are most likely to read the README on github, Mardown works best |
| 13:09 | <jgraham> | gsnedders: I don't think I disagreed with that |
| 13:09 | <jgraham> | I said rST iff readthedocs |
| 13:09 | <annevk> | hsivonen: wow, if that's not needed that'd be so much better |
| 13:09 | <gsnedders> | That wasn't clear. |
| 13:11 | <hsivonen> | annevk: I added a baseline and the baseline works as expected in IE6. |
| 13:11 | <gsnedders> | jgraham: Also, any idea when you can look at reviews, at those from me? Esp. of html5lib-tests? |
| 13:19 | <jgraham> | gsnedders: Internet access is a bit problematic at the moment… |
| 13:25 | <foolip> | annevk, ok to s/HTML5/HTML/ in web-apps-tracker? |
| 13:25 | <gsnedders> | jgraham: That wonderful British thing o taking a month to activate a phone line that already exists? |
| 13:25 | <jgraham> | gsnedders: If I told you you wouldn't believe me |
| 13:25 | <gsnedders> | I probably would, sadly. |
| 13:26 | <annevk> | foolip: "HTML Standard Tracker" then |
| 13:26 | <foolip> | annevk, ok |
| 13:33 | <foolip> | it might amuse people to know that web-apps-tracker now has 22GB of diffs cached |
| 13:34 | <foolip> | annevk, are you going to TPAC? /me is |
| 13:36 | <annevk> | foolip: yeah |
| 13:37 | <annevk> | foolip: haven't really sorted out travel plans yet |
| 13:37 | <foolip> | cool, see you there then |
| 13:52 | <hsivonen> | Ah. I forgot to test the encoding that document.open()ed docs use for scripts and styles |
| 14:15 | <annevk> | hsivonen: okay so I can make it say utf-8 in Windows 7 |
| 14:15 | <annevk> | hsivonen: fresh start, load http://hsivonen.iki.fi/test/moz/charset-inheritance/iframe.htm directly, get windows-1252 |
| 14:16 | <annevk> | hsivonen: load http://hsivonen.iki.fi/test/moz/charset-inheritance/ click iframe.htm, get utf-8 |
| 14:17 | <annevk> | hsivonen: baseline.htm seems to always give windows-1251 |
| 14:19 | <hsivonen> | annevk: well. that's *weird* |
| 14:20 | <annevk> | hsivonen: one might call it a bug |
| 14:20 | <annevk> | hsivonen: maybe the same bullshit Gecko has |
| 14:20 | <zewt> | Hixie_: i've had to do that, it's tricky if i'm trying to actually mimic when click would normally happen though |
| 14:43 | <annevk> | https://twitter.com/jdfitzgerald/status/376998570001715200 but what is 3? |
| 15:42 | <GPHemsley> | annevk: (1) those who understand binary; (2) those who don't [understand binary]; (3) those who didn't expect this joke to be in base 3 |
| 15:49 | jgraham | grumbles about people that make tests render stuff when there is no need |
| 15:49 | <Ms2ger> | Hmm? |
| 15:50 | <jgraham> | I'm just watching a bunch of tests falsh by that have a big formatted table and stuff, but only actually need the DOM |
| 15:50 | <jgraham> | *flash |
| 15:51 | <annevk> | GPHemsley: you didn't get my joke |
| 15:51 | <GPHemsley> | annevk: Nope. |
| 15:53 | <Ms2ger> | jgraham, oh, not the th.js output? |
| 15:54 | <jgraham> | No |
| 15:56 | <Hixie_> | sorry about down time |
| 15:56 | <Hixie_> | dunno what happened there |
| 15:56 | <Hixie_> | rebooted server though |
| 16:13 | <zcorpan> | annevk: yeah it would be more funny if it said "base 10" |
| 16:18 | <annevk> | It's kinda hard for base 3 to be part of the joke if the joke is actually in base 3, indeed. |
| 16:19 | <SimonSapin> | annevk: http://url.spec.whatwg.org#parse are the different parts of a parsed URL bytes or Unicode? And did I miss it in the spec? |
| 16:19 | <annevk> | SimonSapin: parser appends code points |
| 16:20 | <annevk> | SimonSapin: not entirely sure it's correct though |
| 16:20 | <SimonSapin> | code points that all happen to be in ASCII, right? |
| 16:20 | <annevk> | yeah, except fragment |
| 16:20 | <annevk> | fragment needs more research |
| 16:22 | <Hixie_> | btw, if anyone cares, i agree with those saying that getElementById() has a useful purpose and isn't something that querySelector() should replace. |
| 16:22 | <Hixie_> | querySelector() has its purpose too, but it's a different beast entirely imho. |
| 16:23 | <Jude> | Hello everyone, the link under Storage and files from platform.html5.org is broken |
| 16:23 | <Jude> | http://www.w3.org/html/wg/drafts/html/master/offline.html#offline |
| 16:23 | <Jude> | the above link is broken |
| 16:23 | <Hixie_> | Jude: use http://whatwg.org/html#offline instead |
| 16:23 | <Hixie_> | (not sure why platform.html5.org is pointing to w3.org forks) |
| 16:24 | <Jude> | thanks for the info |
| 16:24 | <dglazkov> | good morning, Whatwg! |
| 16:24 | <gsnedders> | good morning, dglazkov! |
| 16:28 | <annevk> | Hixie_: what's wrong with first of #blah as selection mechanism? |
| 16:29 | <Hixie_> | all the things people have already said in the list |
| 16:29 | <Hixie_> | you have to escape it, it's not as fast, etc |
| 16:29 | <Hixie_> | it's ugly in code |
| 16:29 | <annevk> | So where do you stop? |
| 16:30 | <Hixie_> | where we ra enow seems fine |
| 16:30 | <Hixie_> | are |
| 16:30 | <jgraham> | I don't really have a problem with the existing DOM methods |
| 16:30 | <annevk> | Lots of people do though with getElements* |
| 16:30 | <annevk> | And especially with the objects they reeturn |
| 16:30 | <jgraham> | I have never really understood why CSS Selectors are the One True API |
| 16:30 | <Hixie_> | (i mean, i wish the method name was pithier and easier to type, but that's water under the bridge) |
| 16:30 | <annevk> | getElementById() might be okay |
| 16:31 | <Hixie_> | it's not like we can ever actually remove these apis |
| 16:31 | <annevk> | jgraham: just turned out that way |
| 16:31 | <Hixie_> | so why bother pretending we might |
| 16:31 | <jgraham> | annevk: That's sort of just a jquery limitation though |
| 16:31 | <zcorpan> | consider <div style="outline-style:initial">. should div.style.cssText say 'outline-style: none;' or 'outline-style: initial;' ? (not asking what the spec says, but what should happen in your opinion) |
| 16:31 | <annevk> | Hixie_: I don't think we're pretending that, we're just not putting them in new places |
| 16:31 | <jgraham> | Their design favoured a single API to do all things |
| 16:32 | <annevk> | jgraham: as I said in the thread, I'm not opposed to new better APIs for specific purposes |
| 16:32 | <Hixie_> | zcorpan: style[x].cssTest should say what was specified, imho, so 'initial' |
| 16:32 | <Hixie_> | annevk: oh ok, the thread sounded like you were down on them in general |
| 16:33 | <annevk> | Hixie_: well I am, because of their return values, which is why I don't want to spread them :) |
| 16:34 | <Hixie_> | getElementById()'s return value is fine |
| 16:34 | <gsnedders> | The problem with their return values doesn't go away unless we entirely get rid of them, which won't hpapen. |
| 16:35 | <annevk> | Hixie_: fair, torn on that one |
| 16:35 | <annevk> | gsnedders: all of that is true |
| 16:35 | <annevk> | gsnedders: and none of that was disputed |
| 16:36 | <gsnedders> | It means that return types are no reason to avoid proliferation |
| 16:36 | <zcorpan> | Hixie_: ok. i think that matches the spec (the keyword gets swapped for initial value at specified value time, but element.style doesn't do specified value but just expands shorthands and removes dups) |
| 16:36 | <annevk> | gsnedders: I disagree |
| 16:40 | <zcorpan> | annevk: are the return values still bad if [ArrayClass] succeeds? |
| 16:40 | <annevk> | zcorpan: [ArrayClass] is not on HTMLCollection |
| 16:40 | <Ms2ger> | zcorpan, also, named getter |
| 16:40 | <annevk> | zcorpan: iteration might improve matters a bit I suppose |
| 16:41 | <zcorpan> | annevk: is there a reason it can't be on HTMLCollection? |
| 16:41 | <annevk> | zcorpan: names getters |
| 16:41 | <annevk> | named* |
| 16:42 | <zcorpan> | ok |
| 16:42 | <annevk> | iteration can be though, I think |
| 16:47 | <zcorpan> | today i implemented http://dev.w3.org/csswg/cssom/#serialize-a-css-declaration-block in javascript to find my mistakes in my untested spec algorithm, but was surprised to find nothing but a typo. i was expecting infinite loops and bogus checks |
| 16:50 | <zewt> | nothing is scarier than complex code that works the first time |
| 16:58 | <zcorpan> | works the first time is what i meant. :-) but now i found a bug, so maybe there are bogus checks |
| 17:08 | <annevk> | TabAtkins: I'm not happy with the current design |
| 17:08 | <annevk> | TabAtkins: I'm happy to work out something better, but the current thing just feels inconsistent |
| 17:10 | <annevk> | TabAtkins: see also http://krijnhoetmer.nl/irc-logs/whatwg/20130909#l-316 |
| 18:48 | <zcorpan> | heh, i've been debugging what was wrong in my code, it turned out i had forgotten to type ".length" in a for loop so it was always skipped |
| 19:25 | <zcorpan> | has anyone apart from annevk implemented the URL spec? |
| 19:26 | <Ms2ger> | Not afaik |
| 19:27 | <annevk> | zcorpan: I've had comments on tokenizer bits, and Node.js copied bits, but not straight up |
| 19:28 | <zcorpan> | ok. was wondering if there was an obvious candidate for reviewing https://critic.hoppipolla.co.uk/r/300 |
| 19:30 | <zcorpan> | annevk: have you run the tests in multiple browsers and pondered about cases where all or most fail a certain test? |
| 19:30 | <annevk> | zcorpan: I've certainly pondered a fair bit over URLs |
| 19:30 | <annevk> | zcorpan: but I suspect others have different opinions on how I handled various cases |
| 19:32 | <zcorpan> | yeah, i know you have pondered over URLs, but that wasn't exactly what i asked :-) |
| 19:33 | <annevk> | zcorpan: sorry, I pondered over the results too, I used the tests to fix the specification and such |
| 19:34 | <zcorpan> | ok, cool |
| 19:34 | <annevk> | could certainly use scrutiny though I suppose |
| 19:36 | <Ms2ger> | zcorpan, so I'm happy to look at those tests some, but I have no opinion on what the results *should* be :) |
| 19:37 | <zcorpan> | Ms2ger: go ahead :-) |
| 19:37 | <Ms2ger> | But probably only when I get back from vacation |
| 19:41 | <zcorpan> | annevk: "Parsing: <http://f:b/c>; against <http://example.org/foo/bar>; assert_equals: scheme expected ":" but got "http:"" is that right? |
| 19:42 | <annevk> | yeah, f:b would fail to parse |
| 19:51 | <zcorpan> | annevk: does it fail to parse in http://tools.ietf.org/html/rfc3490#section-4.1 ? |
| 19:51 | <annevk> | zcorpan: no it fails because :b is not a numeric port |
| 19:52 | <annevk> | zcorpan: url.spec.whatwg.org/#port-schem |
| 19:52 | <annevk> | zcorpan: http://url.spec.whatwg.org/#port-state sorry |
| 19:52 | <zcorpan> | ah yeah i saw it now |
| 19:55 | <zcorpan> | seems to fail to resolve in gecko |
| 19:56 | <zcorpan> | annevk: but the error message for expected-fail-to-resolve could be more obvious. maybe also the source data file could have a special thing to indicate expected parse failure? |
| 19:57 | <annevk> | ":" seems clear |
| 19:57 | <annevk> | you can't get that any other way |
| 19:57 | <annevk> | well not clear, but yeah, we could build a message around that |
| 19:57 | <annevk> | I meant it's not needed in the source |
| 20:00 | <zcorpan> | yeah it's not needed, but it would be less cryptic :-) but a comment in the source might do the trick |
| 20:29 | <zcorpan> | hmm, though a dedicated field could be shown in the message. like http://f:b/ error:port-state |
| 21:43 | <Hixie_> | we need a RESOLVED LOOKSLIKESPAM in bugzilla |
| 22:39 | <jwalden> | is data:text/html;charset=UTF-8,<script>onerror=function(){alert('hi")};</script><script>var%20function;</script> supposed to alert, or no? I think yes, if I'm reading the spec right, but Gecko at least doesn't right now |
| 22:39 | <Hixie_> | why would it not? |
| 22:40 | <Hixie_> | it's a syntax error, no? |
| 22:40 | <Hixie_> | are you trying to establish if it's a JS error, or if it's reported at the HTML level? :-) |
| 22:40 | <Hixie_> | note that 'hi" isn't valid |
| 22:40 | <jwalden> | it wasn't/isn't clear to me that the onerror hook should necessarily be triggered for syntax errors in scripts |
| 22:40 | <jwalden> | er, ugh |
| 22:40 | <Hixie_> | so i'm assuming your real test doesn't have that |
| 22:41 | <jwalden> | no, that was my real test :-) |
| 22:41 | <Hixie_> | ah |
| 22:41 | <jwalden> | explains things :-) |
| 22:41 | <Hixie_> | well then |
| 22:41 | <Hixie_> | i don't expect an alert :-) |
| 22:41 | <Hixie_> | several console messages though |
| 22:41 | <jwalden> | erm |
| 22:41 | <jwalden> | no, I get alert("hi") with that typo-fix |
| 22:42 | <jwalden> | data:text/html;charset=UTF-8,<script>onerror=function(){alert("hi")};</script><script>var%20delete;</script> for people following logs |
| 22:42 | <Hixie_> | yeah that should alert |
| 22:42 | <jwalden> | okay, this might be handy-ish then |
| 22:43 | <jwalden> | well |
| 22:43 | <jwalden> | handy *if* Gecko exposed the error object that was thrown |
| 22:43 | <jwalden> | which it doesn't |
| 22:43 | <jwalden> | or at least I remember strong complaints about it not doing so |
| 22:43 | <Hixie_> | the spec just changed to expose it |
| 22:44 | <Hixie_> | but that's new |
| 22:44 | <jwalden> | yeah |
| 22:45 | <jwalden> | (this use wouldn't care about CORS concerns, to be completely clear, so .error should always be there) |
| 22:55 | <zcorpan> | jwalden: why would it not care about CORS concerns? (what do you mean by that?) |
| 22:56 | zcorpan | -> sleep, will read logs tomorrow |
| 23:08 | <jwalden> | zcorpan: onerror fires with non-interesting error data ("muted errors") if "the script came from a resource that was fetched in the steps above, and the resource was CORS-cross-origin" per http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html#execute-the-script-block 2.6. |
| 23:43 | <Hixie_> | hmm. so the high density stuff in canvas failed because people create canvases today expecting a 1:1 mapping. |
| 23:43 | <Hixie_> | i wonder if we can still provide a 1:n mapping if we just have a setting in the getContext call for it |
| 23:44 | <Hixie_> | e.g. a 'density' option, valid values being '1:1' and 'native' |
| 23:44 | <Hixie_> | and if it's native we can also just blow away the canvas when you zoom and fire an event letting you know you'd better repaint now |