Peter Burns
Peter Burns
I see your point about it being disruptive to the display for consistently low latency operations. I'm not entirely sure I understand how this would work if the configuration is...
Hm, changing `` to `` isn't quite right, because if `bar` changes, with `iron-meta-query` it would not be pushed down into the store. What we really want is to read...
My first gambit of just changing all `` instances to `` did break a handful of things. Mostly in one app.
/cc @bicknellr
I'd lean towards the encoding scheme that we used for GET params. The reason that we went with that encoding was that it maximizes user control over how their data...
jsbin to reproduce: https://jsbin.com/pibaregaze/edit?html,output I'm not sure what the right way of handling this is though. I could see ignoring those key-value pairs, or encoding them as the empty string...
So, this was deliberate, so that we could use the browser's built in XHR json handler, which is specced to return null on parse errors. In hindsight this probably wasn't...
It sounds like this is a case where iron-pages fixates on its children before page load is finished and doesn't notice as more are added. Changes have landed to this...
What happens if you call `_updateItems()` on the iron-pages element after it's loaded? I wonder if we need to listen for DOMContentLoaded in iron-selector...
\cc @cdata who's done a lot of the work on iron-selector