davidbgk
/
larlet-fr-david
Watch 1
Star 0
Fork 0
Code Releases 0 Activity
Repository with sources and generator of https://larlet.fr/david/ https://larlet.fr/david/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
896 Commits
1 Branch
Tree: ffaa972798
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'ffaa972798'
${ noResults }
larlet-fr-david/david/stream/2015/08/20/index.md

index.md 1.4KB
Raw Normal View History

Add initial content
4 years ago
​
​
​
​
​
​
​
​
 123456789 
  1. title: Continuité de lecture

  2. 

  3. > The HTML5 history API is a standardized way to manipulate the browser history via script. Part of this API — navigating the history — has been available in previous versions of HTML. The new parts in HTML5 include a way to add entries to the browser history, to visibly change the URL in the browser location bar (without triggering a page refresh), and an event that fires when those entries are removed from the stack by the user pressing the browser’s back button. This means that the URL in the browser location bar can continue to do its job as a unique identifier for the current resource, even in script-heavy applications that don’t ever perform a full page refresh.

  4. >

  5. > <cite>*[History API - Dive Into HTML5](http://diveintohtml5.info/history.html)* ([cache](/david/cache/897f370c439ad4b431206ec71e5dc4fa/))</cite>

  6. 

  7. Je rencontre de plus en plus le *pattern* qui consiste à charger d’autres articles à la suite de celui affiché initialement et à se servir de la capacité à pouvoir modifier l’historique du navigateur pour lier soit vers l’article en cours de lecture, soit vers la liste des articles. La pertinence dépendant de la taille de la lecture.

  8. 

  9. C’est tentant à plus d’un titre, surtout pour de la lecture de contenus courts, en mode *stream*. Le *scroll* me semblant être la navigation la plus aisée, est-ce qu’une telle pratique vous a déjà désorienté ?