Do we want to ignore notifications when app is in foreground (call onerror), or use a different mechanism, like a custom growl/toast, or something?
Either way, since the w3c spec does not specify how to delay local notifications or use push, there is nothing useful it can do on ios as is. I'll write some extension to schedule delayed notifications much like the existing LocalNotification plugin, but use the w3c spec wherever possible and with as much overlap with android as possible. Fun! On Tue, Oct 16, 2012 at 9:04 PM, Filip Maj <f...@adobe.com> wrote: > I can.. ? Not sure what your point is. > > On 10/16/12 5:56 PM, "Jesse" <purplecabb...@gmail.com> wrote: > >>You can't ring your doorbell from inside the house either ... >> >>On Tue, Oct 16, 2012 at 5:50 PM, Filip Maj <f...@adobe.com> wrote: >>> >>>>> - StatusBar Notifications: Intended for background services to >>>>>notify a >>>>> user to start some action (instead of just doing the action without >>>>>users' >>>>> explicit intent) -- so what does this mean for iOS without >>>>>background >>>>> services? >>>> >>>>I *think* a fallback to local notification would be the way to handle >>>>this. (But implementation will probably uncover better.) >>> >>> I think this is what tripped me up on iOS a few weeks ago when I >>>attempted >>> this myself :) >>> >>> On iOS, you _cannot_ dispatch a local notification (to the notification >>> center / status bar area) if the app is in the foreground. >>> >> >> >> >>-- >>@purplecabbage >>risingj.com >
