(In reply to James Teh [:Jamie] from comment #1) > Nathan, I'd be interested to know whether any of the position: sticky failures you've seen in the wild are magically working now. Note that this will still probably break if the position: sticky element doesn't have an Accessible (bug 1814800 but for sticky), so if it doesn't, you might need to force one by adding, say, role="group" before you scroll. Most of these issues in the wild have been position: fixed. I've found one major position: sticky issue in the wild which I've been struggling to reproduce for a while now: the Twitter tablist that holds "For you," "Trending", "News," "Sports," and so on. I've been unable to get the Testcase Reducer extension to get me a good isolated test of the position: sticky issue on Twitter, despite that being reasonably straightforward for position: fixed. That said, if I add `role="group"` to the parent div that has position: sticky for that Twitter tablist, the bounds issue is fixed. Do we want a separate bug for that? Also, the test case you provided in comment #3 works for me in latest Nightly.
Bug 1815153 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to James Teh [:Jamie] from comment #1) > Nathan, I'd be interested to know whether any of the position: sticky failures you've seen in the wild are magically working now. Note that this will still probably break if the position: sticky element doesn't have an Accessible (bug 1814800 but for sticky), so if it doesn't, you might need to force one by adding, say, role="group" before you scroll. Most of these issues in the wild have been position: fixed. I've found one major position: sticky issue in the wild which I've been struggling to reproduce for a while now: the Twitter tablist that holds "For you," "Trending", "News," "Sports," and so on. I've been unable to get the Testcase Reducer extension to get me a good isolated test of the position: sticky issue on Twitter, despite that being reasonably straightforward for position: fixed. That said, if I add `role="group"` to the parent div that has position: sticky for that Twitter tablist, the bounds issue is fixed. Do we want a separate bug for that? I think it is _probably_ the same thing as what you've described here, so I doubt we need one yet. Also, the test case you provided in comment #3 works for me in latest Nightly.