Fossil SCM

Moved "Blocking JavaScript" section of javascript.md down into the Q&A section.

wyoung 2020-08-19 23:52 js-policy-doc
Commit 85c7bdb285c46d4ff71d450c69ec4f6dd04b1017019dfa14c78968b155d1dab7
1 file changed +27 -22
+27 -22
--- www/javascript.md
+++ www/javascript.md
@@ -46,30 +46,10 @@
4646
JavaScript is not perfect, but it's what we have, so we will use it
4747
where we find it advantageous.
4848
4949
[cg]: ./contribute.wiki
5050
51
-
52
-## <a id="block"></a>Blocking JavaScript
53
-
54
-Rather than either block JavaScript wholesale or give up on blocking
55
-JavaScript entirely, we recommend that you use tools like [NoScript][ns]
56
-or [uBlock Origin][ub] to selectively block problematic uses of
57
-JavaScript so the rest of the web can use the technology productively,
58
-as it was intended. There are doubtless other useful tools of this sort;
59
-we recommend only these two due to our limited experience, not out of
60
-any wish to exclude other tools.
61
-
62
-The primary difference between these two for our purposes is that
63
-NoScript lets you select scripts to run on a page on a case-by-case
64
-basis, whereas uBlock Origin delegates those choices to a group of
65
-motivated volunteers who maintain whitelists and blacklists to control
66
-all of this; you can then override UBO’s stock rules as needed.
67
-
68
-[ns]: https://noscript.net/
69
-[ub]: https://github.com/gorhill/uBlock/
70
-
7151
7252
## <a id="debate"></a>Arguments Against JavaScript & Our Rebuttals
7353
7454
There many common arguments against the use of JavaScript. Rather than
7555
rehash these same arguments on the [forum][ffor], we distill the common
@@ -228,19 +208,42 @@
228208
run [powerful conditional blocking plugins](#block) in their
229209
browsers, rather than block JavaScript entirely. We suspect that
230210
between these two forces, the number of no-JS purists among Fossil’s
231211
user base is still a tiny minority.
232212
233
-9. “**My browser doesn’t even *have* a JavaScript interpreter.**”
213
+9. <a id="block"></a>“**I block JavaScript entirely in my browser. That breaks Fossil.**”
214
+
215
+ First, see our philosophy statement above. Briefly, we intend that
216
+ there always be some other way to get any given result without using
217
+ JavaScript, developer interest willing.
218
+
219
+ But second, it doesn’t have to be all-or-nothing. We recommend that
220
+ those interested in blocking problematic uses of JavaScript use
221
+ tools like [NoScript][ns] or [uBlock Origin][ubo] to *selectively*
222
+ block JavaScript so the rest of the web can use the technology
223
+ productively, as it was intended.
224
+
225
+ There are doubtless other useful tools of this sort. We recommend
226
+ these two only from our limited experience, not out of any wish to
227
+ exclude other tools.
228
+
229
+ The primary difference between these two for our purposes is that
230
+ NoScript lets you select scripts to run on a page on a case-by-case
231
+ basis, whereas uBlock Origin delegates those choices to a group of
232
+ motivated volunteers who maintain whitelists and blacklists to control
233
+ all of this; you can then override UBO’s stock rules as needed.
234
+
235
+
236
+10. “**My browser doesn’t even *have* a JavaScript interpreter.**”
234237
235238
The Fossil open source project has no full-time developers, and only
236239
a few of these part-timers are responsible for the bulk of the code
237240
in Fossil. If you want Fossil to support such niche use cases, then
238241
you will have to [get involved with its development][cg]; it’s
239242
*your* uncommon itch.
240243
241
-10. <a id="compat"></a>“**Fossil’s JavaScript code isn’t compatible with my browser.**”
244
+11. <a id="compat"></a>“**Fossil’s JavaScript code isn’t compatible with my browser.**”
242245
243246
The Fossil project’s developers aim to remain relatively compatible with
244247
the largest portions of the client-side browser base. We use only
245248
standards-defined JavaScript features which are known to work in the
246249
overwhelmingly vast majority of browsers going back approximately 5
@@ -265,14 +268,16 @@
265268
[flic]: /doc/trunk/COPYRIGHT-BSD2.txt
266269
[fshome]: /doc/trunk/www/server/
267270
[fsrc]: https://fossil-scm.org/home/file/src
268271
[fsrv]: /help?cmd=server
269272
[hljs]: https://fossil-scm.org/forum/forumpost/9150bc22ca
273
+[ns]: https://noscript.net/
270274
[pjs]: https://fossil-scm.org/forum/forumpost/1198651c6d
271275
[s1]: https://blockmetry.com/blog/javascript-disabled
272276
[s2]: https://gds.blog.gov.uk/2013/10/21/how-many-people-are-missing-out-on-javascript-enhancement/
273277
[s3]: https://w3techs.com/technologies/overview/client_side_language/all
278
+[ubo]: https://github.com/gorhill/uBlock/
274279
[v8]: https://en.wikipedia.org/wiki/V8_(JavaScript_engine)
275280
276281
277282
----
278283
279284
--- www/javascript.md
+++ www/javascript.md
@@ -46,30 +46,10 @@
46 JavaScript is not perfect, but it's what we have, so we will use it
47 where we find it advantageous.
48
49 [cg]: ./contribute.wiki
50
51
52 ## <a id="block"></a>Blocking JavaScript
53
54 Rather than either block JavaScript wholesale or give up on blocking
55 JavaScript entirely, we recommend that you use tools like [NoScript][ns]
56 or [uBlock Origin][ub] to selectively block problematic uses of
57 JavaScript so the rest of the web can use the technology productively,
58 as it was intended. There are doubtless other useful tools of this sort;
59 we recommend only these two due to our limited experience, not out of
60 any wish to exclude other tools.
61
62 The primary difference between these two for our purposes is that
63 NoScript lets you select scripts to run on a page on a case-by-case
64 basis, whereas uBlock Origin delegates those choices to a group of
65 motivated volunteers who maintain whitelists and blacklists to control
66 all of this; you can then override UBO’s stock rules as needed.
67
68 [ns]: https://noscript.net/
69 [ub]: https://github.com/gorhill/uBlock/
70
71
72 ## <a id="debate"></a>Arguments Against JavaScript & Our Rebuttals
73
74 There many common arguments against the use of JavaScript. Rather than
75 rehash these same arguments on the [forum][ffor], we distill the common
@@ -228,19 +208,42 @@
228 run [powerful conditional blocking plugins](#block) in their
229 browsers, rather than block JavaScript entirely. We suspect that
230 between these two forces, the number of no-JS purists among Fossil’s
231 user base is still a tiny minority.
232
233 9. “**My browser doesn’t even *have* a JavaScript interpreter.**”
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
234
235 The Fossil open source project has no full-time developers, and only
236 a few of these part-timers are responsible for the bulk of the code
237 in Fossil. If you want Fossil to support such niche use cases, then
238 you will have to [get involved with its development][cg]; it’s
239 *your* uncommon itch.
240
241 10. <a id="compat"></a>“**Fossil’s JavaScript code isn’t compatible with my browser.**”
242
243 The Fossil project’s developers aim to remain relatively compatible with
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
@@ -265,14 +268,16 @@
265 [flic]: /doc/trunk/COPYRIGHT-BSD2.txt
266 [fshome]: /doc/trunk/www/server/
267 [fsrc]: https://fossil-scm.org/home/file/src
268 [fsrv]: /help?cmd=server
269 [hljs]: https://fossil-scm.org/forum/forumpost/9150bc22ca
 
270 [pjs]: https://fossil-scm.org/forum/forumpost/1198651c6d
271 [s1]: https://blockmetry.com/blog/javascript-disabled
272 [s2]: https://gds.blog.gov.uk/2013/10/21/how-many-people-are-missing-out-on-javascript-enhancement/
273 [s3]: https://w3techs.com/technologies/overview/client_side_language/all
 
274 [v8]: https://en.wikipedia.org/wiki/V8_(JavaScript_engine)
275
276
277 ----
278
279
--- www/javascript.md
+++ www/javascript.md
@@ -46,30 +46,10 @@
46 JavaScript is not perfect, but it's what we have, so we will use it
47 where we find it advantageous.
48
49 [cg]: ./contribute.wiki
50
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
51
52 ## <a id="debate"></a>Arguments Against JavaScript & Our Rebuttals
53
54 There many common arguments against the use of JavaScript. Rather than
55 rehash these same arguments on the [forum][ffor], we distill the common
@@ -228,19 +208,42 @@
208 run [powerful conditional blocking plugins](#block) in their
209 browsers, rather than block JavaScript entirely. We suspect that
210 between these two forces, the number of no-JS purists among Fossil’s
211 user base is still a tiny minority.
212
213 9. <a id="block"></a>“**I block JavaScript entirely in my browser. That breaks Fossil.**”
214
215 First, see our philosophy statement above. Briefly, we intend that
216 there always be some other way to get any given result without using
217 JavaScript, developer interest willing.
218
219 But second, it doesn’t have to be all-or-nothing. We recommend that
220 those interested in blocking problematic uses of JavaScript use
221 tools like [NoScript][ns] or [uBlock Origin][ubo] to *selectively*
222 block JavaScript so the rest of the web can use the technology
223 productively, as it was intended.
224
225 There are doubtless other useful tools of this sort. We recommend
226 these two only from our limited experience, not out of any wish to
227 exclude other tools.
228
229 The primary difference between these two for our purposes is that
230 NoScript lets you select scripts to run on a page on a case-by-case
231 basis, whereas uBlock Origin delegates those choices to a group of
232 motivated volunteers who maintain whitelists and blacklists to control
233 all of this; you can then override UBO’s stock rules as needed.
234
235
236 10. “**My browser doesn’t even *have* a JavaScript interpreter.**”
237
238 The Fossil open source project has no full-time developers, and only
239 a few of these part-timers are responsible for the bulk of the code
240 in Fossil. If you want Fossil to support such niche use cases, then
241 you will have to [get involved with its development][cg]; it’s
242 *your* uncommon itch.
243
244 11. <a id="compat"></a>“**Fossil’s JavaScript code isn’t compatible with my browser.**”
245
246 The Fossil project’s developers aim to remain relatively compatible with
247 the largest portions of the client-side browser base. We use only
248 standards-defined JavaScript features which are known to work in the
249 overwhelmingly vast majority of browsers going back approximately 5
@@ -265,14 +268,16 @@
268 [flic]: /doc/trunk/COPYRIGHT-BSD2.txt
269 [fshome]: /doc/trunk/www/server/
270 [fsrc]: https://fossil-scm.org/home/file/src
271 [fsrv]: /help?cmd=server
272 [hljs]: https://fossil-scm.org/forum/forumpost/9150bc22ca
273 [ns]: https://noscript.net/
274 [pjs]: https://fossil-scm.org/forum/forumpost/1198651c6d
275 [s1]: https://blockmetry.com/blog/javascript-disabled
276 [s2]: https://gds.blog.gov.uk/2013/10/21/how-many-people-are-missing-out-on-javascript-enhancement/
277 [s3]: https://w3techs.com/technologies/overview/client_side_language/all
278 [ubo]: https://github.com/gorhill/uBlock/
279 [v8]: https://en.wikipedia.org/wiki/V8_(JavaScript_engine)
280
281
282 ----
283
284

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button