Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-7947

Date Picker on Product Analytics never disappears

XMLWordPrintable

    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Hide
      • Select a Product navigating to {Product} > Analytics > Traffic
      • Select a time-range using the data-time-picker
      • Selecting any "from" or "until" and choosing a date you will observe the pop-up calendar stays in the screen and inspecting the element you'll see the error "Uncaught TypeError: Cannot read properties of null (reading 'inline')"

       

      Show
      Select a Product navigating to {Product} > Analytics > Traffic Select a time-range using the data-time-picker Selecting any "from" or "until" and choosing a date you will observe the pop-up calendar stays in the screen and inspecting the element you'll see the error "Uncaught TypeError: Cannot read properties of null (reading 'inline')"  

      In the 3scale SaaS, on Product Analytics if we select a different time-range using the data-time-picker, it works but the date time picker calendar stays on screen and we can't view the graph properly.

      Inspecting the element we can see the error:

      Uncaught TypeError: Cannot read properties of null (reading 'inline')
          at HTMLAnchorElement.datepicker_handleMouseover (datepicker.js?827d:2440)
          at HTMLDivElement.dispatch (VM43064 141:4670)
          at HTMLDivElement.elemData.handle (VM43064 141:4490)
      datepicker_handleMouseover@datepicker.js?827d:2440
      dispatch@VM43064 141:4670
      elemData.handle@VM43064 141:4490

       

              Unassigned Unassigned
              gpereira@redhat.com Gustavo Pereira
              Dominik Hlavac Duran Dominik Hlavac Duran
              Damian Peralta Damian Peralta (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: