So this seems to be a problem with `document.cloneNode` which Polymer uses
when it stamps out its templates.

You can reproduce it here: http://jsbin.com/tuwuco/1/edit?html,output
Set your devtools to a device pixel density of 3, refresh the page, and hit
the 'run with js' button.

Chromium bug is here:
https://code.google.com/p/chromium/issues/detail?id=446574

In the short term you can work around this by using vanilla custom
elements/shadow dom and using importNode instead of cloneNode. But I think
this should hopefully be fixed quickly.

On Tue, Jan 6, 2015 at 9:06 AM, Rob Dodson <[email protected]> wrote:

> I'm looking into this. Seems like their may be a bug. I'm trying to reduce
> it to an easy test case then I can file a ticket.
>
> On Sun, Dec 14, 2014 at 8:10 AM, Atomiko Lex <[email protected]>
> wrote:
>
>> Hi Rob,
>> I tested the example in beta and the image shows up now, but it isn't
>> responsive. Should I file a bug for Chromium?
>> Lex
>>
>> Am Freitag, 12. Dezember 2014 22:00:44 UTC+1 schrieb Rob Dodson:
>>>
>>> ok that's helpful.
>>>
>>> The example is broken in current stable Chrome but works in Chrome Beta,
>>> so I think you stumbled upon a bug that's been fixed and will be updated
>>> when beta moves to stable. Generally we release a new version of Chrome
>>> every 6 weeks, so shouldn't be too long.
>>>
>>> On Mon, Dec 8, 2014 at 1:04 AM, Atomiko Lex <[email protected]> wrote:
>>>
>>>> I have a jsbin here <http://jsbin.com/haxod/3/edit?html,output> now
>>>> (w/o polymer).
>>>> Lex
>>>>
>>>> Am Freitag, 5. Dezember 2014 02:51:51 UTC+1 schrieb Rob Dodson:
>>>>>
>>>>> ah nvm I see the link in the first email now. Your photo is showing up
>>>>> fine for me
>>>>>
>>>>> On Thu, Dec 4, 2014 at 5:50 PM, Rob Dodson <[email protected]> wrote:
>>>>>
>>>>>> Can you post a reduced test case like a jsbin somewhere? It's hard to
>>>>>> debug without seeing the code
>>>>>>
>>>>>> On Thu, Nov 27, 2014 at 8:52 AM, Atomiko Lex <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>> Ok, so now I just put my img tag into an empty page without polymer
>>>>>>> and there were no issues in Chrome with srcset, so this is seemingly a
>>>>>>> Polymer issue.
>>>>>>>
>>>>>>> I am using version 0.5.0, would updating help, or is this unpatched
>>>>>>> yet? I would rather update later because of the breaking changes in 
>>>>>>> 0.5.1.
>>>>>>>
>>>>>>> Thanks for any hints,
>>>>>>> Lex
>>>>>>>
>>>>>>> Am Mittwoch, 26. November 2014 13:40:56 UTC+1 schrieb Atomiko Lex:
>>>>>>>>
>>>>>>>> I am having issues with an image not showing on page load anymore,
>>>>>>>> after a recent Chrome update. The img has srcset and sizes attributes, 
>>>>>>>> and
>>>>>>>> will only show up after inspecting.
>>>>>>>>
>>>>>>>> Is anybody else having this issue? Is it a Chrome bug? Couldn't
>>>>>>>> find anything for that in the Chrome logs. If anybody wants to check 
>>>>>>>> it on
>>>>>>>> my page, it's here <http://www.therapie-jetzt.de/>.
>>>>>>>>
>>>>>>>> I am on 39.0.2171.71 in Chrome, no issues with that in FF 33.1.1
>>>>>>>> or IE 11.
>>>>>>>>
>>>>>>>> Lex
>>>>>>>>
>>>>>>>  Follow Polymer on Google+: plus.google.com/107187849809354688692
>>>>>>> ---
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "Polymer" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>> send an email to [email protected].
>>>>>>> To view this discussion on the web visit
>>>>>>> https://groups.google.com/d/msgid/polymer-dev/0930d785-2e47-
>>>>>>> 425a-a675-aec89cfab9c4%40googlegroups.com
>>>>>>> <https://groups.google.com/d/msgid/polymer-dev/0930d785-2e47-425a-a675-aec89cfab9c4%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>> .
>>>>>>>
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>>
>>>>>  Follow Polymer on Google+: plus.google.com/107187849809354688692
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Polymer" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>> msgid/polymer-dev/a1445f20-f571-4ea3-9d20-cf5e2a1a54fa%
>>>> 40googlegroups.com
>>>> <https://groups.google.com/d/msgid/polymer-dev/a1445f20-f571-4ea3-9d20-cf5e2a1a54fa%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>  Follow Polymer on Google+: plus.google.com/107187849809354688692
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Polymer" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/polymer-dev/5ea474bc-3e72-4d3a-8791-4441308b13d7%40googlegroups.com
>> <https://groups.google.com/d/msgid/polymer-dev/5ea474bc-3e72-4d3a-8791-4441308b13d7%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

Follow Polymer on Google+: plus.google.com/107187849809354688692
--- 
You received this message because you are subscribed to the Google Groups 
"Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/polymer-dev/CAJj5OwD6rwUr5dEijhHbF7MV8kzA9gMESdHMNbEFUKVBw4PK5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to