Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Hsins

    (@hsins)

    Hi @cteduard,

    It’s a problem about user experience (UX). For example, assuming that there’re 30 posts/products per page.

    1. User visist the archive page, it shows the latest 30 posts (post 01-30). By scrolling down, the page will load another 30 posts (post 31-60). With the pushState() function, browser will add the https://domain/page/2 to history.
    2. When user visit any page and then click “Go Back / Previous Page” button on browser, the browser will goto the https://domain/page/2. However, that page will show posts 31-60 due to the layout template. Most users would be wondering why there’s no posts 01-30 now.

    There’re many approaches to enhance the user experience:

    • Switch to replaceState() function, then the browser history would not change. By the browser cache mechanism, it will go back that position.
    • Use sessionStorage to store the loaded data with AJAX.
    • Make https://domain/page/2 not only load preceding posts/products when scrolling down, but also the previous posts/products when scrolling up.
    Thread Starter Hsins

    (@hsins)

    Hmm… All themes can be considered “developer-friendly” as long as the developer’s skills are sufficient. I surely understand that these issues can be handled through custom CSS, but the reason for suggesting this is because it’s still somewhat troublesome.

    Additionally, not all users are developers, and being able to choose multiple fonts to implement font fallback functionality is likely a need for many users that I think:)

    Thread Starter Hsins

    (@hsins)

    Hi @creativethemeshq,

    The version of WordPress I’m using is exact 6.6.1. I’ve tried that steps, and the autoload field of blocksy_ext_local_google_fonts_settings option is still yes. Meanwhile, I’ve also tried to delete the existed fonts. The result is the same.

    Moreover, I found that the processes of deletion and downloading take more time than before.

Viewing 3 replies - 1 through 3 (of 3 total)