Thread:Mathmagician/@comment-93604-20120509230753/@comment-4674838-20120512203855

So, apparently the buttons are getting added to the correct location in the DOM in Monobook. The problem is the CSS. Monobook interprets "position: absolute;" differently -- it puts all of the buttons at the very top of the screen, above the article title. However, the previous version of the code that I gave you had the buttons as "position: relative;" and they were displaying correctly in Monobook. But (I think) relative positioning won't work for Oasis because it will just put the buttons inside of the comment area -- not slightly above it like your code does. So, it looks like we need skin-specific styling. I'm not a Monobook expert, but I'll see if I can throw together some CSS that'll work and then we'll need to use different styling depending on if skin==oasis or skin==monobook.

How do you do this? var htmlString = ' Text '; var wrapped = $(htmlString);

// need to "unwrap" to get the html string again // but this doesn't quite work... var backToHtmlString = wrapped.toString;

console.log(htmlString); console.log(wrapped); console.log(backToHtmlString);


 * "Don't think of .trigger('toggle') as a function call! Think of it as actual event handler."

But in your code above, .trigger('toggle') is inside of the click handler. So isn't the real handler .click? Also, I wasn't aware the toggle itself was a jQuery method. Now that I read it, it said that toggle itself has an internal click handler. So basically you've got click inside of toggle inside of click? This is confusing. What's with this nesting handlers business?