Hi Kenny,

I seem to recall coming across a similar problem and the way we approached it was to create an initialization module which updated the definition of the SelectionElementBlock to set the Items property to be localisable. If you want to do it manually, you could go into "admin" > "Content Type" > "[Basic Elements] Selection" then check the "Unique value per language" checkbox.

Thanks Paul, I did end up investigating the manual route yesterday but realized for this client that I didn't necessarily want to affect all Selection Element Blocks. (They have a Locations dropdown and it's kind of a pain to keep replicating.) 

So I approached this from another direction. I created a CultureSpecificSelectionElementBlock that inherits from SelectionElementBlock and made the Items CultureSpecific.

    public class CultureSpecificSelectionBlock : SelectionElementBlock
    {
        [CultureSpecific]
        public override IEnumerable<OptionItem> Items { get; set; }
    }

This way I can use the custom block for when I want the options language specific and the out-of-the-box Selection block when it doesn't matter.

Also, I feel I should point out that I think I get WHY the options aren't automatically CultureSpecific. You probably want the submitted value to be the same even when the visible text is specific to the user. With nothing in place to copy those over it would be up to the editor.

If anyone is interested I've got a blog post where I go into a deeper dive about custom form elements.