Page control arrows for PWA

[crazycells]

hi @phenomlab , when the forum is used as PWA, there is no easy way to navigate between pages…

Several days ago, I was reading a post on a forum that mentioned another topic, I have encountered an issue when attempting to return to the original post. So, after reading the linked topic, I had to go to categories page and retrace my steps to locate the topic I was reading initially…

Although this can be achieved by page control arrows on destop and mobile browsers, there is no easy way to achieve this on PWA… so I wonder if you can help me adding some page control buttons that appear at the bottom of the page when scrolled up. (maybe it can be integrated to post navigation bar but I believe those buttons should appear in all pages, not only in topics)

Here is just some suggestions to distinguish them from other arrows…

alternatively the arrows or rewind icons that YouTube uses can be used:

[phenomlab]

@crazycells Right - I’ve put together a base design on this site which will only fire when PWA mode is detected. It looks like the below - note the left and right arrows. They are “basic” but functional

CSS

/* START - CSS settings for PWA navigation */
    
.arrow {
  width: 40px;
  height: 40px;
  background-color: var(--bs-body-bg);
  text-align: center;
  line-height: 30px;
  cursor: pointer;
  font-size: 30px;
  border: 1px solid var(--bs-border-color);
  border-radius: var(--bs-border-radius);
}
.arrow.left, .arrow.right {
    margin-left: 10px;
    margin-right: 10px;
    align-content: center;
    position: fixed;
    top: 50%;
}
.arrow.right {
    position: fixed;
    right: 0;
}

/* END - CSS settings for PWA navigation */

JS

The below code does rely on serviceWorker but that’s typically present in all “modern” browsers

$(document).ready(function() {
  // Check if serviceWorker API is available
  if ('serviceWorker' in navigator) {
    // The browser supports service workers
    console.log('This web app supports service workers.');

    // Check if the app is installed (as PWA)
    if (window.matchMedia('(display-mode: standalone)').matches) {
      console.log('This web app is running as a Progressive Web App.');
      
      // Add HTML for navigation arrows
      $('body').append('<div class="navigation"><div class="arrow left">&lt;</div><div class="arrow right">&gt;</div></div>');

      // Handle click on left arrow
      $('.arrow.left').click(function() {
        history.back(); // Go back in history
      });

      // Handle click on right arrow
      $('.arrow.right').click(function() {
        history.forward(); // Go forward in history
      });
    } else {
      console.log('This web app is not running as a Progressive Web App.');
    }
  } else {
    console.log('This web browser does not support service workers.');
  }
});

Again, this is basic and more of a POC. Other functionality can be added in a similar way if you’d like it.

[phenomlab]

@crazycells haven’t forgotten. Working on this now and expect to have a usable POC you can try in the coming days.

[crazycells]

@phenomlab no problem at all, nothing is urgent please take your time and I really appreciate your help…

[phenomlab]

@crazycells Thanks

[phenomlab]

@crazycells Right - I’ve put together a base design on this site which will only fire when PWA mode is detected. It looks like the below - note the left and right arrows. They are “basic” but functional

CSS

/* START - CSS settings for PWA navigation */
    
.arrow {
  width: 40px;
  height: 40px;
  background-color: var(--bs-body-bg);
  text-align: center;
  line-height: 30px;
  cursor: pointer;
  font-size: 30px;
  border: 1px solid var(--bs-border-color);
  border-radius: var(--bs-border-radius);
}
.arrow.left, .arrow.right {
    margin-left: 10px;
    margin-right: 10px;
    align-content: center;
    position: fixed;
    top: 50%;
}
.arrow.right {
    position: fixed;
    right: 0;
}

/* END - CSS settings for PWA navigation */

JS

The below code does rely on serviceWorker but that’s typically present in all “modern” browsers

$(document).ready(function() {
  // Check if serviceWorker API is available
  if ('serviceWorker' in navigator) {
    // The browser supports service workers
    console.log('This web app supports service workers.');

    // Check if the app is installed (as PWA)
    if (window.matchMedia('(display-mode: standalone)').matches) {
      console.log('This web app is running as a Progressive Web App.');
      
      // Add HTML for navigation arrows
      $('body').append('<div class="navigation"><div class="arrow left">&lt;</div><div class="arrow right">&gt;</div></div>');

      // Handle click on left arrow
      $('.arrow.left').click(function() {
        history.back(); // Go back in history
      });

      // Handle click on right arrow
      $('.arrow.right').click(function() {
        history.forward(); // Go forward in history
      });
    } else {
      console.log('This web app is not running as a Progressive Web App.');
    }
  } else {
    console.log('This web browser does not support service workers.');
  }
});

Again, this is basic and more of a POC. Other functionality can be added in a similar way if you’d like it.

[crazycells]

@phenomlab thank you very much

[crazycells]

@crazycells what would be the z-index value to hide it when the navigation menu options appear? I believe they should be invisible when those options panels are opened…

[phenomlab]

@crazycells yeah, I set that quite high at 9999 which is complete overkill! Try lowering that value to something more sane like 1500

[phenomlab]

@crazycells I think I found a bug. If you position a topic between the two navigation arrows on a mobile device, you cannot click that topic until you scroll up or down past the arrows. I noticed this last night and will address it.

[phenomlab]

A better explanation of that is below

As you can see from the developer view, the width: 100%; sits over the top of the topic meaning it cannot be clicked or tapped. A workaround here should be to set z-index: -1; on the navigation class, but whilst that resolves the ordering issue, it means the navigation buttons no longer work as they sit under the content.

[phenomlab]

Fixed. Change the CSS block (original post is also updated) to the below

/* START - CSS settings for PWA navigation */
    
.arrow {
  width: 40px;
  height: 40px;
  background-color: var(--bs-body-bg);
  text-align: center;
  line-height: 30px;
  cursor: pointer;
  font-size: 30px;
  border: 1px solid var(--bs-border-color);
  border-radius: var(--bs-border-radius);
}
.arrow.left, .arrow.right {
    margin-left: 10px;
    margin-right: 10px;
    align-content: center;
    position: fixed;
    top: 50%;
}
.arrow.right {
    position: fixed;
    right: 0;
}

/* END - CSS settings for PWA navigation */

[crazycells]

I have not tested them in details yet, but I will let you know about any bugs for sure

Additionally, is there any reason that they are in the middle but not close to the bottom? That is usually where the fingers will be

[phenomlab]

@crazycells They can be anywhere you’d prefer. You can just change the .arrow.left, .arrow.right class to move to the preferred position. Currently, it’s set at 50%, but can be any value you want to reach the desired position. In this case, it would probably be better to substitute top for bottom and set the position in px to ensure the placement is the same no matter which screen estate you have.

For example

.arrow.left, .arrow.right {
    margin-left: 10px;
    margin-right: 10px;
    align-content: center;
    position: fixed;
    bottom: 120px;
}

That now means the page scroller (the button that appears bottom right) will be in the way, although on thinking about it, we already have a page navigation when you are in the topic, so no point in having another. That would be a minor alteration to the scroll top function to have it not appear on posts.

[crazycells]

@phenomlab thanks, yes, I will move them close to the menu bar, but I was asking in case there is a technical detail I was not aware…

[phenomlab]

@crazycells No, none that I am aware of - move them to where you’d prefer. In fact, I took your advice and moved them on Sudonix, which uses the CSS class I added in the previous post.

[crazycells]

@phenomlab yes, I believe this looks more natural, they are closer to the fingers and on the top of these, it is not blocking any content in the middle of the screen…

[phenomlab]

@crazycells Exactly. i’m going to hire you as a design guru! You have some great ideas on what Sudonix should look like and I’m grateful for any contribution that enhances what I hope is already a good experience.

[crazycells]

@phenomlab It is nice to hear that I am able to contribute your website

[phenomlab]

@phenomlab said in Page control arrows for PWA:

That now means the page scroller (the button that appears bottom right) will be in the way, although on thinking about it, we already have a page navigation when you are in the topic, so no point in having another.

Based on the above point made, I have now disabled the scroll to top button inside topics.

[crazycells]

@phenomlab this works great! thanks a lot. And thanks to your JS codes, it is only activated on PWA, not on mobile…