The question is what is best: ignored warnings or ignored intermittent
oranges? I assume that the latter have the best chance of being
eventually fixed, but I'm not sure.
On 05/06/15 18:17, Ryan VanderMeulen wrote:
> Uncaught Promise rejections were made fatal and for the most part go
> ignored wh
I also found in pure html window, there is no way to add support for
context menu.
And also popup.
2015-06-08 12:17 GMT+08:00 Paul Rouget :
> B2G on desktop only uses HTML. OS integration is poor, but we are working on
> it.
> See the larch branch (https://hg.mozilla.org/projects/larch).
> We are
Right. Not supported yet.
On Mon, Jun 8, 2015 at 11:13 AM, 罗勇刚(Yonggang Luo)
wrote:
> I also found in pure html window, there is no way to add support for
> context menu.
> And also popup.
>
> 2015-06-08 12:17 GMT+08:00 Paul Rouget :
>> B2G on desktop only uses HTML. OS integration is poor, but w
If I have an about page marked URI_SAFE_FOR_UNTRUSTED_CONTENT, it
happily loads css/js from chrome://browser (in fact, about:home does
this), but throws a security error loading from chrome://foo. Is this
intentional? Should I be filing a bug somewhere?
GL
On Friday, 5 June 2015 20:42:29 UTC+5:30, Kyle Huey wrote:
> You need to look further up the stack. jemalloc_crash is not an
> interesting stack frame.
>
> - Kyle
>
> On Fri, Jun 5, 2015 at 8:05 AM, Meenakshi Shankar
> wrote:
>
> > Hi,
> >
> > We are using Firefox SDKS for our FF extension (l
On Wednesday, 3 June 2015 16:40:31 UTC+5:30, Meenakshi Shankar wrote:
> On Tuesday, 2 June 2015 14:36:48 UTC+5:30, Meenakshi Shankar wrote:
> > On Tuesday, 2 June 2015 02:17:09 UTC+5:30, Mike Hommey wrote:
> > > On Mon, Jun 01, 2015 at 12:51:23PM -0700, Meenakshi Shankar wrote:
> > > > On Thursd
On Thursday, June 4, 2015 at 6:15:35 PM UTC-4, Chris AtLee wrote:
> Very interesting, thank you!
>
> Would there be a way to add an environment variable or harness flag to run
> all tests in chaos mode?
>
There isn't at the moment but one can definitely be added if there is a use for
it. At the
On Thursday, June 4, 2015 at 5:30:32 PM UTC-4, Chris Peterson wrote:
>
> Will chaos mode enabled tests run on Try and release branches?
If a test has chaos mode enabled, then it will have chaos mode enabled on all
branches, including Try and release branches.
> We don't know if chaos mode test
From: Firefox-qe [mailto:firefox-qe-boun...@mozilla.org] On Behalf Of Florin
Mezei
Sent: Monday, June 08, 2015 5:01 PM
To: firefox...@mozilla.org; dev-platf...@mozilla.org;
firefox-...@mozilla.org
Cc: 'Lawrence Mandel'
Subject: [Firefox Desktop] Issues found: June 1st to June 5th
Hi every
On 6/8/15 6:57 AM, Geoff Lankow wrote:
If I have an about page marked URI_SAFE_FOR_UNTRUSTED_CONTENT, it
happily loads css/js from chrome://browser (in fact, about:home does
this), but throws a security error loading from chrome://foo. Is this
intentional?
Whether untrusted content can load CSS
To specifically answer Geoff's question - the difference you're seeing
between JS/CSS and docshell loads is that the former end up with the
principal of the loader, whereas docshell loads end up with the principal
of the loadee. Allowing content to load a chrome-privileged window is super
dangerous
Hi,
On 2015/06/06 2:39, Eric Rahm wrote:
On Friday, June 5, 2015 at 8:23:53 AM UTC-7, ISHIKAWA,chiaki wrote:
After coping with voluminous messages in C-C TB |make mozmill| test
suite log [much smaller volume than full FF logs],
I think we should have NS_INFORMATION() macro that
prints out an in
On 2015-06-05 6:08 AM, David Rajchenbach-Teller wrote:
This API covers all the needs I have encountered for warnings so far in
JS code. I don't think it's terribly different in C++ code.
For C++ non-fatal assertions, we already have a mechanism similar to
this (but it doesn't rely on the exact
The Research team will be holding a pair of 3 hour training sessions, with one
on the new web rendering engine, Servo, and one on the new systems language it
is implemented in, Rust. These sessions will have both presentation components
and a large hands-on piece with exercises to do on your lap
Last time I looked at whitelisting non-fatal assertions, there was only
the option to accept up-to a number of assertions. Have I missed
something? Because a blank check to sweep assertions under the carpet is
really an awful mechanism.
Now, I fully agree that warnings that are not whitelisted sho
Does the Servo session (which is earlier than the Rust session) require
prior experience with Rust?
Thanks,
Jim
On 6/8/15 3:44 PM, Lars Bergstrom wrote:
The Research team will be holding a pair of 3 hour training sessions, with one
on the new web rendering engine, Servo, and one on the new s
Ah, perfect. Thanks Boris.
On 09/06/15 03:18, Boris Zbarsky wrote:
On 6/8/15 6:57 AM, Geoff Lankow wrote:
If I have an about page marked URI_SAFE_FOR_UNTRUSTED_CONTENT, it
happily loads css/js from chrome://browser (in fact, about:home does
this), but throws a security error loading from chrome
Jim,
We won’t get into anything that requires prior Rust experience during the Servo
session - the focus is intended to be more on architecture, web platform
compat, and with a bit of poking around to make small changes (e.g., either
fixing or breaking WPT and CSS WG ref tests with tiny code ch
On 6/8/15 4:28 PM, David Rajchenbach-Teller wrote:
Last time I looked at whitelisting non-fatal assertions, there was only
the option to accept up-to a number of assertions.
You can specify an exact number or a range.
But you're right that you can't specify the assertion text involved...
-Bor
19 matches
Mail list logo
