Fossil SCM
Update the comments about back/forward caching.
Commit
e62b171dbc7a6f310d2ee98f6ec21d04f2d25df37a99c9cbcd89fb1d8554af5a
Parent
89a0438f8f3bf6e…
1 file changed
+5
-3
+5
-3
| --- src/graph.js | ||
| +++ src/graph.js | ||
| @@ -828,13 +828,15 @@ | ||
| 828 | 828 | ** A session cookie is preferred over other storage APIs because Fossil already |
| 829 | 829 | ** requires cookies to be enabled for reasonable functionality, and it's more |
| 830 | 830 | ** likely that other storage APIs are blocked by users for privacy reasons, for |
| 831 | 831 | ** example. |
| 832 | 832 | ** [1]: This feature only works with a normal (text) input field hidden by CSS |
| 833 | -** styles, instead of a true hidden (by type) input field, so may cause side | |
| 834 | -** effects, for example with screen readers. Moreover, this feature currently | |
| 835 | -** only works with Chrome, but not with FF or IE. | |
| 833 | +** styles, instead of a true hidden (by type) input field, but according to MDN, | |
| 834 | +** screen readers should ignore it even without an aria-hidden="true" attribute | |
| 835 | +** (which is even discouraged for hidden by CSS elements). Also, this feature | |
| 836 | +** breaks if disabled[=true] or tabindex="-1" attributes are added to the input | |
| 837 | +** field, or (in FF) if page unload handlers are present. | |
| 836 | 838 | ** |
| 837 | 839 | ** Ideas and TODOs: |
| 838 | 840 | ** |
| 839 | 841 | ** o Shortcut to select the topmost or bottommost entry, either by separate |
| 840 | 842 | ** key, or with modifiers (SHIFT+N, SHIFT+M)? |
| 841 | 843 |
| --- src/graph.js | |
| +++ src/graph.js | |
| @@ -828,13 +828,15 @@ | |
| 828 | ** A session cookie is preferred over other storage APIs because Fossil already |
| 829 | ** requires cookies to be enabled for reasonable functionality, and it's more |
| 830 | ** likely that other storage APIs are blocked by users for privacy reasons, for |
| 831 | ** example. |
| 832 | ** [1]: This feature only works with a normal (text) input field hidden by CSS |
| 833 | ** styles, instead of a true hidden (by type) input field, so may cause side |
| 834 | ** effects, for example with screen readers. Moreover, this feature currently |
| 835 | ** only works with Chrome, but not with FF or IE. |
| 836 | ** |
| 837 | ** Ideas and TODOs: |
| 838 | ** |
| 839 | ** o Shortcut to select the topmost or bottommost entry, either by separate |
| 840 | ** key, or with modifiers (SHIFT+N, SHIFT+M)? |
| 841 |
| --- src/graph.js | |
| +++ src/graph.js | |
| @@ -828,13 +828,15 @@ | |
| 828 | ** A session cookie is preferred over other storage APIs because Fossil already |
| 829 | ** requires cookies to be enabled for reasonable functionality, and it's more |
| 830 | ** likely that other storage APIs are blocked by users for privacy reasons, for |
| 831 | ** example. |
| 832 | ** [1]: This feature only works with a normal (text) input field hidden by CSS |
| 833 | ** styles, instead of a true hidden (by type) input field, but according to MDN, |
| 834 | ** screen readers should ignore it even without an aria-hidden="true" attribute |
| 835 | ** (which is even discouraged for hidden by CSS elements). Also, this feature |
| 836 | ** breaks if disabled[=true] or tabindex="-1" attributes are added to the input |
| 837 | ** field, or (in FF) if page unload handlers are present. |
| 838 | ** |
| 839 | ** Ideas and TODOs: |
| 840 | ** |
| 841 | ** o Shortcut to select the topmost or bottommost entry, either by separate |
| 842 | ** key, or with modifiers (SHIFT+N, SHIFT+M)? |
| 843 |