ICEfaces
  1. ICEfaces
  2. ICE-2408

XHTML: <select>, using attribute not defined by DTD

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Minor Minor
          • Resolution: Won't Fix
          • Affects Version/s: 1.6.2
          • Fix Version/s: 1.7RC1, 1.7
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            All

            Description

            According to the ICEfaces documentation, one can add the 'accesskey' attribute to <ice:selectManyListbox>, <ice:selectManyMenu>, <ice:selectOneListbox>,
            and<ice:selectOneMenu>, which is passed through to the <select> element, but the DTD doesn't define this attribute for the <select> element.

              Issue Links

              blocks

              Bug - A problem which impairs or prevents the functions of the product. ICE-1114 Accessiblity: Components must support XHTML v1.0 Transitional markup

              • Major - Major loss of function.
              • Closed

                Activity

                Descending order - Click to sort in ascending order
                Hide
                Permalink
                Adnan Durrani added a comment -

                This info should go into the docs, to let developers know to not to define "accesskey" if they want to valid XHTML.

                Show
                Adnan Durrani added a comment - This info should go into the docs, to let developers know to not to define "accesskey" if they want to valid XHTML.
                Hide
                Permalink
                Adnan Durrani added a comment -

                The "accesskey" attribute is defined by the JSF spec, besides that its not being rendered by default. It will be only rendered if the user will define one. So I don't think if it has to be removed.

                Show
                Adnan Durrani added a comment - The "accesskey" attribute is defined by the JSF spec, besides that its not being rendered by default. It will be only rendered if the user will define one. So I don't think if it has to be removed.

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    Arturo Zambrano
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: