It's the "sticky failures" day at TablesNG manor. Here is a test case: https://wptest.center/#/1vb898 (my first time using wptest) It applies sticky constraints table parts, scrolls, and observes part position. I am testing for the most common behavior in current browsers which is: "Table wrapper fragment is the sticky container for all table parts" Results: // FF 82: pass // Chrome legacy: TD pass, TR/TBODY fail, sticky treated as static // Edge 17:TD pass, TR/TBODY fail, sticky treated as static // Safari: TD/TR fail creatively, TBODY pass. For TD, sticky container being Table wrapper matches widest current behavior. If we adopt this for TD, makes sense to do it for TR too. -- GitHub Notification of comment by atotic Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5020#issuecomment-728659603 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Tuesday, 17 November 2020 03:16:45 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:22 UTC