a cat named Tempest (isabeau) wrote in suggestions,
a cat named Tempest

Change S1 style browser to allow previews again

Change S1 style browser to allow previews again

Short, concise description of the idea
Due to the way customview currently works, the Style Browser cannot be used to preview another person's custom styles. This should be changed so that the Style Browser works again.

Full description of the idea
The S1 style browser was designed to allow you to both preview, and view the code of, another user's public styles. However, since that time, customview has been changed so that you can only view someone else's custom style on your journal if you explicitly mark it as trusted. For people who know about this change, it's rather of an annoyance having to dig up the styleid, go to the admin console, set the style as trusted, go back to the style browser, preview, and then repeat as necessary. For people who /don't/ know what's going on, they're just given a rather nonintuitive error message.

Probably the easiest way to give back functionality of the browser while retaining the security of the trust system, would be to change the links from previewing the viewing user's journal in that style, to previewing the style owner's journal in that style. (There could be an exception for system styles.)

Other options include making some sort of exception for the trusted thing for styles viewed within the style browser, providing an easy way (button/link) to trust the style, and other things I'm not thinking of. At the very least, the error message should be something more helpful than the "bad username, styleid, or style definition" error that's currently given.

If the style browser is changed at all, too, the customview links should be changed to use the new URL format rather than the old one. And it would be super-spiffy if the styleID number were more visible...

An ordered list of benefits
  • Easier to preview S1 styles
  • Restores functionality of the style browser
  • Would make me happy \o/

An ordered list of problems/issues involved
  • Possibly allows some of the problems that the customview change was meant to prevent?
  • Requires effort on a deprecated style system

An organized list, or a few short paragraphs detailing suggestions for implementation
  • Change things (aren't I helpful?)
Tags: s1, styles, styles: selection/customization interfac, § historical
  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded