You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes. The issue here is that we started with renderUrl, but Web Javascript standards use renderURL. So currently, we support both, but we want to get everyone over to using renderURL, and then (eventually) remove renderUrl, probably displaying some sort of warning for quite some time until we finally remove it.
renderUrls
(camel case) is mentioned https://github.com/WICG/turtledove/blob/main/FLEDGE_Key_Value_Server_API.md#examples:https://www.ssp-kv-server.example/v1/getvalues?renderUrls=url1,url2&adComponentRenderUrls=url3,url4
And that's in fact what we see in the network tab for the SSP K/V call:

However, both the explainer and the spec make mention of
renderURLs
-- whereURL
is all-uppercase -- which doesn't match Chrome's behaviour.Can the docs & spec be updated accordingly?
The text was updated successfully, but these errors were encountered: