On 6/27/18 7:14 PM, Jonathan Kingston wrote:
Is this feature enabled by default in sandboxed iframes? N/A
It is, yes.
-Boris
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
\o/
On Thu, Jun 28, 2018 at 12:52:51AM +0200, Tom Schuster wrote:
Since landing bug 1465911 [1], CPOWs [2] are only functional on our testing
infrastructure. In normal builds that we ship to users CPOWs can be
created, but no operations like property lookup can be performed on them.
CPOWs
Many JavaScript libraries exist to toggle attributes in the DOM. By moving
this to the web platform we will simplify the boilerplate developers have
to use.
This method will behave similar to Element.classList.toggle, this will
allow developers to pass an argument of the attribute to toggle:
This is awesome - thanks Tom!
On Wed, Jun 27, 2018 at 3:53 PM Tom Schuster wrote:
> Since landing bug 1465911 [1], CPOWs [2] are only functional on our testing
> infrastructure. In normal builds that we ship to users CPOWs can be
> created, but no operations like property lookup can be
Since landing bug 1465911 [1], CPOWs [2] are only functional on our testing
infrastructure. In normal builds that we ship to users CPOWs can be
created, but no operations like property lookup can be performed on them.
CPOWs continue to exist, because a lot of tests still depend on them. We
can't
On Thu, 28 Jun 2018, Martin Thomson wrote:
If we ever have code to support .local in the browser, then those will need
to avoid using the DoH stack for resolving those names.
That is *exactly* what we already have and do! =) Since they're explicitly
local, they're considered "blacklisted" by
On Thu, Jun 28, 2018 at 1:21 AM Benjamin Francis wrote:
> On 25 June 2018 at 16:50, Brannon Dorsey wrote:
>
> > As far as I see it, a
> > domain name should never be allowed to respond with a private IP address
> > moments after it first responded with a public IP address.
> >
>
> If I
On Wed, Jun 27, 2018 at 12:42 PM Simon Sapin wrote:
> On 27/06/18 19:45, Bobby Holley wrote:
> > Hi Adam,
> >
> > At present, I think you should raise your questions with Nathan Froyd and
> > Ehsan Akhgari, who are the owners of the C++/Rust usage module [1].
> >
> > There has been some
On 27/06/18 19:45, Bobby Holley wrote:
Hi Adam,
At present, I think you should raise your questions with Nathan Froyd and
Ehsan Akhgari, who are the owners of the C++/Rust usage module [1].
There has been some discussion around creating a Rust-in-Firefox Advisory
Committee to handle questions
Hi Adam,
At present, I think you should raise your questions with Nathan Froyd and
Ehsan Akhgari, who are the owners of the C++/Rust usage module [1].
There has been some discussion around creating a Rust-in-Firefox Advisory
Committee to handle questions like this, but it hasn't happened yet. In
On 25 June 2018 at 16:50, Brannon Dorsey wrote:
> As far as I see it, a
> domain name should never be allowed to respond with a private IP address
> moments after it first responded with a public IP address.
>
If I understand correctly, this is exactly what we plan to do on our Mozilla
IoT
Hello,
Due to a forecast increase in demand for Event Telemetry, we have (via
bug 1460595) moved Event Telemetry transmission from the "main" ping to
special-purpose "event" pings.
This has a couple of benefits, most notably that they are sent more often
(less latency) and can also send more
12 matches
Mail list logo
