On 8 July 2015 at 04:41, Jonas Sicking jo...@sicking.cc wrote:
Given this, and given that I don't actually see a downside to
re-downloading the HTML page again, I definitely think that that's
what we should do.
Actually the conclusion I drew from the W3C GitHub thread [1] was that we
should
On 8 July 2015 at 04:36, Jonas Sicking jo...@sicking.cc wrote:
But how should we handle the case where the user navigates to a Firefox
App
in the browser (either a legacy hosted Open Web App or a new signed
streamable packaged app), and then tries to pin it? Would we a) just pin
it
like
On Tue, Jul 7, 2015 at 10:41 PM, Jonas Sicking jo...@sicking.cc wrote:
At the very least I'd like to see solid data on that CDNs most of the
time support updating the manifest in-place
I might be misreading the question, but I'll give it a try.
From both past work experience and vendor docs,
On Wed, Jul 8, 2015 at 3:30 AM, Benjamin Francis bfran...@mozilla.com wrote:
On 8 July 2015 at 04:36, Jonas Sicking jo...@sicking.cc wrote:
But how should we handle the case where the user navigates to a Firefox
App
in the browser (either a legacy hosted Open Web App or a new signed
On Wed, Jul 1, 2015 at 2:11 PM, Benjamin Francis bfran...@mozilla.com wrote:
On 16 June 2015 at 00:59, Jonas Sicking jo...@sicking.cc wrote:
We will definitely need a FirefoxOS-specific API which tracks the list
of URLs that have been bookmarked, and which maybe caches manifest
information as
On Wed, Jul 1, 2015 at 2:20 PM, Benjamin Francis bfran...@mozilla.com wrote:
On 16 June 2015 at 00:59, Jonas Sicking jo...@sicking.cc wrote:
One thing that is tricky is that in the new manifest spec the manifest
URL is meaningless. In order to update an icon we need to re-download
the HTML
On 7 July 2015 at 07:12, Jonas Sicking jo...@sicking.cc wrote:
So in practice, if we don't do any of this, and simply treat pins as
bookmarks, there will be relatively few downsides.
If, on the other hand, we stick pins in the application registry, the
main thing that would immediately
On 7 July 2015 at 07:21, Jonas Sicking jo...@sicking.cc wrote:
Generally speaking, CDNs use a new URL any time you want to change the
file contents.
Alex Russell claims this impression is outdated, that the vast majority of
modern CDNs do allow for stable URLs. How can we get some objective
On Tue, Jul 7, 2015 at 6:19 AM, Benjamin Francis bfran...@mozilla.com wrote:
On 7 July 2015 at 07:12, Jonas Sicking jo...@sicking.cc wrote:
So in practice, if we don't do any of this, and simply treat pins as
bookmarks, there will be relatively few downsides.
If, on the other hand, we stick
On Tue, Jul 7, 2015 at 6:29 AM, Benjamin Francis bfran...@mozilla.com wrote:
On 7 July 2015 at 07:21, Jonas Sicking jo...@sicking.cc wrote:
Generally speaking, CDNs use a new URL any time you want to change the
file contents.
Alex Russell claims this impression is outdated, that the vast
On 12 June 2015 at 18:41, Benjamin Francis bfran...@mozilla.com wrote:
Yeah that's really what I'm getting at. Do we still need
window.navigator.mozApps.install() ? If not then how do we do all the other
things that we currently register at install time? Do we need new
(internal?) APIs for
On 16 June 2015 at 00:59, Jonas Sicking jo...@sicking.cc wrote:
One thing that is tricky is that in the new manifest spec the manifest
URL is meaningless. In order to update an icon we need to re-download
the HTML file and see what manifest URL it points to.
This is especially problematic if
On 16 June 2015 at 00:59, Jonas Sicking jo...@sicking.cc wrote:
We will definitely need a FirefoxOS-specific API which tracks the list
of URLs that have been bookmarked, and which maybe caches manifest
information as needed. Likely this API would also need to send
notifications when pins are
On Tue, Jun 16, 2015 at 12:02 PM, Benjamin Francis bfran...@mozilla.com wrote:
On 16 June 2015 at 00:59, Jonas Sicking jo...@sicking.cc wrote:
We will definitely need a FirefoxOS-specific API which tracks the list
of URLs that have been bookmarked, and which maybe caches manifest
information
On 16 June 2015 at 00:59, Jonas Sicking jo...@sicking.cc wrote:
We will definitely need a FirefoxOS-specific API which tracks the list
of URLs that have been bookmarked, and which maybe caches manifest
information as needed. Likely this API would also need to send
notifications when pins are
On Fri, Jun 12, 2015 at 10:41 AM, Benjamin Francis bfran...@mozilla.com wrote:
On 12 June 2015 at 04:46, Paul Theriault ptheria...@mozilla.com wrote:
Thats correct. Though you are mixing things up a little here by throwing
in Activities. That’s not a permission, that’s just something that is
On 12 June 2015 at 04:46, Paul Theriault ptheria...@mozilla.com wrote:
Thats correct. Though you are mixing things up a little here by throwing
in Activities. That’s not a permission, that’s just something that is
registered at install time. (In the same way that system message listeners
are
On 11 June 2015 at 06:17, Paul Theriault ptheria...@mozilla.com wrote:
We discussed this in another thread, but Jonas convinced me that pinning
will not have any security side-effects, and I’ve updated the permission
model to reflect this [1].
To clarify, have you decided that granting extra
On 11 Jun 2015, at 10:39 pm, Benjamin Francis bfran...@mozilla.com wrote:
On 11 June 2015 at 06:17, Paul Theriault ptheria...@mozilla.com
mailto:ptheria...@mozilla.com wrote:
We discussed this in another thread, but Jonas convinced me that pinning will
not have any security side-effects,
On 4 May 2015 at 22:06, Jonas Sicking jo...@sicking.cc wrote:
The main thing that I think we should do is abandon the term app.
The term app is often associated with things like installing and
app store, both of which I'd like to move away from.
...
But I think we generally should just
One part I'm not sure about is if we're saying we want to grant permissions
based on pinning, how will Gecko know when a site is pinned? Currently an app
is registered in the app registry when it's installed via the Apps API using
its app manifest so that Gecko knows about it. What should
On 04/05/2015 23:06, Jonas Sicking wrote:
The second complexity is pinning. I think we should allow users to
pin websites to the homescreen. This should be possible for *any*
website, whether it has a W3C manifest, a FirefoxOS manifest, the
Apple-invented meta tags, or none of the above.
When
On Tue, May 5, 2015 at 7:14 PM, Paul Theriault ptheria...@mozilla.com wrote:
While I'm all for simplification, installation is a useful metaphor for
signalling user intent. Removing installation leaves us limited to prompts
only. Prompts are pretty limited in terms of a security mitigation and
While I’m all for simplification, installation is a useful metaphor for
signalling user intent. Removing installation leaves us limited to prompts
only. Prompts are pretty limited in terms of a security mitigation and we will
have a hard time authorising access to the privileged APIs,
Jonas Sicking mailto:jo...@sicking.cc
May 4, 2015 at 5:06 PM
Hi Peter,
I think we can and should simplify this actually.
The main thing that I think we should do is abandon the term app.
The term app is often associated with things like installing and
app store, both of which I'd like to move
Thanks Jonas/Eric.
Excellent points. Let me engage some folks on our UX team to get their
input and we'll summarize that on this thread.
A big thing that we need to grapple with are user expectations and
perceptions with respect to apps. Obviously we want to advance the
technology and change
Hi Peter,
I think we can and should simplify this actually.
The main thing that I think we should do is abandon the term app.
The term app is often associated with things like installing and
app store, both of which I'd like to move away from.
To be clear, I think we should still have our
Webmaker will create apps under the Web App or Web Site categories.
Nothing special needed.
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
thanks Peter, that's very clear.
what about apps created through webmaker ?
where would they fit ?
On 24/04/15 17:49, Peter Dolanjski wrote:
As an update, I've created a wiki for the summarized app types here:
https://wiki.mozilla.org/Gaia/App_Definitions#App_Types_Proposal
Please let me know
On Friday, April 24, 2015 at 5:49:25 PM UTC+2, Peter Dolanjski wrote:
As an update, I've created a wiki for the summarized app types here:
https://wiki.mozilla.org/Gaia/App_Definitions#App_Types_Proposal
Please let me know if you disagree with anything as this will be used as the
basis for
As an update, I've created a wiki for the summarized app types here:
https://wiki.mozilla.org/Gaia/App_Definitions#App_Types_Proposal
Please let me know if you disagree with anything as this will be used as
the basis for the app types that we will support going forward.
Thanks,
*Peter
Hello All,
There have been a number of discussion threads around the details
pertaining to the various forms of apps that are needed as we move forward
with new architecture (based on permissions, presence of a manifest,
etc.). A few of us (product, engineering, partner engineering,
Marketplace)
32 matches
Mail list logo
