Problem/Motivation
We should reduce the amount of "special patterns" that only applies to Views.
Proposed resolution
Improve specificity on a line of CSS on views dropdown button.
before patch List Views
The edit button font size was 10px, because a css rule from views-ui was affecting this button.

before patch Views UI
The add button font size was 10px, this is correct, needs to stay after patch.

after patch List Views
css rule no longer applies to the "edit" button on this page because css rule was made more specific.

after patch Views UI
css rule is now more specific to apply to the buttons on this page only.

Remaining tasks
- Patch created - done
- Community tested - done
- Beta evaluation - done
- Screenshots - done
User interface changes
Dropbutton font size increase on the views listing page.
API changes
None
Beta phase evaluation
| Issue category | Task because issue cleans up CSS code |
|---|---|
| Issue priority | Normal because CSS change is isolated to specific Views user interface. |
| Unfrozen changes | Unfrozen because it only changes CSS |
Comments
Comment #1
lewisnymanComment #2
shellshocked59 commentedI changed the CSS from
.js .dropbutton-wrapper .dropbutton .dropbutton-action > * {to
.js #view-edit-form .dropbutton-wrapper .dropbutton .dropbutton-action > * {Comment #3
Bojhan commentedLooks good, tested it and only effected what we needed.
Comment #4
lewisnymanSorry, can we use a class instead of an ID?
Comment #5
shellshocked59 commentedSure, here it is using .views-edit-view instead
Comment #6
shellshocked59 commentedComment #7
AllieRays commentedpatch working as expected. =)
Comment #8
AllieRays commentedComment #9
AllieRays commentedComment #10
davidneedhamLook good to me.
Comment #11
mradcliffeIt would really be nice to have some screenshots, and we need to do a beta evaluation for this normal task.
Comment #12
bpleduc commentedI have tested this and found that it applied in the Views UI. Not sure this was the desired location as it was stated above "(not Views UI itself)".
Screen shot attached.
Comment #13
bpleduc commentedComment #14
alimac commentedbpleduc, is that a before or after screenshot? Can you add the before/after screenshot?
Comment #15
AllieRays commentedComment #16
mradcliffeThat's great, @devuable. Could you submit as 2 different screenshots? I found it a bit confusing as one image.
Comment #17
AllieRays commentedComment #18
AllieRays commentedComment #19
bpleduc commentedI will be reviewing before and after screen shots and cleaning up attached files.
Comment #20
bpleduc commentedComment #21
jdcosta commentedAdded beta evaluation
Comment #22
mradcliffe@jdcosta, I think this issue is more about user experience than usability - re: beta evaluation
Comment #23
jdcosta commentedIt is user usability experience
Comment #24
alimac commentedComment #25
alimac commentedComment #26
lewisnymanThanks for adding the screenshots. This looks good.
Comment #27
shellshocked59 commentedComment #28
shellshocked59 commentedComment #29
shellshocked59 commentedComment #30
shellshocked59 commentedComment #31
AllieRays commentedComment #32
AllieRays commentedComment #33
AllieRays commentedComment #34
AllieRays commentedComment #35
AllieRays commentedComment #36
mradcliffeImproved beta evaluation.
Comment #37
mradcliffeI changed the priority row of the beta evaluation because it did not accurately reflect the Priority levels of issues page based on the first part of the Normal section instead of just looking at the Normal Tasks sub-section.
Comment #38
yesct commentedComment #39
xjmComment #40
yesct commentedopps. one of the screenshots was the wrong file name. fixed it to show the edit button before screenshot.
Comment #41
alexpottCommitted e9a25fc and pushed to 8.0.x. Thanks!
Thanks for adding the beta evaluation.