Fossil SCM
Typo fixes in fileedit-page.md
Commit
d400f403f9447ef1072aee97ee7a15cb5a5a3a5a3d7278e4bcb733bdb7e90757
Parent
9e9fb33caf883c4…
1 file changed
+5
-5
+5
-5
| --- www/fileedit-page.md | ||
| +++ www/fileedit-page.md | ||
| @@ -44,11 +44,11 @@ | ||
| 44 | 44 | policy, so Chrome without such an add-on will not suppress this |
| 45 | 45 | header. |
| 46 | 46 | - **Safari**: ??? |
| 47 | 47 | - **Other browsers**: ??? |
| 48 | 48 | |
| 49 | -If `/filepage` shows an error message saying "CSRF violation," the | |
| 49 | +If `/fileedit` shows an error message saying "CSRF violation," the | |
| 50 | 50 | problem is that the browser is not sending a `Referer` header to XHR |
| 51 | 51 | connections. Fossil does not offer a way to disable its CSRF |
| 52 | 52 | protections. |
| 53 | 53 | |
| 54 | 54 | [referer]: https://en.wikipedia.org/wiki/HTTP_referer |
| @@ -137,11 +137,11 @@ | ||
| 137 | 137 | Exactly how long `localStorage` will survive, and how much it or |
| 138 | 138 | `sessionStorage` can hold, is environment-dependent. `sessionStorage` |
| 139 | 139 | will survive until the current browser tab is closed, but it survives |
| 140 | 140 | across reloads of the same tab. |
| 141 | 141 | |
| 142 | -If `/filepage` determines that no persistent storage is available a | |
| 142 | +If `/fileedit` determines that no persistent storage is available a | |
| 143 | 143 | warning is displayed on the editor page. |
| 144 | 144 | |
| 145 | 145 | [html5storage]: https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API |
| 146 | 146 | |
| 147 | 147 | ## <a id="power"></a> The Power is Yours, but... |
| @@ -204,11 +204,11 @@ | ||
| 204 | 204 | |
| 205 | 205 | The first line of the script just ensures that the expected JS-level |
| 206 | 206 | infrastructure is loaded. It's only loaded in the `/fileedit` page and |
| 207 | 207 | possibly pages added or "upgraded" since `/fileedit`'s introduction. |
| 208 | 208 | |
| 209 | -The part in the `if` block adds an event listener to the `/filepage` | |
| 209 | +The part in the `if` block adds an event listener to the `/fileedit` | |
| 210 | 210 | app which gets called when the preview is refreshed. That event |
| 211 | 211 | contains 3 properties: |
| 212 | 212 | |
| 213 | 213 | - `previewMode`: a string describing the current preview mode: `wiki` |
| 214 | 214 | (which includes Fossil-native wiki and markdown), `text`, |
| @@ -225,14 +225,14 @@ | ||
| 225 | 225 | the preview which explicitly have a CSS class named |
| 226 | 226 | `language-`something, and then asks highlightjs to highlight them. |
| 227 | 227 | |
| 228 | 228 | ## <a id="editor"></a> Integrating a Custom Editor Widget |
| 229 | 229 | |
| 230 | -(These instructions also work for the `/wikiedit` page by eplacing | |
| 230 | +(These instructions also work for the `/wikiedit` page by replacing | |
| 231 | 231 | "fileedit" with "wikiedit" in any strings or symbol names!) |
| 232 | 232 | |
| 233 | -It is possible to replace `/filepage`'s basic text-editing widget (a | |
| 233 | +It is possible to replace `/fileedit`'s basic text-editing widget (a | |
| 234 | 234 | `textarea` element) with a fancy 3rd-party editor widget by following |
| 235 | 235 | these instructions... |
| 236 | 236 | |
| 237 | 237 | All JavaScript code which follows is assumed to be in a script tag |
| 238 | 238 | similar to the one shown in the previous section: |
| 239 | 239 |
| --- www/fileedit-page.md | |
| +++ www/fileedit-page.md | |
| @@ -44,11 +44,11 @@ | |
| 44 | policy, so Chrome without such an add-on will not suppress this |
| 45 | header. |
| 46 | - **Safari**: ??? |
| 47 | - **Other browsers**: ??? |
| 48 | |
| 49 | If `/filepage` shows an error message saying "CSRF violation," the |
| 50 | problem is that the browser is not sending a `Referer` header to XHR |
| 51 | connections. Fossil does not offer a way to disable its CSRF |
| 52 | protections. |
| 53 | |
| 54 | [referer]: https://en.wikipedia.org/wiki/HTTP_referer |
| @@ -137,11 +137,11 @@ | |
| 137 | Exactly how long `localStorage` will survive, and how much it or |
| 138 | `sessionStorage` can hold, is environment-dependent. `sessionStorage` |
| 139 | will survive until the current browser tab is closed, but it survives |
| 140 | across reloads of the same tab. |
| 141 | |
| 142 | If `/filepage` determines that no persistent storage is available a |
| 143 | warning is displayed on the editor page. |
| 144 | |
| 145 | [html5storage]: https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API |
| 146 | |
| 147 | ## <a id="power"></a> The Power is Yours, but... |
| @@ -204,11 +204,11 @@ | |
| 204 | |
| 205 | The first line of the script just ensures that the expected JS-level |
| 206 | infrastructure is loaded. It's only loaded in the `/fileedit` page and |
| 207 | possibly pages added or "upgraded" since `/fileedit`'s introduction. |
| 208 | |
| 209 | The part in the `if` block adds an event listener to the `/filepage` |
| 210 | app which gets called when the preview is refreshed. That event |
| 211 | contains 3 properties: |
| 212 | |
| 213 | - `previewMode`: a string describing the current preview mode: `wiki` |
| 214 | (which includes Fossil-native wiki and markdown), `text`, |
| @@ -225,14 +225,14 @@ | |
| 225 | the preview which explicitly have a CSS class named |
| 226 | `language-`something, and then asks highlightjs to highlight them. |
| 227 | |
| 228 | ## <a id="editor"></a> Integrating a Custom Editor Widget |
| 229 | |
| 230 | (These instructions also work for the `/wikiedit` page by eplacing |
| 231 | "fileedit" with "wikiedit" in any strings or symbol names!) |
| 232 | |
| 233 | It is possible to replace `/filepage`'s basic text-editing widget (a |
| 234 | `textarea` element) with a fancy 3rd-party editor widget by following |
| 235 | these instructions... |
| 236 | |
| 237 | All JavaScript code which follows is assumed to be in a script tag |
| 238 | similar to the one shown in the previous section: |
| 239 |
| --- www/fileedit-page.md | |
| +++ www/fileedit-page.md | |
| @@ -44,11 +44,11 @@ | |
| 44 | policy, so Chrome without such an add-on will not suppress this |
| 45 | header. |
| 46 | - **Safari**: ??? |
| 47 | - **Other browsers**: ??? |
| 48 | |
| 49 | If `/fileedit` shows an error message saying "CSRF violation," the |
| 50 | problem is that the browser is not sending a `Referer` header to XHR |
| 51 | connections. Fossil does not offer a way to disable its CSRF |
| 52 | protections. |
| 53 | |
| 54 | [referer]: https://en.wikipedia.org/wiki/HTTP_referer |
| @@ -137,11 +137,11 @@ | |
| 137 | Exactly how long `localStorage` will survive, and how much it or |
| 138 | `sessionStorage` can hold, is environment-dependent. `sessionStorage` |
| 139 | will survive until the current browser tab is closed, but it survives |
| 140 | across reloads of the same tab. |
| 141 | |
| 142 | If `/fileedit` determines that no persistent storage is available a |
| 143 | warning is displayed on the editor page. |
| 144 | |
| 145 | [html5storage]: https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API |
| 146 | |
| 147 | ## <a id="power"></a> The Power is Yours, but... |
| @@ -204,11 +204,11 @@ | |
| 204 | |
| 205 | The first line of the script just ensures that the expected JS-level |
| 206 | infrastructure is loaded. It's only loaded in the `/fileedit` page and |
| 207 | possibly pages added or "upgraded" since `/fileedit`'s introduction. |
| 208 | |
| 209 | The part in the `if` block adds an event listener to the `/fileedit` |
| 210 | app which gets called when the preview is refreshed. That event |
| 211 | contains 3 properties: |
| 212 | |
| 213 | - `previewMode`: a string describing the current preview mode: `wiki` |
| 214 | (which includes Fossil-native wiki and markdown), `text`, |
| @@ -225,14 +225,14 @@ | |
| 225 | the preview which explicitly have a CSS class named |
| 226 | `language-`something, and then asks highlightjs to highlight them. |
| 227 | |
| 228 | ## <a id="editor"></a> Integrating a Custom Editor Widget |
| 229 | |
| 230 | (These instructions also work for the `/wikiedit` page by replacing |
| 231 | "fileedit" with "wikiedit" in any strings or symbol names!) |
| 232 | |
| 233 | It is possible to replace `/fileedit`'s basic text-editing widget (a |
| 234 | `textarea` element) with a fancy 3rd-party editor widget by following |
| 235 | these instructions... |
| 236 | |
| 237 | All JavaScript code which follows is assumed to be in a script tag |
| 238 | similar to the one shown in the previous section: |
| 239 |