Serial API events: on(dis)connect -> (dis)connect_event

[Elchi3]

Update per new events guideline

Content work needed.

[Elchi3]

@foolip There are two events here but we have 4 entries because the event bubbles from SerialPort to Serial. Is this a scenario where we would want to have 2 entries only?

[foolip]

@Elchi3 bubbling is fairly rare out side of the Node hierarchy, but for consistency I think we should do the same thing for everything that overrides the get the parent algorithm to allow bubbling. In addition to Serial, it happens in https://w3c.github.io/IndexedDB/.

On MDN, perhaps we should also consider pointing to bubbling event for the parent object types, similar to inherited properties and methods.

[Elchi3]

but for consistency I think we should do the same thing for everything that overrides the get the parent algorithm to allow bubbling.

I don't know this algorithm and I understand what this means. Can you elaborate? What is the consequence for BCD?

On MDN, perhaps we should also consider pointing to bubbling event for the parent object types, similar to inherited properties and methods.

Okay. So then we probably want the two events documented under SerialPort? The Serial interface page can then contain pointers to bubbled events from SerialPort?

[foolip]

but for consistency I think we should do the same thing for everything that overrides the get the parent algorithm to allow bubbling.

I don't know this algorithm and I understand what this means. Can you elaborate? What is the consequence for BCD?

It's how the specs express what event targets event bubble through. The kind of bubbling you're familiar with is when an event is fired on an element, and it bubbles first through all of its parent elements, then to the document and finally to the window. That path comes from "get the parent" being defined for the nodes involved here. Bubbling is very uncommon outside of nodes, but one can find those places by looking for "get the parent" in other specs. Serial and IndexedDB is what I found.

On MDN, perhaps we should also consider pointing to bubbling event for the parent object types, similar to inherited properties and methods.

Okay. So then we probably want the two events documented under SerialPort? The Serial interface page can then contain pointers to bubbled events from SerialPort?

Yes, I think that's exactly right.

[foolip]

On MDN, perhaps we should also consider pointing to bubbling event for the parent object types, similar to inherited properties and methods.

Okay. So then we probably want the two events documented under SerialPort? The Serial interface page can then contain pointers to bubbled events from SerialPort?

Yes, I think that's exactly right.

@Elchi3 I'm not sure if we ended up on the same page after all. I see you've left the event entries in Serial.json, and I thought they'd only be left in the MDN page for Serial, not in BCD outside of SerialPort.json.

[Elchi3]

I'm happy to remove them in Serial.json. In fact, that makes more sense to me now, too.

[foolip]

Cool, back on the same page :D