这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@JensenPaul
Copy link
Contributor

@JensenPaul JensenPaul commented May 21, 2024

Addresses #160


Preview | Diff

@qingxinwu
Copy link

LGTM

@gtanzer
Copy link
Collaborator

gtanzer commented May 28, 2024

LGTM % fyi

@domfarolino
Copy link
Collaborator

I saw this in my inbox but I noticed I was not added as a reviewer. Should I take a look? Feel free to add me as a reviewer and I will take a look after I'm back from vacation.

@domfarolino domfarolino self-requested a review June 3, 2024 14:58
Copy link
Collaborator

@domfarolino domfarolino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty much lgtm; nothing major here.

JensenPaul and others added 4 commits June 4, 2024 12:11
Co-authored-by: Dominic Farolino <domfarolino@gmail.com>
Co-authored-by: Dominic Farolino <domfarolino@gmail.com>
Co-authored-by: Dominic Farolino <domfarolino@gmail.com>
Copy link
Collaborator

@domfarolino domfarolino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Btw what is the motivation to include this API in this spec, instead of the PA spec? Impl-wise, it looks like it was included closer to the PA stuff: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/ad_auction/navigator_auction.idl;l=41;drc=ac83a5a2d3c04763d86ce16d92f3904cc9566d3a;bpv=1;bpt=0

spec.bs Outdated

1. Otherwise, set |urn| to |urnOrConfig|'s [=fencedframeconfig/urn=].

1. If |urn| is <span class=XXX>TODO invalid</span>, then [=exception/throw=] a {{TypeError}}.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#161 (comment) got marked outdated, so I guess I'll re-file this comment as a stand-in for it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I proposed some new words here, WDYT?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that sounds right? Although it would be inelegant to have to write that i.e., each time we reference the concept of an invalid URN. But I suppose this is an incremental improvement so that's fine.

@JensenPaul
Copy link
Contributor Author

Btw what is the motivation to include this API in this spec, instead of the PA spec? Impl-wise, it looks like it was included closer to the PA stuff: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/ad_auction/navigator_auction.idl;l=41;drc=ac83a5a2d3c04763d86ce16d92f3904cc9566d3a;bpv=1;bpt=0

I feel like stuff that only relates to URNs, like deprecatedURNtoURL(), should be in the FF spec, like deprecatedReplaceInURN() already is. The use of URNs (and then FFConfig) seems tied to seeding FFs, and could be used by specs other than PA.

@domfarolino
Copy link
Collaborator

Ah darn it looks there are conflicts now that the other PR merged. Would you be able to sort them out please?

@JensenPaul
Copy link
Contributor Author

Ah darn it looks there are conflicts now that the other PR merged. Would you be able to sort them out please?

I fixed the merge conflict. Now it looks like the build is failing on an unrelated line:
LINE 1724: Couldn't find WPT test 'fenced-frame/fence-report-event-cross-origin.https.html' - did you misspell something?
Looks related to https://chromium-review.googlesource.com/c/chromium/src/+/5544804
So I updated the WPT file name.

spec.bs Outdated

1. Otherwise, set |urn| to |urnOrConfig|'s [=fencedframeconfig/urn=].

1. If |urn| is <span class=XXX>TODO invalid</span>, then [=exception/throw=] a {{TypeError}}.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that sounds right? Although it would be inelegant to have to write that i.e., each time we reference the concept of an invalid URN. But I suppose this is an incremental improvement so that's fine.

Copy link
Collaborator

@domfarolino domfarolino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Meant to "approve" with nits, whoops)

JensenPaul and others added 2 commits June 6, 2024 09:31
Co-authored-by: Dominic Farolino <domfarolino@gmail.com>
@domfarolino domfarolino merged commit 09f6c66 into WICG:master Jun 6, 2024
github-actions bot added a commit that referenced this pull request Jun 6, 2024
SHA: 09f6c66
Reason: push, by domfarolino

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants