Carl Vitullo

Hm @keith-gould-zocdoc so does this seem like a bug with how Sticky renders in Enzyme? I'm not super familiar with the quirks of rendering with Enzyme, but it does seem...

@denis-sokolov I'm not quite understanding what the problem is. You're trying to replicate the stacked demo?

Gotcha, okay. It definitely does seem like if the stacked demo works, and the relative demo works, a stacked relative demo should work as well. I'm still familiarizing myself with...

Okay, that's fine! I'll leave this open as a doc enhancement issue, and will open a bug issue if I find something's not working right.

Hi @041616 @liuhelen10 would one of you be able to create a minimal reproduction of the problem? Setting up an SSR app to test this would take me a bit...

We have very similar usernames! Good suggestion, care to open a PR? :)

I agree with you, but as you note IntersectionObserver has poor browser support. Do you have any recommendations for only including the polyfill if the consumer doesn't already supply it?...

I see your use case, but I'm not a fan of reaching outside of the component arbitrarily. Would something like ```js {/* ... */} ``` work for you? I'm not...

That's due to how the promise is being made, returning `Promise.resolve` means only the success case is promise-ified. Replacing your `test` with ```js function test() { return new Promise(() =>...

I'd suggest avoiding pulling in any polyfills if possible. [sokra sums up my thoughts on it here](https://github.com/w3ctag/polyfills/issues/6#issuecomment-272647475), it leads to redundant code for library consumers, and `fetch` is common enough...