From: Jan Miksovsky [mailto:email@example.com]
> As a reminder: the proposed agenda for the meeting is to go through the > “needs consensus” items posted at > https://github.com/w3c/webcomponents/issues?q=is:issue+is:open+label:"needs+consensus". > It sounds like it would be good to resolve pending Shadow DOM issues before > tackling Custom Elements issues. I spent some time organizing these "needs consensus" issues into a category/priority list. Let's try to go in this order (which interleaves SD and CE): ## Definitely needs discussion * [SD] https://github.com/w3c/webcomponents/issues/308: should we use `display: contents` * [CE] https://github.com/w3c/webcomponents/issues/417: caching vs. late binding of lifecycle callbacks ## Discussion would be good; still contentious/tricky * [SD] https://github.com/w3c/webcomponents/issues/477: `document.currentScript` censoring * [SD] https://github.com/w3c/webcomponents/issues/355: use CSS containment features by default * [CE] https://github.com/w3c/webcomponents/issues/186: integrating callback invocation with IDL and editing operations ## New feature proposals * [CE] https://github.com/w3c/webcomponents/issues/468: provide a mechanism for adding default/"UA" styles to a custom element * [SD] https://github.com/w3c/webcomponents/issues/288: `slotchange` event ## Discussion would be good, but there's likely a default consensus based on GitHub discussions so far * [SD] https://github.com/w3c/webcomponents/issues/59: parse `<slot>` like `<template>` * [Both] https://github.com/w3c/webcomponents/issues/449: restrict to secure contexts * [CE] https://github.com/w3c/webcomponents/issues/474: define order for attributeChangedCallback invocations ## Bikeshedding; probably does not need telecom time * [SD] https://github.com/w3c/webcomponents/issues/451: rename getAssignedNodes and assignedSlot * [CE] https://github.com/w3c/webcomponents/issues/434: rename "custom tag" and "type extension" See you all in a few!