Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-4164

Core FAB is not removed properly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 4.1.0
    • 4.0.2
    • Site add-ons
    • Hide
      1. Install the local_sandbox plugin attached to this issue in a Moodle site.
      2. Connect to the site using the mobile app.
      3. Open the more menu, and click on "Sandbox".
      4. Refresh the page multiple times, and make sure that the fab button is not being rendered multiple times. You should be able to tell by looking that the drop shadow is not darker every time.
      Show
      Install the local_sandbox plugin attached to this issue in a Moodle site. Connect to the site using the mobile app. Open the more menu, and click on "Sandbox". Refresh the page multiple times, and make sure that the fab button is not being rendered multiple times. You should be able to tell by looking that the drop shadow is not darker every time.
    • MOODLE_400_STABLE
    • MOODLE_401_STABLE
    • Moodle App 4.1.0

      The core-fab directive is used to move ion-fabs to their proper DOM location when they are rendered inside of a component.

      In most situations in the app, this is not a problem because these components are not refreshed, and whenever they get destroyed the parent where the FAB was moved to is destroyed as well. However, if this is used in a site plugin, it is possible that the plugin component is refreshed without the fab being removed. This creates a situation where the FAB is duplicated every time.

            noeldemartin Noel De Martin
            noeldemartin Noel De Martin
            Dani Palou Dani Palou
            Isabel Renedo Rouco Isabel Renedo Rouco
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.