This is so an accidental change in the drop-down doesn't do something the user isn't expecting and expose something they wanted private, so it's a feature, not a bug.
To clarify (and you'll know this, Rah, but just making sure it's known), that's not the initial reason why they're greyed out. LJ had it so that if you set a minimum security level, you *couldn't* select anything more public than that on a first post, but the options weren't greyed out, which caused confusion. The greying out was to bring the user interface in line with what already happened in the backend and prevent the confusion from *that*.
I hate the way this works, and I think mskala's reply makes sense, instead that I think it should go one further and have a separate option for "Default Posting Level". That's because there's no way to specify that at the moment for clients and no way to get that information, either, which means that clients are forced to default to an option by themselves - either public, or something you specify.
I would dearly love to see this fixed, and I'd be happy to code it, too. The only problem is it breaks expected behaviour for existing clients, which could be a problem, especially when crossposting client-side. :/
no subject
Date: 2009-04-15 09:37 pm (UTC)To clarify (and you'll know this, Rah, but just making sure it's known), that's not the initial reason why they're greyed out. LJ had it so that if you set a minimum security level, you *couldn't* select anything more public than that on a first post, but the options weren't greyed out, which caused confusion. The greying out was to bring the user interface in line with what already happened in the backend and prevent the confusion from *that*.
I hate the way this works, and I think
I would dearly love to see this fixed, and I'd be happy to code it, too. The only problem is it breaks expected behaviour for existing clients, which could be a problem, especially when crossposting client-side. :/