Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/52149efb-bb20-46ce-aa38-dafe9c708adc%40googlegroups.com.
The more important question... why do you feel you need /deep/ to test components?
-Karl Tiedt
On Fri, Sep 29, 2017 at 12:58 PM, <peter...@gmail.com> wrote:
I will reply with something i found on slack overflow"The piercing selector is being dropped (/deep/ and >>>). There's currently no other alternative to search through the whole DOM with a single query. The current solution is to implement a custom selector taking multiple CSS segments to search each context"
On Thursday, September 28, 2017 at 9:18:01 AM UTC-6, peter...@gmail.com wrote:My organization is going to be moving to Polymer 2 and with that they will have to move away from the shady dom to the shadow dom. I do know that /deep/ is being deprecated? Is there going to be something that will substitute for /deep/ that we can use in place when using Selenium and Protractor and Mocha?
Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/0f92cce9-a733-4391-8b7d-dacc1f70620f%40googlegroups.com.