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

No need to style sr-only elements #1634

Merged
merged 1 commit into from
Apr 26, 2017
Merged

No need to style sr-only elements #1634

merged 1 commit into from
Apr 26, 2017

Conversation

jcoyne
Copy link
Member

@jcoyne jcoyne commented Feb 28, 2017

No description provided.

@coveralls
Copy link

coveralls commented Feb 28, 2017

Coverage Status

Coverage remained the same at 94.416% when pulling fe044fe on fix_style into 4e5af82 on master.

@@ -2,7 +2,7 @@
@extend .mb-2;
}

span.constraints-label {
.constraints-label {
Copy link
Member

Choose a reason for hiding this comment

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

Is this only used to style this .sr-only element?

<span class="constraints-label sr-only"><%= t('blacklight.search.filters.title') %></span>

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, as far as I can tell.

Copy link
Member

Choose a reason for hiding this comment

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

Can we just remove the style entirely? No reason to make some sr-only text bold, is there?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, that's best. We didn't have sr-only in the 6 branch, so I didn't notice.

@atz
Copy link
Member

atz commented Apr 21, 2017

@jcoyne, @cbeer So we can close this or rework it?

@jcoyne jcoyne changed the title No need for an element selector. Class works fine. No need to style sr-only elements Apr 26, 2017
@coveralls
Copy link

Coverage Status

Coverage remained the same at 94.377% when pulling efab7d4 on fix_style into 207cce9 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 94.377% when pulling efab7d4 on fix_style into 207cce9 on master.

@cbeer cbeer merged commit 5e329f6 into master Apr 26, 2017
@cbeer cbeer deleted the fix_style branch April 26, 2017 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants