path: root/files/ko/web/css/display/index.html

---
title: display
slug: Web/CSS/display
tags:
  - CSS
  - CSS Display
  - CSS Property
  - Reference
  - display
translation_of: Web/CSS/display
---

<div>{{CSSRef}}</div>

<p class="summary">
  <strong><code>display</code></strong> <a href="/ko/docs/Web/CSS">CSS</a> 속성은 요소를
  <a href="/ko/docs/Web/CSS/CSS_Flow_Layout">블록과 인라인</a> 요소 중 어느 쪽으로 처리할지와 함께,
  <a href="/ko/docs/Web/CSS/CSS_Flow_Layout">플로우</a>, <a href="/ko/docs/Web/CSS/CSS_Grid_Layout">그리드</a>,
  <a href="/ko/docs/Web/CSS/CSS_Flexible_Box_Layout">플렉스</a>처럼 자식 요소를 배치할 때 사용할 레이아웃을 설정합니다.
</p>

<p class="summary">
  <code>display</code> 속성은, 형식적으로는 요소의 내부와 외부 디스플레이 유형을 설정합니다. 외부 디스플레이 유형은
  플로우 레이아웃에 요소가 참여하는 방법을 나타내고, 내부 디스플레이 유형은 자식의 레이아웃 방식을 설정합니다.
  <code>display</code>의 일부 값은 자신만의 명세를 가지고 있습니다. 이 문서의 끝에서 찾을 수 있는 명세표를 참고하세요.
</p>

<h2 id="구문">구문</h2>

<p><code>display</code> 속성은 키워드 값을 사용해 지정합니다. 키워드는 6개의 카테고리로 분류할 수 있습니다.</p>

<pre>
.container {
  display: &lt;display-keyword&gt;;
}
</pre>

<h3 id="바깥쪽">바깥쪽</h3>

<dl>
  <dt>{{CSSxRef("&lt;display-outside&gt;")}}</dt>
  <dd>
    <p>
      요소의 외부 디스플레이 유형을 설정하는 키워드입니다. 외부 디스플레이 유형은 플로우 레이아웃에서 요소 자신의 역할과
      마찬가지입니다.
    </p>
    <dl>
      <dt><code>block</code></dt>
      <dd>
        <p>
          The element generates a block element box, generating line breaks both before and after the element when in
          the normal flow.
        </p>
      </dd>
      <dt><code>inline</code></dt>
      <dd>
        <p>
          The element generates one or more inline element boxes that do not generate line breaks before or after
          themselves. In normal flow, the next element will be on the same line if there is space
        </p>
      </dd>
    </dl>
  </dd>
</dl>
<div class="notecard note">
  <p>
    <strong>Note:</strong> Browsers that support the two-value syntax, on finding the outer value only, such as when
    <code>display: block</code> or <code>display: inline</code> is specified, will set the inner value to
    <code>flow</code>. This will result in expected behavior; for example, if you specify an element to be block, you
    would expect that the children of that element would participate in block and inline normal flow layout.
  </p>
</div>

<h3 id="안쪽">안쪽</h3>

<dl>
  <dt>{{CSSxRef("&lt;display-inside&gt;")}}</dt>
  <dd>
    <p>
      요소의 내부 디스플레이 유형을 설정하는 키워드입니다. 내부 디스플레이 유형은 대체 요소가 아닌 요소의 콘텐츠 서식과
      배치 방법을 나타냅니다.
    </p>
    <dl>
      <dt><code>flow</code> {{Experimental_Inline}}</dt>
      <dd>
        <p>The element lays out its contents using flow layout (block-and-inline layout).</p>
        <p>
          If its outer display type is <code>inline</code> or <code>run-in</code>, and it is participating in a block or
          inline formatting context, then it generates an inline box. Otherwise it generates a block container box.
        </p>
        <p>
          Depending on the value of other properties (such as {{CSSxRef("position")}}, {{CSSxRef("float")}}, or
          {{CSSxRef("overflow")}}) and whether it is itself participating in a block or inline formatting context, it
          either establishes a new
          <a href="/ko/docs/Web/Guide/CSS/Block_formatting_context">block formatting context</a> (BFC) for its contents
          or integrates its contents into its parent formatting context.
        </p>
      </dd>
      <dt><code>flow-root</code></dt>
      <dd>
        <p>
          The element generates a block element box that establishes a new
          <a href="/ko/docs/Web/Guide/CSS/Block_formatting_context">block formatting context</a>, defining where the
          formatting root lies.
        </p>
      </dd>
      <dt><code>table</code></dt>
      <dd>
        <p>These elements behave like HTML {{HTMLElement("table")}} elements. It defines a block-level box.</p>
      </dd>
      <dt><code>flex</code></dt>
      <dd>
        <p>
          The element behaves like a block element and lays out its content according to the
          <a href="/ko/docs/Web/CSS/CSS_Flexible_Box_Layout">flexbox model</a>.
        </p>
      </dd>
      <dt><code>grid</code></dt>
      <dd>
        <p>
          The element behaves like a block element and lays out its content according to the
          <a href="/ko/docs/Web/CSS/CSS_Grid_Layout/Basic_Concepts_of_Grid_Layout">grid model</a>.
        </p>
      </dd>
      <dt><code>ruby</code> {{Experimental_Inline}}</dt>
      <dd>
        <p>
          The element behaves like an inline element and lays out its content according to the ruby formatting model. It
          behaves like the corresponding HTML {{HTMLElement("ruby")}} elements.
        </p>
      </dd>
    </dl>
  </dd>
</dl>
<div class="notecard note">
  <p>
    <strong>Note:</strong> Browsers that support the two-value syntax, on finding the inner value only, such as when
    <code>display: flex</code> or <code>display: grid</code> is specified, will set their outer value to
    <code>block</code>. This will result in expected behavior; for example, if you specify an element to be
    <code>display: grid</code>, you would expect that the box created on the grid container would be a block-level box.
  </p>
</div>

<h3 id="리스트_아이템">리스트 아이템</h3>

<dl>
  <dt>{{cssxref("&lt;display-listitem&gt;")}}</dt>
  <dd>
    <p>요소가 콘텐츠 블록 박스를 생성하고, 리스트 아이템 인라인 박스를 분리합니다.</p>
  </dd>
</dl>
<p>
  A single value of <code>list-item</code> will cause the element to behave like a list item. This can be used together
  with {{CSSxRef("list-style-type")}} and {{CSSxRef("list-style-position")}}.
</p>
<p>
  <code>list-item</code> can also be combined with any {{CSSxRef("&lt;display-outside&gt;")}} keyword and the
  <code>flow</code> or <code>flow-root</code> {{CSSxRef("&lt;display-inside&gt;")}} keywords.
</p>
<div class="notecard note">
  <p>
    <strong>Note:</strong> In browsers that support the two-value syntax, if no inner value is specified, it will
    default to <code>flow</code>. If no outer value is specified, the principal box will have an outer display type of
    <code>block</code>.
  </p>
</div>

<h3 id="내부적">내부적</h3>

<dl>
  <dt>{{cssxref("&lt;display-internal&gt;")}}</dt>
  <dd>
    <p>
      <code>table</code>, <code>ruby</code> 등 일부 레이아웃 모델은 복잡한 내부 구조를 가지며, 자식과 자손이 채워넣을
      여러가지 역할을 지닙니다. 이 항목은 그런 특정 레이아웃 모드에서만 의미를 갖는 "내부적"인 값을 정의합니다.
    </p>
    <dl>
      <dt><code>table-row-group</code></dt>
      <dd>
        <p>These elements behave like {{HTMLElement("tbody")}} HTML elements.</p>
      </dd>
      <dt><code>table-header-group</code></dt>
      <dd>
        <p>These elements behave like {{HTMLElement("thead")}} HTML elements.</p>
      </dd>
      <dt><code>table-footer-group</code></dt>
      <dd>
        <p>These elements behave like {{HTMLElement("tfoot")}} HTML elements.</p>
      </dd>
      <dt><code>table-row</code></dt>
      <dd>
        <p>These elements behave like {{HTMLElement("tr")}} HTML elements.</p>
      </dd>
      <dt><code>table-cell</code></dt>
      <dd>
        <p>These elements behave like {{HTMLElement("td")}} HTML elements.</p>
      </dd>
      <dt><code>table-column-group</code></dt>
      <dd>
        <p>These elements behave like {{HTMLElement("colgroup")}} HTML elements.</p>
      </dd>
      <dt><code>table-column</code></dt>
      <dd>
        <p>These elements behave like {{HTMLElement("col")}} HTML elements.</p>
      </dd>
      <dt><code>table-caption</code></dt>
      <dd>
        <p>These elements behave like {{HTMLElement("caption")}} HTML elements.</p>
      </dd>
      <dt><code>ruby-base</code> {{Experimental_Inline}}</dt>
      <dd>
        <p>These elements behave like {{HTMLElement("rb")}} HTML elements.</p>
      </dd>
      <dt><code>ruby-text</code> {{Experimental_Inline}}</dt>
      <dd>
        <p>These elements behave like {{HTMLElement("rt")}} HTML elements.</p>
      </dd>
      <dt><code>ruby-base-container</code> {{Experimental_Inline}}</dt>
      <dd>
        <p>These elements behave like {{HTMLElement("rbc")}} HTML elements generated as anonymous boxes.</p>
      </dd>
      <dt><code>ruby-text-container</code> {{Experimental_Inline}}</dt>
      <dd>
        <p>These elements behave like {{HTMLElement("rtc")}} HTML elements.</p>
      </dd>
    </dl>
  </dd>
</dl>

<h3 id="박스">박스</h3>

<dl>
  <dt>{{CSSxRef("&lt;display-box&gt;")}}</dt>
  <dd>
    <p>요소의 디스플레이 박스를 생성해야 하는지 지정합니다.</p>
    <dl>
      <dt><code>contents</code></dt>
      <dd>
        <p>
          These elements don't produce a specific box by themselves. They are replaced by their pseudo-box and their
          child boxes. Please note that the CSS Display Level 3 spec defines how the <code>contents</code> value should
          affect "unusual elements" — elements that aren't rendered purely by CSS box concepts such as replaced
          elements. See
          <a href="https://drafts.csswg.org/css-display/#unbox"
            >Appendix B: Effects of display: contents on Unusual Elements</a
          >
          for more details.
        </p>
        <p>
          <em
            >Due to a bug in browsers, this will currently remove the element from the accessibility tree — screen
            readers will not look at what's inside. See the
            <a href="#accessibility_concerns">Accessibility concerns</a> section below for more details.</em
          >
        </p>
      </dd>
      <dt><code>none</code></dt>
      <dd>
        <p>
          Turns off the display of an element so that it has no effect on layout (the document is rendered as though the
          element did not exist). All descendant elements also have their display turned off. To have an element take up
          the space that it would normally take, but without actually rendering anything, use the
          {{CSSxRef("visibility")}} property instead.
        </p>
      </dd>
    </dl>
  </dd>
</dl>

<h3 id="레거시">레거시</h3>

<dl>
  <dt>{{CSSxRef("&lt;display-legacy&gt;")}}</dt>
  <dd>
    <p>
      CSS 2는 <code>display</code> 속성에 단일 키워드만 사용했으므로, 같은 레이아웃 모드를 위해 블록 레벨과 인라인 레벨
      키워드를 각각 필요로 했습니다.
    </p>
    <dl>
      <dt><code>inline-block</code></dt>
      <dd>
        <p>
          The element generates a block element box that will be flowed with surrounding content as if it were a single
          inline box (behaving much like a replaced element would).
        </p>
        <p>It is equivalent to <code>inline flow-root</code>.</p>
      </dd>
      <dt><code>inline-table</code></dt>
      <dd>
        <p>
          The <code>inline-table</code> value does not have a direct mapping in HTML. It behaves like an HTML
          {{HTMLElement("table")}} element, but as an inline box, rather than a block-level box. Inside the table box is
          a block-level context.
        </p>
        <p>It is equivalent to <code>inline table</code>.</p>
      </dd>
      <dt><code>inline-flex</code></dt>
      <dd>
        <p>The element behaves like an inline element and lays out its content according to the flexbox model.</p>
        <p>It is equivalent to <code>inline flex</code>.</p>
      </dd>
      <dt><code>inline-grid</code></dt>
      <dd>
        <p>The element behaves like an inline element and lays out its content according to the grid model.</p>
        <p>It is equivalent to <code>inline grid</code>.</p>
      </dd>
    </dl>
  </dd>
</dl>

<h3>Which syntax should you use now?</h3>
<p>
  The Level 3 specification details two values for the <code>display</code> property — enabling the specification of the
  outer and inner display type explicitly — but this is not yet well-supported by browsers.
</p>
<p>
  The <code>&#x3C;display-legacy></code> methods allow the same results with single keyword values, and should be
  favoured by developers until the two keyword values are better supported. For example, using two values you might
  specify an inline flex container as follows:
</p>
<pre class="brush: css">
.container {
  display: inline flex;
}
</pre>
<p>This can currently be specified using a single value.</p>
<pre class="brush: css">
.container {
  display: inline-flex;
}
</pre>
<p>
  For more information on these changes to the specification, see the article
  <a href="/ko/docs/Web/CSS/display/two-value_syntax_of_display">Adapting to the new two-value syntax of display</a>.
</p>
<h3>Global</h3>
<pre class="brush: css">
/* Global values */
display: inherit;
display: initial;
display: unset;
</pre>

<h2 id="안내서_및_예제">안내서 및 예제</h2>

<p>
  The individual pages for the different types of value that <code>display</code> can have set on it feature multiple
  examples of those values in action — see the {{anch("Syntax")}} section. In addition, see the following material,
  which covers the various values of display in depth.
</p>

<h3 id="CSS_Flow_Layout_display_block_display_inline">
  CSS Flow Layout (<code>display: block</code>, <code>display: inline</code>)
</h3>

<ul>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Flow_Layout/Block_and_Inline_Layout_in_Normal_Flow"
      >Block and Inline Layout in Normal Flow</a
    >
  </li>
  <li><a href="/ko/docs/Web/CSS/CSS_Flow_Layout/Flow_Layout_and_Overflow">Flow Layout and Overflow</a></li>
  <li><a href="/ko/docs/Web/CSS/CSS_Flow_Layout/Flow_Layout_and_Writing_Modes">Flow Layout and Writing Modes</a></li>
  <li><a href="/ko/docs/Web/CSS/CSS_Flow_Layout/Formatting_Contexts_Explained">Formatting Contexts Explained</a></li>
  <li><a href="/ko/docs/Web/CSS/CSS_Flow_Layout/In_Flow_and_Out_of_Flow">In Flow and Out of Flow</a></li>
</ul>

<h3 id="display_flex"><code>display: flex</code></h3>

<ul>
  <li><a href="/ko/docs/Web/CSS/CSS_Flexible_Box_Layout/Basic_Concepts_of_Flexbox">Basic concepts of flexbox</a></li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Flexible_Box_Layout/Aligning_Items_in_a_Flex_Container"
      >Aligning Items in a Flex Container</a
    >
  </li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Flexible_Box_Layout/Controlling_Ratios_of_Flex_Items_Along_the_Main_Ax"
      >Controlling Ratios of Flex Items Along the Main Axis</a
    >
  </li>
  <li><a href="/ko/docs/Web/CSS/CSS_Flexible_Box_Layout/Mixins">Cross-browser Flexbox mixins</a></li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Flexible_Box_Layout/Mastering_Wrapping_of_Flex_Items"
      >Mastering Wrapping of Flex Items</a
    >
  </li>
  <li><a href="/ko/docs/Web/CSS/CSS_Flexible_Box_Layout/Ordering_Flex_Items">Ordering Flex Items</a></li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Flexible_Box_Layout/Relationship_of_Flexbox_to_Other_Layout_Methods"
      >Relationship of flexbox to other layout methods</a
    >
  </li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Flexible_Box_Layout/Backwards_Compatibility_of_Flexbox"
      >Backwards Compatibility of Flexbox</a
    >
  </li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Flexible_Box_Layout/Typical_Use_Cases_of_Flexbox">Typical use cases of Flexbox</a>
  </li>
</ul>

<h3 id="display_grid"><code>display: grid</code></h3>

<ul>
  <li><a href="/ko/docs/Web/CSS/CSS_Grid_Layout/Basic_Concepts_of_Grid_Layout">Basic Concepts of Grid Layout</a></li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Grid_Layout/Relationship_of_Grid_Layout">Relationship to other layout methods</a>
  </li>
  <li><a href="/ko/docs/Web/CSS/CSS_Grid_Layout/Line-based_Placement_with_CSS_Grid">Line-based placement</a></li>
  <li><a href="/ko/docs/Web/CSS/CSS_Grid_Layout/Grid_Template_Areas">Grid template areas</a></li>
  <li><a href="/ko/docs/Web/CSS/CSS_Grid_Layout/Layout_using_Named_Grid_Lines">Layout using named grid lines</a></li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Grid_Layout/Auto-placement_in_CSS_Grid_Layout">Auto-placement in grid layout</a>
  </li>
  <li><a href="/ko/docs/Web/CSS/CSS_Grid_Layout/Box_Alignment_in_CSS_Grid_Layout">Box alignment in grid layout</a></li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Grid_Layout/CSS_Grid,_Logical_Values_and_Writing_Modes"
      >Grids, logical values and writing modes</a
    >
  </li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Grid_Layout/CSS_Grid_Layout_and_Accessibility">CSS Grid Layout and Accessibility</a>
  </li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Grid_Layout/CSS_Grid_and_Progressive_Enhancement"
      >CSS Grid Layout and Progressive Enhancement</a
    >
  </li>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Grid_Layout/Realizing_common_layouts_using_CSS_Grid_Layout"
      >Realizing common layouts using grids</a
    >
  </li>
</ul>

<h2 id="접근성_고려사항">접근성 고려사항</h2>

<h3 id="display_none"><code>display: none</code></h3>

<p>
  Using a <code>display</code> value of <code>none</code> on an element will remove it from the
  <a href="/ko/docs/Learn/Accessibility/What_is_accessibility#Accessibility_APIs">accessibility tree</a>. This will
  cause the element and all its descendant elements to no longer be announced by screen reading technology.
</p>

<p>
  If you want to visually hide the element, a more accessible alternative is to use
  <a class="external" href="https://gomakethings.com/hidden-content-for-better-a11y/#hiding-the-link"
    >a combination of properties</a
  >
  to remove it visually from the screen but keep it parseable by assistive technology such as screen readers.
</p>

<h3 id="display_contents"><code>display: contents</code></h3>

<p>
  Current implementations in most browsers will remove from the
  <a href="/ko/docs/Learn/Accessibility/What_is_accessibility#Accessibility_APIs">accessibility tree</a> any element
  with a <code>display</code> value of <code>contents</code> (but descendants will remain). This will cause the element
  itself to no longer be announced by screen reading technology. This is incorrect behavior according to the
  <a href="https://drafts.csswg.org/css-display/#valdef-display-contents">CSS specification</a>.
</p>

<ul>
  <li>
    <a class="external" href="https://hiddedevries.nl/en/blog/2018-04-21-more-accessible-markup-with-display-contents"
      >More accessible markup with display: contents | Hidde de Vries</a
    >
  </li>
  <li>
    <a class="external" href="http://adrianroselli.com/2018/05/display-contents-is-not-a-css-reset.html"
      >Display: Contents Is Not a CSS Reset | Adrian Roselli</a
    >
  </li>
</ul>

<h3 id="Tables">Tables</h3>

<p>
  Changing the <code>display</code> value of a {{HTMLElement("table")}} element to <code>block</code>,
  <code>grid</code>, or <code>flex</code> will alter its representation in the
  <a href="/ko/docs/Learn/Accessibility/What_is_accessibility#Accessibility_APIs">accessibility tree</a>. This will
  cause the table to no longer be announced properly by screen reading technology.
</p>

<ul>
  <li>
    <a
      class="external"
      href="https://developer.paciellogroup.com/blog/2018/03/short-note-on-what-css-display-properties-do-to-table-semantics/"
      >Short note on what CSS display properties do to table semantics — The Paciello Group</a
    >
  </li>
  <li>
    <a class="external" href="https://gomakethings.com/hidden-content-for-better-a11y/"
      >Hidden content for better a11y | Go Make Things</a
    >
  </li>
  <li>
    <a
      href="/ko/docs/Web/Accessibility/Understanding_WCAG/Perceivable#Guideline_1.3_%E2%80%94_Create_content_that_can_be_presented_in_different_ways"
      >MDN Understanding WCAG, Guideline 1.3 explanations</a
    >
  </li>
  <li>
    <a class="external" href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html"
      >Understanding Success Criterion 1.3.1 | W3C Understanding WCAG 2.0</a
    >
  </li>
</ul>

<h2 id="Specifications" name="Specifications">명세</h2>

<table class="standard-table">
  <thead>
    <tr>
      <th scope="col">Specification</th>
      <th scope="col">Status</th>
      <th scope="col">Comment</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>{{SpecName('CSS3 Display', '#the-display-properties', 'display')}}</td>
      <td>{{Spec2('CSS3 Display')}}</td>
      <td>
        Added <code>run-in</code>, <code>flow</code>, <code>flow-root</code>, <code>contents</code>, and multi-keyword
        values.
      </td>
    </tr>
    <tr>
      <td>{{SpecName('CSS3 Ruby', '#ruby-display', 'display')}}</td>
      <td>{{Spec2('CSS3 Ruby')}}</td>
      <td>
        Added <code>ruby</code>, <code>ruby-base</code>, <code>ruby-text</code>, <code>ruby-base-container</code>, and
        <code>ruby-text-container</code>.
      </td>
    </tr>
    <tr>
      <td>{{SpecName('CSS3 Grid', '#grid-containers', 'display')}}</td>
      <td>{{Spec2('CSS3 Grid')}}</td>
      <td>Added the grid box model values.</td>
    </tr>
    <tr>
      <td>{{SpecName('CSS3 Flexbox', '#flex-containers', 'display')}}</td>
      <td>{{Spec2('CSS3 Flexbox')}}</td>
      <td>Added the flexible box model values.</td>
    </tr>
    <tr>
      <td>{{SpecName('CSS2.1', 'visuren.html#display-prop', 'display')}}</td>
      <td>{{Spec2('CSS2.1')}}</td>
      <td>
        Added the table model values and <code>inline-block<em>.</em></code>
      </td>
    </tr>
    <tr>
      <td>{{SpecName('CSS1', '#display', 'display')}}</td>
      <td>{{Spec2('CSS1')}}</td>
      <td>
        Initial definition. Basic values: <code>none</code>, <code>block</code>, <code>inline</code>, and
        <code>list-item</code>.
      </td>
    </tr>
  </tbody>
</table>

<p>{{cssinfo}}</p>

<h2 id="브라우저_호환성">브라우저 호환성</h2>

<p>{{Compat("css.properties.display", 10)}}</p>

<h2 id="같이_보기">같이 보기</h2>

<ul>
  <li>
    <a href="/ko/docs/Web/CSS/CSS_Flow_Layout/Block_and_Inline_Layout_in_Normal_Flow"
      >Block and Inline Layout in Normal Flow</a
    >
  </li>
  <li><a href="/ko/docs/Web/CSS/CSS_Flow_Layout/Formatting_Contexts_Explained">Formatting contexts explained</a></li>
  <li>{{CSSxRef("visibility")}}, {{CSSxRef("float")}}, {{CSSxRef("position")}}</li>
  <li>{{CSSxRef("grid")}}, {{CSSxRef("flex")}}</li>
</ul>