The New checker features look really promising. Yes, more of this stuff in
C++ is very welcome.
On Wed, May 23, 2018 at 1:53 PM, Chris Peterson
wrote:
> On 2018-05-23 1:35 PM, Botond Ballo wrote:
>
>> There is also work being done in this area outside the formal
>> standards process, in the
The continued work on the 2D GFx API as a C++ standard is concerning. Since
we're sending a GFx engineer to the committee, and AFAIK we're not going to
use such an API to build our GFx stack, the arguments against continued
development seem very compelling:
-
there are no clear users or
On Wed, May 23, 2018 at 1:35 PM, Botond Ballo <bba...@mozilla.com> wrote:
> On Wed, May 23, 2018 at 4:05 PM, Jet Villegas <jville...@mozilla.com>
> wrote:
> > I'd rather see the committee focus on things like object lifetime
> management
> > so we don't have to po
I like that our link handling is getting shared but would really love a fix
for this bug in SVG rendering:
https://bugzilla.mozilla.org/show_bug.cgi?id=1366494
Robert: do you have time to fix that one while you're in there?
Thanks!
--Jet
On Tue, Apr 10, 2018 at 1:09 AM, Gijs Kruitbosch
SGTM. Please follow up to make sure this workaround makes it on to MDN:
> document.execCommand("defaultParagraphSeparator", false, "br");
Thx!
On Tue, Feb 13, 2018 at 8:14 PM, Masayuki Nakano
wrote:
> Starting from Firefox 60, I'd like to enable as default paragraph
>
On Sun, Dec 3, 2017 at 05:15 Axel Hecht wrote:
> Am 01.12.17 um 16:45 schrieb Justin Wood:
> > Hey Everyone,
> >
> > tl;dr if you don't download nightly l10n repacks via taskcluster index
> > routes, this does not affect you.
> >
> > Up until recently you could only find
Do you have a use case for shipping the ESR with --disable-stylo? We want
to be very quick about removing the legacy C++ style system as it adds
significant impedance to new feature development. I have not heard of any
site breakage that would warrant keeping --disable-stylo after Stylo is in
Nice! Binary literals sound cool for bit masks. I’d hate to have to
read/write them for anything else :-)
On Wed, Nov 15, 2017 at 20:44 Nathan Froyd wrote:
> C++14 constructs are now usable in mozilla-central and related trees.
> According to:
>
>
SGTM. BTW, bug 143038 was filed 16 years ago. Is that a bugzilla record for
oldest fixed bug?
That is, do I owe you another steak? :-)
On Wed, Oct 18, 2017 at 2:52 PM, Masayuki Nakano
wrote:
> From some users who use legacy mice which supports only vertical wheel, we
>
+1
On Tue, Oct 3, 2017 at 15:00 Chris Peterson wrote:
> On 2017-10-03 2:18 PM, Boris Zbarsky wrote:
> > Right now, at 60px, I can see 7-10 chars in a tab title. This is
> > sometimes (but not always) enough for me to make sense of what I'm
> > looking at when the favicon
Can you summarize the desired outcomes?
e.g.,
1. people using devtools in Chrome can also debug Firefox
2. devtools for Chrome can be ported to Firefox
3. devtools for Firefox can be used with Chrome
4. ...
This is potentially a very large API surface to support, and I'm skeptical
about our
Based on product plans I've heard, this sounds like the right approach. We
should try to limit the scope of such browser-specific APIs but it's likely
necessary in some cases (e.g., in the devtools.)
On Tue, Jul 25, 2017 at 2:44 AM, Gabor Krizsanits
wrote:
> In my mind
There's a lot of maneuvering going on with all the WebVR browser vendors
about which VR hardware vendors will get "Tier 1" support. The support
matrix can get quite complex as more vendors come in, and many of these new
vendors will not be W3C members. It would be good to encourage a more
around :-/
Thanks,
--Jet
On Thu, Jul 6, 2017 at 11:05 PM, Tim Huang <tihu...@mozilla.com> wrote:
>
>
> On Fri, Jul 7, 2017 at 11:54 AM, Jet Villegas <jville...@mozilla.com>
> wrote:
>
>> What do we expect to break?
>
>
> I can see that video quality auto adju
It looks like there may be a lot more of these:
https://stackoverflow.com/a/25397485
How about we just stub out the Stylo impls instead of unshipping the pseudo
in content?
On Thu, Jul 6, 2017 at 9:03 PM, Xidorn Quan <m...@upsuper.org> wrote:
> On Fri, Jul 7, 2017, at 01:42 PM, Jet
What do we expect to break? Who's out there using these APIs now?
Thanks,
--Jet
On Thu, Jul 6, 2017 at 8:21 PM, Tim Huang wrote:
> I intent to unship the support of moz*Frames of HTMLVideoElement including
> * HTMLVideoElement.mozParsedFrames
> *
Thanks for cleaning this up.
On Thu, Jul 6, 2017 at 8:29 PM, Xidorn Quan wrote:
> Although they don't currently match anything on web content, there is
> still some risk for unshipping them. Specifically, some websites seem to
> use them for browser-sniffing.
Do you have some
+cc: dev-servo, dev-tech-layout
Also, \o/ !!!
On Wed, Jun 21, 2017 at 3:24 PM, Gregory Szorc wrote:
> We're starting to enable the *building* (not enabling) of Stylo in various
> platforms in automation. This means that Nightly will start shipping Stylo
> bits soon - possibly
SGTM, Thanks for pushing on this one.
One comment: although this is a proposed change to non-normative spec
text, it appears that several implementations already implement the
original (also non-normative) recommendation. Would it be worthwhile
to propose the reversal and also mark the section as
xml:base (bug 1349024) has been removed in Nightly 55 for 2 months
now, and we haven't sen any reports of ill effects. Let's have this
testing expand to Beta 55, and on to Release if all goes well. Bug
1350521 tracks this change riding the trains.
--Jet
On Thu, Feb 16, 2017 at 2:51 PM, Xidorn
Might be good to serialize to/from disk after the first run, so only
the first process pays the compute cost?
On Thu, May 18, 2017 at 10:44 PM, Henri Sivonen wrote:
> On Tue, May 16, 2017 at 7:03 AM, Tim Guan-tin Chien
> wrote:
>> According to Alexa
Thanks, Tobias. If all goes well, please request uplift to FF 54 for
this after a few days in Nightly 55 to unblock bugs like:
https://bugzilla.mozilla.org/show_bug.cgi?id=1131937#c28
--Jet
On Wed, Apr 5, 2017 at 2:21 PM, Tobias Schneider wrote:
> Out final experiment on
During recent discussions with Koji Iishi, we said we would consider
this feature for implementation if we could find examples of content
authored for this feature that satisfy use cases from web and/or print
designers. I'd still love to see those examples ( authored by someone
outside the working
On Thu, Feb 16, 2017 at 7:23 AM, Mats Palmgren wrote:
> On 02/11/2017 04:59 AM, Boris Zbarsky wrote:
>
>> The biggest worry for me is that inline style is never a "chrome sheet"
>> in this sense.
>>
>
> That's a valid concern, but I think ignoring -moz-appearance has fairly
>
We had a good conversation with Ramin last week in Tokyo. The topic of
interoperability was discussed at length, and we also talked about where
Mozilla's 2017 priorities align with KDDI's.
To summarize, Mozilla is prioritizing the Web-compatibility and Performance
of the interoperable subset of
* Including a special-case check for the name Raanana when enumerating
> the system fonts
>
My preference as well, though I'm not convinced it's worth doing.
The Wikipedia page for the city of Ra'anana [0] marks up the city's Hebrew
name as:
רַעֲנָנָה
The Hebrew version [1] doesn't specify
Spec: https://drafts.css-houdini.org/css-paint-api/
Summary: The CSS Paint API is the first of several Web Rendering proposals
from the CSS Houdini Task Force. The CSS Paint API allows Web authors to
define and register a custom Paint method to be executed by the Layout
engine as other elements
+1 on expanding the search. That should help get earlier diagnosis. We
should also add 'regression' to those bugs as part of triage, as
appropriate.
--Jet
On Wed, Dec 14, 2016 at 6:11 PM, Nicholas Nethercote wrote:
> Hi,
>
> Currently there are two platform regression
+cc: abillings re: fuzzing CSS Grid.
On Monday, December 5, 2016, Benjamin Smedberg
wrote:
> Have the various grid properties be added to our fuzzers and we've been
> fuzzing the implementation fairly comprehensively?
>
> --BDS
>
> On Tue, Nov 15, 2016 at 7:40 PM, Mats
Unlike other parts of the Grid spec, we don't have sufficient implementor
feedback (from ourselves or others) to evaluate the subgrid feature's
suitability for implementation. That will take time to get, and we do plan
to get it, but we want Grid available to people while we do so. That's not
the
I generally support reducing the support matrix for Linux PCM audio.
A quick search for "ALSA vs. PulseAudio" comes up with mixed reviews for
either, which probably explains why we have both. It also seems like we can
count on ALSA being available on every distro, but perhaps not PulseAudio.
Can
at 11:15 AM, Nathan Froyd <nfr...@mozilla.com> wrote:
> On Mon, Jun 27, 2016 at 2:01 PM, Jet Villegas <jville...@mozilla.com>
> wrote:
> > Shing Lyu from our Taipei Layout team reports a 25% page load improvement
> > in Servo from moving to a hashtable lookup from an ite
Yay! Thank you :-)
--Jet
On Thursday, June 23, 2016, Dale Harvey wrote:
> In https://bugzilla.mozilla.org/show_bug.cgi?id=1273351 I am working on
> removing the pointerlock permissions UI, now instead of a doorhanger
> permission that the user needs to respond to before
We should offer both.
--Jet
On Thursday, June 2, 2016, Ben Kelly wrote:
> Hi all,
>
> I noticed recently that all of the available download links for dev edition
> point to the 32-bit installer. Is there a reason for this?
>
> Given we are talking about how to upgrade
On Thu, May 26, 2016 at 7:49 PM, Tzu-Hao Kuo wrote:
> *Link to standard*: No standard. This API was first discussed at Mozlando
> and has been discussed online here(
> https://github.com/w3c/mediacapture-worker/issues/33). The discussion has
> been led to a stream-based design
I'm surprised to see Skia (which I assume is also Chrome 53's canvas
backend) lagging behind CoreGraphics and even Cairo here. Do we have a bug
to track that down? This is the same code that powers our CSS filters, so a
speedup there should help both canvas and content.
--Jet
On Wed, Jun 1, 2016
If I'm reading the dependency list correctly, we still plan to uplift to 48
if we can get bug 1264905 fixed in time. Is that correct?
--Jet
On Fri, May 13, 2016 at 10:15 AM, Daniel Holbert
wrote:
> On 12/30/2015 10:40 PM, Daniel Holbert wrote:
> > Estimated or target
On Sun, May 8, 2016 at 10:35 PM, L. David Baron wrote:
> I just landed a patch to implement the #rgba and #rrggbbaa syntax
> for colors in CSS,
>
Nice!
> It affects only colors specified in CSS, and not those specified in
> HTML attributes.
>
> Is this a follow-up, or are
The "Intent to Implement" should help some of the concerns and allow for
comments. "Intent to Ship" usually means (at least for Platform Rendering)
that we'll be removing the #ifndef RELEASE flags and enabling preferences.
That is, by the time the "Intent to Ship" e-mail is sent, fundamental
+1 for streamlining Telemetry deployment
I think we'd still want to:
1. broadcast when experiments are shipping, with a specific start/end/goal,
and what data is collected
2. define scope: Nightly/Aurora/Beta (with a higher approval bar for each,)
+ Desktop/Mobile/Other
3. track bugs that
Holbert <dholb...@mozilla.com>
wrote:
> On 03/21/2016 10:38 PM, Jet Villegas wrote:
> > I'd like to see this guarded by its own pref &&
> layout.css.prefixes.webkit
>
> Pushing back on this slightly:
> - At this point, I don't think it's conceivable that we'd want
I'd like to see this guarded by its own pref && layout.css.prefixes.webkit
Thanks for working on this, CJ!
--Jet
On Tue, Mar 22, 2016 at 1:59 PM, Ku(顧思捷)CJ wrote:
> Summary:
> -webkit-background-clip:text has been available for years in webkit based
> browsers and has seen
On Thu, Nov 19, 2015 at 5:33 PM, Karl Dubost wrote:
> Jonas,
>
> Le 20 nov. 2015 à 04:22, Jonas Sicking a écrit :
> > I don't think authors will use this very much unless they can style it.
>
> DetailsElement - 0.0856%
>
> *Platform coverage*:
> everywhere
>
>
I'm so happy to see more Core Layout Engine features coming out of the
Taipei office. Nice work, CJ!
--Jet
___
dev-platform mailing list
dev-platform@lists.mozilla.org
Let the record state that Firefox is first to deliver Web Virtual Reality
to Planet Earth. On to other (virtual) worlds...
Congratulations, VR Team! \o/
--Jet
On Tue, Oct 27, 2015 at 4:19 AM, Kearwood "Kip" Gilbert <
kgilb...@mozilla.com> wrote:
> As of Oct 29, 2015 I intend to turn WebVR on
SGTM. It seems that the internal subset string was for non-HTML parsers to
use for whatever SGML/XML processing, so it should be OK to yank it from
the DOM. I can't find any docs on why it was added to the DOM in the first
place, so I can't comment on use cases we have to cover with an alternative
The next MemShrink meeting is brought to you by the new sampling based
memory profiler:
https://bugzilla.mozilla.org/show_bug.cgi?id=1123237
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we
It looks like most of the Security discussion is happening in this bug now:
https://bugzilla.mozilla.org/show_bug.cgi?id=907707
--Jet
On Mon, Sep 21, 2015 at 9:18 PM, Eric Rescorla wrote:
> On Mon, Sep 21, 2015 at 8:48 PM, Eric Shepherd
> wrote:
>
> >
The next MemShrink meeting is brought to you by better string processing in
the HTML5 parser:
https://bugzilla.mozilla.org/show_bug.cgi?id=1029671
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss
Today's MemShrink meeting is brought to you by cycle-free media buffers:
https://bugzilla.mozilla.org/show_bug.cgi?id=1190019
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure
Today's MemShrink meeting is brought to you by proper reference counting in
HTML5 media source extensions:
https://bugzilla.mozilla.org/show_bug.cgi?id=1190019
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink
This is the bug I filed to capture the unprefix list:
https://bugzilla.mozilla.org/show_bug.cgi?id=775235
Having our dev-tools alert for deprecated syntax would be very helpful. +cc
dev-developer-tools for feedback.
--Jet
On Wed, Jul 15, 2015 at 10:05 PM, Karl Dubost kdub...@mozilla.com wrote:
On Mon, Jul 6, 2015 at 8:12 PM, Jeff Gilbert jgilb...@mozilla.com wrote:
I propose we strike the `aFoo` recommendation from the Mozilla style guide.
Just so the proposal doesn't get lost in the bike shed, Jeff is only
proposing a change to the style guide, not a tree-wide find/replace
This. I don't want to lose Jonas' point in this long thread, but I also
haven't read anything here that warrants new native parser(s) yet. Let's
iterate in Gaia for now. I don't see how a C++ metadata parser is
advantageous at this point, and the RDF history lessons certainly don't
encourage that
Bug 1156135 https://bugzilla.mozilla.org/show_bug.cgi?id=1156135 will
enable Runtime Hardware Testing for Firefox Desktop. Once enabled, we'll
test the rendering capabilities of the current user's hardware prior to
enabling features that depend on that hardware.
A more detailed overview is posted
!!! \o/ !!!
We'll also post the proposed spec on this wiki page:
https://wiki.mozilla.org/CanvasFilters
--Jet
On Mon, Jun 15, 2015 at 10:15 AM, Markus Stange msta...@themasta.com
wrote:
Summary: The filter property on CanvasRenderingContext2D allows authors
to specify a filter that will get
Markus, Tobias, and Tantek will update the wiki page with our proposed
normative text.
Our key use case here is Shumway, where graphics filter implementations in
JS code have not (yet) been able to offer acceptable performance
characteristics in Canvas2D. We've proven that it's polyfillable in
Today's MemShrink meeting is brought to you by memory reporting for layout
style structs:
https://bugzilla.mozilla.org/show_bug.cgi?id=1168299
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how
avikpal...@gmail.com wrote:
Hey Jet,
Is there any recording of the meeting that you can share on air mozilla?
Thanks and regards,
Avik Pal
@avikpalme
On 9 June 2015 at 23:03, Jet Villegas jville...@mozilla.com wrote:
Today's MemShrink meeting is brought to you by memory reporting
Today's MemShrink meeting is brought to you by memory.report_concurrency:
https://bugzilla.mozilla.org/show_bug.cgi?id=1154053
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure
Awesome! What's the plan for getting the patches you mention in the video
into the tree?
Do we have instructions for Visual Studio anywhere?
--Jet
On Fri, May 22, 2015 at 10:31 AM, garvankee...@gmail.com wrote:
A video demo of how to get working quickly with Xcode:
\o/ Great to see this come through. Shumway was already using this but
needed chrome privilege to do so. It's nice to open it up.
--Jet
On Tue, May 5, 2015 at 2:51 PM, Ehsan Akhgari ehsan.akhg...@gmail.com
wrote:
Summary: We currently disallow programmatic copying and cutting from JS for
Web
We're adding UX to clearly indicate http:// or https:// in fullscreen while
still meeting the user desire for secure one-click-to-fullscreen. The
latest and greatest proposal posted here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1129061
--Jet
On Mon, May 4, 2015 at 2:04 PM, Eric Rescorla
...@hoppipolla.co.uk wrote:
On 30/04/15 23:42, Jet Villegas wrote:
I wonder why we'd allow *any* parsing differences here? Couldn't you just
assert and fail hard while you're testing against our tests and in
Nightly?
I imagine the differences you don't catch this way will be so subtle that
crowd
I wonder why we'd allow *any* parsing differences here? Couldn't you just
assert and fail hard while you're testing against our tests and in Nightly?
I imagine the differences you don't catch this way will be so subtle that
crowd-sourcing is unlikely to catch them either.
--Jet
On Thu, Apr 30,
The next MemShrink meeting is brought to you by debuggerMallocSizeOf:
https://bugzilla.mozilla.org/show_bug.cgi?id=1158257
https://bugzilla.mozilla.org/show_bug.cgi?id=1142183
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize
Thanks, Kip!
On Mon, Apr 6, 2015 at 11:47 AM, Kearwood Kip Gilbert
kgilb...@mozilla.com wrote:
Mobile platforms can benefit greatly from DEAA; however, we will need to
be selective on which hardware to enable this on to avoid performance
regressions.
The demos of this feature look
\o/ Hooray! This one took a lot of effort from many people across the
Rendering teams. Super-Happy to see it land.
--Jet
On Tuesday, March 31, 2015, L. David Baron dba...@dbaron.org wrote:
I just landed (on mozilla-inbound) a patch for
https://bugzilla.mozilla.org/show_bug.cgi?id=980770 that
The next Memshrink meeting begins in 1 hour and is brought to you by a
slimmer JS BaseShape:
https://bugzilla.mozilla.org/show_bug.cgi?id=1143256
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss
Excellent thread! Yes to more Dev Tools!!! Feel free to add a dev tooling
section to the e-mail templates we use for Intent to Implement and
Intent to Ship linked here:
https://wiki.mozilla.org/Intent_to_implement
We've started implementing the Web Animations API [1] with very early
Probably safe for the integer types, but can we add strong assertions when
converting from Thebes and Moz2D floats? Bugs like this one are tough to
debug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1091709
Thanks!
--Jet
On Fri, Mar 27, 2015 at 9:44 AM, Nicolas Silva nsi...@mozilla.com
The next Memshrink meeting is is brought to you by the Shumway project:
http://www.areweflashyet.com/shumway/
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Review Shumway memory reports/usage
* Prioritize unprioritized MemShrink bugs.
* Discuss
Cross-posting to dev-platform. Much of Simon's summary below applies to
Gecko.
--Jet
-- Forwarded message --
From: Simon Sapin simon.sa...@exyr.org
Date: Thu, Feb 19, 2015 at 9:28 AM
Subject: [dev-servo] CSS Houdini meeting report
To: dev-se...@lists.mozilla.org
Today's Memshrink meeting is is brought to you by delayed initialization of
D3D11 texture objects:
https://bugzilla.mozilla.org/show_bug.cgi?id=1127925
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
*
We should pick this up too.
--Jet
-- Forwarded message --
From: Jet Villegas W3C w...@junglecode.net
Date: Sat, Feb 7, 2015 at 1:36 AM
Subject: Fwd: [blink-dev] Intent to Ship: Plugin Power Saver Poster Images
To: j...@mozilla.com
-- Forwarded message --
From
Today's Memshrink meeting is is brought to you by areweslimyet.com:
https://bugzilla.mozilla.org/show_bug.cgi?id=1100253
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure progress.
*
CSSWG determined that display:contents covers use cases that CSS Grid
subgrid would otherwise cover [1]. We may punt on subgrid now that we've
got display:contents in Gecko. Other UAs have voiced support for the same
at the May 2014 F2F.
--Jet
[1]
The next Memshrink meeting is is brought to you by proper shutdown when IPC
messages are dropped:
https://bugzilla.mozilla.org/show_bug.cgi?id=1091766
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
*
The current Firefox implementation via a context-menu item (presumably
available to screen readers) seems innocuous to me. While I agree with many
of the points objecting to the spec, I don't see much upside for us (and
plenty of downside) to deprecating the feature without a counter-proposal.
, 2015 at 5:43 PM, Jet Villegas jville...@mozilla.com
wrote:
The current Firefox implementation via a context-menu item (presumably
available to screen readers) seems innocuous to me. While I agree with
many
of the points objecting to the spec, I don't see much upside for us (and
plenty
The next Memshrink meeting is is brought to you by cumulative heap
profiling:
https://bugzilla.mozilla.org/show_bug.cgi?id=1094552
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure
The next Memshrink meeting is is brought to you by the ImageLib SurfaceCache:
https://bugzilla.mozilla.org/show_bug.cgi?id=923302
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure
Hi dev-platform:
I'm seeing a lot of #ifdef RELEASE_BUILD lines in this file:
http://mxr.mozilla.org/mozilla-central/source/modules/libpref/init/all.js
A few features are currently enabled on all channels except Release. Do we have
any features (that we think have shipped) slipping through the
Note: new meeting time!
The next Memshrink meeting is is brought to you by better accounting for GFx
surface cache entries:
https://bugzilla.mozilla.org/show_bug.cgi?id=1096913
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize
Note: new meeting time!
The next Memshrink meeting is is brought to you by the replace_malloc tool to
capture and reproduce Firefox's memory allocations:
https://bugzilla.mozilla.org/show_bug.cgi?id=1083686
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
CSS position:sticky:
https://bugzilla.mozilla.org/show_bug.cgi?id=886646
--Jet
- Original Message -
From: Chris Mills cmi...@mozilla.com
To: dev-...@lists.mozilla.org, dev-platform dev-platform@lists.mozilla.org
Sent: Thursday, November 6, 2014 10:50:26 AM
Subject: Urgent request — info
\o/
Cross-posting to b2g-internal as these are the features the Gaia team will use
for the scrolling effects requested for Firefox OS.
--Jet
- Original Message -
From: Kip Gilbert kgilb...@mozilla.com
To: dev-platform@lists.mozilla.org
Sent: Monday, October 27, 2014 1:31:43 PM
Subject:
The next Memshrink meeting is is brought to you by e10s now reporting
performance timing in the content process:
https://bugzilla.mozilla.org/show_bug.cgi?id=1079705
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized
Roc wrote up a proposal last year for a web-facing screen capture API:
https://wiki.mozilla.org/User:Roc/ScreenCaptureAPI
Even if not web-facing, we could use the implementation code to cover chrome
use cases like this one:
https://bugzilla.mozilla.org/show_bug.cgi?id=933389
At a recent
I see the r+ on https://bugzilla.mozilla.org/show_bug.cgi?id=1057180
Are we missing anything else to checkin+ and turn this on?
--Jet
- Original Message -
From: Max Vujovic mvujo...@adobe.com
To: Dirk Schulze dschu...@adobe.com
Cc: Jacob Goldstein jac...@adobe.com, L. David Baron
The next MemShrink meeting is brought to you by DestroyWindow()
https://bugzilla.mozilla.org/show_bug.cgi?id=1060526
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure progress.
*
Would it be wise to allow for image-rendering: pixelated that applies to any
scale operation, and give us an option to add other operations (eg.
image-rendering: smooth or image-rendering: bilinear) later?
--Jet
- Original Message -
From: Daniel Holbert dholb...@mozilla.com
To: Ehsan
The next MemShrink meeting will be brought to you by app-theme-changed
observers not getting double-added:
https://bugzilla.mozilla.org/show_bug.cgi?id=1061202
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink
The next MemShrink meeting will be brought to you by the Gfx layer tile tracker:
https://bugzilla.mozilla.org/show_bug.cgi?id=1047945
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we
The next MemShrink meeting will be brought to you by the Asynchronous Pan/Zoom
Controller (APZC) not leaking testing data when disabled:
https://bugzilla.mozilla.org/show_bug.cgi?id=1041751
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
*
The next MemShrink meeting will be brought to you by the gray color #2d2d2d and
not by gradient bitmaps:
https://bugzilla.mozilla.org/show_bug.cgi?id=1039631
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink
The next MemShrink meeting is brought to you by the slimmer Firefox OS 2.0
Homescreen:
https://bugzilla.mozilla.org/show_bug.cgi?id=1029902
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we
after a user isn't using it any more
How good are we at determining any more? Flash is used in all sorts of crazy
ways, and guessing wrong can be more harmful than unloading too soon/late.
--Jet
___
dev-platform mailing list
Today's MemShrink meeting is brought to you by consolidated JS code:
https://bugzilla.mozilla.org/show_bug.cgi?id=1020012
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure progress.
The next MemShrink meeting will be brought to you by LeakSanitizer now running
on TBPL Mochitests:
https://bugzilla.mozilla.org/show_bug.cgi?id=988041
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
*
1 - 100 of 162 matches
Mail list logo