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

loop-nav: should .previous be .prev? #5

Open
lkraav opened this issue Sep 26, 2013 · 1 comment
Open

loop-nav: should .previous be .prev? #5

lkraav opened this issue Sep 26, 2013 · 1 comment

Comments

@lkraav
Copy link

lkraav commented Sep 26, 2013

This is to eliminate the difference with paginate_links()

http://core.trac.wordpress.org/browser/tags/3.6.1/wp-includes/general-template.php#L1994

AFAiCS theme's navigation class should follow core naming, so we don't have to chase this in styling. Am I missing anything significant with this reasoning?

@justintadlock
Copy link
Owner

Core naming doesn't really matter in this instance. .previous is more consistent with my other themes. Plus, core isn't even consistent with this naming and doesn't always use the class:
http://core.trac.wordpress.org/browser/tags/3.6.1/wp-includes/link-template.php#L1612

I've got some Hybrid Core filters I plan on adding for cleaning some of this stuff up though.

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

No branches or pull requests

2 participants