Skip to content

Commit 06ef06b

Browse files
committed
removing more stuff, updating hyphenation
1 parent 122a411 commit 06ef06b

File tree

1 file changed

+7
-199
lines changed

1 file changed

+7
-199
lines changed

css3-gcpm/Overview.src.html

Lines changed: 7 additions & 199 deletions
Original file line numberDiff line numberDiff line change
@@ -1212,12 +1212,11 @@ <h2>Sidenotes</h2>
12121212
footnote/sidenote, or are two "magic" areas enough?
12131213
-->
12141214

1215-
<h2>Border parts</h2>
1215+
<h2>Clipping borders</h2>
12161216

12171217
<p>CSS borders traditionally cover an entire border edge. Sometimes,
12181218
however, it can be useful to hide some parts of the border.
12191219

1220-
12211220
<h3>The 'border-clip' properties</h3>
12221221

12231222
<table class=propdef>
@@ -1607,199 +1606,6 @@ <h3>The 'border-clip' properties</h3>
16071606

16081607

16091608

1610-
<!--
1611-
1612-
<div class="example">
1613-
1614-
<p>Consider this code:
1615-
1616-
<pre>
1617-
border-clip-top: 10px 5px repeat(5px 5px) 10px;
1618-
<pre>
1619-
1620-
<p>If top border of an element is 44px long, the parts will be as follows:
1621-
1622-
<table>
1623-
<tr><td>specified<td>absolute<td>visible?
1624-
<tr><td>10px<td>10px<td>yes
1625-
<tr><td>1fr<td>2px<td>no
1626-
<tr><td>5px<td>5px<td>yes
1627-
<tr><td>5px<td>5px<td>no
1628-
<tr><td>0<td>0px<td>no
1629-
<tr><td>1fr<td>2px<td>no
1630-
<tr><td>10px<td>10px<td>yes
1631-
</table>
1632-
1633-
</div>
1634-
1635-
-->
1636-
1637-
1638-
1639-
<h2>Pulling elements: the ''target-pull()'' value</h2>
1640-
1641-
<p>In order to move an element from one place in the presentation to
1642-
another, the ''target-pull()'' value is introduced on the 'content'
1643-
property. The value uses a functional notation and takes a URI value
1644-
as argument. In combination with the 'content' property, target
1645-
elements can be pulled to the anchor element. The content of the
1646-
anchor element is lost. The target element is only moved in the
1647-
presentation of the document and not in the structure of the document.
1648-
1649-
<div class="example">
1650-
<p>Consider this code:
1651-
1652-
<pre>
1653-
&lt;style>
1654-
@media print {
1655-
.footnote {
1656-
float: footnote;
1657-
content: target-pull(attr(href, url)) }
1658-
.footnote::footnote-call { content: counter(footnote, super-decimal) }
1659-
.footnote::footnote-marker { content: counter(footnote, super-decimal) }
1660-
.marker { display: none }
1661-
}
1662-
&lt;/style>
1663-
...
1664-
&lt;p>A sentence consists of words&lt;a class="footnote" href="#words"> [3]&lt;/a>.&lt;/p>
1665-
...
1666-
&lt;p id="words">&lt;span class="marker">[3]&lt;/span> Most often.&lt;/p>
1667-
</pre>
1668-
1669-
<p>As a result of the ''target-pull()'' value, the last <code>p</code> element is moved from its normal place of presentation and into the footnote.
1670-
1671-
</div>
1672-
1673-
1674-
1675-
<h2>Pushing elements: named flows</h2>
1676-
1677-
<p>Footnotes and running elements are print-specific conventions that
1678-
move content from one place to another in the presentation of a
1679-
document. In this section, a generic mechanism for moving content is
1680-
described: <em>named flows</em> make it possible to push elements from
1681-
one place in the presentation to another. Different from footnotes,
1682-
named flows are not counted by default. Also, while UAs are allowed to
1683-
employ certain heuristics when formatting footnotes, this is not the
1684-
case for named flows.
1685-
1686-
<p>Named flows introduce two new values:
1687-
1688-
<ol>
1689-
1690-
<li>On the 'float' property, ''to()'' is introduced to indicate that
1691-
the element should be pushed from its natural position in the
1692-
presentation and into a named flow.
1693-
1694-
<li>On the 'content' property, ''from()'' is introduced to indicate
1695-
that a named flow should be emptied and that the emptied elements
1696-
should become the content of the element. The ''from()'' value cannot
1697-
be combined with any other values.
1698-
1699-
</ol>
1700-
1701-
<p>Elements that are moved into a new flow are removed from their
1702-
current position to where ''from()'' has been set. Elements that are
1703-
moved into a named flow are only displayed once.
1704-
1705-
<div class="example">
1706-
<p>Named flows can be used to create endnotes:
1707-
1708-
<pre>
1709-
.note {
1710-
float: to(endnote);
1711-
}
1712-
div.chapter::after { content: from(endnote) }
1713-
</pre>
1714-
</div>
1715-
1716-
1717-
<div class="example">
1718-
<p>Consider this markup:
1719-
1720-
<pre>
1721-
&lt;contrib contrib-type="author">
1722-
&lt;name>
1723-
&lt;surname>Knuth&lt;/surname>
1724-
&lt;given-names>Donald E.&lt;/given-names>
1725-
&lt;/name>
1726-
&lt;role>professor&lt;/role>
1727-
&lt;/contrib>
1728-
</pre>
1729-
1730-
<p>combined with this style sheet:
1731-
1732-
<pre>
1733-
surname { float: to(lastname) }
1734-
given-names::after { content: from(lastname) }
1735-
role::before { content: ", " }
1736-
</pre>
1737-
1738-
will result in this presentation:
1739-
1740-
<pre>
1741-
Donald E. Knuth, professor
1742-
</pre>
1743-
1744-
</div>
1745-
1746-
<p>Just like footnotes, elements in named flows can have
1747-
<em>call</em> and <em>marker</em> pseudo-elements. However, these
1748-
pseudo-elements are not shown by default.
1749-
1750-
<div class="example">
1751-
<p>Notes inside tables can be moved to after the table by way of a
1752-
named flow.
1753-
1754-
<pre>
1755-
table .note { float: to(tablenote); counter-increment: tablenotes }
1756-
table .note::note-marker { content: counter(tablenotes, super-decimal) }
1757-
table .note::note-call { content: counter(tablenotes, super-decimal) }
1758-
table::after { content: from(tablenote) }
1759-
</pre>
1760-
1761-
<p class=issue>How does one remove identical table notes?
1762-
1763-
</div>
1764-
1765-
<p>If a named flow isn't emptied, its content is lost.
1766-
1767-
<div class="example">
1768-
<p>Consider this code:
1769-
1770-
<pre>
1771-
.remove { to(dev-null) }
1772-
</pre>
1773-
1774-
<p>If there is no corresponding ''from(dev-null)'' value, elements with class names "remove" are not displayed. The effect is identical to this code:
1775-
1776-
<pre>
1777-
.remove { display: none }
1778-
</pre>
1779-
</div>
1780-
1781-
<div class="example">
1782-
<p>Named flows can be used to create sidenotes. In this example, notes
1783-
are floated into margin boxes in the outside margins:
1784-
1785-
<pre>
1786-
.note {
1787-
float: to(sidenote);
1788-
}
1789-
@page :left {
1790-
@left-bottom {
1791-
content: from(sidenote);
1792-
}
1793-
}
1794-
@page :right {
1795-
@right-bottom {
1796-
content: from(sidenote);
1797-
}
1798-
}
1799-
</pre>
1800-
1801-
</div>
1802-
18031609

18041610
<h2>Hyphenation</h2>
18051611

@@ -1844,12 +1650,12 @@ <h2>Hyphenation</h2>
18441650
18451651
-->
18461652

1847-
1653+
<p>Hyphenation means splitting words to improve the layout of
1654+
paragraphs. This specifications does not define the exact rules for
1655+
hyphenation, but describes six properties that influence hyphenation.
18481656

18491657
<h3>Hyphenate properties</h3>
18501658

1851-
<p>This specification defines six new properties to describe hyphenation.
1852-
18531659
<table class=propdef>
18541660
<tr>
18551661
<td><em>Name:</em>
@@ -2075,7 +1881,7 @@ <h3>Hyphenate properties</h3>
20751881
</table>
20761882

20771883
<p>This property specifies a string that is shown when a
2078-
hyphenate-break occurs. The 'auto' value means that the User Agent
1884+
hyphenate-break occurs. The 'auto' value means that the user agent
20791885
should find an appropriate value.
20801886

20811887
<!--
@@ -3779,6 +3585,8 @@ <h3>The 'float-offset' property</h3>
37793585

37803586
<h2>Conformance</h2>
37813587

3588+
<!--User agents that support hyphenation and support this specification must a-->
3589+
37823590
<h2>Appendix A: Default style sheet</h2>
37833591

37843592
<p class=issue>

0 commit comments

Comments
 (0)