The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure progress.
* Discuss approaches to getting more data.
Meeting details:
* Tue, Aug 21, 2012, 4:00 PM PDT
* PBJ, Mountain View
Tomorrow's MemShrink meeting will be brought to you by the number 0x5f3759df
http://blog.quenta.org/2012/09/0x5f3759df.html
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure
Tomorrow's MemShrink meeting will be brought to you by the BananaBread browser
benchmarks:
https://github.com/kripken/misc-js-benchmarks/tree/master/banana
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink
Today's MemShrink meeting will be brought to you by a gigantic data URI:
https://bugzilla.mozilla.org/show_bug.cgi?id=786108
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure
This week's MemShrink meeting will be brought to you by infallible allocation
from Gecko Layout arenas:
https://bugzilla.mozilla.org/show_bug.cgi?id=809533
Note:
* New meeting time (2:00pm PST)
* New meeting room (today only)
The wiki page for this meeting is at:
This week's MemShrink meeting will be brought to you by Dark Matter:
https://wiki.mozilla.org/Performance/MemShrink/DMD
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* 64-bit Windows Builds Update
* Prioritize unprioritized MemShrink bugs.
*
Some key contributors are away at the FirefoxOS work week. Next meeting will be
on January 22.
In the meantime, check out the new improved Dark Matter Detector:
https://wiki.mozilla.org/Performance/MemShrink/DMD
--Jet
___
dev-platform mailing list
This week's MemShrink meeting will be brought to you by this awesome bug fix:
https://bugzilla.mozilla.org/show_bug.cgi?id=795988
Note:
* New meeting/vidyo room (this week only)
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize
Agreed! Looks like Fennec Team has a plan for PanZoomController.java:
https://bugzilla.mozilla.org/show_bug.cgi?id=745136
I think we need to get past this big one to unify the other platforms:
https://bugzilla.mozilla.org/show_bug.cgi?id=825928
--Jet
- Original Message -
From: Anthony
Re-sending in case you missed this invitation over the weekend.
--Jet
- Original Message -
From: Benoit Jacob jacob.benoi...@gmail.com
To: dev-platform dev-platform@lists.mozilla.org,
dev-plann...@lists.mozilla.org planning dev-plann...@lists.mozilla.org
Sent: Saturday, February 2, 2013
Some key contributors are away at the DOM/WebAPI work week. Next meeting will
be on Feb 12.
In the meantime, please check out Nick's excellent blog about all things
Memshrink:
https://blog.mozilla.org/nnethercote/
See you next week!
--Jet
___
I assume we would send the same diff we use for DLBI over to the painting
thread to minimize the cost. How would this new design interact with the
current refresh driver scheduling?
--Jet
- Original Message -
From: L. David Baron dba...@dbaron.org
To: Chris Lord cl...@mozilla.com
Cc:
I'm not too concerned about the landing schedule here as I don't expect to see
OMTP landing too soon (though mwoodrow has surprised us before.) We should have
plenty of runway between the required Layers work and OMTP.
Let's put OMTP (and prerequisites) on the next Rendering call agenda. This
Stephen:
We talked about extracting this snapshot from the GFx Layers. Have you explored
that possibility? Taking the screencap from the raster data we already paint
should help here. BTW, 20 seems to be a very high number to cache per tab. The
biggest problem I'd like to solve is that I often
AIUI, a key goal of our Layers Refactoring is to significantly reduce the cost
of standing up new GFx backends (the first new one being D3Dv11.) As that
progresses, I'd like to see detailed documentation about how new backends are
added. I think we can get an intern or volunteer to stand up
deciding on committing to
full-blown implementations.
--Jet
- Original Message -
From: Nicholas Cameron nick.r.came...@gmail.com
To: mozilla dev platform mozilla.dev.platf...@googlegroups.com
Cc: dev-platform@lists.mozilla.org, Jet Villegas j...@mozilla.com
Sent: Monday, February 25, 2013 11:40
Today's MemShrink meeting will be brought to you by this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=689623
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Discuss Images Memory Usage
* Prioritize unprioritized MemShrink bugs.
* Discuss
That's Terrible!
I mean the word TeRriBLe will help people remember how this works now :)
--Jet
- Original Message -
From: Daniel Holbert dholb...@mozilla.com
To: dev-platform@lists.mozilla.org
Sent: Wednesday, March 6, 2013 10:24:52 AM
Subject: PSA: nsMargin, gfxMargin, etc.
Note new meeting time: Tuesday, 19 March 2013, 16:00:00
Today's MemShrink meeting will be brought to you by this fixed bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=843733
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Discuss Images
Today's MemShrink meeting will be brought to you by zones, a.k.a. compartment
groups:
https://bugzilla.mozilla.org/show_bug.cgi?id=759585
NOTE: new meeting time, new vidyo room
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Discuss results of
Note new meeting time: Tuesday, 16 April 2013, 16:00:00 PDT
Today's MemShrink meeting will be brought to you by lower-memory Android fonts:
https://bugzilla.mozilla.org/show_bug.cgi?id=844669
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
*
Friendly Reminder: Gecko Rendering (Layout, GFx, Media) meeting Today, May 6,
2:30 PM US/Pacific
--Jet
- Original Message -
From: Benoit Jacob jacob.benoi...@gmail.com
To: dev-platform dev-platform@lists.mozilla.org,
dev-plann...@lists.mozilla.org planning dev-plann...@lists.mozilla.org
The next MemShrink meeting will be brought to you by leaky(?) offscreen
surfaces in Windows:
https://bugzilla.mozilla.org/show_bug.cgi?id=869252
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss
Sounds like a good candidate for a Metrics web crawl to help predict the
bustage level. If the number is low enough, we can skip the whitelist. In
general, removing -moz-prefixed syntax is a good thing, especially when
standard alternatives have taken hold.
--Jet
- Original Message -
The next MemShrink meeting will be a birthday party:
https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure
Don't forget to add your prefixed API's/properties to this meta bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=775235
We've been very active in getting rid of prefixes as quickly as we can. I love
that CSS Flexbox shipped unprefixed after testing with an about:config flag for
several cycles.
I may have a skewed view of things, but I personally have not had problems
getting prompt code reviews. I also don't have a problem talking to my
reviewers about what I'm hacking on. I'm hesitant to throw a bunch of
technology at this problem, if it's a social issue. Code reviews are a
I think we found usage of -moz-font-smoothing in the wild. John Jensen may
have more info.
--Jet
- Original Message -
From: L. David Baron dba...@dbaron.org
To: dev-platform@lists.mozilla.org
Sent: Tuesday, July 23, 2013 12:43:54 PM
Subject: intent to make exception to prefixing policy:
The next MemShrink meeting will be brought to you by the Mushroomer game:
http://www.areweflashyet.com/Mushroomer
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure progress.
*
Mozilla proposed the NPAPI changes to get rid of windowed plug-ins [1] but
there wasn't a big enough reason to change the Flash Player at that time--the
threat of content breakage wasn't that high. If content breakage is certain via
multi-process with windowed plug-ins, then Adobe will likely
thread on the subject for context.
--Jet
- Original Message -
From: Jeff Muizelaar jmuizel...@mozilla.com
To: Tobias Schneider schnei...@jancona.com
Cc: Jet Villegas j...@mozilla.com, Benoit Jacob bja...@mozilla.com,
Joe Drew j...@mozilla.com, Boris Zbarsky bzbar...@mozilla.com, L.
David
Thanks, Rob! Definitely worth hacking up a prototype and timing the results. I
think the key bit is the section on lowering latency. IMO, this (N ms delay)
should be a parameter computed at runtime based on workload and available
resources. I don't think shipping a static N across multiple
This is awesome! Is it possible to see a log of the recipients/patches?
--Jet
- Original Message -
From: Matt Brubeck mbrub...@mozilla.com
To: dev-platform@lists.mozilla.org
Sent: Monday, August 12, 2013 3:14:20 PM
Subject: Proposal: Email individual patch authors who improve
Sweet! Lots of goodness already in the first e-mail I clicked on:
https://groups.google.com/forum/#!topic/mozilla.dev.tree-management/UcpnVNOdr28
--Jet
- Original Message -
From: Matt Brubeck mbrub...@mozilla.com
To: Jet Villegas j...@mozilla.com
Cc: dev-platform@lists.mozilla.org
Sent
The next MemShrink meeting will be brought to you by bug 907201:
Enable Type Inference and IonMonkey for chrome code
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 bug 847223
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure progress.
* Discuss approaches to getting more data.
Meeting
The only Pepper plug-in worth talking about is the Flash Player. The Flash
Player that ships in Chrome is developed by Google and distributed with the
Chrome browser. That is, Adobe doesn't make this Pepper plug-in and has no
installers for Firefox users to use. In other words, Pepper support
Hi All:
I hope everyone had a chance to see Shumway on the big screen at the Summit.
I'm very proud of what the Shumway team has accomplished to date. While the
demos looked amazing, we've got quite a bit to do to get Shumway to a
product-ready state. In particular, the user experience on
/09/13 05:35 PM, Jet Villegas wrote:
I'm currently looking for someone to green up the tests on Win64. Can we
dedicate one machine instance (I'm assuming this is on AWS?) for the purpose
of advancing this greenery project? Also, who is the point-person on Release
Engineering that we should
Excellent.
Now to find willing volunteer(s.) Windows 64 represents a key platform for us
now that we've opened up Firefox for high-performance graphics via WebGL and
Canvas. Freeing up the CPU by going to the GPU exposes the next bottleneck:
Memory Bandwidth.
Can you help get the test
Now that everyone's back from Summit, it's time to MemShrink...
The next MemShrink meeting will be brought to you by bug 771765
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 Fast Per-Tab Memory
Profiling:
https://bugzilla.mozilla.org/show_bug.cgi?id=918207
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we
Vidyo Room Change (today only:) SFO-7I Independent
--Jet
- Original Message -
From: Jet Villegas j...@mozilla.com
To: mozilla.dev.platform group dev-platform@lists.mozilla.org,
dev-plann...@lists.mozilla.org planning dev-plann...@lists.mozilla.org
Sent: Monday, October 28, 2013 4:46:00
Hi All:
At the W3C TPAC conference in China, there's a lot of activity around HTML
CSS Ruby. Here are the relevant spec drafts presented at the conference:
HTML:
http://darobin.github.io/html-ruby/
CSS:
http://www.w3.org/TR/css3-ruby/
The Platform Rendering team is investing a lot of energy
The next MemShrink meeting will be brought to you by the shutdown leak detector:
https://bugzilla.mozilla.org/show_bug.cgi?id=932898
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 will be brought to you by the Nuwa process on B2G:
https://bugzilla.mozilla.org/show_bug.cgi?id=930282
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 will be brought to you by about:memory on B2G:
https://bugzilla.mozilla.org/show_bug.cgi?id=948774
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 will be brought to you by efficient MP3 memory
buffers on Firefox OS:
https://bugzilla.mozilla.org/show_bug.cgi?id=960873
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
*
The next MemShrink meeting will be brought to you by images decoded *and*
downsampled at the same time:
https://bugzilla.mozilla.org/show_bug.cgi?id=854795
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
We're still quite busy working on it. Watch these bugs...
Add filter support to Moz2D (fixed)
https://bugzilla.mozilla.org/show_bug.cgi?id=924102
Move SVG filters to Moz2D (fixed)
https://bugzilla.mozilla.org/show_bug.cgi?id=924103
Add CSS Filters with Moz2D (in progress, almost done.)
Hi Platform Team:
I've asked Cameron McCormack to look into how Firefox and other browsers should
behave when under mild to severe stress. As all browser engines have to manage
how to run under low memory, feeble network, pegged CPU, weak GPU, low battery,
small/slow screens, etc., I think web
Do you think this should require author opt-in? I was thinking that we spec
what we degrade automagically so it's less of a black box even without opt-in.
--Jet
- Original Message -
From: smaug sm...@welho.com
To: Nicholas Nethercote n.netherc...@gmail.com, Jet Villegas
j
Excellent info, Boris! I added a link here and removed the TODO comment:
https://wiki.mozilla.org/Gecko:Overview#DOM_.2F_Content
--Jet
- Original Message -
From: Boris Zbarsky bzbar...@mit.edu
To: dev-platform@lists.mozilla.org
Sent: Friday, March 28, 2014 10:32:00 PM
Subject: Overview
The next MemShrink meeting will be brought to you by auto-minified javascript
code in B2G chrome:
https://bugzilla.mozilla.org/show_bug.cgi?id=903149
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
*
The next MemShrink meeting will be brought to you by purging IPC messages prior
to B2G process shutdown:
https://bugzilla.mozilla.org/show_bug.cgi?id=999351
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
Today's MemShrink meeting will be brought to you by correct use of the Gecko
Cycle Collector:
https://bugzilla.mozilla.org/show_bug.cgi?id=1004630
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss
Today's MemShrink meeting will be brought to you by correct use of the Gecko
Cycle Collector:
https://bugzilla.mozilla.org/show_bug.cgi?id=1004630
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss
Today's MemShrink meeting will be brought to you by image urls and sizes in
about:memory:
https://bugzilla.mozilla.org/show_bug.cgi?id=1009097
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how
It seems healthy for the core C++ language to explore new territory here.
Modern primitives for things like pixels and colors would be a good thing, I
think. Let the compiler vendors compete to boil it down to the CPU/GPU. There
will always be the argument for keeping such things out of Systems
Today's MemShrink meeting will be brought to you by MapMemory() safety for the
VirtualAlloc() footgun:
https://bugzilla.mozilla.org/show_bug.cgi?id=1005849
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
Hi All:
We need a path forward on the deployment of Icon fonts in FxOS. The Gaia team
understandably wants to squeeze every bit of performance on their apps in v1.4:
https://bugzilla.mozilla.org/show_bug.cgi?id=951593
We are concerned about leaking these fonts into Open Web content, so we want
Wilson:
How difficult would it be to have your grunt script add a dlig table to your
font?
https://www.microsoft.com/typography/otspec/features_ae.htm#dlig
https://bugzilla.mozilla.org/show_bug.cgi?id=1008458#c22
--Jet
- Original Message -
From: Wilson Page wilsonp...@mozilla.com
We
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.
*
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.
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
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
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 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 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 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
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 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.
*
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
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
\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
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
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
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
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
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
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]
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.
*
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.
*
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.
*
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
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 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
\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
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
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
...@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
\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
1 - 100 of 162 matches
Mail list logo