-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Impl nit] IDL string fields related to size declarations should be DOMString rather than USVString #1250
Comments
I believe that would be a mistake. Note that we have no good way of sending DOMString fields to devtools, and we would like to send accurate information to devtools about interest groups people join. |
|
Hmm, I have to imagine there are plenty of APIs and web platform features that allow DevTools introspection, but that use DOMStrings under the hood. What do those APIs do? Or can you point to the mechanism that only allows USVStrings to be passed to developer tools? |
We are sending a JSON object to devtools to represent complex stuff like this. Which means if it's got invalid utf-8, we check-fail. |
Also worth noting that interest groups can be updated by a URL, that's specced to contain a JSON response body. Seems like it would be a bit awkward if you could set invalid utf-8 values via JS, but not via the update API. |
Regarding this issue, the last I remember was discussing this with @JensenPaul and resolving to ask around in the Chromium community about the |
The following string fields related to size declarations in the joinAdInterestGroup API surface should be DOMStrings rather than USVStrings, because there is no specific reason for them to be USVStrings (they will not appear in a UI).
sizeGroup
inAuctionAd
https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/ad_auction/auction_ad.idl
width
andheight
inAuctionAdInterestGroupSize
https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/ad_auction/auction_ad_interest_group.idl;l=15
The text was updated successfully, but these errors were encountered: