Just to be clear, when I said the BlackBerry Browser "allows me to type" a certain number of characters in an input text field, I meant that that was the number of characters visible on screen at any given time. This is unrelated to "maxColumns," which works fine.
Take care, Joey On 8/15/06, Joseph Rozier <[EMAIL PROTECTED]> wrote:
Hello, Another general question I'd like to get other people's thoughts on regarding how much we should handle in our renderers vs. how much we should expect the developer to handle with regards to browser-specific functionality/workarounds. The BlackBerry Browser does not honor the "size" attribute on an input type=text correctly. When it is specified (with default styles), it allows for significantly more space than expected (for example, if size="1", it allows me to type 4-6 capital M's, at size="10", it allows 16-18 capital M's. I've made a local change that makes this adjustment for the user automatically. If the user specifies the columns attribute on an af:inputText, I've written code that divides it by 1.7, which gets to approximately the desired behavior for most values. Should this go in the renderers, though? Or should the developer wanting his/her device to work on a BlackBerry Browser have to use an EL in the columns attribute each time, checking for the BlackBerry? If we DO code it in the renderers, though, then the user might get frustrated that we are adjusting the columns with no obvious way of overriding it. Where should the balance get struck in this case and in general? Thanks, Joey
