Please read our documentation on submitting patches to Firefox:
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch
On Mon, Jul 31, 2017 at 12:28 AM, Enrico Weigelt, metux IT consult <
enrico.weig...@gr13.net> wrote:
> Signed-off-by: Enrico Weigelt, metux IT
Sorry for the slow reply, I was half-waiting to see if anybody else would
jump in but I guess product managers don't follow dev-platform :)
I think we're mostly in sync on most of the nuts and bolts and the
unresolved topics are generally pretty high-level concerns.
On Thu, Jul 27, 2017 at 10:02
Sorry, that was my mistake. Of course preload has a pref:
network.preload
My apologies, I was writing e-mail in a hurry.
The pref was implemented in
https://bugzilla.mozilla.org/show_bug.cgi?id=1222633.
The is turn on by default and we are planning to ship it
turned on.
dragana
On Mon, Jul
Node dependency trees tend to be pretty large, so I'm a little concerned
here. Has the memory footprint be measured?
Cheers,
David
On 31/07/17 19:45, Michael Cooper wrote:
> If you mean using modules from NPM in a browser add-on, the Shield client
> extension recently started doing this <
>
If you mean using modules from NPM in a browser add-on, the Shield client
extension recently started doing this <
https://github.com/mozilla/normandy/tree/master/recipe-client-addon>
We do this by using webpack to process the node modules, bundling the
entire dependency tree of a library into a
This also seems like a feature which some users may want to disable, for
example in order to reduce bandwidth usage on certain websites (I'm not
sure how bad the impact would be bug *shrug*).
I imagine we should add a pref if possible before shipping this feature.
On Mon, Jul 31, 2017 at 1:25
Why is there no preference to control it? I thought that was standard
practice for new features to make it easier to unship them if we
discover a problem that makes it difficult to back out.
Cheers,
Josh
On 7/31/17 1:14 PM, Dragana Damjanovic wrote:
As of Firefox 56, I intent to ship link
As of Firefox 56, I intent to ship link rel=preload. The feature is
developed in bug 1222633 <
https://bugzilla.mozilla.org/show_bug.cgi?id=1222633>. There is no pref for
this feature, so it will be shipped directly.
**Bug to turn on by default**:
On Mon, Jul 31, 2017 at 3:40 AM, Enrico Weigelt, metux IT consult
wrote:
> On 31.07.2017 09:23, Cameron McCormack wrote:
>> Firefox patches should be submitted via Bugzilla, rather than by email
>> to dev-platform. Please see:
>>
>>
On 07/31/2017 01:02 PM, Henri Sivonen wrote:
On Tue, Jul 18, 2017 at 7:01 AM, Jim Blandy wrote:
BTW, speaking of training: Jason's and my book, "Programming Rust" will be
available on paper from O'Reilly on August 29th!
And already available on Safari Books Online
On Mon, Jul 24, 2017 at 6:11 PM, Anne van Kesteren wrote:
> Please consider the request to remove device orientation retracted for
> now. We'll still need to figure out some kind of long term plan for
> that API though. WebVR building on it through libraries that abstract
> away
On Tue, Jul 18, 2017 at 7:01 AM, Jim Blandy wrote:
> BTW, speaking of training: Jason's and my book, "Programming Rust" will be
> available on paper from O'Reilly on August 29th!
And already available on Safari Books Online (access available via
Service Now request subject
If you now see Mac compilation errors about "stdlib.h not found", try
running `xcode-select --install`.
Part of the Stylo build process (rust-bindgen) can get confused about
which clang header #include paths it should use. xcode-select can fix
this. Bug 1366564 is a feature request for mach
On Thu, Jul 20, 2017 at 11:00 PM, wrote:
> Hi everyone, as title, I want to use the C/C++ to research the Gecko-dev html
> parser.
> Is it possible to build the Gecko-dev html parser?
>
>
yes -
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch
covers this.
please read all of the document linked by cameron and this one.
-glob
Enrico Weigelt, metux IT consult wrote:
On 31.07.2017 09:23, Cameron McCormack wrote:
Hi Enrico,
Firefox patches
On 31.07.2017 09:23, Cameron McCormack wrote:
Hi Enrico,
Firefox patches should be submitted via Bugzilla, rather than by email
to dev-platform. Please see:
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction#Step_4_-_Get_your_code_reviewed
Is there a way to submit
Signed-off-by: Enrico Weigelt, metux IT consult
---
gfx/2d/DrawTargetCairo.cpp | 10 --
1 file changed, 10 deletions(-)
diff --git a/gfx/2d/DrawTargetCairo.cpp b/gfx/2d/DrawTargetCairo.cpp
index c0e4f0af2..66e3f8854 100644
--- a/gfx/2d/DrawTargetCairo.cpp
+++
Signed-off-by: Enrico Weigelt, metux IT consult
---
mfbt/Poison.cpp | 34 +-
1 file changed, 1 insertion(+), 33 deletions(-)
diff --git a/mfbt/Poison.cpp b/mfbt/Poison.cpp
index b2767011d..e9981764f 100644
--- a/mfbt/Poison.cpp
+++
Hey Enrico, patches are certainly appreciated, but please attach them
(and corresponding rationale) to bugs instead. This one should
probably go here:
https://bugzilla.mozilla.org/enter_bug.cgi?product=Core=Graphics.
dev-platform has a ton of subscribers and is really only meant for
more
Hi Enrico,
Firefox patches should be submitted via Bugzilla, rather than by email
to dev-platform. Please see:
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction#Step_4_-_Get_your_code_reviewed
Thanks,
Cameron
On Mon, Jul 31, 2017, at 03:14 PM, Enrico Weigelt, metux
startupcache depends on zipwriter.
when enabled, check that zipwriter is also enabled.
Signed-off-by: Enrico Weigelt, metux IT consult
---
old-configure.in | 4
1 file changed, 4 insertions(+)
diff --git a/old-configure.in b/old-configure.in
index
For now, our GfxSurfaceType enum (and things depending on it) is tightly
coupled to cairo_surface_type_t, which is bad for encapsulation. And we're
also tightly coupled to the current, meanwhile pretty old and customized
in-tree version of cairo.
To reduce maintenance burden and as a first step
Hi everyone,
Here's the list of new issues found and filed by the Desktop Release QA
Team last week, *July 24 - July 28* (week 30).
Additional details on the team's priorities last week, as well as the
plans for the current week are available at:
23 matches
Mail list logo