Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fixed a copy/paste error in www/sync.wiki per an anonymous forum post. |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
3f736de9867d85ef027d4f5df4c6b032 |
User & Date: | wyoung 2021-10-07 13:01:30 |
Context
2021-10-07
| ||
16:27 | /chat: 1) force the cursor on the input element to always be 'text' (I-beam), even when it doesn't have focus (browser inconsistency) and 2) when the chat window regains visibility after having lost it, give focus to the input element to try to work around a problem where Pale Moon is giving focus to one of the pseudo-buttons. Change (2) comes with a couple of minor but annoying quirks and might have to be undone, but it's worth a try. ... (check-in: 50339579 user: stephan tags: trunk) | |
13:01 | Fixed a copy/paste error in www/sync.wiki per an anonymous forum post. ... (check-in: 3f736de9 user: wyoung tags: trunk) | |
04:07 | /chat another CSS-side contenteditable portability workaround to keep Firefox from losing newlines on pasted-in text. ... (check-in: c7fa9f15 user: stephan tags: trunk) | |
Changes
Changes to www/sync.wiki.
︙ | ︙ | |||
702 703 704 705 706 707 708 | the client because the client login lacks the "write-unversioned" permission.</p> <li><p><b>uv-push-ok</b></i> <p>A server sends the uv-push-ok pragma to the client in response to a uv-hash pragma with a mismatched content hash argument. This pragma indicates that there are differences in unversioned content | | | 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 | the client because the client login lacks the "write-unversioned" permission.</p> <li><p><b>uv-push-ok</b></i> <p>A server sends the uv-push-ok pragma to the client in response to a uv-hash pragma with a mismatched content hash argument. This pragma indicates that there are differences in unversioned content between the client and server and that content can be transferred in either direction. The server is willing to accept content from the client because the client login has the "write-unversioned" permission.</p> <li><p><b>ci-lock</b> <i>CHECKIN-HASH CLIENT-ID</i></p> <p>A client sends the "ci-lock" pragma to the server to indicate that it is about to add a new check-in as a child of the |
︙ | ︙ |