Does not seem to support @media queries with Flex Grid

[born2net]

Bug Report

I have the following CSS:

@media (min-width: 1000px) {
  .cardInner {
    grid-template-columns: 100% 100%;  /** width per columns **/
    grid-row-gap: 0;
    grid-column-gap: 0;
    grid-template-areas:
      'header'
      'sideA'
      'sideB'
      'sideC'
      'sideD';
  }
}


.cardInner {
  display: grid;
  //justify-content: end;
  //justify-items: end;
  grid-template-areas:
    "header header"
    "sideA sideB"
    "sideC sideD";

  grid-template-columns: 50% 50%;  /** width per columns **/
  grid-template-rows: auto 50px 50px; /** height per row **/
  grid-row-gap: 0;
  grid-column-gap: 0;
}

and when I scale down browser I expect to have the new .grid query apply.
Nothing happens when I scale down and I am using the latest version of flex-layout.

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.800.2
@angular-devkit/build-angular      0.800.2
@angular-devkit/build-optimizer    0.800.2
@angular-devkit/build-webpack      0.800.2
@angular-devkit/core               8.0.2
@angular-devkit/schematics         8.0.6
@angular/cdk                       8.0.1
@angular/cli                       8.0.6
@angular/flex-layout               8.0.0-beta.26
@angular/http                      7.2.15
@angular/material                  8.0.1
@angular/material-moment-adapter   8.0.1
@ngtools/webpack                   8.0.2
@schematics/angular                8.0.6
@schematics/update                 0.800.6
rxjs                               6.4.0
typescript                         3.4.5
webpack                            4.30.0

[CaerusKaru]

Pardon the bluntness, but how is this possibly an issue with Angular Layout?

[born2net]

fixed it with !important

@media (max-width: 1200px) {
  .cardInner {
    grid-template-areas: "header" "sideA" "sideB" "sideC" "sideD" !important;
  }
}

[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.}