Preserve Custom Modifications Across Upgrades
LonM last edited by Pesala
Currently if a user has a custom mod for the browser ui they have to do some sort of hacky installation by modifying the browser.html file. This is lost when the browser is upgraded to a new version. It would be nice if there was some way to store custom styles in a setting that is persistent when the browser is upgraded.
Morg42 last edited by
A possible solution might be to enter a directory in V settings where user customizations are loaded automatically (custom.js / custom.css).
This would also remove the need to modify browser.html
@lonm This capability is already on the roadmap, insofar as a roadmap can be said to exist. It is a fairly common subject of discussion among the team. Unfortunately, major projects such as Mail, Sync and Calendar have a lot more priority, and the team is small.
@ayespy This is good to hear. Luckily with a script the job of patching in mods isn't too tedious for now.
LonM last edited by LonM
I think that CSS mods would fit well if they were stored along with a theme, that way you could have different mods active depending on the theme.
JS mods wouldn't fit in with themes though.
luetage last edited by
@luetage Good point. Maybe if the theme name was just added to the other class names in
#browserthat would be enough
Also useful would be the ability to preserve custom page actions - files the user added to the
These would be more easy to maintain, as the installer would simply need to copy them over to the new directory. Page Actions also don't cause side-effects on the browser (as far as I can tell), so there is no issue of incompatibility as there is with mods.
Hadden89 last edited by Hadden89
@luetage A kind of a mod loader after an update?
V was updated. Reviews your mods. Please - check - if they're compatible before loading or V couldn't work correctly. - Don't - report any bug about modding issues.
[images] (usually under styles)
(Of course, this screen shouldn't appear if no mod is used)