Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore clean-repo-header feature #6908

Merged
merged 4 commits into from
Sep 17, 2023
Merged

Conversation

fregante
Copy link
Member

Reverts #6759

The header is still long, ugly and it still causes a wrap and Cumulative Layout Shift.

We can restore it without making it disableable because all of that information is visible in the sidebar, on the same page, as well as in the upcoming:

Screenshot 16

@fregante
Copy link
Member Author

Before

Screenshot 20

After

Screenshot 21

@fregante fregante marked this pull request as ready for review September 12, 2023 06:22
@fregante
Copy link
Member Author

I limited this feature to the new header

Affected

Screenshot 24

Unaffected (except "pins" label)

Screenshot 23

@fregante fregante merged commit ca58484 into main Sep 17, 2023
10 checks passed
@fregante fregante deleted the revert-6759-clean-repo-header branch September 17, 2023 06:05
@innocenzi
Copy link
Contributor

This is disruptive when disabling the new repo-header-info feature, we don't get star count anywhere. :/

Should the CSS in this PR not only be added when repo-header-info is enabled?

@fregante
Copy link
Member Author

fregante commented Sep 19, 2023

we don't get star count anywhere. :/

See the first screenshot, the stars appear 2 times on the page, 400px away

@innocenzi
Copy link
Contributor

Indeed, I phrased that poorly. I really just meant that this was a downgrade in scannability. Is there any way to only hide the stars when the feature is enabled?

@fregante
Copy link
Member Author

Update to 23.9.21

@refined-github refined-github locked as resolved and limited conversation to collaborators Sep 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

Successfully merging this pull request may close these issues.

None yet

2 participants