#35776 closed defect (bug) (fixed)
Installation pages do not have forms.css enqueued
Reported by: | iseulde | Owned by: | SergeyBiryukov |
---|---|---|---|
Milestone: | 5.3 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Upgrade/Install | Keywords: | good-first-bug has-patch |
Focuses: | ui | Cc: |
Description
Attachments (11)
Change History (27)
#2
@
9 years ago
- Keywords dev-feedback added
Of course the formatting issue differ depending on the order forms is enqueued, Is there some specific css in forms.css that is needed that can be coped to install.css ?
#4
@
8 years ago
@iseulde Can you please clarify what exact styles are missing from forms.css.
How should it look like?
#5
@
8 years ago
- Keywords 2nd-opinion dev-feedback removed
At first glance it looks like the input styles are missing. You can see the default browser focus style and checkbox style in the first screenshot. If the password input doesn't look good, then it'd need to be adjusted.
#6
@
8 years ago
Attached is a patch which mirrors relevant styles from "wp-admin/css/forms.css" into "wp-admin/css/install.css".
Find also before and after screenshots attached, the changes are mainly about the checkbox at the bottom of the form.
#8
@
8 years ago
- Owner set to bassgang
- Status changed from new to assigned
Assigning to mark the good-first-bug as "claimed".
See 35776.patch
#9
@
7 years ago
See 35776.diff for a simpler approach. It imports core forms.css
styles and then adjusts some form controls properties to match the new styles.
This ticket was mentioned in Slack in #core by sergey. View the logs.
5 years ago
#11
@
5 years ago
- Keywords reporter-feedback removed
- Milestone changed from Future Release to 5.3
- Owner changed from bassgang to SergeyBiryukov
- Status changed from assigned to reviewing
#15
in reply to:
↑ 14
@
5 years ago
Replying to JeffPaul:
looks like the prop in r45673 and r45844 should have been to
danmicamediacom
.
Thanks for bringing that up!
Previously, the rule of thumb was to always use the name that Trac shows:
https://wordpress.slack.com/archives/C18723MQ8/p1471699137000226
However, there are indeed some quirks when the username has spaces or is an email address:
https://wordpress.slack.com/archives/C18723MQ8/p1513306349000049
So apparently user_nicename
should be used instead, but it's not currently available for Trac templates.
I'll double check the correct username when updating the Credits API for 5.2.3.
Should it be? When I did enqueue it during the install page formatting got screwed up and i'm not sure I see what the difference is. See the following attachments: