On Tue, Nov 22, 2022 at 3:41 AM Yoshifumi Inoue <[email protected]> wrote:
> Contact [email protected], [email protected] > > ExplainerNone > > Specificationhttps://drafts.csswg.org/css-inline/#initial-letter-styling > > Design docs > https://bit.ly/3KzJ27G > > Summary > > Initial letters are large, decorative letters have been used to start new > sections of text since before the invention of printing. In fact, their use > predates lowercase letters entirely. Blink will support CSS property > "initial-letter". > > > Blink componentBlink>Layout>Inline > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELayout%3EInline> > > TAG reviewWebKit shipped `-webkit-initial-letter`. > > TAG review statusNot applicable > > Risks > > > Interoperability and Compatibility > > Chrome supports full syntax of `initial-letter`: 1 `initial-letter:` > number 2 `initial-letter:` number integer 3.`initial-letter:` number `drop` > 4.`initial-letter:` number `raise` However Safari supports: 1. > `-webkit-initial-letter:` integer 2. `-webkit-initial-letter:` integer > integer So, web authors needs to use Safari compatible syntax. > > > *Gecko*: In development ( > https://github.com/mozilla/standards-positions/issues/711) No active > development since 2017. > > *WebKit*: Shipped/Shipping ( > https://github.com/WebKit/standards-positions/issues/94) Needs to use > prefix version `-webkit-initial-letter`. Supports only an integer size. No > `drop` and `raise` keyword support. > > *Web developers*: No signals It’s implemented only in Safari, but the > usage is high. * 40.2% usage ratio according to CSS2021 Usage Overview[1]. > * 23.9% have used it according to CSS2021 Typography features[2]. [1] > https://2021.stateofcss.com/en-US/features/#features_overview [2] > https://2021.stateofcss.com/en-US/features/typography/#initial_letter > > *Other signals*: > > WebView application risks > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > None. > > > Debuggability > > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)?No > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?No > Why not? Is there any reason tests couldn't reasonably be added prior to shipping? DevTrial instructionshttps://output.jsbin.com/basukanebo/1 > > Flag name > > Requires code in //chrome?False > > Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1276900 > > Non-OSS dependencies > > Does the feature depend on any code or APIs outside the Chromium open > source repository and its open-source dependencies to function? > No. > > Sample links > https://output.jsbin.com/basukanebo/1 > > Estimated milestones > > M110 > > > Anticipated spec changes > > Open questions about a feature may be a source of future web compat or > interop issues. Please list open issues (e.g. links to known github issues > in the project for the feature specification) whose resolution may > introduce web compat/interop risk (e.g., changing to naming or structure of > the API in a non-backward-compatible way). > None. > Any idea what the position in the CSS WG is about the maturity of the spec for this feature? I see a bunch of open spec issues <https://github.com/w3c/csswg-drafts/issues?q=is%3Aopen+label%3Acss-inline-3+initial-letter> mentioning initial letter. To what extent are you confident that none of them represent a potential breaking change depending on their resolution? > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5167442033115136 > > Links to previous Intent discussionsIntent to prototype: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABJ-EHNMC29gEMkgopMJFW6LfWCCuxXmC0F%2BRPpOuM%3Dznbo5LQ%40mail.gmail.com > Intent to Experiment: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABJ-EHPFVLa-frSXmjhbK97L%3D8eh7ZeS6Uap3BiSNfksDicdHA%40mail.gmail.com > > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/dcc32334-ed12-4c85-b80e-0eb97027496cn%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/dcc32334-ed12-4c85-b80e-0eb97027496cn%40chromium.org?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY883FMK-OMrRcvG9woeY2YpbRmzEVNx%2BTwrYx8vL-%2BBNA%40mail.gmail.com.
