On 23/03/2018 18:23, Emilio Cobos Álvarez wrote:
> Bug 1408301 tracks unshipping CSSStyleDeclaration.getPropertyCSSValue.
>
> This is a non-standard API only implemented by Mozilla
It was removed from Blink[1] after they forked, but it's actually still
implemented in Webkit it seems. Hopefully we
On 03/23/2018 11:50 PM, Jonathan Watt wrote:
> On 23/03/2018 18:23, Emilio Cobos Álvarez wrote:
>> Bug 1408301 tracks unshipping CSSStyleDeclaration.getPropertyCSSValue.
>>
>> This is a non-standard API only implemented by Mozilla
>
> It was removed from Blink[1] after they forked, but it's actual
On 23 March 2018 at 21:06, Ben Kelly wrote:
> This is so great. Thank you!
>
> One question that comes to mind, though, is there any chance this could be
> uplifted to 60? As we start doing more OMT nsIURI stuff its going to
> become difficult to uplift code to 60ESR.
>
Certainly doable.
Most
On Friday 2018-03-23 19:23 +0100, Emilio Cobos Álvarez wrote:
> Bug 1408301 tracks unshipping CSSStyleDeclaration.getPropertyCSSValue.
>
> This is a non-standard API only implemented by Mozilla, and that
> generally can be replaced by usage of the standard .getPropertyValue.
I should clarify that
Hello,
Here's the list of new issues found and filed by the Desktop Release QA team
last week.
Additional details on the team's priorities last week, as well as the plans for
the current week are available at: https://goo.gl/fgDzo5
Bugs logged by Desktop Release QA in the last 8 days
Core: Wid
\o/ !!
On Friday, March 23, 2018, Valentin Gosu wrote:
> Hello everyone,
>
> I would like to announce that with the landing of bug 1447194, all nsIURI
> implementations in Gecko are now threadsafe, as well as immutable. As a
> consequence, you no longer have to clone a URI when you pass it arou
Unfortunately it hasn't been a priority. Hopefully we'll get to it eventually.
-Jeff
On Fri, Mar 23, 2018 at 10:56 AM, wrote:
> Chrome, Safari treat untagged images as sRGB, can read tagged ICCv4 images
> and support video color management.
>
> Firefox does not have these features by default.
Hi,
In bug 509958 I intend to unprefix the ::-moz-selection pseudo-element.
The situation here is not great wrt the spec saying what we do, or what
other implementations do for that matter, see [1].
However other engines have shipped this unprefixed for a long time with
the same semantics that w
For what it’s worth, here’s a summary of the issue:
Apple’s iMac (since September 2015) and MacBook Pro (since October 2016)
computers have wide-gamut displays that support the P3 color space (larger than
the sRGB color space). Unlike Safari and Chrome, Firefox still doesn’t convert
sRGB data t
I have just landed changes on inbound that restrict WebIDL
QueryInterface [1] and the Components object [2] to system scopes.
There are two caveats:
1) The Components bit is not fully enforced by the security
infrastructure yet, but those patches are coming in the next day or so. [3].
2) "
On 3/26/18 1:55 PM, Boris Zbarsky wrote:
I have just landed changes on inbound that restrict WebIDL
QueryInterface [1] and the Components object [2] to system scopes.
Oh, I meant to mention: in particular there is no longer a Components
available in XBL bindings attached to non-system-principa
On 3/26/18 3:16 AM, Emilio Cobos Álvarez wrote:
However other engines have shipped this unprefixed for a long time with
the same semantics that we implement
https://bugzilla.mozilla.org/show_bug.cgi?id=509958#c14 claims the
semantics are not actually quite the same. Have we done some testing
Considering that C++11 has a type for a Unicode scalar value and
considering that our compilers support C++11, I suggest we adopt a C++
code style guideline that we should use char32_t (as opposed to
uint32_t) to represent a single Unicode scalar value as the argument
type or return value of a meth
The issue has been resolved and all queued bugmail has been sent out. Thank
you for your patience.
Mark
On Monday, 26 March 2018 11:48:04 UTC-4, Mark Côté wrote:
> As a result of the migration of bugzilla.mozilla.org (BMO) from SCL3 to AWS,
> mail from BMO is currently being sent very slowly
As a result of the migration of bugzilla.mozilla.org (BMO) from SCL3 to AWS,
mail from BMO is currently being sent very slowly. The mail servers are
processing requests much more slowly than expected. There is no data loss; the
mail will be sent out eventually. The BMO and Cloud Operations teams
15 matches
Mail list logo