Words can be like X-rays, if you use them properly – they'll go through anything. You read and you're pierced.
– Aldous Huxley, Brave New World
Avian carriers can provide high delay, low throughput, and low altitude service. The connection topology is limited to a single point-to-point path for each carrier, used with standard carriers, but many carriers can be used without significant interference with each other, outside of early spring. This is because of the 3D ether space available to the carriers, in contrast to the 1D ether used by IEEE802.3. The carriers have an intrinsic collision avoidance system, which increases availability.
Previous Versions:
https://www.w3.org/TR/2016/WD-css-inline-3-20160524/
https://www.w3.org/TR/2015/WD-css-inline-3-20150917/
https://www.w3.org/TR/2014/WD-css-inline-3-20141218/
https://www.w3.org/TR/2002/WD-css3-linebox-20020515/
Issue Tracking:
Editors:
Suggest an Edit for this Spec:
Issues list:
Abstract
The CSS formatting model provides for a flow of elements and text inside of a container to be wrapped into lines. The formatting of elements and text within a line, its positioning in the inline progression direction, and the breaking of lines are described in [CSS-TEXT-3].
CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, etc.
Status of this document
This is a public copy of the editors’ draft. It is provided for discussion only and may change at any moment. Its publication here does not imply endorsement of its contents by W3C. Don’t cite this document other than as work in progress.GitHub Issues are preferred for discussion of this specification. When filing an issue, please put the text “css-inline” in the title, preferably like this: “[css-inline] …summary of comment…”. All issues and comments are archived, and there is also a historical archive.This document was produced by the CSS Working Group.
In the following snippet, samp and kbd elements are mixed in the contents of a pre element to show a session of Zork I.
This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent.An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.This document is governed by the 1 February 2018 W3C Process Document.
Issues Index
Many aspects of layout here depend on font metrics. While the relevant metrics exist in OpenType for Latin/Cyrillic/Greek and for CJK, they are missing for many other writing systems. For example, the visual top metric for Hebrew has no metric in the OpenType tables. For this module to work well for the world, we need fonts to provide the relevant metrics for all writing systems, and that means both that OpenType needs to allow such metrics and font designers need to provide accurate numbers. ↵This section is being rewritten.Refer to section 10.8 of [CSS2] for the normative CSS definition or the 2002 Working Draft if you want pretty pictures. (But ignore the old text, half of it’s wrong. We’re not specifying which half, that’s to be determined.) The CSS2 specification should be used as the guideline for implementation. ↵
↵The CSSWG would like to know which baseline values are necessary: if any can be dropped, or any need to be added. See GitHub issue 859. ↵Should be text-over and text-under instead of text-top and text-bottom, but maybe it’s better not to use those terms for consistency with legacy vertical-align.See GitHub issue 860. ↵
Add first and last values. Note, in this property, these are combinatorial, whereas in the align/justify-self/content properties, it’s singular. Do we want to align the syntaxes wrt hyphens vs. spaces or what? See GitHub issue 861.
This property will gain first and last keywords, like in the box alignment properties, see CSS Box Alignment 3 §4.2 Baseline Alignment: the baseline keyword and first/last modifiers.The open question is whether they should be added to alignment-baseline or a new sub-property should be created to hold the first | last preference.↵This is a rought draft of a proposal, and has not yet been approved by the CSSWG. See discussion in Issue 3199, Hyatt’s message, and dbaron’s proposal. ↵Should this property apply to block containers or to inline boxes? In the latter case, an individual inline could say "pay attention to me" or "don’t pay attention to me". ↵This is a rought draft of a proposal, and is likely to change significantly as design critiques and use cases are registered. Values and property names may be added, dropped, and/or renamed, and the overall syntax or behavior may change. Do not implement (yet). The CSSWG particularly invites feedback on which font metrics need corresponding keyword values.
I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours.
We might want to use this opportunity to more precisely define normal, rename it to match, and possibly introduce any other values that may seem necessary.The editors would appreciate any examples of drop initials in non-western scripts, especially Arabic and Indic scripts. ↵
Should there be a way to opt out of this behavior? See Github Issue 310. ↵
Renaming this property (and the others in this section) is currently under discussion. ↵Is there a proper typographic term for the hebrew “hanging” baseline? ↵This only covers the most common cross-linguistic transcription systems. Should we include any other / all script tags in the UA style sheet? ↵
Reword that to handle box-sizing correctly. ↵
What about inheritance to descendants? ↵
Update this calculation to be a) generic across writing systems / alignment points and b) handle non-integer sizes. ↵
Are there other things we need to consider here? ↵Should the hanging punctuation be included in the box instead (so that the box is drawn around the punctuation when it is made visible through borders/background), but rather only excluded when positioning the box (so that the initial letter remains flush, with the hanging punctuation properly hanging)? See discussion. ↵Do we need an unconditional first? (I.e. Should we rename this value to auto and add a first value that does not check for spaces?) See GitHub issue 410 ↵This really needs font-relative lengths to be relative to the used size. ↵
These values and related annoyance is likely unnecessary if someone submits a patch to Blink to support first. ↵
Edit figure to show how auto behaves in varying contexts ↵
The interaction of initial-letters and hanging-punctuation is under discussion. ↵
Handle glyph ink above cap height of font. Proposal: Make it an exclusion area for line boxes and border boxes. Include margin specified on initial-letters as part of exclusion area in order to control spacing. ↵
Draw a box model diagram here. Does the margin of the initial letter collapse with its container? ↵
Whether an inline-end float originating in subsequent lines must clear the initial letter (as inline-start floats do) is still under discussion. There is no aesthetic reason to require it; however it’s yet unclear how the underlying layout model would distinguish between the two cases. ↵
Pick a default. ↵
Somebody sanity-check these heuristics please. ↵
Copy over text from CSS Writing Modes and expand for additional baseline values.