4 commits

Author	SHA1	Message	Date
bwang	f36c58db2f	Update how pinnable elements are handled with no-js and gradeC cases ... Bug: T331563 Bug: T331168 Change-Id: Ibd5aaa605c45216783a2707b3813e1e7e2c46b9b	2023-03-14 17:35:59 -05:00
bwang	62da66047f	Ensure the TOC works across all pinned/unpinned cases when JS is disabled ... - Also consolidates how we hide the pin/unpin buttons into a single CSS block Bug: T331176 Change-Id: I359bde8abee48596186486d48fa6e59297094153	2023-03-13 23:48:18 +00:00
ksarabia	aba94865c2	Removes old style rule ... This patch removes the old style rules for .vector-toc-pinned after one week of cache. Also removes 'data-name' which was no longer used Bug: T325032 Change-Id: I7c8d8e51a61646151706b71a1733b1daac5dbd45	2023-03-10 14:31:44 -06:00
Jon Robson	d4903b8e57	Remove TableOfContents mustache template and mark layout rules ... Follow up to I3484a790ce8ebadf21054ac1d222d5632b2dc5a4 __Template__ The template is not particularly useful - it is only ever used once in this context and features a static ID which means it can never be reused. It is also tied to the #vector-toc-collapsed-checkbox element. In current form it doesn't make sense to have this template. Maybe in future, I could see an argument for a PinnableTableOfContents component that wrapped the checkbox and nav element, and generalized the IDs but currently there's no pressing need or value for that. __Layouts__ The existing Pinned and Unpinned stylesheets are concerned with how the table of contents is layed out holistically with regards to other components and features enabled on the page. I think these should therefore be organized as such. The way I reason with this, is these styles would be irrelevant in a component library if the component was rendered in isolation. Bug: T328719 Change-Id: I9ff0e0eeb35f215a8cae5950d08dc1277b662a71	2023-02-28 00:27:31 +00:00

Renamed from resources/skins.vector.styles/components/TableOfContentsUnpinned.less (Browse further)