I am from India i like Firefox OS very much wanted to port it
to my phone REDMI 1S (Details:
http://www.gsmarena.com/xiaomi_redmi_1s-6373.php ) which is a budget
android mobile launched in india china few months ago had good
sales. We have 33,000 user group on facebook also
Hey,
See this fiddle:
http://jsfiddle.net/2ccvwjmr/1/
Seems like DOM order has influence on the absolutely positioned element. I
don't think it's a desired behaviour.
Did I do anything wrong? Can you verify if this is a bug?
Thanks,
Amit
___
On 04/29/2015 03:06 AM, Amit Zur wrote:
http://jsfiddle.net/2ccvwjmr/1/
Seems like DOM order has influence on the absolutely positioned element. I
don't think it's a desired behaviour.
Did I do anything wrong? Can you verify if this is a bug?
It's correct according to an older version of
We have a bunch of preferences controlling web-exposure of various
things that are always true. canvas.path.enabled, for example.
Some of these are there so that users or redistributors can turn off
certain features, but some are just leftover cruft from when we used to
only support the
On 2015-04-29 12:48 PM, Eric Shepherd wrote:
Boris Zbarsky wrote:
I'd appreciate it if people would go through their IDL, find the
things that are still cruft, and remove them...
The docs team would appreciate a heads-up for any that get removed
(either by email or by dev-doc-needed if you
(Sorry for cross-posting)
Dear Mozilla developer,
We, researchers from the University of Waterloo and Universite de Montreal,
Canada (some of you might remember our names from the previous study), are
currently conducting a study on code review quality and factors affecting it.
We have
Boris Zbarsky wrote:
I'd appreciate it if people would go through their IDL, find the
things that are still cruft, and remove them...
The docs team would appreciate a heads-up for any that get removed
(either by email or by dev-doc-needed if you use bugs to track the
work). Even for prefs
On 04/29/2015 03:10 PM, Jonas Sicking wrote:
But has anyone reached out to the JS
team and let them know that we really need let and yield in workers to
see if A is an option?
This is the reaching-out stage now* :). When I filed bug 1151739 the
only impacted app was the email app, and that
Can you link to the previous study?
~ Gijs
On 29/04/2015 17:59, olgabay...@gmail.com wrote:
(Sorry for cross-posting)
Dear Mozilla developer,
We, researchers from the University of Waterloo and Universite de Montreal,
Canada (some of you might remember our names from the previous study),
On Wed, Apr 29, 2015 at 9:05 AM, Andrew Sutherland
asutherl...@asutherland.org wrote:
A) The JS concept of versions goes away, at least for web content and ES6
features (in the next few weeks). This covers things like
https://bugzil.la/855665 on making let work without requiring JS 1.7.
I
Hi all,
Bhavana, Peter, and I have been working together to produce developer release
notes for Firefox OS 2.1 and 2.2:
https://developer.mozilla.org/en-US/Firefox_OS/Releases/2.1
https://developer.mozilla.org/en-US/Firefox_OS/Releases/2.2
At this point, I think they are looking relatively
On Wed, Apr 29, 2015 at 9:05 AM, Andrew Sutherland
asutherl...@asutherland.org wrote:
E) B2G-Specific:
E1) Set dom.workers.latestJSVersion for only B2G's trunk, which has no
releases planned for the foreseeable future.
This feels like painting ourselves into a corner.
E2) On B2G have
On 01/16/2015 04:31 AM, L. David Baron wrote:
On Tuesday 2015-01-06 15:14 -0800, L. David Baron wrote:
W3C recently published the following proposed recommendation (the
stage before W3C's final stage, Recommendation):
http://www.w3.org/TR/pointerevents/
Pointer Events
There's a call for
On 04/24/2015 08:57 PM, Matt Brubeck wrote:
tl;dr:
We plan to enable Pointer Events for mouse and pen input in Firefox Nightly
builds within the next few weeks.
Background:
Pointer Events is a W3C recommendation that defines new DOM events for unified
handling of mouse, touch, and pen
On 2015-04-28 6:52 AM, Aryeh Gregor wrote:
But why do you find it
more clear to say |virtual ... final| than |... final|? They both convey
the exact same amount of information. Is it just habit and/or personal
preference?
Personally, I was surprised when I first learned that override/final
On 2015-04-27 9:54 PM, Trevor Saunders wrote:
On Mon, Apr 27, 2015 at 09:07:51PM -0400, Ehsan Akhgari wrote:
On Mon, Apr 27, 2015 at 5:45 PM, Trevor Saunders tbsau...@tbsaunde.org
wrote:
On Mon, Apr 27, 2015 at 03:48:48PM -0400, Ehsan Akhgari wrote:
Right now, our coding style requires that
Update/data after talking with sfink/jorendorff/Waldo/shu of the JS team
and some follow-up investigation with thanks to sfink to initiating the
conversation:
- yield inside function* is working fine inside a worker with
JSVERSION_DEFAULT; we suspect the error I was relaying was not inside a
On Thu, Apr 30, 2015 at 2:52 AM, Honza Bambas hbam...@mozilla.com wrote:
Just let you know about my intensive work on Backtrack or Caller Chain
which is about connecting Gecko Profiler and Task Tracer together to catch
all (instrumented) inter-object and inter-thread calls + IO blocking, lock
I think this is a good plan, and the harmony with the Google style guide is
a nice incidental benefit.
Does this mean that every c++ *must* be marked with override, or is that
still optional? Do we intend to make that a requirement in the future?
--BDS
On Mon, Apr 27, 2015 at 3:48 PM, Ehsan
Just let you know about my intensive work on Backtrack or Caller
Chain which is about connecting Gecko Profiler and Task Tracer together
to catch all (instrumented) inter-object and inter-thread calls + IO
blocking, lock waits, queuing, event (nsIRunnable) dispatches, network
query/response
Ehsan Akhgari writes:
On 2015-04-27 9:54 PM, Trevor Saunders wrote:
On Mon, Apr 27, 2015 at 09:07:51PM -0400, Ehsan Akhgari wrote:
On Mon, Apr 27, 2015 at 5:45 PM, Trevor Saunders tbsau...@tbsaunde.org
wrote:
I believe we have some cases in the tree where a virtual function
doesn't
Ehsan Akhgari writes:
I think there's a typo of some sort in the question, but if you
meant every overriding function must be marked with override,
then yes, that is the change I'm proposing, but the good news is
that you can now run clang-tidy on the entire tree and get it to
rewrite the
All content DOM workers use JSVERSION_DEFAULT unless the
dom.workers.latestJSVersion pref is set to true. (Note: you need to
manually add the pref in about:config.) Chrome workers get
JSVERSION_LATEST. There is no way to tell the worker to use a specific
JS version like we can do in page
On 2015-04-29 10:23 AM, Benjamin Smedberg wrote:
I think this is a good plan, and the harmony with the Google style guide
is a nice incidental benefit.
Does this mean that every c++ *must* be marked with override, or is that
still optional? Do we intend to make that a requirement in the future?
24 matches
Mail list logo
