That's very strange. I don't know of any limits and nobody has reported the same issue to me, for what it's worth. Send me an email at support@sideviewapps.com and we'll get to the bottom of it.
Does it appear to cut off at a certain number of characters? (if so how many?)
Or rather does the pulldown seem to not want to expand past a certain width?
My instinct is to first test the search itself, that maybe at the field extraction level or the search-language level, somehow the full value isn't being passed along.
UPDATE: We discovered the problem after some further investigation. On Internet Explorer, when a dynamic pulldown, whose 'width' param is not set, contains enough options so that IE gives the Pulldown layer a scrollbar, the automatic width that is determined for the <select> node does not adequately account for the extra width of the scrollbar. Here I make it sound like it's IE's fault and it kind of is. But it's equally the fault of the Pulldown module. The fix is very simple and will be gone in the next version of Sideview Utils (1.2.6).
Hotfix was sent to jtosborne79 in the meantime.
UPDATE: I forgot to mention that this same fix was released in the very next version of Sideview Utils, which is now comparatively ancient so this problem has been fixed for months.
