Fission Newsletter #3

2019-10-07 Thread Nika Layzell 
Hey All!

Over the last two months, we've made some excellent progress towards
improving the stability and feature support of Fission-enabled Firefox!

Are We Fission Yet?

The team has been hard at work, pushing down the number of failing Fission
Mochitests dramatically over the past few months! We've managed to get the
current count down to 324 total skipped and failing tests. Fission
Mochitests are now running on tier1 and need your help to get them all to a
passing state. Huge thanks to the M-fis team, and everyone who has worked
with us to help make this happen!

Thanks to the amazing work of :bgrins, :ahal, :gbrown and :kmag, we now
have a site for visualizing our current progress on Fission mochitests (and
hopefully more in the future)! In classic Mozillian fashion, you can find
it at https://arewefissionyet.com/! :kmag also maintains a canonical list
†
of failing tests, who's working on them, and their current status, if
you're looking to pick up some work and get involved!

†: mozilla-internal document, public read-only mirror

also available.


We have had tremendous progress during the ongoing M4 milestone with over
145 fixed bugs
.
We would like to thank everyone who’s helped us get this far.

The Omniscient Browser Toolbox

The Devtools team has made excellent strides updating the toolbox to add
out-of-process frame support! As part of this effort, a super-experimental
updated Omniscient Toolbox has been created which allows for the Inspector,
Console and Debugger tabs to be used to debug not just the parent process,
but content processes too!


Support for debugging out-of-process Fission content frames is also being
added, meaning that this could soon become an amazing and important piece
of the browser developer's toolbox! To try this, one can enable “omniscient
browser toolbox” in browser toolbox settings panel and restart the toolbox.
Huge thanks to the whole team.

(Previously Newsletter #1
,
Newsletter #2

)
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: [blink-dev] Re: What to do about scroll anchoring?

2019-10-07 Thread Mike Taylor 

Hi Rick,

On 9/28/19 10:07 PM, Rick Byers wrote:
Can you give us a week or so to chat about this within the Chrome team 
and get back to you?


Any updates here?

Thanks.

--
Mike Taylor
Web Compat, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Experimenting with JavaScript type safety in mozilla-central

2019-10-07 Thread Mike Conley 
This is a great thing to start looking into. I myself have definitely been
burned in the past because something unexpected got coerced into something
equally unexpected, resulting in behaviour that is without-a-doubt
unexpected.

So thanks to the folks getting this off the ground!

On Mon, 7 Oct 2019 at 13:06, Dave Townsend  wrote:

> JavaScript powers a lot of Firefox but unlike the other languages that ship
> code in our product JavaScript uses a dynamic type system. Types for
> variables are decided at execution time and can change as new values are
> assigned to them. This leaves you open to accidentally passing the wrong
> kind of data around your code. Easy to do when APIs are changed on the
> other side of the tree.
>
> Flow and Typescript have gained prominence recently as tools that add
> static types on top of JavaScript giving you a build time check (note: no
> runtime checks) to see if the types you’re using look correct. A number of
> us have used these tools successfully in side projects and want to see if
> using a tool like this would be beneficial in Firefox.
>
> A first experiment towards understanding this has just landed (
> https://hg.mozilla.org/integration/autoland/rev/1dd081553a3a).
> Specifically
> Greg Tatum has added TypeScript  type
> annotations and configuration to the JavaScript code in the
> devtools/client/performance-new directory.
>
> The mode of TypeScript we’re testing involves annotating types with
> comments, the JavaScript code itself is just normal JavaScript. All of the
> TypeScript bits live in comments so there is no build step and we’re also
> not adding any automated tests to verify the types in CI for this
> experiment.
>
> For the time being the perf tools team will just be checking the types
> locally before committing. This will give us an idea of the benefits on
> real in-tree code without any impact outside of the team.
>
> If you have any concerns with this or want to know more please let us know.
>
>
> Dave
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Experimenting with JavaScript type safety in mozilla-central

2019-10-07 Thread Dave Townsend 
JavaScript powers a lot of Firefox but unlike the other languages that ship
code in our product JavaScript uses a dynamic type system. Types for
variables are decided at execution time and can change as new values are
assigned to them. This leaves you open to accidentally passing the wrong
kind of data around your code. Easy to do when APIs are changed on the
other side of the tree.

Flow and Typescript have gained prominence recently as tools that add
static types on top of JavaScript giving you a build time check (note: no
runtime checks) to see if the types you’re using look correct. A number of
us have used these tools successfully in side projects and want to see if
using a tool like this would be beneficial in Firefox.

A first experiment towards understanding this has just landed (
https://hg.mozilla.org/integration/autoland/rev/1dd081553a3a). Specifically
Greg Tatum has added TypeScript  type
annotations and configuration to the JavaScript code in the
devtools/client/performance-new directory.

The mode of TypeScript we’re testing involves annotating types with
comments, the JavaScript code itself is just normal JavaScript. All of the
TypeScript bits live in comments so there is no build step and we’re also
not adding any automated tests to verify the types in CI for this
experiment.

For the time being the perf tools team will just be checking the types
locally before committing. This will give us an idea of the benefits on
real in-tree code without any impact outside of the team.

If you have any concerns with this or want to know more please let us know.


Dave
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to ship: Web Speech API

2019-10-07 Thread Jonathan Kew 

On 07/10/2019 09:53, Henri Sivonen wrote:

On Mon, Oct 7, 2019 at 5:00 AM Marcos Caceres  wrote:



  - speech is processed in our cloud servers, not on device.


What should one read to understand the issues that lead to this change?


+1. This seems like a change of direction which has *huge* implications 
for issues like availability (the feature doesn't work if my device is 
offline?), privacy (my device is sending microphone input to the 
cloud?), and cost (how much of my expensive metered data does this 
gobble up?) that need to be openly considered and discussed.


The original "Intent to prototype" seemed to be about an entirely 
device-local feature, which means it had fundamentally different 
characteristics.


Thanks,

JK
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to ship: Web Speech API

2019-10-07 Thread Gijs Kruitbosch 

On 07/10/2019 02:55, Marcos Caceres wrote:

  - speech is processed in our cloud servers, not on device.


Is this the case for both recognition and synthesizing? It's not clear 
from this concise description.


Also, hasn't window.speechSynthesis been shipped before now? It's used 
from e.g. reader mode's "narrate" functionality, and has been for quite 
a while, including on release...


~ Gijs
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to ship: Web Speech API

2019-10-07 Thread Henri Sivonen 
On Mon, Oct 7, 2019 at 5:00 AM Marcos Caceres  wrote:
>  - The updated implementation more closely aligns with Chrome's 
> implementation - meaning we get better interop across significant sites.

What site can one try to get an idea of what the user interface is like?

>  - speech is processed in our cloud servers, not on device.

What should one read to understand the issues that lead to this change?

-- 
Henri Sivonen
hsivo...@mozilla.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

[desktop] Bugs logged by Desktop Release QA in the last 7 days

2019-10-07 Thread Mihai Boldan 

Hello,

Here's the list of new issues found and filed by the Desktop Release QA 
team in the last 7 days.
Additional details on the team's priorities last week, as well as the 
plans for the current week are available at: https://tinyurl.com/y64js7do.

Bugs logged by Desktop Release QA in the last 7 days:
*
*Firefox: about:logins
* NEW    - https://bugzil.la/1585629 - Breach notifications are not 
displayed for some breached websites


Firefox: Distributions
* RESOLVED FIXED - https://bugzil.la/1585367 - [Win][Acer] The code in 
the search is wrongly displayed after Firefox update


Firefox: Migration
* NEW - https://bugzil.la/1586258 - Saved Passwords are imported from 
Internet Explorer but they won't appear in Saved Logins list


Firefox: Security
* NEW - https://bugzil.la/1585904 - [Certificate Viewer] The same 
certificate is opened in different tabs
* NEW - https://bugzil.la/1585620 - Create a standalone page 
(about:certificate) for the new certificate viewer


Firefox: Site Identity and Permission Panels
* NEW - https://bugzil.la/1585965 - Faulty behavior while navigating via 
keyboard the Protections Panel drop-down with Orca Screen reader 
activated on Ubuntu


Firefox: Tracking Protection
* RESOLVED WONTFIX - https://bugzil.la/1585368 - The Social Tracking 
Protection panel is triggered only after the 5th tab
* ASSIGNED - https://bugzil.la/1585615 - The Social Tracking Protection 
panel is not triggered at all


Core: Disability Access APIs
* NEW - https://bugzil.la/1585973 - Orca Reader does not recognize 
strings from drop downs unless accessed via keyboard navigation


Core: Print Preview
* ASSIGNED - https://bugzil.la/1585276 - Print Preview page number range 
can be exceeded


Core: Printing: Setup
* NEW - https://bugzil.la/1585291 - Print Dialog will freeze Firefox on 
Ubuntu


DevTools: Netmonitor
* RESOLVED WONTFIX - https://bugzil.la/1585997 - Netmonitor - Blocked By 
Devtools text should expand over the whole available row instead of 
being limited to the Transferred column
* RESOLVED WONTFIX - https://bugzil.la/1585636 - NetMonitor blocking - 
Add clear filter button in the add path input box
* NEW - https://bugzil.la/1585967 - Netmonitor - reset click 
pressed_status when the Hide Request Details panel is open
* NEW - https://bugzil.la/1585942 - NetMonitor blocking - Request 
blocking inner margins hide content when section width decreases to minValue
* NEW - https://bugzil.la/1585621 - Netmonitor blocking - improve 
visibility for the Request blocking path add (light theme)
* NEW - https://bugzil.la/1585612 - NetMonitor - Timings needs status 
message if none available from a blocked request
* NEW - https://bugzil.la/1585320 - NetMonitor blocking - Row for Enable 
Request blocking / actions should be fixed and not scrollable
* NEW - https://bugzil.la/1585313 - NetMonitor blocking - [Win] Button 
for filter removal remains displayed if click+drag away action is issued
* NEW - https://bugzil.la/1585307 - Netmonitor blocking - The same 
string is accepted twice in the Request Blocking list
* NEW - https://bugzil.la/1584988 - Netmonitor blocking - "Search" and 
"Request Blocking" are draggable
* NEW - https://bugzil.la/1584977 - Netmonitor blocking - filter 
ellipsis are not contained in the selection
* NEW - https://bugzil.la/1584970 - Netmonitor blocking - request 
blocking editing triggers filter toggle checkbox with current double 
click implementation
* NEW - https://bugzil.la/1584965 - There is no button for opening the 
Details side bar
* NEW - https://bugzil.la/1584960 - Netmonitor blocking - remove text 
offset in text-box when editing request filters
* NEW - https://bugzil.la/1584948 - NetMonitor blocking - Address the 
Search and Request blocking headers overlap on resize


Toolkit: Themes
* RESOLVED FIXED - https://bugzil.la/1585971 - Broken UI (mix of dark 
and light background colors / colours) on about:preferences (options) 
and about:addons manager pages


This is available as a Bugzilla bug list as well: 
https://tinyurl.com/y6qv8r3x.


Regards,
Mihai Boldan


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform