| 13:58 | <annevk> | mkwst: did WebAppSec discuss nonce hiding? |
| 14:01 | <mkwst> | annevk: Artur put it on his wishlist for other vendors. |
| 14:02 | <mkwst> | Folks generally nodded along. *shrug* We pointed folks at the PR and asked for feedback. |
| 14:02 | <KevinMarks> | "we don't want to call it an ontology, so we can call it a metadata vocabulary" |
| 14:02 | <annevk> | mkwst: I think that's good enough for me |
| 14:03 | <mkwst> | It's certainly good enough for _me_! |
| 14:03 | <KevinMarks> | Oops, wrong channel |
| 14:30 | <Ms2ger> | Sounds like KevinMarks_ needs an ontology for IRC channels |
| 14:31 | <jgraham> | I think you mean "metadata vocabulary" |
| 14:31 | <KevinMarks_> | I need less recursive bikeshedding |
| 14:36 | jgraham | hands KevinMarks_ a trampoline |
| 15:29 | <Iarfen> | hi! |
| 15:30 | <Iarfen> | I've send an email to the subscription email |
| 15:30 | <Iarfen> | and inside there I didn't get any instruction to reply |
| 15:30 | <Iarfen> | I've replied normally |
| 15:30 | <Iarfen> | I'm then subscribed to the mailing list? |
| 15:32 | <annevk> | Iarfen: likely, though the mailing list isn't used much |
| 15:32 | <Iarfen> | annevk: what's more used? |
| 15:32 | <annevk> | Iarfen: most of our activity is on GitHub: https://github.com/whatwg |
| 15:32 | <Iarfen> | ok |
| 15:33 | <annevk> | Iarfen: https://whatwg.org/faq has some useful information too, if you haven't encountered that already |
| 15:40 | <Iarfen> | well, I'm seeing the repositories now |
| 15:43 | <Iarfen> | The pages of the standards, like this one: https://url.spec.whatwg.org/ are the only pages of that standard? The standard isn't very large then? |
| 15:46 | <wanderview> | JakeA: why is constructable EventTarget so exciting for web devs? just curious |
| 15:46 | <annevk> | Iarfen: for URL that's correct |
| 15:47 | <annevk> | Iarfen: Encoding has additional resources linked from the main document; HTML exists as a multipage version due to the size of the singlepage bringing many a browser to a halt |
| 15:48 | <annevk> | wanderview: means you don't have to implement your own event system |
| 15:48 | <JakeA> | wanderview: for me, it's something I'm tired of importing libraries for. And anything I import will be subtly different to what the web already does. |
| 15:49 | <wanderview> | annevk: JakeA: you don't get isTrusted==true, though, right? |
| 15:50 | <JakeA> | wanderview: no, but that makes sense right? Trusted should only be events from the browser |
| 15:51 | <annevk> | wanderview: it's mostly so you can create your own object that uses events as its notification system |
| 15:51 | <wanderview> | JakeA: yea... I guess I just didn't realize how much code was necessary to polyfill an event system |
| 15:52 | <JakeA> | wanderview: more than 0, and they all differ slightly, and they won't get observables once EventTarget gets observables etc etc |
| 15:53 | <JakeA> | It's more of a "but it's right there, why can't I use it??" problem that's now being fixed |
| 15:53 | <wanderview> | cool |
| 15:55 | <wanderview> | I guess this is our constructable EventTarget bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1379688 |
| 16:05 | <Iarfen> | well, the code inside whatwg/html repository is only for examples right? |
| 16:07 | <annevk> | Iarfen: the file named "source" is the standard |
| 16:08 | <Iarfen> | it contains all possible options? |
| 16:08 | <Iarfen> | no, now I understand |
| 16:08 | <Iarfen> | it's the webpage that displays the standard |
| 16:09 | <annevk> | Iarfen: ah yeah, there's a build step, the final output is not in the repositories |
| 16:10 | <annevk> | Iarfen: just the input and the build instructions (for whatwg/html the build step is a bit more convoluted; it's a special case) |
| 16:14 | <Iarfen> | annevk: in order to add a proposition/idea, how I do it? |
| 16:14 | <Iarfen> | my idea is to group meta information within <meta>, it looks better :D |
| 16:14 | <Iarfen> | and also, it gives the opportunity to add easily a lot of meta-information new |
| 16:15 | <Iarfen> | that actually is not very comfortable to do, because it isn't possible to nest <meta> information, and then it becomes a little laberynthine |
| 17:08 | <annevk> | Iarfen: the FAQ has an entry on new features |
| 17:08 | <annevk> | Iarfen: the bar is quite high for those though; just aesthetics usually doesn't cut it |
| 17:08 | <Iarfen> | ok |
| 17:13 | <annevk> | tobie: a clarifying comment on https://github.com/heycam/webidl/pull/423#issuecomment-326583682 would be helpful before I start reviewing |
| 17:13 | <annevk> | tobie: that is, I'd like to know whether that's addressed |
| 17:34 | <smaug____> | hmm, append() works surprisingly |
| 17:34 | <smaug____> | if one appends ancestor |
| 17:34 | <smaug____> | or ancestor _and_ some other node/text |
| 17:35 | <smaug____> | since if the latter, ancestor is first removed from its parent |
| 17:35 | <smaug____> | and added to DocumentFragment |
| 17:35 | <smaug____> | so no hierarcy request errors |
| 17:49 | <annevk> | smaug____: yeah, that’s not great |
| 17:49 | <annevk> | smaug____: range APIs have similar issues though |
| 21:31 | <Domenic> | wanderview: JakeA: one thing that's quite hard to do when constructing your own EventTarget is "report an exception" behavior so that separate listeners don't interfere with each other |
| 21:31 | <Domenic> | The best you can do is try { callHandler(); }catch (e) { setTimeout(() => { throw e; }, 0); } which sometimes messes up the stack and definitely messes up break on exception. |
| 21:33 | <Domenic> | https://github.com/whatwg/html/pull/1196 tried to add this |
| 21:33 | <Domenic> | Maybe I can push the DOM team to do it |
| 23:08 | <Iarfen> | OS: 64 bit Windows 10 Professional (Version 10.0 Build 15063), CPU: 2 x AMD Phenom(tm) II X2 555 Processor @ 3214 MHz 512 KB Cache, MEM: 4093 MB, 39% (1560 MB) free, DISKS: total 467 GB - 79,1 GB free, GFX: AMD Radeon HD 5670 512 MB, SCREEN: Monitor PnP genérico, 1360 x 768 @ 32 bit, 60 Hz, AUDIO: Realtek High Definition Audio, UPTIME: 0 d, 21 h, 47 m |
| 23:08 | <Iarfen> | CPU: 2 x AMD Phenom(tm) II X2 555 Processor @ 3214 MHZ (AMD64 Family 16 Model 4 Stepping 3), 512 KB Cache |