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! W
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@list
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 20
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
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* im
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. read
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
7 matches
Mail list logo
