I should get off my butt and do the same in Chrome (and also get rid of `document.origin`?).https://twitter.com/wanderview/status/831509296689070080 …
-
-
Replying to @mikewest
@wanderview what's the benefit of this vs self.location.origin?1 reply 0 retweets 0 likes -
Replying to @jaffathecake
: Sandboxed documents have an opaque origin, while their URL probably doesn't.
@wanderview1 reply 0 retweets 2 likes -
Replying to @mikewest
: Also, other weird cases, like `srcdoc` documents have a location of `about:srcdoc`.
@wanderview1 reply 0 retweets 1 like -
Replying to @mikewest
I would also love a origin compare function: see all the bugs with people trying to do regexes for this
@bz_moz@jaffathecake3 replies 0 retweets 0 likes -
Other than equality, what else do people want to compare? Equality should just be string equality.
1 reply 0 retweets 0 likes -
Replying to @really_bz @bz_moz
matches * dot Mozilla dot org or * dot Dev dot Mozilla dot org with arbitrary port and https, e.g.
@mikewest@jaffathecake1 reply 0 retweets 0 likes -
Ah. The sort of operations you're not really supposed to do on an origin... ;)
1 reply 0 retweets 5 likes -
Replying to @really_bz
: Sure. But the kinds of things developers want to do anyway, and generally shoot themselves in the foot doing.
@frgx@jaffathecake2 replies 0 retweets 1 like
Sure, I was being tongue-in-cheek. I agree that API for doing this right, including eTLD bits, would be good.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.