[polymer-dev] Setting undefined properties via data binding

['Michael Giuffrida' via Polymer]

Some questions about what behavior is defined for data binding (and what's
undefined behavior and should be avoided) when using properties which
aren't actually defined.

https://jsfiddle.net/daLLdao2/

If I give a Polymer tag some-made-up-attribute="foo", nothing happens. But
if I give that made-up attribute a value via data binding
(some-made-up-attribute="[[myProperty]]"), the Polymer element gets a new
someMadeUpAttribute property set to the value and type of myProperty. Is
that okay, or should we not expect that to work?

It gets weirder: if I want to create a property and assign it to a literal,
I can do this:
some-made-up-attribute="[[notARealProperty]]my string literal"
the attribute someMadeUpAttribute is again created on the child, and given
the string value "my string literal". Is that a fluke, or is data binding
defined to work that way?

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/CACi5S_1%2BiB7SpHQkhEANxpvhe-4Dgp%3DYNnL%2BU%2Be0obHySi-3pA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Dendrimer

[Michael Giuffrida]

Heh, this keeps happening. I think the team may have taken the metaphor a
bit *too* far.

I mean... polymer, vulcanize, hydrolysis... iron, neon, platinum, gold,
carbon, elements, molecules... probably others I'm forgetting/haven't heard
about.

Maybe you guys should consider "dendrimers" for describing your GitHub
branches?

On Mon, Feb 22, 2016 at 10:02 PM Karl Tiedt  wrote:

> Yeah this is a mailing list for the Polymer javascript project
>  not a science group ;)
>
> -Karl Tiedt
>
> On Mon, Feb 22, 2016 at 9:28 PM,  wrote:
>
>> Hi! I'm new to polymers and while I was looking through some examples, I
>> found what was called a "tailored" dendrimer where one of the terminal
>> surface groups is different from the rest. How might this be synthesised?
>> I've looked through so many textbooks but none of which mention this.
>> Hopefully someone here can help!
>>
>> 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/44bf1149-3749-4c7c-b628-97e87bc4a98d%40googlegroups.com
>> 
>> .
>> 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/CADNgbTHHwwN6rmer7Nmy1r4RXNDYyOYnqSML7zmJ6Ar8Hh43PA%40mail.gmail.com
> 
> .
> 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/CACi5S_0nU6xaV0auTQRbH%3DQngH7Pe8%3DYPj5a4nuNtfEfNaT6Fg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[polymer-dev] Native CSS variable support

[Michael Giuffrida]

Hey Polymer folks,

The latest desktop Chrome supports CSS custom variables natively, as has
Firefox for a while now. This should increase performance compared with
shimming variables.

Is the Polymer shim aware of native implementations, or does it still spend
cycles shimming them? Does this behavior change depending on how styling is
done (s, inside/outside dom-modules, etc.)?

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/CACi5S_3kTTVdNKK34zbndvky027odYz6j36mF1fEL1sjZasTsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[polymer-dev] Re: Deprecating

[Michael Giuffrida]

On Tue, Jan 19, 2016 at 2:20 PM Michael Giuffrida <michae...@chromium.org>
wrote:

> Perusing the docs, I just noticed a change: external stylesheets for local
> DOM are now deprecated in favor of *style modules*. Examples are below.
>
> In addition to adding more boilerplate, this wreaks havoc on text editors
> like emacs/vim because mixed filetype editing *sucks*. What's the
> rationale for deprecating the (granted, experimental)  type="css">?
>
> Furthermore, in the future, can somebody send out announcements for this
> kind of thing? The only notice of  was a few lines in the
> CHANGELOG.md and there's no mention of deprecation there.
>

Okay, this change was clearly announced in the blog post for the 1.1
release. My bad! But it would still be nice to have release announcements
mirrored to this list if possible.

<a  rel="nofollow" href="https://blog.polymer-project.org/announcements/2015/08/13/1.1-release/">https://blog.polymer-project.org/announcements/2015/08/13/1.1-release/</a>


> Examples:
>
> *Deprecated:*
> <!-- x-foo.html -->
> <dom-module id="x-foo">
> *  <link rel="import" type="css" href="my-styles.css">*
>   <template>...</template>
> </dom-module>
> <!-- my-styles.css -->
> *.red { color: red; }*
>
> *New recommendation:*
> <!-- x-foo.html -->
> *<link rel="import" href="my-styles.html">*
> <dom-module id="x-foo">
>   <template>...
> *<style include="my-styles">*
>   
> 
> 
> **
> *  *
> *...*
> *  *
> **
>
>

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/CACi5S_0ircNXnewsu-CBTOX8pvaMSktMkL%2B7j5bdirSScGdPug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[polymer-dev] Deprecating

[Michael Giuffrida]

Perusing the docs, I just noticed a change: external stylesheets for local
DOM are now deprecated in favor of *style modules*. Examples are below.

In addition to adding more boilerplate, this wreaks havoc on text editors
like emacs/vim because mixed filetype editing *sucks*. What's the rationale
for deprecating the (granted, experimental) ?

Furthermore, in the future, can somebody send out announcements for this
kind of thing? The only notice of  was a few lines in the
CHANGELOG.md and there's no mention of deprecation there.

Examples:

*Deprecated:*


*  *
  


*.red { color: red; }*

*New recommendation:*

**