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

Switch to using web component version of nav bar #142

Merged
merged 1 commit into from
Oct 16, 2022

Conversation

halkeye
Copy link
Member

@halkeye halkeye commented Oct 16, 2022

What it looks like right now

image

What it looks like with web component:

image

I realized there's a need to allow sites to extend the nav bar, so i'll add support for it, but I still think its a possible win.

@timja timja merged commit 168b14e into jenkins-infra:main Oct 16, 2022
@timja
Copy link
Member

timja commented Oct 16, 2022

FWIW I tested this locally in Chrome and there's a bit of delay waiting for the header to load, e.g. the page loads without the header and then it appears, probably should be render blocking?

@halkeye
Copy link
Member Author

halkeye commented Oct 16, 2022

I'm not really sure how to make it block, I think it's the nature of web components. It caches really well though

@timja
Copy link
Member

timja commented Oct 16, 2022

Could possibly bundle it in the app? Coming from npm?

@halkeye
Copy link
Member Author

halkeye commented Oct 16, 2022

Unpkg is a pretty fast cdn and has better support for ESM modules.

If you refresh again it's it slow?

@halkeye
Copy link
Member Author

halkeye commented Oct 16, 2022

Oh wait I see what you mean. The first paint is slow. I can move the script tags to the end and async them

@timja
Copy link
Member

timja commented Oct 16, 2022

Sure if that helps, created #147 for tracking

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants