Awesome! Do we have a restriction that pointerlock can only be entered
during a user action, like a click?
And do we completely forgo the warning when the webpage is already in
fullscreen mode?
/ Jonas
On Thu, Jun 23, 2016 at 2:47 AM, Dale Harvey wrote:
> In https://bugzilla.mozilla.org/show_b
On Fri, May 20, 2016 at 4:04 PM, Ben Kelly wrote:
> On May 20, 2016 6:14 PM, "Jonas Sicking" wrote:
>> That doesn't sound good. We should give each worker its own loadgroup.
>> Independent of if it's a dedicated, shared or service worker.
>>
>> O
On Fri, May 20, 2016 at 12:28 PM, Ben Kelly wrote:
> On Fri, May 20, 2016 at 3:12 PM, Jonas Sicking wrote:
>>
>> On Fri, May 20, 2016 at 8:04 AM, Ben Kelly wrote:
>> > On Fri, May 20, 2016 at 10:56 AM, Boris Zbarsky
>> > wrote:
>> >
>> &
On Fri, May 20, 2016 at 8:04 AM, Ben Kelly wrote:
> On Fri, May 20, 2016 at 10:56 AM, Boris Zbarsky wrote:
>
>> Thoughts? Any obvious problems with this plan?
>
> We have the concept of network requests made from workers not associated
> with a single document. For example, SharedWorker attache
On Thu, May 12, 2016 at 12:48 PM, Jan-Ivar Bruaroey wrote:
> Our original intent behind those choices was to let users join a video
> conference as an "audio only" participant. Unfortunately, sites don't expect
> this behavior and often don't work right when the track is missing.
This part should
On Tue, May 10, 2016 at 1:31 PM, Mike Taylor wrote:
> On 5/10/16 3:05 PM, Jack Moffitt wrote:
>
>> We have the Chrome popularity data, and we have the Edge team's data
>> which covers the CSS spectrum quite well. I think it would be far more
>> useful to start covering the DOM API spectrum.
>>
>>
On Mon, Apr 25, 2016 at 11:17 PM, Martin Thomson wrote:
> On Tue, Apr 26, 2016 at 4:10 PM, Xidorn Quan wrote:
>> Could we probably restrict it to non-release builds (aurora and nightly)
>> rather than restrict them to debug builds only? Debug builds are harder to
>> get, and are slow.
>
> That wa
We could also make the default behavior be to cancel old pushes. And
then enable push message syntax for opting in to not cancelling.
/ Jonas
On Fri, Apr 15, 2016 at 10:19 AM, James Graham wrote:
> On 15/04/16 18:09, Tim Guan-tin Chien wrote:
>>
>> I wonder if there is any use cases to do multip
I have two concerns with this.
First off, it means that users might need to actively log in to
websites more often. This is a really big hassle for users, especially
on mobile. We did some studies when we did FirefoxOS between the
differences between native versions and web version of various apps
On Thu, Apr 14, 2016 at 12:53 AM, Ting-Yu Lin wrote:
> One major concern in the "intent to implement" discussion is the ability to
> style the summary disclosure triangle. Currently summary has default style
> "display: list-item", so we can style the triangle via the pseudo element
> |summary::-
On Fri, Apr 8, 2016 at 2:03 PM, Jeff Gilbert wrote:
> Strong preference against eFoo, here. :)
Would you mind saying why?
/ Jonas
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Hi Benoit,
There's two problems that I've seen related to scrolling, and so
possibly the result of APZ.
The most obvious one is that if the child process is busy doing
things, then the scrollable area seems "sticky". When you start
scrolling there's a noticeable delay before the page starts scrol
On Fri, Mar 11, 2016 at 9:20 AM, Benjamin Smedberg
wrote:
> On 3/10/2016 5:25 PM, Mike Hommey wrote:
>> It's unfair to mention those populations by percentage of the global
>> Firefox population.
>
> Why do you think this is unfair? This is about making the best use of our
> limited engineering/te
Generally speaking, I find it really hard to reason about what we
should do regarding clipboard events and drag'n'drop events without
taking a larger look at the sad story that rich-text-editing on the
web is today.
It seemed like there was some really promising explorations happening
for a while
I filed
https://github.com/httpwg/http-extensions/issues/155
https://github.com/httpwg/http-extensions/issues/156
/ Jonas
On Thu, Mar 10, 2016 at 3:07 PM, wrote:
> Hey Jonas,
>
> Please feel free to raise issues:
> https://github.com/httpwg/http-extensions/labels/client-hints
>
> Cheers,
> _
On Wed, Mar 9, 2016 at 11:53 PM, L. David Baron wrote:
> Although we've participated in the development of this work in the
> community group, this is an area that we're becoming less involved
> in.
>
> We're also concerned about the general applicability of this work
> to the Web. Our
On Mon, Mar 7, 2016 at 10:35 PM, Tim Guan-tin Chien
wrote:
> I am confused. In your proposal, are you referring to the chrome
> *user/embedder* of (e.g. shell.html), or a chrome
> *embedded* page (I am not aware of any example).
What I'm saying is that in pages that run with chrome privileges (l
I think the idea is a good one in general, though it would be good to
get data from Google on how it's been used in practice.
It's been quite a while since I reviewed the spec, so my thoughts
below might be outdated (or I might be misremembering).
There were two things that I found unfortunate ab
On Mon, Mar 7, 2016 at 9:51 PM, Tim Guan-tin Chien wrote:
> This implies the Gaia System app, which is framed by shell.html (a
> chrome document), will switch cookie jar when the default is changed,
> no?
No, the Gaia System app doesn't run as chrome (i.e. doesn't have a
system principal). So it
On Mon, Mar 7, 2016 at 1:55 PM, J. Ryan Stinnett wrote:
> By default, can't access the storage used by
> for cookies and other site data, making it hard to share page
> state across the two browser frame types. An additional feature mozbrowser noisolation> has been added, which gives the frame
On Sun, Feb 28, 2016 at 7:49 PM, Mike Lawther wrote:
> On Wed, Feb 24, 2016 at 6:56 AM Jonas Sicking wrote:
>>
>> On Tue, Feb 23, 2016 at 6:14 AM, Anne van Kesteren
>> wrote:
>> > On Tue, Feb 23, 2016 at 12:37 AM, Mike Lawther
>> > wrote:
>> &g
On Tue, Feb 23, 2016 at 6:14 AM, Anne van Kesteren wrote:
> On Tue, Feb 23, 2016 at 12:37 AM, Mike Lawther
> wrote:
>> I'm testing the water here :) Is this at all likely to fly?
>
> I think the problem with APNG, as opposed to other image formats,
> e.g., WebP, is that we already support it. If
On Fri, Jan 15, 2016 at 11:41 AM, Joshua Cranmer 🐧 wrote:
> On 1/15/2016 1:21 PM, Bobby Holley wrote:
>>
>> Has anyone measured recently whether there's still a significant perf win
>> to making IIDs 32-bit? If we stop using them as a versioning tool, we
>> could
>> potentially relax our uniquenes
Ship it!
On Thu, Jan 14, 2016 at 2:06 PM, William Chen wrote:
> *Summary*: WebKitCSSMatrix has been available for years in WebKit based
> browsers and has seen widespread usage on the web. This feature is
> currently available in Chrome, Safari and Edge. Mike Taylor has been
> working on standard
Hi Lars,
So if I understand correctly, this will still remain disabled by
default on all branches. However it will now be possible to test out
on all branches by flipping a pref?
If so that sounds great to me.
/ Jonas
On Thu, Jan 14, 2016 at 5:16 AM, Lars Hansen wrote:
> Until now the new Shar
Sounds good to me as well. As long as it's very clearly defined that
this doesn't return to the event loop and so UI events, timers,
network events, etc MUST NOT be processed between the tasks under any
circumstances.
I.e. something like:
function spinner() {
window.enqueueMicrotask(spinner)
}
s
What is the relationship between this WG and the spec draft at
http://www.w3.org/TR/credential-management-1/
Seems like there's potential for integration between the two?
/ Jonas
On Thu, Jan 7, 2016 at 10:14 AM, Richard Barnes wrote:
> Obviously, given the earlier FIDO thread here, I think thi
On Wed, Jan 6, 2016 at 12:50 PM, Robert O'Callahan wrote:
> On Wed, Jan 6, 2016 at 9:52 PM, Anne van Kesteren wrote:
>>
>> On Tue, Jan 5, 2016 at 10:18 PM, Robert O'Callahan
>> wrote:
>> > That's an option, but it's a very large problem that's very difficult to
>> > get right. And there are so m
On Tue, Jan 5, 2016 at 9:57 AM, smaug wrote:
>> I really liked a lot about the blame implementation that bonsai had,
>> unfortunately we don't have a running copy any more AFAIK so it's hard to
>> take a
>> look at it.
>>
>> For one thing instead of showing author and changeset (or version in CVS)
On Mon, Jan 4, 2016 at 5:46 PM, Robert O'Callahan wrote:
> On Tue, Jan 5, 2016 at 2:38 PM, Jeff Gilbert wrote:
>
>> > Essentially, we would extend the same API but allow the WDTStream
>> >> interface to apply to more HTML elements, not just HTMLCanvasElement,
>> >> HTMLImageElement, or HTMLVideoE
On Mon, Jan 4, 2016 at 4:54 PM, Robert O'Callahan wrote:
> On Tue, Jan 5, 2016 at 1:18 PM, Jonas Sicking wrote:
>>
>> A big problem is sticking HTML/CSS content into WebGL is that WebGL
>> effectively enables reading pixel data through custom shaders and
>> t
On Mon, Jan 4, 2016 at 3:09 PM, Kearwood "Kip" Gilbert
wrote:
> > IIRC, we don't believe WEBGL_security_sensitive_resources is viably
> > implementable in a safe way (timing attacks!), so I suggest ignoring
> > it.
> Perhaps enforcing a CORS-like model would be simpler to secure, by
> limiting wha
Yay!
(I agree that it's sad that we need to do this, but still "yay" for
being more compatible with the web).
/ Jonas
On Wed, Dec 30, 2015 at 10:40 PM, Daniel Holbert wrote:
> Summary:
> A good chunk of the web today (and particularly the mobile web)
> effectively relies on -webkit prefixed C
I think our implementation still has the problem that specifying
referrerpolicy="none-when-downgrade" on an element has no effect. This
is because the ReferrerPolicy enum uses the same value for RP_Unset,
RP_Default and RP_No_Referrer_When_Downgrade.
In general, that enum is a mess :(
Would be go
On Wed, Dec 2, 2015 at 2:13 PM, Robert O'Callahan wrote:
> 1) What I suggested: Whitelist vendor origins for access to their devices
> and have vendor-hosted pages ("Web drivers"?) expose "safe" API to
> third-party applications.
> 2) Design a permissions API that one way or another lets users aut
p and the successor API. I've got a
> similar list started related to crypto and future-proofing.
>
>
> On Tue, Dec 1, 2015 at 8:29 PM, Jonas Sicking wrote:
>>
>> Any chance that the API can be made a little more JS friendly? First
>> thing that stands out is the
Any chance that the API can be made a little more JS friendly? First
thing that stands out is the use of success/error callbacks rather
than the use of Promises.
Also the use of numeric codes, rather than string values, is a pattern
that the web has generally moved away from.
/ Jonas
On Tue, Dec
On Mon, Nov 30, 2015 at 7:38 AM, Henri Sivonen wrote:
> Other browsers don't support this extension, so it clearly can't be a
> requirement for the Web Platform
Generally speaking, I don't think this reasoning is entirely accurate.
We know that there's lots of browser-specific code paths out ther
On Sat, Nov 28, 2015 at 5:28 PM, Mike Hoye wrote:
> One key claim Stillman made, that " A system that takes five minutes to
> circumvent does not “raise the bar” in any real way", is perhaps true in an
> academic sense, but not in a practical one. We know a lot more than we did a
> decade ago abo
On Thu, Nov 19, 2015 at 5:38 PM, Boris Zbarsky wrote:
>> Though Service Workers do actually have a 'client' object which
>> represent window objects. So we could enable passing those as global
>> to the translate function.
>
> That's a good idea. Want to raise it with the webperf WG? Seems like
On Thu, Nov 19, 2015 at 3:05 PM, Xidorn Quan wrote:
> On Fri, Nov 20, 2015 at 6:22 AM, Jonas Sicking wrote:
>> I'll give the same feedback here as I did for .
>>
>> I don't think authors will use this very much unless they can style it.
>
> This pair of
On Thu, Nov 19, 2015 at 2:48 PM, Boris Zbarsky wrote:
> On 11/19/15 5:39 PM, Jonas Sicking wrote:
>>
>> This API doesn't seem to work for nested workers (which Blink doesn't
>> implement), does it? Since there's no way in the window to get hold of
>>
This API doesn't seem to work for nested workers (which Blink doesn't
implement), does it? Since there's no way in the window to get hold of
a reference of a sub-sub-worker.
It also doesn't seem possible for a worker to convert to the timeline
of a parent window, since there's no object representi
I'll give the same feedback here as I did for .
I don't think authors will use this very much unless they can style it.
In this case enabling styling might not actually be that hard either,
so especially worth looking into.
/ Jonas
On Thu, Nov 19, 2015 at 1:21 AM, Ting-Yu Lin wrote:
> Summary:
On Sun, Nov 1, 2015 at 3:06 PM, Xidorn Quan wrote:
> On Fri, Oct 30, 2015 at 6:57 PM, Jonas Sicking wrote:
>> On Fri, Oct 30, 2015 at 12:36 AM, Xidorn Quan wrote:
>>> Authors sometimes just want something usable. It doesn't matter if it
>>> is not stylable, o
On Fri, Oct 30, 2015 at 12:36 AM, Xidorn Quan wrote:
> Authors sometimes just want something usable. It doesn't matter if it
> is not stylable, or it doesn't fit in the UI. When they really need to
> start caring about such things, they can switch to use jQuery UI then.
I think this is true for a
On Thu, Oct 29, 2015 at 9:38 PM, Xidorn Quan wrote:
> On Fri, Oct 30, 2015 at 10:25 AM, Ehsan Akhgari
> wrote:
>> On 2015-10-29 7:21 PM, Carlos Valim Coragem wrote:
>>>
>>> It seems that this problem only happens in the desktop version and not
>>> in
>>> mobile, I just did a test with the sam
Please make sure to coordinate with the FirefoxOS release team since
Gecko 44 is the release that will be used for FirefoxOS 2.5.
/ Jonas
On Wed, Oct 28, 2015 at 1:10 PM, Sylvestre Ledru wrote:
> Hello,
>
> Because we want to synchronize the release of 42 and 44 devedition (next
> Tuesday),
> we
On Mon, Oct 26, 2015 at 8:27 PM, Nicholas Nethercote
wrote:
> On Tue, Oct 27, 2015 at 10:26 AM, Jonas Sicking wrote:
>>
>> The question is, do we fix that friction by making collaboration
>> easier, or do we fix it by reducing collaboration.
>
> Yes. Merging c-c into
On Mon, Oct 26, 2015 at 3:45 PM, Nicholas Nethercote
wrote:
> On Mon, Oct 26, 2015 at 11:39 AM, Jonas Sicking wrote:
>>
>> Given that people are already feeling pressure to fix up thunderbird
>> code when they land patches, I can only see that pressure increasing
>>
On Mon, Oct 26, 2015 at 9:20 AM, Robert Kaiser wrote:
> Jonas Sicking schrieb:
>>
>> I definitely think that some aspects of Firefox development has gotten
>> easier thanks to the split.
>
> I'd like to see which. I don't see much that has gotten easier *beca
On Fri, Oct 23, 2015 at 4:30 PM, Gregory Szorc wrote:
> If we (m-c build peers) didn't care about comm-central at all, I can pretty
> much guarantee that comm-central would be perpetually broken once m-c build
> system improvements ramp up in the months ahead. C-c's contributors would
> have to sp
On Fri, Oct 23, 2015 at 3:53 PM, Joshua Cranmer 🐧 wrote:
>> The goal of putting seamonkey and thunderbird in separate trees has
>> always been to make firefox development easier, not harder. That
>> should include the build system.
>
> And the point of this thread is that it hasn't, and I can't em
On Fri, Oct 23, 2015 at 3:11 PM, Gregory Szorc wrote:
>
> We'll be investing pretty heavily in the Firefox build system in 2016. I
> cannot stress enough the pain comm-central's existence as a separate
> repository gives us when trying to make build system, mach, and automation
> changes. It slows
On Fri, Oct 23, 2015 at 11:17 AM, Joshua Cranmer 🐧 wrote:
>> I'm sorry that it makes you sad, but Mozilla has explicitly decided to
>> prioritize the bar to entry for Firefox development, and the speed of
>> development of Firefox, at the expense of Thunderbird (and seamonkey). And
>> as Firefox d
On Tue, Oct 20, 2015 at 2:49 AM, Mounir Lamouri wrote:
> Should we add this to the Screen Orientation specification?
I think so yes.
/ Jonas
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
As someone pushing for the ScreenOrientation API, I agree with this
intent nonetheless.
It *might* be worth warning about this property being inconsistent,
and that it's better for users to use the ScreenOrientation API. But I
think it's really only worth doing if this is something that other
brow
On Sun, Oct 18, 2015 at 4:14 PM, Nicholas Nethercote
wrote:
>
>> not more ways for the user to tell the build system "only rebuild some
>> stuff".
>
> ... except that bholley and ehsan are asking for a way to override the
> dependency tracking and just rebuild particular directories. Which is
> r
On Fri, Oct 16, 2015 at 11:44 AM, Boris Zbarsky wrote:
> So if you want to have value type like behavior, use a value type; for now
> long long (in IDL terms; Number in JS terms) is good
FWIW, when the problems with using Date objects in attributes were
raised with TC39, their recommendation afte
On Fri, Oct 16, 2015 at 9:20 AM, Martin Thomson wrote:
> On Fri, Oct 16, 2015 at 6:39 AM, Boris Zbarsky wrote:
>> You should _especially_ not create attributes of type Date.
>
>
> Well, that's interesting. I think that I might have to eat crow:
> https://github.com/w3c/webrtc-pc/issues/324
>
> I
Should we try to remove support for "Date" from our webidl implementation?
There's relatively few uses of it in our tree. Many are from tests,
and most of the remaining ones are from FirefoxOS certified APIs which
can be changed easily changed.
And in a few of the remaining cases we can change fr
On Sat, Oct 10, 2015 at 9:26 PM, wrote:
> On Saturday, October 10, 2015 at 4:28:30 AM UTC-7, Mounir Lamouri wrote:
>> 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
> |mach build binaries| is much slower for me than the present behavior,
> because I often hack on header files that are included all over the tree,
> but whose #include-ers generally don't need to be rebuilt all of the time.
Before we had mach, I had an alias for linking libxul. If there is a
sim
Yay! Ship it!
On Wed, Oct 14, 2015 at 10:40 AM, Kyle Huey wrote:
> I intend to ship the following features in Gecko 44:
>
> IDBObjectStore.getAll
> IDBObjectStore.getAllKeys
> IDBObjectStore.openKeyCursor
> IDBIndex.getAll
> IDBIndex.getAllKeys
>
> These features will be available on all platform
It's pretty easy to enable access to specific settings in mozSettings
to lower privileged content these days.
If it is acceptable that the pages have to be part of an installed app
(hosted or packaged), then all it takes is adding a few entries to
PermissionsTable.jsm
/ Jonas
On Tue, Oct 13, 201
On Fri, Oct 2, 2015 at 1:03 PM, Ehsan Akhgari wrote:
> On 2015-10-02 2:42 PM, Jonas Sicking wrote:
>>
>> It might still mean that we can save time on tryserver if we only
>> build these by default if the user has opted in to running the
>> relevant tests.
>>
It might still mean that we can save time on tryserver if we only
build these by default if the user has opted in to running the
relevant tests.
I agree with Gregory. I really don't see much value in building these
binaries by default. For the people that use them often enough that
they are worth
On Sep 26, 2015 09:33, "Eric Rescorla" wrote:
>
> On Fri, Sep 25, 2015 at 3:20 PM, wrote:
>
> > On Saturday, September 19, 2015 at 8:15:50 PM UTC+2, Eric Rescorla
wrote:
> > > On Sat, Sep 19, 2015 at 11:09 AM, Oliver Lietz
wrote:
> > >
> > > > Hi,
> > > > our nanoStream plugin supports live enco
On Tue, Sep 22, 2015 at 11:16 PM, Eric Rescorla wrote:
>> The api has been extensively discussed with all browser vendors and has
>> changed substantially in response to this
>
> Can you please point me to those changes and to the security analysis?
Security wasn't discussed much in these convers
On Sep 21, 2015 11:57, "Eric Rescorla" wrote:
>
> On Mon, Sep 21, 2015 at 11:23 AM, Jonas Sicking wrote:
>>
>> Note that this, similarly to clipboard integration, is already exposed
>> to the web through flash. So the main goal of this feature is to
>> e
On Sep 21, 2015 11:57, "Eric Rescorla" wrote:
>
> On Mon, Sep 21, 2015 at 11:23 AM, Jonas Sicking wrote:
>>
>> Note that this, similarly to clipboard integration, is already exposed
>> to the web through flash. So the main goal of this feature is to
>> e
Note that this, similarly to clipboard integration, is already exposed
to the web through flash. So the main goal of this feature is to
enable developers to migrate off of flash and instead use Gecko.
That said, if there are ways we can improve the UI here to further
explain to users what is going
On Thu, Sep 10, 2015 at 5:27 PM, Tantek Çelik wrote:
>> On 09/10/2015 06:36 PM, Jonas Sicking wrote:
>> > If I am the only one that wants to put in a formal objection here,
>> > then I'll let it go and go with whatever everyone else think we
>> > should d
If I am the only one that wants to put in a formal objection here,
then I'll let it go and go with whatever everyone else think we should
do.
/ Jonas
On Wed, Sep 9, 2015 at 11:22 PM, L. David Baron wrote:
> On Tuesday 2015-09-08 23:25 -0700, Jonas Sicking wrote:
>> On Tue, Sep 8
On Wed, Sep 9, 2015 at 8:16 AM, L. David Baron wrote:
> On Tuesday 2015-09-08 23:25 -0700, Jonas Sicking wrote:
>> On Tue, Sep 8, 2015 at 5:33 PM, Tantek Çelik wrote:
>> > On Wed, Aug 19, 2015 at 3:16 AM, Henri Sivonen
>> > wrote:
>> >> On Sun, Aug 9,
On Tue, Sep 8, 2015 at 5:33 PM, Tantek Çelik wrote:
> On Wed, Aug 19, 2015 at 3:16 AM, Henri Sivonen wrote:
>> On Sun, Aug 9, 2015 at 9:59 PM, L. David Baron wrote:
>> > The W3C is proposing revised charters for:
>> >
>> > Web Platform Working Group:
>> > http://www.w3.org/2015/07/web-platfo
I'm ok with implementing this. My biggest concern has always been
fingerprinting, and I think that we'll need some way to deal with
active (i.e. client-side) fingerprinting anyway, so I don't think this
makes a big difference either way.
/ Jonas
On Tue, Sep 8, 2015 at 12:21 PM, Luke Wagner wrote
On Mon, Aug 24, 2015 at 11:57 PM, 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
I'm less psyched about Permissions.request, but looking forward to
having .query ship!
Does it also work in workers?
/ Jonas
On Sat, Aug 22, 2015 at 5:03 AM, Birunthan Mohanathas
wrote:
> Hi,
>
> navigator.permissions.query has been Nightly-only for a few weeks. We
> are going to let it ride th
On Tue, Aug 18, 2015 at 2:39 PM, Ehsan Akhgari wrote:
> On 2015-08-18 5:37 PM, Tanvi Vyas wrote:
>> It is nice to see that we are moving towards an "Accept third party
>> cookies and data" setting instead of just "Allow third party cookies".
>> Will localstorage and sessionstorage also start honor
Yay!
On Mon, Aug 17, 2015 at 1:55 PM, William Chen wrote:
> Summary: The Screen Orientation API provides the ability to read the screen
> orientation type and angle, to be informed when the screen orientation
> state changes, and be able to lock the screen orientation to a specific
> state. We ha
On Sun, Aug 9, 2015 at 11:59 AM, L. David Baron wrote:
> The W3C is proposing revised charters for:
>
> Web Platform Working Group:
> http://www.w3.org/2015/07/web-platform-wg.html
> https://lists.w3.org/Archives/Public/public-new-work/2015Jul/0020.html
...
>
> The Web Platform Working Group
On Sun, Aug 9, 2015 at 2:51 AM, Anne van Kesteren wrote:
> On Sun, Aug 9, 2015 at 4:00 AM, Andrew Sutherland
> wrote:
>> Are there any plans to surface the contents of
>> https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIEffectiveTLDService
>> from https://publics
On Thu, Aug 6, 2015 at 1:07 AM, Anne van Kesteren wrote:
>> A simple solution here would be to simply use MutationObservers to
>> detect when the last is removed. Any time that layout
>> properties are queried after that they could behave like they
>> currently do, i.e. force a synchronous layout
On Thu, Aug 6, 2015 at 12:53 AM, Anne van Kesteren wrote:
> On Tue, Aug 4, 2015 at 9:10 PM, James Burke wrote:
>> If the meta tag, or whatever the toggle becomes, is set, then I expect
>> if the page's JS asks for a DOM element's box properties, it will get
>> values like 0 for sizes, since I bel
On Tue, Aug 4, 2015 at 10:06 AM, Bobby Holley wrote:
> How about a scheme in which there can be N such elements, and the
> painting only happens when all of them are gone (or some timeout occurs)?
> That solve the common case that Jonas is talking about, and allows libraries
> to insert their own
Fingerprinting doesn't seem useful if the fingerprint changes every
few minutes as the battery level changes.
I do agree that there are concerns that if the user has
private-browsing pages and non-private-browsing pages open at the same
time, that the pages can track when exactly the battery level
On Tue, Aug 4, 2015 at 2:55 AM, Anne van Kesteren wrote:
> On Tue, Aug 4, 2015 at 11:07 AM, James Graham wrote:
>> I am extremely wary of designing a solution like this where there's a single
>> master switch that any code can unilaterally flip; if the assumption that
>> libraries will never want
On Mon, Aug 3, 2015 at 6:03 PM, Mike Hommey wrote:
> On Mon, Aug 03, 2015 at 05:55:01PM -0700, Jonas Sicking wrote:
>> On Mon, Aug 3, 2015 at 5:06 PM, Karl Tomlinson wrote:
>> > but I don't see much advantage of public constructors over
>> > something like
>>
On Mon, Aug 3, 2015 at 5:06 PM, Karl Tomlinson wrote:
> but I don't see much advantage of public constructors over
> something like
>
> static already_AddRefed Foo::Create()
>
> or
>
> static nsRefPtr Foo::Make()
Fair enough. Though it is somewhat more boilerplate in the class
itself. But may
On Mon, Aug 3, 2015 at 12:32 AM, Anne van Kesteren wrote:
> On Mon, Aug 3, 2015 at 9:23 AM, Jonas Sicking wrote:
>> I think something like a might be a
>> simpler solution here. Coupled with either simply removing the
>> from the DOM, or having a function which indica
On Sun, Aug 2, 2015 at 11:12 PM, Anne van Kesteren wrote:
> On Mon, Aug 3, 2015 at 7:59 AM, Jonas Sicking wrote:
>> Ah, yes, that makes sense.
>
> Is this yet another API where we want to basically have an internal
> list of promises?
>
> someInstance.doNotRenderUntil(
On Sun, Aug 2, 2015 at 10:28 PM, Robert O'Callahan wrote:
> On Mon, Aug 3, 2015 at 4:53 PM, Jonas Sicking wrote:
>>
>> The need is not for an event, no? But rather for an API which allows
>> the page to tell the browser that it's ready for initial rendering?
>
On Sun, Aug 2, 2015 at 3:47 AM, Xidorn Quan wrote:
> On Sun, Aug 2, 2015 at 7:57 PM, Kyle Huey wrote:
>> On Sun, Aug 2, 2015 at 2:56 AM, Hubert Figuière wrote:
>>> On 02/08/15 04:55 AM, smaug wrote:
A new type of error 'auto' seems to cause, now seen on m-i, is
auto foo = new SomeRefCo
On Sun, Aug 2, 2015 at 2:41 PM, Robert O'Callahan wrote:
> On Mon, Aug 3, 2015 at 8:15 AM, Jonas Sicking wrote:
>>
>> Often times the "chrome" of a webapp is ready before various other
>> things that are loaded during initial page load is loaded.
>
> OK
On Sun, Aug 2, 2015 at 2:03 AM, Robert O'Callahan wrote:
> On Sun, Aug 2, 2015 at 11:58 AM, Zibi Braniecki <
> zbigniew.branie...@gmail.com> wrote:
>
>> So maybe we would need another event that the website fires to indicate
>> when it for paint/cache/screenshot.
>
> Assuming pages have an easy wa
On Sat, Aug 1, 2015 at 12:30 PM, Zibi Braniecki
wrote:
> 2) We want to bring app to foreground/paint it only when the app's chrome is
> visually complete.
I would very much want this. Right now, during a navigation from page
A to page B I believe that we render A until we've parsed B's opening
On Tue, Jul 28, 2015 at 7:52 AM, Jesper Kristensen
wrote:
> Den 28-07-2015 kl. 02:05 skrev Jonas Sicking:
>>
>> I don't think registerProtocolHandler has nearly enough API surface to
>> support what's needed here. But if you mean copying the idea that
>> the
On Mon, Jul 27, 2015 at 4:31 AM, Ted Mielczarek wrote:
> On Fri, Jul 24, 2015, at 12:43 PM, Jonas Sicking wrote:
>> On Fri, Jul 24, 2015 at 3:49 AM, David Rajchenbach-Teller
>> wrote:
>> > On 24/07/15 11:38, Jonas Sicking wrote:
>> >> I think we should allo
g on the desktop support. I suspect there will be more things to
point to once the initial support has landed.
/ Jonas
> Best Regards,
> Shih-Chiang Chien
> Mozilla Taiwan
>
> On Mon, Jul 27, 2015 at 6:31 AM, Jonas Sicking wrote:
>>
>> On Sat, Jul 25, 2015 at 7:14 AM,
1 - 100 of 344 matches
Mail list logo
