On 10/3/14 1:12 PM, Eric Rahm wrote:
Hi all-
In bug 806819 we're planning on landing a change that allows us to turn
on NSPR logging in release builds [1]. To be clear, by default all
logging output is disabled, this will just allow you to turn on logging
via the same mechanisms [2] that have be
Hi alll,
I just landed https://bugzilla.mozilla.org/show_bug.cgi?id=1074656 on
mozilla-inbound, which merged |mach debug| and |mach dmd| into |mach
run|. This avoids a lot of code duplication in mach and also lets you
run the browser under a debugger and DMD at the same time.
If you used to use |
On Wed, Oct 8, 2014 at 2:15 PM, Robert Kaiser wrote:
> Jonathan Kew schrieb:
>>
>> But the model for webfonts is explicitly *not* to have a single URL that
>> may be delivered in any of several formats, but rather to offer several
>> distinct resources with different URLs, and let the browser deci
Jonathan Kew schrieb:
But the model for webfonts is explicitly *not* to have a single URL that
may be delivered in any of several formats, but rather to offer several
distinct resources with different URLs, and let the browser decide which
of them to request.
So the "negotiation" is handled with
The Web APIs documentation meeting is Friday at 10 AM Pacific Time (see
http://bit.ly/APIdocsMDN for your time zone). Everyone's welcome to
attend; if you're interested in ensuring that all Web APIs are properly
documented, we'd love your input.
We have an agenda, as well as details on how to
On Wed, Oct 8, 2014 at 12:03 PM, Jonathan Kew wrote:
> Possible in theory, I guess; unlikely in practice. The compression
> algorithm used in WOFF2 is extremely asymmetrical, offering fast decoding
> but at the cost of slow encoding. The intent is that a large library like
> Google Fonts can pre-
On 8/10/14 16:48, Patrick McManus wrote:
On Wed, Oct 8, 2014 at 11:44 AM, Anne van Kesteren mailto:ann...@annevk.nl>> wrote:
On Wed, Oct 8, 2014 at 5:34 PM, Patrick McManus
mailto:mcma...@ducksong.com>> wrote:
> intermediaries, as I mentioned before, are a big reason. It provides a
On Wed, Oct 8, 2014 at 11:44 AM, Anne van Kesteren wrote:
> On Wed, Oct 8, 2014 at 5:34 PM, Patrick McManus
> wrote:
> > intermediaries, as I mentioned before, are a big reason. It provides an
> > opt-in opportunity for transcoding where appropriate (and I'm not
> claiming
> > I'm up to speed on
On Wed, Oct 8, 2014 at 5:34 PM, Patrick McManus wrote:
> intermediaries, as I mentioned before, are a big reason. It provides an
> opt-in opportunity for transcoding where appropriate (and I'm not claiming
> I'm up to speed on the ins and outs of font coding).
If the format is negotiated client-s
On Wed, Oct 8, 2014 at 11:18 AM, Jonathan Kew wrote:
>
> So the "negotiation" is handled within the browser, on the basis of the
> information provided in the CSS stylesheet, *prior* to sending any request
> for an actual font resource.
>
>
I'm not advocating that we don't do the css bits too. Th
On 8/10/14 15:44, Patrick McManus wrote:
On Wed, Oct 8, 2014 at 6:10 AM, Gervase Markham mailto:g...@mozilla.org>> wrote:
On 07/10/14 14:53, Patrick McManus wrote:
> content format negotiation is what accept is meant to do. Protocol level
> negotiation also allows designated interm
On Wed, Oct 8, 2014 at 6:10 AM, Gervase Markham wrote:
> On 07/10/14 14:53, Patrick McManus wrote:
> > content format negotiation is what accept is meant to do. Protocol level
> > negotiation also allows designated intermediaries to potentially
> transcode
> > between formats.
>
> Do you know of
On Wed, Oct 8, 2014 at 12:10 PM, Gervase Markham wrote:
> (This situation is basically "the Accept: problem".)
There's a bit more elaboration here for those new to it:
https://wiki.whatwg.org/wiki/Why_not_conneg
--
https://annevankesteren.nl/
___
On 07/10/14 14:53, Patrick McManus wrote:
> content format negotiation is what accept is meant to do. Protocol level
> negotiation also allows designated intermediaries to potentially transcode
> between formats.
Do you know of any software which transcodes font formats on the fly as
they move ac
When implementing a class inheriting from nsWrapperCache and using DOM
bindings it used to be the case that one needed to call
SetIsDOMBinding() from the constructor. This is no longer necessary, and
nsWrapperCache::SetIsDOMBinding has been removed.
We've added a private nsWrapperCache::SetIsN
15 matches
Mail list logo
