wikimedia/mediawiki-extensions-InputBox
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/InputBox synced 2024-11-24 07:03:41 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-InputBox/tests/parser/inputBoxParserTests.txt

258 lines
14 KiB
Plaintext
Raw Permalink Normal View History

Update parserTests to v2 (tidy by default) Bug: T249137 Change-Id: I746ee2b985537dc6bbb8a114e21cd11a683e0f74
2020-04-01 19:44:44 +00:00
!! Version 2
# Force the test runner to ensure the extension is loaded
!! hooks
inputbox
!! endhooks
Add parser tests Change-Id: I718b0e0c1dd0a4507e77abc7e2cb88800ae2176a
2016-07-08 06:18:43 +00:00
!! test
InputBox type=search
!! wikitext
<inputbox>
type=search
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="searchbox" class="searchbox" action="/wiki/Special:Search"><input class="mw-inputbox-input mw-searchInput searchboxInput mw-ui-input mw-ui-input-inline" name="search" placeholder="" size="50" dir="ltr" /><br /><input type="submit" name="go" class="mw-ui-button" value="Try exact match" />&#160;<input type="submit" name="fulltext" class="mw-ui-button" value="Search full text" /></form></div>
Add parser tests Change-Id: I718b0e0c1dd0a4507e77abc7e2cb88800ae2176a
2016-07-08 06:18:43 +00:00
!! end
!! test
InputBox type=create
!! wikitext
<inputbox>
type=create
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with minor
!! wikitext
<inputbox>
type=create
minor=1
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" value="1" name="minor" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with minor=0
!! wikitext
<inputbox>
type=create
minor=0
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" value="0" name="minor" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with preloadparams
!! wikitext
<inputbox>
type=create
preloadparams[]=param1
preloadparams[]=param2
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" value="param1" name="preloadparams[]" /><input type="hidden" value="param2" name="preloadparams[]" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with empty preloadparams
!! wikitext
<inputbox>
type=create
preloadparams[]=
preloadparams[]=
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" name="preloadparams[]" /><input type="hidden" name="preloadparams[]" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with editintro
!! wikitext
<inputbox>
type=create
editintro=MediaWiki:Test
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" value="MediaWiki:Test" name="editintro" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with empty editintro
!! wikitext
<inputbox>
type=create
editintro=
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" name="editintro" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with summary
!! wikitext
<inputbox>
type=create
summary=Summary test
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" value="Summary test" name="summary" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with empty summary
!! wikitext
<inputbox>
type=create
summary=
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" name="summary" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with nosummary
!! wikitext
<inputbox>
type=create
nosummary=true
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" value="true" name="nosummary" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with empty nosummary
!! wikitext
<inputbox>
type=create
nosummary=
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" name="nosummary" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with prefix
!! wikitext
<inputbox>
type=create
prefix=Test/
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" value="Test/" name="prefix" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with empty prefix
!! wikitext
<inputbox>
type=create
prefix=
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with preload
!! wikitext
<inputbox>
type=create
preload=test
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" value="test" name="preload" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Don't add url parameters to an input box, if the parameter is empty If a parameter isn't set, it shouldn't be added to the form. Bug: T147048 Change-Id: I7e5aa21528fbc98e9e4d52baca93870f213d4c15
2016-10-04 20:24:54 +00:00
!! end
!! test
InputBox type=create with empty preload
!! wikitext
<inputbox>
type=create
preload=
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" name="preload" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Create page" /></form></div>
Add parser tests Change-Id: I718b0e0c1dd0a4507e77abc7e2cb88800ae2176a
2016-07-08 06:18:43 +00:00
!! end
!! test
InputBox type=comment
!! wikitext
<inputbox>
type=comment
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input type="hidden" value="new" name="section" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" placeholder="" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="New section" /></form></div>
Add parser tests Change-Id: I718b0e0c1dd0a4507e77abc7e2cb88800ae2176a
2016-07-08 06:18:43 +00:00
!! end
!! test
InputBox type=commenttitle
!! wikitext
<inputbox>
type=commenttitle
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="commentbox" class="commentbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input name="preloadtitle" class="mw-inputbox-input commentboxInput mw-ui-input mw-ui-input-inline" placeholder="" size="50" dir="ltr" /><input type="hidden" value="new" name="section" /><input type="hidden" name="title" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="New section" /></form></div>
Add parser tests Change-Id: I718b0e0c1dd0a4507e77abc7e2cb88800ae2176a
2016-07-08 06:18:43 +00:00
!! end
!! test
InputBox type=fulltext
!! wikitext
<inputbox>
type=fulltext
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="searchbox" class="searchbox" action="/wiki/Special:Search"><input class="mw-inputbox-input mw-searchInput searchboxInput mw-ui-input mw-ui-input-inline" name="search" placeholder="" size="50" dir="ltr" /><br /><input type="submit" name="fulltext" class="mw-ui-button" value="Search full text" /><input type="hidden" value="Search" name="fulltext" /></form></div>
Add parser tests Change-Id: I718b0e0c1dd0a4507e77abc7e2cb88800ae2176a
2016-07-08 06:18:43 +00:00
!! end
!! test
InputBox type=move
!! wikitext
<inputbox>
type=move
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="movebox" class="mw-movebox" action="/index.php" method="get"><input type="hidden" value="Special:MovePage/" name="title" /><input type="hidden" name="wpReason" /><input type="hidden" name="prefix" /><input name="wpNewTitle" class="mw-inputbox-input mw-moveboxInput mw-ui-input mw-ui-input-inline" placeholder="" size="50" dir="ltr" /><br /><input type="submit" class="mw-ui-button mw-ui-progressive" value="Move page" /></form></div>
Add parser tests Change-Id: I718b0e0c1dd0a4507e77abc7e2cb88800ae2176a
2016-07-08 06:18:43 +00:00
!! end
Add tour parameter Add an optional tour parameter with adds `&tour=[x]` to the local Special:Search URL Remove whitespace error Add test Modify test HTML (x3) Bug: T174077 Change-Id: Iaaf1d04e1939bd555cacd4ea3ac4390d7e43b19d
2017-08-24 19:45:31 +00:00
!! test
InputBox type=search with tour
!! wikitext
<inputbox>
type=search
tour=test
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="searchbox" class="searchbox" action="/wiki/Special:Search"><input class="mw-inputbox-input mw-searchInput searchboxInput mw-ui-input mw-ui-input-inline" name="search" placeholder="" size="50" dir="ltr" /><input type="hidden" value="test" name="tour" /><br /><input type="submit" name="go" class="mw-ui-button" value="Try exact match" />&#160;<input type="submit" name="fulltext" class="mw-ui-button" value="Search full text" /></form></div>
Have inputbox langconvert certain attributes This approximates the behaviour prior to core change for T119158. It will language convert the options: default, buttonlabel, searchbuttonlabel, and placeholder if they contain a "-{". The old behaviour was to handle the insides of -{ glossary rules here }- and convert text if there was a glossary rule both prior to the beginning of the attribute and prior to the end of the attribute (So default=foo-{}-bar-{}-baz only bar would be converted). I believe that just looking for -{ is probably close enough. It also opens the question of if these options should always be language converted, but I'll leave that for someone else to decide. Bug: T180485 Change-Id: I3aa10890950afce445075e895baf6b10327bc222
2017-11-21 04:01:57 +00:00
!! end
!! test
InputBox langconvert
!! options
Rename language codes sr-ec and sr-el to sr-Cyrl and sr-Latn in tests sr-ec and sr-el are not conform to BCP 47. BCP 47 explicit mentions sr-Latn and sr-Cyrl as examples. MediaWiki already supports both the old language codes 'sr-ec' and 'sr-el' and the new language codes 'sr-Cyrl' and 'sr-Latn' as language codes for variants. Bug: T117845 Change-Id: I59fd307664769efb8a6e4c47a866c3b1dd17ed5d
2019-07-06 19:29:07 +00:00
language=sr variant=sr-Latn
Have inputbox langconvert certain attributes This approximates the behaviour prior to core change for T119158. It will language convert the options: default, buttonlabel, searchbuttonlabel, and placeholder if they contain a "-{". The old behaviour was to handle the insides of -{ glossary rules here }- and convert text if there was a glossary rule both prior to the beginning of the attribute and prior to the end of the attribute (So default=foo-{}-bar-{}-baz only bar would be converted). I believe that just looking for -{ is probably close enough. It also opens the question of if these options should always be language converted, but I'll leave that for someone else to decide. Bug: T180485 Change-Id: I3aa10890950afce445075e895baf6b10327bc222
2017-11-21 04:01:57 +00:00
!! wikitext
<inputbox>
type=create
Rename language codes sr-ec and sr-el to sr-Cyrl and sr-Latn in tests sr-ec and sr-el are not conform to BCP 47. BCP 47 explicit mentions sr-Latn and sr-Cyrl as examples. MediaWiki already supports both the old language codes 'sr-ec' and 'sr-el' and the new language codes 'sr-Cyrl' and 'sr-Latn' as language codes for variants. Bug: T117845 Change-Id: I59fd307664769efb8a6e4c47a866c3b1dd17ed5d
2019-07-06 19:29:07 +00:00
default=-{sr-Latn: Some latin; sr-Cyrl: Not latin }-
placeholder=-{sr-Latn: Latn; sr-Cyrl: Cyrl}-
Have inputbox langconvert certain attributes This approximates the behaviour prior to core change for T119158. It will language convert the options: default, buttonlabel, searchbuttonlabel, and placeholder if they contain a "-{". The old behaviour was to handle the insides of -{ glossary rules here }- and convert text if there was a glossary rule both prior to the beginning of the attribute and prior to the end of the attribute (So default=foo-{}-bar-{}-baz only bar would be converted). I believe that just looking for -{ is probably close enough. It also opens the question of if these options should always be language converted, but I'll leave that for someone else to decide. Bug: T180485 Change-Id: I3aa10890950afce445075e895baf6b10327bc222
2017-11-21 04:01:57 +00:00
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Repair a broken parser test Before Ia72c960b2c7914342eb4d5e3e63f2d6af14719ad the parser test framework wasn't setting the user language correctly when a variant was requested, which meant that the UX text was being selected from the base language, not the user's preferred variant. Depends-On: I0c9c9fec920f7cb028d935e552a8f11475a23ba7 Change-Id: I7ab40a1d9adc6478c2fe99f44c8f51cbe4ac23a0
2023-01-26 19:26:58 +00:00
<div class="mw-inputbox-centered" style=""><form name="createbox" class="createbox" action="/index.php" method="get"><input type="hidden" value="edit" name="action" /><input name="title" class="mw-inputbox-input mw-ui-input mw-ui-input-inline mw-inputbox-createbox" value="Some latin" placeholder="Latn" required="" size="50" dir="ltr" /><br /><input type="submit" name="create" class="mw-ui-button mw-ui-progressive" value="Napravi stranicu" /></form></div>
Have inputbox langconvert certain attributes This approximates the behaviour prior to core change for T119158. It will language convert the options: default, buttonlabel, searchbuttonlabel, and placeholder if they contain a "-{". The old behaviour was to handle the insides of -{ glossary rules here }- and convert text if there was a glossary rule both prior to the beginning of the attribute and prior to the end of the attribute (So default=foo-{}-bar-{}-baz only bar would be converted). I believe that just looking for -{ is probably close enough. It also opens the question of if these options should always be language converted, but I'll leave that for someone else to decide. Bug: T180485 Change-Id: I3aa10890950afce445075e895baf6b10327bc222
2017-11-21 04:01:57 +00:00
!! end
Provide an `aria-label` attribute option to the input textbox Provide an option to supply the aria-label attribute to the inputbox to allow generated markup be accessible to screen readers <inputbox> type=search width=120 buttonlabel=Search arialabel=Search this wiki </inputbox> Bug: T242354 Change-Id: I40c62bc9889a4912b43244ec65e628ec8bc8533f
2020-01-22 22:58:00 +00:00
!! test
InputBox type=search with aria label
!! wikitext
<inputbox>
type=search
arialabel=Search this wiki
</inputbox>
Get rid of +tidy references from parser tests Bug: T198214 Change-Id: I0dbe2b47e052bf5a42604431d8f04794d3c461e0
2021-09-30 18:46:38 +00:00
!! html
Use native <input required> instead of JS-based disabled toggling Remove the JavaScript module and its logic to toggle the disabled state on the submit button. Instead, let the browser handle this natively by setting the `required` attribute, which naturally prevents early submissions. Retain the current styling for 99% of cases by using the :required:invalid selector to target the submit button to make it appear disabled. This slight duplication of styles is needed because, despite the form effectively being disabled natively, the core mediawiki-ui styles only account for :disabled on the button directly and not e.g. inherited via form:invalid. It is also unclear whether we would want that, since there is some value to be had from having the form give a consistent look with a progressive button that can be submitted even at the wrong time to yield an assistive message to the required field, so hence handling this locally for now instead of with a generalised approach. In order to use the required true/false idiom, I have switched the generating of the HTML string from the old Xml::element method to Html::element. This means there is no need to store it in an array first and conditionally set it since true/false will result in absence or required="" as needed. As side-effect from this, redundant attributes like value="" and type="text" are ommitted from the output, just as MediaWiki core does more generally. Bug: T283303 Change-Id: I2c75e09dd3f89fa11fca311b4e1f8133946b01b1
2021-05-21 02:03:06 +00:00
<div class="mw-inputbox-centered" style=""><form name="searchbox" class="searchbox" action="/wiki/Special:Search"><input class="mw-inputbox-input mw-searchInput searchboxInput mw-ui-input mw-ui-input-inline" name="search" placeholder="" size="50" dir="ltr" aria-label="Search this wiki" /><br /><input type="submit" name="go" class="mw-ui-button" value="Try exact match" />&#160;<input type="submit" name="fulltext" class="mw-ui-button" value="Search full text" /></form></div>
Add newline at end of parser tests file The new parser tests file parser seems to require it. Change-Id: I8ab4a8c59ed1b6837dba428f96a8ba0084b7fb68
2020-08-04 18:23:54 +00:00
!! end
Reference in a new issue Copy permalink