When the property was changed, it now blows up on any browser with the previous configuration schema, explicitly checking for the expected text value without parsing.