Page control arrows for PWA

[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…

[phenomlab]

@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

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

[crazycells]

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

[phenomlab]

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

[crazycells]

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

[phenomlab]

@crazycells Good point, thanks.

[crazycells]

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

[phenomlab]

@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.