Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After creating new data type from modal window unable to close alert #17171

Open
PeterKvayt opened this issue Oct 2, 2024 · 3 comments
Open

Comments

@PeterKvayt
Copy link
Contributor

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

14.2.0

Bug summary

I tried to close alert by clicking on "close" icon, but nothing happen.

image

Specifics

No response

Steps to reproduce

  1. Create new document type "A"
  2. Add new property
  3. In modal window "Edit property" click "Select Property Editor"
  4. In modal window "Select editor" click "Decimal" -> "Create new"
  5. In opened modal window for editing new editor click "Save"
  6. Then alert is displayed "Created"
  7. Try to close it by clicking on cross icon

Expected result / actual result

Expected: alert closed and dissapiar
Actual: unable to interact with it. I waited long time but it does not dissapiared. Only after clicking "Submit" button in "Add property" modal window I have abillity to interact with alert.

Copy link

github-actions bot commented Oct 2, 2024

Hi there @PeterKvayt!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@iOvergaard
Copy link
Contributor

Hello @PeterKvayt, thanks for reporting this! I can confirm this is an issue in v14 and v15. We would like some help fixing it, and it could be a suitable candidate for hacktoberfest, which just started, so I will go ahead and mark the issue as such to maximise the potential of getting it fixed sooner rather than later.

Copy link

github-actions bot commented Oct 2, 2024

Hi @PeterKvayt,

We're writing to let you know that we would love some help with this issue. We feel that this issue is ideal to flag for a community member to work on it. Once flagged here, folk looking for issues to work on will know to look at yours. Of course, please feel free work on this yourself ;-). If there are any changes to this status, we'll be sure to let you know.

For more information about issues and states, have a look at this blog post.

Thanks muchly, from your friendly Umbraco GitHub bot :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants