tiddlywiki 5.3.7 → 5.4.0

package/editions/tw5.com/tiddlers/testcases/Calls/ProcedureStaticAttributes.tid

@@ -0,0 +1,48 @@
+created: 20260301000418824
+description: Procedure calls with static attributes
+modified: 20260301031128810
+tags: $:/tags/wiki-test-spec
+title: TestCases/Calls/ProcedureStaticAttributes
+type: text/vnd.tiddlywiki-multiple
+
+title: Narrative
+
+Positional, old style colon named parameters, and new-style equals sign named parameters support static values
++
+title: Output
+
+\procedure p(a1) <$text text=<<a1>>/>
+
+<<p foo1>> -
+<<p a1:foo2>> -
+<<p a1=foo3>>
+
+<<p "foo 4">> -
+<<p a1:"foo 5">> -
+<<p a1="foo 6">>
+
+<<p 'foo 7'>> -
+<<p a1:'foo 8'>> -
+<<p a1='foo 9'>>
+
+<<p """foo 10""">> -
+<<p a1:"""foo 11""">> -
+<<p a1="""foo 12""">>
+
+<<p [[foo 13]]>> -
+<<p a1:[[foo 14]]>> -
+<<p a1=[[foo 15]]>>
++
+title: ExpectedResult
+
+<p>foo1 -
+foo2 -
+foo3</p><p>foo 4 -
+foo 5 -
+foo 6</p><p>foo 7 -
+foo 8 -
+foo 9</p><p>foo 10 -
+foo 11 -
+foo 12</p><p>foo 13 -
+foo 14 -
+foo 15</p>

package/editions/tw5.com/tiddlers/testcases/RevealWidget/AccordionSlider.tid

@@ -27,4 +27,4 @@ And this is some text
 +
 title: ExpectedResult
 
-<div class=" tc-reveal"><p><button class="">Show me</button></p></div><div class=" tc-reveal" hidden="true"></div>
+<div class="tc-reveal"><p><button class="">Show me</button></p></div><div class="tc-reveal" hidden="true"></div>

package/editions/tw5.com/tiddlers/testcases/RevealWidget/Popup.tid

@@ -24,4 +24,4 @@ And this is some text
 +
 title: ExpectedResult
 
-<p><button aria-expanded="false" class="">Pop me up!</button></p><p><span class=" tc-reveal" hidden="true"></span></p>
+<p><button aria-expanded="false" class="">Pop me up!</button></p><p><span class="tc-reveal" hidden="true"></span></p>

package/editions/tw5.com/tiddlers/testcases/RevealWidget/SimpleReveal.tid

@@ -24,4 +24,4 @@ And this is some text
 title: ExpectedResult
 
 <p><button class="">Show me</button>
-<button class="">Hide me</button></p><div class=" tc-reveal" hidden="true"></div>
+<button class="">Hide me</button></p><div class="tc-reveal" hidden="true"></div>

package/editions/tw5.com/tiddlers/testcases/RevealWidget/TextReference.tid

@@ -18,6 +18,6 @@ jeremy: tiddlywiki
 +
 title: ExpectedResult
 
-<p><span class=" tc-reveal">
+<p><span class="tc-reveal">
 TiddlyWiki!
 </span></p>

package/editions/tw5.com/tiddlers/v5.4.0/Improvements to Macro Calls.tid

@@ -0,0 +1,48 @@
+title: Improvements to Macro Calls in v5.4.0
+tags: v5.4.0
+
+<$macrocall $name='wikitext-example-without-html'
+src="""\define testmacro(one)
+Result: $one$.
+\end testmacro
+
+<<testmacro one={{{ [[There]addprefix[Hello]] }}}>>
+"""/>
+
+<$macrocall $name='wikitext-example-without-html'
+src="""\function testfunction(one)
+[<one>addprefix[Hello]]
+\end testfunction
+
+<<testfunction one={{{ [[re]addprefix[The]] }}}>>
+"""/>
+
+<$macrocall $name='wikitext-example-without-html'
+src="""\define testmacro(one)
+Result: $one$.
+\end testmacro
+
+<$text text=<<testmacro one={{{ [[There]addprefix[Hello]] }}}>>/>
+"""/>
+
+<$macrocall $name='wikitext-example-without-html'
+src="""\function testfunction(one)
+[<one>addprefix[Hello]]
+\end testfunction
+
+<$text text=<<testfunction one={{{ [[re]addprefix[The]] }}}>>/>
+"""/>
+
+<$macrocall $name='wikitext-example'
+src="""\define innermacro(one)
+:$one$:$one$:
+\end innermacro
+
+\define mymacro(param)
+|$param$|$param$|
+\end mymacro
+
+<div class=<<mymacro param={{{ [<innermacro one={{$:/palette}}>addprefix[The palette named ]] }}}>>>
+Content
+</div>
+"""/>

package/editions/tw5.com/tiddlers/variables/Behaviour of called variables depends on how the variable was declared.tid

@@ -0,0 +1,52 @@
+created: 20230726145210484
+modified: 20260130210336084
+tags: [[Variable Usage]]
+title: Behaviour of called variables depends on how the variable was declared
+type: text/vnd.tiddlywiki
+
+\define m1(a1) $a1$ - <<__a1__>> - <<a1>>
+\procedure p1(a1) $a1$ - <<__a1__>> - <<a1>>
+\function f1(a1) "$a1$" "-" [<__a1__>] ="-" [<a1>] :and[join[ ]]
+
+Called in normal wikitext context: `<$transclude $variable=myvar/>` or `<<myvar>>`
+
+{{Behaviour of variables called via normal wikitext}}
+
+Called via widget attribute: `<div class=<<myvar>>/>`
+
+{{Behaviour of variables called via widget attributes}}
+
+Called via filter operator parameter: `[<myvar>]`
+
+{{Behaviour of variables called via filter operator parameter}}
+
+Called via function call in a filter expression: `[function[.myfun]]`
+
+{{Behaviour of variables called via filter expression function call}}
+
+!! Examples
+
+Below is an example macro, procedure and function definition.  All three forms of parameter substitution `$a1$`, `<<__a1__>>`, and `<<a1>>` are included in each definition. The output helps illustrate when each form of substitution will or will not have affect.
+
+```
+\define m1(a1) $a1$ - <<__a1__>> - <<a1>>
+\procedure p1(a1) $a1$ - <<__a1__>> - <<a1>>
+\function f1(a1) $a1$ "-" [<__a1__>] ="-" [<a1>] :and[join[ ]]
+```
+
+| !Variable transclusion|!output |
+| `<<m1 foo>>`|<<m1 foo>>|
+| `<<p1 foo>>`|<<p1 foo>>|
+| `<<f1 foo>>`|<<f1 foo>>|
+| !Widget attribute|!output |
+| `<$text text=<<m1 foo>>/>`|<$text text=<<m1 foo>>/>|
+| `<$text text=<<p1 foo>>/>`|<$text text=<<p1 foo>>/>|
+| `<$text text=<<f1 foo>>/>`|<$text text=<<f1 foo>>/>|
+| !Filter operator parameter|!output |
+| `[<m1 foo>]`|<$text text={{{[<m1 foo>]}}}/>|
+| `[<p1 foo>]`|<$text text={{{[<p1 foo>]}}}/>|
+| `[<f1 foo>]`|<$text text={{{[<f1 foo>]}}}/>|
+| !Function call in filter expression|!output |
+| `[function[m1],[foo]]`|<$text text={{{[function[m1],[foo]]}}}/>|
+| `[function[p1],[foo]]`|<$text text={{{[function[p1],[foo]]}}}/>|
+| `[function[f1],[foo]]`|<$text text={{{[function[f1],[foo]]}}}/>|

package/editions/tw5.com/tiddlers/variables/Behaviour of variables invoked via filter expression function call.tid

@@ -6,5 +6,5 @@ type: text/vnd.tiddlywiki
 
 |tc-first-col-min-width|k
 |!how declared|!behaviour|
-|\define, <<.wlink SetWidget>>, <<.wlink LetWidget>>, <<.wlink VarsWidget>>, \procedure, \widget|Every function is a variable, but only variables defined using \function are invokable using the <<.olink function>> filter operator. Attempts to use a non-function variable is the same as if the function doesn't exist. The behavior in this case is like the identity function. All filter input is passed unchanged to the output.|
+|\define, <<.wlink SetWidget>>, <<.wlink LetWidget>>, <<.wlink VarsWidget>>, \procedure, \widget|Every function is a variable, but only variables defined using \function are callable using the <<.olink function>> filter operator. Attempts to use a non-function variable is the same as if the function doesn't exist. The behavior in this case is like the identity function. All filter input is passed unchanged to the output.|
 |\function|The body text of the function is treated as a filter expression and evaluated. This filter expression can itself contain a function call. Filter expressions can be factored out into functions arbitrarily deep.|

package/editions/tw5.com/tiddlers/variables/Behaviour of variables invoked via widget attributes.tid

@@ -8,4 +8,6 @@ type: text/vnd.tiddlywiki
 |!how declared|!behaviour|
 |\define|Textual substitution of parameters is performed on the body text. No further processing takes place. The result after textual substitution is used as the attribute's value|
 |<<.wlink SetWidget>>, <<.wlink LetWidget>>, <<.wlink VarsWidget>>, \procedure, \widget|Body text is retrieved as-is and used as the attribute's value.|
-|\function|When a function (e.g. `.myfun`) is invoked as `<div class=<<.myfun>>/>`, it is a synonym for `<div class={{{[function[.myfun]]}}}/>`. As with any filtered transclusion (i.e. triple curly braces), all results except the first are discarded. That first result is used as the attribute's value. Note that functions are recursively processed even when invoked in this form. In other words a filter expression in a function can invoke another function and the processing will continue|
+|\function|When a function (e.g. `.myfun`) is invoked as `<div class=<<.myfun>>/>`, it is a synonym for `<div class={{{[function[.myfun]]}}}/>`. As with any filtered transclusion (i.e. triple curly braces), all results except the first are discarded. That first result is used as the attribute's value. Note that functions are recursively processed even when invoked in this form. In other words a filter expression in a function can invoke another function and the processing will continue|
+
+<<.from-version "5.4.0">> Using the [[multi-valued variable attribute|Multi-Valued Variable Attribute Values]] syntax `((var))` instead of `<<var>>` passes the complete list of values to the attribute rather than just the first value. This is primarily useful for passing [[multi-valued variables|Multi-Valued Variables]] to procedure and function parameters via the TranscludeWidget.

package/editions/tw5.com/tiddlers/variables/Multi-Valued Variables.tid

@@ -0,0 +1,118 @@
+title: Multi-Valued Variables
+created: 20250307212252946
+modified: 20250307212252946
+tags: Concepts Variables
+
+<<.from-version "5.4.0">> In ordinary usage, [[variables|Variables]] contain a single snippet of text. With the introduction of multi-valued variables. it is now possible to store a list of multiple values in a single variable. When accessed in the usual way, only the first value is returned, but using round brackets instead of angle brackets around the variable name allows access to the complete list of the values. This makes multi-valued variables largely invisible unless you specifically need to use them.
+
+! Setting Multi-Valued Variables
+
+Generally, all the methods for setting variables implicitly set multi-valued variables, with the exception of the [[Set Widget|Set Widget]].
+
+!! LetWidget
+
+The <<.wid let>> widget allows multi-valued variables to be set in one operation, each to the complete list of results obtained from evaluating an attribute that is defined via a filtered transclusion. For example:
+
+```
+<$let
+	varname={{{ [all[tiddlers]sort[]] }}}
+>
+```
+
+The <<.wid let>> widget also allows the complete list of return values from a function to be assigned to a multi-valued variable. For example:
+
+```
+<$let
+	varname=<<my.func>>
+>
+```
+
+!! [[Let Filter Run Prefix]]
+
+The `:let` filter run prefix (or its shortcut syntax `=>`) assigns the complete list of results of a filter run to a multi-valued variable.
+
+! Retrieving Multi-Valued Variables
+
+!! [[title Operator]]
+
+The simplest way to retrieve the complete list of values stored in a multi-valued variable is to use the [[title Operator]]. For example:
+
+```
+[title(varname)]
+```
+
+Because `title` is the default operator when the operator name is missing from a filter step, the following example is equivalent to the previous one:
+
+```
+[(varname)]
+```
+
+!! Multi-valued Parameters for Filter Operators
+
+Certain filter operators can accept multi-valued parameters:
+
+* [[function Operator]]
+* [[title Operator]]
+
+For example:
+
+```
+\function myfunc(tiddlers) [(tiddlers)sort[]]
+
+<$let varname={{{ [all[tiddlers]limit[50]] }}}>
+<$text text={{{ [function[myfunc],(varname)] +[join[-]] }}}/>
+</$let>
+```
+
+!! Passing Multi-Valued Variables to Procedures and Functions
+
+<<.from-version "5.4.0">> Multi-valued variables can be passed to procedures and functions using the `((var))` syntax in [[widget attributes|Multi-Valued Variable Attribute Values]]. This is the multi-valued counterpart of the `<<var>>` syntax:
+
+```
+\procedure showItems(itemList)
+<$text text={{{ [(itemList)join[-]] }}}/>
+\end
+
+<$let items={{{ [all[tiddlers]sort[]] }}}>
+<$transclude $variable="showItems" itemList=((items))/>
+</$let>
+```
+
+The `((var))` syntax can also be used in procedure and function parameter defaults:
+
+```
+\procedure showItems(itemList:((defaults)))
+<$text text={{{ [(itemList)join[-]] }}}/>
+\end
+```
+
+! Displaying Multi-Valued Variables
+
+<<.from-version "5.4.0">> Multi-valued variables can be displayed inline in wikitext using the `((var))` syntax. The values are joined with a comma and space by default:
+
+```
+<$let items={{{ [all[tiddlers]sort[]] }}}>
+((items))
+</$let>
+```
+
+A custom separator can be specified using the `||` delimiter:
+
+```
+((items||:))
+```
+
+A similar syntax with triple round brackets is available for displaying the results of a filter expression:
+
+```
+(((  [all[tiddlers]sort[]]  )))
+(((  [all[tiddlers]sort[]]  ||:  )))
+```
+
+! Examples
+
+```
+<$let varname={{{ [all[tiddlers]sort[]] }}}>
+<$text text={{{ [(varname)] +[join[-]] }}}/>
+</$let>
+```

package/editions/tw5.com/tiddlers/variables/Variables.tid

@@ -1,13 +1,15 @@
 created: 20141002133113496
-modified: 20240422084347375
+modified: 20250307212252946
 tags: Concepts WikiText
 title: Variables
 type: text/vnd.tiddlywiki
 
 !! Introduction
 
-* A <<.def variable>> is a ''snippet of text'' that can be accessed by name.
-* The text is referred to as the variable's <<.def value>>.
+* A <<.def variable>> is a ''snippet of text'' that can be accessed by name
+* The text is referred to as the variable's <<.def value>>
+
+<<.from-version "5.4.0">> In ordinary usage, variables contain a single snippet of text. With the introduction of [[Multi-Valued Variables]] it is possible to store a list of multiple values in a single variable. When accessed in the usual way, only the first value is returned, but using round brackets instead of the usual angle brackets retrieves the complete list of values. This makes the existence of multi-valued variables invisible unless you specifically need to use them.
 
 Variables are defined by [[widgets|Widgets]]. Several core widgets define variables, the most common being the <<.wlink LetWidget>>, <<.wlink SetWidget>> and <<.wlink ListWidget>> widgets.
 

package/editions/tw5.com/tiddlers/webserver/WebServer API_ Get All Tiddlers.tid

@@ -22,7 +22,7 @@ In order to avoid denial of service attacks with malformed filters in the defaul
 To enable a particular filter, create a tiddler with the title "$:/config/Server/ExternalFilters/" concatenated with the filter text, and the text field set to "yes". For example, the TiddlyWeb plugin includes the following shadow tiddler to enable the filter that it requires:
 
 ```
-title: $:/config/Server/ExternalFilters/[all[tiddlers]] -[[$:/isEncrypted]] -[prefix[$:/temp/]] -[prefix[$:/status/]] -[[$:/boot/boot.js]] -[[$:/boot/bootprefix.js]] -[[$:/library/sjcl.js]] -[[$:/core]]
+title: $:/config/Server/ExternalFilters/[all[tiddlers]] -[[$:/isEncrypted]] -[prefix[$:/temp/]] -[prefix[$:/status/]] -[[$:/boot/boot.js]] -[[$:/boot/bootprefix.js]] -[has[plugin-type]field:platform[server]] -[[$:/library/sjcl.js]] -[[$:/core]]
 text: yes
 ```
 

package/editions/tw5.com/tiddlers/webserver/WebServer API_ Get File.tid

@@ -1,5 +1,5 @@
 created: 20181002123907518
-modified: 20181002124345482
+modified: 20250605000000000
 tags: [[WebServer API]]
 title: WebServer API: Get File
 type: text/vnd.tiddlywiki
@@ -15,11 +15,22 @@ Parameters:
 
 * ''pathname'' - URI encoded path to the file
 
+Headers:
+
+* ''Range'' - <<.from-version "5.3.7">> (optional) Request specific byte ranges using the format `bytes=start-end`. Supports partial content delivery for media streaming.
+
 Response:
 
 * 200 OK
 *> `Content-Type: <content-type>` (determined from file extension)
-*> Body: data retrieved from file
+*> `Content-Length: <file-size>`
+*> `Accept-Ranges: bytes`
+*> Body: complete file data
+* 206 Partial Content (when Range header is provided)
+*> `Content-Type: <content-type>` (determined from file extension)
+*> `Content-Length: <range-size>`
+*> `Content-Range: bytes <start>-<end>/<total-size>`
+*> `Accept-Ranges: bytes`
+*> Body: requested byte range data
 * 403 Forbidden
 * 404 Not Found
-

package/editions/tw5.com/tiddlers/widgets/ActionLogWidget.tid

@@ -1,50 +1,77 @@
 caption: action-log
 created: 20201114113318785
-modified: 20201120155202652
+modified: 20260105121108063
 tags: Widgets ActionWidgets [[Debugging Widgets]]
 title: ActionLogWidget
 type: text/vnd.tiddlywiki
 
 ! Introduction
 
-<<.from-version "5.1.23">> The ''action-log'' widget is an [[action widget|ActionWidgets]] that can be used to output debugging information to the [[JavaScript console|Web Developer Tools]] supported by most browsers. This can be useful because otherwise it is difficult to observe what is going on within a sequence of actions.
+<<.from-version "5.1.23">> The <<.wid action-log>> widget is an [[action widget|ActionWidgets]] that can be used to output debugging information to the [[JavaScript console|Web Developer Tools]] supported by most browsers. This can be useful to observe and debug the behavior within a sequence of actions.
+
+When the action is invoked, the names and values of all [[attributes|Widget Attributes]] are logged to the JavaScript console.
+
+```
+<$action-log name=value />
+```
 
 ActionWidgets are used within triggering widgets such as the ButtonWidget.
 
-<<.tip """ For debugging outside of actions see [[LogWidget]]""">>
+<<.note """ For debugging outside of actions see [[LogWidget]]""">>
 
 ! Content and Attributes
 
-The ''action-log'' widget is invisible. Any content within it is ignored.
+The <<.wid action-log>> widget is invisible. Any content within it is ignored.
 
-When the actions are invoked, the names and values of all attributes are logged to the JavaScript console.
-In addition there are optional attributes that can be used:
+<<.from-version "5.4.0">> Any [[multi-valued variables|Multi-Valued Variables]] or attributes are logged as a list of values.
 
-|!Optional Attribute |!Description |
-|$$filter|All variables matching this filter will also be logged. |
-|$$message |A message to display as the title of the information logged. Useful when several `action-log` widgets are used in sequence. |
-|$$all |Set to "yes" to log all variables in a collapsed table. Note that if there is nothing specified to log, all variables are always logged instead.|
+|!Attribute |!Description |
+|<<.attr $$filter>>|(Optional) All variables whose name matches the [[Filter Expression]] will be logged |
+|<<.attr $$message>> |(Optional) A message to display as the title of the information logged. Useful when several <<.wid action-log>> widgets are used in sequence |
+|<<.attr $$all>> |(Optional) Set to <<.value yes>> to log all variables |
 
+<<.note """ If `<$action-log />` is called without any attributes, all defined variables will be logged as if `$$all=yes` were set.""">>
 
-<<.tip """A handy tip if an action widget is not behaving as expected is to temporarily change it to an `<$action-log>` widget so that the attributes can be observed.""">>
+<<.note """When logging [[Variable Attribute Values]], the body text of macros and procedures will be output as their value. Functions are evaluated and their first result is logged.""">>
 
-! Example
+! Examples
 
-Here is an example of logging two variables:
+!! Basic Example
+
+Log the value of variable <<.var name>>, the first result of the filter expression `[tag[Learning]]` and the value of field <<.field created>> of the current tiddler:
 
 ```
-<$action-log myVar=<<myVar>> otherVar=<<otherVar>>/>
+<$action-log name=<<name>> filter={{{ [tag[Learning]] }}} created={{!!created}} />
 ```
 
-To log all variables:
+!! Example using <<.attr $$filter>> and <<.attr $$message>> 
+
+Log all core variables (which start with <<.var tv->>) with a table title:
 
 ```
-<$action-log />
+<$action-log $$message="Core Variables" $$filter="[prefix[tv-]]" />
 ```
 
+!! Widget Debugging
 
-To log two variables as well as all core variables (which start with `tv-`):
+Change a misbehaving <<.wlink ActionSetFieldWidget>> widget to an <<.wid action-log>> widget to verify that <<.var currentTiddler>> and <<.var value>> match their expected values:
+
+<<.tip """If an action widget is not behaving as expected it is often useful to temporarily change it to an <<.wid action-log>> widget so that the passed attributes can be verified.""">>
 
 ```
-<$action-log myVar=<<myVar>> other={{!!status}} $$filter="[prefix[tv-]]"/>
+<$action-log $tiddler=<<currentTiddler>> $field="text" $value=<<value>> />
 ```
+
+This application is the primary reason that the attributes of the <<.wid action-log>> widget are prefixed with two dollar signs instead of one. Otherwise, the attributes of the original widget could be interpreted as attributes to <<.wid action-log>> and lead to unintended consequences.
+
+!! Example with Function
+
+Log the <<.var tiddlerList>> function definition and its first evaluation result:
+
+```
+\function tiddlerList() [tag[Learning]]
+
+<$action-log $$filter="[title[tiddlerList]]" value=<<tiddlerList>> />
+```
+
+<<.note """The values output with the <<.attr $$filter>> or <<.attr $$all>> attributes will only contain the definition of functions instead of their values, as the evaluation of many functions can lead to significant performance penalties.""">>

package/editions/tw5.com/tiddlers/widgets/ButtonWidget.tid

@@ -1,6 +1,6 @@
 caption: button
 created: 20131024141900000
-modified: 20231113093304323
+modified: 20251101091926820
 tags: Widgets TriggeringWidgets
 title: ButtonWidget
 type: text/vnd.tiddlywiki
@@ -9,11 +9,11 @@ type: text/vnd.tiddlywiki
 
 The button widget displays an HTML `<button>` element that can perform a combination of optional actions when clicked:
 
-* Executing any ActionWidgets passed in the `actions` attribute
-* Executing any ActionWidgets that are immediate children of the button widget
+* Executing any ActionWidgets passed in the `actions` attribute, which is the preferred approach
+* Executing any ActionWidgets that are immediate children of the button widget, which is now deprecated in favour of using the `actions` attribute
 * Execute any integrated actions:
 ** Navigate to a specified tiddler
-** Dispatch a user defined [[widget message|Messages]]
+** Dispatch a user defined [[widget message|Core Messages]]
 ** Trigger a user defined [[popup|PopupMechanism]]
 ** Assign new text to a specified tiddler
 
@@ -34,15 +34,18 @@ The content of the `<$button>` widget is displayed within the button.
 |setIndex |An ''index'' to which the new value will be assigned, if the attribute <<.attr setTitle>> is present |
 |setTo |The new value to assign to the TextReference identified in the `set` attribute or the text field / the field specified through <<.attr setField>> / the index specified through <<.attr setIndex>> of the title given through <<.attr setTitle>> |
 |selectedClass |An optional additional CSS class to be assigned if the popup is triggered or the tiddler specified in <<.attr set>> already has the value specified in <<.attr setTo>>  |
+|selectedAria |<<.from-version "5.4.0">> An ARIA attribute to be set to `true` or `false` when <<.attr selectedClass>> is defined. Allowed values are `aria-checked` (default), `aria-selected` and `aria-pressed`  |
 |default |Default value if <<.attr set>> tiddler is missing for testing against <<.attr setTo>> to determine <<.attr selectedClass>> |
 |popup |Title of a state tiddler for a popup that is toggled when the button is clicked. See PopupMechanism for details |
 |popupTitle |Title of a state tiddler for a popup that is toggled when the button is clicked. In difference to the <<.attr popup>> attribute, ''no'' TextReference is used. See PopupMechanism for details |
 |popupAbsCoords |<<.from-version "5.2.4">> If set to ''yes'' writes absolute coordinates to the tiddler referenced by the <<.attr popup>>. If set to ''no'' (the default) uses relative coordinates. See [[Coordinate Systems]] for details |
 |aria-label |Optional [[Accessibility]] label |
+|role |<<.from-version "5.2.3">> Optional [[ARIA role|https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles]] |
 |tooltip |Optional tooltip |
 |class |An optional CSS class name to be assigned to the HTML element|
 |data-* |<<.from-version "5.3.2">> Optional [[data attributes|https://developer.mozilla.org/en-US/docs/Learn/HTML/Howto/Use_data_attributes]] to be assigned to the HTML element |
 |style.* |<<.from-version "5.3.2">> Optional [[CSS properties|https://developer.mozilla.org/en-US/docs/Web/CSS/Reference]] to be assigned to the HTML element |
+|aria-* |<<.from-version "5.4.0">> Optional [[ARIA attributes|https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes]]. |
 |style |An optional CSS style attribute to be assigned to the HTML element |
 |tag |An optional html tag to use instead of the default "button" |
 |dragTiddler |An optional tiddler title making the button draggable and identifying the payload tiddler. See DraggableWidget for details |