<scribe> scribenick: gregwhitworth

Adjusting time of Telecon to allow for Asia/Australia attendees

<levi> Greg: Mozilla interested in engaging from Australia

<levi> Grep: Proposal, adjust time to Thr afternoon at 3pm PST

<levi> Levi: Works

<levi> Rob: Works

<nicholasrice> Works

RESOLUTION: Move meeting to 3PM on Thursday

https://github.com/WICG/open-ui/issues/83#issuecomment-625988334

dandclark: on the Open UI thread, there is a general notion to allow users to slot arbitrary HTML into select. We wont' allow an iframe into a custom UI of a select. How does that work, do we want to block it from being put on there in the first place but script can still make that happen. If illegal content is there or we can selectively not render banned content
... Mason, Google, pointed out that there is precedence for this now - so that is the direction we're leaning towards now

Rob: What would be the list of items?

gregwhitworth: not currently, but we can do that for each part

levi: have there been other considerations. Is it not possible to throw an error?

dandclark: it may be possible but I can't think of any case where that hasn't been done
... even arbitrary under input, etc won't do that. The parser will block it but not in script

Rob: With Shadow DOM there are certain HTML elements you'll get a DOM exception.
... Consistency is better, so I'd prefer to go along with it

dandclark: one problem is that from perf when I do node changes that I just move pointers I then need to do O<N> operations.

chrisdholt: I agree with not dropping it in the DOM, it is not in the DOM. It would be the largest hint. I agree with consistency

Levi: React will tell you if elements are not allowed

Proposed Resolution: Keeping with precedent and allow script to add DOM elements that are not supported for Render. Recommend tooling to inform the developers that invalid elements were added

Rob: This does seem like something would be valuable in general for slots and it may be worth disallowing elements

RESOLUTION: Keeping with precedent and allow script to add DOM elements that are not supported for Render. Recommend tooling to inform the developers that invalid elements were added

https://github.com/WICG/open-ui/issues/82

dandclark: do we change how focus works within <select> since we hope to allow additional content within a select. Tabindex, select psuedo, etc
... currently this is fine because an option is the only thing that allows a select
... I can call .focus on my select, if we continue to follow the old behavior with options things get weird for other APIs
... what I'm suggesting is break away from the current behavior with options. Should devs have full control over focus on elements that they slot in

chrisdholt: our general principle is that you can do a lot more than in our current model. I would love to remove the "select is special"
... just on the a11y side those special things have made it very difficult so if it can align with the rest of the platform it will help all developers

levi: in the spirit of Open UI, looking at other elements that look similar you'll see APIs to allow for different capabilities so I think the community has shown that there is a need for that and has implemented it

Proposed Resolution: make the <select> similar to the rest of the platform and allow other platform focus APIs to work on descendants of a select

RESOLUTION: make the <select> similar to the rest of the platform and allow other platform focus APIs to work on descendants of a select

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: Greg, Whitworth, Chris, Holt, Rob, Eisenberg, (EisenbergEffect), nicholasrice, Levi, Thomason
Present: Greg Whitworth Chris Holt Rob Eisenberg (EisenbergEffect) nicholasrice Levi Thomason
Found ScribeNick: gregwhitworth
Inferring Scribes: gregwhitworth

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)