Since Firefox 27 (bug 8950470), SpiderMonkey's jschar has been a typedef
for char16_t, a new C++11 type distinct from uint16_t.
With bug 1063962, SpiderMonkey's jschar typedef is gone. SpiderMonkey,
its JSAPI, and Gecko now use char16_t directly.
C++ code (outside mozilla-central) compiling a
On 08/09/14 17:10, Daniel Veditz wrote:
It wouldn't be every API call, it'd be the first API call. Would it help
to have an option to remember for the session (rather than
per-document)? We have no guarantee that the foo.com you connect to
tomorrow is the same foo.com you trusted today, especiall
On 9/8/2014 2:16 AM, Mounir Lamouri wrote:
> On Sun, 7 Sep 2014, at 04:56, Martin Thomson wrote:
>> It's more the case that a persistent positive grant from permission
>> manager would be ignored for non-secure origins and non-secure origins
>> would not show any option to persist.
>
> I don't kno
Hi Everyone!
Marionette now has it's own mailing list[1] that allows us to be able to
send a message to one place that is open for anyone to send to.
We can use it to discuss changes that are happening in the WebDriver
spec, breaking changes we want to do and for releases. Please join the
li
On 2014-09-08, 6:47 AM, Aryeh Gregor wrote:
On Sun, Sep 7, 2014 at 5:49 PM, James Graham wrote:
Well, it would also make sense to have interop for editing of course :)
Not a single major browser has significant resources invested in
working on their editing code. Until that changes, nothing
Den 08-09-2014 kl. 18:58 skrev Martin Thomson:
On 07/09/14 07:09, Jesper Kristensen wrote:
Cookies are segregated by http vs https, right?
No, unfortunately they are not. Numerous attempts at fixing it has been
rejected by browser vendors. For example
http://tools.ietf.org/html/draft-abarth-ca
On 08/09/14 10:08, Anne van Kesteren wrote:
>That's been the question people have asked, and I think that the answer was
>that we don't want to break test pages and that sort of thing unnecessarily.
Whoa, that definitely seems like the wrong way to prioritize things.
Tests or demos should not in
On Mon, Sep 8, 2014 at 7:00 PM, Martin Thomson wrote:
> On 08/09/14 04:05, Henri Sivonen wrote:
>> Considering that the remedy would be migrating the app to an
>> authenticated origin, how useful is it to have gUM available (without
>> persistent permissions) for unauthenticated origins?
>
> That'
On 08/09/14 04:05, Henri Sivonen wrote:
Considering that the remedy would be migrating the app to an
authenticated origin, how useful is it to have gUM available (without
persistent permissions) for unauthenticated origins?
That's been the question people have asked, and I think that the answer
On 07/09/14 07:09, Jesper Kristensen wrote:
Cookies are segregated by http vs https, right?
No, unfortunately they are not. Numerous attempts at fixing it has been
rejected by browser vendors. For example
http://tools.ietf.org/html/draft-abarth-cake-01
They are, somewhat.
All cookies are ava
dictionary AvailableChangeEventInit : EventInit {
boolean available;
This needs a default value.
interface SocketChannelWithATwist { // temporary name
Should this inherit from EventTarget? Seems like it, given the
EventHandler attributes it has. Or does it not trigger those via
dispat
Hi Kilik,
Please note that the intent emails should be sent to dev-platform in
order to reach a wider audience. I'm leaving the full context below for
the benefit of the readers of that mailing list.
The proposal looks sane overall. I have one question though, is the
implementation going t
On Sun, Sep 7, 2014 at 11:45 PM, Henri Sivonen wrote:
> On Fri, Sep 5, 2014 at 4:15 PM, Eric Rescorla wrote:
> >
> >
> >
> > On Fri, Sep 5, 2014 at 3:34 AM, Henri Sivonen
> wrote:
> >>
> >> On Fri, Sep 5, 2014 at 1:25 PM, Robert O'Callahan >
> >> wrote:
> >> > On Fri, Sep 5, 2014 at 10:19 PM,
Nice work - this is really interesting. I’ve given it a quick copy edit, to fix
a few typos and iron out a few bits of slightly ambiguous prose.
Chris
On 8 Sep 2014, at 15:15, Lars Knudsen wrote:
> looks good,
>
> maybe adding to always take a holistic view on what you are doing and how
> it
looks good,
maybe adding to always take a holistic view on what you are doing and how
it will interact with other specs/standards used in the same apps (e.g.
considering DeviceOrientation and DeviceMotion before makeing
OrientationLock ;))
br
Lars
On Mon, Sep 8, 2014 at 3:52 PM, Andrew Overholt
A few of us have written some tips and suggestions to make standardizing
web APIs easier. They're mostly intended for Mozillians and are most
useful for those doing this for the first time. If you have
suggestions, please let me know.
https://wiki.mozilla.org/WebAPI/DesignGuidelines
On Mon, Sep 8, 2014 at 12:16 PM, Mounir Lamouri wrote:
> On Sun, 7 Sep 2014, at 04:56, Martin Thomson wrote:
>> It's more the case that a persistent positive grant from permission
>> manager would be ignored for non-secure origins and non-secure origins
>> would not show any option to persist.
>
>
On Sun, Sep 7, 2014 at 5:49 PM, James Graham wrote:
> Well, it would also make sense to have interop for editing of course :)
Not a single major browser has significant resources invested in
working on their editing code. Until that changes, nothing much is
going to happen.
> I would certainly
On Sun, 7 Sep 2014, at 04:56, Martin Thomson wrote:
> It's more the case that a persistent positive grant from permission
> manager would be ignored for non-secure origins and non-secure origins
> would not show any option to persist.
I don't know the specifics about the UI, but you don't want to
19 matches
Mail list logo
