This is a known issue. See here and here.
From what I can see there, it is planned for later milestones, which probably means no fix soon, unless the community manages to convince the team.