diff options
Diffstat (limited to 'files/ko/web')
8 files changed, 1037 insertions, 267 deletions
diff --git a/files/ko/web/css/css_transforms/using_css_transforms/index.html b/files/ko/web/css/css_transforms/using_css_transforms/index.html deleted file mode 100644 index 1c29e3b1e3..0000000000 --- a/files/ko/web/css/css_transforms/using_css_transforms/index.html +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: CSS 변형 사용하기 -slug: Web/CSS/CSS_Transforms/Using_CSS_transforms -tags: - - 3D - - Advanced - - CSS - - CSS Transforms - - Graphics - - Guide -translation_of: Web/CSS/CSS_Transforms/Using_CSS_transforms ---- -<div>{{CSSRef}}</div> - -<p><strong>CSS 변형</strong>(transform)은 좌표공간을 변형함으로써 일반적인 문서 흐름을 방해하지 않고 콘텐츠의 형태와 위치를 바꿉니다. 본 가이드는 변형 사용법의 기초를 제시합니다.</p> - -<p>CSS 변형은 HTML 요소에 선형 아핀 변형(affine linear transformation)을 적용하는 여러 개의 CSS 속성을 조합해 구현합니다. 변형은 평면과 3D 공간에서의 회전, 확대, 이동, 비틀기를 포함합니다.</p> - -<div class="warning"> -<p><a href="/ko/docs/Web/CSS/CSS_Box_Model">박스 모델</a>에 따라 배치된 요소만 <code>transform</code>을 적용할 수 있습니다. 한 가지 예를 들자면, <code>display: block</code>속성을 가진 요소는 박스 모델을 따릅니다. </p> -</div> - -<h2 id="CSS_변형_속성">CSS 변형 속성</h2> - -<p>CSS 변형을 정의할 때 중요한 두 가지 속성은 {{cssxref("transform")}}과 {{cssxref("transform-origin")}}입니다.</p> - -<dl> - <dt>{{cssxref("transform-origin")}}</dt> - <dd>원점의 위치를 지정합니다. 기본값은 요소의 중심이며 변경할 수 있습니다. 회전, 확대, 비틀기 등 하나의 점을 기준으로 하는 변형에서 사용합니다.</dd> - <dt>{{cssxref("transform")}}</dt> - <dd>요소에 적용할 변형을 지정합니다. 여러 개의 변형 목록을 공백으로 구분하여 대입하면 순차적으로 합성한 결과물을 적용합니다. 합성은 오른쪽부터 왼쪽으로 진행합니다.</dd> -</dl> - -<h2 id="예제">예제</h2> - -<p>다음 이미지는 변형하지 않은 MDN 로고입니다.</p> - -<p><img alt="MDN Logo" src="https://mdn.mozillademos.org/files/12539/Screen%20Shot%202016-02-16%20at%2015.53.54.png"></p> - -<h3 id="회전">회전</h3> - -<p>MDN 로고를 90도 회전합니다.</p> - -<pre class="brush: html notranslate"><img style="transform: rotate(90deg); - transform-origin: bottom left;" - src="https://mdn.mozillademos.org/files/12539/Screen%20Shot%202016-02-16%20at%2015.53.54.png"></pre> - -<p>{{EmbedLiveSample('회전', 'auto', 240) }}</p> - -<h3 id="비틀고_옮기기">비틀고 옮기기</h3> - -<p>MDN 로고를 10도 비틀고 X축으로 150픽셀 옮깁니다.</p> - -<pre class="brush: html notranslate"><img style="transform: skewx(10deg) translatex(150px); - transform-origin: bottom left;" - src="https://mdn.mozillademos.org/files/12539/Screen%20Shot%202016-02-16%20at%2015.53.54.png"></pre> - -<p>{{EmbedLiveSample('비틀고_옮기기') }}</p> - -<h2 id="3D_전용_CSS_속성">3D 전용 CSS 속성</h2> - -<p>3D 공간에서의 CSS 변환은 좀 더 복잡합니다. 우선 원근감을 부여해 3D 공간을 설정한 후에, 2D 요소가 그 안에서 어떻게 행동할지 설정해야 합니다..</p> - -<h3 id="원근">원근</h3> - -<p>처음으로 정할 항목은 {{cssxref("perspective")}}입니다. 우리가 입체라고 느낄 수 있는 건 원근감 덕분입니다. 요소가 관찰자에서 멀어질 수록 더 작게 보입니다.</p> - -<p>{{page("/ko/docs/Web/CSS/perspective", "Setting perspective", 0, 0, 3)}}</p> - -<p>다음으로는 {{cssxref("perspective-origin")}} 속성으로 관찰자의 위치를 정해야 합니다. 기본값은 중앙으로, 언제나 충분한 위치는 아닙니다.</p> - -<p>{{page("/ko/docs/Web/CSS/perspective-origin", "Changing the perspective origin", 0, 0, 3)}}</p> - -<p>모든 과정을 마쳤다면 3D 공간의 요소를 작업할 수 있습니다.</p> - -<h2 id="더_보기">더 보기</h2> - -<ul> - <li><a href="/en-US/docs/Web/Guide/Events/Using_device_orientation_with_3D_transforms" title="Using Deviceorientation In 3D Transforms">Using device orientation with 3D Transforms</a></li> -</ul> diff --git a/files/ko/web/css/css_transforms/using_css_transforms/index.md b/files/ko/web/css/css_transforms/using_css_transforms/index.md new file mode 100644 index 0000000000..fb163d5113 --- /dev/null +++ b/files/ko/web/css/css_transforms/using_css_transforms/index.md @@ -0,0 +1,541 @@ +--- +title: CSS 변형 사용하기 +slug: Web/CSS/CSS_Transforms/Using_CSS_transforms +tags: + - 3D + - Advanced + - CSS + - CSS Transforms + - Graphics + - Guide +translation_of: Web/CSS/CSS_Transforms/Using_CSS_transforms +--- +{{CSSRef}} + +**CSS 변형**(transform)은 좌표공간을 변형함으로써 일반적인 문서 흐름을 방해하지 않고 콘텐츠의 형태와 위치를 바꿉니다. 본 가이드는 변형 사용법의 기초를 제시합니다. + +CSS 변형은 HTML 요소에 선형 아핀 변형(affine linear transformation)을 적용하는 여러 개의 CSS 속성을 조합해 구현합니다. 변형은 평면과 3D 공간에서의 회전, 확대, 이동, 비틀기를 포함합니다. + +> **경고:** [박스 모델](/ko/docs/Web/CSS/CSS_Box_Model)에 따라 배치된 요소만 `transform`을 적용할 수 있습니다. 한 가지 예를 들자면, `display: block` 속성을 가진 요소는 박스 모델을 따릅니다. + +## CSS 변형 속성 + +CSS 변형을 정의할 때 중요한 두 가지 속성은 {{cssxref("transform")}}과 {{cssxref("transform-origin")}}입니다. + +- {{cssxref("transform-origin")}} + - : 원점의 위치를 지정합니다. 기본값은 요소의 중심이며 변경할 수 있습니다. 회전, 확대, 비틀기 등 하나의 점을 기준으로 하는 변형에서 사용합니다. +- {{cssxref("transform")}} + - : 요소에 적용할 변형을 지정합니다. 여러 개의 변형 목록을 공백으로 구분하여 대입하면 순차적으로 합성한 결과물을 적용합니다. 합성은 오른쪽부터 왼쪽으로 진행합니다. + +## 예제 + +다음 이미지는 변형하지 않은 MDN 로고입니다. + +![MDN Logo](https://mdn.mozillademos.org/files/12539/Screen%20Shot%202016-02-16%20at%2015.53.54.png) + +### 회전 + +MDN 로고를 90도 회전합니다. + +```html +<img style="transform: rotate(90deg); + transform-origin: bottom left;" + src="https://mdn.mozillademos.org/files/12539/Screen%20Shot%202016-02-16%20at%2015.53.54.png"> +``` + +{{EmbedLiveSample('회전', 'auto', 240) }} + +### 비틀고 옮기기 + +MDN 로고를 10도 비틀고 X축으로 150픽셀 옮깁니다. + +```html +<img style="transform: skewx(10deg) translatex(150px); + transform-origin: bottom left;" + src="https://mdn.mozillademos.org/files/12539/Screen%20Shot%202016-02-16%20at%2015.53.54.png"> +``` + +{{EmbedLiveSample('비틀고_옮기기') }} + +## 3D 전용 CSS 속성 + +3D 공간에서의 CSS 변환은 좀 더 복잡합니다. 우선 원근감을 부여해 3D 공간을 설정한 후에, 2D 요소가 그 안에서 어떻게 행동할지 설정해야 합니다.. + +### 원근 + +처음으로 정할 항목은 {{cssxref("perspective")}}입니다. 우리가 입체라고 느낄 수 있는 건 원근감 덕분입니다. 요소가 관찰자에서 멀어질 수록 더 작게 보입니다. + +#### Setting perspective + +This example shows a cube with the perspective set at different positions. How quick the cube shrinks is defined by the {{ cssxref("perspective") }} property. The smaller its value is, the deeper the perspective is. + +##### HTML + +The HTML below creates four copies of the same box, with the perspective set at different values. + +```html +<table> + <tbody> + <tr> + <th><code>perspective: 250px;</code> + </th> + <th><code>perspective: 350px;</code> + </th> + </tr> + <tr> + <td> + <div class="container"> + <div class="cube pers250"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> + </td> + <td> + <div class="container"> + <div class="cube pers350"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> + </td> + </tr> + <tr> + <th><code>perspective: 500px;</code> + </th> + <th><code>perspective: 650px;</code> + </th> + </tr> + <tr> + <td> + <div class="container"> + <div class="cube pers500"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> + </td> + <td> + <div class="container"> + <div class="cube pers650"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> + </td> + </tr> + </tbody> +</table> +``` + +##### CSS + +The CSS establishes classes that can be used to set the perspective to different distances. It also includes classes for the container box and the cube itself, as well as each of its faces. + +```css +/* Shorthand classes for different perspective values */ +.pers250 { + perspective: 250px; +} + +.pers350 { + perspective: 350px; +} + +.pers500 { + perspective: 500px; +} + +.pers650 { + perspective: 650px; +} + +/* Define the container div, the cube div, and a generic face */ +.container { + width: 200px; + height: 200px; + margin: 75px 0 0 75px; + border: none; +} + +.cube { + width: 100%; + height: 100%; + backface-visibility: visible; + perspective-origin: 150% 150%; + transform-style: preserve-3d; +} + +.face { + display: block; + position: absolute; + width: 100px; + height: 100px; + border: none; + line-height: 100px; + font-family: sans-serif; + font-size: 60px; + color: white; + text-align: center; +} + +/* Define each face based on direction */ +.front { + background: rgba(0, 0, 0, 0.3); + transform: translateZ(50px); +} + +.back { + background: rgba(0, 255, 0, 1); + color: black; + transform: rotateY(180deg) translateZ(50px); +} + +.right { + background: rgba(196, 0, 0, 0.7); + transform: rotateY(90deg) translateZ(50px); +} + +.left { + background: rgba(0, 0, 196, 0.7); + transform: rotateY(-90deg) translateZ(50px); +} + +.top { + background: rgba(196, 196, 0, 0.7); + transform: rotateX(90deg) translateZ(50px); +} + +.bottom { + background: rgba(196, 0, 196, 0.7); + transform: rotateX(-90deg) translateZ(50px); +} + +/* Make the table a little nicer */ +th, p, td { + background-color: #EEEEEE; + padding: 10px; + font-family: sans-serif; + text-align: left; +} +``` + +##### Result + +{{EmbedLiveSample('Setting_perspective', 660, 700)}} + +다음으로는 {{cssxref("perspective-origin")}} 속성으로 관찰자의 위치를 정해야 합니다. 기본값은 중앙으로, 언제나 충분한 위치는 아닙니다. + +#### Changing the perspective origin + +This example shows cubes with popular `perspective-origin` values. + +##### HTML + +```html +<section> + +<figure> + <figcaption><code>perspective-origin: top left;</code></figcaption> + <div class="container"> + <div class="cube potl"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +<figure> + <figcaption><code>perspective-origin: top;</code></figcaption> + <div class="container"> + <div class="cube potm"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +<figure> + <figcaption><code>perspective-origin: top right;</code></figcaption> + <div class="container"> + <div class="cube potr"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +<figure> + <figcaption><code>perspective-origin: left;</code></figcaption> + <div class="container"> + <div class="cube poml"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +<figure> + <figcaption><code>perspective-origin: 50% 50%;</code></figcaption> + <div class="container"> + <div class="cube pomm"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +<figure> + <figcaption><code>perspective-origin: right;</code></figcaption> + <div class="container"> + <div class="cube pomr"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +<figure> + <figcaption><code>perspective-origin: bottom left;</code></figcaption> + <div class="container"> + <div class="cube pobl"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +<figure> + <figcaption><code>perspective-origin: bottom;</code></figcaption> + <div class="container"> + <div class="cube pobm"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +<figure> + <figcaption><code>perspective-origin: bottom right;</code></figcaption> + <div class="container"> + <div class="cube pobr"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +<figure> + <figcaption><code>perspective-origin: -200% -200%;</code></figcaption> + <div class="container"> + <div class="cube po200200neg"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +<figure> + <figcaption><code>perspective-origin: 200% 200%;</code></figcaption> + <div class="container"> + <div class="cube po200200pos"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +<figure> + <figcaption><code>perspective-origin: 200% -200%;</code></figcaption> + <div class="container"> + <div class="cube po200200"> + <div class="face front">1</div> + <div class="face back">2</div> + <div class="face right">3</div> + <div class="face left">4</div> + <div class="face top">5</div> + <div class="face bottom">6</div> + </div> + </div> +</figure> + +</section> +``` + +##### CSS + +```css +/* perspective-origin values (unique per example) */ +.potl { + perspective-origin: top left; +} +.potm { + perspective-origin: top; +} +.potr { + perspective-origin: top right; +} +.poml { + perspective-origin: left; +} +.pomm { + perspective-origin: 50% 50%; +} +.pomr { + perspective-origin: right; +} +.pobl { + perspective-origin: bottom left; +} +.pobm { + perspective-origin: bottom; +} +.pobr { + perspective-origin: bottom right; +} +.po200200neg { + perspective-origin: -200% -200%; +} +.po200200pos { + perspective-origin: 200% 200%; +} +.po200200 { + perspective-origin: 200% -200%; +} + +/* Define the container div, the cube div, and a generic face */ +.container { + width: 100px; + height: 100px; + margin: 24px; + border: none; +} + +.cube { + width: 100%; + height: 100%; + backface-visibility: visible; + perspective: 300px; + transform-style: preserve-3d; +} + +.face { + display: block; + position: absolute; + width: 100px; + height: 100px; + border: none; + line-height: 100px; + font-family: sans-serif; + font-size: 60px; + color: white; + text-align: center; +} + +/* Define each face based on direction */ +.front { + background: rgba(0, 0, 0, 0.3); + transform: translateZ(50px); +} +.back { + background: rgba(0, 255, 0, 1); + color: black; + transform: rotateY(180deg) translateZ(50px); +} +.right { + background: rgba(196, 0, 0, 0.7); + transform: rotateY(90deg) translateZ(50px); +} +.left { + background: rgba(0, 0, 196, 0.7); + transform: rotateY(-90deg) translateZ(50px); +} +.top { + background: rgba(196, 196, 0, 0.7); + transform: rotateX(90deg) translateZ(50px); +} +.bottom { + background: rgba(196, 0, 196, 0.7); + transform: rotateX(-90deg) translateZ(50px); +} + +/* Make the layout a little nicer */ +section { + background-color: #EEE; + padding: 10px; + font-family: sans-serif; + text-align: left; + display: grid; + grid-template-columns: repeat(3, 1fr); +} +``` + +##### Result + +{{EmbedLiveSample('Changing_the_perspective_origin', '100%', 700)}} + +모든 과정을 마쳤다면 3D 공간의 요소를 작업할 수 있습니다. + +## 더 보기 + +- [Using device orientation with 3D Transforms](/en-US/docs/Web/Guide/Events/Using_device_orientation_with_3D_transforms "Using Deviceorientation In 3D Transforms") diff --git a/files/ko/web/css/display/index.html b/files/ko/web/css/display/index.html index 73a6545e54..41ebe49019 100644 --- a/files/ko/web/css/display/index.html +++ b/files/ko/web/css/display/index.html @@ -9,17 +9,28 @@ tags: - 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"> + <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> +<p class="summary"> + <code>display</code> 속성은, 형식적으로는 요소의 내부와 외부 디스플레이 유형을 설정합니다. 외부 디스플레이 유형은 + 플로우 레이아웃에 요소가 참여하는 방법을 나타내고, 내부 디스플레이 유형은 자식의 레이아웃 방식을 설정합니다. + <code>display</code>의 일부 값은 자신만의 명세를 가지고 있습니다. 이 문서의 끝에서 찾을 수 있는 명세표를 참고하세요. +</p> <h2 id="구문">구문</h2> <p><code>display</code> 속성은 키워드 값을 사용해 지정합니다. 키워드는 6개의 카테고리로 분류할 수 있습니다.</p> -<pre>.container { +<pre> +.container { display: <display-keyword>; } </pre> @@ -27,193 +38,532 @@ translation_of: Web/CSS/display <h3 id="바깥쪽">바깥쪽</h3> <dl> - <dt>{{CSSxRef("<display-outside>")}}</dt> - <dd>요소의 외부 디스플레이 유형을 설정하는 키워드입니다. 외부 디스플레이 유형은 플로우 레이아웃에서 요소 자신의 역할과 마찬가지입니다.</dd> + <dt>{{CSSxRef("<display-outside>")}}</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> - -<p>{{page("/ko/docs/Web/CSS/display-outside", "Syntax")}}</p> +<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("<display-inside>")}}</dt> - <dd>요소의 내부 디스플레이 유형을 설정하는 키워드입니다. 내부 디스플레이 유형은 대체 요소가 아닌 요소의 콘텐츠 서식과 배치 방법을 나타냅니다.</dd> + <dt>{{CSSxRef("<display-inside>")}}</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> - -<p>{{page("/ko/docs/Web/CSS/display-inside", "Syntax")}}</p> +<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("<display-listitem>")}}</dt> - <dd>요소가 콘텐츠 블록 박스를 생성하고, 리스트 아이템 인라인 박스를 분리합니다.</dd> + <dt>{{cssxref("<display-listitem>")}}</dt> + <dd> + <p>요소가 콘텐츠 블록 박스를 생성하고, 리스트 아이템 인라인 박스를 분리합니다.</p> + </dd> </dl> - -<p>{{page("/ko/docs/Web/CSS/display-listitem", "Syntax")}}</p> +<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("<display-outside>")}} keyword and the + <code>flow</code> or <code>flow-root</code> {{CSSxRef("<display-inside>")}} 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("<display-internal>")}}</dt> - <dd><code>table</code>, <code>ruby</code> 등 일부 레이아웃 모델은 복잡한 내부 구조를 가지며, 자식과 자손이 채워넣을 여러가지 역할을 지닙니다. 이 항목은 그런 특정 레이아웃 모드에서만 의미를 갖는 "내부적"인 값을 정의합니다.</dd> + <dt>{{cssxref("<display-internal>")}}</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> -<p>{{page("/ko/docs/Web/CSS/display-internal", "Syntax")}}</p> - <h3 id="박스">박스</h3> <dl> - <dt>{{CSSxRef("<display-box>")}}</dt> - <dd>요소의 디스플레이 박스를 생성해야 하는지 지정합니다.</dd> + <dt>{{CSSxRef("<display-box>")}}</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> -<p>{{page("/ko/docs/Web/CSS/display-box", "Syntax")}}</p> - <h3 id="레거시">레거시</h3> <dl> - <dt>{{CSSxRef("<display-legacy>")}}</dt> - <dd>CSS 2는 <code>display</code> 속성에 단일 키워드만 사용했으므로, 같은 레이아웃 모드를 위해 블록 레벨과 인라인 레벨 키워드를 각각 필요로 했습니다.</dd> + <dt>{{CSSxRef("<display-legacy>")}}</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> -<p>{{page("/ko/docs/Web/CSS/display-legacy", "Syntax")}}</p> - -<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 display-legacy 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 { +<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><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> - +} +</pre> <p>This can currently be specified using a single value.</p> - -<pre class="brush: css">.container { +<pre class="brush: css"> +.container { display: inline-flex; } </pre> - -<h3 id="전역">전역</h3> - -<pre class="brush: css">display: inherit; +<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> +<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> +<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="/en-US/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="/en-US/docs/Web/CSS/CSS_Flow_Layout/Flow_Layout_and_Overflow">Flow Layout and Overflow</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Flow_Layout/Flow_Layout_and_Writing_Modes">Flow Layout and Writing Modes</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Flow_Layout/Formatting_Contexts_Explained">Formatting Contexts Explained</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Flow_Layout/In_Flow_and_Out_of_Flow">In Flow and Out of Flow</a></li> + <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="/en-US/docs/Web/CSS/CSS_Flexible_Box_Layout/Basic_Concepts_of_Flexbox">Basic concepts of flexbox</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Flexible_Box_Layout/Aligning_Items_in_a_Flex_Container">Aligning Items in a Flex Container</a></li> - <li><a href="/en-US/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="/en-US/docs/Web/CSS/CSS_Flexible_Box_Layout/Mixins">Cross-browser Flexbox mixins</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Flexible_Box_Layout/Mastering_Wrapping_of_Flex_Items">Mastering Wrapping of Flex Items</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Flexible_Box_Layout/Ordering_Flex_Items">Ordering Flex Items</a></li> - <li><a href="/en-US/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="/en-US/docs/Web/CSS/CSS_Flexible_Box_Layout/Backwards_Compatibility_of_Flexbox">Backwards Compatibility of Flexbox</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Flexible_Box_Layout/Typical_Use_Cases_of_Flexbox">Typical use cases of Flexbox</a></li> + <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="/en-US/docs/Web/CSS/CSS_Grid_Layout/Basic_Concepts_of_Grid_Layout">Basic Concepts of Grid Layout</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Grid_Layout/Relationship_of_Grid_Layout">Relationship to other layout methods</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Grid_Layout/Line-based_Placement_with_CSS_Grid">Line-based placement</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Grid_Layout/Grid_Template_Areas">Grid template areas</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Grid_Layout/Layout_using_Named_Grid_Lines">Layout using named grid lines</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Grid_Layout/Auto-placement_in_CSS_Grid_Layout">Auto-placement in grid layout</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Grid_Layout/Box_Alignment_in_CSS_Grid_Layout">Box alignment in grid layout</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Grid_Layout/CSS_Grid,_Logical_Values_and_Writing_Modes">Grids, logical values and writing modes</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Grid_Layout/CSS_Grid_Layout_and_Accessibility">CSS Grid Layout and Accessibility</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Grid_Layout/CSS_Grid_and_Progressive_Enhancement">CSS Grid Layout and Progressive Enhancement</a></li> - <li><a href="/en-US/docs/Web/CSS/CSS_Grid_Layout/Realizing_common_layouts_using_CSS_Grid_Layout">Realizing common layouts using grids</a></li> + <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="/en-US/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> + 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> +<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="/en-US/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> +<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> + <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="/en-US/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> +<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="/en-US/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> + <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> + <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> @@ -225,8 +575,12 @@ display: unset; <h2 id="같이_보기">같이 보기</h2> <ul> - <li><a href="/en-US/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="/en-US/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> + <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> diff --git a/files/ko/web/html/element/input/date/index.html b/files/ko/web/html/element/input/date/index.html index 8a40c3cc75..79fae01f34 100644 --- a/files/ko/web/html/element/input/date/index.html +++ b/files/ko/web/html/element/input/date/index.html @@ -124,11 +124,17 @@ console.log(dateControl.valueAsNumber); // prints 1496275200000, a UNIX timestam <h3 id="htmlattrdefstep">{{htmlattrdef("step")}}</h3> -<p>{{page("/en-US/docs/Web/HTML/Element/input/number", "step-include")}}</p> +<p>The <code>step</code> attribute is a number that specifies the granularity that the value must adhere to, or the special value <code>any</code>, which is described below. Only values which are equal to the basis for stepping (<code>{{anch("min")}}</code> if specified, {{htmlattrxref("value", "input")}} otherwise, and an appropriate default value if neither of those is provided) are valid.</p> + +<p>A string value of <code>any</code> means that no stepping is implied, and any value is allowed (barring other constraints, such as <code>{{anch("min")}}</code> and <code>{{anch("max")}}</code>).</p> + +<div class="note notecard"> +<p><strong>참고:</strong> When the data entered by the user doesn't adhere to the stepping configuration, the {{Glossary("user agent")}} may round to the nearest valid value, preferring numbers in the positive direction when there are two equally close options.</p> +</div> <p><code>date</code> 입력 칸의 <code>step</code> 값은 날짜 단위, 즉 밀리초 단위로 86,400,000 ✕ <code>step</code>로 처리합니다. 기본값은 1로, 하루를 나타냅니다.</p> -<div class="blockIndicator note"> +<div class="note notecard"> <p><strong>참고:</strong> <code>date</code> 입력 칸에서 <code>step</code>의 값으로 <code>any</code>를 지정하면 <code>1</code>과 같습니다.</p> </div> diff --git a/files/ko/web/html/element/input/index.html b/files/ko/web/html/element/input/index.html index 8ff435e12d..aae4e879d9 100644 --- a/files/ko/web/html/element/input/index.html +++ b/files/ko/web/html/element/input/index.html @@ -756,60 +756,6 @@ let hatSize = form.elements["hat-size"]; </dd> </dl> -<h3 id="Non-standard_attributes">Non-standard attributes</h3> - -<p>The following non-standard attributes are also available on some browsers. As a general rule, you should avoid using them unless it can't be helped.</p> - -<table class="standard-table"> - <thead> - <tr> - <th scope="col">Attribute</th> - <th scope="col">Description</th> - </tr> - </thead> - <tbody> - <tr> - <td><code>{{anch("autocorrect")}}</code></td> - <td>A string indicating whether or not autocorrect is <code>on</code> or <code>off</code>. <strong>Safari only.</strong></td> - </tr> - <tr> - <td><code>{{anch("incremental")}}</code></td> - <td>Whether or not to send repeated {{event("search")}} events to allow updating live search results while the user is still editing the value of the field. <strong>WebKit and Blink only (Safari, Chrome, Opera, etc.).</strong></td> - </tr> - <tr> - <td><code>{{anch("mozactionhint")}}</code></td> - <td>A string indicating the type of action that will be taken when the user presses the <kbd>Enter</kbd> or <kbd>Return</kbd> key while editing the field; this is used to determine an appropriate label for that key on a virtual keyboard. <strong>Firefox for Android only.</strong></td> - </tr> - <tr> - <td><code>{{anch("orient")}}</code></td> - <td>Sets the orientation of the range slider. <strong>Firefox only.</strong></td> - </tr> - <tr> - <td><code>{{anch("results")}}</code></td> - <td>The maximum number of items that should be displayed in the drop-down list of previous search queries. <strong>Safari only.</strong></td> - </tr> - <tr> - <td><code>{{anch("webkitdirectory")}}</code></td> - <td>A Boolean indicating whether or not to only allow the user to choose a directory (or directories, if <code>{{anch("multiple")}}</code> is also present)</td> - </tr> - </tbody> -</table> - -<dl> - <dt>{{htmlattrdef("autocorrect")}} {{non-standard_inline}}</dt> - <dd>{{page("/en-US/docs/Web/HTML/Element/input/text", "autocorrect-include")}}</dd> - <dt>{{htmlattrdef("incremental")}} {{non-standard_inline}}</dt> - <dd>{{page("/en-US/docs/Web/HTML/Element/input/search", "incremental-include")}}</dd> - <dt>{{htmlattrdef("mozactionhint")}} {{non-standard_inline}}</dt> - <dd>{{page("/en-US/docs/Web/HTML/Element/input/text", "mozactionhint-include")}}</dd> - <dt>{{htmlattrdef("orient")}} {{non-standard_inline}}</dt> - <dd>{{page("/en-US/docs/Web/HTML/Element/input/range", "orient-include")}}</dd> - <dt>{{htmlattrdef("results")}} {{non-standard_inline}}</dt> - <dd>{{page("/en-US/docs/Web/HTML/Element/input/search", "results-include")}}</dd> - <dt>{{htmlattrdef("webkitdirectory")}} {{non-standard_inline}}</dt> - <dd>{{page("/en-US/docs/Web/HTML/Element/input/file", "webkitdirectory-include")}}</dd> -</dl> - <h2 id="예제">예제</h2> <h3 id="A_simple_input_box">A simple input box</h3> diff --git a/files/ko/web/html/element/track/index.html b/files/ko/web/html/element/track/index.html index 9ac120629d..cb391ba9f6 100644 --- a/files/ko/web/html/element/track/index.html +++ b/files/ko/web/html/element/track/index.html @@ -107,11 +107,15 @@ translation_of: Web/HTML/Element/track <p>미디어 요소는 동일한 <code>kind</code>, <code>srclang</code>, <code>label</code>을 가진 <code><track></code>을 하나보다 많이 포함할 수 없습니다.</p> -<div class="hidden"> -<h3 id="Detecting_cue_changes">Detecting cue changes</h3> - -<p>{{page("/en-US/docs/Web/API/TextTrack/cuechange_event", "On the track element")}}</p> -</div> +<h3 id="detecting_cue_changes">Detecting cue changes</h3> +<p>The underlying {{domxref("TextTrack")}}, indicated by the {{domxref("HTMLTrackElement.track", "track")}} property, receives a <code>cuechange</code> event every time the currently-presented cue is changed. This happens even if the track isn't associated with a media element.</p> +<p>If the track <em>is</em> associated with a media element, using the {{HTMLElement("track")}} element as a child of the {{HTMLElement("audio")}} or {{HTMLElement("video")}} element, the <code>cuechange</code> event is also sent to the {{domxref("HTMLTrackElement")}}.</p> +<pre class="brush: js">let textTrackElem = document.getElementById("texttrack"); + +textTrackElem.addEventListener("cuechange", event => { + let cues = event.target.track.activeCues; +}); +</pre> <h2 id="예제">예제</h2> diff --git a/files/ko/web/http/headers/content-security-policy/img-src/index.html b/files/ko/web/http/headers/content-security-policy/img-src/index.html index 6bd205e5f4..c9c47fa769 100644 --- a/files/ko/web/http/headers/content-security-policy/img-src/index.html +++ b/files/ko/web/http/headers/content-security-policy/img-src/index.html @@ -34,7 +34,9 @@ Content-Security-Policy: img-src <source> <source>; <h3 id="Sources">Sources</h3> -<p>{{page("Web/HTTP/Headers/Content-Security-Policy/default-src", "Sources")}}</p> +<p><code><source></code> can be any one of the values listed in <a href="/ko/docs/Web/HTTP/Headers/Content-Security-Policy/Sources#sources">CSP Source Values</a>.</p> + +<p>Note that this same set of values can be used in all {{Glossary("fetch directive", "fetch directives")}} (and a <a href="/ko/docs/Web/HTTP/Headers/Content-Security-Policy/Sources#relevant_directives">number of other directives</a>).</p> <h2 id="Examples">Examples</h2> diff --git a/files/ko/web/http/headers/content-security-policy/script-src/index.html b/files/ko/web/http/headers/content-security-policy/script-src/index.html index 766043ee67..9cfba52f56 100644 --- a/files/ko/web/http/headers/content-security-policy/script-src/index.html +++ b/files/ko/web/http/headers/content-security-policy/script-src/index.html @@ -34,12 +34,9 @@ Content-Security-Policy: script-src <source> <source>; <h3 id="Sources">Sources</h3> -<p>{{page("Web/HTTP/Headers/Content-Security-Policy/default-src", "Sources")}}</p> +<p><code><source></code> can be any one of the values listed in <a href="/ko/docs/Web/HTTP/Headers/Content-Security-Policy/Sources#sources">CSP Source Values</a>.</p> -<dl> - <dt>'report-sample'</dt> - <dd> Report에 위반 코드 샘플을 포함시키려면 이 항목을 추가 해야 합니다.</dd> -</dl> +<p>Note that this same set of values can be used in all {{Glossary("fetch directive", "fetch directives")}} (and a <a href="/ko/docs/Web/HTTP/Headers/Content-Security-Policy/Sources#relevant_directives">number of other directives</a>).</p> <h2 id="예제">예제</h2> |