Skip to content

Page control arrows for PWA

Solved Customisation
27 2 15.1k 1
  • @phenomlab this works great! thanks a lot. And thanks to your JS codes, it is only activated on PWA, not on mobile…

    wrote on last edited by
    #21

    @crazycells Not sure if you are using the scroll-top function, but if you are, I have enhanced the position of the button and re-sized it to match the forward and back arrows as below

    bd290755-5232-4a4c-9801-aa23235c1563-image.png

    The scroll-top button is located on the bottom right.

  • @crazycells Not sure if you are using the scroll-top function, but if you are, I have enhanced the position of the button and re-sized it to match the forward and back arrows as below

    bd290755-5232-4a4c-9801-aa23235c1563-image.png

    The scroll-top button is located on the bottom right.

    wrote on last edited by
    #22

    @phenomlab yes I used it before but not very frequently… Maybe you should put it above… just because it is more intuitive…
    ^
    < >
    v

  • @phenomlab yes I used it before but not very frequently… Maybe you should put it above… just because it is more intuitive…
    ^
    < >
    v

    wrote on last edited by
    #23

    @crazycells Ok, but there’s no “scroll-down” 🙂

  • @crazycells Ok, but there’s no “scroll-down” 🙂

    wrote on last edited by
    #24

    @phenomlab yeah , I know 😄 not necessary, but “up” should be above right/left buttons I guess… that is how people would think…

  • @phenomlab yeah , I know 😄 not necessary, but “up” should be above right/left buttons I guess… that is how people would think…

    wrote on last edited by
    #25

    @crazycells Good point, thanks.

  • @crazycells Ok, but there’s no “scroll-down” 🙂

    wrote on last edited by
    #26

    @phenomlab but I guess “up” is on mobile, right? not PWA specific?

  • @phenomlab but I guess “up” is on mobile, right? not PWA specific?

    wrote on last edited by
    #27

    @crazycells it is, yes - I think I’ll leave it as there is no specific PWA CSS classes I know of. Well, you could use something like the below, but this means multiple CSS files for different operating systems.

    /**
    * Determine the mobile operating system.
    * This function returns one of 'iOS', 'Android', 'Windows Phone', or 'unknown'.
    *
    * @returns {String}
    */
    
    function getMobileOperatingSystem()
    {
      var userAgent = navigator.userAgent || navigator.vendor || window.opera;
      // Windows Phone must come first because its UA also contains "Android"
      if (/windows phone/i.test(userAgent))
      {
        return  "Windows Phone";
      }
    
      if (/android/i.test(userAgent))
      {
        return  "Android";
      }
    
      if (/iPad|iPhone|iPod/.test(userAgent) && !window.MSStream)
      {
        return  "iOS";
      }
    
      return  "unknown";
      // return “Android” - one should either handle the unknown or fallback to a specific platform, let’s say Android
    }
    

    Once you’re in that rabbit hole, it’s impossible to get out of it.


Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee ☕
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics