/irc-logs / w3c / #webapps / 2016-01-26 / end
Options:
Previous day, Next day
- # Session Start: Tue Jan 26 00:00:00 2016
- # Session Ident: #webapps
- # [00:00] <rniwa> esprehn: so there is no way to put things into head with custom elements
- # [00:00] <rniwa> esprehn: and we need to make the parser behavior different in order to allow this
- # [00:00] <rniwa> annevk: we probably don't want to allow that because that would require everyone running scripts all the time
- # [00:01] <rniwa> Domenic_: more generic syntax for inheriting from an element will be <super-a extends="a"> instead of <a is="super-a">
- # [00:01] <rniwa> but this syntax has all the downsides of having to look up definitions
- # [00:02] <rniwa> hober: is= seems like a good feature to think about when we think about what features are missing
- # [00:02] <justin> q+
- # [00:02] <rniwa> hober: but since removing a feature is impossible, but maybe we should not add this feature now because we may regret later
- # [00:02] * Zakim sees justin on the speaker queue
- # [00:02] <chaals> q+
- # [00:02] * Zakim sees justin, chaals on the speaker queue
- # [00:02] <chaals> ack ju
- # [00:02] * Zakim sees chaals on the speaker queue
- # [00:03] <rniwa> justin: from API consumer point of view, we used link element (subclassed) and it's a real shame to lose that functionality
- # [00:03] <rniwa> justin: what's the objection from implementor's side?
- # [00:03] <rniwa> Travis: it's that it's a bad declarative syntax
- # [00:03] <rniwa> chaals: it's ugly; this is what I hear.
- # [00:04] <LJWatson> q+ to ask whether role= could be used/extended to trigger native behaviour?
- # [00:04] * Zakim sees chaals, LJWatson on the speaker queue
- # [00:04] <rniwa> chaals: a question I pose counter to hober's point is that perhaps is= will solve many problems for once instead of having to go figure out three different problems separately and come up with a separate solution
- # [00:05] <rniwa> chaals: like some things in HTML, we may regret about this feature but it might be cheaper to be sorry later than not having anything that works for years
- # [00:05] <rniwa> esprehn: we also find that this is useful for polyfilling
- # [00:06] <rniwa> esprehn: e.g. dialog element can be polyfilled using lifecycle callbacks to get the timing right which is hard to do today
- # [00:06] <rniwa> Domenic_: here's a lot of things you can do with is=
- # [00:06] <rniwa> parsing hooks for <template>, <p>, <head>, <table>
- # [00:06] <rniwa> accessibility bheavior
- # [00:07] <rniwa> some DOM objects such as DOMTokenList
- # [00:07] <rniwa> status bar hover (e.g. on a)
- # [00:07] <rniwa> default style cascade position
- # [00:07] <rniwa> some pseudo class states such as :visited, :disabled, :link, :read-only, etc...
- # [00:07] <rniwa> focusable w/o tabindex
- # [00:07] <rniwa> hook into preload scanner
- # [00:08] <rniwa> hober: I think this is a lost of features some of which we may want or not want
- # [00:08] <rniwa> hober: e.g. we may not want custom elements to override status bar
- # [00:08] <rniwa> hober: pseudo style matching or having accessibility API might be useful
- # [00:09] <rniwa> justin: is= attribute is ugly and in many cases you'd use custom tag name
- # [00:09] <rniwa> justin: but it's useful in a few minority cases in which this feature is useful.
- # [00:09] <rniwa> justin: so it's ugly but only in subset of cases
- # [00:10] <rniwa> hober: it's weird that author has to use one or another sometimes
- # [00:10] <rniwa> monica: but author already knows because there are some things browser wouldn't allow you to do
- # [00:10] <rniwa> justin: similar things with link and template.
- # [00:11] <rniwa> Travis: this is really about participate in lifecycle/callbacks of native elements
- # [00:12] <rniwa> dglazkov: what if i asked all browsers had all these features except is=
- # [00:13] <chaals> s/i asked/
- # [00:13] <rniwa> justin: what worries me is what if we had a set of native features and some of them were not extensible or amendable to support our use case
- # [00:13] * Quits: wilsonpage (~wilsonpage@public.cloak) ("My Mac has gone to sleep. ZZZzzz…")
- # [00:13] <chaals> s/except/instead of
- # [00:14] <rniwa> justin: for our subclass of link element, we say use <link is=~> so it's never ambiguous as to which syntax you use
- # [00:14] <rniwa> annevk: what if instead of is=, we added the capability to add lifecycle callbacks
- # [00:15] <rniwa> Domenic_: what if I wanted to add methods and properties
- # [00:15] <rniwa> esprehn: what if I wanted one behavior in one a and another in another a
- # [00:15] <rniwa> annevk: you don't. you get custom behaviors for all elements
- # [00:15] <justin> q+
- # [00:15] * Zakim sees chaals, LJWatson, justin on the speaker queue
- # [00:16] <rniwa> chaals: with custom elements, we can have my-evan-links, my-odd-links, and you can put different ones
- # [00:16] <rniwa> chaals: but you can't do that with that kind of global extension
- # [00:16] <chaals> ack me
- # [00:16] * Zakim sees LJWatson, justin on the speaker queue
- # [00:16] <rniwa> justin: now for our use case, we have to implement our non-standardized attribute
- # [00:17] <rniwa> esprehn: this can be very spammy
- # [00:17] <chaals> ack LJWatson
- # [00:17] <Zakim> LJWatson, you wanted to ask whether role= could be used/extended to trigger native behaviour?
- # [00:17] * Zakim sees justin on the speaker queue
- # [00:17] <rniwa> LJWatson: I was wondering if we could extend "role" attribute
- # [00:17] <rniwa> LJWatson: what if "role" attribute made element actually linkable instead of only exposing it to AT.
- # [00:18] <rniwa> hober, Domenic_ : this might not be backwards compatible because authors put this on some elements in which they don't expect such a behavior
- # [00:19] <LJWatson> ack me
- # [00:19] * Zakim sees justin on the speaker queue
- # [00:26] * Quits: LJWatson (~LJWatson@public.cloak) ("Page closed")
- # [00:27] * Quits: arronei (~arronei@public.cloak) (Ping timeout: 180 seconds)
- # [00:28] * Joins: LJWatson (~LJWatson@public.cloak)
- # [00:31] * Quits: jan_miksovsky (~jan_miksovsky@public.cloak) (Ping timeout: 180 seconds)
- # [00:49] <esprehn> chaals: Asked esprehn to scribe
- # [00:49] <chaals> scribe: esprehn
- # [00:49] <esprehn> dglazkov: can we summarize all the in person discussions?
- # [00:49] <esprehn> justin: we were mainly talking about the (polymer) use cases
- # [00:50] <esprehn> justin: the only way we can see working around losing is is to essentially run the custom elements polyfill in every shadowroot of the document
- # [00:50] <esprehn> justin: and do the upgrading ourselves with mutation observers, with MO timing, etc. it'll be very difficult
- # [00:50] <esprehn> Travis: change to as or "with"
- # [00:50] <esprehn> "as"
- # [00:50] * plh waits for "couldbe"
- # [00:51] * dglazkov wannabe
- # [00:51] <esprehn> Travis: I found that "with" explains it better
- # [00:52] <chaals> esprehn: Other discussion: all this stuff is does is important,but years of work. is= is a really quick way to solve it, and that avoids having authors making piles of broken things while they are waiting for us to get to nirvana
- # [00:52] * plh "isForNow"
- # [00:52] <esprehn> justin: what's the conclusion?
- # [00:53] <esprehn> chaals: who opposes?
- # [00:53] <esprehn> rniwa: I oppose
- # [00:53] <dglazkov> \
- # [00:53] <dglazkov> ooops
- # [00:53] * dglazkov was cleaning keyboard
- # [00:53] <esprehn> monica: do you mean in v1 or v2 or ever?
- # [00:54] <esprehn> rniwa: what can we agree on and have this feature be available in all browsers?
- # [00:54] * plh "withoutApple"
- # [00:54] <esprehn> chaals: what do others think?
- # [00:54] <esprehn> Travis: I think it's a compelling feature
- # [00:54] <esprehn> wchen: we're neutral
- # [00:55] <esprehn> Travis: it layers on top of custom elements, you can have both things
- # [00:55] <esprehn> justin: I want to make sure that everyone understands our use cases
- # [00:55] <esprehn> rniwa: we understand them
- # [00:55] <esprehn> justin: if we get native custom elements without them it'll be very tough for us
- # [00:55] <esprehn> Domenic_: just continue using your polyfill?
- # [00:56] <esprehn> justin: we can't polyfill it
- # [00:56] <esprehn> Domenic_: you can continue using it like you do in other browsers
- # [00:56] <esprehn> justin: Firefox doesn't have native shadow dom so we can use a single MO
- # [00:56] <esprehn> rniwa: replace attachShadow and add a MO there
- # [00:56] <esprehn> Domenic_: if you don't want to work with the browser you have to do hacks
- # [00:56] <esprehn> justin: we don't want to have thousands of MO
- # [00:57] <esprehn> MO = MutationObserver
- # [00:57] <esprehn> chaals: there's a certain amount of support for doing this
- # [00:57] <esprehn> rniwa: I think there's a lot of frameworks that could work without this, maybe we can come to consensus in v2 and then add it
- # [00:57] <esprehn> justin: I think we've come a little closer on understanding the need for this feature
- # [00:58] <esprehn> Travis: decouple it from custom elements?
- # [00:58] <esprehn> Travis: we could create a new feature separate from defineElement
- # [00:58] <esprehn> chaals: what's the support from chrome for actually doing this?
- # [00:58] <esprehn> dglazkov: easy, it's already done
- # [00:59] <esprehn> esprehn: we think it's easy, without it authors do something really bad to emulate links
- # [00:59] * Quits: cdata (~cdata@public.cloak) (Ping timeout: 180 seconds)
- # [00:59] <esprehn> chaals: we could sit around and argue consensus, or we could break it apart
- # [01:00] <esprehn> rniwa: why would you put the link element in a shadow dom since you can just querySelector without the parser
- # [01:00] <esprehn> rniwa: and the <head> problem doesn't apply
- # [01:00] <esprehn> rniwa: in the case where in the main document you can querySelector and define all instances of a link
- # [01:01] <esprehn> esprehn: when do you upgrade the links in the page?
- # [01:01] <esprehn> rniwa: I don't think you can expect multiple libraries to coordinate
- # [01:01] <chaals> s/break it apart/write it up and see what people implement and want to rely on
- # [01:02] <esprehn> rniwa: you have to create your own shadow dom yourself, ... this is the problem in the current api (as discussed 3 years ago) we want to have the simplest apis to allow frameworks authors to decide how they're used
- # [01:02] <esprehn> rniwa: now you're saying without this API some frameworks have issues
- # [01:02] <esprehn> justin: we think without this there's issues
- # [01:02] <esprehn> chaals: my experience is that the use cases keep coming back and the browsers keep coming back and saying they dont' want do it. One browser did it (chrome), one said we think it's compelling (Edge), one said no (Safari)
- # [01:03] <esprehn> chaals: sitting around and discussing if it'll fly is less useful than going and just doing and writing a separate spec
- # [01:03] <esprehn> chaals: if people implement it then it's done, if the don't then it isn't
- # [01:03] <esprehn> chaals: you can't force people to agree with you in a standards meeting
- # [01:04] <esprehn> hober: lets see what happens in implementations
- # [01:05] * Joins: jan_miksovsky (~jan_miksovsky@public.cloak)
- # [01:05] <esprehn> jan_miksovsky: the question I have is that a component's kids are just as important as its attributes
- # [01:06] <esprehn> jan_miksovsky: lots of components want to know when they have stuff
- # [01:06] <esprehn> jan_miksovsky: how do components respond to this? is there a callback?
- # [01:06] <esprehn> justin: polymer has "effective children changed" for actual or projected children changed (shadow dom concept)
- # [01:07] <esprehn> justin: we had customers who needed to know this
- # [01:07] * chaals wonders who is connected remotely
- # [01:07] <esprehn> rniwa: key question is direct children, or ones projected
- # [01:07] <esprehn> hayato: yeah
- # [01:07] <esprehn> jan_miksovsky: use cases we have us knowing final distribution changing, they want to know if there's a <slot> and what changes
- # [01:07] <esprehn> rniwa: so it's a shadow dom question
- # [01:07] <esprehn> esprehn: right since otherwise you can just use MO
- # [01:08] <esprehn> rniwa: yeah so talking about any projected stuff is a shadow dom question
- # [01:08] <esprehn> hayato: github issue about slotted change event, we think we should support it with a new MO type
- # [01:08] <esprehn> rniwa: we need to have either an event or a MO type
- # [01:08] <esprehn> rniwa: annevk do you remember?
- # [01:08] <esprehn> rniwa: want a new record for when a slot changes what's distributed to it
- # [01:08] <esprehn> Travis: is the timing nano or micro?
- # [01:09] <esprehn> jan_miksovsky: I don't care, today there's nothing, it's hard and brittle to do today
- # [01:09] <kochi2> the issue is: https://github.com/w3c/webcomponents/issues/288
- # [01:09] <esprehn> Domenic_: yeah I think making a nicer MO api for this makes sense, with batching so insert/remove pairs don't spam
- # [01:10] <esprehn> annevk: MO has childList, and you can do subtree too
- # [01:10] <esprehn> Travis: can we use a selector?
- # [01:10] <esprehn> rniwa: still expensive, I don't want to do that
- # [01:10] <esprehn> jan_miksovsky: need something like this to be robust
- # [01:11] <esprehn> jan_miksovsky: I don't want something like this to get lost
- # [01:11] <esprehn> annevk: can you clarify?
- # [01:12] <esprehn> esprehn: this is for slot changing what's distributed
- # [01:12] * leaverou is now known as leaverou_away
- # [01:12] <esprehn> rniwa: you have a custom element with a kid that's a <slot>, slot doesn't generate a box by default, you want to look at the children including the slot to look at the final positions
- # [01:12] <esprehn> jan_miksovsky: /does example of a carousel on the whiteboard
- # [01:13] <esprehn> jan_miksovsky: ex. <my-carousel> and you put <img> in there, but you can also put <slot> in there, but the <my-carousel> wants to see all the <img> that go to the <slot>
- # [01:13] <esprehn> jan_miksovsky: getEffectiveChildren in polymer handles this
- # [01:14] * leaverou_away is now known as leaverou
- # [01:14] <esprehn> rniwa: this doesn't seem like a DOM concern
- # [01:14] * Joins: Florian (~Florian@public.cloak)
- # [01:15] <esprehn> rniwa: seems more like a box tree concern
- # [01:15] <justin> q+
- # [01:15] * Zakim sees justin on the speaker queue
- # [01:15] <esprehn> esprehn: no if you create a custom video element, you want the slotted <source> things to participate
- # [01:15] <esprehn> jan_miksovsky: yeah this is author expectation
- # [01:15] <esprehn> rniwa: you want to know when all slotted elements change, doesn't matter if they're invisible or what
- # [01:16] <esprehn> Domenic_: isn't this just solved in polymer?
- # [01:16] <esprehn> esprehn: at great expense
- # [01:16] <esprehn> rniwa: I thought it was only about boxes, but if you don't think about that and it's just any of the children changed
- # [01:16] <esprehn> rniwa: you just want to know when the list of nodes distributed to a slot, or any child nodes
- # [01:17] <esprehn> annevk: composed includes closed shadow trees?
- # [01:17] <esprehn> justin: no, it doesn't matter
- # [01:17] <esprehn> rniwa: doesn't matter, only see things outside the shadow
- # [01:17] <esprehn> jan_miksovsky: I hear there should really be a mutation you observe the slot with, maybe a new flag for MO
- # [01:17] <esprehn> annevk: maybe like the composed child list
- # [01:17] <esprehn> justin: not really composed, just projected children of the slot have changed
- # [01:18] <esprehn> rniwa: want to know when the assigned nodes changed
- # [01:18] <esprehn> rniwa: and deep tree as well, reuse the subtree flag
- # [01:18] <esprehn> hayato: shouldn't be deep
- # [01:19] <esprehn> rniwa: there's one level, which is know the assigned nodes to your slot, and also want to know if any of them, or any of them all the way down
- # [01:19] <esprehn> justin: bike shed: maybe "tall" ?
- # [01:19] <esprehn> *room laughs*
- # [01:23] <chaals> scribe: chaals
- # [01:23] <chaals> esprehn: You're calculating the list already
- # [01:23] <chaals> rniwa: no
- # [01:23] <Travis> esprehn and rniwa discuss implementation challenges of maintaining a list for the purposes of mutation observer.
- # [01:23] <chaals> justin: what if you get a simple list, and can ask for the expensive part if you need it.
- # [01:23] <chaals> Jan: just notify when the tree changed, and you can walk it
- # [01:24] <chaals> justin: needs to cover the case that something changed a few levels up in the slotting
- # [01:24] <chaals> esprehn: can you queue a record that the slots changed and then getComputed ?
- # [01:24] <chaals> … then the user can call the getComp
- # [01:24] <chaals> rniwa: Yes
- # [01:24] * leaverou is now known as leaverou_away
- # [01:25] <chaals> esprehn: Seems like we can do this, there is a compromise, need a bug on Mutation Observers
- # [01:25] <dglazkov> s/getComputed/getDistributedNodes
- # [01:25] <dglazkov> s/getComputed/getDistributedNodes/
- # [01:25] <chaals> justin: OK that it is microtask timing not nano? There will be effective children that can only be observed at microtask level
- # [01:25] <dglazkov> s/getComp/getDistributedNodes/
- # [01:25] <chaals> dglazkov: microtask is OK
- # [01:25] <chaals> jan_miksovsky: So make a bug for a new mutation observer?
- # [01:26] <chaals> rniwa: Think there is already a GH issue
- # [01:26] <chaals> jan_miksovsky: would tell you the slot that changed, and then you can call getDistributed…
- # [01:26] <rniwa> https://github.com/w3c/webcomponents/issues/288
- # [01:26] <chaals> ^the relevant issue.
- # [01:26] * Joins: arronei (~arronei@public.cloak)
- # [01:26] <chaals> rniwa: someone should come up with a formal spec.
- # [01:27] <chaals> jan_miksovsky: happy to work with someone to spec it.
- # [01:27] <chaals> … don't want to take the task myself.
- # [01:27] <chaals> ACTION: jan_M to work with Hayato and spec this out
- # [01:27] * trackbot is creating a new ACTION.
- # [01:27] * RRSAgent records action 4
- # [01:27] <trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.
- # [01:28] <chaals> Topic: upgrade is top-down, right?
- # [01:28] <chaals> jan_miksovsky: when do you know your children are done parsing?
- # [01:28] <chaals> [you probably don't know]
- # [01:29] <chaals> [in v1 at least]
- # [01:29] <chaals> rniwa: if you use Mutation Observer, by the time you get it all the children have been upgraded
- # [01:30] <chaals> esprehn: We do upgrading bottom-up in innerHTML
- # [01:30] <chaals> Avk: what if your custom elements load midway through parsing a big document?
- # [01:31] <chaals> esprehn: If the definition hasn't appeared, you call a and then b you get all a then all b.
- # [01:31] <chaals> … in construction order
- # [01:31] <chaals> rniwa: That seems bad
- # [01:31] <chaals> … good to stick with top-down always
- # [01:32] <chaals> Domenic_: tend to agree
- # [01:32] <chaals> AvK: tree order doesn't catch things not in the tree
- # [01:32] <chaals> esprehn: that's why we keep a seperate list.
- # [01:32] <chaals> rniwa: why?
- # [01:32] <chaals> esprehn: consistent worldview.
- # [01:32] <chaals> AvK; You have createElement, then a custom element not inserted and then later you add it
- # [01:32] <chaals> rniwa: OK
- # [01:33] <chaals> [theWebIsABadWeb event]
- # [01:33] <chaals> rniwa: Think we should be consistent - keep creation order everywhere then.
- # [01:34] <chaals> esprehn: attach/detach are in tree order…
- # [01:34] <chaals> rniwa: you need to spec that way.
- # [01:34] <chaals> esprehn: polymer wanted upgrades bottom-up so we did that instead.
- # [01:34] <chaals> … and now we ended up all creation order.
- # [01:34] <chaals> RESOLUTION: we remember why we have the spec the way it is.
- # [01:35] <chaals> Rationale: You can't make it work if you don't have creation order, and consistency is good.
- # [01:35] <chaals> ACTION: domenic to document stack of queues and ordering
- # [01:35] * trackbot is creating a new ACTION.
- # [01:35] * RRSAgent records action 5
- # [01:35] <trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.
- # [01:36] <chaals> Topic: Shadow DOM Styling
- # [01:36] <kochi2> #316
- # [01:36] <kochi2> https://github.com/w3c/webcomponents/issues/316
- # [01:36] <chaals> Kochi: think this is a problem of updating order of style comoing from different shadow trees
- # [01:36] <chaals> … we agree prioriity of rules is tree of tree order of shadow trees
- # [01:37] <chaals> … remaining point is bug 315 - how do we handle style attributes
- # [01:37] <kochi2> s/315/316/
- # [01:37] <chaals> esprehn: Where in the order it comes?
- # [01:37] <chaals> … didn't we agree with Tab on this?
- # [01:38] <chaals> LJW: at the last meeting
- # [01:38] <rniwa> Two test cases: https://github.com/w3c/web-platform-tests/pull/2515
- # [01:38] <chaals> hober: No longer see any disagreement in the issue
- # [01:38] <chaals> [jan_miksovsky leaves]
- # [01:39] <chaals> Kochi in the webplatform tests I put some tests. I implemented to follow the option 2 in the github bug.
- # [01:39] <chaals> … if everyone agrees on that approach, we are good.
- # [01:39] <rniwa> Here's the test case: http://w3c-test.org/shadow-dom/styles/shadow-cascade-order.html
- # [01:39] <chaals> hayato: basically this means current vs new implementation. Unless there is a strong objection we should adopt option 2.
- # [01:40] * Quits: jan_miksovsky (~jan_miksovsky@public.cloak) (Ping timeout: 180 seconds)
- # [01:40] <chaals> … if the test cases are unacceptable, please object.
- # [01:40] <chaals> rniwa: proposal is to do option 2?
- # [01:41] <chaals> … we pass everything except a slotted we don't implement yet.
- # [01:42] <chaals> [taken offline]
- # [01:42] <chaals> agenda+ beer
- # [01:42] * Zakim notes agendum 4 added
- # [01:42] * Quits: sicking (~sicking@public.cloak) (sicking)
- # [01:42] <chaals> Topic: Imports
- # [01:43] <chaals> Domenic_: Make them ES6. Awesome.
- # [01:43] <chaals> [But it was DMitri's idea]
- # [01:43] * Joins: sicking (~sicking@public.cloak)
- # [01:43] <chaals> esprehn: we want to drop style
- # [01:43] <chaals> justin: we want the scripts to run
- # [01:43] <chaals> Domenic_: not in the same doc
- # [01:44] <chaals> justin: There should be a registry
- # [01:44] <chaals> TOpic: registry
- # [01:44] <chaals> rniwa: not sure why mutliple documents need to share the registry
- # [01:44] <chaals> Domenic_: yeah Eliot doesn't like that either
- # [01:44] <chaals> esprehn: came from a debate about author expectation
- # [01:45] <chaals> … if imports don't share the same registry it produces undesirable behaviour - you can't share things across your imports. The rest of the sharing is consistency that I think is confusing - you cannot escape the registry.
- # [01:45] <chaals> AvK: if iframe scrdoc and the registry doesn't cross that would be sad
- # [01:45] <chaals> esprehn: It doesn't - thats a different window
- # [01:46] <chaals> rniwa: It would be nice to be able to use a registry, not be stuck with one
- # [01:46] * Joins: rictic (~rictic@public.cloak)
- # [01:46] <chaals> dglazkov: should be a v2
- # [01:46] <chaals> esprehn: want to scale bakc- you don't share registry unless you ask for it
- # [01:46] <chaals> Domenic_: should that be in v1 or can we start out with unshared registry all the time
- # [01:47] <chaals> AvK; if you do shared registry you get global pollution
- # [01:47] <chaals> esprehn: there was one registry for everything. That's not nice - e.g. upgrades run on XHR'ed stuff.
- # [01:47] <chaals> … so it is on some docs
- # [01:47] <chaals> rniwa: yeah. Which is confusing.
- # [01:47] <chaals> … my preference is not to do any of this stuff.
- # [01:47] <chaals> … one registry per document
- # [01:48] <chaals> dglazkov: That's OK
- # [01:48] <chaals> … if we get HTML modules we'll need a registry API.
- # [01:48] <chaals> rniwa: if we get a simple registry API we can have one. Until then you cannot have nice things.
- # [01:48] <chaals> Travis: would it reflect structures?
- # [01:49] <chaals> dglazkov: n argument for doing this in v1, if you had register.set you don't need defineElement
- # [01:50] <chaals> RESOLUTION: no sharing of registries in v1.
- # [01:50] * Quits: LJWatson (~LJWatson@public.cloak) ("Page closed")
- # [01:51] * Quits: Travis (~Travis@public.cloak) ("Page closed")
- # [01:51] * Quits: rniwa (~textual@public.cloak) ("My Mac has gone to sleep. ZZZzzz…")
- # [01:51] * Quits: plh (plehegar@public.cloak) ("Leaving")
- # [01:52] <chaals> Thanks scribes, many thanks apple for hosting, [adjourned]
- # [01:52] * Quits: chaals (~Adium@public.cloak) ("Leaving.")
- # [01:52] * Joins: cdata (~cdata@public.cloak)
- # [01:56] * Quits: monica (~monica@public.cloak) (Ping timeout: 180 seconds)
- # [01:57] * Quits: arronei (~arronei@public.cloak) (Ping timeout: 180 seconds)
- # [01:58] * Quits: justin (~justin@public.cloak) (Ping timeout: 180 seconds)
- # [01:59] * Quits: cdata (~cdata@public.cloak) ("Page closed")
- # [02:11] * leaverou_away is now known as leaverou
- # [02:14] * Quits: bicknellr (~bicknellr@public.cloak) ("Page closed")
- # [02:17] * Quits: jsbell (~jsbell@public.cloak) ("There's no place like home...")
- # [02:17] * Quits: kochi2 (~Adium@public.cloak) (Ping timeout: 180 seconds)
- # [02:22] * leaverou is now known as leaverou_away
- # [02:22] * Quits: marcosc (~marcosc@public.cloak) (Client closed connection)
- # [02:23] * Joins: marcosc (~marcosc@public.cloak)
- # [02:28] * Joins: kochi2 (~Adium@public.cloak)
- # [02:30] * Quits: marcosc (~marcosc@public.cloak) (Ping timeout: 180 seconds)
- # [02:31] * Quits: rictic (~rictic@public.cloak) ("Page closed")
- # [02:33] * Quits: kochi2 (~Adium@public.cloak) (Client closed connection)
- # [02:46] * Joins: estellevw (~estellevw@public.cloak)
- # [02:58] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [03:08] * Joins: estellevw (~estellevw@public.cloak)
- # [03:11] * Quits: smaug (~chatzilla@public.cloak) (Ping timeout: 180 seconds)
- # [03:20] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [03:25] * Quits: sicking (~sicking@public.cloak) (sicking)
- # [03:28] * Joins: marcosc (~marcosc@public.cloak)
- # [03:31] * Joins: estellevw (~estellevw@public.cloak)
- # [03:56] * leaverou_away is now known as leaverou
- # [03:57] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [04:06] * Quits: geheimnis` (~geheimnis@public.cloak) (Client closed connection)
- # [04:08] * Joins: geheimnis` (~geheimnis@public.cloak)
- # [04:13] * leaverou is now known as leaverou_away
- # [04:33] * Joins: estellevw (~estellevw@public.cloak)
- # [04:39] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [05:14] * Joins: estellevw (~estellevw@public.cloak)
- # [06:08] * Quits: marcosc (~marcosc@public.cloak) (Client closed connection)
- # [06:09] * Joins: marcosc (~marcosc@public.cloak)
- # [06:16] * Quits: marcosc (~marcosc@public.cloak) (Ping timeout: 180 seconds)
- # [06:38] * Joins: zcorpan (~zcorpan@public.cloak)
- # [07:07] * Quits: decadance (~decadance@public.cloak) (Ping timeout: 180 seconds)
- # [07:17] * Joins: decadance (~decadance@public.cloak)
- # [07:26] * Joins: sicking (~sicking@public.cloak)
- # [07:37] * Quits: decadance (~decadance@public.cloak) (Client closed connection)
- # [07:44] * Joins: decadance (~decadance@public.cloak)
- # [08:21] <MikeSmith> RRSAgent, make minutes
- # [08:21] <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/26-webapps-minutes.html MikeSmith
- # [08:21] * Quits: zcorpan (~zcorpan@public.cloak) (Client closed connection)
- # [08:22] <MikeSmith> RRSAgent, make logs public
- # [08:22] <RRSAgent> I have made the request, MikeSmith
- # [08:23] <MikeSmith> i/without it authors/scribe: esprehn
- # [08:23] <MikeSmith> i/without it authors/scribenick: esprehn
- # [08:23] <MikeSmith> RRSAgent, make logs public
- # [08:23] <RRSAgent> I have made the request, MikeSmith
- # [08:23] <MikeSmith> RRSAgent, make minutes
- # [08:23] <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/26-webapps-minutes.html MikeSmith
- # [08:41] <MikeSmith> Present: Domenic_Denicola Takayoshi_Kochi Leonie_Watson Travis_Leithead AnneVK Arron_Eicholz Chaals Dimitri_Glazkov Elliott_Sprehn Hayato_Ito Ted_OConnor Jan_Miksovsky Justin_Fagnani Ryosuke_Niwa
- # [08:41] <MikeSmith> RRSAgent, make minutes
- # [08:41] <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/26-webapps-minutes.html MikeSmith
- # [08:42] <MikeSmith> Meeting: Custom Elements discussion
- # [08:42] <MikeSmith> RRSAgent, make minutes
- # [08:42] <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/26-webapps-minutes.html MikeSmith
- # [08:45] * Joins: zcorpan (~zcorpan@public.cloak)
- # [09:21] * Quits: sicking (~sicking@public.cloak) (sicking)
- # [09:21] * Joins: marcosc (~marcosc@public.cloak)
- # [09:30] * Quits: marcosc (~marcosc@public.cloak) (Ping timeout: 180 seconds)
- # [09:42] * Joins: dom (dom@public.cloak)
- # [09:45] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [10:04] * Joins: marcosc (~marcosc@public.cloak)
- # [10:11] * Quits: marcosc (~marcosc@public.cloak) (Client closed connection)
- # [10:29] * Joins: wilsonpage (~wilsonpage@public.cloak)
- # [11:20] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [12:14] * leaverou_away is now known as leaverou
- # [12:20] * Joins: Florian (~Florian@public.cloak)
- # [12:23] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [12:23] * Joins: Florian (~Florian@public.cloak)
- # [12:24] * leaverou is now known as leaverou_away
- # [12:25] * Joins: marcosc (~marcosc@public.cloak)
- # [12:26] * Joins: marcosc_ (~marcosc@public.cloak)
- # [12:26] * Quits: marcosc (~marcosc@public.cloak) (Client closed connection)
- # [12:55] * Quits: zcorpan (~zcorpan@public.cloak) (Client closed connection)
- # [13:10] * Joins: zcorpan (~zcorpan@public.cloak)
- # [13:19] * leaverou_away is now known as leaverou
- # [13:29] * leaverou is now known as leaverou_away
- # [13:49] * Quits: marcosc_ (~marcosc@public.cloak) (Client closed connection)
- # [14:28] * Joins: smaug (~chatzilla@public.cloak)
- # [14:55] * Quits: zcorpan (~zcorpan@public.cloak) (Client closed connection)
- # [15:21] * Joins: estellevw (~estellevw@public.cloak)
- # [15:21] * Quits: wilsonpage (~wilsonpage@public.cloak) ("My Mac has gone to sleep. ZZZzzz…")
- # [15:23] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [15:30] * Quits: flaki (~sid26072@public.cloak) (Client closed connection)
- # [15:30] * Quits: slightlyoff (~sid1768@public.cloak) (Client closed connection)
- # [15:30] * Quits: tyoshino (~sid19222@public.cloak) (Client closed connection)
- # [15:30] * Quits: ebryn (~sid2895@public.cloak) (Client closed connection)
- # [15:30] * Quits: Josh_Soref (~sid4015@public.cloak) (Client closed connection)
- # [15:30] * Quits: dstockwell (~sid40369@public.cloak) (Client closed connection)
- # [15:30] * Quits: koji (~sid53200@public.cloak) (Client closed connection)
- # [15:30] * Quits: hayato (~sid20728@public.cloak) (Client closed connection)
- # [15:31] * Quits: timeless (~sid4015@public.cloak) (Client closed connection)
- # [15:31] * Quits: Domenic_ (~sid10976@public.cloak) (Client closed connection)
- # [15:31] * Quits: mkwst (~sid395@public.cloak) (Client closed connection)
- # [15:31] * Quits: JakeA (~sid3836@public.cloak) (Client closed connection)
- # [15:31] * Quits: ojan (~sid5519@public.cloak) (Client closed connection)
- # [15:31] * Quits: othree (~sid16133@public.cloak) (Client closed connection)
- # [15:31] * Quits: dfreedm (~sid7859@public.cloak) (Client closed connection)
- # [15:31] * Quits: pdr (~sid7901@public.cloak) (Client closed connection)
- # [15:31] * Quits: scheib (~sid4467@public.cloak) (Client closed connection)
- # [15:31] * Quits: dglazkov (~sid4270@public.cloak) (Client closed connection)
- # [15:31] * Quits: ElijahLynn (~sid21431@public.cloak) (Client closed connection)
- # [15:31] * Quits: dcooney (~sid20727@public.cloak) (Client closed connection)
- # [15:31] * Quits: jkomoros (~sid7860@public.cloak) (Client closed connection)
- # [15:31] * Quits: adrianba (~sid55164@public.cloak) (Client closed connection)
- # [15:31] * Quits: TabAtkins (~sid11559@public.cloak) (Client closed connection)
- # [15:31] * Quits: sangwhan (~sid12645@public.cloak) (Client closed connection)
- # [15:31] * Quits: cwilso (~sid10206@public.cloak) (Client closed connection)
- # [15:31] * Quits: esprehn (~sid10445@public.cloak) (Client closed connection)
- # [15:31] * Quits: krit (~sid15081@public.cloak) (Client closed connection)
- # [15:32] * Quits: tobie (~sid5692@public.cloak) (Client closed connection)
- # [15:32] * Joins: dstockwell (~sid40369@public.cloak)
- # [15:32] * Joins: ebryn (~sid2895@public.cloak)
- # [15:32] * Joins: flaki (~sid26072@public.cloak)
- # [15:32] * Joins: tyoshino (~sid19222@public.cloak)
- # [15:32] * Joins: Josh_Soref (~sid4015@public.cloak)
- # [15:32] * Joins: koji (~sid53200@public.cloak)
- # [15:32] * Joins: JakeA (~sid3836@public.cloak)
- # [15:32] * Joins: othree (~sid16133@public.cloak)
- # [15:32] * Joins: Domenic_ (~sid10976@public.cloak)
- # [15:32] * Joins: mkwst (~sid395@public.cloak)
- # [15:32] * Joins: hayato (~sid20728@public.cloak)
- # [15:32] * Joins: pdr (~sid7901@public.cloak)
- # [15:32] * Joins: ojan (~sid5519@public.cloak)
- # [15:32] * Joins: dfreedm (~sid7859@public.cloak)
- # [15:32] * Joins: slightlyoff (~sid1768@public.cloak)
- # [15:33] * Joins: scheib (~sid4467@public.cloak)
- # [15:33] * Joins: dglazkov (~sid4270@public.cloak)
- # [15:33] * Joins: timeless (~sid4015@public.cloak)
- # [15:33] * Joins: dcooney (~sid20727@public.cloak)
- # [15:33] * Joins: jkomoros (~sid7860@public.cloak)
- # [15:33] * Joins: ElijahLynn (~sid21431@public.cloak)
- # [15:33] * Joins: TabAtkins (~sid11559@public.cloak)
- # [15:33] * Joins: adrianba (~sid55164@public.cloak)
- # [15:33] * Joins: esprehn (~sid10445@public.cloak)
- # [15:33] * Joins: sangwhan (~sid12645@public.cloak)
- # [15:33] * Joins: krit (~sid15081@public.cloak)
- # [15:34] * Joins: cwilso (~sid10206@public.cloak)
- # [15:34] * Joins: tobie (~sid5692@public.cloak)
- # [15:55] * Joins: zcorpan (~zcorpan@public.cloak)
- # [16:01] * Joins: wilsonpage (~wilsonpage@public.cloak)
- # [16:03] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [16:06] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [16:07] * leaverou_away is now known as leaverou
- # [16:09] * Joins: Florian (~Florian@public.cloak)
- # [16:18] * leaverou is now known as leaverou_away
- # [16:28] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [16:56] * Joins: zcorpan (~zcorpan@public.cloak)
- # [17:04] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [17:08] * Joins: zcorpan (~zcorpan@public.cloak)
- # [17:22] * shepazu_ is now known as shepazu
- # [17:29] * Joins: Florian (~Florian@public.cloak)
- # [17:29] * leaverou_away is now known as leaverou
- # [17:39] * Quits: zcorpan (~zcorpan@public.cloak) (Client closed connection)
- # [17:51] * Joins: estellevw (~estellevw@public.cloak)
- # [18:02] * Joins: tantek (~tantek@public.cloak)
- # [18:06] * Quits: Florian (~Florian@public.cloak) (Ping timeout: 180 seconds)
- # [18:30] * Joins: chaals (~Adium@public.cloak)
- # [18:36] * Joins: sicking (~sicking@public.cloak)
- # [18:40] * Joins: zcorpan (~zcorpan@public.cloak)
- # [18:47] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [18:51] * Joins: jsbell (~jsbell@public.cloak)
- # [18:52] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [19:00] * Joins: Florian (~Florian@public.cloak)
- # [19:19] * Quits: dom (dom@public.cloak) ("")
- # [19:30] * leaverou is now known as leaverou_away
- # [19:31] * leaverou_away is now known as leaverou
- # [19:36] * Quits: Florian (~Florian@public.cloak) (Ping timeout: 180 seconds)
- # [19:40] * Joins: zcorpan (~zcorpan@public.cloak)
- # [19:42] * wilsonpage is now known as wilsonpage-away
- # [19:48] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [19:49] * leaverou is now known as leaverou_away
- # [19:59] * wilsonpage-away is now known as wilsonpage
- # [20:10] * Quits: wilsonpage (~wilsonpage@public.cloak) ("My Mac has gone to sleep. ZZZzzz…")
- # [20:31] * Joins: Florian (~Florian@public.cloak)
- # [20:41] * Joins: zcorpan (~zcorpan@public.cloak)
- # [20:49] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [20:50] * Quits: sicking (~sicking@public.cloak) (sicking)
- # [20:58] * Quits: tantek (~tantek@public.cloak) (tantek)
- # [21:07] * Quits: Florian (~Florian@public.cloak) (Ping timeout: 180 seconds)
- # [21:21] * Quits: chaals (~Adium@public.cloak) ("Leaving.")
- # [21:30] * Joins: estellevw (~estellevw@public.cloak)
- # [21:43] * Joins: zcorpan (~zcorpan@public.cloak)
- # [21:50] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [22:01] * Joins: Florian (~Florian@public.cloak)
- # [22:35] * Joins: sicking (~sicking@public.cloak)
- # [22:36] * Quits: Florian (~Florian@public.cloak) (Ping timeout: 180 seconds)
- # [22:44] * Joins: zcorpan (~zcorpan@public.cloak)
- # [22:51] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [22:51] * Joins: rniwa (~textual@public.cloak)
- # [22:55] * Joins: marcosc (~marcosc@public.cloak)
- # [22:55] * Joins: tantek (~tantek@public.cloak)
- # [23:03] * Quits: tantek (~tantek@public.cloak) (tantek)
- # [23:14] * Joins: chaals (~Adium@public.cloak)
- # [23:21] <sicking> annevk: my FAQ says that .withCredentials affects how set-cookie headers on the response is handled, no?
- # [23:21] <annevk> yeah, I removed my reply there
- # [23:22] <sicking> annevk: also, did your comment get deleted? I see the email but nothing con github.com
- # [23:22] <annevk> I got confused by the paragraph above
- # [23:22] <sicking> annevk: ah, cool
- # [23:22] <sicking> annevk: would you be interested to try to add some of this stuff to the spec?
- # [23:23] <annevk> I guess I can integrate your justification into https://fetch.spec.whatwg.org/#http-cors-protocol somehow, yes
- # [23:23] <annevk> let me file a bug so I don't forget
- # [23:23] <sicking> annevk: i think I also missed the question timbl was actually asking, which is "why is .withCredentials needed?"
- # [23:23] <sicking> annevk: let me know if I can help
- # [23:24] <annevk> Note that some stuff is explained: https://fetch.spec.whatwg.org/#basic-safe-cors-protocol-setup
- # [23:24] <annevk> but not a whole lot admittedly
- # [23:25] <sicking> yeah. It might be worth having some form of FAQ so people can find this stuff too. I'm not sure
- # [23:25] <sicking> most people aren't going to read the whole spec though
- # [23:25] <sicking> so if we put something in there it needs to be findable
- # [23:31] * Joins: Florian (~Florian@public.cloak)
- # [23:44] * Joins: zcorpan (~zcorpan@public.cloak)
- # [23:52] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # Session Close: Wed Jan 27 00:00:01 2016
Previous day, Next day
Think these logs are useful? Then please donate to show your gratitude (and keep them up, of course). Thanks! — Krijn