On Wed, Jul 22, 2015 at 11:06 PM, Jonas Sicking wrote:
> On Wed, Jul 22, 2015 at 3:38 AM, Bevis Tseng wrote:
> > To prevent exposing too much in the web api level unnecessarily,
> > instead of creating new attribute in Navigator.webidl,
> > we could define the ImsHandler as one attribute of MozM
go into the WebIDE open platform preferences search for push and click
default at the push useragent
2015-07-22 20:19 GMT+02:00 Michael Henretty :
>
> On Tue, Jul 21, 2015 at 1:34 AM, Jovan Gerodetti
> wrote:
>
>> after I played around for some time I accidentally reset my Push user
>> agent and
On Tue, Jul 21, 2015 at 1:34 AM, Jovan Gerodetti
wrote:
> after I played around for some time I accidentally reset my Push user
> agent and suddenly the app was able to register again...
How did you reset your Push user agent?
___
dev-b2g mailing lis
On Wed, Jul 22, 2015 at 3:38 AM, Bevis Tseng wrote:
> To prevent exposing too much in the web api level unnecessarily,
> instead of creating new attribute in Navigator.webidl,
> we could define the ImsHandler as one attribute of MozMobileConnection and
> remove mozImsManager from Navigator, since
On Wed, Jul 22, 2015 at 1:57 AM, Martin Thomson wrote:
> I think that building these sorts of features into the web platform at
> large is a very bad idea.
I assume that this API is only going to be exposed to "certified
apps". Effectively that means that it's no more exposed to the web
than any
To prevent exposing too much in the web api level unnecessarily,
instead of creating new attribute in Navigator.webidl,
we could define the ImsHandler as one attribute of MozMobileConnection and
remove mozImsManager from Navigator, since it's only related to the IMS
registration and is also suitabl
I think that building these sorts of features into the web platform at
large is a very bad idea.
I appreciate that we operate under different constraints for Firefox
OS devices that might have native support for IMS on the baseband chip
and that we don't have much hope of convincing the industry o
