If you use the existing "CSS class" UI for a display, the class is applied to the entire display (as expected). However, when you're using this for skinr-esque reasons, it means that e.g. your pager also inherits the style you're trying to apply to your results.

For the list style plugin, I just wanted to be able to add a class directly to the <ul> or <ol> itself, so that my style only infects my results, not the other stuff on the display.

I've got a slightly ugly patch for this that I'll upload in a second. It's currently against DRUPAL-6--2. I'm guessing this is either going to be "won't fix" or it'll be moved to another branch. Maybe there's a cleaner way to do this in DRUPAL-6--3 (I haven't looked closely yet).

CommentFileSizeAuthor
#1 918782-1.views-list-css-class.patch2.71 KBdww
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dww’s picture

dww
we/he/they
CreditAttribution: dww commented
Status: Active » Needs review
FileSize
918782-1.views-list-css-class.patch2.71 KB

/me hangs head in shame...

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented

I'm wondering why this is specific to style "list"

dww’s picture

dww
we/he/they
CreditAttribution: dww commented
Status: Needs review » Closed (won't fix)

B/c that's what I needed it for. ;)

I briefly discussed this with Earl in IRC. Basically, his line is for D6--2 I should just use semantic views. For D6--3 and D7--3, he wants to merge in the semantic views functionality via #740686: Integrate semantic views.

Hence, won't fix...

Cheers,
-Derek