On Fri, 6 Jul 2018, at 15:35, Chris Pearce wrote:
> On Saturday, July 7, 2018 at 5:04:28 AM UTC+12, Mounir Lamouri wrote:
> > On Fri, 6 Jul 2018, at 00:49, Chris Pearce wrote:
> > > On Friday, July 6, 2018 at 3:10:58 AM UTC+12, Mounir Lamouri wrote:
> > > > On We
On Fri, 6 Jul 2018, at 00:49, Chris Pearce wrote:
> On Friday, July 6, 2018 at 3:10:58 AM UTC+12, Mounir Lamouri wrote:
> > On Wed, 4 Jul 2018, at 18:22, Chris Pearce wrote:
> > > Hi Mounir,
> > >
> > > Replies inline below...
> > >
> > >
On Wed, 4 Jul 2018, at 18:22, Chris Pearce wrote:
> Hi Mounir,
>
> Replies inline below...
>
>
> On Thu, Jul 5, 2018 at 2:56 AM, Mounir Lamouri wrote:
>
> > Hi Chris,
> >
> > Very excited to see Firefox going forward with autoplay blocking. A couple
&g
Hi Chris,
Very excited to see Firefox going forward with autoplay blocking. A couple of
comments inline.
On Tue, 3 Jul 2018, at 19:38, Chris Pearce wrote:
> DETAILS:
>
> We intend to block autoplay of HTMLMediaElement in tabs which haven't
> had user interaction. Web authors should assume that
On Mon, 12 Dec 2016, at 04:00, Boris Zbarsky wrote:
> On 12/11/16 8:47 AM, Mounir Lamouri wrote:
> > On Sat, 10 Dec 2016, at 17:58, Boris Zbarsky wrote:
> >> OK, but a website doing this won't work in Chrome Android. So what
> >> would websites actually do in pra
On Sat, 10 Dec 2016, at 17:58, Boris Zbarsky wrote:
> On 12/5/16 3:20 AM, Mounir Lamouri wrote:
> > Correct. Intent to ship has been sent on blink-dev. Chrome Android
> > should follow.
>
> Do you have any idea what the timeframe is?
Unfortunately not. My best guestima
On Fri, 2 Dec 2016, at 15:09, Boris Zbarsky wrote:
> On 12/2/16 6:11 AM, Shih-Chiang Chien wrote:
> > We implement 1-UA mode described in spec. Session resumption and many-to-1
> > session is not available in this mode.
> .
> > Google have release this API on both desktop and Android browser fo
On Tue, 29 Nov 2016, at 15:17, Boris Zbarsky wrote:
> > I understand the privacy concerns, but why can't these be handled similar
> > to the Geolocation API? Ask permission to use / user opts in.
>
> Because prompting users is generally an antipattern. If, as a user, you
> got a battery API pro
FWIW, this is the usage of window.orientation in the wild recorded by
Chrome:
https://www.chromestatus.com/metrics/feature/timeline/popularity/285
However, Google's internal tools allow me to see the repartition between
platforms and this seen a lot by Chrome Android users.
Should we add this to
On Sat, 10 Oct 2015, at 02:02, zbranie...@mozilla.com wrote:
> On Friday, October 9, 2015 at 10:51:54 AM UTC-7, Mounir Lamouri wrote:
> > As far as speed feeling goes, they would win to show something as soon
> > as possible and handle any post-first paint loading themselve
On Fri, 9 Oct 2015, at 16:27, Vivien Nicolas wrote:
> On Thu, Oct 8, 2015 at 6:10 PM, Mounir Lamouri wrote:
>
> > Note that Chrome 46 has a way to work around the white screen while a
> > page load using a new property in the Manifest. If a website added to
> > the home
Note that Chrome 46 has a way to work around the white screen while a
page load using a new property in the Manifest. If a website added to
the homescreen on Chrome Android has a background_color information, it
will be used while the page loads. After Chrome gets the first paint
following a non-em
On Wed, 2 Sep 2015, at 03:50, Ehsan Akhgari wrote:
> On 2015-09-01 9:57 PM, Jonas Sicking wrote:
> > But I agree that we should make it clear that we do not intend to
> > implement a request API.
>
> There is actually a valid use case for a request API. It has become
> clear that we need to expo
On Tue, 25 Aug 2015, at 07:57, Anne van Kesteren wrote:
> On Sat, Aug 22, 2015 at 5:03 AM, Birunthan Mohanathas
> wrote:
> > Summary: The Permissions API allows a web application to be aware of
> > the status of a given permission, to know whether it is granted,
> > denied or if the user will be a
On Tue, 2 Dec 2014, at 02:09, Boris Zbarsky wrote:
> Summary: document.origin returns the Unicode serialization of the
> document's origin. The returned value does not depend on what
> document.domain was set to.
>
> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=931884
>
> Spec: http://dom
On Wed, 1 Oct 2014, at 10:51, Jonas Sicking wrote:
> On Tue, Sep 30, 2014 at 3:54 AM, Mounir Lamouri
> wrote:
> > On Thu, 25 Sep 2014, at 02:49, Jonas Sicking wrote:
> >> Yes!
> >>
> >> Though as previously expressed, I don't think we should ship th
On Thu, 25 Sep 2014, at 02:49, Jonas Sicking wrote:
> Yes!
>
> Though as previously expressed, I don't think we should ship this until
> it
> supports sending Blobs.
What do other UAs implement?
-- Mounir
___
dev-platform mailing list
dev-platform@list
On Thu, 11 Sep 2014, at 18:26, Ms2ger wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 09/11/2014 08:18 AM, Kershaw Chang wrote:
>
> First of all, you neglected to explain the standardization situation
> here. Is this feature being standardized? If not, why not? How do
> other brow
On Tue, 9 Sep 2014, at 10:10, Daniel Veditz wrote:
> On 9/8/2014 2:16 AM, Mounir Lamouri wrote:
> > On Sun, 7 Sep 2014, at 04:56, Martin Thomson wrote:
> >> It's more the case that a persistent positive grant from permission
> >> manager would be ignored for n
On Tue, 9 Sep 2014, at 00:15, Lars Knudsen wrote:
> looks good,
>
> maybe adding to always take a holistic view on what you are doing and how
> it will interact with other specs/standards used in the same apps (e.g.
> considering DeviceOrientation and DeviceMotion before makeing
> OrientationLock
On Sun, 7 Sep 2014, at 04:56, Martin Thomson wrote:
> It's more the case that a persistent positive grant from permission
> manager would be ignored for non-secure origins and non-secure origins
> would not show any option to persist.
I don't know the specifics about the UI, but you don't want to
On Sat, 6 Sep 2014, at 14:49, Martin Thomson wrote:
> One idea that has been floated
> (https://bugzilla.mozilla.org/show_bug.cgi?id=1002676) is to restrict
> persistent permissions to secure origins. The reasoning there being that
> a persistent grant can be trivially intercepted if you work in t
Hi,
In Firefox 32, instead of returning "yes" or "unspecified",
navigator.doNotTrack will start returning "1", "0" or "unspecified",
making it closer to the specification in some aspects - returning "1"
and "0" is what the specification requires, not "yes". It will also fix
a nasty bug where askin
Hi,
Note: this is not an Intent to Ship because it is a minor change but
given that it is still a content visible change, I want to make sure
dev-platform is aware of it.
I've landed a patch last week to update the vibration API implementation
to match the current specification. The changes make
Hi dev-platform,
As of today, I intend to land patches to implement navigator.languages
and the languagechange event (on the Window object).
This feature will not live behind a flag given that it is not complex
nor controversial.
Bug : https://bugzilla.mozilla.org/show_bug.cgi?id=889335
Spec:
htt
On 26/07/13 18:29, Ehsan Akhgari wrote:
> We're planning to implement a prototype of the NavigationController
> interface (see bug 898524). We will try to get feedback from web
> developers on the prototype and will use that feedback to change the spec
> and the implementation and iterate on the A
On 11/07/13 16:43, Neil wrote:
> Milan Sreckovic wrote:
>
>> That last thing was another item I found useful in the previous life.
>> When requesting a review from somebody, people could see "this person
>> currently has X items in their review queue".
>>
> Even better would be if Bugzilla could
On 26/06/13 18:27, Ehsan Akhgari wrote:
2. ecosystem- and hardware-specific APIs that are not standard or of
interest to the broader web at that time (or ever) may be shipped in
a way to limit their harm of the broader web (ex. only on a device
or only in specific builds with c
On 26/06/13 17:08, Andrew Overholt wrote:
> On 25/06/13 12:15 PM, Mounir Lamouri wrote:
>> Also, I do not understand why we are excluding CSS, WebGL and WebRTC. We
>> should definitely not make this policy retro-apply so existing features
>> should not be affected but if someo
On 26/06/13 18:13, Ehsan Akhgari wrote:
> On 2013-06-26 12:17 PM, Andrew Overholt wrote:
>> On 26/06/13 11:48 AM, Ehsan Akhgari wrote:
>>> On 2013-06-26 11:21 AM, Andrew Overholt wrote:
On 24/06/13 05:52 PM, Ehsan Akhgari wrote:
> There are two things that I think can use clarification. O
On 26/06/13 16:59, Ehsan Akhgari wrote:
> For whatever it's worth, Blink has made the decision to implement Web
> MIDI without receiving any feedback from us (and to the best of my
> knowledge from other vendors),
I am not sure why implementing something should require that many rules
as long as i
On 25/06/13 17:28, Robert O'Callahan wrote:
> On Wed, Jun 26, 2013 at 4:15 AM, Mounir Lamouri wrote:
>
>>> 3. APIs solving use cases which no browser vendor shipping an engine
>>> other Gecko is interested in at that time. In cases such as this,
>>> Mozi
Hi Thomas,
MozICCManager is an API available only for built-in applications on
Firefox OS so it is fine to change it as much as you want.
--
Mounir
On 25/06/13 17:11, Thomas Zimmermann wrote:
> Hi,
>
> I intent to implement an extension to nsIDOMMozICCManager.
>
> When unlocking a SIM card, th
On 21/06/13 21:45, Andrew Overholt wrote:
> I'd appreciate your review feedback. Thanks.
Thank you for putting this together.
I am going to quote some parts of the document to give some context to
my comments.
> Note that at this time, we are specifically focusing on new JS APIs
> and not on C
On 22/05/13 03:09, L. David Baron wrote:
> On Friday 2013-02-08 14:37 -0800, L. David Baron wrote:
>> W3C is proposing a revised charter for the HTML Working Group.
>> For more details, see:
>> http://lists.w3.org/Archives/Public/public-new-work/2013Feb/0009.html
>> http://www.w3.org/html/wg/charte
On 26/04/13 20:42, bent wrote:
> IndexedDB is our answer for this for JS... C++ folks are still pretty
> much on their own!
Why? Wouldn't be the idea of such component to make sure it is usable
from C++?
--
Mounir
___
dev-platform mailing list
dev-platf
On 25/04/13 17:34, Ben Adida wrote:
> Potch has a great proposal: let apps declare a marketplace in their
> manifest. If apps are served from and signed by the marketplace, then
> any origin is okay (after review.) If apps are self-hosted, then the
> only origin allowed is that of the hosting site.
On 26/04/13 11:17, Gregory Szorc wrote:
> Anyway, I just wanted to see if others have thought about this. Do
> others feel it is a concern? If so, can we formulate a plan to address
> it? Who would own this?
As others, I believe that we should use IndexedDB for Gecko internal
storage. I opened a b
On 25/02/13 15:57, Benoit Girard wrote:
> Hello dev.platform,
>
> GTest has landed this weekend on mozilla-central[1]. It should now be
> ready for developers to start writing test. It will appear on
> tinderbox once it is build off '--enable-tests'. For more details see
> the documentation: https
On 23/02/13 07:25, Jared Wein wrote:
> Hi,
>
> I wanted to let you all know about bug 842913, of which I just landed the
> patch for on mozilla-inbound.
>
> The goal of the bug is to make the process of working with the /browser and
> /toolkit themes easier for new contributors. The previous na
On 23/01/13 20:39, edgar.am...@gmail.com wrote:
[...]
> also, the the angularJS app is in my localhost port 81, the php file is in my
> localhost, different port.
You are very likely being stopped by a cross-origin check. Try to run
both code within the same origin [1] and see if that works.
[1
On 27/11/12 22:35, Gregory Szorc wrote:
> I feel the build system should be as fast as possible by default - no
> user action necessary. If you find that -j == # cores isn't providing
> the fastest builds possible, please present your data and we'll change
> the default value.
I recently changed m
On 14/11/12 19:27, Gavin Sharp wrote:
> On Wed, Nov 14, 2012 at 10:53 AM, Mounir Lamouri wrote:
>> For that, we will need some tools to know if we are building for Release
>> (and let say Beta) where the feature should be hidden by default, with
>> opposition to Aurora, Nig
On 06/11/12 13:31, Henri Sivonen wrote:
> Therefore, I propose that we adopt the following policy:
> 1) APIs that are not ready for use by Web developers shall not be
> shipped on the release channel (unless preffed off).
For that, we will need some tools to know if we are building for Release
(a
On 09/29/2012 06:40 PM, Gavin Sharp wrote:
> On Sat, Sep 29, 2012 at 7:53 AM, Chris AtLee wrote:
>> http://people.mozilla.org/~catlee/highscores/highscores.html is a report of
>> where our time on Try is going.
>
> I think we should have this data feed into a cronjob that emails the
> top ~5 week
On 09/21/2012 11:50 PM, Ehsan Akhgari wrote:
> On 12-09-20 8:22 PM, Ehsan Akhgari wrote:
>> Aryeh has been doing a heroic job (I mean, heroic, for reals!) in bug
>> 777292 to make nsresult a C++ enum, as opposed to just an unsigned int.
>> I've stepped in to help for the last few bits, and I'm pl
On 08/31/2012 12:33 AM, Rafael Ávila de Espíndola wrote:
> I was recently hit by most of the shortcomings you mentioned while
> trying to upgrade clang. Fortunately, I found the issue on try, but I
> will admit that comparing talos on try is something I only do when I
> expect a problem.
I'm a bit
47 matches
Mail list logo
