You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I explain in the description for all of my created styles, such as _this one_, if a user chooses to install one of my styles from the "Install Style from Social" drop-down box while on a given domain (gog.com, in this example), that style is not installed on its other intended domains, and there isn't even an option provided to the user to do this. Using the Social installation method, a user must install the same style for each applicable domain, such as for http://gog.com & for https://secure.gog.com, which should be completely unnecessary because they are the very same site, and because this is not the way it is done when installed from stylebot.me.
Obviously, this issue will tend to cause confusion for those choosing to use the Social installation method, and thus I believe this is best classified as a bug.
The text was updated successfully, but these errors were encountered:
Thank you @ankit! Very glad to hear it, and thank you for creating such a wonderful extension. I love creating styles with it, and I love the benefits those styles provide me - it makes browsing my favorite sites so much more enjoyable.
As I explain in the description for all of my created styles, such as _this one_, if a user chooses to install one of my styles from the "Install Style from Social" drop-down box while on a given domain (gog.com, in this example), that style is not installed on its other intended domains, and there isn't even an option provided to the user to do this. Using the Social installation method, a user must install the same style for each applicable domain, such as for http://gog.com & for https://secure.gog.com, which should be completely unnecessary because they are the very same site, and because this is not the way it is done when installed from stylebot.me.
Obviously, this issue will tend to cause confusion for those choosing to use the Social installation method, and thus I believe this is best classified as a bug.
The text was updated successfully, but these errors were encountered: