Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefox Refresh Button

  • No replies
  • 1 has this problem
  • 7 views
tamjk
tamjk
more options

I've implemented a single-page website (SPA) in the following way:

All HTML is in a single .html file, index.html. Alll CSS and JS are likewise consolidated into a single .css and .js file for each. The <main> section of the index.html file is sub-divided into separate <article> parts for each "page". On clicking each link in the nav bar, an immediately invoked script, PAGE.switchpage(newlinkid, newpageid, hist), will: 1. change the new page's <article> display to "block" and the current <article>'s display to "none". 2. highlight the nav bar link corresponding to the current page (except if it's the home page) 3. remove the hyperlink and cursor from the current page link in the nav bar. (If the current page is the home page, then hyperlinks and cursors are removed from the logo and logotype)

I implemented conventional use of the BACK and FORWARD buttons on the browser using the browser's history stack. For nav bar navigation, the third parameter (i.e. "hist") in the PAGE.switchpage(...)" script will always be false and this value triggers: 1. the addition of a JSON object (that provides enough information, e.g. newlinkid, newpageid, for generating the previous page-view) to the history stack 2. changes the "title" element of the .html page, e.g. from MySite | Home to MySite | About, to reflect the current view 3. changes the URL of the .html page to reflect the current view, e.g. from mysite.com to mysite.com/about.html

All the above implementations work well. The problem arises when I try to implement conventional functionality of the Refresh button on a browser. I created .html pages on the server root folder to match the various page states, i.e. about.html, services.html, contact.html, etc. In this way I hoped that after changing page page via the nav bar and seeing the resulting new URL on the address bar, a refresh click would simply reload that page from its version on the server. To make sure that the server pages were identifiable from their client-generated versions on the user's PC, I put in a small <meta name="version" content="off-server"/> element in the header.

To date, all refreshed pages (bar index.html page of course) are never the same as their counterparts on the server although they are in the right page-state, i.e. when the refresh button is clicked with mysite.com/about.html in the address bar I see the right page-state for About content. Neither does the URL on the address bar pertain to the page content - after refreshing the URL always reverts to "mysite.com". This means that the second refresh will always return to the home page rather than the page 2 refreshes previously.

I wish I knew exactly what process occurs when Refresh is clicked or even which documentation to read.

I've implemented a single-page website (SPA) in the following way: All HTML is in a single .html file, index.html. Alll CSS and JS are likewise consolidated into a single .css and .js file for each. The <main> section of the index.html file is sub-divided into separate <article> parts for each "page". On clicking each link in the nav bar, an immediately invoked script, ''PAGE.switchpage(newlinkid, newpageid, hist)'', will: 1. change the new page's <article> display to "block" and the current <article>'s display to "none". 2. highlight the nav bar link corresponding to the current page (except if it's the home page) 3. remove the hyperlink and cursor from the current page link in the nav bar. (If the current page is the home page, then hyperlinks and cursors are removed from the logo and logotype) I implemented conventional use of the ''BACK'' and ''FORWARD'' buttons on the browser using the browser's ''history'' stack. For nav bar navigation, the third parameter (i.e. "hist") in the ''PAGE.switchpage(...)" script will always be ''false'' and this value triggers: 1. the addition of a JSON object (that provides enough information, e.g. newlinkid, newpageid, for generating the previous page-view) to the history stack 2. changes the "title" element of the .html page, e.g. from ''MySite | Home'' to ''MySite | About'', to reflect the current view 3. changes the URL of the .html page to reflect the current view, e.g. from ''mysite.com'' to ''mysite.com/about.html'' All the above implementations work well. The problem arises when I try to implement conventional functionality of the ''Refresh'' button on a browser. I created .html pages on the server root folder to match the various page states, i.e. ''about.html'', ''services.html'', ''contact.html'', etc. In this way I hoped that after changing page page via the nav bar and seeing the resulting new URL on the address bar, a refresh click would simply reload that page from its version on the server. To make sure that the server pages were identifiable from their client-generated versions on the user's PC, I put in a small <meta name="version" content="off-server"/> element in the header. To date, all refreshed pages (bar ''index.html'' page of course) are never the same as their counterparts on the server although they are in the right page-state, i.e. when the refresh button is clicked with ''mysite.com/about.html'' in the address bar I see the right page-state for About content. Neither does the URL on the address bar pertain to the page content - after refreshing the URL always reverts to "mysite.com". This means that the second refresh will always return to the home page rather than the page 2 refreshes previously. I wish I knew exactly what process occurs when ''Refresh'' is clicked or even which documentation to read.