00:56 | <annevk> | base: http://host/a, input: //, browsers: chaos |
01:01 | <annevk> | (URL standard: failure, fwiw) |
01:02 | <annevk> | (Anyone want to explain why it's failure?) |
04:59 | <zewt> | chrome sure is trying to convince me to never use html5 video with this "gone fullscreen" thing that forces you to acknowledge it crap |
05:00 | <zewt> | contrived security risks that don't actually exist driving high-visibility UI == failure |
05:28 | <wyne> | anyone here? |
05:29 | <wyne> | hello? |
09:32 | <mitsuhiko> | does anyone know where "application/x-www-form-urlencoded" is currently specified? |
09:32 | <mitsuhiko> | primarily in regards to charsets |
09:33 | <mitsuhiko> | fonud it: http://www.w3.org/TR/html5/iana.html#application/x-www-form-urlencoded |
09:35 | <Ms2ger> | http://whatwg.org/html/#application/x-www-form-urlencoded is the authoritative definition |
11:31 | <galant> | I don;'t understand CSS specification says inline elements can't have vertical margins but I can set img element a margin-top why? |
11:32 | <SimonSapin> | galant: Do you have a link? Doesn’t it say non-replaced inline elements? Images are "replaced" |
11:33 | <galant> | yeah |
11:33 | <galant> | ah yes SimonSapin yes sry and thanks |
12:10 | <galant> | why I can't see button from the form in iframe? |
12:13 | <galant> | I cant see iframe it should have form |
15:39 | <smaug____> | odd to see someone being against properly defined API (reading public-audio) |
15:46 | <dglazkov> | good morning, Whatwg! |
16:48 | <TabAtkins> | heycam|away: Yo, you got the argument ordering wrong for the MapClass forEach callback. It's supposed to be (value, key, thisarg). |
16:52 | <TabAtkins> | heycam|away: Also, I'm not certain that you understood the way that the second argument of forEach and the third argument of the forEach callback interact: they don't. Calling the callback function's third argument "thisArg" is confusing, because it has nothing to do with "this" relative to the callback function - it's the collection (and thus, yes, must be |
16:52 | <TabAtkins> | consistent with the return type of set()). |
16:57 | <SimonSapin> | TabAtkins: do we still have a lot to do for a Syntax WD? |
16:57 | <TabAtkins> | I'll have to check, but I don't think so. |
18:54 | <annevk> | Hixie_: thanks for the hook |
18:55 | <annevk> | Hixie_: guess I better use it |
19:22 | <ondras> | so, who is the right person to ask re. whatwg Promise object? |
19:24 | <zewt> | gar i can't remember how to cancel text selection on mousedown/mousemove/drag/wherever without preventing a click |
19:33 | <zewt> | why do i have to say <div draggable=true> in chrome instead of <div draggable> :| |
19:35 | <annevk> | ondras: you can try me |
19:36 | <ondras> | annevk: cool, thanks |
19:36 | <ondras> | annevk: my greatest interest are similarities and differences w.r.t. promises/a+ |
19:36 | <ondras> | annevk: are you familiar with that spec? |
19:37 | <annevk> | ondras: Domenic_ ensures we stay in sync with that |
19:38 | <ondras> | hmh |
19:38 | <ondras> | well I do not think those two specs are totally compatible |
19:38 | <ondras> | whatwg promises do not look to be modifyable from outside, using public methods |
19:39 | <ondras> | they do not expose fulfill/reject, right? |
19:39 | <Domenic_> | ondras: neither do Promises/A+ promises. Promises/A+ only specifies `then`. |
19:40 | <ondras> | wow |
19:40 | <ondras> | is it possible that the spec has changed recently in a decent way? |
19:41 | <Domenic_> | ondras: so far the only differences are in somewhat minor things, e.g. DOM Promises do not ignore non-function/non-undefineds---if they see one they make the returned promise a rejection with a TypeError. And DOM promises call their onFulfilled and onRejected handlers as if they were methods of the promise (i.e. with thisArg set to the promise), instead of |
19:41 | <Domenic_> | calling them as functions. |
19:43 | <ondras> | Domenic_: okay, I am somewhat confused now, as I thought that my a+ impl was complete including public fulfill/reject methods |
19:43 | <ondras> | Domenic_: anyway; DOM promises expose these only to the anonymous function passed to the constructor, right? |
19:51 | <ondras> | afk, have to go |
19:53 | <Domenic_> | ondras: From http://promisesaplus.com: "As with Promises/A, this proposal does not deal with how to create, fulfill, or reject promises." Each implementation has their own manner of doing so. |
20:28 | <TabAtkins> | zewt: Bug. |
20:31 | <annevk> | Paul Kalkbrenner's version of Wait For Me <3 |
20:34 | <annevk> | Hixie_: https://github.com/whatwg/xhr/commit/f56d42d57bae8a131db7bdb9e32aa7f21a8715b2 |
20:43 | <annevk> | dglazkov: your summery of the situation sounds correct |
20:44 | <annevk> | dglazkov: with adopting |
20:44 | <annevk> | dglazkov: changing identify is not possible |
20:44 | <annevk> | dglazkov: people do things like appendChild(x) (which does adopt) and then x.textContent = ... |
20:52 | <TabAtkins> | Can anyone remember why <img crossorigin> was necessary, rather than just always respecting CORS headers sent back with the image and untainting appropriately? |
20:53 | <Hixie_> | because sending Origin headers breaks sites |
20:54 | <annevk> | https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMNytJB_YvHJMS8nM6LiT8MF4UsDFqDA6KFAH4pP_n1%2Bd1nGsg%40mail.gmail.com Yay Mark. |
20:59 | <TabAtkins> | Hixie_: Weird, but okay. |
21:02 | <annevk> | Domenic_: http://en.wikipedia.org/wiki/AFC_Ajax ;-) |
21:02 | <annevk> | Domenic_: (icon has been there for a while though) |
21:11 | <annevk> | The joy of debating Node.cloneNode()... |
21:13 | <jgraham> | Is never likely to be a bestseller |
21:38 | <annevk> | I'm adding Notification.get() per email btw |
21:46 | <dglazkov> | annevk: I am leaning toward option 1 -> less magic. |
21:47 | <annevk> | dglazkov: That's not what WebKit/Chromium or Gecko is doing at the moment I believe. |
21:47 | <annevk> | dglazkov: And according to bz is not web-compatible. |
21:47 | <dglazkov> | dglazkov: oh? I think 1 has no compat issues. It has "giant leakage" issues. |
21:47 | <annevk> | dglazkov: I'd be happy with that personally though, as that's what the spec says o_O |
21:47 | <galant> | is it ok to make <img src=aa.jpg" /> and then assign width and height form css file? |
21:48 | <galant> | or I must assign width height in html as attributes |
21:55 | <manshu18> | hello |
21:55 | <manshu18> | any 1 there |
21:55 | <manshu18> | i wnat to fix Line 7, Column 42: Bad value robot for attribute name on element meta: Keyword robot is not registered. |
21:56 | <manshu18> | how do i fix |
22:01 | <annevk> | malcolmva: you should probably write robots |
22:02 | <annevk> | sorry, wrong person :/ |
22:02 | <annevk> | seems manshu18 left |
22:02 | <annevk> | galant: fine |
22:03 | <dglazkov> | "bad value robot" sounds like a great band name. |
22:06 | <annevk> | dglazkov: please add to http://wiki.whatwg.org/wiki/Band_names :) |
22:07 | <dglazkov> | there's a place for everything on Whatwg! |
23:56 | <heycam> | TabAtkins, thanks, I tweaked the forEach stuff |