Initially, no. I think there’s scope to introduce auto later, if I’m not mistaken.
On Wed, 10 Apr 2024, at 6:38 PM, Brian Kardell wrote: > But not experimenting at all with some kind of auto? > > On Wednesday, April 10, 2024 at 1:31:39 PM UTC-4 Keith Cirkel wrote: >> __ >> We’re looking at prototyping the additive model in your latest comments Tab. >> We’ll also be implementing the similar model across GitHub.com (for internal >> validation only, for now) to see how well it aligns to our desired model. >> Hope this helps. >> >> On Wed, 10 Apr 2024, at 6:15 PM, Tab Atkins Jr. wrote: >>> There's been significant discussion in that thread over what the precise >>> behavior should be, particularly when elements using the attribute are >>> nested. Can you elaborate on which behavior you're intending to prototype? >>> >>> On Wednesday, April 10, 2024 at 9:15:47 AM UTC-7 Keith Cirkel wrote: >>>> __ >>>> Contact emails >>>> >>>> [email protected], [email protected] >>>> >>>> Explainer >>>> >>>> https://github.com/whatwg/html/issues/5033 >>>> >>>> Specification >>>> >>>> (Not yet available) >>>> >>>> Summary >>>> >>>> Adding a `headingstart=` attribute to Element nodes, that influences the >>>> child `h1`-`h6` elements' heading levels. >>>> >>>> >>>> >>>> Blink component >>>> >>>> Blink>DOM >>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EDOM> >>>> >>>> Motivation >>>> >>>> Websites which allow users to write comments or documents (User Generated >>>> Content - UGC) rely on users to produce meaningful heading structures for >>>> their written content. This can be difficult for a user where this content >>>> is presented on different surfaces (web pages or applications) that have >>>> different document structures. Giving web developers a headingstart >>>> attribute frees users from trying to pick the correct heading level (they >>>> can always start their comment or document at h1), and makes it >>>> significantly easier for web developers to render blocks of UGC without >>>> rewriting the UGC authors defined heading structures. >>>> >>>> >>>> >>>> Initial public proposal >>>> >>>> https://github.com/whatwg/html/issues/5033 >>>> >>>> TAG review >>>> >>>> None >>>> >>>> TAG review status >>>> >>>> Pending >>>> >>>> Risks >>>> >>>> >>>> >>>> Interoperability and Compatibility >>>> >>>> None >>>> >>>> >>>> >>>> *Gecko*: No signal >>>> >>>> *WebKit*: No signal >>>> >>>> *Web developers*: Positive >>>> >>>> *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 >>>> >>>> None >>>> >>>> >>>> >>>> Is this feature fully tested by web-platform-tests >>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>? >>>> >>>> No >>>> >>>> Flag name on chrome://flags >>>> >>>> Experimental Web Platform Features >>>> >>>> Finch feature name >>>> >>>> None >>>> >>>> Non-finch justification >>>> >>>> None >>>> >>>> Requires code in //chrome? >>>> >>>> False >>>> >>>> Estimated milestones >>>> >>>> No milestones specified >>>> >>>> >>>> >>>> Link to entry on the Chrome Platform Status >>>> >>>> https://chromestatus.com/feature/5090991750250496 >> -- 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/8443b8cf-cca2-4961-b611-fe41f1c1e50c%40app.fastmail.com.
