*frowns* Wait a minute, you're thinking to hang the navlinks position css on the module grouping property?

...that seems like bad metadata usage.

And, since the TR layout children inherit the TR module grouping, how is that supposed to allow the positioning of a module in the notional "header"?