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

Ideas for other userstyle types #299

Open
a0eoc opened this issue Feb 4, 2024 · 0 comments
Open

Ideas for other userstyle types #299

a0eoc opened this issue Feb 4, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@a0eoc
Copy link
Member

a0eoc commented Feb 4, 2024

Currently USw is used for hosting userstyles injected into websites by Stylus extension. But there are other types of injectable user-created CSS modifications for existing software. We may want to add support for some.

  • Custom CSS for BetterDiscord/Vencord/Armcord/other *cord Discord client modifications

    Spec:
    They all seem to use file mask of *.theme.css and commented metadata with fields like @name, @description, @author, @version. There's no @namespace though. Some styles are implementing more fields with links to source code, donation options, links profiles, etc. But I could not find a spec with more than 4 fields documented. I have also seen @updateUrl in some styles. No idea how its used but it should probably be preserved or replaced in case of USw. The styles are also usually making use of @import url('https://').

    Some places where these styles are usually hosted:

    Reasons against:

    • I feel like half of these custom clients are created to make bot farms. Also the lifespan of these clients is usually very short.
    • => the styles are relaying on a proprietary platform and on unstable (as existence stability) modifications prohibited by the platform.
    • Possible spam of styles that just import another style and change the background image.

    There's also discocss which just injects plain *.css files. I guess it should be compatible with the other format

  • Firefox userChrome

    Spec:
    Only works on Firefox with toolkit.legacyUserProfileCustomizations.stylesheets enabled.
    Filenames are userChrome.css and userContent.css, but it seems like *.css is good in case of user wanting to combine multiple themes via @import().
    There's no metadata and no auto-update software.

    Some places where these styles are usually hosted:

    Reasons against:

    • Relies on Firefox legacy functionality, which may be removed soon.
    • Firefox is unpopular and in constant state of user base fall.
    • => if we add support for this type of styles, we may get increased code maintenance cost for a discontinued feature with very few users.
@a0eoc a0eoc added the enhancement New feature or request label Feb 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant