Currently, when a fenced frame used for rendering a FLEDGE ad is navigated to a urn:uuid, its content size is frozen based on the <fencedframe> element’s width and height attributes near that time.

We would like to consolidate fenced frame information flow as follows: when a fenced frame is navigated to a urn:uuid, instead of combining information from the urn:uuid mapping and the embedder’s <fencedframe> element attributes, we will get information only from the urn:uuid mapping. Therefore, instead of mapping to a URL, the urn:uuid now maps to a set of attributes which includes a src URL, width, height, etc.

In order to adjust FLEDGE to the fenced frame design changes, the following API changes would be necessary:

• When declaring the FLEDGE auction config, the publisher must specify an ad size for the auction.
• When submitting a container ad bid, the bidder must declare a size for its component ads. (details TBD)