[webrtc-pc] https://w3c.github.io/webrtc-pc/#dfn-final-steps-to-create-an-offer is unclear (#3095)

youennf has just created a new issue for https://github.com/w3c/webrtc-pc:

== https://w3c.github.io/webrtc-pc/#dfn-final-steps-to-create-an-offer is unclear ==
As can be seen in https://wpt.fyi/results/webrtc/RTCPeerConnection-createOffer.html, one test expects that, if a web site adds a track synchronously after calling createOffer, the offer should include the corresponding m-section.
The assumption is that the following steps mandates that behavior:
```
If connection was modified in such a way that additional inspection of the [offerer's system state](https://w3c.github.io/webrtc-pc/#dfn-offerer-s-system-state) is necessary, then [in parallel](https://html.spec.whatwg.org/multipage/infrastructure.html#in-parallel) begin the [in-parallel steps to create an offer](https://w3c.github.io/webrtc-pc/#dfn-in-parallel-steps-to-create-an-offer) again, given connection and p, and abort these steps.
```

The above text is quite handwavy, it is unclear what additional inspection is necessary means.
It seems the following could be done:
1. Remove that text altogether, which I think would align with Chrome and Safari
2. Align the spec to what seems to be implemented in Firefox (basically, createOffer will always start asynchronously).
3.  Update this text to describe what necessary means (modifying the transceiver's list or transceiver's direction?)

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3095 using your GitHub account


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

Received on Friday, 6 March 2026 15:03:13 UTC