Skip to content
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

update window.browser spec per #532 #546

Merged
merged 7 commits into from
Nov 7, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update specification/window.browser.bs
Co-authored-by: Rob Wu <rob@robwu.nl>
patrickkettner and Rob--W authored Mar 7, 2024
commit a154385c720a4f20bcf183456f6cfddeaae099a6
9 changes: 5 additions & 4 deletions specification/window.browser.bs
Original file line number Diff line number Diff line change
@@ -57,10 +57,11 @@ spec: html; urlPrefix: https://html.spec.whatwg.org/multipage/
<code>chrome</code> as a global identifier for WebExtension related methods,
a UA MAY define a global <code>chrome</code> object that includes all
properties of {{browser}}.
{{browser}} and <code>chrome</code> SHOULD NOT be direct aliases. Instead,
individual subproperties SHOULD be alaised. Any modification of a property
of {{browser}} SHOULD be reflected on the same subproperty of <code>chrome</code>,
and vice versa.
{{browser}} and <code>chrome</code> MAY be direct aliases of each other.
When {{browser}} and <code>chrome</code> are distinct objects, each initial
property of {{browser}} SHOULD be defined on the <code>chrome</code> object,
and each property descriptor on the <code>chrome</code> object SHOULD return
the same value as the corresponding property on the {{browser}} object.

<div class="example" id="example-1">
Here's an example of the expected alias behavior