Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Site Settings: Remove Disabled Input for WordPress Version #32457

Merged

Conversation

Aurorum
Copy link
Contributor

@Aurorum Aurorum commented Apr 21, 2019

Changes proposed in this Pull Request

  • Removes the disabled input in Site Settings for the WordPress version

Some of the elements to mention should obviously not be a text input (why would the version number be a text input?)

Testing instructions

On a Jetpack connected site, visit /settings/general and check the WordPress version.

Current:

Screenshot 2019-04-21 at 14 03 43

Proposed:

Screenshot 2019-04-21 at 14 03 21

cc @simison, @drw158

See #31207 and #26982 for some context on this

@arunsathiya arunsathiya requested review from akirk and a team April 23, 2019 17:27
@arunsathiya arunsathiya added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. [Status] Needs Design Review Add this when you'd like to get a review / feedback from the Design team on your PR Jetpack OSS Citizen [Feature] Site Settings All other general site settings. labels Apr 23, 2019
@flootr flootr requested a review from simison May 27, 2019 13:34
/>
<FormLabel
className="site-settings__wordpress-version"
htmlFor="wpversion"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this be changed to a different component? ie, not FormLabel – there is no input with ID wpversion for this to label anymore (and if somehow there is, in some other component on the page, it shouldn't attach to this label)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Updated the PR to just use a <strong> tag, would that be okay?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better now! :-) There's also FormFieldset component which isn't semantically correct now.

Copy link
Contributor Author

@Aurorum Aurorum May 29, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated it to wrap with Fragment. :)

@akirk akirk removed their request for review May 29, 2019 10:09
@lancewillett lancewillett added [Status] Needs Rebase and removed [Status] Needs Design Review Add this when you'd like to get a review / feedback from the Design team on your PR labels May 5, 2020
@lancewillett lancewillett self-requested a review May 5, 2020 19:24
Copy link
Contributor

@lancewillett lancewillett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The UI changes look good to me, as well as the code changes.

Before:
Screen Shot 2020-05-05 at 12 16 37

After:
Screen Shot 2020-05-05 at 12 23 48

Change requested — please rebase, so I can use your branch to commit. 😄

@lancewillett lancewillett removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label May 5, 2020
@Aurorum
Copy link
Contributor Author

Aurorum commented May 5, 2020

Done, thank you! :)

@lancewillett lancewillett self-requested a review May 5, 2020 22:17
@lancewillett lancewillett self-assigned this May 5, 2020
@lancewillett lancewillett merged commit f5edbda into Automattic:master May 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants