On 3/2/15 1:00 AM, Chris Peterson wrote:
Gecko's offsetX/Y could return doubles, for compatibility with the spec,
that are always snapped to whole numbers, for compatibility with other
browsers.
How, precisely, is this different from returning integers? Remember,
this is JS we're talking abou
On 2/27/15 7:25 PM, Robert O'Callahan wrote:
On Sat, Feb 28, 2015 at 8:30 AM, Jeff Muizelaar
wrote:
>On Fri, Feb 27, 2015 at 2:21 PM, Robert O'Callahan
>wrote:
> >Oh, another issue is that I've followed the spec and made offsetX/Y
> >doubles, whereas Blink is integers, which introduces a small
(forgot to cc dev.platform in my reply)
On Sat, Feb 28, 2015 at 3:47 AM, Paul Rouget wrote:
>> So in order to implement the behaviour you're looking for we would
>> definitely need to make some changes in gecko.
>
> How much work is that? Is it just a matter of "piping" things together
> to expo
(forgot to cc dev.platform in my reply)
On Fri, Feb 27, 2015 at 11:57 AM, Paul Rouget wrote:
> Hi Kats. Thanks for taking a look at this.
>
> On Thu, Feb 26, 2015 at 10:21 PM, wrote:
>> On Thursday, February 26, 2015 at 1:06:15 PM UTC-5, Paul Rouget wrote:
>>> I need a pretty picture to explain
On 03/02/2015 01:11 AM, Xidorn Quan wrote:
On Mon, Mar 2, 2015 at 9:50 AM, Boris Zbarsky wrote:
On 3/1/15 5:04 PM, Xidorn Quan wrote:
Hence I think we should remove this method. All callees should use either
AssignLiteral(MOZ_UTF16("some string")), or, if don't want to bloat the
binary, expl
On 02/28/2015 05:25 AM, Robert O'Callahan wrote:
On Sat, Feb 28, 2015 at 8:30 AM, Jeff Muizelaar
wrote:
On Fri, Feb 27, 2015 at 2:21 PM, Robert O'Callahan
wrote:
Oh, another issue is that I've followed the spec and made offsetX/Y
doubles, whereas Blink is integers, which introduces a small a
On Mon, Mar 2, 2015 at 9:50 AM, Boris Zbarsky wrote:
> On 3/1/15 5:04 PM, Xidorn Quan wrote:
>
>> Hence I think we should remove this method. All callees should use either
>> AssignLiteral(MOZ_UTF16("some string")), or, if don't want to bloat the
>> binary, explicitly use AssignASCII("some string
On 3/1/15 5:04 PM, Xidorn Quan wrote:
Hence I think we should remove this method. All callees should use either
AssignLiteral(MOZ_UTF16("some string")), or, if don't want to bloat the
binary, explicitly use AssignASCII("some string").
The latter requires an strlen() that AssignLiteral optimizes
On Tue, Jan 13, 2015 at 12:44:19PM +0900, Mike Hommey wrote:
> On Tue, Jan 13, 2015 at 10:13:34AM +0900, Mike Hommey wrote:
> > Hi,
> >
> > I just landed bug 762449 on inbound, which enables Jemalloc 3 on the
> > nightly channel. This puts us a step forward to removing mozjemalloc,
> > our highly
I think we should remove the method nsAString::AssignLiteral(const char
(&aStr)[N]) because its name is misleading.
The method name AssignLiteral can easily make people at the callee side
think it makes the string point to a piece of static data, which has no
runtime penalty. But this is false.
T
10 matches
Mail list logo
