On Thu, Oct 8, 2015 at 9:10 AM, 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 homescreen on Chrome Android has a background_color information, it
> will be used while the p
On Tue, Sep 22, 2015 at 4:50 PM, Zibi Braniecki
wrote:
> This sort of repeatable-promise, would reduce it to:
> 1) Set the repeatable promise on the target
>
> Sounds like it would make much easier to write async code without logic for
> preventing race conditions.
>
> Is there any other approach
On Tue, Aug 18, 2015 at 1:22 PM, Zibi Braniecki
wrote:
> My concern here is that if we don't, we're basically saying that the right
> way to write webapps, is to put their content in a template and then inject
> the template into body when we're done with startup JS.
There are other approaches
On Tue, Aug 11, 2015 at 5:17 PM, James Burke wrote:
> https://github.com/jrburke/fxos-startup-test
>
> There are three variations mentioned in the README, each with a
> profile.sh capture "Profile" link:
I did a pass at the "Regular" profile and put the notes
On Thu, Aug 6, 2015 at 1:07 AM, Anne van Kesteren wrote:
> I think at this point it would be nice if we reached out to other
> browsers to see if they have any thoughts on this kind of API. James,
> would you be willing to email either public-weba...@w3.org or
> wha...@whatwg.org?
First, given a
On Tue, Aug 4, 2015 at 1:52 PM, Bobby Holley wrote:
> On Tue, Aug 4, 2015 at 12: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 li
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
On Thu, Jul 30, 2015 at 1:28 PM, Jeff Muizelaar wrote:
> Can't you just make everything display:none until you're ready to show it?
Just using display: none seems like it will run into the same problem
that prompted bug 863499, where the browser did some render/paints of
a white page, which took
There are some forces at play in a web app that point to wanting to delay
layout and rendering until a web app gives a signal that it should start:
* ECMAScript modules, and even developer constructed JS module systems
today, rely on async loading of scripts.
* Custom elements need their JS regis
The details are in:
https://bugzilla.mozilla.org/show_bug.cgi?id=1135960
In the gaia email app, we have come across a case where a clientHeight
check in a function leads to synchronous notification of a transitionend
listener, which then leads to the same function being called and completed
while
Is there a place where I can follow the plan for enabling
document.registerElement for wider web usage? Right now is is only
available behind an about:config setting or if an app is a certified app.
I am just interested in the machinery for document.registerElement/custom
elements to be available,
On 6/18/14 12:20 PM, Ben Francis wrote:
On Wed, Jun 18, 2014 at 6:59 PM, James Burke <mailto:jbu...@mozilla.com>> wrote:
So, I think we just need to set the expectation for at least
another year or two, that the gaia set of apps will not be able to
be "privileged&quo
On 6/18/14 8:25 AM, Jonas Sicking wrote:
Another thing that will likely force us to use certified apps for now
is Web Components. We are only enabling those for certified apps for
now since we want to have freedom to make changes to the spec and the
implementation without worrying about breaking
On 6/17/14, 10:08 AM, Vivien Nicolas wrote:
That's true. Actually there are many other hacks that depends on the
fact that application are certified. So even if I would like to have
more apps as privileged apps just for the principle, it's not that
simple. And we may need to reconsider the |pri
On 6/16/14, 12:34 PM, Jet Villegas wrote:
I also propose that we make any required code changes in v2.0 so that
non-certified apps can't get unrestricted use of the font. All the options
proposed (#2,3, or 4,) have drawbacks, the common one being that they may be
overly restrictive.
The Gaia
15 matches
Mail list logo
