@font-face {
  font-family: 'Material Icons';
  font-style: normal;
  font-weight: 400;
  /*
    For local development we assume that we live at:
        "<hostname>/src/css/material.css"
    while the font we need is at:
        "<hostname>/node_modules/material-design-icons-iconfont/dist/fonts/blah.woff2"
    along with all our other dependencies.
  */
  src: local('Material Icons'),
       local('MaterialIcons-Regular'),
       url('/node_modules/material-design-icons-iconfont/dist/fonts/MaterialIcons-Regular.woff2') format('woff2'),
       url('/node_modules/material-design-icons-iconfont/dist/fonts/MaterialIcons-Regular.ttf') format('truetype');
  /*
    BUT... when `apiconnect-assembly` is used in production we don't know how
    everything will be structured. Probably we will live at
        "<hostname>/.../node_modules/apiconnect-assembly/src/css/material.css"
    while the font we need is in a sibling directory at:
        "<hostname>/.../node_modules/material-design-icons-iconfont/dist/fonts/blah.woff2"
    So, at Gulp build time, the URLs above will be turned into relative URLs
    which climb up to "node_modules" and then descend again.
  */
}

.material-icons {
  font-family: 'Material Icons';
  font-weight: normal;
  font-style: normal;
  font-size: 24px;  /* Preferred icon size */
  display: inline-block;
  width: 1em;
  height: 1em;
  line-height: 1;
  text-transform: none;
  letter-spacing: normal;
  word-wrap: normal;
  white-space: nowrap;
  direction: ltr;

  /* Support for all WebKit browsers. */
  -webkit-font-smoothing: antialiased;
  /* Support for Safari and Chrome. */
  text-rendering: optimizeLegibility;

  /* Support for Firefox. */
  -moz-osx-font-smoothing: grayscale;

  /* Support for IE. */
  font-feature-settings: 'liga';
}