Fossil SCM
Fixed a poorly-placed wordwrap which looked like a new list entry to markup.
Commit
571bf459be99b10516d4582bd5ebeba0cb09a213af5790d4178afbf8e2689bf3
Parent
93e4561b0d56fe6…
1 file changed
+2
-2
+2
-2
| --- www/js-policy.md | ||
| +++ www/js-policy.md | ||
| @@ -48,12 +48,12 @@ | ||
| 48 | 48 | 1. "It's increases the size of the page download." |
| 49 | 49 | - For the fossil pages which make heavy use of JS, the initial page |
| 50 | 50 | transfer size may increase: 6-8kb (compressed) is typical, and it |
| 51 | 51 | may even go up to a whopping 15kb (as of this writing, it's 8kb |
| 52 | 52 | compressed on our most JS-intensive page (`/fileedit`), and only |
| 53 | - 25kb uncompressed and unobfuscated). With fossil's newer (summer | |
| 54 | - 2020) JS delivery mechanism and etags-related caching | |
| 53 | + 25kb uncompressed and unobfuscated). With fossil's newer (summer 2020) | |
| 54 | + JS delivery mechanism and etags-related caching | |
| 55 | 55 | improvements, such JS can be served with a single HTTP request and |
| 56 | 56 | cached by browsers for up to a year. Additionally, most pages |
| 57 | 57 | which use that much JS also use comparitively lightweight ajax |
| 58 | 58 | communication to eliminate page reloads and enable data-loss-free |
| 59 | 59 | recovery in certain error cases which would lose client-side edits |
| 60 | 60 |
| --- www/js-policy.md | |
| +++ www/js-policy.md | |
| @@ -48,12 +48,12 @@ | |
| 48 | 1. "It's increases the size of the page download." |
| 49 | - For the fossil pages which make heavy use of JS, the initial page |
| 50 | transfer size may increase: 6-8kb (compressed) is typical, and it |
| 51 | may even go up to a whopping 15kb (as of this writing, it's 8kb |
| 52 | compressed on our most JS-intensive page (`/fileedit`), and only |
| 53 | 25kb uncompressed and unobfuscated). With fossil's newer (summer |
| 54 | 2020) JS delivery mechanism and etags-related caching |
| 55 | improvements, such JS can be served with a single HTTP request and |
| 56 | cached by browsers for up to a year. Additionally, most pages |
| 57 | which use that much JS also use comparitively lightweight ajax |
| 58 | communication to eliminate page reloads and enable data-loss-free |
| 59 | recovery in certain error cases which would lose client-side edits |
| 60 |
| --- www/js-policy.md | |
| +++ www/js-policy.md | |
| @@ -48,12 +48,12 @@ | |
| 48 | 1. "It's increases the size of the page download." |
| 49 | - For the fossil pages which make heavy use of JS, the initial page |
| 50 | transfer size may increase: 6-8kb (compressed) is typical, and it |
| 51 | may even go up to a whopping 15kb (as of this writing, it's 8kb |
| 52 | compressed on our most JS-intensive page (`/fileedit`), and only |
| 53 | 25kb uncompressed and unobfuscated). With fossil's newer (summer 2020) |
| 54 | JS delivery mechanism and etags-related caching |
| 55 | improvements, such JS can be served with a single HTTP request and |
| 56 | cached by browsers for up to a year. Additionally, most pages |
| 57 | which use that much JS also use comparitively lightweight ajax |
| 58 | communication to eliminate page reloads and enable data-loss-free |
| 59 | recovery in certain error cases which would lose client-side edits |
| 60 |