User tests: Successful: Unsuccessful:
Just another take on #11789
Changes only to UI elements. Removal of background gradients. More uniform styling between template.css and chosen.css
Apply the patch and browse administration.
None
Status | New | ⇒ | Pending |
Labels |
Added:
?
|
Category | ⇒ | Templates (admin) Administration |
The grey buttons looks disabled to me. I dont like it. However I doubt design can be done by collaborative opinions though.
@dgt41 I have applied the changes here but would it be better to close this PR and create a new one? I'm guessing this is something to do with the branch conflict?
@PhilETaylor Fair point on the buttons looking disabled. I bumped up the contrast on the button borders making them hopefully stand out a little more (header screenshot updated).
I like this too actually.
@ciar4n - If it's easier for you to create a new PR, go for it. I'd suggest creating a new branch when based on "staging", on your fork before making then changes though. Will make your life much easier if you want to submit another PR before this is merged ;)
I have tested this item
I have tested this item
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-08-29 07:20:30 |
Closed_By | ⇒ | ciar4n |
@ciar4n I like it!
But the usage of custom.css is wrong. Custom.css is supposed to be used from users to further customise the template. With the current approach you are eliminating that option.
Either make a PR with the changes to #11789 or create a new PR based on #11789 with your changes and let's close #11789.