On 2016/12/16 19:53, Mike Hommey wrote:
On Fri, Dec 16, 2016 at 05:16:25PM +0900, Masayuki Nakano wrote:
Hi,
I'm looking for some documents which explain when we need to touch CLOBBER
to avoid build failure. However, I've not found such document yet. I see
such information only in CLOBBER
Oh, do you mean that nobody doesn't have concrete scenarios when
developers need to touch CLOBBER?
When not touching CLOBBER causes build failure at autoland, will it be
fixed by a follow up landing which touches CLOBBER or backed out and
need to reland same patches with touching CLOBBER?
On 2016-12-15 4:46 AM, Masayuki Nakano wrote:
> At investigating selection API behavior, I realized that non-Gecko
> engines don't support multiple selection.
>
> For example, document.getSelection().addRange(somethingNewRange) does
> nothing when the selection has a range.
>
> You can see the
On Fri, Dec 16, 2016 at 12:25 PM, Jason Duell wrote:
> So a switch that toggles the "network is expensive" bit, plus turns off
> browser updates, phishing list fetches, etc?
Windows 10 has such a switch, although I suspect it's up to
applications to opt-in. An API to query
On Fri, Dec 16, 2016 at 11:35 AM, Tantek Çelik
wrote:
>
> Honestly this is starting to sound more and more like a need for a
> "Minimal Network" variant of the "Work Offline" option we have in
> Firefox (which AFAIK no other current browser has), since no amount of
>
On Fri, Dec 16, 2016 at 10:51 AM, Gervase Markham wrote:
> On 15/12/16 14:20, Daniel Stenberg wrote:
>> Looking at that collection of existing user, basically all of them want
>> the user to anser this question:
>>
>> "Use expensive traffic (y/n)"
>
> And this should be an
On 15/12/16 14:20, Daniel Stenberg wrote:
> Looking at that collection of existing user, basically all of them want
> the user to anser this question:
>
> "Use expensive traffic (y/n)"
And this should be an OS-level switch which the browser and other apps
both respect and reflect. Doesn't
On 12/16/16 3:16 AM, Masayuki Nakano wrote:
I see such information only in CLOBBER about WebIDL change.
This is specifically about
https://bugzilla.mozilla.org/show_bug.cgi?id=1103153 or something else?
-Boris
___
dev-platform mailing list
Anyway, thanks for the suggestion, Simon. I filed
https://bugzil.la/1324040 with this fix.
In the meantime, the curl command line from https://rustup.rs/ should
work equivalently.
-r
On Fri, Dec 16, 2016 at 9:40 AM, Ralph Giles wrote:
> On Fri, Dec 16, 2016 at 9:19 AM,
On Fri, Dec 16, 2016 at 9:19 AM, Simon Sapin wrote:
> RUSTUP_URL_BASE = 'https://static-rust-lang-org.s3.amazonaws.com/rustup'
>
> If that fixes the issue for you, it’s likely that your Python version does
> not support SSL SNI.
I can reproduce with python
One of my goal when introducing CLOBBER was to document what was causing us
to CLOBBER so that we could audit and fix them if we ever found the time.
You can get a pretty good idea by going through the history of the file.
I don't believe anyone has taken to time to go through the CLOBBER hg
On 16/12/16 17:27, Ben Kelly wrote:
I tried ./mach bootstrap on a fresh m-c this morning and got:
Will try to install Rust.
Downloading rustup-init... Error running mach:
['bootstrap']
The error occurred in code that was called by the mach command. This is
either
a bug in the called code
On 2016-12-15 6:28 PM, Boris Zbarsky wrote:
> On 12/15/16 6:15 PM, Ehsan Akhgari wrote:
>> (I personally agree with most of what you said, except that I'm
>> convinced that we should expose that one bit.)
>
> Exposing this one bit makes a lot of sense to me.
>
>> From a more practical
I tried ./mach bootstrap on a fresh m-c this morning and got:
Will try to install Rust.
Downloading rustup-init... Error running mach:
['bootstrap']
The error occurred in code that was called by the mach command. This is
either
a bug in the called code itself or in the way that mach is
On 12/16/2016 10:36 AM, Masayuki Nakano wrote:
Due to the end of B2G platform, I'd like to remove mozbrowserbeforekeydown,
mozbrowserbeforekeyup, mozbrowserafterkeydown and mozbrowserafterkeyup
events and its event classes.
They were implemented by bug 989198 [1] for allowing embedded browser
Due to the end of B2G platform, I'd like to remove
mozbrowserbeforekeydown, mozbrowserbeforekeyup, mozbrowserafterkeydown
and mozbrowserafterkeyup events and its event classes.
They were implemented by bug 989198 [1] for allowing embedded browser
elements to override keyboard events [2].
Hi,
I'm looking for some documents which explain when we need to touch
CLOBBER to avoid build failure. However, I've not found such document
yet. I see such information only in CLOBBER about WebIDL change.
So, is there any document which lists up when we need to touch CLOBBER?
--
Masayuki
17 matches
Mail list logo