[mediacapture-main] Confusingly redundant prose in § 4.3.1 Life-cycle and Media Flow (#994)

jan-ivar has just created a new issue for https://github.com/w3c/mediacapture-main:

== Confusingly redundant prose in § 4.3.1 Life-cycle and Media Flow  ==
The section [§ 4.3.1 Life-cycle and Media Flow](https://w3c.github.io/mediacapture-main/#life-cycle-and-media-flow) has two subsections:
- [§ 4.3.1.1 Life-cycle](https://w3c.github.io/mediacapture-main/#life-cycle), which one might expect to cover `readyState` and the `ended` event
- [§ 4.3.1.2 Media Flow](https://w3c.github.io/mediacapture-main/#life-cycle), which one might expect to cover the `muted` and `enabled` states and events

Unfortunately, [§ 4.3.1.1 Life-cycle](https://w3c.github.io/mediacapture-main/#life-cycle) jumps the gun, describing fundamental aspects of `muted` and `enabled`, like _"A muted or disabled [MediaStreamTrack](https://w3c.github.io/mediacapture-main/#dom-mediastreamtrack) renders either silence (audio), black frames (video), or a zero-information-content equivalent."_ ahead of the section that defines it.

As one measure, there are 20 hits for "muted" in [§ 4.3.1.1 Life-cycle](https://w3c.github.io/mediacapture-main/#life-cycle) vs 17 hits in [§ 4.3.1.2 Media Flow](https://w3c.github.io/mediacapture-main/#life-cycle).

To be fair, there's *one camera and microphone-specific* lifecycle-aspect to muted/disabled, which is that UAs MAY temporarily relinquish devices (Firefox does this on some platforms). This is probably how the muted/disabled concept snuck into the lifecycle section. But this was meant to be an implementation optimization not meant to disturb the API model, so it may be better to discuss it in 4.3.1.2.

This might be good to clean up.

Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/994 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 15 April 2024 17:55:45 UTC