/* saved */ /* Start of CMSMS style sheet 'kontakt' */
#DkrContactForm {
    display: block;
    clear: both;
    margin: 0;
    padding: 10px 0 0 0;
    overflow: hidden;
    width: 230px;
}
    /* Komunitay **************************************************************/
    #DkrContactForm #messages {
        display: block;
        clear: both;
        margin: 0;
        padding: 0;
    }
    
        #DkrContactForm #messages ul {
            list-style: none;
        }
        
            #DkrContactForm #messages ul li {
                background-image: none;
            }
        
            #DkrContactForm #messages ul .fieldName {
                font-weight: bold;
            }
    /************************************************************** Komunitay */
    
    
    /* Formularz **************************************************************/    
    #DkrContactForm .form {
        display: block;
        clear: both;
        margin: 0;
        padding: 0;
    }
    
        #DkrContactForm .form fieldset {
            margin: 0;
            padding: 0;
            border: none;
        }
        
        #DkrContactForm .form fieldset.info {
            float: left;
        }
            
            #DkrContactForm .form fieldset.info .field, input {
                width: 135px;
               
            }
            
            #DkrContectForm .form fieldset.info label {
               background:#fff;}


        #DkrContactForm .form fieldset.message {
            float: right;
            width: 230px;
        }
            
            #DkrContactForm .form fieldset label {
                display: block;
                clear: both;
                background:none;
            }
            
            #DkrContactForm .form fieldset input, #DkrContactForm .form fieldset textarea {
                margin-bottom: 0;
font-size: inherit; font-family: Tahoma, sans-serif;
padding: 2px;
background:#793916 none repeat scroll 0% !important;
border:1px solid #280E01;
color:#fff;
            }
            
            #DkrContactForm input.submit {
                float: right;
	border: none !important;
	background: none !important;
	font-family: tahoma;
	font-size: 1em;
	color: #a95529;
	font-weight: bold;
        width: 100px;
       text-align: right;
            }
            
            #DkrContactForm  input.reset {
                float: left; 
	border: none !important;
	background: none !important;
	font-family: tahoma;
	font-size: 1em;
	color: #a95529;
        width: 100px;
	font-weight: bold;
        text-align:left;
            }
            
            #DkrContactForm .form fieldset input#subject {
                width: 224px;
            }
            
            #DkrContactForm .form fieldset textarea {
                width: 224px;
                height: 150px;
                overflow:auto;
            }
            
            #DkrContactForm .form fieldset .field {
                display: block;
                clear: both;
                margin: 0;
                padding: 0;
                margin-bottom: 8px;
            }
            
            #DkrContactForm .buttons {
                display: block;
                clear: both;
            }  
    /************************************************************** Formularz */

/* SpryFormValidation.css - version 0.5 - Spry Pre-Release 1.5 */

/* Copyright (c) 2006. Adobe Systems Incorporated. All rights reserved. */


/* These are the classes applied on the error messages
 * which prevent them from being displayed by default.
 */ 
.textareaRequiredMsg,
.textareaMinCharsMsg,
.textareaMaxCharsMsg,
.textareaValidMsg {
	display:none;
}

/* These selectors change the way messages look when the widget is in one of the error states.
 * These classes set a default red border and color for the error text.
 * The state class (e.g. .textareaRequiredState) is applied on the top-level container for the widget,
 * and this way only the specific error message can be shown by setting the display property to "inline".
 */
.textareaRequiredState .textareaRequiredMsg,
.textareaMinCharsState .textareaMinCharsMsg,
.textareaMaxCharsState .textareaMaxCharsMsg
{
	display: block;
    clear: both;
    margin-left: 2px;
    margin-bottom: 8px;
    padding: 3px;
    padding-right: 0;
	color: #CC3333;

}

/* The next three group selectors control the way the core element (TEXTAREA) looks like when the widget is in one of the states: * focus, required / minChars / maxChars , valid 
 * There are two selectors for each state, to cover the two main usecases for the widget:
 * - the widget id is placed on the top level container for the TEXTAREA
 * - the widget id is placed on the TEXTAREA element itself (there are no error messages)
 */
 
 /* When the widget is in the valid state the TEXTAREA has a green background applied on it. */
.textareaValidState textarea, textarea.textareaValidState {
	background-color:#B8F5B1;
}

/* When the widget is in an invalid state the TEXTAREA has a red background applied on it. */
textarea.textareaRequiredState, .textareaRequiredState textarea, 
textarea.textareaMinCharsState, .textareaMinCharsState textarea, 
textarea.textareaMaxCharsState, .textareaMaxCharsState textarea {
      /* background-color:#FF9F9F; */
}

/* When the widget has received focus, the TEXTAREA has a yellow background applied on it. */
.textareaFocusState textarea, textarea.textareaFocusState {
	/* background-color:#FFFFCC; */
}

/* This class applies only for a short period of time and changes the way the text in the textarea looks like.
 * It applies only when the widget has enforce max chars enabled and the user tries to type some more.
 */
.textareaFlashState textarea, textarea.textareaFlashState{
	color:red !important;
}
/* When the widget has the hint message on, the hint text can be styled differently than the user typed text. */
textarea.textareaHintState, .textareaHintState textarea{
	/* color: red !important;*/
}

/* SpryFormValidation.css - version 0.4 - Spry Pre-Release 1.5 */

/* Copyright (c) 2006. Adobe Systems Incorporated. All rights reserved. */


/* These are the classes applied on the error messages
 * which prevent them from being displayed by default.
 */ 
.textfieldRequiredMsg, 
.textfieldInvalidFormatMsg, 
.textfieldMinValueMsg,
.textfieldMaxValueMsg,
.textfieldMinCharsMsg,
.textfieldMaxCharsMsg,
.textfieldValidMsg {
	display: none;
}

/* These selectors change the way messages look when the widget is in one of the error states.
 * These classes set a default red border and color for the error text.
 * The state class (e.g. .textfieldRequiredState) is applied on the top-level container for the widget,
 * and this way only the specific error message can be shown by setting the display property to "inline".
 */
.textfieldRequiredState .textfieldRequiredMsg, 
.textfieldInvalidFormatState .textfieldInvalidFormatMsg, 
.textfieldMinValueState .textfieldMinValueMsg,
.textfieldMaxValueState .textfieldMaxValueMsg,
.textfieldMinCharsState .textfieldMinCharsMsg,
.textfieldMaxCharsState .textfieldMaxCharsMsg
{
    display: block;
    clear: both;
    margin-left: 2px;
    margin-bottom: 8px;
    padding: 3px;
    padding-right: 0;
	color: #CC3333;
}


/* The next three group selectors control the way the core element (INPUT) looks like when the widget is in one of the states: * focus, required / invalid / minValue / maxValue / minChars / maxChars , valid 
 * There are two selectors for each state, to cover the two main usecases for the widget:
 * - the widget id is placed on the top level container for the INPUT
 * - the widget id is placed on the INPUT element itself (there are no error messages)
 */
 
 /* When the widget is in the valid state the INPUT has a green background applied on it. */
.textfieldValidState input, input.textfieldValidState {
	background-color: #B8F5B1 !important;
	color: #fff !important;
}

/* When the widget is in an invalid state the INPUT has a red background applied on it. */
input.textfieldRequiredState, .textfieldRequiredState input, 
input.textfieldInvalidFormatState, .textfieldInvalidFormatState input, 
input.textfieldMinValueState, .textfieldMinValueState input, 
input.textfieldMaxValueState, .textfieldMaxValueState input, 
input.textfieldMinCharsState, .textfieldMinCharsState input, 
input.textfieldMaxCharsState, .textfieldMaxCharsState input {
	background-color: #FF9F9F !important;
	color: #fff !important;
}

/* When the widget has received focus, the INPUT has a yellow background applied on it. */
.textfieldFocusState input, input.textfieldFocusState {
	background-color: #FFFFCC;
}

/* This class applies only for a short period of time and changes the way the text in the textbox looks like.
 * It applies only when the widget has character masking enabled and the user tries to type in an invalid character.
 */
.textfieldFlashText input, input.textfieldFlashText {
	color: red !important;
}

/* When the widget has the hint message on, the hint text can be styled differently than the user typed text. */
.textfieldHintState input, input.textfieldHintState {
	/*color: red !important;*/
}


.formMessage {width: 100%; text-align: center; font-weight:bold;
padding-top:30px;}

/* End of 'kontakt' */

/* Start of CMSMS style sheet 'menu rozwijane' */
#primary-nav li ul li {width:148px; height:20px !important; background:#A75327 !important; text-align:left; padding: 2px 5px; border: 1px #3F1602 solid;}
#primary-nav li ul li a {color:#FFF;}

*:first-child+html #primary-nav li ul li a {height:auto;}

#primary-nav li ul li a:hover {/*background-color:#fff !important; color:#789EC5;*/ text-decoration:underline;}
#primary-nav ul a img {float: none; display: inline; border:0 !important;}

*html #primary-nav li a {float:left !important;}
*html #primary-nav li a img {border:0 !important;}

#top_menu {height:31px;}
	#primary-nav li {height:63px; float:left; position:relative;}
	#primary-nav > li > a {height:63px; display: block;}

/* Horizontal menu for the CMS CSS Menu Module */
/* by Alexander Endresen */

#menu_vert {
  margin-left: 1px;
  margin-right: 1px;
  zoom:1;
}

/* The wrapper clears the floating elements of the menu */

/* Fix for Opera 8 */
.clearb { clear: both; }
#menuwrapper {
  /* Fix for Opera 8 */
  /*   overflow: hidden;  */
width:auto;
margin:0 auto;

}

/* Set the width of the menu elements at second level. Leaving first level flexible. */


/* Unless you know what you do, do not touch this */
#primary-nav, #primary-nav ul {
  list-style: none;
  margin: 0px;
  padding: 0px;
}
#primary-nav ul {
  position: absolute;
  top: auto;
  display: none;
  zoom:1;
left:0;
padding-left:0 !important;
}

*html #primary-nav ul {
  position: absolute;
  top: auto;
  display: none;
  zoom:1;

}

*:first-child+html #primary-nav ul {
  position: absolute;
  top: auto;
  display: none;
  zoom:1;

}

#primary-nav ul ul {
  margin-top: 2px;
  margin-left: -1px;

  top: 0px;
  background:#56A83C;
  zoom:1;
width:148px;
}

#primary-nav ul li {display:inline;}

#top #primary-nav li li {
  margin-left: 0px;
  margin-top: -1px;
  float: none;
  position: relative;
  line-height:2.0em;
  font-size:90%;
  background:#56A83C;
  display:block;

}

/* Styling the basic apperance of the menu elements */

{*

#primary-nav a {
  display: block;
  margin: 0px;
  padding: 5px 10px;
  text-decoration: none;
  color: #006699;
}



#primary-nav li a {

}



#primary-nav li li a {
  border: 1px solid #C0C0C0;
}


#primary-nav li li a:hover {
text-decoration:underline !important;
}

#primary-nav li, #primary-nav li.menuparent {

}

*}

/* Styling the basic apperance of the active page elements (shows what page in the menu is being displayed) */

#primary-nav li.menuactive {

}

* html  #primary-nav li {position:relative !important;}
* html  #primary-nav li ul {left:0px !important; top:63px !important;}
* html  #primary-nav li ul li {overflow:hidden;}
{*
* html  #primary-nav li a {float: left;}
* html  #primary-nav li li a {float: none; display inline;}
*}
*:first-child+html #primary-nav li {position:relative !important;}
*:first-child+html #primary-nav li ul {left:0px !important; top:63px !important;}
*:first-child+html #primary-nav li ul li {height:auto !important;}

/* Styling the basic apperance of the menuparents - here styled the same on hover (fixes IE bug) */
#primary-nav ul li.menuparent,
#primary-nav ul li.menuparent:hover,
#primary-nav ul li.menuparenth {
/* arrow for menuparents */
  background-image: url(images/cms/arrow.gif);
  background-position: center right;
  background-repeat: no-repeat;
}


/* Styling the apperance of menu items on hover */

#primary-nav li:hover,
#primary-nav li.menuh,
#primary-nav li.menuparenth,
#primary-nav li.menuactiveh {

}


/* The magic - set to work for up to a 3 level menu, but can be increased unlimited */

/*
just add
#primary-nav li:hover ul ul,
#primary-nav li.menuparenth ul ul ul,
for fourth level
*/
#primary-nav ul,
#primary-nav li:hover ul,
#primary-nav li:hover ul ul,
#primary-nav li.menuparenth ul,
#primary-nav li.menuparenth ul ul {
  display: none;
}

/* add
#primary-nav ul ul ul li:hover ul,
#primary-nav ul ul ul li.menuparenth ul,
for fourth level
*/
#primary-nav li:hover ul,
#primary-nav ul li:hover ul,
#primary-nav ul ul li:hover ul,
#primary-nav li.menuparenth ul,
#primary-nav ul li.menuparenth ul,
#primary-nav ul ul li.menuparenth ul {
  display: block;
}

/* IE Hacks */
#primary-nav li li {
  float: left;
  clear: both;
}
#primary-nav li li a {
  height: 1%;
}

/* End of 'menu rozwijane' */