Re: [csswg-drafts] [css-env] getting access to the document title (#3685)

The CSS Working Group just discussed `getting access to the document title`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: getting access to the document title<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3685<br>
&lt;tantek> q+ to note "title of the document" is not necessarily &lt;title> but sometimes (often) &lt;h1> etc.<br>
&lt;dael> florian: There is a feature in GCPM that lets you in paged media generate header and footer with repeating document title in box. Interesting, but highly specific so not impl by mainstream browser. Base feature to take doc title and inject somewhere visible is useful. nth function seems like it could achieve that. Proposal is to have nth-doc-title expose the title of the element to be used in generated content<br>
&lt;tantek> right, I know that. I'm saying your use-case is disconnected from your solution.<br>
&lt;dael> florian: I'm specifically referring to a title element, not an h1. This isn't regions. H1 can have complex markup which wouldn't transfer to nth. HTML title element is just text so it's useful as well. Regions is useful but bigger<br>
&lt;Rossen_> gtg, bye<br>
&lt;dael> tantek: Not about extra markup but typical title elements contain things from name of website to author to doc name. If looking to solve use case and you want to repeat the huma readable title of document that information is often in first H1. If the use case is the repeating thing that doens't solve with how people publish on web today.<br>
&lt;dael> florian: I think will work with most eBooks but you have a point<br>
&lt;emilio> q+<br>
&lt;bkardell_> hmm<br>
&lt;dael> tantek: I would want to double check solution<br>
&lt;astearns> ack tantek<br>
&lt;Zakim> tantek, you wanted to note "title of the document" is not necessarily &lt;title> but sometimes (often) &lt;h1> etc.<br>
&lt;bkardell_> I cannot hear - is the call running?<br>
&lt;emilio> Audio went out<br>
&lt;emilio> Oh well<br>
&lt;emilio> Will comment on the issue<br>
&lt;astearns> thanks<br>
&lt;AmeliaBR> +1 to tantek's argument on practicality. But I like the general idea of env() to access document properties.<br>
&lt;dael> astearns: We're out of time. THanks everyone for calling in<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3685#issuecomment-477255723 using your GitHub account

Received on Wednesday, 27 March 2019 17:01:58 UTC