Anthology of Ideas

I accidentally posted on the blog comments, please go ahead and remove that entry if you want.Sorry for the duplication!

I think I’m encountering a bug that is driving me crazy. I’m using inline comments with hidden on the default of this page (it happens to be an archive page). I can get my “Show Comments” text to show normally and I can format them in the CSS by using the .comments_link class. After I’ve followed the show comments link, they pop up correctly, but the new text that shows up using the .awpcomments_link_hide class is only correct if I don’t do anything weird in the Show comments text. For example if I try to load a <span>...</span> around my show comments text when I enter it into admin, the Hide Comments text don’t show with the formatting for the .awpcomments_link_hide class, the Show Comments text still does. The same thing happens if I add some html like one or multiple <br /> tags to the Show Comments text when I enter it into admin. If I just add plain text, the Hide Comments that I entered into admin display correctly with the formatting of .awpcomments_link_hide class. Furthermore, after I’ve gone through the Show Comments followed by Hide Comments, the resulting Show Comments text now uses the .awpcomments_link class instead of the .comments_link class that it used the first time. I am assuming this is by design but in case it is a bug, I thought I’d bring it up. As long as I know about it, I can code my CSS correctly, so I don’t care. The other problem, though, is a big issue for me because the wrong Hide text is coming up when I show the comments. I need the html in the code because my .comments_link / .awpcomments_link classes have a background image that is used to indicate the Show Comments instead of the text. I need the html to push the text below or above the background image. As a workaround, I might need to leave a top margin for the text in my background image to contain the text, but I’d rather try to understand better why the code is doing this since it doesn’t seem like the right behavior.

Thanks, Karen

Thanks for responding, Aaron. I ended up working around the limitation in a similar way, but now I’m encountering a class problem with the comment form. Will post that in a separate entry. Thanks for your support, I am LOVING the way this is coming together for me! Very sharp looking and user friendly!

Karen