03:28 | <annevk> | Domenic: executing script while parsing is okay, re custom elements |
03:28 | <annevk> | Domenic: the problem is executing script while cloning |
14:44 | <JakeA> | In specs, if I invoke https://html.spec.whatwg.org/multipage/browsers.html#navigate, how can I capture the error thrown at https://html.spec.whatwg.org/multipage/browsers.html#exceptions-enabled and turn it into a promise rejection? |
15:40 | <Sarunas> | Hello ^^ |
15:42 | <Sarunas> | Can anyone suggest me somewhere to learn DOM ? In javascript, i am thinking about reading https://dom.spec.whatwg.org/ not sure if it will be enough though. |
15:43 | <JakeA> | Sarunas: https://developers.google.com/web/fundamentals/ and https://developer.mozilla.org/en-US/ are more developer friendly |
15:45 | <Sarunas> | JakeA: Thanks! I am reading a book about JS, and as it covered chapter about DOM, i realised it didn't quite got everything, and it is very important part of developing with JS (I know that DOM isn't a JS standard haha ), but it's still very important. So i decided to reach out for help . |
15:51 | <caitp> | the various DOM specs, and the WebIDL spec, are very good to read, but probably not very helpful for beginners |
15:51 | <caitp> | still if you can read IDL, you can pretty much figure out how it's supposed to work |
15:52 | <caitp> | IDL is very self-documenting, except for all the crazy bits =) |
15:53 | <Sarunas> | caitp: IDL specs ?are you talking about w3.org ? I am quite new to these things, so I am not sure haha |
15:54 | <caitp> | IDL is a language for defining interfaces, they're informative about what the API is, and partially explains behaviour |
15:55 | <caitp> | "interfaces" being, for example, a DOM node, or XMLHttpRequest, or similar |
15:57 | <caitp> | anyways, they're certainly helpful for the basics of "what does this method take, what is the return value, what operations can I perform on this type" etc |
15:57 | <Sarunas> | Oh, now i think I get it! I will look into it ! Thank you! |
20:11 | <encryptd_fractal> | purpl |
20:39 | <wanderview> | JakeA: I'm really enjoying the trained to thrill photos today |
21:53 | <JakeA> | wanderview: huh, it's appearing broken for me in Chrome, will check it out |
22:05 | <Domenic> | oh snap, does trained to thrill only work in firefox now!? the tables have turned!!! |
23:34 | <wanderview> | Domenic: JakeA: I had to patch firefox nightly to support skipWaiting()... but it seemed to work after that... I just liked the graffiti pictures that were showing :-) |
23:34 | <wanderview> | (and enabled serviceWorkers again as we have it temp disabled in nightly) |
23:41 | <JakeA> | wanderview: i haven't checked it out yet, what's the debugging story? |
23:41 | <wanderview> | JakeA: for trained to thrill? the only error I saw was we didn't support skipWaiting() |
23:41 | <wanderview> | JakeA: it won't load at all for you? |
23:42 | <JakeA> | wanderview: oh, haven't looked yet, just asking what the state of devtools + SW is in Firefox |
23:42 | <JakeA> | As in, are console messages piped through, can I set breakpoints? Etc etc |
23:42 | <wanderview> | JakeA: oh.... still less than we would like unfortunately :-( |
23:42 | <wanderview> | JakeA: we have console messages going to the browser console (shared with all windows) |
23:43 | <wanderview> | JakeA: and we have an about:serviceworkers page |
23:43 | <wanderview> | JakeA: but our js debugger for workers (not just SW) is still in development... its quite a task to move it from main thread only to support workers I guess |
23:45 | <wanderview> | JakeA: this is the debugger issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1003097 |
23:45 | <JakeA> | wanderview: well, console support goes a long way. Dev tools are perpetually less than we would like |
23:45 | <JakeA> | Until they can write everything for us |
23:45 | <wanderview> | JakeA: we also have work in progress to support Cache API in our storage explorer thing |
23:45 | <JakeA> | Ohh cool |
23:45 | <wanderview> | not sure how close that is |
23:46 | <wanderview> | JakeA: are you blogging about this stuff again? |
23:48 | <JakeA> | wanderview: I don't have anything planned yet, got a few other things in my "queue". Although, if we were to do a joint post with Mozilla, who'd be best to speak to? |
23:48 | <wanderview> | I think someone on our team was going to write a blog about our dev tools |
23:49 | <wanderview> | JakeA: uh... let me ask at our wednesday meeting... I can't remember who took that |
23:50 | <JakeA> | No rush, Google I/O is in between me & doing anything of value |
23:51 | <wanderview> | I'll let you know what I hear... have fun with the conf |
23:51 | wanderview | goes to watch Arrow... |