Introduce 'copy' or 'strings' or 'verbiage' as a Trac focus

[garrett-eclipse]

Hello,

Along with #4609 I'm opening this due to the discussion on slack;
@clorith - "I view strings as a focus within each component, not as a component of them selves"
Reference - ​https://wordpress.slack.com/archives/C02RQBWTW/p1563396887461100

I tend to agree it shouldn't be a component but more a focus. Raising for discussion.

Thanks

[garrett-eclipse]

Patch to introduce a ui-copy focus

[garrett-eclipse]

I've supplied an initial patch to introduce a new ui-copy focus in 4610.diff.;
'ui-copy' : 'Copy focus for the user interface.',

I'm unsure if there needs to be anything else edited for the new focus, with new keywords I had to update this page;
​https://make.wordpress.org/core/handbook/contribute/trac/keywords/
*Should there be a documented page outlining the Focuses?

Or if the reports like this are automatically generated;
​https://core.trac.wordpress.org/focus/accessibility

[dd32]

In 9076:

Trac: Add 'ui-copy' as a focus.

Props garrett-eclipse.
Fixes #4610.

[dd32]

In 9077:

Trac: Bump scripts version after [9076].

See #4610.

[dd32]

I think that's all that actually needs doing here, let's see what happens shall we?

[garrett-eclipse]

Thanks @dd32 much appreciated

[SergeyBiryukov]

In 9353:

Trac: Notifications: Add css and ui-copy focuses to Trac Notifications settings page.

Props noisysocks.
See #4844, #4610.