[
https://issues.apache.org/jira/browse/MYFACES-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666874#comment-16666874
]
Werner Punz edited comment on MYFACES-3751 at 10/29/18 9:02 AM:
----------------------------------------------------------------
Ups sorry... I did not read properly (time for a coffee) oamsubmit is not part
of the standard, this is myfaces specific, so if something is swallowed there
it is better to log the error out.
JSF ajax is another issue, there we have a dedicated error handling.
as for console.error in oamsubmit, check for the existence first, i am not
sure, but there still might be some users who are on browsers without consoles
or where the console is undefined in non debug mode. (ie6-10 I think)
was (Author: werpu):
Afair expected behavior, script errors on the JSF side are only exposed in dev
mode or if an error listener is explicitely set.
I think it was part of the spec... but I really have to look this up.
So if you apply an error listener you can do whatever you want with the error
info.
> Log exception on submitForm in Javascript
> -----------------------------------------
>
> Key: MYFACES-3751
> URL: https://issues.apache.org/jira/browse/MYFACES-3751
> Project: MyFaces Core
> Issue Type: Improvement
> Affects Versions: 2.1.12
> Reporter: dennis hoersch
> Priority: Major
>
> I was looking for a bug in our scripts happening on submit of the form.
> Unfortunately the JSF-Javascript submitting the form
> (myfaces.oam.submitForm()) is swallowing exceptions that occur while
> submitting.
> try {
> form.submit();
> }
> catch(e) {
> }
> Maybe one could do some kind of logging there to help debugging.
> try {
> form.submit();
> }
> catch(e) {
> console.error(e); //?
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
