- From: <bugzilla@jessica.w3.org>
- Date: Mon, 11 Aug 2014 03:08:26 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22141
--- Comment #16 from Hayato Ito <hayato@chromium.org> ---
Thank you for the feedback!
(In reply to Olli Pettay from comment #15)
> I don't really like deepContains (partly because I think CSS is wrong by
> exposing
> shadow dom in that way, and also because 'deep' doesn't really say anything.)
>
> Couldn't we change contains() to take second param, which could be
> some dictionary.
>
> bool contains(Node? other, optional ContainsFilter filter)
>
> dictionary ContainsFilter
> {
> bool includeShadowDOM = false; // includeShadowDOM is a bit bad name.
> }
It looks better to me than deepContains. I like it.
If no one have better idea than this, I'l change the spec.
In this case, should I make a patch for DOM spec?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 11 August 2014 03:08:28 UTC