Fossil SCM
Minuscule tweaks to javascript.md
Commit
5648dcfc3d8452eb3a6af0e1ba79ebf0455e86a078b9637fe6814236f517d171
Parent
ba9480b02b4a189…
1 file changed
+6
-6
+6
-6
| --- www/javascript.md | ||
| +++ www/javascript.md | ||
| @@ -2,14 +2,14 @@ | ||
| 2 | 2 | |
| 3 | 3 | ## Philosophy & Policy |
| 4 | 4 | |
| 5 | 5 | The Fossil development project’s policy is to use JavaScript where it |
| 6 | 6 | helps make its web UI better, but to offer graceful fallbacks wherever |
| 7 | -practical. The intent is that the UI be usable with JavaScript entirely | |
| 8 | -disabled. In every place where Fossil uses JavaScript, it is an | |
| 9 | -enhancement to provided functionality, and there is always another way | |
| 10 | -to accomplish a given end without using JavaScript. | |
| 7 | +practical. The intent is that the UI be usable with JavaScript | |
| 8 | +entirely disabled. In almost all places where Fossil uses JavaScript, | |
| 9 | +it is an enhancement to provided functionality, and there is always | |
| 10 | +another way to accomplish a given end without using JavaScript. | |
| 11 | 11 | |
| 12 | 12 | This is not to say that Fossil’s fall-backs for such cases are always as |
| 13 | 13 | elegant and functional as a no-JS purist might wish. That is simply |
| 14 | 14 | because [the vast majority of web users run with JavaScript enabled](#stats), |
| 15 | 15 | and a minority of those run with some kind of [conditional JavaScript |
| @@ -244,11 +244,11 @@ | ||
| 244 | 244 | the largest portions of the client-side browser base. We use only |
| 245 | 245 | standards-defined JavaScript features which are known to work in the |
| 246 | 246 | overwhelmingly vast majority of browsers going back approximately 5 |
| 247 | 247 | years, at minimum, as documented by [Can I Use...?][ciu] We avoid use of |
| 248 | 248 | features added to the language more recently or those which are still in |
| 249 | - flux in standards committees | |
| 249 | + flux in standards committees. | |
| 250 | 250 | |
| 251 | 251 | We set this threshold based on the amount of time it typically takes for |
| 252 | 252 | new standards to propagate through the installed base. |
| 253 | 253 | |
| 254 | 254 | As of this writing, this means we are only using features defined in |
| @@ -416,11 +416,11 @@ | ||
| 416 | 416 | would have no local backup if something crashes, etc. Still, we are |
| 417 | 417 | likely to accept such a [contribution][cg] as long as it doesn’t |
| 418 | 418 | interfere with the new editor. |
| 419 | 419 | |
| 420 | 420 | [edoc]: /doc/trunk/www/embeddeddoc.wiki |
| 421 | -[fedit]: /help?cmd=/fileedit | |
| 421 | +[fedit]: /doc/trunk/www/fileedit-page.md | |
| 422 | 422 | |
| 423 | 423 | |
| 424 | 424 | ### <a id="ln"></a>Line Numbering |
| 425 | 425 | |
| 426 | 426 | When viewing source files, Fossil offers to show line numbers in some |
| 427 | 427 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -2,14 +2,14 @@ | |
| 2 | |
| 3 | ## Philosophy & Policy |
| 4 | |
| 5 | The Fossil development project’s policy is to use JavaScript where it |
| 6 | helps make its web UI better, but to offer graceful fallbacks wherever |
| 7 | practical. The intent is that the UI be usable with JavaScript entirely |
| 8 | disabled. In every place where Fossil uses JavaScript, it is an |
| 9 | enhancement to provided functionality, and there is always another way |
| 10 | to accomplish a given end without using JavaScript. |
| 11 | |
| 12 | This is not to say that Fossil’s fall-backs for such cases are always as |
| 13 | elegant and functional as a no-JS purist might wish. That is simply |
| 14 | because [the vast majority of web users run with JavaScript enabled](#stats), |
| 15 | and a minority of those run with some kind of [conditional JavaScript |
| @@ -244,11 +244,11 @@ | |
| 244 | the largest portions of the client-side browser base. We use only |
| 245 | standards-defined JavaScript features which are known to work in the |
| 246 | overwhelmingly vast majority of browsers going back approximately 5 |
| 247 | years, at minimum, as documented by [Can I Use...?][ciu] We avoid use of |
| 248 | features added to the language more recently or those which are still in |
| 249 | flux in standards committees |
| 250 | |
| 251 | We set this threshold based on the amount of time it typically takes for |
| 252 | new standards to propagate through the installed base. |
| 253 | |
| 254 | As of this writing, this means we are only using features defined in |
| @@ -416,11 +416,11 @@ | |
| 416 | would have no local backup if something crashes, etc. Still, we are |
| 417 | likely to accept such a [contribution][cg] as long as it doesn’t |
| 418 | interfere with the new editor. |
| 419 | |
| 420 | [edoc]: /doc/trunk/www/embeddeddoc.wiki |
| 421 | [fedit]: /help?cmd=/fileedit |
| 422 | |
| 423 | |
| 424 | ### <a id="ln"></a>Line Numbering |
| 425 | |
| 426 | When viewing source files, Fossil offers to show line numbers in some |
| 427 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -2,14 +2,14 @@ | |
| 2 | |
| 3 | ## Philosophy & Policy |
| 4 | |
| 5 | The Fossil development project’s policy is to use JavaScript where it |
| 6 | helps make its web UI better, but to offer graceful fallbacks wherever |
| 7 | practical. The intent is that the UI be usable with JavaScript |
| 8 | entirely disabled. In almost all places where Fossil uses JavaScript, |
| 9 | it is an enhancement to provided functionality, and there is always |
| 10 | another way to accomplish a given end without using JavaScript. |
| 11 | |
| 12 | This is not to say that Fossil’s fall-backs for such cases are always as |
| 13 | elegant and functional as a no-JS purist might wish. That is simply |
| 14 | because [the vast majority of web users run with JavaScript enabled](#stats), |
| 15 | and a minority of those run with some kind of [conditional JavaScript |
| @@ -244,11 +244,11 @@ | |
| 244 | the largest portions of the client-side browser base. We use only |
| 245 | standards-defined JavaScript features which are known to work in the |
| 246 | overwhelmingly vast majority of browsers going back approximately 5 |
| 247 | years, at minimum, as documented by [Can I Use...?][ciu] We avoid use of |
| 248 | features added to the language more recently or those which are still in |
| 249 | flux in standards committees. |
| 250 | |
| 251 | We set this threshold based on the amount of time it typically takes for |
| 252 | new standards to propagate through the installed base. |
| 253 | |
| 254 | As of this writing, this means we are only using features defined in |
| @@ -416,11 +416,11 @@ | |
| 416 | would have no local backup if something crashes, etc. Still, we are |
| 417 | likely to accept such a [contribution][cg] as long as it doesn’t |
| 418 | interfere with the new editor. |
| 419 | |
| 420 | [edoc]: /doc/trunk/www/embeddeddoc.wiki |
| 421 | [fedit]: /doc/trunk/www/fileedit-page.md |
| 422 | |
| 423 | |
| 424 | ### <a id="ln"></a>Line Numbering |
| 425 | |
| 426 | When viewing source files, Fossil offers to show line numbers in some |
| 427 |