Origin API

[mikewest]

Specification

whatwg/html#11846

Description

The Origin interface represents origins, in much the same way that the URL interface represents urls.

Documentation

https://mikewest.github.io/origin-api/

Browser support

Implementation bugs:

• Chromium: https://issues.chromium.org/issues/434131026
• Gecko: https://bugzilla.mozilla.org/show_bug.cgi?id=2001139
• WebKit: https://bugs.webkit.org/show_bug.cgi?id=302785

[ddbeck]

Thanks for filing this issue, @mikewest. I copied the list of implementation bugs from the WHATWG PR into the issue description. (Psst, you might want to fix the misnaming on your comment in the Gecko bug, if possible.)

This seems to have some implementation activity on Chrome and is slated for 144 according to https://chromestatus.com/feature/5095541277065216. This isn't shipping yet, so I labeled this as "early features" but only just.

If I'm reading the proposal correctly, it looks like the relevant IDL for identifying future browser compat data (BCD) keys would be:

[Exposed=*]
interface Origin {
  constructor();
  static Origin from(any value);
  readonly attribute boolean opaque;
  boolean isSameOrigin(Origin other);
  boolean isSameSite(Origin other);
};

(If you expect any changes to that, I'd appreciate a comment here.)

That would translate to BCD keys as:

• api.Origin
• api.Origin.Origin
• api.Origin.from_static
• api.Origin.opaque
• api.Origin.isSameOrigin
• api.Origin.isSameSite