Re: [polymer-dev] Re: Deprecating
Is there going to be any mechanism for using stylesheets without having to wrap them in a dom-module and template? At my job we have multiple teams using the same stylesheets with different front end frameworks (most teams use React, we're the odd one out using Polymer). Our UX team is not interested in duplicating the styles for each framework (I.e. my-styles.css for non-polymer and my-styles.html with the contents of my-styles.css duplicated inside for polymer), so losing the ability to import a CSS file directly is going to put us in a tough spot. 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/284518f2-87ec-492d-b698-46f2e9877135%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [polymer-dev] Re: Deprecating
Wow, perfect! Not sure how I missed those tools. Thanks! 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/50abc5b4-b5d1-4329-afd8-6305df74f0de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[polymer-dev] Styling distributed nodes with @apply
I asked this question on stackoverflow about a week ago and haven't heard anything from it. I figured I'd cross post it here as well to try to generate some traffic: http://stackoverflow.com/questions/30806194/polymer-1-0-how-to-style-distributed-nodes-with-apply Thanks in advance to anyone who helps out! 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/079e134b-40ff-4705-8da3-4b858ea041fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[polymer-dev] Re: core-scaffold
I think you might be interested in paper-drawer-panel: https://elements.polymer-project.org/elements/paper-drawer-panel It'll at least get you the pop out responsive drawer part...should be able to combine it with a header-panel to get what you're looking for. 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/7cfc82c7-beec-433a-b469-c2421c131c11%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[polymer-dev] Re: localDom API and other libraries
Is the experimental import for avoiding Polymer.dom documented anywhere? I'd be interested in trying it out. On Monday, May 18, 2015 at 8:46:20 PM UTC-4, Eric Eslinger wrote: One of the really rad things about Polymer (0.5) and webcomponents is that everything is just DOM. You can pretty easily use core- and paper- components libraries inside of an (say) angular app to render out content. Doesn't matter if you're using jQuery raw or ember or what have you- DOM is DOM, and it mostly works (modulo some property / attribute bindings) The new localDom API seems to indicate that this may no longer be the case- if I'm redistributing DOM content, I need to use the polymer dom interface, rather than just plain parent/child/append calls on document. This seems to indicate that modern polymer isn't going to be compatible with angular, or with any other library that manipulates the DOM, or is it the case that this only matters when there's more complicated shady/light manipulations? As an example, if I have content in the drawer part of a paper-drawer-panel, and then, using jquery or some other element selector, inject nodes inside of the already-projected menu div, will this break things? Or is it only the case that I need to use the local DOM api when if I'm changing the nodes that would be selected as content to project (and not their child nodes)? Is there some way to shim the document-level query selectors in there or add a mutation observer that calls distributeContent as needed? I'm guessing it was this shimming and mutation observer that contributed to the slowness of 0.5 in non-chrome browsers. I've got next week blocked out to actually work on getting angular 1.4 to play nice with polymer 0.9 (we use angular to build the page and manage data, and polymer for handy flexbox directives and material design ui bindings). So I guess I'll figure it out then. e 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/65c523d0-47b1-4786-8584-fdd2d2fd8047%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [polymer-dev] Re: localDom API and other libraries
We have experimented with patching dom traversal and mutation api's, and there's an experimental import in Polymer that does this. It can let some libraries interoperate more smoothly with Shady DOM powered elements that, for example, perform distribution. We're continuing to work on it and explore if it should be integrated out of the box or be available as an opt in layer. See the above quote. I just want to make sure I was clear about what I was asking about, as Steve Orvell seemed to be hinting at something that would work with Shady DOM and not require falling back to Shadow DOM. On Wednesday, May 20, 2015 at 1:41:47 PM UTC-4, Justin Fagnani wrote: On Wed, May 20, 2015 at 10:36 AM, jim.j...@gmail.com javascript: wrote: Is the experimental import for avoiding Polymer.dom documented anywhere? I'd be interested in trying it out. It's not experimental, it's the same Shadow DOM polyfill that we've had for a a long time: https://github.com/webcomponents/webcomponentsjs webcomponents.js includes the full polyfill, webcomponents-lite.js doesn't. On Monday, May 18, 2015 at 8:46:20 PM UTC-4, Eric Eslinger wrote: One of the really rad things about Polymer (0.5) and webcomponents is that everything is just DOM. You can pretty easily use core- and paper- components libraries inside of an (say) angular app to render out content. Doesn't matter if you're using jQuery raw or ember or what have you- DOM is DOM, and it mostly works (modulo some property / attribute bindings) The new localDom API seems to indicate that this may no longer be the case- if I'm redistributing DOM content, I need to use the polymer dom interface, rather than just plain parent/child/append calls on document. This seems to indicate that modern polymer isn't going to be compatible with angular, or with any other library that manipulates the DOM, or is it the case that this only matters when there's more complicated shady/light manipulations? As an example, if I have content in the drawer part of a paper-drawer-panel, and then, using jquery or some other element selector, inject nodes inside of the already-projected menu div, will this break things? Or is it only the case that I need to use the local DOM api when if I'm changing the nodes that would be selected as content to project (and not their child nodes)? Is there some way to shim the document-level query selectors in there or add a mutation observer that calls distributeContent as needed? I'm guessing it was this shimming and mutation observer that contributed to the slowness of 0.5 in non-chrome browsers. I've got next week blocked out to actually work on getting angular 1.4 to play nice with polymer 0.9 (we use angular to build the page and manage data, and polymer for handy flexbox directives and material design ui bindings). So I guess I'll figure it out then. e 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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/65c523d0-47b1-4786-8584-fdd2d2fd8047%40googlegroups.com https://groups.google.com/d/msgid/polymer-dev/65c523d0-47b1-4786-8584-fdd2d2fd8047%40googlegroups.com?utm_medium=emailutm_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 polymer-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/1c7f2a46-ee03-455f-b73f-c5090dc90873%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[polymer-dev] Re: 0.8 Polyfill Browser Support
There wasn't anything in particular. Someone at my work looked at the compatibility matrix at https://github.com/WebComponents/webcomponentsjs and started asking questions. I was just curious if the new release of Polymer was going to help with the compatibility pieces marked flaky. Thinking about it now, it seems unlikely unless the Polymer team changed the base polyfills directly (or maybe augmented them). On Wednesday, May 6, 2015 at 9:30:06 AM UTC-4, Douglas Hubler wrote: IE10 worked fine for me in 0.5 sans a pause while it groked the embedded CSS. If you had specific IE10 issues I would list them and maybe folks can respond to if things are better or worse or better yet, find them in the bug db and check their status. Considering the basis of the rewrite was for better support for browsers that do not implement web components, it's somewhat safe to assume the overall situation is better. On Tuesday, May 5, 2015 at 1:32:38 PM UTC-4, jim.j...@gmail.com wrote: With 0.8+ being a significant rewrite that is aiming to be lighter weight and less magical, will browser support remain the same? I'm specifically interested to know if IE10 support is going to be any better. 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/55e18c84-4f53-4765-a4d4-9b7ae5da97af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[polymer-dev] 0.8 Polyfill Browser Support
With 0.8+ being a significant rewrite that is aiming to be lighter weight and less magical, will browser support remain the same? I'm specifically interested to know if IE10 support is going to be any better. 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/527c9e56-37c9-4410-b010-dd28f46a6034%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[polymer-dev] Web Component Tester (WCT) with Selenium Grid
We're trying to get Web Component Tester to use a Selenium Grid for our
tests, but we can't seem to get the configuration right (using grunt). Is
this even possible, and if so, what should the configuration look like?
We're currently trying:
'wct-test': {
local: {
options: {
activeBrowsers: [{
browserName: 'chrome',
url: 'http://jenkins.myapp.corp.web:/wd/hub'
}]
}
}}
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/polymer-dev/8d58e44e-24e4-4cbb-b86c-20897a1112f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
