Ian Paterson

I do not know how to account for the discrepancy between where Safari _thinks_ the legend elements are located and where they are rendered. In this example, Safari is indicating...

I no longer use Wunderlist so can't say whether anything has changed since 2015, but there is more discussion related to this in #12

My workaround was to allow the localhost URL to be pasted into the app via a help screen for those who cannot log in. It's ugly but enough users had...

Held off on commenting in the past to avoid bumping but since this is being discussed now... My primary use case for this is to snap photos of outgoing personal...

@stalena, it's been quite awhile, I'm still using my fork from this pull request. I just rebased this pull request against the latest master for you: https://github.com/Newstex/angular-elastic/tree/pull-requests/computed-style-check

I don't think so but haven't used this in a few years. Feel free to give it try.

I'm not seeing this glitch anymore. The CSS workaround is still in place in my implementation but it no longer has any effect because the legend has been moved outside...

Indeed, looks like 3.37.1 fixed it. Check out this codepen with Safari in [3.36.1](https://codepen.io/idpaterson/pen/oNaNpOz) where the legend bug still existed on page zoom in/out vs [3.37.2](https://codepen.io/idpaterson/pen/MWPWrxR) which seems to be...

I think that for backwards compatibility the getter should always be writable in case anyone was using the workaround that I was using (`this.foo = this.foo.bind(this);` in the constructor). I...