#229: DOM

Visit on Github.

Opened Feb 3, 2018

こんにちはTAG!

I'm requesting a TAG review of:

Further details (optional):

You should also know that...

The current DOM 4.1 revision is produced by W3C, with the primary aim of documenting what is interoperably implemented and is, or is likely to become, a core part of the Web Platform. An important secondary goal is to minimise incompatibility with the ongoing work at WHATWG.

We'd prefer the TAG provide feedback as (please select one):

  • open issues in our Github repo for each point of feedback
  • open a single issue in our Github repo for the entire review
  • leave review feedback as a comment in this issue

Discussions

2018-03-20

Minutes

Dan: There is a change log here, so we can start from this. Would like to have a breakout on this. The question is what technical feedback we have.

Dan: Maybe we should have some people do a first pass on this.

Sangwhan: I can volunteer.

Travis: Likewise.

ACTION: Travis and Sangwhan to take a first pass review, possibly revisit during F2F.

2018-03-27

Minutes

Travis: Haven't started anything yet.

Sangwhan: Nor I.

Travis: Punt this down the road a bit.

Peter: Face-to-face, or later?

Travis: I'm thinking after.

Sangwhan: Given the backlog, yeah, I don't think we'll have time during the face-to-face.

Alex: Can we do a triage? Can we figure out what areas deserve attention so we can chew on a smaller piece when we get there. I expect a lot of overlap between people for HTML and DOM reviews. (??)So punt to later if we can't figure out how to split up?(??)

Travis: OK, (?) will do a triage and see if there's anything we want to split out and bite off during the face-to-face.

2018-09-04

Minutes

Hadley: we agreed we would review the whatwg spec.

hhK: there is a wide review tracker for dom4.1 - the w3c one. Missing the TAG feedback.

Hadley: we've explicitly said we won't be giving any.

Kenneth: so what are we doing?

Peter: wide review period ended march 12.

Peter: we should still do our review of the whatwg sP Ppec.

Sangwhan: we schedkued it during the f2f but didn't find time. I will try to get a hold of travis after this call and we can do a separate call.

Peter: reset milestone...

akeDavid: I expect a bunch of whatwg folks to be there.

Peter: we'llc heck u next week

2018-09-25

Minutes

Travis: The goal is to get this closed out today, we spend some time on this last week... thumbs up to our co-chair. I dropped in a polished comment into the issue. There we not a lot of significant feedback, mostly nits.

Lots of historical things are specced in the dom and new things, all mixed together. Would be nice to make it more clear what is old and new. No explainer like text. It sure would have been nice with a bit of intros. Sangwhan was confused about about a few things like Processing Instructions and you wont find out by reading the DOM spec.

Some questions about composed events - what is it and why is it useful

References to mailing lists that might have gone

General feedback about abort controller vs TC39 proposal - is that over?

Alex: They chose not to do anything with Cancellable Promises but they didnt seem to care around that time, so people went ahead.

Alex: I think that there is still going to be work in TC39 around cancellable promises

Alex: Is cancellable an advice or an actual cancellation. TC39 is constrained in what they can do now due to fetch cancellation and they will probably have to come to us for advice on what to do.

Travis: We wondered whether mutation events should be written down and spec'ed. Wording around TreeWalker. Is anyone using that

Kenneth: Yes, lit-html for instance: https://github.com/Polymer/lit-html/blob/14f7e67b1a325946030aff031d4518c4a9e54ff2/src/lib/template.ts#L53

Travis: It is interesting, I just wondered whether its time had come and gone

Dan: Shall we close this off?

Travis: I think that is fine... take it or leave it feedback

Dan: Close it off! Great