FAQ

###How is the efficiency? The extension works not so efficiently since all the rules have to be tested for each page. Consequently, it may be unexpectedly slow when there are TOO many rules.

###Where is the data stored? Since extensions of Opera do not have the permission to read or write files in local drives, all the data are stored in the extension storage. CSS files can be exported since version 1.3.

###What are the matching rules? There are four types of rules. (One per line)

• domain: matches a domain and all of its subdomains.
• regexp: parsed as a regular-expression and then test the URL.
• url-prefix: matches the URLs that exactly starts with the rule text.
• url: matches the URL that is exactly the same as the rule text.

If any one of the rules matches the URL of current page, the CSS code will be applied.
Excluding rules are removed to keep up with official Stylish. If you have any questions or suggestions, please contact http://userstyles.org directly.

###Why are CSS separated into sections? Since @document rules are discarded by the standards and only supported by Firefox now, Opera itself will not apply CSS according to the rules. So it is easier for Stylish for Opera to manage and apply CSS stored in sections. Since version 1.3, CSS can be exported into a zip file with .user.css files inside, of which the sections are integrated again into a @-moz-document format.