Skip to content

Remove oneRealm arg from set_permission#37152

Merged
gsnedders merged 1 commit intomasterfrom
oneRealm
Dec 2, 2022
Merged

Remove oneRealm arg from set_permission#37152
gsnedders merged 1 commit intomasterfrom
oneRealm

Conversation

@marcoscaceres
Copy link
Copy Markdown
Contributor

The use of realm and "oneRealm" are being removed from the Permission spec.
w3c/permissions#397

And related discussion:
w3c/permissions#387

Copy link
Copy Markdown
Contributor

@reillyeon reillyeon left a comment

Choose a reason for hiding this comment

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

Test changes that I would probably be considered an owner of look good to me. Didn't look at any of the automation infrastructure changes.

Copy link
Copy Markdown
Member

@rakuco rakuco left a comment

Choose a reason for hiding this comment

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

lgtm

The Chromium failure in the checks looks unrelated; I'd try pushing again to see if it goes away, otherwise someone with enough power will have to force-merge this PR.

@marcoscaceres
Copy link
Copy Markdown
Contributor Author

@rakuco indeed.

@jgraham maybe you can override it?

@reillyeon, as spec editor, any chance you could check if idle-detection/idle-detection-allowed-by-permissions-policy.https.sub.html is indeed flaky? It does to a lot of cross origin stuff, so it certainly has the potential to be flaky.

Copy link
Copy Markdown
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

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

I missed this was already being reviewed by @rakuco. Anyway, couple small drive-by nits.

@@ -1,17 +1,23 @@
<!DOCTYPE html>
<meta charset="utf-8">
<meta charset="utf-8" />
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This seems unrelated?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

No, ran prettier over it… it adds the “ />” garbage.

await test_driver.set_permission(descriptor, "denied");
permission = await navigator.permissions.query(descriptor);
assert_equals(permission.state, "denied");
}, "Deny Permission");
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should we really be changing this entire test as part of this?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

In this case, yes. It doesn’t do any harm to test that setting the permission worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants