W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2010

[whatwg] Qs about <details> element

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 4 Feb 2010 09:06:05 -0600
Message-ID: <dd0fbad1002040706sa7192s7e7a4514d9cd5f@mail.gmail.com>
On Thu, Feb 4, 2010 at 6:51 AM, Philippe Wittenbergh <emps at l-c-n.com> wrote:
> On Feb 4, 2010, at 9:21 PM, Ian Hickson wrote:
>>> 2) What should UAs do when printing? It seems to me that, when printing,
>>> a <details> element should be open, regardless of the state of the
>>> boolean open attribute. (because it's a markup attribute, there is
>>> presumably now way for a print stylesheet to override this). Can that be
>>> added to the spec?
>>
>> Generally speaking, browser vendors have found that people expect their
>> "print" features to just print what's on the screen. However, I'm
>> certainly open to changing the spec on this if the browser vendors feel
>> the spec should change -- any implementors have an opinion on this?
>
> As a page author and site developer (and as a user), I would certainly want the possibility to display the content of the details element when printing, insofar as it is relevant to the document in a printed state.
> (that is, a print stylesheet should be able to override the onscreen display state of <details>)

The <details> implementation will likely be nothing more than this CSS
(roughly):

details:not([open]) > :not(summary:first-of-type) { display: none; }

So it should be easily overrideable in a print stylesheet.

~TJ
Received on Thursday, 4 February 2010 07:06:05 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:20 UTC