On 12/2/14, 8:17 AM, Kevin Grandon wrote:
We currently use location.origin quite frequently in gaia, and we also use it
in workers.
So the difference between location.origin and document.origin is that
the latter is the origin of the document and the former is the origin of
the document's UR
On 2014-12-01 10:22 PM, Karl Tomlinson wrote:
On Fri, 28 Nov 2014 00:46:07 -0800, L. David Baron wrote:
On Friday 2014-11-28 10:12 +0900, Mike Hommey wrote:
The downside from doing so, though, is that non-unified build *will*
be broken, and code "purity" (right includes in the right sources,
mo
We currently use location.origin quite frequently in gaia, and we also use it
in workers. My vote would be to keep it around, especially if we have no way of
getting document.origin from a worker.
The naming is a bit confusing to me as a web developer. Not sure if it's
possible, but at first gl
On 11/27/2014 9:28 PM, Ehsan Akhgari wrote:
Another point in favor of dropping support for non-unified builds is
that it frees up some infrastructure resources that is currently used to
test those builds, and also makes the builds in some configurations
where we build non-unified by default (such
On Tue, 2 Dec 2014, at 02:09, Boris Zbarsky wrote:
> Summary: document.origin returns the Unicode serialization of the
> document's origin. The returned value does not depend on what
> document.domain was set to.
>
> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=931884
>
> Spec: http://dom
5 matches
Mail list logo
