Fossil SCM
Add a paragraph to www/forum.wiki, in the Accessing the Forum section, about how to either disable or bypass the newfangled JS forum bits and use the legacy UI instead. Based on confusion caused by having inadvertently visited a forum post via /info instead of /forumpost.
Commit
5354447e329e1b60c5632192ccc167efa0d6983cac278f35b24b7967e85a9f7c
Parent
63826bf8a4ce730…
1 file changed
+11
+11
| --- www/forum.wiki | ||
| +++ www/forum.wiki | ||
| @@ -281,10 +281,21 @@ | ||
| 281 | 281 | |
| 282 | 282 | <li>That same link also appears on the repository's <tt>/sitemap</tt> |
| 283 | 283 | page, since it provides the content for the hamburger menu's |
| 284 | 284 | panel.</li> |
| 285 | 285 | </ul> |
| 286 | + | |
| 287 | +The forum uses JavaScript to allow for a more comfortable editing | |
| 288 | +experience than is possible with static HTML. If one takes issue with, | |
| 289 | +or has issues with, the JavaScript-based forum editing and response | |
| 290 | +features, there are several ways around them: (1) Clients with JS | |
| 291 | +disabled should see the legacy (pre-mid-2026) input forms and | |
| 292 | +buttons. (2) Adding <code>?nojs</code> to any <code>/forumpost</code> | |
| 293 | +URL will disable plugging-in of the JS UI elements. (3) When forum | |
| 294 | +posts are visited via <code>/info</code> instead of | |
| 295 | +<code>/forumpost</code>, the JS-based UI elements do not plug | |
| 296 | +themselves in, leaving the legacy UI intact. | |
| 286 | 297 | |
| 287 | 298 | |
| 288 | 299 | <h2 id="moderation">How Moderation Works</h2> |
| 289 | 300 | |
| 290 | 301 | In this section, we're going to call all of the following a "forum |
| 291 | 302 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -281,10 +281,21 @@ | |
| 281 | |
| 282 | <li>That same link also appears on the repository's <tt>/sitemap</tt> |
| 283 | page, since it provides the content for the hamburger menu's |
| 284 | panel.</li> |
| 285 | </ul> |
| 286 | |
| 287 | |
| 288 | <h2 id="moderation">How Moderation Works</h2> |
| 289 | |
| 290 | In this section, we're going to call all of the following a "forum |
| 291 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -281,10 +281,21 @@ | |
| 281 | |
| 282 | <li>That same link also appears on the repository's <tt>/sitemap</tt> |
| 283 | page, since it provides the content for the hamburger menu's |
| 284 | panel.</li> |
| 285 | </ul> |
| 286 | |
| 287 | The forum uses JavaScript to allow for a more comfortable editing |
| 288 | experience than is possible with static HTML. If one takes issue with, |
| 289 | or has issues with, the JavaScript-based forum editing and response |
| 290 | features, there are several ways around them: (1) Clients with JS |
| 291 | disabled should see the legacy (pre-mid-2026) input forms and |
| 292 | buttons. (2) Adding <code>?nojs</code> to any <code>/forumpost</code> |
| 293 | URL will disable plugging-in of the JS UI elements. (3) When forum |
| 294 | posts are visited via <code>/info</code> instead of |
| 295 | <code>/forumpost</code>, the JS-based UI elements do not plug |
| 296 | themselves in, leaving the legacy UI intact. |
| 297 | |
| 298 | |
| 299 | <h2 id="moderation">How Moderation Works</h2> |
| 300 | |
| 301 | In this section, we're going to call all of the following a "forum |
| 302 |