Description
According to https://github.com/WICG/turtledove/blob/main/FLEDGE.md#23-scoring-bids, browserSignals in scoreAd should contain the following:
'renderSize': {width: 100, height: 200}, /* if specified in the bid */
However, when looking at the spec, https://wicg.github.io/turtledove/#structures, ScoringBrowserSignals doesn't seems to have any mention of the width and height from the AdRender object (cf. https://wicg.github.io/turtledove/#convert-an-ad-render):
dictionary ScoringBrowserSignals {
required [DOMString](https://webidl.spec.whatwg.org/#idl-DOMString) topWindowHostname;
required [USVString](https://webidl.spec.whatwg.org/#idl-USVString) interestGroupOwner;
required [USVString](https://webidl.spec.whatwg.org/#idl-USVString) renderURL;
required [unsigned long](https://webidl.spec.whatwg.org/#idl-unsigned-long) biddingDurationMsec;
required [DOMString](https://webidl.spec.whatwg.org/#idl-DOMString) bidCurrency;
[unsigned long](https://webidl.spec.whatwg.org/#idl-unsigned-long) dataVersion;
[sequence](https://webidl.spec.whatwg.org/#idl-sequence)<[USVString](https://webidl.spec.whatwg.org/#idl-USVString)> adComponents;
[boolean](https://webidl.spec.whatwg.org/#idl-boolean) forDebuggingOnlyInCooldownOrLockout = false;
};
Using M124, despite bidding with a render object including url, width and height, I'm unable to observe the renderSize in scoreAd's browserSignals -- can you elaborate on when this value should be populated?
(perhaps related -- #970 recently found another gap in the implementation, where the behaviour doesn't match the explainer -- could something similar be happening here)?