There is only one use case of cond-state classes passed to the client-side, and it can be done more natively. Change-Id: Ib6835bb334bd65c6176f0a5c3881b20265901af9
35 lines
1.1 KiB
PHP
35 lines
1.1 KiB
PHP
<?php
|
|
|
|
/**
|
|
* Allows custom data specific to HTMLFormField to be set for OOUI forms. A matching JS widget
|
|
* (defined in htmlform.Element.js) picks up the extra config when constructed using OO.ui.infuse().
|
|
*
|
|
* Currently only supports passing 'hide-if' and 'disable-if' data.
|
|
* @phan-file-suppress PhanUndeclaredMethod
|
|
*
|
|
* @stable to extend
|
|
*/
|
|
trait HTMLFormElement {
|
|
|
|
protected $condState = null;
|
|
protected $modules = null;
|
|
|
|
public function initializeHTMLFormElement( array $config = [] ) {
|
|
// Properties
|
|
$this->condState = $config['condState'] ?? [];
|
|
$this->modules = $config['modules'] ?? [];
|
|
|
|
// Initialization
|
|
if ( $this->modules ) {
|
|
// JS code must be able to read this before infusing (before OOUI is even loaded),
|
|
// so we put this in a separate attribute (not with the rest of the config).
|
|
// And it's not needed anymore after infusing, so we don't put it in JS config at all.
|
|
$this->setAttributes( [ 'data-mw-modules' => implode( ',', $this->modules ) ] );
|
|
}
|
|
$this->registerConfigCallback( function ( &$config ) {
|
|
if ( $this->condState ) {
|
|
$config['condState'] = $this->condState;
|
|
}
|
|
} );
|
|
}
|
|
}
|