Hi

I've think I've found a bug.

I've created custom user fields, and I want them to be searchable. So I set them up, and they display and are searchable exactly as they should be.

However, the tooltip that shows up in the text box (or select dropdown, whatever type it is) draws the information exactly from the database, which includes html which JCE automatically added to the textarea field I used to give the custom field a description (i.e. the paragraph tags).

It looks odd, and while the work-around is simple (turn off the WYSIWYG editor when editing those fields) it would be nice if the tool-tip didn't display any html by using strip_tags on the output before adding it to the title attribute. I had a search but couldn't find where this was located in the files sorry, so I'm not sure whether it's a problem with the default template or with the actual core CB Code or not.

Hi Krileon

I completely agree, attributes do not support HTML. Which is why this is a bug, because Community Builder is telling me that I can put either text OR html in.

I've attached an image to demonstrate this.



The arrow is pointing to the field that is used as both the description of the field, the title and the alt attribute. You can see it clearly says "Text or HTML". Works great for editing a user, as you have that nice JS mouse overs in the title attribute. And all the HTML in the alt attribute. On other pages, the HTML has the possibility of being added to both the alt and title attributes.

Obviously with all the legacy support that CB provides, I'm not saying this is an easy fix, nor even an essential one. If the CB team wants a hand with this area I'm happy to help, PM me if you'd like to take me up on the offer.

--- Ben

Post edited by: Muuurgh, at: 2010/07/06 18:38

Hi

I think you've misunderstood me. I do not want to put html in the title and alt attributes.

The bug, as I see it, is that CB puts HTML into those attributes. Given that the code already exists to strip the tags from the text, I believe it is a bug that this behaviour is not experienced when the alt and title attributes are filled in.

But hey, it's not my code and no skin off my nose Since I'm not worried about the accessibility and I've disabled the ability for users to create accounts I can come up with workarounds for my site.

Thanks for your time