Hi Ehsan,
Yes, in my opinion that is the problem. I'm trying to use the global stream
variable across module boundaries, more specifically from the following source
files: content\base\src\Element.cpp; layout\style\nsCSSParser.cpp;
content\base\src\nsINode.cpp, js\src\builtin\Eval.cpp,
Thanks for the tip. Can you perhaps drop the internal stream class names, so I
can investigate a bit on how to use them.
Thank you!
On Friday, October 24, 2014 4:56:07 PM UTC+2, David Rajchenbach-Teller wrote:
Well, for one thing, never perform I/O on the main thread. It really
kills
On 28/10/14 09:35, Josip Maras wrote:
Thanks for the tip. Can you perhaps drop the internal stream class names, so
I can investigate a bit on how to use them.
Thank you!
You may want to open an nsAtomicFileOutputStream on a thread:
On 2014-10-28 4:16 AM, Josip Maras wrote:
Hi Ehsan,
Yes, in my opinion that is the problem. I'm trying to use the global stream
variable across module boundaries, more specifically from the following source
files: content\base\src\Element.cpp; layout\style\nsCSSParser.cpp;
Hello Jonas,
I appreciate your detailed reviews on the topic. I'm sorry if I did
not yet address all of your issues. Please advise if there is
anything else I may have missed.
I guess what I'm arguing is that smooth-scrolling vs. instant
scrolling shouldn't be a per-element CSS property,
(cross posting to b2g as this might be an interesting api for on-device
tools).
I have just landed the patches for bug 1020244 [1].
These patches introduce a new (chrome-only) API at document level that
can be used to insert custom DOM elements into the root container of the
page (the canvas
On Tue, Oct 28, 2014 at 11:08 AM, Kip Gilbert kgilb...@mozilla.com wrote:
Hello Jonas,
I appreciate your detailed reviews on the topic. I'm sorry if I did
not yet address all of your issues. Please advise if there is
anything else I may have missed.
Thanks for your comments below. Much
On Wed, Oct 29, 2014 at 9:40 AM, Jonas Sicking jo...@sicking.cc wrote:
That said, it's scary that these APIs are described in terms of
synchronous operations on the scroll position. I.e. it seems to
pretend that off-main-thread scrolling doesn't exist and then hope
that implementations are
On Tue, Oct 28, 2014 at 11:56:49AM -0400, Ehsan Akhgari wrote:
On 2014-10-28 4:16 AM, Josip Maras wrote:
Hi Ehsan,
Yes, in my opinion that is the problem. I'm trying to use the global stream
variable across module boundaries, more specifically from the following
source files:
On Wed, Oct 29, 2014 at 08:08:23AM +0900, Mike Hommey wrote:
On Tue, Oct 28, 2014 at 11:56:49AM -0400, Ehsan Akhgari wrote:
On 2014-10-28 4:16 AM, Josip Maras wrote:
Hi Ehsan,
Yes, in my opinion that is the problem. I'm trying to use the global
stream variable across module
Mike Hommey schrieb:
Note a significant amount of the omni.ja and browser/omni.ja data is
used for jsloader/jssubloader data: 4744949 and 1560499 bytes from those
files are that. These jsloader/jssubloader data are there for startup
benefits on Firefox first run (if the data wasn't there, it
Hi,
I've just finished a major overhaul of our documentation about memory-related
tools. We used to have two main pages on this topic:
- https://wiki.mozilla.org/Performance:Leak_Tools
-
https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/Debugging_memory_leaks
There was some overlap
Does scroll-behavior:smooth apply on scrolling that happens due to navigation
(as per spec)? I've tested a Back to top link (href=#top) and got an
instant scroll.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
13 matches
Mail list logo
