section.content table td {
	display: table-cell;
	word-wrap: break-word;
	overflow-wrap: break-word;
}

section.content table .label {
	color: #fff;
}

textarea.systemInfoData {
	height: 22em;
	line-height: 1.5em;
}

.login-box {
	height: 500px;

    border-top-left-radius:...

<component name="ProjectRunConfigurationManager">
  <configuration default="false" name="Symbol Light Classes Tests" type="GradleRunConfiguration" factoryName="Gradle" folderName="Analysis">
    <ExternalSystemSettings>
      <option name="executionName" />
      <option name="externalProjectPath" value="$PROJECT_DIR$" />
      <option name="externalSystemIdString" value="GRADLE" />
      <option name="scriptParameters" value="" />
      <option name="taskDescriptions">

    font-weight: 700;
    font-style: normal
}

body, input {
    font-family: cash-market,"Helvetica Neue",helvetica,sans-serif;
}

.md-typeset h1, .md-typeset h2, .md-typeset h3, .md-typeset h4 {
    font-family: cash-market,"Helvetica Neue",helvetica,sans-serif;
    line-height: normal;
    font-weight: bold;
}

button.dl {
  font-weight: 300;
  font-size: 25px;

        height: 15px;
        font-family: Verdana, sans-serif;
        font-size: 8pt;
        font-weight: bold;
        text-decoration: none;
        color: #000000;
        background-color: #d0d0d0;
        border-top-color: #ffffff;
        border-bottom-color: #707070;
        border-right-color: #707070;
        border-left-color: #ffffff;
        border-style: solid solid;
        border-top-width: 1px;

<component name="ProjectRunConfigurationManager">
  <configuration default="false" name="Test: Commonizer / Light" type="GradleRunConfiguration" factoryName="Gradle" folderName="Tests">
    <ExternalSystemSettings>
      <option name="executionName" />
      <option name="externalProjectPath" value="$PROJECT_DIR$" />
      <option name="externalSystemIdString" value="GRADLE" />
      <option name="scriptParameters" value="" />
      <option name="taskDescriptions">

 * annotated with LargeTest.
 *
 * <p>Why use a custom annotation instead of {@code android.test.suitebuilder.annotation.Suppress}?
 * I'm not completely sure that this is the right choice, but it has various advantages:
 *
 * <ul>
 *   <li>An annotation named just "Suppress" might someday be treated by a non-Android tool as a
 *       suppression. This would follow the precedent of many of our annotation processors, which

                <mxCell id="1" parent="0"/>
                <mxCell id="2" value="" style="rounded=0;whiteSpace=wrap;html=1;fontStyle=1;strokeWidth=4;" parent="1" vertex="1">
                    <mxGeometry x="450" y="-50" width="820" height="970" as="geometry"/>
                </mxCell>

                final int width = reader.getWidth(0);
                final int height = reader.getHeight(0);
                if (width <= 0 || height <= 0) {
                    return Result.NO_IMAGE;
                }
                if (!fessConfig.validateThumbnailSize(width, height)) {
                    return Result.INVALID_SIZE;
                }

        height: 1.25
      font:
        family: *font_family
        style: Bold

  # Page description
  - size: { width: 832, height: 64 }
    offset: { x: 64, y: 512 }
    typography:
      content: *page_description
      align: start
      color: *color
      line:
        amount: 2
        height: 1.5
      font:
        family: *font_family