Well now I feel ashamed of my harsh words; should have thought twice before posting. I apologize for that.
I have read the blog post you are ref to, doesn't help. Arthure suggests below to force polyfills to make it work; this I will try and see if that helps. On Saturday, September 23, 2017 at 3:17:11 AM UTC+3, Karl Tiedt wrote: > > The problem isnt Javascript, the problem is CSS and relying on overly > general CSS selectors... You've still failed to elaborate on this extremely > flamboyant claim of "flat out ignores virtually all of the Javascript > libraries in existence". 1 question about 1 library is not cause for such > an alarmist response. It is also worth noting that the problem isnt Polymer > 0.5, 0.8, 1.x, 2.x or even 3.x, this is the nature of Web Components. > > Rob Dodson wrote a pretty good explanation surrounding jQuery plugins that > explains my first statement - > http://robdodson.me/dont-use-jquery-with-shadow-dom/ > > -Karl Tiedt > > On Fri, Sep 22, 2017 at 7:04 PM, Egor Egorov <[email protected] > <javascript:>> wrote: > >> >> See https://groups.google.com/d/msg/polymer-dev/vB7upjV_z7s/5Hk9BJFTAAAJ >> - no replies. No one uses Bootstrap with Polymer? >> >> Am I right assuming that basically anything jQuery-based is a no go? >> >> >> On Saturday, September 23, 2017 at 3:01:06 AM UTC+3, Karl Tiedt wrote: >>> >>> Please elaborate on this, " and 2.0 flat-out ignores virtually all of >>> the javascript libraries in existence"... I worked with many 3rd party >>> libraries and so have many people... In fact you can find these >>> integrations on GitHub and the web components website... >>> >>> On Sep 22, 2017 18:49, "Egor Egorov" <[email protected]> wrote: >>> >>> Hello. >>> >>> We are running a huge enterprise application written with Polymer 1.0 >>> and Bootstrap. Now what we face is a bit of devastating: 1.0 is going to >>> stop working around Chrome 63 and 2.0 flat-out ignores virtually all of the >>> javascript libraries in existence, hence no Bootstrap on Polymer 2.0. As >>> much as we love Polymer 1.0, we have found no way to integrate existing JS >>> libraries we use with the 2.0. >>> >>> What would be a good migration path for a Polymer 1.0 application? >>> >>> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/polymer-dev/78829894-3022-417b-9624-e3cd1c02656c%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/polymer-dev/78829894-3022-417b-9624-e3cd1c02656c%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/polymer-dev/edac8597-c940-4abf-9e19-e5adcab1bde7%40googlegroups.com >> >> <https://groups.google.com/d/msgid/polymer-dev/edac8597-c940-4abf-9e19-e5adcab1bde7%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/a778de39-1e26-4a97-b219-74e644297b94%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
