Giter Club home page Giter Club logo

Comments (4)

ionitron-bot avatar ionitron-bot commented on September 21, 2024

Thanks for the issue! This issue has been labeled as needs reproduction. This label is added to issues that need a code reproduction.

Please reproduce this issue in an Ionic starter application and provide a way for us to access it (GitHub repo, StackBlitz, etc). Without a reliable code reproduction, it is unlikely we will be able to resolve the issue, leading to it being closed.

If you have already provided a code snippet and are seeing this message, it is likely that the code snippet was not enough for our team to reproduce the issue.

For a guide on how to create a good reproduction, see our Contributing Guide.

from ionic-framework.

mattiaGec avatar mattiaGec commented on September 21, 2024

Here the github repo https://github.com/mattiaGec/IonicModalTest

from ionic-framework.

MattiaGeccheleAxa avatar MattiaGeccheleAxa commented on September 21, 2024
modal.bug.mp4

from ionic-framework.

sean-perkins avatar sean-perkins commented on September 21, 2024

Hello @mattiaGec thank you for reporting this issue!

I can confirm the problematic behavior.

When the dismiss callback returned by useIonModal is called multiple times, it only attempts to dismiss the modal the first time it is called.

This is due to the implementation for the dismiss method in useOverlay:

const dismiss = useCallback(async (data?: any, role?: string) => {
overlayRef.current && (await overlayRef.current.dismiss(data, role));
overlayRef.current = undefined;
containerElRef.current = undefined;
}, []);

The specific problem is this line of code:

overlayRef.current = undefined;
We should only be clearing the overlay reference if the overlay actually dismissed, by looking at the return value of overlayRef.current.dismiss. If the overlay did not dismiss, we should not clear the reference.

I will classify this as a bug and the team can prioritize it within the backlog. If anyone would like to submit a PR for this, I would gladly welcome the contribution!

This would be the proposed change that I would validate with testing:

const dismiss = useCallback(async (data?: any, role?: string) => {
  if (overlayRef.current) {
    const didDismiss = await overlayRef.current.dismiss(data, role);
    if (didDismiss) {
      overlayRef.current = undefined;
      containerElRef.current = undefined;
    }
  }
}, []);

from ionic-framework.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.