|
|
|
Learning English and discovering / understanding UK and US history with news stories, interactive articles, videos, podcasts, photos, cartoons, comics, illustrations, posters and interactive maps.
Les Anglonautes is optimized for Firefox (desktop) and Firefox focus (mobile).
Firefox is available in over 90 languages, and compatible with Windows, Mac and Linux.
Navigating between an Anglonautes page and an external page / link > Going back to scroll position
A left click will take you back to where you were on the previous Anglonautes page.
When navigating back from an external link to Anglonautes, Chrome and Firefox use a built-in browser engine feature called BFcache (Back-Forward cache) to try and restore your exact scroll position.
While this works seamlessly most of the time, several technical factors explain why it can fail, instantly dropping you back to the top of the page.
Disabling extensions helps fix the scroll issue
Many extensions—especially ad blockers, cookie pop-up dismitters, and translation tools— inject custom code into a web page.
Chrome and Firefox detect these modifications and, for security or structural reasons, completely disable the BFcache.
Without this cache, the browser cannot freeze the page, forcing it to rebuild Anglonautes from scratch and dropping you back at the top.
Other method
To guarantee you never lose your reading position on Anglonautes, avoid clicking external links directly.
Instead, use tabbed navigation.
Right-click on the external link and select "Open link in new tab", or simply click the link using your mouse's scroll wheel (middle-click).
This opens the external content separately while leaving your current Anglonautes tab open, completely frozen at your current line of text.
bfcache explained
The back/forward cache, or bfcache, is a performance-enhancing feature available in modern browsers that enables instant back and forward navigation between previously-visited pages.
It does this by storing a complete snapshot of a page as the user navigates away from it;
the browser can then quickly restore the snapshot if the user decides to return to it, rather than needing to repeat the network requests required to load the page.
The snapshot contains the entire page in memory, including the JavaScript heap; in-progress code is paused when the user navigates away and resumed when they return to the page.
A regular HTTP cache entry on the other hand contains only responses to previous requests.
The bfcache therefore provides faster results than the HTTP cache.
The downside is that bfcache entries require more resources, and create complexity in terms of how to represent in-progress code.
Some code features (for example the unload handler) are not compatible, so their presence on a page blocks it from using the bfcache.
The bfcache is great for performance, so it is in your interests to make sure your pages are not blocked from using it.
You can use the notRestoredReasons API to monitor whether pages are blocked from using the bfcache, and reasons why.
https://developer.mozilla.org/en-US/
Microsoft FP stats > 15 August 2026
55 327 embedded NPR podcasts
905 703 external hyperlinks
275 891 internal hyperlinks
8 676 style sheet links
all hyperlinks: 1 181 594
all files: 30 022
all images : 21 130
PRO-Sitemaps stats > 15 August 2026
7 200 pages
15 130 images
6 394 videos
Anglonautes is best viewed with Firefox on photo editing 2K / 4K monitors in full-screen mode.
First beautiful MC responsive design edition: December 2020.
First edition: September 2001.
Warning: graphic images / distressing content
Anglonautes ®
is a nonprofit, educational website.
No cookies. No ads. No paid links.
No donations. No bank account.
17 U.S. Code § 107
Limitations on exclusive rights: Fair use
Notwithstanding the provisions of sections 106 and 106A, the fair use of a copyrighted work, including such use by reproduction in copies or phonorecords or by any other means specified by that section, for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright. https://www.law.cornell.edu/uscode/text/17/107
|
|
|
