Details

    • Type: Bug Fix Bug Fix
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.2.0-m3
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-10004On mouse over not getting triggered
      KULRICE-13280Mouse Events demo: In Chrome, mousing over the checkbox doesn’t do anything
      KULRICE-11700Replace tooltip implementation with Bootstrap
      KULRICE-7332Tooltip behavior is inconsistent
      KULRICE-8081Problem with 'no tooltips' in validation framework demo
      KULRICE-13790Fill AFT Gap: Kitchen Sink: Event Examples
      KULRICE-7870Tooltips are not removed if a timed refresh occurs while they are open
      KULRICE-11949Rework help tooltip logic to prevent problems with lifecycle strictness check
      KULRICE-7158Validation messaging - single checkbox tooltip persists/open
      KULRICE-7466Validation messaging - user should be able to move cursor/focus into validation tooltip area
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      UIF Component
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      I saw that the behaviour really get difficult to control if you add a tooltip on a group and then on elements in that group. I am starting to feel that limiting the components it can be added to would be the safest route for now - would recommend not allowing adding on container components.

      Just a note on the mouse events. I changed the .hover to mouseenter and mouseleave and then remember I did have a look at it. So I had a look at .hover() - it actually uses the mouseenter and mouseleave events.

      http://api.jquery.com/hover/

      The group depends on the type of group : Uif-Disclosure-TableCollectionSection had issues. Uif-VerticalBoxSection worked fine.

        Activity

        Hide
        Jessica Coltrin (Inactive) added a comment -

        moving non-blocker and non-critical m4 Jiras to 2.2-backlog

        Show
        Jessica Coltrin (Inactive) added a comment - moving non-blocker and non-critical m4 Jiras to 2.2-backlog

          People

          • Assignee:
            Unassigned
            Reporter:
            Samuel Holtzkampf (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Structure Helper Panel