- From: Takayoshi Kochi via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Dec 2016 08:04:01 +0000
- To: public-css-archive@w3.org
That's a fair argument, thanks for the explanation. What I am concerned is that if a web author doesn't care if his/her component exposes an internal element as offsetParent, or rather would like to get offsetParent for slotted element intentionally, and if we change offsetParent the way you propose, we lose the ability to know the exact offsetParent which is not closed-shadow-hidden to the context object. I cannot say that anyone doesn't need to poke offsetParent inside shadow trees at all with confidence. I haven't tried yet, but can we write a polyfill to get the exact offsetParent algorithm (as in cssom-view spec as of today) using `.assignedSlot` etc.? -- GitHub Notification of comment by TakayoshiKochi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/159#issuecomment-266968706 using your GitHub account
Received on Wednesday, 14 December 2016 08:04:07 UTC