Looks like someone has reported this issue on GitHub for iron-media-query:
https://github.com/PolymerElements/iron-media-query/issues/15
Still, any comments or recommendations?
On Tuesday, 22 September 2015 11:02:58 UTC-7, Kelly St. John wrote:
>
> Has anyone run into issues where iron-media-query doesn't seem to be
> setting the query-matches bound property on initial loading of the site? In
> other words, if the site is initially loaded in a smaller viewport (such as
> on mobile or on desktop in smaller window), various local DOM elements are
> not being hidden using
>
>
>
> hidden$="{{_smallScreen}}"
>
>
> However, if the site is initially loaded in a larger viewport and then
> subsequently reduced in size, the iron-media-query hides the local DOM
> elements appropriately. Perhaps something to do with initial value of
> element's _smallScreen property or maybe I should perform some action on a
> loading lifecycle event?
>
>
> FYI, I have posted on SO as well:
> http://stackoverflow.com/questions/32723163/iron-media-query-not-hiding-local-dom-elements-if-initially-loaded-in-smaller-vi
>
>
>
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/43cd717d-0198-4329-9967-21bb59ab9efd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
