fabb

If autoplacing and strict could only be activated together, I could still deactivate it both together using a control comment for regions where the autoplacing does the wrong thing. But...

> Autoplacement can get in the way of manual placement Exactly. The problem is that when `grid-template-areas` is not set, PostCSS cannot know if any child sets `grid-column/row` manually. So...

I stumbled over a conceptual issue when thinking through „output a warning on every `grid-column/row` declaration in strict mode“. I have both an npm package and a main app module...

@Dan503 Yeah sure, but since I suggested the thing with the warning, Inwanted to add a warning for the suggestion 😉. Joke aside, since it seems to be a default...

I'm on 9.4.1 (and now I updated to 9.4.2, same there), but I hadn't activated `autoplace`. When I activate `autoplace`, I get a warning `Autoplacement does not work without grid-template-rows...

Unfortunately I cannot activate `autoplace` since it will jumble the elements in the wrong order, as `autoplace` ignores `grid-column` set in child css rules of the input css.

I was using `grid-column-gap` and `grid-row-gap` separately: ``` .blah { grid-template-areas: 'left right'; grid-template-columns: auto 1fr; grid-template-rows: auto; grid-column-gap: 10px; } ```

Would it be possible to also show a warning when I just specify `grid-template-columns` and `grid-template-rows` but forget about `grid-template-areas`? That would help to reduce regressions in IE11 support a...

> Manually placing cells using line numbers is still a valid way to write grid styles. True, forgot about that. And postcss has no way of knowing if all children...

Created followup ticket: #1167