build: set dev app density class on body

[crisbeto]

Sets the desnity class on the body, rather than the layout element. We'll need this for overlay-based components that implement the density system.

[devversion]

@crisbeto I think I did it intentionally that way because focused tasks (i.e. overlays) should never scale per density according to the Material Design specification.

[crisbeto]

I've definitely seen different densities for some of the overlay-based components in the spec. E.g. see the "desktop" vs "mobile" in the menu spec: https://material.io/components/menus#specs

[devversion]

To be clear: I'm not concerned with adding this to the body. We can do this either way, but this is just my understanding based on the dedicated density Material Design section. e.g. it says specifically about the menu:

Don’t increase the density of components that involve focused tasks, such as interacting with a dropdown menu or picker.

I might be misinterpreting that though? any ideas?

[crisbeto]

I understand what you mean and it seems like you're interpreting it correctly, but the menu spec contradicts it so I can also see it going either way. IMO we still need this on the body so we can test components that support density and are placed in an overlay.

[devversion]

Yeah, I don't think it matters too much. The fact that the spec is contradictory here, doesn't help here.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}