Uploaded image for project: 'ZK'
  1. ZK
  2. ZK-5097

Reconsider the API of Anchornav to make Anchornav more consistent with other ZK component.

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • Components
    • None

      User Story

      https://www.zkoss.org/wiki/ZK_Component_Reference/Essential_Components/Anchornav

      Details

      1. Please consider maintain the mapping of ZK containers and anchornav in anchornav it self instead of using "ca:data-anchornav-scroll" on targets.
      2. Inconsistency API: Find better solution to prevent idspace issue, that is the reason we use "name" attribute but "id" attribute for Anchornav, But other component use "id" e.g. Popup, Button.
      3. The JQuery-based selector syntax: in the example, ca:data-anchornav-target="$win1" but the window id="win". Please consider not to use JQuery-based selector or keep it as a fallback solution(do not suggest this usage in document).

       

            jumperchen jumperchen
            Leon03 Leon03
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: