Define You:

• Contributor

Is your feature request related to a problem? Please describe.

Peersky and Agregore both supply browser-level styles for web apps to import. I think it would be good for us to standardize on a browser protocol handler for features like that.

I'm open to whatever other names you think would be good for it too!

I think it'd be good to start with the theme stuff.

Describe the solution you'd like...

I propose browser://theme/style.css gives "browser level styles" which users or the browser might set. Web apps should assume that they don't need to add any style related CSS and focus on content / structure.

Then, I think it could also be nice to standardize on some values for vars.css (maybe a minimum shared set like bg color/text color?) I think PeerSky's supplies a different set than (Agregore's). What do you think?

Also down to bikeshed browser://css/style.css or whatever other folder structure you'd prefer.

Also based on the element convo we should be considering CSP values? I have no strong opinions other than the CSS being as easy to load from other domains as possible.

Describe alternatives you've considered?

• Some way of getting apps to try to link both peersky/agregore protocols (and other browsers in the future if they care about this?)
• just not worrying about it and seeing what happens

Approach to be followed (optional):

I think it'd be good to talk about what we want / bikeshed a little before implementing. Then I think it'd be good to publish docs to make it easy to reproduce elsewhere. (e.g. mobile)

Additional context