V8: Grid layout editorService dialogs close row settings dialog

Hi, When you try to open any editorService-editor (i.e. contentPicker, mediaPicker) from the row-settings dialog it will show a blur over the opened dialog. You can click this blur away but as soon as you close the mediaPicker (with editorService.close()), it will also close the row-settings dialog. This causes the image to never be saved. Please look at this gif for a visual representation (note the blur when the mediaPicker opens):

The code i use within the row-settings dialog looks like :

$scope.addImage = function () {
    editorService.mediaPicker({
        onlyImages: true,
        multiPicker: false,
        submit: function (item) {
            // do stuff
            editorService.close();
        },
        close: function () {
            editorService.close();
        }
    });
};

When you open another dialog, Umbraco renders a second div with class “umb-overlay-backdrop”. This overlay renders in front of the media picker, which will make it unclickable. I hacked the backdrop to never show, which fixes the issue, but is not the solution. .umb-overlay-backdrop { display: none !important; }

[mecograph]

@marcoteodoro here you go:

var options = {
     title: "Edit settings",
     view: "/App_Plugins/ListBoxStatic/assets/editSettings.html",
     size: "small",
     data: data,
     submit: (response) => {
          // do sth with response
          editorService.close();
     },
     close: () => editorService.close()
};
editorService.open(options);

[umbrabot]

Hiya @Lars-OJ,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we’re happy to open it up again if you think it’s still relevant (for example: it’s a feature request that’s not yet implemented, or it’s a bug that’s not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it’s still relevant.

For example:

@umbrabot still relevant This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂