Upcoming HTML standard issue triage meeting on 1/13/2022

[past]

Yesterday we held our monthly triage call (#7299) and I will post the meeting notes there in a bit. The next one is scheduled for January 13th, 9 am PST. People interested in attending the next call please respond here or reach out privately to me or the spec editors. We will be tagging issues for the next call again using the agenda+ label and we would like to invite anyone that can contribute to said issues to join us.

[past]

Note that this is a week later than usual to avoid interfering with anyone's New Year holiday plans.

[Kaleidea]

I'm interested in the next and there are some carryover questions.

[past]

The same scheduling conflict that we had last time is occurring again, but I am told it's for the last time. I plan to move this meeting an hour later again to accommodate the several folks who need to be in both meetings, unless a large number of people tell me otherwise.

[domenic]

Let's add whatwg/dom#849 (comment) from whatwg/dom to the agenda, if we have room. (Not really high priority.)

[past]

I'm interested in the next and there are some carryover questions.

I have added you to the invite.

[past]

Thanks everyone for attending! Here are the notes from this meeting (next one is at #7488):

Agenda

1. Review past action items
   1. Mason will add a use counter for the <object> without "data" attribute issue. Tess will provide feedback in the thread.
      1. Mason commented. Will revisit when the new use counter provides more accurate data.
   2. Domenic to update the spec for the :active pseudo-class specification doesn't account for children/labels of disabled form elements issue.
      1. Domenic discovered another issue. Spec PR is up, new tests need to be written from Chrome folks.
   3. Eric will be discussing with Elika the validity of the current Directionality in Shadow DOM proposal. We will ask for volunteers afterwards.
      1. Eric proposed spec text. PR is under review. Anne reviewing, it would be good if someone more experienced with the layout parts could review.
   4. Tess will add a proposal to the <input type=password> should provide UI to show/hide its value thread.
      1. Tess commented. Will revisit next time.
   5. Mason and Anne will collaborate on a spec for Selection APIs for Shadow DOM.
      1. Planned for early to mid 2022.
   6. Domenic will add a comment expanding on the re-ordering requirement for Adding scriptElement.exports for configuration use cases. More feedback from everyone is welcome.
      1. Some discussion occurred. Will continue discussing on the thread.
   7. Xiaocheng will start speccing and summarize the current status of Feature proposal: blocking="render" attribute on <link> and <script> in the thread.
      1. Xiaocheng has a spec draft.
   8. Domenic to investigate compat impact of removing the fallback behavior in <object> element can tell whether child document loaded or not, since removing error events without removing fallback behavior is not actually a security win.
      1. Domenic added a use counter, we will revisit it in a few months.
2. Carryovers from last time
   1. [Domenic] popstate/hashchange dispatching doesn't match what browsers do
      1. Olli & Anne will send Domenic more info.
   2. [Domenic] Add the <search> element
      1. A few open questions still, discussion will continue on the thread. Henri will think a bit more about the parser implications.
   3. [Dominic F] Images refetching upon insertion if <base> URL changes
      1. Will revisit when Dom is back.
3. [Henri] Use the real tokenizer and tree builder for meta scan
   1. Mason is supportive and will review and comment in the thread.
4. [Anne+Henri] Add a legacy encoding for Azeri
   1. Mason is waiting to hear back.
5. [Anne] XML MIME types used for documents are not interoperable
   1. Didn't have time for this.
6. [Mason] Should 'true' count as truthy in parsing windowFeatures booleans?
   1. Didn't have time for this.
7. [Domenic] Valid/Invalid characters in document.createElement()
   1. Didn't have time for this.
8. [saschanaz] Mouse events & disabled form controls
   1. Didn't have time for this.
9. [Anne] Meta: Notice: Moving PR6478 to W3C Extension Specification
   1. Didn't have time for this.
10. [Domenic] :active pseudo-class specification doesn't account for children/labels of disabled form elements
    1. Didn't have time for this.
11. [Domenic] Add ability to query UserActivation state
    1. Didn't have time for this.

Action Items

1. @smaug---- & @annevk will send @domenic more info on popstate/hashchange dispatching doesn't match what browsers do.
2. @hsivonen will think a bit more about the parser implications from adding the <search> element.
3. @mfreed7 will review and comment on the Use the real tokenizer and tree builder for meta scan thread.
4. @mfreed7 to solicit feedback for adding a legacy encoding for Azeri.