mobile-tabs - Restore feature#9231
Conversation
mobile-tabs - Restore feature
Agent-Logs-Url: https://github.com/refined-github/refined-github/sessions/1d269f5e-939c-4706-b990-a9595d22bd2e Co-authored-by: fregante <[email protected]>
Agent-Logs-Url: https://github.com/refined-github/refined-github/sessions/1d269f5e-939c-4706-b990-a9595d22bd2e Co-authored-by: fregante <[email protected]>
mobile-tabs - Restore featuremobile-tabs selectors for GitHub’s new repository nav markup
mobile-tabs selectors for GitHub’s new repository nav markupmobile-tabs - Restore feature
fregante
left a comment
There was a problem hiding this comment.
li > adoesn't filllivertically,lihas this style:.prc-UnderlineNav-UnderlineNavItem-syRjR { flex-direction: column; align-items: center; display: flex; }
- the contents of
li > ashould be bottom-aligned - the
data-tab-item="security-and-quality"tab has a long label. shorten to "Sec" like we did for Pulls - the custom "Pulls" label is bold, but it shouldn't be bold anymore
- some tabs are missing the counter, so the top-right cell is empty; refer to the previous CSS to target this format again, it will center the icon horizontally. We already have CSS that does this but the selectors are out of date.
- Some tabs are missing the icon, the same thing should happen
- The icon and counter should have
margin:0!important - Don't rename the PR
Agent-Logs-Url: https://github.com/refined-github/refined-github/sessions/a8d34190-f1d7-4363-9e02-a727f5e79f50 Co-authored-by: fregante <[email protected]>
Fixed in 687c947. I updated the mobile tab CSS to bottom-align |
|
Can't finish this tonight. Releasing 26.4.20 without it. I can add it via hotfix later. |
Agent-Logs-Url: https://github.com/refined-github/refined-github/sessions/5283e7eb-db73-4807-9ac4-e174eef5f092 Co-authored-by: fregante <[email protected]>
|
They have some weird on-the-fly calculation and caching that break any attempts at changing the size. Mainly:
I'm going back to the idea we should reimplement the tabs from scratch, but this is super risky for future developments by GitHub. The really difficult part is knowing what tabs are available: GitHub won't render them at all if the viewport is too small :( |


No description provided.