W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2016

Re: [csswg-drafts] [css-content] Generation of bookmarks from CSS is not defined

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Wed, 22 Jun 2016 19:38:36 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-227853727-1466624316-sysbot+gh@w3.org>
> Document order after execution of any/all scripts? So the "final 
DOM", if you will, for the document? Or the order as originally 
parsed, before execution?

CSS has no notion of document mutation (besides the hacked-in 
time/state management of Transitions and Animations); as far as it's 
concerned, the document is stable and has always been in that state, 
and if anything changes, it's always been in that new state.

> OK - I think that's perfectly fine. If you could make this clear in 
the spec, that would be helpful.

Iframes are replaced elements, which CSS explicitly has no control 
over nor gets any information from besides sizing, unless otherwise 
explicitly specified. So we don't need to say anything special here; 
bookmark info just doesn't come from those. 

GitHub Notification of comment by tabatkins
Please view or discuss this issue at 
using your GitHub account
Received on Wednesday, 22 June 2016 19:38:39 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:40:59 UTC