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

Theme options broken #51

Open
loopy750 opened this issue Nov 29, 2023 · 8 comments
Open

Theme options broken #51

loopy750 opened this issue Nov 29, 2023 · 8 comments

Comments

@loopy750
Copy link

After being mirrored from Userstyles, comments are being removed, including theme comments, eg: /*[[font]]*/

Changing settings on the theme therefore has no effect.

@tophf
Copy link

tophf commented Nov 29, 2023

Apparently they've disabled the API to get the original CSS just to thwart our efforts. They even broke "Show CSS" button on their site.

@loopy750
Copy link
Author

Dang, thanks for the update. They really broke a lot of stuff with the major overhaul, including browsing with Firefox, as mentioned in the other thread. I even reported the issue, and am not one for a conspiracy, but it sure seems intentional.

Good to know I didn't do something wrong, but sucks that it means it's broken for everyone.

@tophf
Copy link

tophf commented Nov 29, 2023

@33KK, here's an idea: make the API request for style sections using unique random values for style variables, then replace them in the result with /*[[name]]*/ comments.

@33KK
Copy link
Collaborator

33KK commented Nov 29, 2023

@33KK, here's an idea: make the API request for style sections using unique random values for style variables, then replace them in the result with /*[[name]]*/ comments.

That's exactly what I am doing right now. Dropdowns are indeed broken though. Unless they changed anything else the other settings should work

@33KK
Copy link
Collaborator

33KK commented Nov 29, 2023

Right, your styles only use dropdowns. That's why they are broken. Recovering dropdown options isn't trivial and I gave up on it because their website was (maybe still is) broken and didn't even parse sections correctly

@tophf
Copy link

tophf commented Nov 29, 2023

The web site or do you use the API for getStyleCustomOptions?

@33KK
Copy link
Collaborator

33KK commented Nov 29, 2023

I do what their site is doing

@tophf
Copy link

tophf commented Nov 29, 2023

Then maybe there's another way? I've been using getStyleCustomOptions and it still works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants