Search results

CSS styling suggestions

Status: Open.

#42 In wpaccessibility/settings-api-enhanced;

· hedgefield opened on Jun 16, 2017

Figure out proper way to handle radio groups with a custom text element

Semantic Markup

Status: Open.

#40 In wpaccessibility/settings-api-enhanced;

· felixarntz opened on Jun 11, 2017

Consider removing the .settings-fields wrap element

Semantic Markup

Status: Open.

#37 In wpaccessibility/settings-api-enhanced;

· felixarntz opened on Jun 8, 2017

Reconsider how render_settings_field_multibox() works

Status: Open.

#36 In wpaccessibility/settings-api-enhanced;

· afercia opened on Jun 5, 2017

Consider using sane defaults for fields based on REST API registered settings

later

php-infrastructure

Status: Open.

#24 In wpaccessibility/settings-api-enhanced;

· felixarntz opened on May 29, 2017

Use the Settings API for the Discussion page

task

Status: Open.

#19 In wpaccessibility/settings-api-enhanced;

· felixarntz opened on May 29, 2017

Consider to make add_settings_section() optionally output a fieldset

php-infrastructure

Semantic Markup

Status: Open.

#14 In wpaccessibility/settings-api-enhanced;

· afercia opened on Apr 24, 2017

Consider to abstract the description output

later

php-infrastructure

Status: Open.

#13 In wpaccessibility/settings-api-enhanced;

· afercia opened on Apr 24, 2017

Consider to abstract checking for is_callable / is_string

later

php-infrastructure

Status: Open.

#12 In wpaccessibility/settings-api-enhanced;

· afercia opened on Apr 24, 2017

CSS naming conventions for JS targeting

Status: Open.

#11 In wpaccessibility/settings-api-enhanced;

· afercia opened on Apr 24, 2017

What types of fields the Settings API should support? (see type=number)

Status: Open.

#10 In wpaccessibility/settings-api-enhanced;

· afercia opened on Apr 11, 2017

CSS best practices

Status: Open.

#9 In wpaccessibility/settings-api-enhanced;

· afercia opened on Apr 11, 2017