Richard MaherRichard Maher

My feedback

  1. 7,253 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      48 comments  ·  Microsoft Edge Developer » JavaScript  ·  Flag idea as inappropriate…  ·  Admin →
      Richard MaherRichard Maher commented  · 

      Please be advised that, as promised/threatened, I have added the Trip Summary page and you can now map and replay your trip on Google Maps.

      The new version of the code is at the same link https://drive.google.com/open?id=0B7Rmd3Rn8_hDNW1zSWRoXzBTclU

      Can someone please try it on Edge 16?

      Most important design/proposed-specification change is that TravelManager subscription should now be Client specific. The TravelEvent must contain the intended Client.id (TravelEvent.source.id). This means that the UA must monitor and filter GeoLocation updates per client. I have also added new demo functionality such as a Trip Summary that is displayed when you press the "Arrive" button. The trip can also be replayed onto Google Maps by pressing "Map Trip" or "Replay". If the last and next geolocation updates for the trip are both visible in the Map window then smooth Marker movement is achieved via CSS transitions.

      *PLEASE* help Background GeoLocation get up and help Web Apps compete with Native Apps!

      If there is something wrong with my TravelManager solution design then let me know. Tear holes in it!

      Richard MaherRichard Maher supported this idea  · 
      Richard MaherRichard Maher commented  · 

      As promised/threatened. The TravelManager.PollyFill.js file is all Edge developers need to implement in order to be the first browser out there with supportable background geolocation. See aaa_readme.txt here: - https://drive.google.com/drive/folders/0B7Rmd3Rn8_hDNW1zSWRoXzBTclU

      Richard MaherRichard Maher commented  · 

      To be fair to Edge Developers, this is a large effort requiring much coordination. (Especially, If Microsoft are to deliver Background Geolocation and Topic Push Message Subscription in Version 1)

      May I suggest that you also give Safari Devs at hurry up: -
      https://webkit.org/status/#specification-service-workers

      Richard MaherRichard Maher commented  · 

      @Jake Archibald *Please* stop blackballing Background Geolocation. Just try operating in a meritocracy for a change where the best ideas are approved by the best available minds. I know it was impertinent and insubordinate to attempt to bypass the W3C/IETF tentacles and go straight to engineering but please don't punish others for my folly!

      WebApps *need* Background Geolocation if we are to compete at all with Native Apps. Uber, Dominos, Deliveroo, GrindR, Facebook, Maps and on and ON.

      Stop this "Not invented here" nonsense and get on with it!

      Service Workers are the conduit; just make it happen!

      Are there no adults here?

      Richard MaherRichard Maher commented  · 

      And, finally, (Sorry for multiple replies) is the Service Worker GitHub "issue" that explains everything: -
      https://github.com/w3c/ServiceWorker/issues/745

      Richard MaherRichard Maher commented  · 

      And here is the link to what is monopolizing the F2F time of the cognescente: -
      https://github.com/w3c/ServiceWorker/issues/1053

      Richard MaherRichard Maher commented  · 

      Look mate, I don't think johnny-come-lately Microsoft should be lecturing anyone about the definition of ServiceWorker functionality.

      Once again, this is the link to the *very* recent F2F Tokyo session specifically and exclusively dealing with Service Worker issues. Yet, from that very agenda: -

      Foreign fetch

      Foreign fetch vs non-credentialed requests
      consider allowing static routing only for "foreign fetch" for anonymous requests
      Is there any way for a web page to see if their requests will be intercepted by a foreign fetch handler?
      Allow overlapping scopes
      clientId on ForeignFetchEvents
      registerForeignFetch({ origins, scope }) optional
      Define procedure to convert options object of <code>sw.register()
      Expose fragments cross-origin for subresources
      Foreign fetch and no-referrer Referrer Policy
      CORS pre-flight for foreign fetch
      Installing a foreign SW as part of a subresource request
      preload for Foreign Fetch

      Fetch & streams

      Consider mechanisms to bypass the service worker for things that we know won't be in it's cache
      Upload streams
      Fetch cancellation/control/observing

      Richard MaherRichard Maher commented  · 

      @David, I am sorry that the facts do not support your (and W3C's and IETF's) narrative of Background-Geolocation being completely divorced from Service-Workers. One merely needs to peruse the Tokyo F2F agenda (link posted in previous) to see just how much time background-fetch monopolized proceedings. To pretend via smoke and mirrors that "Fetch" is an intrinsic part of Service Workers but "Background Geolocation" is not would be to treat the user-base as absolute fools :-(

      Apart from that hypocrisy, let me please draw everyone's attention to the current Service Worker specification: - https://www.w3.org/TR/service-workers/#extensibility

      David, the fact that you, and others, may not be able to see the obvious plug-n-play correlation between this Service Worker Extensibility and Background GeoLocation is neither here nor there.

      Edge users voting for Service Workers ARE voting for background-geolocation, background Fetch and Background Notifications and so on.

      The cynical attempt to ring-fence funding and development effort toward the pet-projects of the privileged few is not something I will stand idly by and witness!

      Richard MaherRichard Maher commented  · 

      For those hoping that W3C/IETF will wake up to the background geolocation requirement, I'm afraid the answer is "Not this year" :-(
      https://github.com/w3c/ServiceWorker/issues/1053

      Still, at least the sponsors are getting value for their money and quality F2F time in Tokyo: -
      https://twitter.com/jaffathecake/status/848018836922093570

      You just can't be that productive via email or a conference call!

      Hav no idea what Microsoft representatives (Ali Alabbas, Jatinder Mann) were doing there

    • 28 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        5 comments  ·  Microsoft Edge Developer » JavaScript  ·  Flag idea as inappropriate…  ·  Admin →
        Richard MaherRichard Maher commented  · 

        As promised/threatened. The TravelManager.PollyFill.js file is all Edge developers need to implement in order to be the first browser out there with supportable background geolocation. See aaa_readme.txt here: - https://drive.google.com/drive/folders/0B7Rmd3Rn8_hDNW1zSWRoXzBTclU

        Richard MaherRichard Maher supported this idea  · 
      • 8,118 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          90 comments  ·  Microsoft Edge Developer » HTML  ·  Flag idea as inappropriate…  ·  Admin →
          Richard MaherRichard Maher commented  · 

          I don't understand what the alternative for HTML Imports is meant to be? Why the recalcitrance?

          Richard MaherRichard Maher supported this idea  · 
        • 11,319 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            97 comments  ·  Microsoft Edge Developer » HTML  ·  Flag idea as inappropriate…  ·  Admin →
            Richard MaherRichard Maher commented  · 

            Please provide an update later that 2015 :-(

            Richard MaherRichard Maher supported this idea  · 
          • 9,878 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              89 comments  ·  Microsoft Edge Developer » HTML  ·  Flag idea as inappropriate…  ·  Admin →
              Richard MaherRichard Maher commented  · 

              The future of Web development along with Shadow Dom, Templates, and Import.

              Add to ServiceWorkers and Background GeoLocation and these are exciting times indeed.

            • 1,820 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                22 comments  ·  Microsoft Edge Developer » JavaScript  ·  Flag idea as inappropriate…  ·  Admin →
                Richard MaherRichard Maher commented  · 

                Firebase Cloud Messaging (FCM) blows the W3C/IETF Success Prevention Depts out of the water!

                See my comment below 4-Jul-16. Edge engineers no longer have an excuse to hamstring Microsoft Hub Notification broadcasts. (NB: Firebase are also working on implementing background geolocation!!!)

                Broadcast Messaging and Topic Based subscription is now available to
                your WebApp just like native Apps thanks to FCM.

                https://firebase.google.com/docs/cloud-messaging/js/send-multiple

                I am absolutely ecstatic about this, as we all should be, and equally
                grateful to FCM for having managed to bypass the recalcitrance and sheer
                bloody-mindedness of spec-authors to provide functionality that everyone
                outside the ivory-towers was begging for.

                Anyway rejoice and be glad as Native Apps have one less stick to beat us
                over the head with. And you Firefox fans are no longer stuck with
                Mozilla's third-rate AutoPush!

                Now if we can only get background geolocation with ServiceWorkers
                nothing can stop WebApps: -
                https://github.com/w3c/ServiceWorker/issues/745

                Happy Days!!!

              Feedback and Knowledge Base