DevOps:Doc/FlexForm/2.0/ShowOnSelect - Revision history

Fd4138e7-8b46-4c8f-99bf-d4b738ebc295 at 07:35, 30 March 2026

2026-03-30T07:35:32Z

← Older revision		Revision as of 09:35, 30 March 2026
Line 62:		Line 62:
	</form>		</form>
	</syntaxhighlight>		</syntaxhighlight>
	<form show-on-select="show-on-select" restrictions="lifted" >		<form show-on-select="show-on-select" restrictions="lifted" ><!-- Example 2 -->
	<select name="selectme" id="selectme" >		<select name="selectme" id="selectme" >
	<option for="selectme" show-on-select="testingId2" selected="selected" value="1">1</option>		<option for="selectme" show-on-select="testingId2" selected="selected" value="1">1</option>
Line 81:		Line 81:
	</form>		</form>
	</syntaxhighlight>		</syntaxhighlight>
	<form show-on-select="show-on-select" restrictions="lifted" >		<form show-on-select="show-on-select" restrictions="lifted" ><!-- Example 3 -->
	<input type="radio" show-on-checked="tester"/>		<input type="radio" show-on-checked="tester"/>
	<div show-on-select-trigger="tester">		<div show-on-select-trigger="tester">
Line 96:		Line 96:
	</form>		</form>
	</syntaxhighlight>		</syntaxhighlight>
	<form action="addToWiki" show-on-select="show-on-select" restrictions="lifted" >		<form action="addToWiki" show-on-select="show-on-select" restrictions="lifted" ><!-- Example 4 -->
	<input type="checkbox" show-on-checked="test A" show-on-unchecked="test B" />		<input type="checkbox" show-on-checked="test A" show-on-unchecked="test B" />
	<div show-on-select-trigger="test A">test checked</div>		<div show-on-select-trigger="test A">test checked</div>
Line 111:		Line 111:
	</form>		</form>
	</syntaxhighlight>		</syntaxhighlight>
	<form show-on-select="show-on-select" restrictions="lifted" >		<form show-on-select="show-on-select" restrictions="lifted" ><!-- Example 5 -->
	<input type="text" show-on-select="testingId" name="test" /> The predefined value is "testingValue"		<input type="text" show-on-select="testingId" name="test" /> The predefined value is "testingValue"
	<div show-on-select-trigger="testingId" show-on-select-type="equals::testingValue">		<div show-on-select-trigger="testingId" show-on-select-type="equals::testingValue">
Line 128:		Line 128:
	</form>		</form>
	</syntaxhighlight>		</syntaxhighlight>
	<form show-on-select="show-on-select" restrictions="lifted" >		<form show-on-select="show-on-select" restrictions="lifted"><!-- Example 6 -->
	<input type="text" show-on-select="testingId" name="test" /> The predefined value is "testingValue"		<input type="text" show-on-select="testingId" name="test" /> The predefined value is "testingValue"
	<div show-on-select-trigger="testingId" show-on-select-type="contains::testingValue">		<div show-on-select-trigger="testingId" show-on-select-type="contains::testingValue">
Line 151:		Line 151:
	</form>		</form>
	</syntaxhighlight>		</syntaxhighlight>
	<form show-on-select="show-on-select" restrictions="lifted" >		<form show-on-select="show-on-select" restrictions="lifted" ><!-- Example 7 -->
	<select name="selectme" id="selectme" >		<select name="selectme" id="selectme" >
	<option for="selectme" show-on-select="testingId2" selected="selected" value="1">1</option >		<option for="selectme" show-on-select="testingId2" selected="selected" value="1">1</option >
Line 180:		Line 180:
	</form>		</form>
	</syntaxhighlight>		</syntaxhighlight>
	<form show-on-select="show-on-select" restrictions="lifted" >		<form show-on-select="show-on-select" restrictions="lifted" ><!-- Example 8 -->
	<select name="selectme" id="selectme2" >		<select name="selectme" id="selectme2" >
	<option for="selectme2" show-on-select="testingId2" selected="selected" value="1">1</option >		<option for="selectme2" show-on-select="testingId2" selected="selected" value="1">1</option >

Charlot at 11:36, 24 March 2026

2026-03-24T11:36:56Z

← Older revision		Revision as of 13:36, 24 March 2026
Line 4:		Line 4:
	form		form
	===Synopsis===		===Synopsis===
	Show or hide elements based on a form input change		Show or hide elements based on a form input change.
	===Description===		===Description===
	This allows to show elements in a form based on a selection option, a checkbox status or radio button status.		This allows to show elements in a form based on a selection option, a checkbox status or radio button status.

Fd4138e7-8b46-4c8f-99bf-d4b738ebc295: Text replacement - "|Subject version=2.0,2.1" to "|Subject version=2.0,2.1,2.5"

2025-08-21T09:13:04Z

Text replacement - "|Subject version=2.0,2.1" to "|Subject version=2.0,2.1,2.5"

ws-class-props
← Older revision		Revision as of 11:13, 21 August 2025
Line 1:		Line 1:
	{{Csp class properties		{{Csp class properties
	\|Subject version=2.0,2.1		\|Subject version=2.0,2.1,2.5
	\|Doc subject=DevOps:Doc/FlexForm		\|Doc subject=DevOps:Doc/FlexForm
	\|Doc sort order=225		\|Doc sort order=225

Maintenance script: Imported by PageSync

2025-07-15T08:34:52Z

Imported by PageSync

ws-class-props
← Older revision		Revision as of 10:34, 15 July 2025
Line 1:		Line 1:
	{{~~Doc~~ properties		{{Csp class properties
	\|Subject version=2.0,2.1		\|Subject version=2.0,2.1
	\|Doc subject=DevOps:Doc/FlexForm		\|Doc subject=DevOps:Doc/FlexForm

Fd4138e7-8b46-4c8f-99bf-d4b738ebc295 at 06:46, 16 July 2024

2024-07-16T06:46:46Z

← Older revision		Revision as of 08:46, 16 July 2024
Line 197:		Line 197:
	* Currently if the AND or OR triggers are wrongly defined, no form will be rendered. It's on the list to be fixed.		* Currently if the AND or OR triggers are wrongly defined, no form will be rendered. It's on the list to be fixed.
	* There is one notable difference between the way FlexForm and Page Forms let you tie multiple selectors to the same selectable area, aside from differences in their choice of attributes. Where PageForms insists that each selectable area has a unique ID and lets you connect it to one or multiple selectors, FlexForm lets you assign one or multiple identifiers (<code>show-on-select-trigger</code>) to each selectable area while insisting that the <code>show-on-select</code> attributes are unique to individual selectors.		* There is one notable difference between the way FlexForm and Page Forms let you tie multiple selectors to the same selectable area, aside from differences in their choice of attributes. Where PageForms insists that each selectable area has a unique ID and lets you connect it to one or multiple selectors, FlexForm lets you assign one or multiple identifiers (<code>show-on-select-trigger</code>) to each selectable area while insisting that the <code>show-on-select</code> attributes are unique to individual selectors.
	* When you have multiple select elements in a form, you need to add the '''<code>for=</code>''' argument to every option field. This ways, regardless in what order MediaWiki will parse the form element, FlexForm will always know what option fields belong to what select element.		* When you have multiple select elements in a form, you need to add the '''<code>for=</code>''' argument to every option field. The value should be the value of the '''select''' '''''id''''' argument. This ways, regardless in what order MediaWiki will parse the form element, FlexForm will always know what option fields belong to what select element.

	===Links===		===Links===
	Tutorial on show-on-select : https://wikibase-solutions.com/developer-logs/flexform-show-on-select?WSLanguage=en		Tutorial on show-on-select : https://wikibase-solutions.com/developer-logs/flexform-show-on-select?WSLanguage=en

Fd4138e7-8b46-4c8f-99bf-d4b738ebc295 at 06:45, 16 July 2024

2024-07-16T06:45:30Z

← Older revision		Revision as of 08:45, 16 July 2024
Line 197:		Line 197:
	* Currently if the AND or OR triggers are wrongly defined, no form will be rendered. It's on the list to be fixed.		* Currently if the AND or OR triggers are wrongly defined, no form will be rendered. It's on the list to be fixed.
	* There is one notable difference between the way FlexForm and Page Forms let you tie multiple selectors to the same selectable area, aside from differences in their choice of attributes. Where PageForms insists that each selectable area has a unique ID and lets you connect it to one or multiple selectors, FlexForm lets you assign one or multiple identifiers (<code>show-on-select-trigger</code>) to each selectable area while insisting that the <code>show-on-select</code> attributes are unique to individual selectors.		* There is one notable difference between the way FlexForm and Page Forms let you tie multiple selectors to the same selectable area, aside from differences in their choice of attributes. Where PageForms insists that each selectable area has a unique ID and lets you connect it to one or multiple selectors, FlexForm lets you assign one or multiple identifiers (<code>show-on-select-trigger</code>) to each selectable area while insisting that the <code>show-on-select</code> attributes are unique to individual selectors.
	* When you have multiple select elements in a form, you need to add the <~~syntaxhighlight lang="html"~~>for=</~~syntaxhighlight~~> argument to every option field. This ways, regardless in what order MediaWiki will parse the form element, FlexForm will always know what option fields belong to what select element.		* When you have multiple select elements in a form, you need to add the '''<code>for=</code>''' argument to every option field. This ways, regardless in what order MediaWiki will parse the form element, FlexForm will always know what option fields belong to what select element.

	===Links===		===Links===
	Tutorial on show-on-select : https://wikibase-solutions.com/developer-logs/flexform-show-on-select?WSLanguage=en		Tutorial on show-on-select : https://wikibase-solutions.com/developer-logs/flexform-show-on-select?WSLanguage=en

Fd4138e7-8b46-4c8f-99bf-d4b738ebc295 at 06:44, 16 July 2024

2024-07-16T06:44:16Z

← Older revision		Revision as of 08:44, 16 July 2024
Line 197:		Line 197:
	* Currently if the AND or OR triggers are wrongly defined, no form will be rendered. It's on the list to be fixed.		* Currently if the AND or OR triggers are wrongly defined, no form will be rendered. It's on the list to be fixed.
	* There is one notable difference between the way FlexForm and Page Forms let you tie multiple selectors to the same selectable area, aside from differences in their choice of attributes. Where PageForms insists that each selectable area has a unique ID and lets you connect it to one or multiple selectors, FlexForm lets you assign one or multiple identifiers (<code>show-on-select-trigger</code>) to each selectable area while insisting that the <code>show-on-select</code> attributes are unique to individual selectors.		* There is one notable difference between the way FlexForm and Page Forms let you tie multiple selectors to the same selectable area, aside from differences in their choice of attributes. Where PageForms insists that each selectable area has a unique ID and lets you connect it to one or multiple selectors, FlexForm lets you assign one or multiple identifiers (<code>show-on-select-trigger</code>) to each selectable area while insisting that the <code>show-on-select</code> attributes are unique to individual selectors.
			* When you have multiple select elements in a form, you need to add the <syntaxhighlight lang="html">for=</syntaxhighlight> argument to every option field. This ways, regardless in what order MediaWiki will parse the form element, FlexForm will always know what option fields belong to what select element.

	===Links===		===Links===
	Tutorial on show-on-select : https://wikibase-solutions.com/developer-logs/flexform-show-on-select?WSLanguage=en		Tutorial on show-on-select : https://wikibase-solutions.com/developer-logs/flexform-show-on-select?WSLanguage=en

Charlot: User:Charlot

2023-03-31T20:13:41Z

User:Charlot

ws-class-props
← Older revision		Revision as of 22:13, 31 March 2023
Line 1:		Line 1:
	{{Doc properties		{{Doc properties
	\|Subject version=2.0		\|Subject version=2.0,2.1
	\|Doc subject=DevOps:Doc/FlexForm		\|Doc subject=DevOps:Doc/FlexForm
	\|Doc sort order=225		\|Doc sort order=225

Charlot at 13:18, 4 January 2023

2023-01-04T13:18:37Z

Show changes

Charlot: User:Charlot

2023-01-04T13:09:16Z

User:Charlot

ws-class-props
← Older revision		Revision as of 15:09, 4 January 2023
Line 4:		Line 4:
	\|Doc sort order=225		\|Doc sort order=225
	\|Doc target group=User		\|Doc target group=User
			\|Doc synopsis=Show or hide elements based on a form input change
			\|Doc parent=
	}}		}}