| 02:03 | <rniwa> | anyone here? |
| 02:10 | <xfq> | yep |
| 02:12 | <MikeSmith> | rniwa: yep2 |
| 02:12 | <MikeSmith> | rniwa: one more yep and you can ship |
| 02:13 | <rniwa> | MikeSmith: so DataTransfer is quite a bit of mess... |
| 02:14 | <MikeSmith> | agreed :) |
| 02:14 | <MikeSmith> | seems like all of drag and drop is a mess |
| 02:15 | <MikeSmith> | waiting to hear you say you gonna fix it all :) |
| 02:17 | <rniwa> | MikeSmith: e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1199729 means that Firefox would let you keep accessing dataTransfer.items, files, etc... |
| 02:17 | <rniwa> | while other browsers won't. |
| 02:18 | MikeSmith | looks |
| 02:18 | <rniwa> | so dataTransfer.files.length change in Blink/WebKit but not in Gecko |
| 02:18 | <rniwa> | my goodness, someone is using nic name of "so". |
| 02:18 | <rniwa> | this is very confusing. |
| 02:18 | <MikeSmith> | heh |
| 02:18 | <MikeSmith> | so what does the spec say? |
| 02:18 | <MikeSmith> | or it doesn’t say? |
| 02:18 | MikeSmith | is still reading the bug |
| 02:19 | <MikeSmith> | so the gecko behavior or just non-conforming, right? |
| 02:19 | <MikeSmith> | as far as what the bug says |
| 02:19 | <rniwa> | MikeSmith: as far as I read the spec, Blink/WebKit behavior implements this correctly |
| 02:20 | <MikeSmith> | the problem described in that bug seems different than what you just described btw |
| 02:21 | <MikeSmith> | oh, “means that Firefox would let you keep accessing dataTransfer.items, files, etc” |
| 02:22 | <rniwa> | MikeSmith: yeah |
| 02:22 | <rniwa> | it took me a while to decipher what the spec was trying to say |
| 02:22 | <MikeSmith> | OK yeah the word “Protected” threw me off |
| 02:23 | <MikeSmith> | I didn’t realize that was a specific dfn’ed term in the spec |
| 02:23 | <rniwa> | MikeSmith: see step 13 in https://html.spec.whatwg.org/multipage/dnd.html#fire-a-dnd-event |
| 02:23 | <MikeSmith> | “the data itself is unavailable” |
| 02:24 | MikeSmith | looks at https://html.spec.whatwg.org/multipage/dnd.html#fire-a-dnd-event |
| 02:24 | <MikeSmith> | rniwa: that seems clear enough to me |
| 02:24 | <MikeSmith> | but then I’m not implementing it.. |
| 02:25 | <MikeSmith> | hmm though the first step is “If no specific related target was provided, set related target to null.” |
| 02:26 | <rniwa> | MikeSmith: it's step 3 |
| 02:26 | <MikeSmith> | yeah I see that now |
| 02:26 | <rniwa> | it's really annoying that all these algorithm based spec text gets out of date easily |
| 02:26 | <MikeSmith> | yeah |
| 02:26 | <MikeSmith> | well I will PR that one right now |
| 02:26 | <MikeSmith> | before I forget |
| 02:26 | <MikeSmith> | (unless you have already) |
| 02:35 | <MikeSmith> | https://github.com/whatwg/html/pull/2907 |
| 02:45 | <rniwa> | MikeSmith: the change looks great but I don't have the commit access to the repo |
| 03:02 | <MikeSmith> | yeah I' |
| 03:02 | <MikeSmith> | oofs |
| 03:02 | <MikeSmith> | yeah I’ll just wait for Domenic or annevk to review it |
| 03:03 | <MikeSmith> | a meta issue here is that ideally we should be writing those algorithms in a way where references like that get automatically updated if a step moves |
| 03:04 | <MikeSmith> | maybe bikeshed has some magic for that |
| 03:04 | <MikeSmith> | but it’s obviously pretty brittle to have references to step numbers hardcoded like that |
| 03:06 | <MikeSmith> | and it’s imaginable that in some cases it could cause real implementation bugs, if the changed step number being referenced isn’t obviously the wrong step as it was in this case |
| 13:36 | <TimothyGu> | annevk: ok, thanks. it's summer break for me so lots of time on my hand |
| 19:54 | <zcorpan-OOO-14Au> | Hello |