-
1. Re: Controlling column widths of rich:autocomplete?
rlmarsh85 Sep 13, 2011 8:35 PM (in response to sbalmos1)Scott,
I am facing the same exact problem. I will post and let you know if I find an answer.
-
2. Re: Controlling column widths of rich:autocomplete?
rlmarsh85 Sep 13, 2011 8:50 PM (in response to rlmarsh85)1 of 1 people found this helpfulThis solution came quicker than I anticipated. Looks like we're not the only two having a hard time. Read this thread:
-
3. Re: Controlling column widths of rich:autocomplete?
sbalmos1 Sep 14, 2011 9:45 AM (in response to rlmarsh85)Well... Honestly it looks like another oversight / hack job. But it works. I added the rf-au-lst-scrl override, which works fine. But ultimately, the width attribute of the contained <rich:column> elements is still being ignored. I don't care too much, since everything seems to be rendering close to how it used to. But I think it's still an oversight.
Also interesting to note, in the rendered table for the popup list, I had to define td.rf-au-inp { padding-right: 5px; } to properly mimic the slight cell spacing in the old 3.3 suggestionbox. Otherwise, the cells are scrunched up right next to each other - visually annoying. Looking at the generated HTML, each cell's td element references a rf-au-inp class that doesn't exist. There's input.rf-au-inp, for the text input box itself. But no td.rf-au-inp or such. Additional FYI.
-
4. Re: Controlling column widths of rich:autocomplete?
bcn Dec 9, 2011 2:24 PM (in response to sbalmos1)Hi,
I think one should file a bug / enhancement request.
Because, even with this workaround you cannot change the width of one autocomplete on a page without changing others on the same page, can you?
Another doubt, if the default width is 100%, why does it not adapt to the item widths automatically?
Thanks