[richfaces-issues] [JBoss JIRA] (RF-13246) Richfaces 4.3.4 ajax fails on ie8 packed.js cannot find console.

[Jeremy Landis (JIRA)]

    [ https://issues.jboss.org/browse/RF-13246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12938641#comment-12938641 ] 

Jeremy Landis commented on RF-13246:
------------------------------------

Brian, thanks for a quick response.  I have did a little more digging and isolated the actual root problem.  I made too many assumptions on the cause of this until I stumbled down this path today.  I'm sorry for causing any additional effort to verify and will do a better job next time of knowing my issue before reporting.  I no longer believe there is anything in the showcase that would result in this issue.

The issue actually appears to be this line of code used on our master template.  So likely it doesn't affect the showcase as I assumed.

<a4j:log level="ALL" mode="popup" />

Looking over the jira changes for 4.3.4, it appears that "ALL" is no longer a valid option.  Aside from fixing that, how might I be able to still use this logic with the 4.3.4 changes to logging?
                
> Richfaces 4.3.4 ajax fails on ie8 packed.js cannot find console.
> ----------------------------------------------------------------
>
>                 Key: RF-13246
>                 URL: https://issues.jboss.org/browse/RF-13246
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: Jeremy Landis
>            Assignee: Jiří Štefek
>              Labels: waiting_on_user
>
> After upgrading to richfaces 4.3.4 using jsf 2.1.26, ajax has stopped working in IE8.  I have been able to verify non issue in firefox and IE11.  The issue affects specialized ajax calls within a page as well as overall ajax page areas.  It further affects extended data grids where it will not allow next page logic to work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira