MediaPicker3: "Accepted Types" makes not accepted types act ac folder

[enkelmedia]

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

13.3.1

Bug summary

I've noticed that MediaPicker3 behaves strangely when limiting the Accepted types. A custom media type will start to act as a folder if not accepted for the current data type.

Specifics

Here is a video that shows the behavior, after limiting the "Accepted types" for the data type the custom file type that we have define, starts to act as a folder. Clicking the icon will navigate "in to" the file as if it was a folder.

I'm guessing that this is because the umb-media-grid thinks that this is a folder, at least it looks like this in the markup:

Steps to reproduce

Setup a new Umbraco site and:

• Create a new custom file type "My Custom Thing" with one property Umbraco File (alias: umbracoFile). Allow at root.
• Create a new custom file type "Custom Video" with one property Umbraco File (alias: umbracoFile). Allow at root.
• Go to media and create one of each of the new media types (no need to upload files).
• Add a document type called "Home" and add a property with data type MediaPicker3.
• Open the data type and add "Custom Video" in the "Accepted Types" list.
• Go to the content-section, create a home-document and try to pick the "My Custom Thing", notice that it does not show any "stop"-icon and that it allows to navigate "in to" the "Custom Video" as if it was a folder.

Expected result / actual result

Media types not included in "Accepted Types" should probably not be clickable if they are not a folder.

Not sure what determines if a media type is a folder but it would probably make sense to either:

• Assume that anything that allows another media below (Allowed child node types) is a folder
• Add some kind of setting (like the "Is Element Type" for documents) but "Is Folder Type" in media.

[github-actions[bot]]

Hi there @enkelmedia!

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 :robot: :slightly_smiling_face: