Ingo Schommer

> but I would think if you jump from one grid field to another the previous selection could be deselected That's going to be a bit confusing - often a...

I think with drag/drop moving in the gallery view, and the batch move currently implemented through https://github.com/silverstripe/silverstripe-asset-admin/issues/578, the priority of this decreases - removing from milestone.

@clarkepaul Actually do you think we need to do this at all, given there's two other ways of achieving this goal for the user already?

History view is operational without GraphQL, hence this card isn't essential for beta1.

Agreed, we should use flexbox pretty much everywhere. For me that's more of a long-term maintenance concern though. I'm happy to live with with the visual spacing issues for now....

That's quite a theoretical use case, right? Either you upload an image for use in the content, in which case it'll be published when you publish the page. Or you...

Yeah I'm keen to address the root of this issue through https://github.com/silverstripe/silverstripe-asset-admin/issues/591, rather than further complicate the already heavyweight customisations we do inside TinyMCE.

@flamerohr @unclecheese Do you think this is the next most important cleanup activity to work on after Chris' work on "Cleanup React Conventions" (https://github.com/silverstripe/silverstripe-framework/issues/6427)? What React code patterns are giving...

> We could also look at how we're communicating across components when something needs to refresh This would be solved by more widespread use of GraphQL, right? The fact that...

Sigh, not going to fit in the milestone