Skip to content

luci-theme-*: Remove LuCI from title, material theme fixes#8330

Open
Self-Hosting-Group wants to merge 1 commit intoopenwrt:masterfrom
Self-Hosting-Group:theme-changes
Open

luci-theme-*: Remove LuCI from title, material theme fixes#8330
Self-Hosting-Group wants to merge 1 commit intoopenwrt:masterfrom
Self-Hosting-Group:theme-changes

Conversation

@Self-Hosting-Group
Copy link
Contributor

  • Remove | LuCI suffix from title tag
  • Make material theme zoomable and remove old tags

Follow-up to ce358ad

@Self-Hosting-Group Self-Hosting-Group changed the title luci-theme-*: remove LuCI from title, material theme fixes luci-theme-*: Remove LuCI from title, material theme fixes Feb 17, 2026
@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@Self-Hosting-Group
Copy link
Contributor Author

Hello @systemcrash. Here is the PR.

@systemcrash
Copy link
Contributor

@Ramon00 ?

@Ramon00
Copy link
Contributor

Ramon00 commented Feb 18, 2026

two remarks:

  1. Why remove all the "web-app" meta tags? I guess somebody had a use case there? BTW I do think it is inconsistent, i.e. either do it for all themes or for none. We can make it a configurable as well I suppose. Im fine either way, but i dont really see the use case to be honest. So question is why was it added in the past?
  2. I personally just want to have the hostname first, the rest I do not really mind, either with page name or whole menu. I typically do not have multiple tabs for the same router open. So why was it there before, and why was it removed?

@github-actions

This comment has been minimized.

@systemcrash
Copy link
Contributor

two remarks:

  1. Why remove all the "web-app" meta tags? I guess somebody had a use case there? BTW I do think it is inconsistent, i.e. either do it for all themes or for none. We can make it a configurable as well I suppose. Im fine either way, but i dont really see the use case to be honest. So question is why was it added in the past?
  2. I personally just want to have the hostname first, the rest I do not really mind, either with page name or whole menu. I typically do not have multiple tabs for the same router open. So why was it there before, and why was it removed?

Fair points. They were added a long time ago when browsers were… older standards.

  1. probably fanatical use of tags in the templates. Similar to recent comments: for users managing multiple devices and so on. On a normal dev day I have several open.

@Self-Hosting-Group
Copy link
Contributor Author

Thanks for the comments.

  1. Why remove all the "web-app" meta tags? I guess somebody had a use case there? BTW I do think it is inconsistent, i.e. either do it for all themes or for none. We can make it a configurable as well I suppose. Im fine either way, but i dont really see the use case to be honest. So question is why was it added in the past?

Removed for consistency, as these meta tags were only present in the material/openwrt2020 themes, introduced in 2015 in b825a14. Most of them are legacy tags that would be replaced by a web application manifest (PWA), but this only works (installable) with HTTPS and trusted certificates, which is probably not common with OpenWrt's UI. However, even without installation, some manifest properties should be applied (has to be checked). See: https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Making_PWAs_installable

So, if you prefer, we could add a minimal web app manifest instead with a PR later, or we could add mobile-web-app-capable/apple-mobile-web-app-capable for consistency to all themes as an alternative with this PR. Note: I see some differences between the legacy meta tags and the manifest, as the latter seems to be for the whole site and not just the URL.

  1. I personally just want to have the hostname first, the rest I do not really mind, either with page name or whole menu. I typically do not have multiple tabs for the same router open. So why was it there before, and why was it removed?
  1. Probably fanatical use of tags in the templates. Similar to recent comments: for users managing multiple devices and so on. On a normal dev day I have several open.

I see these user cases:

  1. Users having single/multiple tabs open for the same router (home users/devs)
  2. Users managing multiple routers (router managers)

By showing the menu in the title, it's already good for user case 1, but IMHO, preferred would be the menu first that I proposed first, inspired by how it is with the OPNsense UI. The software/site can easily be identified by the icon and hostname first, perfect for case 2. I removed the LuCI suffix, as it seems to me unnecessary, as more details are available in the footer.

What should we do now?

It would actually be good to have the top menu (already translated) in the title, as mentioned here: #7731 (comment). What would be necessary to have a dispatched.topmenu?

@systemcrash
Copy link
Contributor

Fix commit formalities plz

@Self-Hosting-Group Self-Hosting-Group force-pushed the theme-changes branch 2 times, most recently from a49e68f to 6443f81 Compare February 20, 2026 20:47
@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

- Remove `| LuCI` suffix from title tag
- Make material theme zoomable and remove legacy meta tags
- Unify viewport

Link: openwrt#8330
Link: openwrt#7731

Signed-off-by: Self-Hosting-Group <selfhostinggroup-git+openwrt@shost.ing>
Self-Hosting-Group added a commit to Self-Hosting-Group/luci that referenced this pull request Feb 25, 2026
- Remove `| LuCI` suffix from title tag
- Make material theme zoomable and remove legacy meta tags
- Unify viewport

Link: openwrt#8330

Signed-off-by: Self-Hosting-Group <selfhostinggroup-git+openwrt@shost.ing>
@Self-Hosting-Group Self-Hosting-Group force-pushed the theme-changes branch 3 times, most recently from 753e866 to b8dddc6 Compare February 25, 2026 14:33
@Self-Hosting-Group
Copy link
Contributor Author

I try to fix the failing formality check, Commit subject line MUST start with <package name>, I've changed it to luci-theme:, which was last time accepted by the CI check.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions
Copy link

Warning

Some formality checks failed.

Consider (re)reading submissions guidelines.

Failed checks

Issues marked with an ❌ are failing checks.

Commit b8dddc6

  • 🔶 Author name (Self-Hosting-Group) seems to be a nickname or an alias
  • 🔶 Committer name (Self-Hosting-Group) seems to be a nickname or an alias

For more details, see the full job log.

Something broken? Consider providing feedback.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants