Add last CSS class for UL and OL Lists

[viriava]

In Ul and OL lists add CSS class like: class="last" for last list's item.
Example:

<ul>

<li>item 01</li>

<li>item 02</li>

<li>item 03</li>

<li class="last">item 04</li>

</ul>

It will be helpful for theme styling.

[viriava]

Also, will be good add class="first"

<ul>

<li class="first">item 01</li>

<li>item 02</li>

<li>item 03</li>

<li class="last">item 04</li>

</ul>

[alexdunae]

One of my plugins does this: Classy wp_list_pages: ​http://wordpress.org/extend/plugins/classy-wp-list-pages/

[Nicholas91]

I disagree, because I'm not sure how many people would find styling the first and last item of an ol/ul useful. They should use the plugin above instead...

[Denis-de-Bernardy]

isn't this done in the walker classes already?

[wojtek.szkutnik]

:first-child and :last-child are compatible with all modern browsers, isn't it sufficient?

[nacin]

We've discussed this elsewhere and using CSS selectors has generally prevailed previously. As we continue to hold that argument of HTML versus CSS, the bad browsers will die off and the current browsers will only get better, so no use leaving this open longer.

[hm2k]

As far as I am aware, Wordpress supports _all_ browsers, including older ones (unlike ​Yahoo's Graded Browser support)

Using :first-child shouldn't be a problem as it was part of the 1998 CSS2 specification.

However, :last-child was introduced in the 2009 "Selectors Level 3" specification.

According to ​litmus tests, IE6, IE7 and IE8 do not support :last-child.

According to ​Microsoft IE6 still over 9% world wide market share, while ​others report around 40% market share for Internet Explorer overall.

While I agree, and hope that bad browsers will "die off", surely we can't ignore _current_ browsers.

[SergeyBiryukov]

Since WordPress 3.2, ​IE6 is deprecated, and IE7 is going to be deprecated in 3.4.

As a workaround, it's probably possible to use ​jQuery or ​some other workaround.

[hm2k]

Right now, ​IE8 has the biggest market share at almost 20% or are we ignoring that?

Microsoft will ​continue to support IE8 until it stops supporting ​Windows Server 2008 in 2013, possibly 2018.

When a native CSS solution is so simply to implement in the core by adding a class to the markup, javascript workarounds aren't the answer.

[SergeyBiryukov]

Version number is used to track when the issue was initially reported.

[hm2k]

More of an enhancement than a feature.

[dd32]

In the last 3 years the psuedo selector support has increased dramatically, and whilst we do "Support" old browsers, things such as list styling should be seen as graceful-degradation.

I'm reclosing as wontfix, as it's of little benefit to those using modern browsers - and the JavaScript tools to add missing features to old browsers are becoming more commonly needed for HTML5/etc support anyway.