Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Hopefully, we will see if anyone raises an issue. That's the only change I was uncertain of making but it should not be a big impact and I can definitely reproduce the error if it's selectable.

Makes sense, text in a drop container will probably never need to be selectable, right?

Hmmm, one case I can see it being useful to be selectable is Kanban board? Tho it seems like even in github it doesn't work well, you can select the first container, but not the others as when you try to do it, it inits the drag action.

Thanks @Anu6is

I think this change is problematic, since datagrid uses drop container even if you don't have drag and drop enabled, you can't select anything in the datagrid at all, and we don't have intuitive opt out for this logic, and somebody on discord already complained about it.

Maybe we should at least add datagrid to exclusion and remove user-select for it.

Also one moment, always do this in future:

Resolves: #10645
Resolves: #6427 
Resolves: #4601
Resolves: #9836
Resolves: #8147
Resolves: #5869
Resolves: #3991

rather than in one line, otherwise github will not register the issues and auto close them on merge.

Maybe we should at least add datagrid to exclusion and remove user-select for it.

Reverted the no select in the container. The other two fixes remain. Excluding data grid helps with our component but not if a user wraps something they made in a similar manner.

Another option could be adding a SelectContent parameter to the drop container to toggle selection. But for now I think reverting is fine