| 12:23 | <Ms2ger> | wtf: https://github.com/ylafon/webidl |
| 12:31 | <nox> | Ms2ger: What's the problem? |
| 12:31 | <Ms2ger> | Some random guy forking the spec with no communication whatsoever |
| 12:33 | <nox> | Ms2ger: I didn't realise he is part of W3C; |
| 12:33 | <nox> | now I see the problem. |
| 12:34 | <smaug____> | remind me, which spec defines how .style.* is mapped to style attribute |
| 12:34 | <botie> | will do |
| 12:38 | <smaug____> | (could someone finally kill w3schools) |
| 13:00 | <ondras> | so I have this strange behavior (so far in Firefox only), when I append a large absolutely positioned element that is translated (css transform) far to the right (out of the screen) and the browser scrolls the documentElement to try to keep this big offscreen thing in the viewport |
| 13:01 | <ondras> | is this specced/documented/reported/explained somewhere? |
| 13:56 | <howdoi> | Is w3c open for proposals like TC39? |
| 13:56 | <howdoi> | if yes, what's the process like? |
| 13:56 | <howdoi> | how many stages? |
| 13:59 | <howdoi> | have you tired adding an event listener is a promise? |
| 13:59 | <howdoi> | new Promise((res, rej) => element.addEventListner('click', () => if(...){resolve()} reject())) // something like |
| 13:59 | <howdoi> | Domenic: is that a bad idea? |
| 14:23 | <Ms2ger> | The W3C process is based on stubbornness to the point of exhausting anyone with actual work to do |
| 14:24 | <Ms2ger> | As for the WHATWG, https://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F |
| 14:26 | <jgraham> | In general event listeners and promises have an impedance mismatch because promises are resolve-once and event listeners are continuous streams of events |
| 14:28 | <howdoi> | jgraham: so it's a no no, it won't work right? |
| 14:28 | <howdoi> | Ms2ger: Forget about the particular solution you have in mind! Solution time is later! :D |
| 14:28 | <howdoi> | So much of writing to do :( |
| 14:28 | <jgraham> | Well you can make something that works if you want a promise to resolve the next time a particular event fires |
| 14:29 | <jgraham> | But it generally doesn't seem useful enough to add to the platform; for events that only fire once new APIs are sneakily using promises directly (eg. fetch vs xhr) |
| 14:56 | <tobie> | Ms2ger: afaik, there's been communication about it. ylafon is working on a bringing version 1 to Rec. That version would only contain bindings actually implemented by vendors. |
| 14:57 | <tobie> | Ms2ger: note I'm offering info about it. Not my opinion on the topic. :) |
| 15:07 | <howdoi> | jgraham: try, luck that fetch is a function, we done need to do a new Fetch() heh heh |
| 15:07 | <howdoi> | jgraham: does fetch extend promise internally? |
| 15:07 | <howdoi> | or just returns a new Promise() ? |
| 15:21 | <Ms2ger> | > W3C invites implementations of Mixed Content |
| 15:21 | <Ms2ger> | Noooooooooo |
| 15:25 | <AutomatedTester> | I thought we were only doing HTTPS these days |
| 15:26 | <AutomatedTester> | HTTPS is the new HTTP |
| 15:35 | <annevk> | Ms2ger: is that a serious IDL fork? Seems weird… |
| 15:43 | <tobie> | annevk: see my comments above |
| 15:58 | <annevk> | Ah |
| 15:58 | <annevk> | Missed that somehow |
| 17:14 | <duper> | Is it possible to represent IPv6 addresses in decimal or octal, similar to how IPv4 addresses can be? |
| 17:20 | <TabAtkins> | smaug____: As far as I can tell... it's not defined anywhere. |
| 17:21 | <TabAtkins> | Style Attributes just defines that the contents of a style attribute apply to the document as if they were in a stylesheet. |
| 17:21 | <smaug____> | TabAtkins: ok. The question I have is that when should setting .style.foo = "some new value" cause a dom attribute set |
| 17:21 | <TabAtkins> | And OM doesn't seem to ahve any specific text about this. |
| 17:23 | <smaug____> | IMO element.style.width = "10px"; element.style.width = "10px"; should cause two mutation records, to be consistent with element.setAttribute("style", "width: 10px;"); element.setAttribute("style", "width: 10px;"); |
| 17:24 | <smaug____> | but not all the browsers create the latter record for the .style case |
| 17:25 | <TabAtkins> | Yeah, I think that's utterly undefined. A good bug report for CSSOM. Make zcorpan fix it. ^_^ |
| 17:25 | <TabAtkins> | (I wouldn't be surprised if it does dirty-checking and only writes when there's a change.) |
| 17:26 | <Ms2ger> | > Mutating the declarations must set the style content attribute on the context object to the serialization of the declarations. If the style content attribute is set, changed or removed, the declarations must be updated as appropriate. |
| 17:27 | <Ms2ger> | So what is "Mutating the declarations"? |
| 17:27 | <Ms2ger> | smaug____, file a bug on cssom? |
| 17:28 | <smaug____> | reading... |
| 17:28 | <smaug____> | perhaps this is speced? |
| 17:28 | <smaug____> | hmm, " Mutating the declarations" is indeed too vague |