Ian Clark

Perhaps you could apply it to the `in-view-container`. In this case the container would be the tab, and so, if specified, you check to see if the container is visible?...

So after looking at this a little more, hopefully I have a solution (above). Adding the `requireOffsetParent` to `in-view-options` should address the issue by only regarding an element as in...

Hey, sure, happy to add to README. BTW #116 was a more trivial way of determining whether an element is within the viewport, but I opted against it because I...

I also just came across this when bumping dependencies for my [DRF package](https://github.com/evenicoulddoit/django-rest-framework-serializer-extensions). I didn't manage to bisect, only to confirm that the issue was definitely present in 4.2.0, and...

To build on @karlhaas's comment, here's something I've come up with, which allows for cache-busting on a *per-build* basis, rather than @errolgr's solution - which will force the client to...

But having not meticulously looked through the code I'm not sure why `===` equality checking would make the above infeasible? The `rz-slider-model` and `rz-slider-high` values are both members of the...

@sci-tab thanks for going through the PR, should have addressed all your comments

I'm getting the same error as those reporting here, *again* with NgRx selectors, however if I'm reading the situation correctly this issue isn't limited to secondary endpoints. My build is...

Hi @philipstarkey, sorry for the late reply, was on vacation. I must confess, having lived in Flask-land for such a period of time, I'm returning to this unsure as to...

@philipstarkey I'm sorry it took me so long to look into this. You mentioned specifically the issue of accessing the request context from within a nested serializer. [In this branch](https://github.com/evenicoulddoit/django-rest-framework-serializer-extensions/compare/test_nested_serializer_context-ijc#diff-7aad4f75e1993c5ce805f8340139b2523125e7d872294f1d816248079df4e1c2),...