theme_pager : id="pager" to class="pager"

Seems correct to me: as there can be multiple pagers on one page, one would have multiple divs with the same id, which is not allowed. So making it a class would solve that.

Of course the .css file also needs to be altered to use .pager instead of #pager.

Patch attached.

The argumentation makes sense.
I grepped but couldn't find other occurrences of #pager or id="pager" other than the ones in the patch.

I don't know how this would affect custom made themes, though. I guess very few, if any, would theme #pager, so I think it is safe.

I set as RTBC, but I don't know the exact policy on such changes.

How can there be multiple pagers on the same page? How do you make the URLs of each pager different so the pager code knows what pager is clicked? AFAIK, we don't support multiple pagers on the same page, but I might be wrong ... please clarify how you use this so we can evaluate the usefulness/correctness of this patch.

Ah, makes sense.

Committed to CVS HEAD.

Attached patch for 4.7.4.

I am not sure I should apply this to 4.7. Wouldn't this break any custom CSS? To have two pagers on one page is probably rarer than theming the single pager that is usually there.

Agreed. Any existing theme which had styled the pager would cease to work with this patch. Kind of a mean thing to do in a stable version of Drupal.

I agree also, found at least 30 themes using #pager. Well, set this to fixed then? Btw, documentation needed for 4.7->5.0 themes in regards to the original patch that Dries committed.

done