[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-10980: ------------------------------------ Hi Dmitry, I cannot reproduce the bug with sample similar to the one below. It works in Chrome 11, Firefox 3.6 and IE9. Could you please let me know what implementation of JSF and which versions of browsers are you using? {code:xml} <h:inputText tabindex="1"/> <h:inputSecret tabindex="2"/> <rich:popupPanel ...> <h:inputText tabindex="3"/> <h:inputSecret tabindex="4"/> <h:inputText tabindex="5"/> <h:inputSecret tabindex="6"/> </rich:popupPanel> {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak reassigned RF-10980: ---------------------------------- Assignee: Jay Balunas (was: Pavol Pitonak) Reproduced in following environment: RichFaces 4.1.0-SNAPSHOT Metamer 4.1.0-SNAPSHOT r.22517 Mojarra 2.1.0-FCS GlassFish Server Open Source Edition 3.1 Java(TM) SE Runtime Environment 1.6.0_24-b07 @ Linux Chrome 11.0.696.71 @ Linux i686 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] Jay Balunas updated RF-10980: ----------------------------- Fix Version/s: 4.Future (was: 4.1.0.Milestone1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] Eugenia Sergueeva commented on RF-10980: ---------------------------------------- Hi! I also faced the problem with tabindex being set to -1 in the pop up panel. What I have also noticed is that the pop up in the richfaces showcase's page dataTableEdit-sample.xhtml is actually a well working one(<rich:popupPanel id="editPane".../>). After some investigation a came up to the following- if I remove the <a4j:status onstart="#{rich:component('statPane')}.show()" onstop="#{rich:component('statPane')}.hide()" /> line and the corresponding pop up panel <rich:popupPanel id="statPane" ... /> from the page, the editPane pop up stops responding to the tab key (the tabindex is set to -1). So adding the same a4j:status to any page with a pop up solves the tab traversing issue... Reproduced in richfaces demo, versions 4.0.1-SNAPSHOT, 4.1.0-SNAPSHOT I think this might be connected with this bug. -- 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

[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] Eugenia Sergueeva edited comment on RF-10980 at 10/26/11 11:19 AM: ------------------------------------------------------------------- Hi! I also faced the problem with tabindex being set to --1 in the pop up panel. What I have also noticed is that the pop up in the richfaces showcase's page dataTableEdit-sample.xhtml is actually a well working one(<rich:popupPanel id="editPane".../>). After some investigation a came up to the following- if I remove the <a4j:status onstart="#{rich:component('statPane')}.show()" onstop="#{rich:component('statPane')}.hide()" /> line and the corresponding pop up panel <rich:popupPanel id="statPane" ... /> from the page, the editPane pop up stops responding to the tab key (the tabindex is set to --1). So adding the same a4j:status to any page with a pop up solves the tab traversing issue... Reproduced in richfaces demo, versions 4.0.1-SNAPSHOT, 4.1.0-SNAPSHOT I think this might be connected with this bug. was (Author: jeniajeni): Hi! I also faced the problem with tabindex being set to "-1" in the pop up panel. What I have also noticed is that the pop up in the richfaces showcase's page dataTableEdit-sample.xhtml is actually a well working one(<rich:popupPanel id="editPane".../>). After some investigation a came up to the following- if I remove the <a4j:status onstart="#{rich:component('statPane')}.show()" onstop="#{rich:component('statPane')}.hide()" /> line and the corresponding pop up panel <rich:popupPanel id="statPane" ... /> from the page, the editPane pop up stops responding to the tab key (the tabindex is set to "-1"). So adding the same a4j:status to any page with a pop up solves the tab traversing issue... Reproduced in richfaces demo, versions 4.0.1-SNAPSHOT, 4.1.0-SNAPSHOT I think this might be connected with this bug. -- 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

[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] u j commented on RF-10980: -------------------------- Indeed, I could remedy the problem with your workaround, but only on Firefox and Chrome and setting tabindex values on the fields. (In Chrome it works without the workaround, just using tabindex.) In IE (9) it does not help, independent of the compatibility mode. Crazy, you really need the show and hide calls, without it does not work. Thanks -- 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

[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] u j commented on RF-10980: -------------------------- Of course I prefer the bug to be fixed, but meanwhile I need every workaround I can get. -- 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

[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] Nicolas Daniels commented on RF-10980: -------------------------------------- If it can help, what've done as workarround is (using jquery): In any included JS (or even in the page): function fixTabIndexes(elem) { //See rich faces bug https://issues.jboss.org/browse/RF-10980 (tab index set to -1 in popup panel) $(elem).find('*[tabindex="-1"]').each(function() { $(this).removeAttr('tabindex'); }); } And in my page: function displayEditProfilePopup() { #{rich:component('editProfilePopup')}.show(); fixTabIndexes(#{rich:element("editProfilePopupContent")}); } -- 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

[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-10980: ---------------------------- Fix Version/s: 4.3.0.Milestone1 (was: 4.Future) Assignee: Bernard Labno -- 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

[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-10980: --------------------------------- As Bernard pointed out, the problem is that all inputs are processed in the {{[processTabindex|https://github.com/richfaces/components/blob/develop/output/ui/src/main/resources/META-INF/resources/org.richfaces/popupPanel.js#L425}}/{{restoreTabindexes}} methods. We need to add condition and do not process indexes which are inside the modal panel. -- 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

[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-10980: --------------------------------- Thanks Pavol -- 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

[ https://issues.jboss.org/browse/RF-10980?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-10980: ------------------------------- Fix Version/s: 4.2.3.CR1 (was: 4.2-Tracking) -- 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