[ http://jira.jboss.com/jira/browse/RF-3477?page=all ] Nick Belaevski updated RF-3477: ------------------------------- Assignee: Vladimir Molotkov (was: Nick Belaevski) Fix Version/s: Future -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-3477?page=com.atlassian.jira.plugin... ] Gilles Demarty commented on RF-3477: ------------------------------------ i think using jquery live query plugin (http://brandonaaron.net/docs/livequery/) could help into solving this issue. quote : Live Query utilizes the power of jQuery selectors by binding events or firing callbacks for matched elements auto-magically, even after the page has been loaded and the DOM updated. -- 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

[ https://jira.jboss.org/jira/browse/RF-3477?page=com.atlassian.jira.plugin... ] Nick Belaevski updated RF-3477: ------------------------------- Component/s: component-misc core Fix Version/s: 4.0.0.ALPHA1 (was: Future) Assignee: Nick Belaevski -- 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

[ https://jira.jboss.org/jira/browse/RF-3477?page=com.atlassian.jira.plugin... ] Robert Raksi commented on RF-3477: ---------------------------------- I encountered the same problem using livequery( matchedFn, unmatchedFn ) http://docs.jquery.com/Plugins/livequery/livequery#matchedFnunmatchedFn When rerendering the component the unmatchedFn is called but the matchedFn is never called again even though the newly rendered component is the same as the old one as far as the jQuery matcher is concerned. Environment: - RF 3.3.1 - JBoss 4.2.3 - Seam 2.1.1 -- 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

[ https://jira.jboss.org/jira/browse/RF-3477?page=com.atlassian.jira.plugin... ] Robert Raksi commented on RF-3477: ---------------------------------- Sorry for spamming, I know that this is not a forum but I did some digging. I attached a simple test case (test.xhtml). Scenario: - execute jQuery("input.foo") in the firebug console, you get one match - type something in the input field than hit tab, the input is rerendered - execute jQuery("input.foo") again, you get zero match instead of one, this is bad The cause: the content type of the page is set to text/html but the response of the ajax request is text/xml. If I set the content type of the page to application/xhtml+xml everything works fine, but in IE I get a download window. Is there a way to set the content type of the ajax responses to text/html? Or this is not a good idea? The environment is the one mentioned in my previous comment. -- 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

[ https://jira.jboss.org/jira/browse/RF-3477?page=com.atlassian.jira.plugin... ] Nick Belaevski commented on RF-3477: ------------------------------------ Robert, Just remove contentType="text/html" - Facelets should do the necessary negotiation themselves -- 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

[ https://jira.jboss.org/jira/browse/RF-3477?page=com.atlassian.jira.plugin... ] Nick Belaevski commented on RF-3477: ------------------------------------ That's right, this doesn't work. Looks like FF 3.5 fixed the problem, please try in it -- 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

[ https://jira.jboss.org/jira/browse/RF-3477?page=com.atlassian.jira.plugin... ] Nick Belaevski commented on RF-3477: ------------------------------------ Browser's function importNode() doesn't import XML nodes correct into HTML document, that's the cause of the problem -- 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

[ https://jira.jboss.org/browse/RF-3477?page=com.atlassian.jira.plugin.syst... ] Lukas Fryc closed RF-3477. -------------------------- Verified with 4.0.0.20100715-M1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira