- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Apr 2023 19:23:57 +0000
- To: public-css-archive@w3.org
> @flackr @bramus Wrt multiple scroll containers attempting to attach to the same name: should we be erroring this case to nothing, or taking the last one in tree order? CSS tends to use the "take the last one" principle to resolve conflicts in most places... Given the expectation that the developer has chosen a particular timeline to be elevated / visible at the ancestor we expect that they have a 1:1 pairing of ancestor/descendant. I think treating multiple descendants trying to slot into the same name as an error would help bring the issue to the developer's attention when this happens accidentally. I feel like it would be unlikely for developers to identify multiple scroll timelines intentionally. That said I do agree that it goes against the usual convention - but the usual convention with properties is also the one from the selector with most specificity which this does not do. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7759#issuecomment-1498002007 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 April 2023 19:23:59 UTC