Skip to content
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.

[css-regions-1] Style cascading when element is flowed in itself #78

Closed
mibalan opened this issue Aug 29, 2013 · 1 comment
Closed

[css-regions-1] Style cascading when element is flowed in itself #78

mibalan opened this issue Aug 29, 2013 · 1 comment
Labels
spec:regions type:missing-coverage
Milestone
css-regions-1_dev

Comments

@mibalan
Copy link

mibalan commented Aug 29, 2013 •
edited by wpt-issue-mover
Loading

The CSS cascade follows the DOM order. This test(s) should make sure that in more complicated cases where an element is flowed in itself (or an indirect child gets flowed in the element) the CSS cascade does not get confused.

Something similar should cover proper CSS cascading when using nested named flows.
@wpt-issue-mover wpt-issue-mover mentioned this issue Apr 7, 2017
Closed
@w3c w3c locked and limited conversation to collaborators Apr 7, 2017
@w3c w3c unlocked this conversation Apr 7, 2017
@gsnedders gsnedders reopened this Apr 7, 2017
@gsnedders gsnedders mentioned this issue Apr 13, 2017
Closed
38 tasks
@wpt-issue-mover
Copy link
Collaborator

This issue has been merged into web-platform-tests/wpt#5556; please see that issue if you wish to discuss or work on this.

@w3c w3c locked and limited conversation to collaborators Apr 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
spec:regions type:missing-coverage
Projects
None yet
Milestone
css-regions-1_dev
Development

No branches or pull requests
3 participants
@gsnedders @mibalan @wpt-issue-mover