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

Block Grid Property Editor UI does not always show blocks on Safari. #18457

Open
jdicker-dc opened this issue Feb 25, 2025 · 2 comments
Open

Comments

@jdicker-dc
Copy link

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

14.3.2

Bug summary

On Safari, pages that have blocks selected via a Block Grid Property Editor field, the blocks do not always render in the backoffice. The space is there where the blocks should be, but no blocks are rendered. After saving, the blocks are removed from the content page. If published, the blocks also disappear from the actual site.

Specifics

Tested on Chrome, Firefox, Brave and Safari. It only happens on Safari (Version 18.3 (20620.2.4.11.5).

Image

Steps to reproduce

On Safari: Select a content page that has a field with the Block Grid Property Editor data type and selected blocks. Then save when the blocks do not show and check the page.

Expected result / actual result

Expected result: The blocks should always render if added, and saving the content page should not remove any blocks.

Actual result: The blocks do mostly not render, and saving the content page removes the blocks from that page.

Copy link

Hi there @jdicker-dc!

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 🤖 🙂

@nielslyngsoe
Copy link
Member

Hi @jdicker-dc I see you reported this a few hours ago. Is there any reason why you haven't upgraded to the latest v.15?

I can inform that 15.2 brings a lot of fixes in regards to this area and the soon to come 15.3 brings even more.
So if possible I would upgrade to v.15.2, and then please let us know if you still experience this issue.

Thanks in advance

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