Fossil SCM
Moved the named anchors within www/javascript.md after the first Unicode rune of numbered lists to avoid an MD rendering problem.
Commit
5b46aafb6a35261434db669e3e6bfa0fc414b1d1c37c9d7c898ea2e5948b47e5
Parent
26a96e8d95b857a…
1 file changed
+5
-5
+5
-5
| --- www/javascript.md | ||
| +++ www/javascript.md | ||
| @@ -100,11 +100,11 @@ | ||
| 100 | 100 | Ajax partial page updates are faster than |
| 101 | 101 | the no-JS alternative, a full HTTP POST round-trip to submit new |
| 102 | 102 | data to the remote server, retrieve an entire new HTML document, |
| 103 | 103 | and re-render the whole thing client-side. |
| 104 | 104 | |
| 105 | -3. <a id="3pjs"></a>“**Third-party JavaScript cannot be trusted.**” | |
| 105 | +3. “<a id="3pjs"></a>**Third-party JavaScript cannot be trusted.**” | |
| 106 | 106 | |
| 107 | 107 | Fossil does not use any third-party JavaScript libraries, not even |
| 108 | 108 | very common ones like jQuery. Every bit of JavaScript served by the |
| 109 | 109 | stock version of Fossil was written specifically for the Fossil |
| 110 | 110 | project and is stored [in its code repository][fsrc]. |
| @@ -113,11 +113,11 @@ | ||
| 113 | 113 | Fossil and mechanisms like [skin editing][cskin] don’t suffice for your |
| 114 | 114 | purposes, you can hack on the JavaScript in your local instance |
| 115 | 115 | directly, just as you can hack on its C, SQL, and Tcl code. Fossil |
| 116 | 116 | is free and open source software, under [a single license][2cbsd]. |
| 117 | 117 | |
| 118 | -4. <a id="snoop"></a>“**JavaScript and cookies are used to snoop on web users.**” | |
| 118 | +4. “<a id="snoop"></a>**JavaScript and cookies are used to snoop on web users.**” | |
| 119 | 119 | |
| 120 | 120 | There is no tracking or other snooping technology in Fossil other than |
| 121 | 121 | that necessary for basic security, such as IP address logging on |
| 122 | 122 | check-ins. (This is in part why we have no [comprehensive user |
| 123 | 123 | statistics](#stats)!) |
| @@ -184,11 +184,11 @@ | ||
| 184 | 184 | The no-JS case is a [minority position](#stats), so those that want |
| 185 | 185 | Fossil to have no-JS alternatives and graceful fallbacks will need |
| 186 | 186 | to get involved with the development if they want this state of |
| 187 | 187 | affairs to continue. |
| 188 | 188 | |
| 189 | -8. <a id="stats"></a>“**A large number of users run without JavaScript enabled.**” | |
| 189 | +8. “<a id="stats"></a>**A large number of users run without JavaScript enabled.**” | |
| 190 | 190 | |
| 191 | 191 | That’s not what web audience measurements say: |
| 192 | 192 | |
| 193 | 193 | * [What percentage of browsers with javascript disabled?][s1] |
| 194 | 194 | * [How many people are missing out on JavaScript enhancement?][s2] |
| @@ -207,11 +207,11 @@ | ||
| 207 | 207 | run [powerful conditional blocking plugins](#block) in their |
| 208 | 208 | browsers, rather than block JavaScript entirely. We suspect that |
| 209 | 209 | between these two forces, the number of no-JS purists among Fossil’s |
| 210 | 210 | user base is still a tiny minority. |
| 211 | 211 | |
| 212 | -9. <a id="block"></a>“**I block JavaScript entirely in my browser. That breaks Fossil.**” | |
| 212 | +9. “<a id="block"></a>**I block JavaScript entirely in my browser. That breaks Fossil.**” | |
| 213 | 213 | |
| 214 | 214 | First, see our philosophy statements above. Briefly, we intend that |
| 215 | 215 | there always be some other way to get any given result without using |
| 216 | 216 | JavaScript, developer interest willing. |
| 217 | 217 | |
| @@ -237,11 +237,11 @@ | ||
| 237 | 237 | a few of these part-timers are responsible for the bulk of the code |
| 238 | 238 | in Fossil. If you want Fossil to support such niche use cases, then |
| 239 | 239 | you will have to [get involved with its development][cg]: it’s |
| 240 | 240 | *your* uncommon itch. |
| 241 | 241 | |
| 242 | -11. <a id="compat"></a>“**Fossil’s JavaScript code isn’t compatible with my browser.**” | |
| 242 | +11. “<a id="compat"></a>**Fossil’s JavaScript code isn’t compatible with my browser.**” | |
| 243 | 243 | |
| 244 | 244 | The Fossil project’s developers aim to remain compatible with |
| 245 | 245 | the largest portions of the client-side browser base. We use only |
| 246 | 246 | standards-defined JavaScript features which are known to work in the |
| 247 | 247 | overwhelmingly vast majority of browsers going back approximately 5 |
| 248 | 248 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -100,11 +100,11 @@ | |
| 100 | Ajax partial page updates are faster than |
| 101 | the no-JS alternative, a full HTTP POST round-trip to submit new |
| 102 | data to the remote server, retrieve an entire new HTML document, |
| 103 | and re-render the whole thing client-side. |
| 104 | |
| 105 | 3. <a id="3pjs"></a>“**Third-party JavaScript cannot be trusted.**” |
| 106 | |
| 107 | Fossil does not use any third-party JavaScript libraries, not even |
| 108 | very common ones like jQuery. Every bit of JavaScript served by the |
| 109 | stock version of Fossil was written specifically for the Fossil |
| 110 | project and is stored [in its code repository][fsrc]. |
| @@ -113,11 +113,11 @@ | |
| 113 | Fossil and mechanisms like [skin editing][cskin] don’t suffice for your |
| 114 | purposes, you can hack on the JavaScript in your local instance |
| 115 | directly, just as you can hack on its C, SQL, and Tcl code. Fossil |
| 116 | is free and open source software, under [a single license][2cbsd]. |
| 117 | |
| 118 | 4. <a id="snoop"></a>“**JavaScript and cookies are used to snoop on web users.**” |
| 119 | |
| 120 | There is no tracking or other snooping technology in Fossil other than |
| 121 | that necessary for basic security, such as IP address logging on |
| 122 | check-ins. (This is in part why we have no [comprehensive user |
| 123 | statistics](#stats)!) |
| @@ -184,11 +184,11 @@ | |
| 184 | The no-JS case is a [minority position](#stats), so those that want |
| 185 | Fossil to have no-JS alternatives and graceful fallbacks will need |
| 186 | to get involved with the development if they want this state of |
| 187 | affairs to continue. |
| 188 | |
| 189 | 8. <a id="stats"></a>“**A large number of users run without JavaScript enabled.**” |
| 190 | |
| 191 | That’s not what web audience measurements say: |
| 192 | |
| 193 | * [What percentage of browsers with javascript disabled?][s1] |
| 194 | * [How many people are missing out on JavaScript enhancement?][s2] |
| @@ -207,11 +207,11 @@ | |
| 207 | run [powerful conditional blocking plugins](#block) in their |
| 208 | browsers, rather than block JavaScript entirely. We suspect that |
| 209 | between these two forces, the number of no-JS purists among Fossil’s |
| 210 | user base is still a tiny minority. |
| 211 | |
| 212 | 9. <a id="block"></a>“**I block JavaScript entirely in my browser. That breaks Fossil.**” |
| 213 | |
| 214 | First, see our philosophy statements above. Briefly, we intend that |
| 215 | there always be some other way to get any given result without using |
| 216 | JavaScript, developer interest willing. |
| 217 | |
| @@ -237,11 +237,11 @@ | |
| 237 | a few of these part-timers are responsible for the bulk of the code |
| 238 | in Fossil. If you want Fossil to support such niche use cases, then |
| 239 | you will have to [get involved with its development][cg]: it’s |
| 240 | *your* uncommon itch. |
| 241 | |
| 242 | 11. <a id="compat"></a>“**Fossil’s JavaScript code isn’t compatible with my browser.**” |
| 243 | |
| 244 | The Fossil project’s developers aim to remain compatible with |
| 245 | the largest portions of the client-side browser base. We use only |
| 246 | standards-defined JavaScript features which are known to work in the |
| 247 | overwhelmingly vast majority of browsers going back approximately 5 |
| 248 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -100,11 +100,11 @@ | |
| 100 | Ajax partial page updates are faster than |
| 101 | the no-JS alternative, a full HTTP POST round-trip to submit new |
| 102 | data to the remote server, retrieve an entire new HTML document, |
| 103 | and re-render the whole thing client-side. |
| 104 | |
| 105 | 3. “<a id="3pjs"></a>**Third-party JavaScript cannot be trusted.**” |
| 106 | |
| 107 | Fossil does not use any third-party JavaScript libraries, not even |
| 108 | very common ones like jQuery. Every bit of JavaScript served by the |
| 109 | stock version of Fossil was written specifically for the Fossil |
| 110 | project and is stored [in its code repository][fsrc]. |
| @@ -113,11 +113,11 @@ | |
| 113 | Fossil and mechanisms like [skin editing][cskin] don’t suffice for your |
| 114 | purposes, you can hack on the JavaScript in your local instance |
| 115 | directly, just as you can hack on its C, SQL, and Tcl code. Fossil |
| 116 | is free and open source software, under [a single license][2cbsd]. |
| 117 | |
| 118 | 4. “<a id="snoop"></a>**JavaScript and cookies are used to snoop on web users.**” |
| 119 | |
| 120 | There is no tracking or other snooping technology in Fossil other than |
| 121 | that necessary for basic security, such as IP address logging on |
| 122 | check-ins. (This is in part why we have no [comprehensive user |
| 123 | statistics](#stats)!) |
| @@ -184,11 +184,11 @@ | |
| 184 | The no-JS case is a [minority position](#stats), so those that want |
| 185 | Fossil to have no-JS alternatives and graceful fallbacks will need |
| 186 | to get involved with the development if they want this state of |
| 187 | affairs to continue. |
| 188 | |
| 189 | 8. “<a id="stats"></a>**A large number of users run without JavaScript enabled.**” |
| 190 | |
| 191 | That’s not what web audience measurements say: |
| 192 | |
| 193 | * [What percentage of browsers with javascript disabled?][s1] |
| 194 | * [How many people are missing out on JavaScript enhancement?][s2] |
| @@ -207,11 +207,11 @@ | |
| 207 | run [powerful conditional blocking plugins](#block) in their |
| 208 | browsers, rather than block JavaScript entirely. We suspect that |
| 209 | between these two forces, the number of no-JS purists among Fossil’s |
| 210 | user base is still a tiny minority. |
| 211 | |
| 212 | 9. “<a id="block"></a>**I block JavaScript entirely in my browser. That breaks Fossil.**” |
| 213 | |
| 214 | First, see our philosophy statements above. Briefly, we intend that |
| 215 | there always be some other way to get any given result without using |
| 216 | JavaScript, developer interest willing. |
| 217 | |
| @@ -237,11 +237,11 @@ | |
| 237 | a few of these part-timers are responsible for the bulk of the code |
| 238 | in Fossil. If you want Fossil to support such niche use cases, then |
| 239 | you will have to [get involved with its development][cg]: it’s |
| 240 | *your* uncommon itch. |
| 241 | |
| 242 | 11. “<a id="compat"></a>**Fossil’s JavaScript code isn’t compatible with my browser.**” |
| 243 | |
| 244 | The Fossil project’s developers aim to remain compatible with |
| 245 | the largest portions of the client-side browser base. We use only |
| 246 | standards-defined JavaScript features which are known to work in the |
| 247 | overwhelmingly vast majority of browsers going back approximately 5 |
| 248 |