While there is a workaround that @bart pointed out, it certainly feels like unexpected default behavior, so we’re treating it as a bug internally. Hoping to have better UX around this interaction soon 
4 Likes