The W3C is proposing a revised charter for:
Web Performance Working Group
https://www.w3.org/2018/07/webperf-charter
https://lists.w3.org/Archives/Public/public-new-work/2018Jul/0002.html
Mozilla has the opportunity to send comments or objections through
Friday, August 3.
The changes relat
The W3C is proposing revised charters for:
Accessible Platform Architectures (APA) Working Group
https://www.w3.org/2018/03/draft-apa-charter
Accessible Rich Internet Applications (ARIA) Working Group
https://www.w3.org/2018/03/draft-aria-charter
https://lists.w3.org/Archives/Public/pu
Two W3C Proposed Recommendations are available for the membership of
W3C (including Mozilla) to vote on, before they proceed to the final
stage of being a W3C Recomendation:
WAI-ARIA Graphics Module
https://www.w3.org/TR/graphics-aria-1.0/
https://w3c.github.io/graphics-aria/
Graphics Acc
+1. This is really fantastic news, and frankly happened way faster than I
would have thought possible. Thanks to everyone involved!
On Tue, Jul 10, 2018 at 1:51 PM Gregory Szorc wrote:
> On Tue, Jul 10, 2018 at 1:29 PM, David Major wrote:
>
>> Bug 1443590 is switching our official Windows build
At the moment, performance is a mixed bag. Some tests are up and some
are down. In particular I believe Speedometer is down a few percent.
Note however that clang-cl is punching above its weight. These builds
currently have neither LTO nor PGO, while our MSVC builds use both of
those. Any regressi
On Tue, Jul 10, 2018 at 1:29 PM, David Major wrote:
> Bug 1443590 is switching our official Windows builds to use clang-cl
> as the compiler.
>
> Please keep an eye out for regressions and file a blocking bug for
> anything that might be fallout from this change. I'm especially
> interested in he
How does the performance of clang-cl builds compare to MSVC builds on
benchmarks like Speedometer?
On 2018-07-10 1:29 PM, David Major wrote:
Bug 1443590 is switching our official Windows builds to use clang-cl
as the compiler.
Please keep an eye out for regressions and file a blocking bug for
Bug 1443590 is switching our official Windows builds to use clang-cl
as the compiler.
Please keep an eye out for regressions and file a blocking bug for
anything that might be fallout from this change. I'm especially
interested in hearing about the quality of the debugging experience.
It's possib
>Welcome to the first edition of the Fission MemShrink newsletter.[1]
This is awesome and critical.
I'll note (and many of you know this well) that in addition to getting
rid of allocations (or making them lazy), another primary solution is to
move data out of the Content processes, and into the
On 7/10/18 11:47 AM, James Graham wrote:
Are there web-platform-tests covering this behaviour (both the part we
are changing and the part we aren't)?
I added some tests in bug 820891. See the three
testing/web-platform/tests/css/cssom-view/table-*-props.html tests.
There was also a tiny lit
On 10/07/2018 17:25, Boris Zbarsky wrote:
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=820891
Summary: In other browsers, and arguably per spec as far as cssom-view
specs things, various geometry APIs on tables should report values for
the table wrapper, not the table itself, because they
Welcome to the first edition of the Fission MemShrink newsletter.[1]
In this edition, I'll sum up what the project is, and why it matters to you.
In subsequent editions, I'll give updates on progress that we've made, and
areas that we'll need to focus on next.[2]
The Fission MemShrink projec
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=820891
Summary: In other browsers, and arguably per spec as far as cssom-view
specs things, various geometry APIs on tables should report values for
the table wrapper, not the table itself, because they are defined to
work on the "first" box ge
> On Jul 9, 2018, at 6:31 PM, Xidorn Quan wrote:
>
> On Tue, Jul 10, 2018, at 7:36 AM, Tantek Çelik wrote:
Platform coverage: Desktop
>>>
>>> Why not on mobile?
>>
>> Requires platform specific code that just hasn't been written (yet)
>> for mobile platforms.
>
> Actually I don't really
The diffs for all review requests will be archived. More details soon. :)
Mark
On Thu, Jul 5, 2018 at 4:23 PM, Henrik Skupin wrote:
> Mark Côté wrote on 03.07.18 21:34:
>
> > We’re aiming for late July for these implementations, which will allow us
> > to close down MozReview soon after, in ti
Hi,
We are modifying the webrtc library to use another transport protocol (based on
ICN).
The problem is that in this preliminary phase we have configure the socket
using static parameters inside a file.
The new socket is implemented in a library that communicates via TCP with an
external dae
There are indeed a lot of edge cases and concerns, but this is off-topic
for this thread now. We're still in early stages here, as some more
groundwork has to be laid. We'll be coming back to this after some crucial
Phabricator/Lando work has landed. It's something we're quite interested in
and has
I sympathize with the concerns here; however, changing the default would be
a very invasive change to Phabricator, which would not only be complex to
implement but troublesome to maintain, as we upgrade Phabricator every week
or two.
This is, however, something we can address with our new custom
c
No, I'm not of irtf Group.
I need to use a version of customized webrtc on Android.
Thank you
Il Ven 6 Lug 2018, 18:23 Nils Ohlmeier ha scritto:
>
>
> > On Jul 6, 2018, at 08:26, Randell Jesup wrote:
> >
> >>> On 05/07/2018 10:16, amantell...@gmail.com wrote:
> I want to open a file inside
19 matches
Mail list logo
