RE: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
Hello Carsten, I guess the content style is causing the issue. I am not sure if you really require the content style to be set for a read-only field. So, you have three options - remove the content style for read-only fields, or increase the width (problem can still exist if the value is of greater length), or use tr:outputText when you want it to be read-only(I guess this is the best). Thanks. ~Sandeep -Original Message- From: Carsten Pieper [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 1:59 PM To: users@myfaces.apache.org Subject: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour Hello everyone, is this a bug or am I missing something? The situation is as follows: tr:inputText label=My short inputText value=Hello inputText contentStyle=width: 50px; readOnly=true /tr:inputText The text then exceeds the actual text area as shown in the screenshot (note that the read-only text area background is slightly darker than the rest...). http://www.nabble.com/file/p12049157/inputTextReadOnly.jpg If readOnly isn't set (or false), then everything is as expected as again shown in the screenshot (only 50 px of text are shown, but you can access the rest via mouse/keyboard): http://www.nabble.com/file/p12049157/inputText.jpg Any ideas? Thanks in advance, Carsten -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-an d-limited-width-shows-strange-behaviour-tf4234891.html#a12049157 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
Hi Carsten, what is the rendered HTML-output of both cases for this field? regards, Martin On 8/8/07, Carsten Pieper [EMAIL PROTECTED] wrote: Hello everyone, is this a bug or am I missing something? The situation is as follows: tr:inputText label=My short inputText value=Hello inputText contentStyle=width: 50px; readOnly=true /tr:inputText The text then exceeds the actual text area as shown in the screenshot (note that the read-only text area background is slightly darker than the rest...). http://www.nabble.com/file/p12049157/inputTextReadOnly.jpg If readOnly isn't set (or false), then everything is as expected as again shown in the screenshot (only 50 px of text are shown, but you can access the rest via mouse/keyboard): http://www.nabble.com/file/p12049157/inputText.jpg Any ideas? Thanks in advance, Carsten -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12049157 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
Hi Martin, readOnly=true results in this HTML: td!--Start: org.apache.myfaces.trinidad.Input[_id28]--table id=_id28__xc_ class=af_inputText p_AFReadOnly cellpadding=0 cellspacing=0 border=0 summary=tr td class=af_inputText_label nowrapMy short inputText/td td valign=top nowrap class=AFContentCell!--Start: org.apache.myfaces.trinidad.Input[_id28]--div id=_id28 class=af_inputText_content style=width: 50px;Hello inputText/div/td /tr!--Start: org.apache.myfaces.trinidad.Input[_id28]--tr td/td td class=AFComponentMessageCell!--Start: org.apache.myfaces.trinidad.Input[_id28]--/td /tr/table/td and readOnly=false in this: td!--Start: org.apache.myfaces.trinidad.Input[_id28]--table id=_id28__xc_ class=af_inputText cellpadding=0 cellspacing=0 border=0 summary=tr td class=af_inputText_label nowrap X nbsp;label for=_id28My short inputText/label/td td valign=top nowrap class=AFContentCell!--Start: org.apache.myfaces.trinidad.Input[_id28]--input id=_id28 name=_id28 class=af_inputText_content style=width: 50px; size=30 type=text value=Hello inputText/td /tr!--Start: org.apache.myfaces.trinidad.Input[_id28]--tr td/td td class=AFComponentMessageCell!--Start: org.apache.myfaces.trinidad.Input[_id28]--/td /tr/table/td Thanks, Carsten Martin Marinschek wrote: Hi Carsten, what is the rendered HTML-output of both cases for this field? regards, Martin On 8/8/07, Carsten Pieper [EMAIL PROTECTED] wrote: Hello everyone, is this a bug or am I missing something? The situation is as follows: tr:inputText label=My short inputText value=Hello inputText contentStyle=width: 50px; readOnly=true /tr:inputText The text then exceeds the actual text area as shown in the screenshot (note that the read-only text area background is slightly darker than the rest...). http://www.nabble.com/file/p12049157/inputTextReadOnly.jpg If readOnly isn't set (or false), then everything is as expected as again shown in the screenshot (only 50 px of text are shown, but you can access the rest via mouse/keyboard): http://www.nabble.com/file/p12049157/inputText.jpg Any ideas? Thanks in advance, Carsten -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12049157 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12050583 Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
Hello Sandeep, thanks so far! I guess the content style is causing the issue. I am not sure if you really require the content style to be set for a read-only field. Yes, I think we do: We want to be able to use the same pages for input or read-only just by flipping a switch (readOnly would then of course be connected to a boolean property in the backing bean...). We want those pages to have the same input field width in both cases. Thus, the contentStyle... In my opinion, the behaviour of the input-enabled field (concerning too long texts) would be ideal for the read-only version as well , i.e. showing as much of the text as the defined width allows and making the rest accessible via mouse/keyboard actions. By the way, the outputText doesn't seem to offer this, neither. As far as I am aware, it can only truncate long texts... (well, via tooltip / shortDescription you can at least offer the complete text). Best regards, Carsten sandeep gururaj wrote: Hello Carsten, I guess the content style is causing the issue. I am not sure if you really require the content style to be set for a read-only field. So, you have three options - remove the content style for read-only fields, or increase the width (problem can still exist if the value is of greater length), or use tr:outputText when you want it to be read-only(I guess this is the best). Thanks. ~Sandeep -Original Message- From: Carsten Pieper [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 1:59 PM To: users@myfaces.apache.org Subject: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour Hello everyone, is this a bug or am I missing something? The situation is as follows: tr:inputText label=My short inputText value=Hello inputText contentStyle=width: 50px; readOnly=true /tr:inputText The text then exceeds the actual text area as shown in the screenshot (note that the read-only text area background is slightly darker than the rest...). http://www.nabble.com/file/p12049157/inputTextReadOnly.jpg If readOnly isn't set (or false), then everything is as expected as again shown in the screenshot (only 50 px of text are shown, but you can access the rest via mouse/keyboard): http://www.nabble.com/file/p12049157/inputText.jpg Any ideas? Thanks in advance, Carsten -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-an d-limited-width-shows-strange-behaviour-tf4234891.html#a12049157 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12050833 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
Hi Carsten, you'd have to play a bit more with CSS there. What you'd really want is something like clipping enabled for the core tag of the readOnly-inputText. http://de.selfhtml.org/css/eigenschaften/positionierung.htm#clip regards, Martin On 8/8/07, Carsten Pieper [EMAIL PROTECTED] wrote: Hello Sandeep, thanks so far! I guess the content style is causing the issue. I am not sure if you really require the content style to be set for a read-only field. Yes, I think we do: We want to be able to use the same pages for input or read-only just by flipping a switch (readOnly would then of course be connected to a boolean property in the backing bean...). We want those pages to have the same input field width in both cases. Thus, the contentStyle... In my opinion, the behaviour of the input-enabled field (concerning too long texts) would be ideal for the read-only version as well , i.e. showing as much of the text as the defined width allows and making the rest accessible via mouse/keyboard actions. By the way, the outputText doesn't seem to offer this, neither. As far as I am aware, it can only truncate long texts... (well, via tooltip / shortDescription you can at least offer the complete text). Best regards, Carsten sandeep gururaj wrote: Hello Carsten, I guess the content style is causing the issue. I am not sure if you really require the content style to be set for a read-only field. So, you have three options - remove the content style for read-only fields, or increase the width (problem can still exist if the value is of greater length), or use tr:outputText when you want it to be read-only(I guess this is the best). Thanks. ~Sandeep -Original Message- From: Carsten Pieper [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 1:59 PM To: users@myfaces.apache.org Subject: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour Hello everyone, is this a bug or am I missing something? The situation is as follows: tr:inputText label=My short inputText value=Hello inputText contentStyle=width: 50px; readOnly=true /tr:inputText The text then exceeds the actual text area as shown in the screenshot (note that the read-only text area background is slightly darker than the rest...). http://www.nabble.com/file/p12049157/inputTextReadOnly.jpg If readOnly isn't set (or false), then everything is as expected as again shown in the screenshot (only 50 px of text are shown, but you can access the rest via mouse/keyboard): http://www.nabble.com/file/p12049157/inputText.jpg Any ideas? Thanks in advance, Carsten -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-an d-limited-width-shows-strange-behaviour-tf4234891.html#a12049157 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12050833 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
Thanks Martin, yes, clipping helps in a way, but things really seem to become complicated then. Clipping plus absolute positioning (which seems to be required by clip to work) and then, for some reason, I had to fiddle with the margins, too, which leads to this (still everything done directly in the inlineStyle/contentStyle attributes, not yet in the CSS file): inlineStyle=margin-right: 55px; // this part only for Firefox... contentStyle=width: 50px; position: absolute; margin-top: -2px; clip:rect(0px, 50px, 20px, 0px) I wonder, if that really is the way to go? Well, probably it is... :-| Cheers, Carsten Martin Marinschek wrote: Hi Carsten, you'd have to play a bit more with CSS there. What you'd really want is something like clipping enabled for the core tag of the readOnly-inputText. http://de.selfhtml.org/css/eigenschaften/positionierung.htm#clip regards, Martin ... -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12052193 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
Hi Carsten, you might also want to try with: display:block; overflow:hidden; and play around some more with this... regards, Martin On 8/8/07, Carsten Pieper [EMAIL PROTECTED] wrote: Thanks Martin, yes, clipping helps in a way, but things really seem to become complicated then. Clipping plus absolute positioning (which seems to be required by clip to work) and then, for some reason, I had to fiddle with the margins, too, which leads to this (still everything done directly in the inlineStyle/contentStyle attributes, not yet in the CSS file): inlineStyle=margin-right: 55px; // this part only for Firefox... contentStyle=width: 50px; position: absolute; margin-top: -2px; clip:rect(0px, 50px, 20px, 0px) I wonder, if that really is the way to go? Well, probably it is... :-| Cheers, Carsten Martin Marinschek wrote: Hi Carsten, you'd have to play a bit more with CSS there. What you'd really want is something like clipping enabled for the core tag of the readOnly-inputText. http://de.selfhtml.org/css/eigenschaften/positionierung.htm#clip regards, Martin ... -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12052193 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
Hi Martin, you might also want to try with: display:block; overflow:hidden; yes, that seems nicer, thanks again! So, to sum up, the only way to get the complete text out with read-only fields who aren't long enough for the actual text, is to provide it via the tooltip (shortDesc)? Best regards, Carsten Martin Marinschek wrote: Hi Carsten, you might also want to try with: display:block; overflow:hidden; and play around some more with this... regards, Martin ... -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12054523 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
is that Firefox only ? try something like width: 90%; :-) On 8/8/07, Carsten Pieper [EMAIL PROTECTED] wrote: Hello everyone, is this a bug or am I missing something? The situation is as follows: tr:inputText label=My short inputText value=Hello inputText contentStyle=width: 50px; readOnly=true /tr:inputText The text then exceeds the actual text area as shown in the screenshot (note that the read-only text area background is slightly darker than the rest...). http://www.nabble.com/file/p12049157/inputTextReadOnly.jpg If readOnly isn't set (or false), then everything is as expected as again shown in the screenshot (only 50 px of text are shown, but you can access the rest via mouse/keyboard): http://www.nabble.com/file/p12049157/inputText.jpg Any ideas? Thanks in advance, Carsten -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12049157 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
Re: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
Carsten wants to have the exact number of pixels, I heavily suppose ;) There is javascript functionality e.g. in Dojo which counts the character which fit in a specified width - you could try applying a function like this. regards, Martin On 8/8/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: is that Firefox only ? try something like width: 90%; :-) On 8/8/07, Carsten Pieper [EMAIL PROTECTED] wrote: Hello everyone, is this a bug or am I missing something? The situation is as follows: tr:inputText label=My short inputText value=Hello inputText contentStyle=width: 50px; readOnly=true /tr:inputText The text then exceeds the actual text area as shown in the screenshot (note that the read-only text area background is slightly darker than the rest...). http://www.nabble.com/file/p12049157/inputTextReadOnly.jpg If readOnly isn't set (or false), then everything is as expected as again shown in the screenshot (only 50 px of text are shown, but you can access the rest via mouse/keyboard): http://www.nabble.com/file/p12049157/inputText.jpg Any ideas? Thanks in advance, Carsten -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12049157 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
Carsten wants to have the exact number of pixels, I heavily suppose ;) You bet! That's why they call me the Pixel-Schubser (pixel jostler?) 'round here ;-) Carsten -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12055264 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Trinidad] inputText with readOnly=true and limited width shows strange behaviour
Pixel-Schubser works :-) On 8/8/07, Carsten Pieper [EMAIL PROTECTED] wrote: Carsten wants to have the exact number of pixels, I heavily suppose ;) You bet! That's why they call me the Pixel-Schubser (pixel jostler?) 'round here ;-) Carsten -- View this message in context: http://www.nabble.com/-Trinidad--inputText-with-readOnly%3D%22true%22-and-limited-width-shows-strange-behaviour-tf4234891.html#a12055264 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
