AutoComplete custom content without columns

[bjoern]

Hello,

I'm new to this forum.

I'm looking for a solution for custom content in an autocomplete selection.

The user searches for something like: "123"
and gets suggestions with some additional information in brackets:
1234 (some infos)
1238 (some other infos)
1239 (some additional infos)

If the user chooses "1234 (some infos)" then in the input field is only written "1234". Because "1234" ist the key.

I found a solution by using custom content with one column.
But using custom content with columns changes the look of the suggestions dropdown.
Is there a better solution?

[bsanders1979]

Are you using the itemLabel attribute?

[bjoern]

thanks for your input.

Yes, I use itemLabel. But when I use itemLabel without a custom content column is it in the end the same in the input-box and in the suggestions-list.

At the moment I use one custom content column:

Code: Select all

<p:autoComplete ... var="item" itemLabel="#{item.searchText}" itemValue="#{item}"  converter="..." emptyMessage="...">
    <p:column>
        <h:outputText value="#{item.searchText}" /> (<h:outputText value="#{item.additionalText}" />)
    </p:column>
</p:autoComplete>

But I don't want any table.
What I need is close to the itemtip functionality. But I don't want an extra itemtip pop-up. I want the information in the suggestions-list.

[kukeltje]

But using custom content with columns changes the look of the suggestions dropdown.
Is there a better solution?

Restyling the suggestions dropdown?

[bjoern]

Yes, restyling the suggestions dropdown is a logic step.

But I decided to override the AutoCompleteRenderer. The advantage of overriding the renderer is, that the autocomplete character highlighting still works.

Would be nice if PF would add a suggestion facet... for layouting the suggestions.

So this thread is solved.

[kukeltje]

why would hightlighting not work anymore when styling the dropdown? Care to elaborate?

[bsanders1979]

I've run into the same issue. I dicovered that &'s would be rendered as "&". So, after reviewing the source and finding the cause of the issue (something about CDATA in the ResponseWriter, IIRC), I added <p:column /> as a child which killed the bolding.