[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197737#comment-16197737 ] Leonardo Uribe commented on MYFACES-4162: - I'm still here. Just don't have enough time to

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197316#comment-16197316 ] Werner Punz commented on MYFACES-4162: -- Yeah I noticed. I will ask around what happened to him. He

[jira] [Commented] (MYFACES-4154) The browser (chrome) always show the previous page name while its on the current page rendered properly

[ https://issues.apache.org/jira/browse/MYFACES-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197313#comment-16197313 ] Werner Punz commented on MYFACES-4154: -- Upping the bug to major, since the navigational code is

[jira] [Comment Edited] (MYFACES-4154) The browser (chrome) always show the previous page name while its on the current page rendered properly

[ https://issues.apache.org/jira/browse/MYFACES-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197309#comment-16197309 ] Werner Punz edited comment on MYFACES-4154 at 10/9/17 5:02 PM: --- Adding the

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197308#comment-16197308 ] Thomas Andraschko commented on MYFACES-4162: All right. I will try to have a look at this.

[jira] [Commented] (MYFACES-4154) The browser (chrome) always show the previous page name while its on the current page rendered properly

[ https://issues.apache.org/jira/browse/MYFACES-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197309#comment-16197309 ] Werner Punz commented on MYFACES-4154: -- Adding the comment from 4162 I just checked the usecase,

[jira] [Commented] (MYFACES-4154) The browser (chrome) always show the previous page name while its on the current page rendered properly

[ https://issues.apache.org/jira/browse/MYFACES-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197304#comment-16197304 ] Werner Punz commented on MYFACES-4154: -- I investigated the issue, this seems like a wrong viewstate

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197277#comment-16197277 ] Werner Punz commented on MYFACES-4162: -- I just checked the usecase, that is unrelated to the ajax

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197153#comment-16197153 ] Thomas Andraschko commented on MYFACES-4162: So

[jira] [Resolved] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved MYFACES-4162. -- Resolution: Resolved > bug in the response handling if a full page is sent via ajax >

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197128#comment-16197128 ] Werner Punz commented on MYFACES-4162: -- so fixed in 1811580 apparently, there were some smaller

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197098#comment-16197098 ] Werner Punz commented on MYFACES-4162: -- Actually it seems to be a slight js error on my side in the

[jira] [Comment Edited] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197068#comment-16197068 ] Werner Punz edited comment on MYFACES-4162 at 10/9/17 2:36 PM: --- Actually

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197068#comment-16197068 ] Werner Punz commented on MYFACES-4162: -- Actually on the response side it looks ok

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197067#comment-16197067 ] Dora Rajappan commented on MYFACES-4162: Works fine with IE and not with chrome! > bug in the

[jira] [Comment Edited] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197062#comment-16197062 ] Thomas Andraschko edited comment on MYFACES-4162 at 10/9/17 2:33 PM: -

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197062#comment-16197062 ] Thomas Andraschko commented on MYFACES-4162: so the navigation is triggered but not via

[jira] [Created] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

Werner Punz created MYFACES-4162: Summary: bug in the response handling if a full page is sent via ajax Key: MYFACES-4162 URL: https://issues.apache.org/jira/browse/MYFACES-4162 Project: MyFaces Core

Re: jsf.js post 2.3 plans

 Hi Werner,      I had a mvn clean package of core and checked it from IE 11 and it works very good.     The fix works fine with repeated ajax calls now!    Thanks & Regards, Dora Rajappan. .On Monday, October 9, 2017, 3:19:19 PM GMT+5:30, Werner Punz wrote:

[jira] [Commented] (TOBAGO-1810) Create a markup for expanding tc:bar

[ https://issues.apache.org/jira/browse/TOBAGO-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196768#comment-16196768 ] Hudson commented on TOBAGO-1810: SUCCESS: Integrated in Jenkins build Tobago Trunk #1065 (See

Re: jsf.js post 2.3 plans

Just to clarify it: Before the update it looks like https://gist.github.com/werpu/071e11cc6328f9f439a6342b0e128ec8 Both forms have a viewstate element. Before my fixes, the viewstate of the first form was gone. Hence you ran into issues: After my yesterdays update the result now looks like

Re: jsf.js post 2.3 plans

Hi Dora, what do you mean that the behavior of repeated ajax calls is same? I tried your example yesterday after building the final js file via a mvn build and before only the second form got an ajax viestate update now both forms get one. What behavior do you get? Did you make a proper mvn

Re: jsf.js post 2.3 plans

Hi,  Thank you very much for the fix Werner. I took the latest core today and built it and tested from payara without any config changes. Found ajaxresponse22.js deleted and ajaxresponse.js changed. And the behavior of repeated ajax calls is same. Can we have the config changes exactly if any

Re: JSF 2.3 some minor questions regarding jsf.js

Ok thanks for the clarification. Cheers Werner All my fixes are pushed, give it a proper beating. Am 08.10.17 um 17:06 schrieb Thomas Andraschko: Hi, cool +1! 1) yep, push should be already done 2) the server should already only render real new resources, if it's not happening, we

[jira] [Comment Edited] (MYFACES-4160) ViewState not written for Ajax request

[ https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1619#comment-1619 ] Werner Punz edited comment on MYFACES-4160 at 10/9/17 8:39 AM: --- The

[jira] [Commented] (MYFACES-4160) ViewState not written for Ajax request

[ https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1619#comment-1619 ] Werner Punz commented on MYFACES-4160: -- The example from MYFACES-4156 looks fine now. My testing

[jira] [Created] (TOBAGO-1814) Create markups for light / dark tc:bar

Henning Noeth created TOBAGO-1814: - Summary: Create markups for light / dark tc:bar Key: TOBAGO-1814 URL: https://issues.apache.org/jira/browse/TOBAGO-1814 Project: MyFaces Tobago Issue

[jira] [Commented] (MYFACES-4160) ViewState not written for Ajax request

[ https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196588#comment-16196588 ] Thomas Andraschko commented on MYFACES-4160: Thanks werner! So my example app is also

[jira] [Commented] (EXTSCRIPT-188) Extension don't works on Myfaces 2.2.3 / 2.2.11

[ https://issues.apache.org/jira/browse/EXTSCRIPT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196557#comment-16196557 ] Werner Punz commented on EXTSCRIPT-188: --- The config should be ok... the examples are basically

Re: jsf.js post 2.3 plans

Ok just to FUP... To give food for discussion: I gave kotlin a few minutes ago a testrun, here is the result: package test.test2 class TestClass { val hello: String = ""; fun helloWorld() { console.info("hello"); } } and the resulting Javascript was: if (typeof

[jira] [Commented] (EXTSCRIPT-188) Extension don't works on Myfaces 2.2.3 / 2.2.11

[ https://issues.apache.org/jira/browse/EXTSCRIPT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196551#comment-16196551 ] NCister commented on EXTSCRIPT-188: --- Hi Werner. Excuse me ... what's your test environment ? (app.