You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to #1157, but also completely different. grid-column-gap affects the child grid, not the parent grid; it and grid-area have nothing to do with each other. But presumably because autoprefixer is looking for grid-column-* properties, it warns about it anyway:
You already have a grid-area declaration present in the rule. You should use either grid-area or grid-column-gap, not both
I think this should be removed.
The text was updated successfully, but these errors were encountered:
It shouldn't be warning if using grid-column-gap (or grid-row-gap) in combination with grid-area.
The warning is more intended for uses of grid-area in combination with grid-column, grid-column-start, and grid-column-end.
We should be more specific when checking for a match when displaying the warning or explicitly exclude grid-column-gap and grid-row-gap from the warning message check.
Similar to #1157, but also completely different.
grid-column-gap
affects the child grid, not the parent grid; it andgrid-area
have nothing to do with each other. But presumably because autoprefixer is looking forgrid-column-*
properties, it warns about it anyway:You already have a grid-area declaration present in the rule. You should use either grid-area or grid-column-gap, not both
I think this should be removed.
The text was updated successfully, but these errors were encountered: