semantic.min.css loads first and produces UI lag while using custom.css #5782

Closed
opened 2025-11-02 06:35:49 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @ghost on GitHub (Jul 24, 2020).

  • Gitea version (or commit ref): 1.12.2
  • Git version: 2.25.1
  • Operating system: Ubuntu Server / Manjaro XFCE
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

I tried to make changes to profile page on my own Gitea instance. I successfully changed the profile-card but it looks weird since the webpages loads original semantic.min.css file first and only then my custom.css file. Because of that new profile card looks a bit weird since user is able to see old card loading and immediately changing to a new one. The same happens when I am trying to switch tabs from "Repositories" to "Public Activity" and etc.

In case my explanation was not clear enough, here is the webpage which load my custom.css file and where you can experience this lag: https://git.iniguma.org/makkusu

Screenshots

This is how it looks like in the first second when page loads
Screenshot_2020-07-24_17-12-06

This is how it should look like and how it does after that weird old-style loading.
Screenshot_2020-07-24_17-11-31

Here are shows domain names from which website loads .css files. It loads semantic.min.css at first and only after that it loads custom.css what provides such weird lag.
Screenshot_2020-07-24_17-12-54

Originally created by @ghost on GitHub (Jul 24, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.12.2 - Git version: 2.25.1 - Operating system: Ubuntu Server / Manjaro XFCE - Database (use `[x]`): - [ ] PostgreSQL - [X] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - Log gist: ## Description I tried to make changes to profile page on my own Gitea instance. I successfully changed the profile-card but it looks weird since the webpages loads original semantic.min.css file first and only then my custom.css file. Because of that new profile card looks a bit weird since user is able to see old card loading and immediately changing to a new one. The same happens when I am trying to switch tabs from "Repositories" to "Public Activity" and etc. In case my explanation was not clear enough, here is the webpage which load my custom.css file and where you can experience this lag: https://git.iniguma.org/makkusu ## Screenshots This is how it looks like in the first second when page loads ![Screenshot_2020-07-24_17-12-06](https://user-images.githubusercontent.com/68738973/88400443-e43af600-cdb7-11ea-9b29-62f299911f48.png) This is how it should look like and how it does after that weird old-style loading. ![Screenshot_2020-07-24_17-11-31](https://user-images.githubusercontent.com/68738973/88400457-e7ce7d00-cdb7-11ea-8924-4c2187f6f2f7.png) Here are shows domain names from which website loads .css files. It loads semantic.min.css at first and only after that it loads custom.css what provides such weird lag. ![Screenshot_2020-07-24_17-12-54](https://user-images.githubusercontent.com/68738973/88400464-e9984080-cdb7-11ea-89bf-f24e0ebe1a7c.png) <!-- **If this issue involves the Web Interface, please include a screenshot** -->
Author
Owner

@ghost commented on GitHub (Jul 24, 2020):

I am closing an issue since I solved it. I put the code for stylesheet into footer.tmpl rather than header.tmpl which, as I suppose, made an old .css UI load at first and only then my UI rather than overwrite it immediately.

@ghost commented on GitHub (Jul 24, 2020): I am closing an issue since I solved it. I put the <link> code for stylesheet into footer.tmpl rather than header.tmpl which, as I suppose, made an old .css UI load at first and only then my UI rather than overwrite it immediately.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5782