I’d like to finetune my earlier statement - after talking things over a bit
with Benjamin - to say: I’d like to volunteer if there’s no one else moving
forward to take this project on.
The reason is that I’m not currently working on or using XULRunner tech, so my
level of engagement is low.
On Wednesday, July 29, 2015 at 8:44:57 PM UTC-6, Eric Shepherd wrote:
Benjamin Smedberg wrote:
I am looking to see whether there is an alternate owner who is
interested in the task of keeping XULRunner building and running
properly and reviewing patches to XULRuner-specific code. Please
There are some forces at play in a web app that point to wanting to delay
layout and rendering until a web app gives a signal that it should start:
* ECMAScript modules, and even developer constructed JS module systems
today, rely on async loading of scripts.
* Custom elements need their JS
Can't you just make everything display:none until you're ready to show it?
-Jeff
On Thu, Jul 30, 2015 at 4:20 PM, James Burke jbu...@mozilla.com wrote:
There are some forces at play in a web app that point to wanting to delay
layout and rendering until a web app gives a signal that it should
On Thu, Jul 30, 2015 at 10:15 AM webko...@gmail.com wrote:
Problem it this introduced some bugs, like disabling scrolling completely
on some pages, such as a google search page.
Did you report a bug on this yet? I find this can be reproduced reliably
by loading in more log history in an
A reminder that my presentation is less than an hour away!
It'll be live in MV commons as well as streamed on AirMo at 3pm PDT; tune
in to hear the latest on what's happening in DXR land.
Thanks,
Peter
On Tue, Jul 28, 2015 at 8:33 AM, Peter Elmers pelm...@mozilla.com wrote:
Hello!
I'm
I can't speak about the validity of the requirement, but in terms of
API, we probably want something more compositional, if several codepaths
need to stop rendering. And then, we end up with the possibility that
someone forgets to enable rendering, with all the ensuing debugging joy.
Since this
The OP filed bug 1189237 for this issue, but it seems like it was
reported on Firefox 39 where we don't support async-pan-zoom. If you
can reproduce this issue in a Nightly build please file a new bug.
Thanks,
kats
On Thu, Jul 30, 2015 at 5:32 PM, Andreas Tolfsen a...@mozilla.com wrote:
On Thu,
On Thu, Jul 30, 2015 at 4:27 PM, James Burke jbu...@mozilla.com wrote:
On Thu, Jul 30, 2015 at 1:28 PM, Jeff Muizelaar jmuizel...@mozilla.com
wrote:
Can't you just make everything display:none until you're ready to show
it?
Just using display: none seems like it will run into the same
On Thu, Jul 30, 2015 at 1:28 PM, Jeff Muizelaar jmuizel...@mozilla.com wrote:
Can't you just make everything display:none until you're ready to show it?
Just using display: none seems like it will run into the same problem
that prompted bug 863499, where the browser did some render/paints of
a
James Burke writes:
On Thu, Jul 30, 2015 at 1:28 PM, Jeff Muizelaar jmuizel...@mozilla.com
wrote:
Can't you just make everything display:none until you're ready to show it?
Just using display: none seems like it will run into the same problem
that prompted bug 863499, where the browser did
On Thu, Jul 30, 2015 at 1:35 AM, David Keeler dkee...@mozilla.com wrote:
I therefore propose we follow suit and begin the process of deprecating
and removing these features. The intention of this post is to begin a
discussion to determine the feasibility of doing so.
Deprecating and adding
On Thu, Jul 30, 2015 at 9:00 AM, Tim Guan-tin Chien
timdr...@mozilla.com wrote:
This is not as convenient as a keyword in WebIDL but I think it's good enough.
You might want to chime in on
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29004
which is asking for something similar (though more
On Thu, Jul 30, 2015 at 6:33 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Jul 30, 2015 at 12:28 PM, Teoli
news.fakeaddress@localhost.invalid wrote:
Do you think it is already worth to flag it as deprecated in the MDN
documentation as Google plans to remove it too?
Yeah, seems
On Thu, Jul 30, 2015 at 6:53 AM, Hubert Kario hka...@redhat.com wrote:
On Wednesday 29 July 2015 16:35:41 David Keeler wrote:
[cc'd to dev-security for visibility. This discussion is intended to
happen on dev-platform; please reply to that list.]
Ryan Sleevi recently announced the
reverendli...@gmail.com mailto:reverendli...@gmail.com
July 30, 2015 at 10:17 AM
I'll volunteer to help out with documentation.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Benjamin
On Thu, Jul 30, 2015 at 12:28 PM, Teoli
news.fakeaddress@localhost.invalid wrote:
Do you think it is already worth to flag it as deprecated in the MDN
documentation as Google plans to remove it too?
Yeah, seems worth a note at least given that Microsoft doesn't ship it
either (nor plans to
On Wednesday 29 July 2015 16:35:41 David Keeler wrote:
[cc'd to dev-security for visibility. This discussion is intended to
happen on dev-platform; please reply to that list.]
Ryan Sleevi recently announced the pre-intention to deprecate and
eventually remove support for the keygen element
On 30/07/2015 08:58, Anne van Kesteren wrote:
On Thu, Jul 30, 2015 at 1:35 AM, David Keeler dkee...@mozilla.com wrote:
I therefore propose we follow suit and begin the process of deprecating
and removing these features. The intention of this post is to begin a
discussion to determine the
On Thursday, July 30, 2015 at 11:13:57 AM UTC+2, webk...@gmail.com wrote:
Hi,
i enabled layers.async-pan-zoom.enabled in firefox on Mac OSX Yosemite, and
noticed dramatic performance increase.
Problem it this introduced some bugs, like disabling scrolling completely on
some pages, such as
On Thu, Jul 30, 2015 at 9:13 PM, webko...@gmail.com wrote:
Hi,
i enabled layers.async-pan-zoom.enabled in firefox on Mac OSX Yosemite,
and noticed dramatic performance increase.
Great!
Problem it this introduced some bugs, like disabling scrolling completely
on some pages, such as a
Hi,
i enabled layers.async-pan-zoom.enabled in firefox on Mac OSX Yosemite, and
noticed dramatic performance increase.
Problem it this introduced some bugs, like disabling scrolling completely on
some pages, such as a google search page.
Is this the proper place to report such bugs ?
I'd like
22 matches
Mail list logo
