Re: [polymer-dev] Re: Autogenerate README for polymer element

['Daniel Freedman' via Polymer]

We use a tool called tedium to update our elements:
https://github.com/polymerlabs/tedium. It does a lot more than generate the
README, such as generating issue templates and enforcing shadow dom
testing, but it is not quite ready yet for use outside of Polymer's
elements (a lot of things are hardcoded). You could try copying some of the
techniques, or maybe Peter has some better suggestions.

On Sun, Mar 27, 2016 at 10:31 AM, Luv Agarwal 
wrote:

> I see that Polymer is using hydrolysis for generating docs. But there is
> no proper documentation available which explains how to generate docs in
> markdown format given an element.
>
> 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/781f47bb-64bd-4c0c-a63a-f16712aa83bd%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/CAAUAVAi2BgBN1fUYyfZ-ra0ROPPASVoCjcY5YPacdzp-13-rCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Behavior Polymer.PaperInkyFocusBehavior not found when mixing properties into...

['Daniel Freedman' via Polymer]

This seems like it may be a bug in `iron-component-page`, the doc viewer
element.

+AJ, is hydrolysis smart enough to load behaviors that aren't named in the
top level import?

On Sat, Feb 27, 2016 at 7:55 AM, Thad Humphries 
wrote:

> I am writing my first serious component and have found something odd. My
> component includes the behavior Polymer.PaperInkyFocusBehavior. When I load
> the component served by polyserve, I see in an alert message in my browser
> console, "Behavior Polymer.PaperInkyFocusBehavior not found when mixing
> properties into my-component!" from line docs.js:155. In the Docs page,
> the members of the "Behaviors" block do not format correctly. I am getting
> this error with Polymer 1.2.x and 1.3.0.
>
> You can recreate this error yourselves by cloning the Polymer
> paper-icon-button ,
> running `bower install` and `polyserve`, and opening
> http://localhost:8081/components/paper-icon-button/ in Chrome. You'll see
> the message "Behavior Polymer.PaperInkyFocusBehavior not found when
> mixing properties into paper-icon-button!" in the Chrome console, and the
> bad formatting of Docs:Behaviors.
>
> My component and paper-icon-button work as expected, but the message and
> formatting are annoying.
>
> 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/d262724f-79c1-4591-8a3a-b1ace24fbeb8%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/CAAUAVAgsORnnoEghfByOM3f9xVBUaRbwy600%3D%2B5uh_WWkygJzg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Minification and Vulcanization ought to be simplified

['Daniel Freedman' via Polymer]

If you want a simple build setup, we provide an all-in-one minification
tool for gulp called polybuild: https://www.npmjs.com/package/polybuild.

You can also copy the gulp configuration of the Polymer Starter Kit:
https://github.com/polymerelements/polymer-starter-kit

On Fri, Dec 4, 2015 at 6:17 PM,  wrote:

> Thanks for your reply. I forgot that Polymer was designed to be modular in
> case others want to use a mix of components from different vendors. I guess
> for now I need to figure out grunt
>  in order to minify
> my vulcanized components.
>
> On Friday, December 4, 2015 at 9:06:53 PM UTC-5, Eric Bidelman wrote:
>>
>> The a la carte nature of web components means you only need to load the
>> components you need. If someone only wants to use a paper-button on their
>> page, why should they be forced to request a vulcanized build of all the
>> minified components? How would this work in practice?
>>
>> On Fri, Dec 4, 2015 at 5:36 PM  wrote:
>>
>>> I'd like to be able to use Polymer on a production environment, and
>>> Polymer has a nice shopping cart style, but it isn't ideal.
>>>
>>> 1. It only downloads individual components, unminified, and without
>>> their dependencies (bower makes this step easier, but all files are still
>>> unminified)
>>> 2. You end up with a couple  tags in the ,
>>> but they rely on multiple dependencies, resulting in numerous http requests
>>> (hence the need to vulcanize)
>>> 3. After vulcanizing, you need to minify it yourself
>>>
>>> I hope someday soon I'll be able to check out my favourite elements to
>>> the shopping cart, and download 1-2 minified files for production use: (1)
>>> the polymer components vulcanized and minified, (2) webcomponentsjs - which
>>> I understand must be loaded outside of the polymer components.
>>>
>>> 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 view this discussion on the web visit
>>> https://groups.google.com/d/msgid/polymer-dev/1e20a3e1-5335-4d00-bc4e-819b3fcfaa5b%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/9510fe70-613c-4f40-9174-29cf5c12d077%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/CAAUAVAjOraQHrEPTF4s-uZ4Hp5SR9-Qp1C0ORco_CwFU_V1K7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] polymer js

['Daniel Freedman' via Polymer]

You probably didn't specify the `is` property in your element in the
Polymer call.



Polymer({
is: 'my-element'
})



On Mon, Nov 16, 2015 at 10:08 PM, Eric Bidelman  wrote:

> It would be helpful if you posted your code.
>
> On Mon, Nov 16, 2015 at 9:34 PM  wrote:
>
>> Hi,  I need polymer js without errors...
>>
>>
>> 
>>
>> 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/d148b509-4582-4c64-a734-2bab7065d0dd%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/CACGqRCAkj_A8p7siTT8xsYcDXhFFKas8pXeWZC6k6kMCcCAeeQ%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/CAAUAVAisQMj_ujG7i%2BXMAq6_PTuAjbfpkGeB%2B56o%3Dd4uQrhbmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] polymer on mobile - prevent scroll to refresh

['Daniel Freedman' via Polymer]

The "prevent scrolling" behavior is already present as
`element.setScrollDirection('none')`. You probably don't want to prevent
scrolling on the whole page, so it is an element-by-element behavior.

I'd like to get some feedback from Chrome's Input team for more elegant
solutions that don't require whole-document touch handlers, which jank
scrolling.

On Wed, Oct 7, 2015 at 11:33 AM, Eric Bidelman  wrote:

> +1 This would be a useful pattern to codify.
>
> Dan have we thought about componentizing this pattern as a behavior?
>
> On Fri, Oct 2, 2015 at 2:50 AM Ged Wed  wrote:
>
>> With SPA on mobile, its easy to accidently swipe down, hit the top and
>> force a refresh of the whole AP application. This is a pretty bad usability
>> bug.
>>
>> So i found some code to prevent it. Works on Android.
>> Can someone verify it works on IOS ?
>>
>> The jsbin is here:
>> http://jsbin.com/qofuwa/2/edit?html,js,output
>>
>> Ideally i see two thing to do next:
>> 1. Make it a polymer behaviour
>> 2. There are some Elements where you want to reload on scroll-to-refesh
>> swipe, but only if the user is swiping on that specific element. It can
>> then do its own ajax call for update.
>>
>> I am wondering if the Polymer devs have thought about this as a
>> behaviour, and are planning to work on this anyway and officially support
>> it.
>>
>> 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/e5cb3894-0bd5-4c4b-9e04-fa3360125f6c%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/CAAUAVAihxF-iTeAPFCpswz1piAxD0aiBUZ3YEB8_5T5K%2BWnmAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] String concatenation is not supported inside a tag, and the tag can’t contain any whitespace:

['Daniel Freedman' via Polymer]

Arguments to functions in data-binding must be the names of data-bound
properties:
https://www.polymer-project.org/1.0/docs/devguide/data-binding.html#annotated-computed

I'd also suggest not trying to change the id or on-click bindings like
that, but instead place a new attribute on paper-button with your computed
binding.
Then the "validate" function can be a lot simpler:
http://jsbin.com/baxucesusa/edit?html,console,output

On Sun, Sep 20, 2015 at 10:24 PM, toduu  wrote:

> String concatenation is not supported inside a tag, and the tag can’t
> contain any whitespace.   This limitation is hampering.
>
> The moment you do auto format in an ide like eclipse the whole thing gets
> messed up because spaces get inserted.
>
> All the function writing one has to do to overcome this limitation also
> adds more javascript to the code.
>
> Also I was unable to pass data binding to a function.
>
> e.g.  I have a iron-list with items which are paper-cards that have
> paper-button  .   While setting id based on a function works passing it to
> another function validate fails ...
>
> Any suggestions?
>
> 
> 
> 
>
> 
>
> 
>
>
> 
>
> ...
>
> 
>
>
>
>  "validate({{_ans('W',que)}})">
>
> ..
>
> 
>
> 
>
>Polymer({
>
>is : 'a-card',
>
>properties : {
>
>que : Object
>
>},
>
>_ans : function(ans, que) {
>
>return 'xx_' + ans + que.queNum;
>
>}
>
>
> });
>
>
> function validate(option) {
>
>console.log(option);
>
>};
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 
>
>
>
>
> 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/a8b38417-1728-4544-a39a-f17d45f2adda%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/CAAUAVAj3zeqY421VV%3DYMXZKdO7-E-7vWV_t-nnyWtTUBmFXr0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Fastclick needed?

['Daniel Freedman' via Polymer]

Can you be more specific about how the tap event is not working for you?
Can you file a github issue with stepa to reproduce the issue? Ideally a
very small sample app that demonstrates what you're seeing.
Thanks!
On Sep 10, 2015 10:24 AM,  wrote:

> 'on-tap' doesn't work on Mac Safari. Is there a graceful workaround for
> this?
>
> 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/4c5cf02d-d80d-4f0a-b174-1ccbfc164478%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/CAAUAVAiyTWL%2BKY7oFCoisOxrkQrAHSrzKPj%3DOtT55cLxgRD4Mw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Meteor - Polymer - Bower issues

['Daniel Freedman' via Polymer]

Polymer/core-elements is all Polymer 0.5x elements

You want PolymerElements/iron-elements

On Wed, Aug 19, 2015 at 2:54 PM, paul.darmantc...@gmail.com wrote:

 Hi guys,

 Having a few issues that I could use some help with. I have decided to use
 meteor + polymer on my next app.

 1. Pretty new to Meteor
 2. Brand new to Polymer

 Deploying Meteor as you likely know is a breeze. Polymer in my experience
 has been less of a breeze :)

 I have tried to go through the current available examples but they're all
 based on Polymer 0.5.x I am hoping to use the production 1.1 release and I
 think that's the problem I am having.

 I am trying to use Bower as it appears to be the recommended way of
 setting up Polymer but I'm running in to a few issues.

 I have a .bowerrc file in my app folder with the following content:

 {directory:public/components/}

 From what I understand that's the recommended way of working with meteor
 and polymer.

 The problem arises mainly when I try to install Polymer

 bower install --save Polymer/polymer  - no problems, pulls in polymer 1.1
 in to /public/components as configured.

 problem starts here: bower install --save Polymer/core-elements
 -- at this step it finds multiple webcomponentsjs version and makes me
 chose between different ones as some elements have different versions
 listed as dependencies
 -- it also creates a second folder /public/public/components with the
 core-* elements in there.

 try to run bower install --save Polymer/iron-elements resolves to a non
 existing repository.

 Having had to learn so much in such a short time on both meteor and
 polymer I'm sure it's just jumbled in my mind. If someone could help out
 with a couple of clear steps on deploying a sample polymer + meteor app
 from scratch (with version 1 for production) that would be much appreciated!

 Thanks in advance.

 Paul

 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/ad5f7363-4a38-4c9d-a011-85fa9a590562%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/ad5f7363-4a38-4c9d-a011-85fa9a590562%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/CAAUAVAhEPJ%3D9ZMNN_h2UZ1YftE2Fdi9J5MU26%2BL6LXq%3DbqUfYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[polymer-dev] Re: iron-list scroll interaction with child element tap

['Daniel Freedman' via Polymer]

This is fixed in master with https://github.com/Polymer/polymer/pull/2134,
and will be released with the next version of Polymer.

On Wed, Jul 29, 2015 at 10:35 AM, Emmanuel Garcia egarc...@google.com
wrote:

 Hey Jim,

 It sounds like an issue, I can repro this issue.  What do you think Dan?

 On Tuesday, July 28, 2015 at 4:48:07 AM UTC-7, Jim Trainor wrote:

 I created an iron-list that has a paper-ripple, with a tap event handler,
 on each child list element. On desktop browsers the scroll action and tap
 actions are distinct so I can scroll the list without causing ripples and
 tap events on list items.  On touch devices I cannot scroll the list
 without also triggering ripple animations and tap events on the list items
 at the point where the scroll gesture starts on the iron-list.

 The tap event on the list element is undesirable when the touch was for
 the purpose of scrolling the list (i.e. was actually a swipe).

 I don't have much experience with these sort of issues and I'm not sure
 if this something that needs to be improved in Polymer or if this is
 something that I sort out in my own application. Anyone have any thoughts?







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/CAAUAVAidvt%2B5d7Ksq4U5bXQca-UBtCB7K5Pg96biXqNy3%3Dzi7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[polymer-dev] Re: iron-list scroll interaction with child element tap

['Daniel Freedman' via Polymer]

Oh, this might be seperate, since that PR is for the track gesture.

You can disable all gestures on vertical scrollable areas by using this
API: element.setScrollDirection('y'), and horizontal with
setScrollDirection('x')
Without that, I can't tell if your touches are for scrolling or gestures.

On Wed, Jul 29, 2015 at 10:46 AM, Daniel Freedman dfre...@google.com
wrote:

 This is fixed in master with https://github.com/Polymer/polymer/pull/2134,
 and will be released with the next version of Polymer.

 On Wed, Jul 29, 2015 at 10:35 AM, Emmanuel Garcia egarc...@google.com
 wrote:

 Hey Jim,

 It sounds like an issue, I can repro this issue.  What do you think Dan?

 On Tuesday, July 28, 2015 at 4:48:07 AM UTC-7, Jim Trainor wrote:

 I created an iron-list that has a paper-ripple, with a tap event
 handler, on each child list element. On desktop browsers the scroll action
 and tap actions are distinct so I can scroll the list without causing
 ripples and tap events on list items.  On touch devices I cannot scroll the
 list without also triggering ripple animations and tap events on the list
 items at the point where the scroll gesture starts on the iron-list.

 The tap event on the list element is undesirable when the touch was for
 the purpose of scrolling the list (i.e. was actually a swipe).

 I don't have much experience with these sort of issues and I'm not sure
 if this something that needs to be improved in Polymer or if this is
 something that I sort out in my own application. Anyone have any thoughts?








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

Re: [polymer-dev] Skip Safari when running web-component-tester

['Daniel Freedman' via Polymer]

Answered on StackOverflow:
https://stackoverflow.com/questions/31619457/skip-safari-when-running-web-component-tester/31660651#31660651

On Sun, Jul 26, 2015 at 2:04 PM, Sam Carpenter jetcity...@gmail.com wrote:

 I am trying to work around the known Safari issue in the Selenium Safari
 driver:

 https://github.com/SeleniumHQ/selenium/issues/631

 Until there is a new build of the Safari driver I would like to skip
 Safari when running web-component-tester. Is there a way to do that?

 I am working with the polymer-starter-kit 1.0.3 and using gulp test:local
 to run the tests. I found some configuration information on the
 web-component-tester regarding plugins but I am not sure the information
 applies to Polymer 1.0.

 I asked this same question on StackOverflow a few days ago but there has
 been no response:


 http://stackoverflow.com/questions/31619457/skip-safari-when-running-web-component-tester


 Any suggestions would be greatly appreciated.

 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/75af203d-6d32-45a3-b83c-3fab2b6289da%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/75af203d-6d32-45a3-b83c-3fab2b6289da%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/CAAUAVAhptH%3DNt_%3DOvyU8iAKOqpiNSVdLx534FeTAN9y32v-f_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Error! : Listener method not defined

['Daniel Freedman' via Polymer]

Looks like your firebase element is not in the template, and therefore
won't be in this.$
On Jul 22, 2015 9:45 PM, Himali Kiran mybut...@gmail.com wrote:

 Thank you so much,
 But if I remove curly braces it gives another error:

 Uncaught TypeError: Cannot read property 'login' of undefined

 I made following changes:

  firebase-auth id=baseLogin user={{user}}
 statusKnown={{statusKnown}}

   location=https://himalikiran.firebaseio.com; provider=github
 on-login=onLogin

   on-error=onLoginError/firebase-auth


   template

 paper-menu-button

 paper-icon-button icon=social:person
 class=dropdown-trigger/paper-icon-button

   paper-menu class=dropdown-content

   paper-item on-tap=login hidden?={{!statusKnown ||
 user}}Login/paper-item

   paper-item on-tap=logout hidden?={{!statusKnown ||
 !user}}Logout/paper-item

   /paper-menu

 /paper-menu-button

   /template



 On Thursday, 23 July 2015 09:35:30 UTC+5:45, Daniel Freedman wrote:

 Polymer 1.0 event handlers don't use the curly brace syntax. Just
 on-login=onLogin and all the others as well.
 On Jul 22, 2015 8:47 PM, Himali Kiran mybu...@gmail.com wrote:

 I am getting following error.
 [firebase-login::_createEventHandler]: listener method `{{login}}` not
 defined

 Actual Code:

 dom-module id=firebase-login
   style
 :host {
   display: block;
 }
   /style
   firebase-auth id=baseLogin user={{user}}
 statusKnown={{statusKnown}}
   location=https://himalikiran.firebaseio.com; provider=github
 on-login={{onLogin}}
   on-error={{onLoginError}}/firebase-auth

   template
 paper-menu-button
 paper-icon-button icon=social:person
 class=dropdown-trigger/paper-icon-button
   paper-menu class=dropdown-content
   paper-item on-tap={{login}} hidden?={{!statusKnown
 || user}}Login/paper-item
   paper-item on-tap={{logout}}
 hidden?={{!statusKnown || !user}}Logout/paper-item
   /paper-menu
 /paper-menu-button
   /template
   template if={{user}}{{user.github.username}}/template
 /dom-module

 script
 (function() {
   Polymer({
 is: 'firebase-login',

 properties: {

 },

 login : function(){
   console.log('working');
   this.$.baseLogin.login();
 },
 logout : function() {
   this.$.baseLogin.logout();
 }
   });
 })();
 /script

  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 view this discussion on the web visit
 https://groups.google.com/d/msgid/polymer-dev/7c418074-23f8-4405-bef5-88ac9a23dd44%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/7c418074-23f8-4405-bef5-88ac9a23dd44%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/CAAUAVAjKc%3DPjq45PkwRZLoHPVm6UhDK5%2B5_FxV5jHcHSUO53LQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Error! : Listener method not defined

['Daniel Freedman' via Polymer]

Polymer 1.0 event handlers don't use the curly brace syntax. Just
on-login=onLogin and all the others as well.
On Jul 22, 2015 8:47 PM, Himali Kiran mybut...@gmail.com wrote:

 I am getting following error.
 [firebase-login::_createEventHandler]: listener method `{{login}}` not
 defined

 Actual Code:

 dom-module id=firebase-login
   style
 :host {
   display: block;
 }
   /style
   firebase-auth id=baseLogin user={{user}}
 statusKnown={{statusKnown}}
   location=https://himalikiran.firebaseio.com; provider=github
 on-login={{onLogin}}
   on-error={{onLoginError}}/firebase-auth

   template
 paper-menu-button
 paper-icon-button icon=social:person
 class=dropdown-trigger/paper-icon-button
   paper-menu class=dropdown-content
   paper-item on-tap={{login}} hidden?={{!statusKnown
 || user}}Login/paper-item
   paper-item on-tap={{logout}} hidden?={{!statusKnown
 || !user}}Logout/paper-item
   /paper-menu
 /paper-menu-button
   /template
   template if={{user}}{{user.github.username}}/template
 /dom-module

 script
 (function() {
   Polymer({
 is: 'firebase-login',

 properties: {

 },

 login : function(){
   console.log('working');
   this.$.baseLogin.login();
 },
 logout : function() {
   this.$.baseLogin.logout();
 }
   });
 })();
 /script

  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/7c418074-23f8-4405-bef5-88ac9a23dd44%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/7c418074-23f8-4405-bef5-88ac9a23dd44%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/CAAUAVAhJfV%2BjuhOCbVLQncWUE3Lnx5FW%2BAdGbwLVquxn7twJwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Using distributed node inside a repeat

['Daniel Freedman' via Polymer]

That won't work because of how distribution with content works.
Distributed nodes will fill the first content they match, so your example
will have all distributed nodes appear in the first list item. You either
have to decorate the nodes for distribution (put a unique class on each
item and use content select=.uniqueClass-%item number% in your
dom-repeat), or manually move the nodes.

You might want to rethink this design. Maybe it would be easier to wrap
each node you want in this list in a ul higher up, and just have
licontent/content/li where you have this dom-repeat.

On Mon, Jul 20, 2015 at 10:52 AM, e3satterwh...@gmail.com wrote:

 Is it possible to use a content block inside of a dom-repeat, say for
 example, in a repeating list, to be able to inject some parts of list items?


 template is=dom-repeat items={{items}}
   ul
 li{{item}}content/content/li
   /ul
 /template

 It seems like the content is always and only inserted into the first item.
 Is there a better way to accomplish this?

 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/33a1a8b4-e6e3-4f04-8402-6e66c9300a9b%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/33a1a8b4-e6e3-4f04-8402-6e66c9300a9b%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/CAAUAVAgv9urjHE8Rw%3DMajRK%2BfjS4218TT3dTYx8eQV%3DucykoRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Redefining a Polmer element at runtime

['Daniel Freedman' via Polymer]

No component definitions are write-once for now (
https://github.com/w3c/webcomponents/issues/152). There are ideas for v2 to
have CustomElement registries exposed and modifiable, but no concrete
proposals as far as I know.

On Mon, Jul 20, 2015 at 6:49 AM, phil cleaver gigglestheth...@gmail.com
wrote:

 Hi,

 I'm writing an IDE for web components and I'm trying to find a way of
 changing the definition of a web component at runtime.  If I try to
 reregister the element I simply get a message that a component with this
 name already exists.

 Is there a way to remove a web component definttion from the document so I
 can reload it?

 Regards

 Phil

 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/c51868db-5606-4ae7-ab5e-9bbb61a52f44%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/c51868db-5606-4ae7-ab5e-9bbb61a52f44%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/CAAUAVAg%2BqbuGoM5L5pkis4KsFFysx%2B-6ZKymPYS6jG8_EFNAeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] When do I have to call flush() in wct?

['Daniel Freedman' via Polymer]

Generally you can get away with not using flush.

You may still need flush for testing element lifecycle callbacks in
polyfilled browsers, or measuring DOM, but I expect very few cornercases
like that.

On Thu, Jul 16, 2015 at 10:46 AM, aro...@flux.io wrote:

 With Polymer 1.0, observers are now evaluated synchronously.  If I have an
 element whose behavior is driven by observers on attributes, and everything
 appears to work in synchronous tests, is there any reason to call flush()?
 That is, is it necessary that I call it before/after each test?

 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/adc4db0a-459d-4abf-ab8f-6453dae62213%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/adc4db0a-459d-4abf-ab8f-6453dae62213%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/CAAUAVAhtWUNOMEw8Zm2Nq5JVA0Q4ihDEtgPJ4pDjRVqZHk1ENA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Polybuild not available with npm

['Daniel Freedman' via Polymer]

Fixed with
https://github.com/PolymerLabs/polybuild/commit/cfbbc4182ac93ec49e10b96d3bec84f2af2c4880
in version 1.0.2

On Sat, May 23, 2015 at 10:10 AM, Adrian Aioanei 
adrian.aioa...@ayonesoftware.com wrote:

 Ran npm install -g polybuild but seems it's not recognised.
 Running polybuild --maximum-crush index.html issues:
 -bash: polybuild: command not found

 Thanks for your help!

 On Saturday, May 23, 2015 at 12:46:14 AM UTC+3, Daniel Freedman wrote:

 It wasn't quite ready to ship yesterday. I have published it into npm
 today however.

 On Fri, May 22, 2015 at 1:58 AM, Adrian Aioanei 
 adrian@ayonesoftware.com wrote:

 Running:
 npm install -g polybuild

 issues:
 npm http GET https://registry.npmjs.org/polybuild
 npm http 404 https://registry.npmjs.org/polybuild
 npm ERR! 404 404 Not Found: polybuild
 npm ERR! 404
 npm ERR! 404 'polybuild' is not in the npm registry.
 npm ERR! 404 You should bug the author to publish it
 npm ERR! 404
 npm ERR! 404 Note that you can also install from a
 npm ERR! 404 tarball, folder, or http url, or git url.

 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 view this discussion on the web visit
 https://groups.google.com/d/msgid/polymer-dev/c33e46d6-5e5f-4d41-acae-44e0deb342f1%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/c33e46d6-5e5f-4d41-acae-44e0deb342f1%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/11dbfee5-082a-4a73-b711-58155fbf44c9%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/11dbfee5-082a-4a73-b711-58155fbf44c9%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/CAAUAVAh0tZDxAd8qSNhV8WHqVPJkSPspeVEQ76%3DvLxmumwR_Ng%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Polybuild not available with npm

['Daniel Freedman' via Polymer]

It wasn't quite ready to ship yesterday. I have published it into npm today
however.

On Fri, May 22, 2015 at 1:58 AM, Adrian Aioanei 
adrian.aioa...@ayonesoftware.com wrote:

 Running:
 npm install -g polybuild

 issues:
 npm http GET https://registry.npmjs.org/polybuild
 npm http 404 https://registry.npmjs.org/polybuild
 npm ERR! 404 404 Not Found: polybuild
 npm ERR! 404
 npm ERR! 404 'polybuild' is not in the npm registry.
 npm ERR! 404 You should bug the author to publish it
 npm ERR! 404
 npm ERR! 404 Note that you can also install from a
 npm ERR! 404 tarball, folder, or http url, or git url.

 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/c33e46d6-5e5f-4d41-acae-44e0deb342f1%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/c33e46d6-5e5f-4d41-acae-44e0deb342f1%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/CAAUAVAi29umXbLn9fab6kyMN5vcgpYj7bGR3Y7mfqqZkM6Lwnw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Referring to an Apple Documentation

['Daniel Freedman' via Polymer]

Thanks for reminding me I wrote that. Good to see it is still there, thanks
for checking.

On Tue, Apr 14, 2015 at 5:43 AM, Joel Montealegre j...@sphereware.com
wrote:

 Hi,



 Just to let you know.
 https://www.polymer-project.org/0.5/docs/polymer/touch.html recommends a
 reference to the Apple Developer Documentation.



 For example, a simple finger paint app needs plenty of work to behave
 correctly with mouse and touch:

- Mouse events are only fired after the touch sequence ends.
- Mouse events are not fired on elements without a click event
handler. One must be attached by default, or directly on the element with
“onclick”.
- Click events are not fired if the content of the page changes in a
mousemove or mouseover event.
- Click events are fired 300ms after the touch sequence ends.
- More information: Apple Developer Documentation

 http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/HandlingEvents/HandlingEvents.html
.





 Regards.



 Joel

 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/BAY403-EAS3060AB30475D726447F9AA5A1E60%40phx.gbl
 https://groups.google.com/d/msgid/polymer-dev/BAY403-EAS3060AB30475D726447F9AA5A1E60%40phx.gbl?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/CAAUAVAjX4qbhPV5Q9m1Co9_V5N%2BJ%2B%2BuX5NJW8vY6jOhkU95nkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Vulcanize v1 factored out --csp. How-to now?

['Daniel Freedman' via Polymer]

I factored out the CSP component into a new project called crisper:
https://github.com/polymerlabs/crisper.

You can pipe the output of vulcanize through crisper to make separate JS
and HTML files:

vulcanize target.html | crisper --html build.html --js build.js

I'll put this into the README of vulcanize.

On Mon, Apr 13, 2015 at 8:38 AM, Eric Bidelman ebi...@gmail.com wrote:

 +Daniel Freedman dfre...@google.com

 On Mon, Apr 13, 2015 at 7:32 AM Silver Techar silver.tec...@gmail.com
 wrote:

 Hi,

 How do you do following v.0.7 vulcanize command in the braeking v.1 ?

 My vulacnize v.0.7 command was: vulcanize -o ../build.html ../index.html
 --strip --csp

 where index.html looked something like

 !doctype html
 html
 head
  script src=all.js/script

 link rel=import
 href=bower_components/paper-input/paper-input.html
 ..etc..
 /head
 body
 x-app/x-app
 /body
 /html


 Ref: https://github.com/Polymer/vulcanize/blob/master/CHANGELOG.md

 Kr,
 Ainur

 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/75741b5b-51f8-4bbe-8f42-9ed85cbdbfbc%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/75741b5b-51f8-4bbe-8f42-9ed85cbdbfbc%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/CAAUAVAgw0jNx%3DuxewDN8T9F2uMz8yf4X9WMfgJH402N%2BdCtS1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Creating Custom/nested element-registries

['Daniel Freedman' via Polymer]

As far as I know, there is nothing in the spec as of yet to allow for user
defined registries. I believe this is planned for a later iteration of the
spec.
Spec bug about this topic:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24578

On Wed, Apr 1, 2015 at 2:36 PM, alessandro meyer alessandro.me...@gmail.com
 wrote:

 Hello There

 I've been trying to found out whether it is possible to create nested
 registries either through polymer or native web components. But the W3C
 Spec is not really explicit enough for me about it.


 http://w3c.github.io/webcomponents/spec/custom/#creating-and-passing-registries


 Says:
 *When creating a template contents owner document
 https://html.spec.whatwg.org/multipage/scripting.html#appropriate-template-contents-owner-document,
 use a new empty registry
 http://w3c.github.io/webcomponents/spec/custom/#dfn-registry.*

 How would I do that? My goal is to have scoped imports so elements never
 clash in the global scope. If there are other approaches to it I'm happy to
 give them a try.

 Thanks!
 Alessandro

 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/53c86322-eb32-4f23-84a3-0d2727d911bd%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/53c86322-eb32-4f23-84a3-0d2727d911bd%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/CAAUAVAgFCK3uv_NvR6W2ViinMRw1n22NeRGx6%2BAu6M0-U-sWZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Re: Indenting custom tags in Vim

['Daniel Freedman' via Polymer]

I use https://github.com/othree/html5.vim for syntax and use jshint as my
inline script linter with let g:syntastic_html_checkers=['jshint']. In my
opinion, html syntax checkers are at best obsolete with html5, as the
parser has a forgiving nature, as opposed to xhtml. At worst, the html
syntax checkers will not understand custom elements for a long time, to the
detriment of their utility.

On Tue, Feb 24, 2015 at 4:55 AM, Martin Kleinschrodt 
makles...@googlemail.com wrote:

 Thats awesome! I've recently switched over to vim, too and I've had a
 couple of problems working on Polymer components as well. My biggest issue
 is with Syntastic (or rather the included linters), which does not
 recognize custom element tags as valid html and fails to lint inline JS.
 I'm curious if there is anyone in the Polymer team who uses vim as their
 main editor and has some recommendations for optimizing the workflow with
 vim.

 On Monday, February 23, 2015 at 7:11:39 PM UTC+1, mich...@chromium.org
 wrote:

 So I've just begun switching to Vim after using emacs for six years. It's
 been rough but what really bugs me is how badly auto-indent fails with web
 components  custom elements. I tried using xml mode but that chokes on
 void elements.

 I've made a patch that adds support for template, shadow and
 content, as well as any-custom-tags, so that instead of this:

 section
   paper-dropdown-menu label=Your favorite pastry
   paper-dropdown class=dropdown
   core-menu class=menu
   template repeat={{pastries}}
   paper-item{{}}/paper-item
   /template
   /core-menu
   /paper-dropdown
   /paper-dropdown-menu
 /section


 vim will give you this:

 section
   paper-dropdown-menu label=Your favorite pastry
 paper-dropdown class=dropdown
   core-menu class=menu
 template repeat={{pastries}}
   paper-item{{}}/paper-item
 /template
   /core-menu
 /paper-dropdown
   /paper-dropdown-menu
 /section

 I've uploaded the updated html.vim here
 https://github.com/michaelpg/vim/blob/patch-1/runtime/indent/html.vim,
 which you can add to your vim/runtime/indent or $VIMFILES/indent/ to get
 this behavior.

 This is my first attempt at editing vimscript so use at your own risk! Of
 course if anyone has run into this issue before and come up with a better
 solution, please let me know.

 Thanks,
 Michael

  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/49b01e9e-a3f4-4333-91f0-18a73896fc9e%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/49b01e9e-a3f4-4333-91f0-18a73896fc9e%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/CAAUAVAgWeK-scYRfAfkXxR2sW9h_QK4ckqGr%3DRg4x171%2Bbd3Ag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Re: PSA: PointerEvents and PointerGestures are being replaced by polymer-gestures, breaking changes for pointer* events

['Daniel Freedman' via Polymer]

The polymer-gestures equivalent to touchstart is the down event.

On Tue, Feb 17, 2015 at 10:42 AM, Rob Dodson robdod...@google.com wrote:

 I'm guessing it's `down` but +dfreedman can confirm

 On Sun, Feb 15, 2015 at 5:11 AM, Rich learn.moderndevelo...@gmail.com
 wrote:

 There is no reference to *touchstart*. What is the Polymer equivalent to
 *touchstart*?

 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/e8a19612-d744-40ef-9038-e0fe6d451fca%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/e8a19612-d744-40ef-9038-e0fe6d451fca%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/CAAUAVAi%3Dm2QSZKhG3NV6ezNxWNbp83nY15ff8ZSP%3DWjNTRi%2BOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Mixed line endings in Polymer source :'(

['Daniel Freedman' via Polymer]

Yeah all for that. The only task would be to go through all the components
and fix them up.

On Thu, Feb 12, 2015 at 8:37 PM, Rob Dodson robdod...@google.com wrote:

 gotta get on that .editorconfig train! http://editorconfig.org/

 On Thu, Feb 12, 2015 at 2:37 PM, 'Michael Giuffrida' via Polymer 
 polymer-dev@googlegroups.com wrote:

 Rietveld and/or the CQ cannot apply changes when the unified diff
 contains CRs. See discussion on chromium-dev:

 https://groups.google.com/a/chromium.org/d/msg/chromium-dev/u5KeH1lqDmY/ZzZTKdGa7IoJ

 We'll be adding a script to the tree to remove those line endings after
 bower install.

 On Thu, Feb 12, 2015 at 2:07 PM, Daniel Freedman dfre...@google.com
 wrote:

 None of our tools ever cared about line endings. What breaks about mixed
 line endings breaks the Chromium tree? Anything beyond some linter step?

 On Thu, Feb 12, 2015 at 2:02 PM, Elliott Sprehn espr...@gmail.com
 wrote:

 I blame Scott and his windows habit. :P

 On Thu, Feb 12, 2015 at 2:00 PM, 'Michael Giuffrida' via Polymer 
 polymer-dev@googlegroups.com wrote:

 Several Polymer files on GitHub (and when installed through bower) mix
 CRLF with LF, and it's making the Chromium tree sad.

 Example:
 https://github.com/Polymer/paper-checkbox/blob/master/paper-checkbox.css

 Polymer devs, why? https://i.imgflip.com/hkdgs.jpg

 Michael

 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_1RrSQEKzxGWhQPUzfqBSSFS6-SPkqjWDG9me9%2B05GhwA%40mail.gmail.com
 https://groups.google.com/d/msgid/polymer-dev/CACi5S_1RrSQEKzxGWhQPUzfqBSSFS6-SPkqjWDG9me9%2B05GhwA%40mail.gmail.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/CAPJYB1ieg5zD6f9_1Y%2BOW6gu%2B0xGJ6sMTi4B4Z0zHX48d8tzVw%40mail.gmail.com
 https://groups.google.com/d/msgid/polymer-dev/CAPJYB1ieg5zD6f9_1Y%2BOW6gu%2B0xGJ6sMTi4B4Z0zHX48d8tzVw%40mail.gmail.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/CACi5S_0QC7qSaawkgUWmRyn5kYeh8TA5dwEQCh%3DDwxBuy3xpSA%40mail.gmail.com
 https://groups.google.com/d/msgid/polymer-dev/CACi5S_0QC7qSaawkgUWmRyn5kYeh8TA5dwEQCh%3DDwxBuy3xpSA%40mail.gmail.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/CAAUAVAgOfppyFM4QKHzOP7czkfGZomRAh6fMBHRoQQ3SmS0inw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] my core-a11y-keys implementation not working

['Daniel Freedman' via Polymer]

This is missing an example of the actual instance of your `rappets-redbull`
element, but my guess would be that your instance does not receive focus.
The `core-a11y-keys` element is active only when the target element is
focused.

On Sun, Nov 23, 2014 at 10:28 AM, Jahlom Agboado jahl...@gmail.com wrote:

 The following code is my implementation of core-a11y-keys but is not
 working. What I'm I doing wrong?


 link rel=import href=polymer/polymer/polymer.html
 link rel=import href=polymer/core-a11y-keys/core-a11y-keys.html

 polymer-element name=rappts-redball
   template
   style
   :host {
 width: 50px;
 height: 50px;
 border-radius: 50px;
 background-color: red;
 position: absolute;
 bottom: 0px;
   }
   :host #output {
   position: absolute;
 top: -47px;
   }
 /style
 core-a11y-keys target={{}} keys=up pageup
 on-keys-pressed={{moveUp}}/core-a11y-keys
 pre id=output/pre
   /template
   script
 Polymer('rappts-redball', {

 moveUp: function(event) {
 this.$.output.textContent += event.detail.key + ' pressed!\n';
 console.log(event);
   }
 });
   /script
 /polymer-element

 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/CAGB-B9fLu_UhQf4o%2BA3_as7RqYZvCAA2zFF9T8-uBB9otnvBLw%40mail.gmail.com
 https://groups.google.com/d/msgid/polymer-dev/CAGB-B9fLu_UhQf4o%2BA3_as7RqYZvCAA2zFF9T8-uBB9otnvBLw%40mail.gmail.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/CAAUAVAjc1WmbzoDmVvJtNsQWtkBgCT1SGuQmvwriiA6mazjE2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Prevent click event after tap

['Daniel Freedman' via Polymer]

Ah OK. I can only seem to reproduce this in Chrome for iOS, probably a
UIWebView specific issue (at least on ios8). At least I have a case to test
against now. Thanks!

On Tue, Oct 28, 2014 at 12:43 AM, Akhilesh akhilesh.i...@gmail.com wrote:

 Seems like that JSBin sample expired as it was on anonymous account. Just
 created a new one: http://jsbin.com/zidaqa/3

 I am able to trigger the focus bug when I run it inside the chrome browser
 on iOS 8. This is essentially an issue on UIWebView but not on iOS8 Safari.
 Let me know if you can't reproduce it.


 On Mon Oct 27 2014 at 5:46:21 PM Daniel Freedman dfre...@google.com
 wrote:

 Hey Akhilesh.

 I've been playing with your example and I can't seem to trigger the focus
 bug on iOS 8. Are you only seeing this on iOS 7?

 On Fri, Oct 24, 2014 at 10:56 AM, Akhilesh akhilesh.i...@gmail.com
 wrote:

 Thanks Daniel. Let me know once you have something that I can play with.

 On Thu, Oct 23, 2014 at 6:19 PM, Daniel Freedman dfre...@google.com
 wrote:

 Yeah this seems like a pretty valid use case to fix in the gesture
 system. I'll investigate this for the next release.
 On Oct 22, 2014 9:19 AM, Akhilesh akhilesh.i...@gmail.com wrote:

 Apologies for delayed response. Was kind of heads down with the
 Dreamforce prep and polymer demos, which were just awesome!

 Coming back to the preventDefault problem, I was able to create a
 simple sample that shows the issue. Try this link on Chrome on iOS:
 http://jsbin.com/mogusutono
 Source: http://jsbin.com/mogusutono/edit?html

 When you click the button, the view navigates to next page with the
 paper-input element. And on the next page, paper-input automatically
 receives a focus event and and keyboard pops up. Not ideal. I am able to
 work-around this by listening for touch-end event after the tap and then
 calling event.preventDefault. Would be better if tap event could handle
 this automatically for me. This also seems to only happen inside the
 UIWebView and not the iOS Safari.

 Let me know if you guys need more details. Hope this helps!

 On Thu, Oct 2, 2014 at 9:59 AM, Steve Orvell sorv...@google.com
 wrote:

 Hey Akhilesh,

 Can you outline why you'd like to prevent clicks? Is it because some
 other user code may have installed a click listener you want to avoid or 
 is
 it some native platform action (e.g. following a link) that you want to
 abort?

 It would be great if you could just preventDefault in the tap event,
 unfortunately, tap is generated separately from click and is typically
 fired after it.

 As Daniel mentioned, we're investigating providing a relatively easy
 way to do this in PolymerGestures.

 On Thu, Oct 2, 2014 at 8:57 AM, 'Daniel Freedman' via Polymer 
 polymer-dev@googlegroups.com wrote:

 Hi Akhilesh

 We don't currently have a strategy to prevent clicks. I can take a
 look at what that would entail.

 Touch-action is only supposed to control scrolling and zoom, so
 making the none value control clicks as well is a little outside the
 intended scope.

 What you can do for now is place a document wide, capturing click
 listener that calls stopPropagation inside the up event handler, and 
 then
 remove that click handler when a click happens, or after a timeout. 
 This is
 the approach I am planning to evaluate.
 I have been trying to figure out an easier way to prevent click
 events from an element that listens for tap. This is more of an issue on
 touch devices (iOS in particular). Here's an example:
 http://jsbin.com/totuhoveguke/2/edit

 One solution is to attach another listener for touchend and then do
 event.preventDefault(). This causes weird side-effects which I want to
 avoid. Ideally my assumption was that when I am using touch-action =
 none, I will be able to avoid all default browser events.

 What's the best solution for such cases?


  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/6f3bb3d1-52cb-4b89-9424-2cfdec3139f2%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/6f3bb3d1-52cb-4b89-9424-2cfdec3139f2%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/CAAUAVAgfxq6JQDX%2Bev%2BPtbuo48a2D780rZLP2VpQ_AJBujUxEQ%40mail.gmail.com
 https://groups.google.com/d/msgid/polymer-dev/CAAUAVAgfxq6JQDX%2Bev

Re: [polymer-dev] Prevent click event after tap

['Daniel Freedman' via Polymer]

Hey Akhilesh.

I've been playing with your example and I can't seem to trigger the focus
bug on iOS 8. Are you only seeing this on iOS 7?

On Fri, Oct 24, 2014 at 10:56 AM, Akhilesh akhilesh.i...@gmail.com wrote:

 Thanks Daniel. Let me know once you have something that I can play with.

 On Thu, Oct 23, 2014 at 6:19 PM, Daniel Freedman dfre...@google.com
 wrote:

 Yeah this seems like a pretty valid use case to fix in the gesture
 system. I'll investigate this for the next release.
 On Oct 22, 2014 9:19 AM, Akhilesh akhilesh.i...@gmail.com wrote:

 Apologies for delayed response. Was kind of heads down with the
 Dreamforce prep and polymer demos, which were just awesome!

 Coming back to the preventDefault problem, I was able to create a simple
 sample that shows the issue. Try this link on Chrome on iOS:
 http://jsbin.com/mogusutono
 Source: http://jsbin.com/mogusutono/edit?html

 When you click the button, the view navigates to next page with the
 paper-input element. And on the next page, paper-input automatically
 receives a focus event and and keyboard pops up. Not ideal. I am able to
 work-around this by listening for touch-end event after the tap and then
 calling event.preventDefault. Would be better if tap event could handle
 this automatically for me. This also seems to only happen inside the
 UIWebView and not the iOS Safari.

 Let me know if you guys need more details. Hope this helps!

 On Thu, Oct 2, 2014 at 9:59 AM, Steve Orvell sorv...@google.com wrote:

 Hey Akhilesh,

 Can you outline why you'd like to prevent clicks? Is it because some
 other user code may have installed a click listener you want to avoid or is
 it some native platform action (e.g. following a link) that you want to
 abort?

 It would be great if you could just preventDefault in the tap event,
 unfortunately, tap is generated separately from click and is typically
 fired after it.

 As Daniel mentioned, we're investigating providing a relatively easy
 way to do this in PolymerGestures.

 On Thu, Oct 2, 2014 at 8:57 AM, 'Daniel Freedman' via Polymer 
 polymer-dev@googlegroups.com wrote:

 Hi Akhilesh

 We don't currently have a strategy to prevent clicks. I can take a
 look at what that would entail.

 Touch-action is only supposed to control scrolling and zoom, so making
 the none value control clicks as well is a little outside the intended
 scope.

 What you can do for now is place a document wide, capturing click
 listener that calls stopPropagation inside the up event handler, and 
 then
 remove that click handler when a click happens, or after a timeout. This 
 is
 the approach I am planning to evaluate.
 I have been trying to figure out an easier way to prevent click events
 from an element that listens for tap. This is more of an issue on touch
 devices (iOS in particular). Here's an example:
 http://jsbin.com/totuhoveguke/2/edit

 One solution is to attach another listener for touchend and then do
 event.preventDefault(). This causes weird side-effects which I want to
 avoid. Ideally my assumption was that when I am using touch-action =
 none, I will be able to avoid all default browser events.

 What's the best solution for such cases?


  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/6f3bb3d1-52cb-4b89-9424-2cfdec3139f2%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/6f3bb3d1-52cb-4b89-9424-2cfdec3139f2%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/CAAUAVAgfxq6JQDX%2Bev%2BPtbuo48a2D780rZLP2VpQ_AJBujUxEQ%40mail.gmail.com
 https://groups.google.com/d/msgid/polymer-dev/CAAUAVAgfxq6JQDX%2Bev%2BPtbuo48a2D780rZLP2VpQ_AJBujUxEQ%40mail.gmail.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/CAAUAVAhhHAHTD_nCU0-9qe8Vcw_aAQWEPMexM%3DBJpOrVCs1LBQ%40mail.gmail.com.
For more options, visit https

Re: [polymer-dev] Minifies HTML issue with

['Daniel Freedman' via Polymer]

collapseBooleanAttributes should be false since selected is considered a
boolean attribute:
http://perfectionkills.com/experimenting-with-html-minifier/#collapse_boolean_attributes

On Thu, Oct 23, 2014 at 11:13 AM, ignacio.manz...@gmail.com wrote:

 Hi,

 Yes, sorry.

 Im using grunt as following

htmlmin: {
   dist: {
 options: {
   collapseWhitespace: true,
   conservativeCollapse: true,
   collapseBooleanAttributes: true,
   removeCommentsFromCDATA: true,
   removeOptionalTags: true,
   removeComments:true,
   minifyJS:true,
   minifyCSS:true
 },
 files: [{
   expand: true,
   cwd: '%= yeoman.dist %',
   src: ['*.html', 'views/{,*/}*.html'],
   dest: '%= yeoman.dist %'
 },{
 expand: true,
 cwd: '%= yeoman.dist %',
 src: [
 'bower_components/{,*/}core-overlay.html',
 'bower_components/{,*/}core-selector.html',
 'bower_components/{,*/}core-a11y-keys.html',
 'bower_components/{,*/}paper-ripple.html',
 'bower_components/{,*/}core-style.html',
 'bower_components/{,*/}core-iconset.html',
 'bower_components/{,*/}core-icons.html',
 'bower_components/{,*/}core-transition-css.html',
 'bower_components/{,*/}paper-shadow.html',
 'bower_components/{,*/}core-icon.html',
 'bower_components/{,*/}core-dropdown.html',
 /*'bower_components/{,*//*}paper-dialog.html',*/
 'bower_components/{,*/}core-selection.html',
 'bower_components/{,*/}core-iconset-svg.html',
 'bower_components/{,*/}core-collapse.html',
 'bower_components/{,*/}core-transition.html',
 'bower_components/{,*/}paper-icon-button.html',
 'bower_components/{,*/}paper-button.html',
 'bower_components/{,*/}core-meta.html',
 'bower_components/{,*/}paper-menu-button.html',
 'bower_components/{,*/}core-dropdown-overlay.html',
 'bower_components/{,*/}paper-focusable.html',
 /*'bower_components/{,*//*}paper-radio-button.html',*/
 'bower_components/{,*/}core-submenu.html',
 /*'bower_components/{,*//*}paper-checkbox.html',*/
 /*'bower_components/{,*//*}paper-item.html',*/
 'bower_components/{,*/}core-menu.html',
 'bower_components/{,*/}layout.html',
 'bower_components/{,*/}paper-menu-button-transition.html',
 'bower_components/{,*/}paper-button-base.html',
 'bower_components/{,*/}core-overlay-layer.html',
 'bower_components/{,*/}paper-radio-group.html',
 /*'bower_components/{,*//*}core-item.html',*/
 'bower_components/{,*/}core-icons.html',
 'bower_components/{,*/}polymer.html',
 'bower_components/{,*/}paper-dialog-transition.html',
 'bower_components/{,*/}core-key-helper.html',
 'bower_components/{,*/}web-animations.html',
 /*'bower_components/{,*//*}core-header-panel.html',*/
 //'bower_components/{,*/}core-drawer-panel.html',
 'bower_components/{,*/}core-toolbar.html',
 'bower_components/{,*/}core-media-query.html',
 /*'bower_components/{,*//*}paper-dropdown-menu.html',*/
 'bower_components/{,*/}core-range.html',
 'bower_components/{,*/}paper-progress.html'
 /*'bower_components/{,*//*}core-input.html',*/
 /*'bower_components/{,*//*}paper-input.html'*/],
 dest: '%= yeoman.dist %'
 }]
   }
 }

 Just when I copied the text I realize that the issue is with  
 collapseBooleanAttributes:
 true,

 Sorry for the inconveniences.

 Best Regards,
 Ignacio


 On Thursday, October 23, 2014 2:56:45 PM UTC-3, Eric Bidelman wrote:

 Can you be more specific on the minifier you're using? It shouldn't trip
 out attribute values from the markup.

 On Thu, Oct 23, 2014 at 10:46 AM, ignacio...@gmail.com wrote:

 Hi,


 If my code use some polymer elements that have attribute like
 select='something' and I try to minify my file, the generate html file is
 broken. How ?

 If I have

 {code}
 core-selector selected=tab1 horizontal justified layout center
 
 /core-selector
 {code}

 the minify version is

 {code}
 core-selector selected horizontal justified layout
 center/core-selector
 {code}

 is there a way to specify not to resolver the select attribute ?
 If I modify the polymer element and change selected to selectedElement
 or another name it work without problem.

 Today minify my html and polymer elements are crucial because my page
 use 

Re: [polymer-dev] Prevent click event after tap

['Daniel Freedman' via Polymer]

Hi Akhilesh

We don't currently have a strategy to prevent clicks. I can take a look at
what that would entail.

Touch-action is only supposed to control scrolling and zoom, so making the
none value control clicks as well is a little outside the intended scope.

What you can do for now is place a document wide, capturing click listener
that calls stopPropagation inside the up event handler, and then remove
that click handler when a click happens, or after a timeout. This is the
approach I am planning to evaluate.
I have been trying to figure out an easier way to prevent click events from
an element that listens for tap. This is more of an issue on touch devices
(iOS in particular). Here's an example: http://jsbin.com/totuhoveguke/2/edit

One solution is to attach another listener for touchend and then do
event.preventDefault(). This causes weird side-effects which I want to
avoid. Ideally my assumption was that when I am using touch-action =
none, I will be able to avoid all default browser events.

What's the best solution for such cases?


 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/6f3bb3d1-52cb-4b89-9424-2cfdec3139f2%40googlegroups.com
https://groups.google.com/d/msgid/polymer-dev/6f3bb3d1-52cb-4b89-9424-2cfdec3139f2%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/CAAUAVAgfxq6JQDX%2Bev%2BPtbuo48a2D780rZLP2VpQ_AJBujUxEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Re: how to make polymer components accessible?

['Daniel Freedman' via Polymer]

Hi Steve and John,

I've filed https://github.com/Polymer/paper-elements/issues/17 to track
making all of the demos for the paper elements, and the demo app itself,
keyboard accessible.

I admit that IE11 on Windows has not been a primary area of focus for
screen reader support. I should probably requisition a set of popular
screen readers for Windows to do some manual testing soon.


On Sat, Sep 27, 2014 at 12:57 PM, cov...@ccs.covici.com wrote:

 So how can we make our pages usable that way?  Should we use native
 input elements instead of paperinput?

 Steve Faulkner faulkner.st...@gmail.com wrote:

  Hi John
 
  On Saturday, 27 September 2014 12:05:48 UTC+1, John Covici wrote:
  
   But were you able to locate the input field using the arrow keys while
   browse mode was on and press enter to turn browse mode off on the edit
   fields? Right now the edit fields are not recognized at all.
  
 
  I was unable to successfully navigate or use the paper element demo page.
  iI tried with NVDA in Firefox and IE and window eyes in IE and Firefox.
  Unless I am missing something The demo page(s) navigation menu items are
  not exposed as interactive element and are not focusable. The demo pages
 do
  not include basic semantic structures such as headings, lists etc, which
  make it very difficult to use with a screen reader (or indeed with the
  keyboard alone).
 
 
  
   Steve Faulkner faulkne...@gmail.com javascript: wrote:
  
   

 Would the fact that we have the animated-pages component in there
 make
 any difference?

   
I just did some quick testing on the paper input demo page:
   
Using Window Eyes 8.4 and IE 11 I was able to navigate to the text
   inputs
(using either the tab key or the E shortcut key) and they worked as
expected most of the time. Window eyes exhibited some superfluous
announcements one frame repeatedly.
   
Note: I am a sighted user and placed focus on the first text input
 using
the mouse, then used keyboard after that.
   
   
On Saturday, 27 September 2014 09:29:05 UTC+1, John Covici wrote:


 Steve Faulkner faulkne...@gmail.com javascript: wrote:

  Hi John,
 
  reviewing the code of the paper input elements demo
  (

  
 http://www.polymer-project.org/components/paper-elements/demo.html#paper-input
 )
  

  they use an input type=text in the shadow DOM, and this gets
   exposed
  correctly in the accessibility tree, so not sure what the cause
 of
   the
  issue is you are experiencing.
 
  On Friday, 26 September 2014 21:15:03 UTC+1, John Covici wrote:
  
   The version of Window-eyes I am using does support aria, at
 least
   as
 far
   as I have been able to figure out.  It is not  public
 version.  I
   am
   using ie11.  I wonder if we should use native input instead of
   paper-input?
  
   Steve Faulkner faulkne...@gmail.com javascript: wrote:
  
Hi John,
   
I think you may be encountering a number of issues:
1. accessibility support in polymer UI components is half
 baked
2. Window Eyes support for ARIA is half baked
3. if you are using IE...
   
If possible try Firefox and NVDA, it won't solve the polymer
 UI
 issues
   but
will give you best chance at making use of accessibility
 polymer
 does
   have
implemented.
   
   
On Friday, 26 September 2014 20:31:17 UTC+1, John Covici
 wrote:

 I am using Window-eyes.

 Steve Faulkner faulkne...@gmail.com javascript: wrote:

  Hi John,
 
  can I ask what screen reader are you using?
 
  On Friday, 26 September 2014 19:40:50 UTC+1, John Covici
   wrote:
  
   I am a newbie at Polymer, so please bear with me.  I am
 involved
   in a
   project whose website uses some of your components and
 I
   would
   like to
   make it accessible -- right now it is not really
   accessible.
  \so
   I
   tried to get the starter project going  by copying the
   finish
   folder
 to
   a Linux server I have, but all I get is something which
   says
 all
   favorites.
  
   Thanks in advance for any suggestions.
  
   --
   Your life is like a penny.  You're going to lose it.
 The
 question
   is:
   How do
   you spend it?
  
John Covici
cov...@ccs.covici.com javascript:
  
 
  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 

Re: [polymer-dev] Re: Polymer app very unstable in mobile safari (iOS 7)

['Daniel Freedman' via Polymer]

Martin, I've nailed down a workaround for iOS in
https://github.com/Polymer/polymer-gestures/pull/57.

I'll make a new build of polymer in the master branch if you'd like to test
with it.

Thanks for your patience!

On Fri, Sep 5, 2014 at 12:14 PM, Martin Kleinschrodt 
makles...@googlemail.com wrote:

 Thanks Daniel, thats great to hear. Any idea on how long this might take
 to fix? Meanwhile, can you think of a possible workaround?

 On 5. September 2014 at 02:38:55, Daniel Freedman (dfre...@google.com)
 wrote:

 Hi Martin,

 I've identified what I believe to be the root cause (touchevents on nodes
 stamped from a template + edge case timing of the removal of a node that is
 a tap target) and reported the crash case to Apple (
 https://bugs.webkit.org/show_bug.cgi?id=136506)

 The fix in Polymer is going to take me some more time to complete.

 In the mean time, I've filed
 https://github.com/Polymer/polymer-gestures/issues/56 to track for myself.

 Thanks!


 On Thu, Sep 4, 2014 at 1:06 AM, Martin Kleinschrodt 
 makles...@googlemail.com wrote:

  Thanks, guys! I really appreciate the help. Glad, Daniel could
 reproduce this and it's not something stupid I did.

  For what it's worth, I think your analysis is pretty spot on. It seems
 there is some race condition going on since the problem occurs only part of
 the time. All things considered, I now think the problem was most likely
 introduced in polymer-gestures since TemplateBinding didn't see a lot of
 changes between 0.3.4 and 0.3.5.

 On 3. September 2014 at 23:14:40, 'Daniel Freedman' via Polymer (
 polymer-dev@googlegroups.com) wrote:

   I was able to make a repro case just with templates and tap handlers.

 It looks like this error is triggered when the a node with a touch
 handler is being removed by a template model update while a touch event is
 being dispatched.

 Minimal repro: https://gist.github.com/azakus/72d2b7d1ffde1e94283a

 Since this seems related to template stamping timing, I'll have to sit
 down with the template polyfill authors to get a better understanding of
 the exact timing of the polyfill.

 Thanks for your patience.


 On Wed, Sep 3, 2014 at 10:23 AM, Daniel Freedman dfre...@google.com
 wrote:

 Hi Martin,

 I'm not very familiar with iOS, but it looks like there was a bad
 dereference inside of the WebView (that 0xfff9 looks like the highest
 address on your process stack).

 I did get it to fail in the ios simulator as well, but mobile safari
 only reports a bus error, which suggests that this is a bad pointer
 dereference.

 I have a hunch that this is related to a node being removed from the DOM
 that also has a touch listener on it, but that idea is just based on the
 fact that safari stops sending touch events when the origin node is removed.

 The WebCore::Document::touchEventsChangedTimerFired code is an IOS only
 extension to WebKit, so I'm not sure how to look at what that is doing.


 On Wed, Sep 3, 2014 at 9:46 AM, Rob Dodson robdod...@google.com wrote:

 Hey Martin, sorry for the delay, I think we're still catching up a bit
 from the long weekend :)
 We're looking into this and hopefully will have a response soon.

 - Rob


 On Wednesday, September 3, 2014 7:29:18 AM UTC-7, Martin Kleinschrodt
 wrote:

 Anyone? I could really use some help on this...

 On Monday, September 1, 2014 11:39:55 AM UTC+2, Martin Kleinschrodt
 wrote:

 After some more experimentation, I narrowed it down a little more: It
 seems the issue was introduced between versions 0.3.4 and 0.3.5. Also, it
 seems that the problem is inside the polymer package, *not* the
 platform layer as one might expect (I reproduced the crashes with
 Polymer/polymer#0.3.5 + Polymer/platform#0.3.2). Then again, apparently
 TemplateBinding and polymer-expressions are contained in the polymer
 package, so maybe not that surprising after all. So it seems the culprit 
 is
 hiding in one of these changesets:

 https://github.com/Polymer/polymer-dev/compare/0.3.4...0.3.5
 https://github.com/polymer/TemplateBinding/compare/0.3.4...0.3.5
 https://github.com/polymer/polymer-expressions/compare/0.3.4...0.3.5
 https://github.com/Polymer/polymer-gestures/compare/0.3.4...0.3.5

 Anything else I missed that is part of the polymer package?

 On Monday, September 1, 2014 10:56:18 AM UTC+2, Martin Kleinschrodt
 wrote:

 Ever since updating from v0.3.2, my Polymer app crashes all the
 time. The problem is extremely hard to debug since I don't get any error
 messages in the browser console but instead the app crashes completely.
 This happens both in mobile safari and in the web view. The only clue 
 that
 I have is this log from my cordova app:

   Process 15971 stopped
 * thread #6: tid = 0x5783c3, 0x36ae071a
 WebCore`WebCore::Document::touchEventsChangedTimerFired(WebCore::TimerWebCore::Document*)
 + 254, name = 'WebThread', stop reason = EXC_BAD_ACCESS (code=1,
 address=0xfff9)
 frame #0: 0x36ae071a
 WebCore`WebCore::Document::touchEventsChangedTimerFired

Re: [polymer-dev] Re: Polymer app very unstable in mobile safari (iOS 7)

['Daniel Freedman' via Polymer]

Hi Martin,

I'm not very familiar with iOS, but it looks like there was a bad
dereference inside of the WebView (that 0xfff9 looks like the highest
address on your process stack).

I did get it to fail in the ios simulator as well, but mobile safari only
reports a bus error, which suggests that this is a bad pointer
dereference.

I have a hunch that this is related to a node being removed from the DOM
that also has a touch listener on it, but that idea is just based on the
fact that safari stops sending touch events when the origin node is removed.

The WebCore::Document::touchEventsChangedTimerFired code is an IOS only
extension to WebKit, so I'm not sure how to look at what that is doing.


On Wed, Sep 3, 2014 at 9:46 AM, Rob Dodson robdod...@google.com wrote:

 Hey Martin, sorry for the delay, I think we're still catching up a bit
 from the long weekend :)
 We're looking into this and hopefully will have a response soon.

 - Rob


 On Wednesday, September 3, 2014 7:29:18 AM UTC-7, Martin Kleinschrodt
 wrote:

 Anyone? I could really use some help on this...

 On Monday, September 1, 2014 11:39:55 AM UTC+2, Martin Kleinschrodt wrote:

 After some more experimentation, I narrowed it down a little more: It
 seems the issue was introduced between versions 0.3.4 and 0.3.5. Also, it
 seems that the problem is inside the polymer package, *not* the
 platform layer as one might expect (I reproduced the crashes with
 Polymer/polymer#0.3.5 + Polymer/platform#0.3.2). Then again, apparently
 TemplateBinding and polymer-expressions are contained in the polymer
 package, so maybe not that surprising after all. So it seems the culprit is
 hiding in one of these changesets:

 https://github.com/Polymer/polymer-dev/compare/0.3.4...0.3.5
 https://github.com/polymer/TemplateBinding/compare/0.3.4...0.3.5
 https://github.com/polymer/polymer-expressions/compare/0.3.4...0.3.5
 https://github.com/Polymer/polymer-gestures/compare/0.3.4...0.3.5

 Anything else I missed that is part of the polymer package?

 On Monday, September 1, 2014 10:56:18 AM UTC+2, Martin Kleinschrodt
 wrote:

 Ever since updating from v0.3.2, my Polymer app crashes all the time.
 The problem is extremely hard to debug since I don't get any error messages
 in the browser console but instead the app crashes completely. This happens
 both in mobile safari and in the web view. The only clue that I have is
 this log from my cordova app:

 Process 15971 stopped
 * thread #6: tid = 0x5783c3, 0x36ae071a WebCore`WebCore::Document::
 touchEventsChangedTimerFired(WebCore::TimerWebCore::Document*) +
 254, name = 'WebThread', stop reason = EXC_BAD_ACCESS (code=1,
 address=0xfff9)
 frame #0: 0x36ae071a WebCore`WebCore::Document::
 touchEventsChangedTimerFired(WebCore::TimerWebCore::Document*) + 254
 WebCore`WebCore::Document::touchEventsChangedTimerFired(
 WebCore::TimerWebCore::Document*) + 254:
 - 0x36ae071a:  ldr.w  r8, [r0]
0x36ae071e:  cmp.w  r8, #0x0
0x36ae0722:  beq0x36ae07e4; WebCore::Document::
 touchEventsChangedTimerFired(WebCore::TimerWebCore::Document*) + 456
0x36ae0724:  movs   r0, #0x0

 I don't know enough about WebCore to get anything from this, but based
 on when the crashes occur (usually after updating a model) I suspect that
 the problem has something to do with either polymer-expressions or
 TemplateBinding.

 I'm currently using Polymer 0.4.0 but I think the problem exists since
 0.3.3.

 If you want to reproduce the problem yourself, go ahead and open
 http://maklesoft.github.io/padlock on your iPhone (or iOS simulator)
 and follow these steps:

 - Choose a master password (you can simply use an empty one)
 - Create a record
 - Go back
 - Create another record
 - Switch back and forth between the two records (tap a record to select
 it), at some point the app will crash (probably sooner rather than later)

 Other ways to reproduce the crash

 - Delete a record
 - Add a field to a record
 - Add a category to a record

 I wish I could offer more information, but at this point I am pretty
 much clueless. If you want to dig through the code, you can find it at

 https://github.com/maklesoft/padlock

 I probably don't have to mention that this is a show stopper for me. I
 wonder if anybody is having similar problems?

  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/8b2b71eb-2508-4aea-a7c2-de1ad34bec25%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/8b2b71eb-2508-4aea-a7c2-de1ad34bec25%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


Follow Polymer on Google+: 

Re: [polymer-dev] Re: Polymer app very unstable in mobile safari (iOS 7)

['Daniel Freedman' via Polymer]

I was able to make a repro case just with templates and tap handlers.

It looks like this error is triggered when the a node with a touch handler
is being removed by a template model update while a touch event is being
dispatched.

Minimal repro: https://gist.github.com/azakus/72d2b7d1ffde1e94283a

Since this seems related to template stamping timing, I'll have to sit down
with the template polyfill authors to get a better understanding of the
exact timing of the polyfill.

Thanks for your patience.


On Wed, Sep 3, 2014 at 10:23 AM, Daniel Freedman dfre...@google.com wrote:

 Hi Martin,

 I'm not very familiar with iOS, but it looks like there was a bad
 dereference inside of the WebView (that 0xfff9 looks like the highest
 address on your process stack).

 I did get it to fail in the ios simulator as well, but mobile safari only
 reports a bus error, which suggests that this is a bad pointer
 dereference.

 I have a hunch that this is related to a node being removed from the DOM
 that also has a touch listener on it, but that idea is just based on the
 fact that safari stops sending touch events when the origin node is removed.

 The WebCore::Document::touchEventsChangedTimerFired code is an IOS only
 extension to WebKit, so I'm not sure how to look at what that is doing.


 On Wed, Sep 3, 2014 at 9:46 AM, Rob Dodson robdod...@google.com wrote:

 Hey Martin, sorry for the delay, I think we're still catching up a bit
 from the long weekend :)
 We're looking into this and hopefully will have a response soon.

 - Rob


 On Wednesday, September 3, 2014 7:29:18 AM UTC-7, Martin Kleinschrodt
 wrote:

 Anyone? I could really use some help on this...

 On Monday, September 1, 2014 11:39:55 AM UTC+2, Martin Kleinschrodt
 wrote:

 After some more experimentation, I narrowed it down a little more: It
 seems the issue was introduced between versions 0.3.4 and 0.3.5. Also, it
 seems that the problem is inside the polymer package, *not* the
 platform layer as one might expect (I reproduced the crashes with
 Polymer/polymer#0.3.5 + Polymer/platform#0.3.2). Then again, apparently
 TemplateBinding and polymer-expressions are contained in the polymer
 package, so maybe not that surprising after all. So it seems the culprit is
 hiding in one of these changesets:

 https://github.com/Polymer/polymer-dev/compare/0.3.4...0.3.5
 https://github.com/polymer/TemplateBinding/compare/0.3.4...0.3.5
 https://github.com/polymer/polymer-expressions/compare/0.3.4...0.3.5
 https://github.com/Polymer/polymer-gestures/compare/0.3.4...0.3.5

 Anything else I missed that is part of the polymer package?

 On Monday, September 1, 2014 10:56:18 AM UTC+2, Martin Kleinschrodt
 wrote:

 Ever since updating from v0.3.2, my Polymer app crashes all the time.
 The problem is extremely hard to debug since I don't get any error 
 messages
 in the browser console but instead the app crashes completely. This 
 happens
 both in mobile safari and in the web view. The only clue that I have is
 this log from my cordova app:

 Process 15971 stopped
 * thread #6: tid = 0x5783c3, 0x36ae071a WebCore`WebCore::Document::
 touchEventsChangedTimerFired(WebCore::TimerWebCore::Document*) +
 254, name = 'WebThread', stop reason = EXC_BAD_ACCESS (code=1,
 address=0xfff9)
 frame #0: 0x36ae071a WebCore`WebCore::Document::
 touchEventsChangedTimerFired(WebCore::TimerWebCore::Document*) + 254
 WebCore`WebCore::Document::touchEventsChangedTimerFired(
 WebCore::TimerWebCore::Document*) + 254:
 - 0x36ae071a:  ldr.w  r8, [r0]
0x36ae071e:  cmp.w  r8, #0x0
0x36ae0722:  beq0x36ae07e4; WebCore::Document::
 touchEventsChangedTimerFired(WebCore::TimerWebCore::Document*) + 456
0x36ae0724:  movs   r0, #0x0

 I don't know enough about WebCore to get anything from this, but based
 on when the crashes occur (usually after updating a model) I suspect that
 the problem has something to do with either polymer-expressions or
 TemplateBinding.

 I'm currently using Polymer 0.4.0 but I think the problem exists since
 0.3.3.

 If you want to reproduce the problem yourself, go ahead and open
 http://maklesoft.github.io/padlock on your iPhone (or iOS simulator)
 and follow these steps:

 - Choose a master password (you can simply use an empty one)
 - Create a record
 - Go back
 - Create another record
 - Switch back and forth between the two records (tap a record to
 select it), at some point the app will crash (probably sooner rather than
 later)

 Other ways to reproduce the crash

 - Delete a record
 - Add a field to a record
 - Add a category to a record

 I wish I could offer more information, but at this point I am pretty
 much clueless. If you want to dig through the code, you can find it at

 https://github.com/maklesoft/padlock

 I probably don't have to mention that this is a show stopper for me. I
 wonder if anybody is having similar problems?

  Follow Polymer on Google+: plus.google.com/107187849809354688692
 ---
 You received this message 

Re: [polymer-dev] PSA: PointerEvents and PointerGestures are being replaced by polymer-gestures, breaking changes for pointer* events

['Daniel Freedman' via Polymer]

Given Blink's decision to not implement PointerEvents natively (
http://lists.w3.org/Archives/Public/public-pointer-events/2014JulSep/0051.html),
I can't justify keeping the torch lit for the Polymer polyfill to myself
anymore.
If there are others who have the time and energy to keep the dream alive, I
think the best course of action would be to fork
https://github.com/Polymer/PointerEvents, as I and Polymer, and Google
won't be the active maintainers.
I will happily answer code questions and be available to review changes if
asked.

I do have a few bits of feedback for the pointerevents folks that you might
find useful.

As Polymer has progressed as a project, we've found that good UX requires a
system that can handle sloppy user input, where a mouse or finger could
move outside the node with the event handlers.

This case happens quite frequently with dragging interactions, especially
on mobile. It doesn't just come up because of poor hand-eye coordination,
but because the user can frequently move faster than the event/layout/paint
system can handle.

In order to counteract this degenerative case, a developer either has to
use pointer capturing for every instance of draggable UI, or add another
set of listeners higher up the DOM tree and do some event delegation. This
proves to be too great of a burden to development, and necessitated the
creation of Polymer's gesture library, which has a TouchEvent-like event
targeting system. For all the horrible API of TouchEvents, the event
targeting model is almost ideal for user interaction.

Another great observation: no one remembers touch-action. Ever. Everyone
gets confused about when they need to use it, and the mirrored directions
of the pan-* values. I had to go as far as making trackx and tracky
gestures that just set intended touch-action for dragging interactions.

In addition, no one ever seemed to use over/out/enter/leave. As long as
:hover works for touch and mouse, all is well.

In closing, I think this whole exercise just proves how *hard* it is to
make an event system. I greatly appreciate everyone's effort, from spec to
implementation, and the users. The web ecosystem can only benefit from the
experiments and hard work of everyone involved.


On Thu, Aug 14, 2014 at 2:05 PM, Rick Byers rby...@google.com wrote:

 Hey Daniel,
 I see you recently marked
 https://github.com/Polymer/PointerEvents/commit/b80d4c2f282758e68c0e9805ee3700b0c36256f2
 the PointerEvents repo as deprecated.  Does this reflect a change to your
 position earlier in this thread (plan to maintain...)?  Any advice for
 people in the PointerEvents community looking to use the polyfill in their
 own projects?

 By the way, I'm working on a hit-test cache feature
 https://code.google.com/p/chromium/issues/detail?id=398920 in blink
 that I hope will (among other benefits) address the shadow DOM hit-test
 perf problem you hit (without requiring any new shadow-piercing API - yay!).

 Thanks,
   Rick



 On Tue, Apr 15, 2014 at 9:12 AM, Rick Byers rby...@google.com wrote:

 Thanks Daniel.  I know this was a tough decision for the Polymer team.
  I'm glad we can continue to collaborate on Pointer Events and the polyfill!

 Rick


 On Mon, Apr 14, 2014 at 11:58 PM, Daniel Freedman dfre...@google.com
 wrote:

 Yes, there are no plans to move it anywhere else.
 On Apr 14, 2014 8:18 PM, Jacob Rossi jacob.ro...@microsoft.com
 wrote:

  Will the polyfill continue to live here:
 https://github.com/polymer/PointerEvents?



 *From:* Daniel Freedman [mailto:dfre...@google.com]
 *Sent:* Monday, April 14, 2014 4:42 PM
 *To:* Rick Byers
 *Cc:* polymer-dev; public-pointer-eve...@w3.org
 *Subject:* Re: [polymer-dev] PSA: PointerEvents and PointerGestures
 are being replaced by polymer-gestures, breaking changes for pointer* 
 events



 It is my hope that when PointerEvents has a few more native
 implementations, then polymer-gestures can transition to being a consumer
 of PointerEvents only, and we can reinstate the polyfill for other browers.

 To that end, I plan to maintain the PointerEvents polyfill to follow
 the spec as it evolves (thankfully there have been few breaking changes
 since the WG started).



 Unfortunately, the polyfill's performance penalty on mobile is an
 information problem, and not one I see workarounds for in the near to
 medium term.

 Target finding seems to be expensive no matter which way I try to slice
 it, and mobile already operates at a tremendous speed disadvantage.



 I do not intend this change to be negative signal on the part of
 PointerEvents, but an (unfortunate) acceptance of the practical realities
 of mobile devices and polyfill performance.



 On Mon, Apr 14, 2014 at 4:23 PM, Rick Byers rby...@google.com wrote:

 +public-pointer-events

 What does this mean for other consumers of the PointerEvents polyfill?
 Will it be effectively orphaned?

 On Apr 14, 2014 7:15 PM, Daniel Freedman dfre...@google.com wrote:

   Hi Polymer users,



 We recently had a big 

Re: [polymer-dev] Can on-$(event) attrs be used outside of Shadow DOM?

['Daniel Freedman' via Polymer]

It's a bit more subtle than that. The binding syntax can only be used
inside of bound template elements. To be bound, a template needs a
the model property to be set, and to have the correct bind attribute set:
http://www.polymer-project.org/docs/polymer/binding-types.html, or be
inside an already bound template.

Polymer provides an auto-binding template that we use extensively for
element demos:
https://github.com/Polymer/core-icons/blob/master/demo.html#L79-L93

The template binding magic is done automatically to the template inside
of polymer-element.


On Wed, Aug 6, 2014 at 12:35 PM, Marco Scannadinari m...@scannadinari.co.uk
wrote:

 Judging by this link
 http://www.polymer-project.org/docs/polymer/polymer.html#declarative-event-mapping
  it
 looks like it can't, but if so, then what is the use of the
 double-moustache syntax if it is bound to that scope anyway? i.e. what
 other scope could on-tap access apart from the element prototype defined in
 Polymer(foo, { THIS BIT })?

 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/3650743a-81c0-4512-952b-4f0447e9337e%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/3650743a-81c0-4512-952b-4f0447e9337e%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/CAAUAVAhrSCQdFnUG-6Xj4GpQyNPMTwRTKL1Nemd4puJwPA0iEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[polymer-dev] Re: Polymer input events

['Daniel Freedman' via Polymer]

We can't use click as is because preventDefault on touchevents will prevent
the click, and we need to call preventDefault to receive events on safari.
Also, click on touch does not have the sloppy cursor mechanics as it does
on mouse, where the deepest common ancestor of the mousedown and mouseup
determine where the click is sent.


On Wed, Jul 16, 2014 at 9:03 AM, Rick Byers rby...@chromium.org wrote:

 Yeah I don't think there's really a perf argument here.  The overhead of
 eager GR should be trivial.

 Back to Tom's original question about detecting 'tap' in a way consistent
 with the platform: we do effectively expose this gesture to the web page -
 via the click event.  Note that this currently takes things into account
 (does touch adjustment, uses device-specific slop values, etc.) which can't
 be done well from JavaScript today.  So we generally encourage people to
 use 'click' rather than do their own gesture detection for tap.

 There are some scenarios where this is inconvenient though, but we've got
 some ideas for how to fix that - it's just not clear to me what's important
 enough to prioritize.  Daniel, what are the scenarios where your tap
 gesture is better than relying on the browser's click event?

 Rick

 On Wed, Jul 16, 2014 at 11:37 AM, Jared Duke jdd...@chromium.org wrote:

 We've worked hard to keep browser-side gesture detection costs down (~60
 microseconds CPU time per event across a given touch scroll on a Nexus 4).
  There may be some clever tricks we can do to cut this down further, e.g,
 if we see that Javascript has preventDefault'ed the initial touchstart we
 can early out from detection for that sequence (modulo some async nuances).
  The advantages in doing eager/greedy gesture detection have so far
 outweighed the potentially redundant cost.

 Longer term, there may be advantages to hosting the (native) gesture
 detector in the render process where communication with JS is cheaper and
 tighter.




 On Wed, Jul 16, 2014 at 5:49 AM, Timothy Dresser tdres...@chromium.org
 wrote:

 With eager gesture detection, the browser gesture detector will run on
 all touches, which means that when a JS gesture detection library is
 running, gesture detection is happening twice.

  There are two problems here:
 1. JS gesture detection feels different from native gesture detection
 2. Doing gesture detection twice may cause performance issues.

 The first problem could be solved for Chrome by releasing a JS version
 of Chrome's gesture detector (emscripten anyone?). Perhaps the community
 would also create versions which match the behavior of other browsers'
 gesture detectors.

 We could solve both problems by dispatching some event to JS for each
 gesture that the browser detects, but I think there are a lot of
 non-technical hurdles here. Trying to expose the notion of gestures
 through web standards would be... difficult to navigate. +rbyers, as he's
 more familiar with why this would be hard.

 Tom, do you have any data on much of a performance problem JS gesture
 detection is?



 On Tue, Jul 15, 2014 at 11:27 PM, 'Zeeshan Qureshi' via input-dev 
 input-...@chromium.org wrote:

 Yes, and with eager gr we might already be processing the event stream
 in parallel waiting for the ack.
  On Jul 15, 2014 11:25 PM, Tom Wiltzius wiltz...@chromium.org
 wrote:




 On Wed, Jul 16, 2014 at 12:19 PM, Zeeshan Qureshi zeesh...@google.com
  wrote:

  Folks on input-dev can correct my understanding if its wrong, but
 there's already a first-class notion of a tap gesture in Chrome. I 
 don't
 think we expose it, but it's there (eating up resources), so it would be
 really nice to take advantage of it. There's also a gesture recognizer 
 in
 the browser that decides whether you're e.g. scrolling vs tapping. It 
 seems
 a real shame to have this logic running every time the user touches the
 screen, only to have all of that logic re-done (potentially with slight
 differences in behavior) in JS.


 I don't think the logic is run twice, Tim can correct me if I'm
 wrong. If there is a touch handler, the touch events are dispatched to
 blink which can be consumed and prevent defaulted. Only if they are not
 prevent defaulted are they fed into the gesture recognizer to generate
 Gesture* events and then dispatched to blink.

 Any library that wants to have their own gesture detector would start
 consuming them at the touch events level and prevent default them.


 It can't quite be that neat, though, because you can still get
 scrolling with touch event handlers. So a JS gesture library would
 intercept all touch events and at some point early in a touch stream 
 decide
 that this wasn't a gesture it was interested in. At that point, the 
 browser
 would have to look at the touch event stream and decide that this *was
 *worth scrolling. The conclusions are different, but the logic must
 be nearly the same...







Follow Polymer on Google+: plus.google.com/107187849809354688692
--- 
You received this 

[polymer-dev] Re: Polymer input events

['Daniel Freedman' via Polymer]

Hey Tom, I'm not sure I understand all of your question.


On Mon, Jul 14, 2014 at 2:51 AM, Tom Wiltzius wiltz...@chromium.org wrote:

 I have a naive question about input events-- to what extent is the Polymer
 input events library
 http://www.polymer-project.org/docs/polymer/touch.html meant to obviate
 gesture disambiguation in script?

 Specifically, if I have an element that I'm interested in taps and swipes
 on, I can listen to both the tap and the trackstart/track/trackend event
 with Polymer's gesture event library. But the tap gesture fires after the
 touch up whether the user tracked in the middle or not.


This is because we made tap have this behavior. A tap will always fire on
the deepest part of the DOM that contains the start and the end position.
You can disable this by calling preventTap on any gesture event, like
track.



 It isn't too painful to stop listening for other events when a track
 begins, but in an ideal world we'd lean on the browser to do disambiguation
 of all gestures that the gesture library exposes -- it needs to do them
 anyway for browser UI (like long press and scrolling), and this provides
 much neater encapsulation of behavior for components (the various gesture
 handlers don't need to know about one another).


This is the part I'm confused about. Do you mean to suggest that the
gesture library should be subsumed by the platform, or that there should be
some sort of exposed low level hooks that a library could use to make a set
of gestures?



 Do we have a path to making that happen?

 To unsubscribe from this group and stop receiving emails from it, send an
 email to input-dev+unsubscr...@chromium.org.


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

Re: [polymer-dev] Implement oninput event for paper-slider

['Daniel Freedman' via Polymer]

Doesn't look like this is supported in paper-slider. Please file a github
issue at https://github.com/Polymer/paper-slider/issues


On Fri, Jul 4, 2014 at 6:33 AM, cyril.marechal...@gmail.com wrote:

 Hi,

 I need to implement the oninput event for paper-slider (see how it
 works here : http://jsfiddle.net/Xjxe6/ ). The actual change event is
 called only when you up the click. And I really need to have the live
 value of my paper-slider.

 How can I do that ?

 Thank you,
 Cyril Maréchal.

 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/5e896e40-a6fa-4734-b009-fbdec6f248c8%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/5e896e40-a6fa-4734-b009-fbdec6f248c8%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/CAAUAVAh366XkygajZhK%2BOuNn8g9LZnhZ363o-W7CWw6rx%3Dqr9Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] core-icon designer question

['Daniel Freedman' via Polymer]

You have to import the other icon sets from core-icons. The demo page
should show you which imports bring which sets.
On Jul 3, 2014 3:36 PM, Martin Amm m...@adenin.de wrote:

 I'm trying to get the Hardware Phone icon from
 http://polymer.github.io/core-icons/components/core-icons/demo.html to
 show in a core-icon. But what ever I tried it didn't succeed.

 Also the core-icon icon=social:cake/core-icon  from
 http://www.polymer-project.org/docs/elements/icons.html doesn't show the
 cake. So I'm wondering what I'm missing.

 How can I use an icon from one of the additional iconsets in
 core-icons/iconsets ?

 Martin





  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/d0504c42-3fa1-461e-bac8-2ecedd147190%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/d0504c42-3fa1-461e-bac8-2ecedd147190%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/CAAUAVAgs4YNJnxCrhWao9Lny2nBeJXwR%2BYivMBPA0Psgh4CNxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] core-icon designer question

['Daniel Freedman' via Polymer]

Oops the instructions weren't pushed to the github pages version. All you
need is an import, link rel=import
href=core-icons/iconsets/social-icons.HTML for the social set.
On Jul 3, 2014 3:54 PM, Martin Amm m...@adenin.de wrote:

 I might be wrong - but on the documentation
 http://www.polymer-project.org/docs/elements/icons.html I don't see how
 the Social iconset should be loaded exactly before using Social:cake

 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/2e7b0231-6e5a-4779-8e08-533b3edceaab%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/2e7b0231-6e5a-4779-8e08-533b3edceaab%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/CAAUAVAhX3PrEuURsUxE%2B9urbKQ3sHW_sHbnfpsuKzi4Wqrpw%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] polymer-gestures not getting triggered on iOS Safari

['Daniel Freedman' via Polymer]

I'm pretty sure this is related to
https://github.com/Polymer/ShadowDOM/issues/452
On Jun 6, 2014 8:48 AM, Eric Bidelman ebi...@gmail.com wrote:

 +daniel


 On Thu, Jun 5, 2014 at 11:51 PM, akhilesh.i...@gmail.com wrote:

 Try out this sample on iOS Safari: http://jsbin.com/poracihi/2/edit

 The tap event is getting triggered on all other desktop and android
 browsers.

 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/136b7b0b-41bd-4e19-8827-18832979cbf4%40googlegroups.com
 https://groups.google.com/d/msgid/polymer-dev/136b7b0b-41bd-4e19-8827-18832979cbf4%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/CAAUAVAgQ-z_Cupf4Y2GxmGvg7VVeM38rrmudq8cfoX_OVXA5%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Access is denied when I tried to access the local HTML files instead of local Host

['Daniel Freedman' via Polymer]

There is a work around that may work. If you use the
vulcanizehttps://github.com/polymer/vulcanize#vulcanizetool to
inline all of the polymer elements, then there probably will not be
any Access Denied errors.

After installing vulcanize (see the link above), you can run `vulcanize
--inline index.html` and it will build a file called `vulcanized.html` that
should have no external dependencies anymore.

However, this is just a workaround, and I cannot guarantee that it will
work for you.

In general, running web applications from file:/// is not advisable due to
security concerns, which is why all browser vendors have made it difficult.

I suggest that you find a way to alter your business requirements on this
issue, or it will only become more problematic for you in the future.


On Tue, May 20, 2014 at 1:36 PM, maksy...@gmail.com wrote:

 I tried all the possible setting suggested in the internet and I am unable
 to solve the issue! Polymer still shouts Access is denied
 And this stops me from using the Polymer library . I am not sure if anyone
 else hasn't faced the same issue? and why there is not work around for it?
 So obvious issue but no fixes.
 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/94e1ab4b-53c0-4871-b93f-0393c6c6%40googlegroups.comhttps://groups.google.com/d/msgid/polymer-dev/94e1ab4b-53c0-4871-b93f-0393c6c6%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/CAAUAVAgUfgtJ3z_p084F76kFqo-UwMeZwvKCbwYeF-KE6tt58w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] jQuery hide('fast') function doest not work inside from Shadow DOM

['Daniel Freedman' via Polymer]

Hi Carlos,

It looks like jQuery does some is this element in the document checks
before deciding to apply the animation.
However, ShadowDOM spec says that document.contains(someNodeInShadowRoot)
should return false for encapsulation reasons.

Polymer's gesture library implements a deepContains method that works
around the ShadowDOM limitation.
As a total hack, I tried setting jQuery.contains =
PolymerGestures.deepContains, and that worked.

This is absolutely not supported, and I'm suprised it worked, but maybe you
can use that for now.

I suspect that jQuery will have to implement something similar to support
ShadowDOM's notion of contains sooner or later.


On Tue, May 13, 2014 at 10:07 PM, Carlos Alberto Castaño García 
calber...@gmail.com wrote:

 Hi,

 I'm testing Custom Elements and I've found this:

 $.hide('fast') --- Doesn't work inside Shadow DOM
 $.hide()  Works on Shadow DOM

 Out Shadow DOM both works.

 Here's a test: http://jsfiddle.net/Ysasn/4/

 Some idea?

 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/75036026-ec35-448d-97ef-5f120572c76e%40googlegroups.comhttps://groups.google.com/d/msgid/polymer-dev/75036026-ec35-448d-97ef-5f120572c76e%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/CAAUAVAgGgPHRaP_0hf5_HSr1A%3Dr7itTJbxSRtTTPeU8LgE9Fog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] unencessary event listeners reqistered on custom elements?

['Daniel Freedman' via Polymer]

I made a reply to that thread.

In essence, an interaction between the ShadowDOM Polyfill is and Polymer's
gesture system is causing the mouse handlers to be set. The gesture system
is a bit naive in that it spams all ShadowRoots with mouse handlers to
recognize gestures, and the ShadowDOM Polyfill has to put those handlers on
the host element and do some event path fixups.

The solution is to keep track of what elements are interested in gesture
events, and only set up listeners on those elements. I'll have to do a bit
of work to implement this, and add some hooks into Polymer elements, but
hopefully that will result in at least limiting the clickable action to
elements that are interactive.
Perhaps that is not even far from wrong in that case.

Thoughts?


On Sat, May 10, 2014 at 1:54 AM, Steve Faulkner faulkner.st...@gmail.comwrote:

 I have emailed [1] Marco, Dave and Alex from the Moz acc team to see if
 they can help. Marco is already aware of the issue.

 [1] http://lists.w3.org/Archives/Public/www-archive/2014May/0003.html


 On Friday, 9 May 2014 19:26:57 UTC+1, Daniel Freedman wrote:

 It looks like any element with a mousedown handler is treated as a
 clickable element in firefox: http://jsbin.com/vegan/1/quiet

 The example only has a div and mousedown handler, no bits of Polymer
 anywhere.

 The Polymer gesture library adds mouse listeners so it doesn't have to
 wrap addEventListener and keep track of interested elements. However, it
 does not add a click event listener, and it seems odd to me that only
 Firefox adds the click default action for this strategy. Chrome and IE both
 give an accDefaultAction of none.

 Alice, Addy, this seems like a FF bug to me. Can one of you reach out to
 their a11y team to figure out why they made this heuristic?
 On May 8, 2014 10:46 PM, Steve Faulkner faulkne...@gmail.com wrote:



 On Thursday, 8 May 2014 23:25:18 UTC+1, Daniel Freedman wrote:

 Hi Steve,

 Alice and Addy alerted me to this the other day, and I'm going to carve
 out some time to work on this, probably tomorrow.


 great! thank you.





 On Thu, May 8, 2014 at 3:16 PM, Steve Faulkner faulkne...@gmail.comwrote:

  I have found that on non interactive polymer based custom elements,
 when using Firefox, a click handler is exposed via accessibility APIs. 
 This
 causes assistive technology such as a screen reader to announce the custom
 element as clickable (when it isn't).

 Would appreciate some help tracking down the cause, as it is annoying
 to usershttps://twitter.com/MarcoInEnglish/status/464383799640735745
 .

 custom element example where the issue occurs: https://github.com/
 ThePacielloGroup/w3c-heading demo page http://thepaciellogroup.github
 .io/w3c-heading/




  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 view this discussion on the web visit https://groups.google.com/d/
 msgid/polymer-dev/d32ad8ac-6a0d-41aa-baeb-492d04e7ed87%40googl
 egroups.comhttps://groups.google.com/d/msgid/polymer-dev/d32ad8ac-6a0d-41aa-baeb-492d04e7ed87%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...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/polymer-dev/dea3c1f3-3f2a-41c8-b215-fcbc92b7bc59%
 40googlegroups.comhttps://groups.google.com/d/msgid/polymer-dev/dea3c1f3-3f2a-41c8-b215-fcbc92b7bc59%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/ec982dea-c566-42ae-971a-a19a3f4ea174%40googlegroups.comhttps://groups.google.com/d/msgid/polymer-dev/ec982dea-c566-42ae-971a-a19a3f4ea174%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 

Re: [polymer-dev] unencessary event listeners reqistered on custom elements?

['Daniel Freedman' via Polymer]

It looks like any element with a mousedown handler is treated as a
clickable element in firefox: http://jsbin.com/vegan/1/quiet

The example only has a div and mousedown handler, no bits of Polymer
anywhere.

The Polymer gesture library adds mouse listeners so it doesn't have to wrap
addEventListener and keep track of interested elements. However, it does
not add a click event listener, and it seems odd to me that only Firefox
adds the click default action for this strategy. Chrome and IE both give an
accDefaultAction of none.

Alice, Addy, this seems like a FF bug to me. Can one of you reach out to
their a11y team to figure out why they made this heuristic?
On May 8, 2014 10:46 PM, Steve Faulkner faulkner.st...@gmail.com wrote:



 On Thursday, 8 May 2014 23:25:18 UTC+1, Daniel Freedman wrote:

 Hi Steve,

 Alice and Addy alerted me to this the other day, and I'm going to carve
 out some time to work on this, probably tomorrow.


 great! thank you.





 On Thu, May 8, 2014 at 3:16 PM, Steve Faulkner faulkne...@gmail.comwrote:

  I have found that on non interactive polymer based custom elements,
 when using Firefox, a click handler is exposed via accessibility APIs. This
 causes assistive technology such as a screen reader to announce the custom
 element as clickable (when it isn't).

 Would appreciate some help tracking down the cause, as it is annoying
 to users https://twitter.com/MarcoInEnglish/status/464383799640735745.

 custom element example where the issue occurs: https://github.com/
 ThePacielloGroup/w3c-heading demo page http://thepaciellogroup.
 github.io/w3c-heading/




  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 view this discussion on the web visit https://groups.google.com/d/
 msgid/polymer-dev/d32ad8ac-6a0d-41aa-baeb-492d04e7ed87%
 40googlegroups.comhttps://groups.google.com/d/msgid/polymer-dev/d32ad8ac-6a0d-41aa-baeb-492d04e7ed87%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/dea3c1f3-3f2a-41c8-b215-fcbc92b7bc59%40googlegroups.comhttps://groups.google.com/d/msgid/polymer-dev/dea3c1f3-3f2a-41c8-b215-fcbc92b7bc59%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/CAAUAVAicsYdMCWfZuPM%2B_s9ziDR%3DCW2EXbDP0ie2Ud3hEL34yA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] All event-properties of the pointer-gestures are returning undefined.

['Daniel Freedman' via Polymer]

Hi Irfan

I'm not seeing where this example has the script for Pointer Events and
gestures loading.

Is it meant to be part of something else?
On May 4, 2014 11:02 PM, Rob Dodson robdod...@google.com wrote:

 hm, Daniel, any idea what's up?


 On Sat, May 3, 2014 at 10:38 PM, irfan mir the...@gmail.com wrote:

 Dear Polymer Devs,

 I'm trying to make gestures involving pinch and track pointer gestures,
 but when I try to get properties of the event, I get undefined.

 event.scale in pinch is undefined when logged in the console and so is
 event.dy in track.

 Here is a sample of where I'm trying to access and use those properties:
 http://goo.gl/XySiBr

 I'd greatly appreciate help!

 Best Regards,
 Irfan

 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/CAMPj_RpPbuAxqEHAuGiJxPVOhKMkX153wiCH1M%2BLhOWPH7%2Bu_g%40mail.gmail.comhttps://groups.google.com/d/msgid/polymer-dev/CAMPj_RpPbuAxqEHAuGiJxPVOhKMkX153wiCH1M%2BLhOWPH7%2Bu_g%40mail.gmail.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/CAAUAVAjeZLU4ii11Neq_oj_68v2opfQ8RbsgGFaphUqqAhA3-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [polymer-dev] Designer Issues

['Daniel Freedman' via Polymer]

Please update bower to 1.3.3. They fixed a few cyclic dependency issues
since 1.2.8


On Thu, May 1, 2014 at 10:52 AM, Mike Parsons mike.r.pars...@gmail.comwrote:

 So I follow the instructions here ...
 https://github.com/PolymerLabs/designer

 but when I run bower install, it errrors out with

 ...
 bower install   platform#cc891ac91a
 bower error Maximum call stack size exceeded

 Stack trace:
 N/A

 Console trace:
 Trace
 at StandardRenderer.error
 (C:\Users\Mike\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
 at Logger.updateNotifier.packageName
 (C:\Users\Mike\AppData\Roaming\npm\node_modules\bower\bin\bower:109:18)
 at Logger.EventEmitter.emit (events.js:95:17)
 at Logger.emit
 (C:\Users\Mike\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
 at
 C:\Users\Mike\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:27:16
 at _rejected
 (C:\Users\Mike\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:808:24)
 at
 C:\Users\Mike\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:834:30
 at Promise.when
 (C:\Users\Mike\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:1079:31)
 at Promise.promise.promiseDispatch
 (C:\Users\Mike\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:752:41)
 at
 C:\Users\Mike\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:574:44

 System info:
 Bower version: 1.2.8
 Node version: 0.10.26
 OS: Windows_NT 6.2.9200 x64


  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/29ab8f05-bda2-478c-a27b-66a1c9070245%40googlegroups.comhttps://groups.google.com/d/msgid/polymer-dev/29ab8f05-bda2-478c-a27b-66a1c9070245%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/CAAUAVAgKsTVp2jtjZb-Nbz2Y96Pi1ceBiXBWzxNoxybgrvB9qQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.