search

sharat87 / custom-web

An annoyingly simple chrome extension to let users add their own snippets of CSS and JS to websites.
https://chrome.google.com/webstore/detail/custom-web/nlacgphiebglipgnadgcegiefbfcpnjk
5 stars 0 forks source link

Support for wildcards / patterns #1

Open ghost opened 10 years ago

ghost commented 10 years ago

For example CSS rules defined for www.deviantart.com do not work on user.deviantart.com.

sharat87 commented 10 years ago

I wanted custom web to be as simple as it can be, which is why I didn't add wildcard support. But I can understand wanting such features so I put in a list of alternatives in the readme. I think stylish and rweb support this. Is there a reason they fail to do what you want?

That aside, I am interested in may be we can support just the subdomain wildcards i.e., *.deviantart.com. I'll see if its simple and if I can afford the time.

Btw, can I ask where you learned about this extension? ;)

ghost commented 10 years ago

Subdomain support would be enough for me, so I hope you could implement it.

Since Chrome 33.x dropped support for Custom.css file, I have been searching for an alternative to inject custom stuff to web pages (preferably CSS rules). I came across to your extension here in GitHub. I want to have as small/lightweight and simple solution as possible. I think that StyleBot and Stylish are too bloated, because the only thing that I want is to customize the layout of web pages with a small memory footprint.

sharat87 commented 10 years ago

Okay, will work on it.

What is this custom.css file? I have no idea such a thing existed.

ghost commented 10 years ago

Chrome(ium) supported custom CSS rules from a file located in

~/Library/Application Support/Google/Chrome/Default/User StyleSheets/Custom.css (Mac) %AppData%\Local\Google\Chrome\User Data\Default\User StyleSheets\Custom.css (Windows)

However CSS rules were global and writing them per-site required some additional code.