7:53 a.m.
s:defaultAction blocks new lines in <textArea>
----------------------------------------------
Key: JBSEAM-4648
URL: https://jira.jboss.org/jira/browse/JBSEAM-4648
Project: Seam
Issue Type: Bug
Components: JSF Controls
Reporter: Adrian Mitev
s:defaultAction shouldn't work if the enter button is presses inside textarea element.
To fix the issue wrap the javascript that s:convertEntity generates inside this code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:53 a.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>
[
https://jira.jboss.org/jira/browse/JBSEAM-4648?page=com.atlassian.jira.pl...
]
Adrian Mitev updated JBSEAM-4648:
---------------------------------
Affects Version/s: 2.2.1.CR1
s:defaultAction blocks new lines in <textArea>
----------------------------------------------
Key: JBSEAM-4648
URL: https://jira.jboss.org/jira/browse/JBSEAM-4648
Project: Seam
Issue Type: Bug
Components: JSF Controls
Affects Versions: 2.2.1.CR1
Reporter: Adrian Mitev
s:defaultAction shouldn't work if the enter button is presses inside textarea
element. To fix the issue wrap the javascript that s:convertEntity generates inside this
code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:43 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>
[
https://issues.jboss.org/browse/JBSEAM-4648?page=com.atlassian.jira.plugi...
]
Nicholas Oxhøj commented on JBSEAM-4648:
----------------------------------------
The wrapping suggested in the original post, is for fixing the issue, right? (I take it
that "s:convertEntity" should have said "s:defaultAction")
I don't think there is currently any workaround for using <s:defaultAaction> on
forms with textarea's, so I can't understand, that this issue seems to go
unnoticed - and why more people apparently don't have a problem with this: Googling
for s:defaultaction and textarea, basically have this issue report as it's only hit.
s:defaultAction blocks new lines in <textArea>
----------------------------------------------
Key: JBSEAM-4648
URL: https://issues.jboss.org/browse/JBSEAM-4648
Project: Seam
Issue Type: Bug
Components: JSF Controls
Affects Versions: 2.2.1.CR1
Reporter: Adrian Mitev
s:defaultAction shouldn't work if the enter button is presses inside textarea
element. To fix the issue wrap the javascript that s:convertEntity generates inside this
code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:53 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>
[
https://issues.jboss.org/browse/JBSEAM-4648?page=com.atlassian.jira.plugi...
]
Adrian Mitev commented on JBSEAM-4648:
--------------------------------------
Which is strange because this prevents enters in textarea.
s:defaultAction blocks new lines in <textArea>
----------------------------------------------
Key: JBSEAM-4648
URL: https://issues.jboss.org/browse/JBSEAM-4648
Project: Seam
Issue Type: Bug
Components: JSF Controls
Affects Versions: 2.2.1.CR1
Reporter: Adrian Mitev
s:defaultAction shouldn't work if the enter button is presses inside textarea
element. To fix the issue wrap the javascript that s:defaultAction generates inside this
code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:53 a.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>
[
https://issues.jboss.org/browse/JBSEAM-4648?page=com.atlassian.jira.plugi...
]
Adrian Mitev updated JBSEAM-4648:
---------------------------------
Description:
s:defaultAction shouldn't work if the enter button is presses inside textarea element.
To fix the issue wrap the javascript that s:defaultAction generates inside this code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
was:
s:defaultAction shouldn't work if the enter button is presses inside textarea element.
To fix the issue wrap the javascript that s:convertEntity generates inside this code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
s:defaultAction blocks new lines in <textArea>
----------------------------------------------
Key: JBSEAM-4648
URL: https://issues.jboss.org/browse/JBSEAM-4648
Project: Seam
Issue Type: Bug
Components: JSF Controls
Affects Versions: 2.2.1.CR1
Reporter: Adrian Mitev
s:defaultAction shouldn't work if the enter button is presses inside textarea
element. To fix the issue wrap the javascript that s:defaultAction generates inside this
code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:55 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>
[
https://issues.jboss.org/browse/JBSEAM-4648?page=com.atlassian.jira.plugi...
]
Adrian Mitev edited comment on JBSEAM-4648 at 3/8/11 3:53 AM:
--------------------------------------------------------------
Which is strange because this prevents new lines in textarea.
was (Author: amitev):
Which is strange because this prevents enters in textarea.
s:defaultAction blocks new lines in <textArea>
----------------------------------------------
Key: JBSEAM-4648
URL: https://issues.jboss.org/browse/JBSEAM-4648
Project: Seam
Issue Type: Bug
Components: JSF Controls
Affects Versions: 2.2.1.CR1
Reporter: Adrian Mitev
s:defaultAction shouldn't work if the enter button is presses inside textarea
element. To fix the issue wrap the javascript that s:defaultAction generates inside this
code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:07 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>
[
https://issues.jboss.org/browse/JBSEAM-4648?page=com.atlassian.jira.plugi...
]
Nicholas Oxhøj commented on JBSEAM-4648:
----------------------------------------
Yes - very strange. But I was right in assuming that the JavaScript wrapping code you
gave, was a suggested fix for the Seam developers and not a workaround that I could use
with the current version of Seam, right?
s:defaultAction blocks new lines in <textArea>
----------------------------------------------
Key: JBSEAM-4648
URL: https://issues.jboss.org/browse/JBSEAM-4648
Project: Seam
Issue Type: Bug
Components: JSF Controls
Affects Versions: 2.2.1.CR1
Reporter: Adrian Mitev
s:defaultAction shouldn't work if the enter button is presses inside textarea
element. To fix the issue wrap the javascript that s:defaultAction generates inside this
code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:12 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>
[
https://issues.jboss.org/browse/JBSEAM-4648?page=com.atlassian.jira.plugi...
]
Adrian Mitev commented on JBSEAM-4648:
--------------------------------------
I use it currently in production by substituting the s:defaultAction tag with a patched
version of the javascript generated by the tag.
s:defaultAction blocks new lines in <textArea>
----------------------------------------------
Key: JBSEAM-4648
URL: https://issues.jboss.org/browse/JBSEAM-4648
Project: Seam
Issue Type: Bug
Components: JSF Controls
Affects Versions: 2.2.1.CR1
Reporter: Adrian Mitev
s:defaultAction shouldn't work if the enter button is presses inside textarea
element. To fix the issue wrap the javascript that s:defaultAction generates inside this
code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:11 p.m.
New subject: [JBoss JIRA] (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>
[
https://issues.jboss.org/browse/JBSEAM-4648?page=com.atlassian.jira.plugi...
]
ahus1 commented on JBSEAM-4648:
-------------------------------
Hi, there is a forum reference here that offers a solution for this:
http://seamframework.org/Community/SdefaultActionBlocksNewlinesInTextarea
s:defaultAction blocks new lines in <textArea>
----------------------------------------------
Key: JBSEAM-4648
URL: https://issues.jboss.org/browse/JBSEAM-4648
Project: Seam 2
Issue Type: Bug
Components: JSF Controls
Affects Versions: 2.2.1.CR1
Reporter: Adrian Mitev
s:defaultAction shouldn't work if the enter button is presses inside textarea
element. To fix the issue wrap the javascript that s:defaultAction generates inside this
code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:23 a.m.
New subject: [JBoss JIRA] (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>
[
https://issues.jboss.org/browse/JBSEAM-4648?page=com.atlassian.jira.plugi...
]
Nicholas Oxhøj commented on JBSEAM-4648:
----------------------------------------
Hmm, I just found a problem with the proposed solutions (including my own).
The problem is that we want the user to actually be able to press "Enter" to
create a new line in a textarea. But to implement keyboard navigation in custom
components, at least OpenFaces often place the focus in a "hidden" (not using
"display:none" or "visibility:hidden", but just placed outside the
visible window) textarea to listen to keyboard events. And, as you probably guessed by
now, the defaultAction does not work if the focus is currently placed in e.g. an OpenFaces
DataTable or an OpenFaces TreeTable :-(
Unfortunately I currently don't have any good suggestions on how to work around this
issue. I am not very keen on starting to check for e.g. OpenFaces specific classes (like
"o_hiddenFocus") in the code for defaultAction...
s:defaultAction blocks new lines in <textArea>
----------------------------------------------
Key: JBSEAM-4648
URL: https://issues.jboss.org/browse/JBSEAM-4648
Project: Seam 2
Issue Type: Bug
Components: JSF Controls
Affects Versions: 2.2.1.CR1
Reporter: Adrian Mitev
s:defaultAction shouldn't work if the enter button is presses inside textarea
element. To fix the issue wrap the javascript that s:defaultAction generates inside this
code:
var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() !=
'textarea') { <original javascript here> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4495
days inactive
5134
days old
9 comments
3 participants
participants (3)
-
Adrian Mitev (JIRA) -
ahus1 (JIRA)
-
Nicholas Oxhøj (JIRA)