Skip to content

Remove use of realms#397

Merged
marcoscaceres merged 1 commit intomainfrom
consume
Nov 29, 2022
Merged

Remove use of realms#397
marcoscaceres merged 1 commit intomainfrom
consume

Conversation

@marcoscaceres
Copy link
Copy Markdown
Member

@marcoscaceres marcoscaceres commented Nov 25, 2022

closes #387

The following tasks have been completed:

Implementation commitment:

  • Realm-based permissions is not implemented by any engine.

Preview | Diff

@marcoscaceres
Copy link
Copy Markdown
Member Author

Sent a PR to remove it from WPT web-platform-tests/wpt#37152 ... it might need to go through the RFC process, but not sure yet.

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.

Copy link
Copy Markdown
Member

@johannhof johannhof left a comment

Choose a reason for hiding this comment

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

Thanks!

Comment on lines +320 to +321
The user agent tracks which <a>powerful features</a> the user has [=permission=] to use
via the [=environment settings object=].
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 implies that the user is forbidden from using some features, but it's really the user who grants permission for the environment settings objects (ESOs) to use the features.

I think this change is replacing Realm-scope with origin scope? So it might say:

Suggested change
The user agent tracks which <a>powerful features</a> the user has [=permission=] to use
via the [=environment settings object=].
The user agent tracks which <a>powerful features</a> each [=origin=] has the user's [=permission=] to use....

I don't remember anymore why it's "via the ESO", and an origin tends to have multiple ESOs, so "the" isn't really the right article once things have transitioned to origins.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

right, I think we might need to reframe all this as part of #390 (as that will govern how permissions are associated with origins).

@marcoscaceres marcoscaceres merged commit 91ea715 into main Nov 29, 2022
@marcoscaceres marcoscaceres deleted the consume branch November 29, 2022 04:28
aarongable pushed a commit to chromium/chromium that referenced this pull request Dec 6, 2022
This concept was removed in w3c/permissions#397 and
the shared WPT pieces were already removed in
web-platform-tests/wpt#37152.

Chrome never supported it outside of ignoring the parameter.

Bug: 977612
Change-Id: I69b5838dea5d25ddf9345689bf220d8a9a1bf602
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4079214
Auto-Submit: Johann Hofmann <johannhof@chromium.org>
Commit-Queue: Johann Hofmann <johannhof@chromium.org>
Reviewed-by: Vladimir Nechaev <nechaev@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1079726}
T3-M4 pushed a commit to bayandin/chromedriver that referenced this pull request Dec 7, 2022
This concept was removed in w3c/permissions#397 and
the shared WPT pieces were already removed in
web-platform-tests/wpt#37152.

Chrome never supported it outside of ignoring the parameter.

Bug: 977612
Change-Id: I69b5838dea5d25ddf9345689bf220d8a9a1bf602
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4079214
Auto-Submit: Johann Hofmann <johannhof@chromium.org>
Commit-Queue: Johann Hofmann <johannhof@chromium.org>
Reviewed-by: Vladimir Nechaev <nechaev@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1079726}
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.

Potentially revisit oneRealm

5 participants