Check-in [a6177fd43d]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Chat docs: added notes about client-side message deletion and clarified hyperlink parsing a bit.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: a6177fd43dbef3cef8194ff0eab827f0087bf807aba01f3d05d9ee4ab884faf8
User & Date: stephan 2021-01-04 14:58:24.082
Context
2021-01-04
15:18
Fix rendering on the /file page that causes text files to be reported as binary. Caused by check-in [6643d4a0c1aabb85]. check-in: e5d30a7c34 user: drh tags: trunk
14:58
Chat docs: added notes about client-side message deletion and clarified hyperlink parsing a bit. check-in: a6177fd43d user: stephan tags: trunk
14:15
chat: the 'New message...' toast now includes a button which scrolls to the bottom of the message area. check-in: e85b679d99 user: stephan tags: trunk
Changes
Unified Diff Ignore Whitespace Patch
Changes to www/chat.md.
68
69
70
71
72
73
74
75
76


77
78
79





















80
81
82
83
84
85
86
the chat system does try to identify and tag hyperlinks, as follows:

  *  Any word that begins with "http://" or "https://" is assumed
     to be a hyperlink and is tagged.

  *  Text within `[...]` is parsed and it if is a valid hyperlink
     target (according to the way that [Fossil Wiki](/wiki_rules) or
     [Markdown](/md_rules) understand hyperlinks) then that text
     is tagged.



Apart from adding hyperlink anchor tags to bits of text that look
like hyperlinks, no changes are made to the input text.






















## Implementation Details

*You do not need to understand how Fossil chat works in order to use it.
But many developers prefer to know how their tools work.
This section is provided for the benefit of those curious developers.*








|
|
>
>



>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>







68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
the chat system does try to identify and tag hyperlinks, as follows:

  *  Any word that begins with "http://" or "https://" is assumed
     to be a hyperlink and is tagged.

  *  Text within `[...]` is parsed and it if is a valid hyperlink
     target (according to the way that [Fossil Wiki](/wiki_rules) or
     [Markdown](/md_rules) understand hyperlinks) then that text is
     tagged. Note that only URLs and fossil-internal constructs such
     as checkin hashes and wiki pages names are recognized here, not
     constructs such as `[URL | label]` or `[label](URL)`.

Apart from adding hyperlink anchor tags to bits of text that look
like hyperlinks, no changes are made to the input text.

Files may be sent via chat using the file selection element at the
bottom of the page. If the desktop environment system supports it,
files may be dragged and dropped onto that element. Files are not
automatically sent - selection of a file can be cancelled using the
Cancel button which appears only when a file is selected. When the
Send button is pressed, any pending text is submitted along with the
selected file. Image files sent this way will, by default, appear
inline in messages but each user may toggle that via the settings
popup menu, such that images instead appear as downloadable links.
Non-image files always appear in messages as download links.

### Deletion of Messages

Any user may *locally* delete a given message by clicking on the "tab"
at the top of the message and clicking the button which appears. Such
deletions are local-only and the messages will reappear if the page
page is reloaded. Admin users may additionally choose to globally
delete a message from the chat record, which deletes it not only from
their own browser but also propagates the removal to all connected
clients the next time they poll for new messages.

## Implementation Details

*You do not need to understand how Fossil chat works in order to use it.
But many developers prefer to know how their tools work.
This section is provided for the benefit of those curious developers.*