Put_MES/.svn/pristine/5b/5bf5c978684b8c346b4ac2cdc334d5c68e9b9460.svn-base

.sidebar.sidebar-fixed {
	position: fixed;
	top: auto;
	float: none !important;
	
	z-index: @zindex-sidebar-fixed;//???!
	
	&:before {
		height: 5000px;
		top: auto;
		bottom: auto;
	}
}

 //android's default browser has a problem with "top: auto" when fixed
 body.mob-safari {
	 .sidebar.sidebar-fixed {
		top: @navbar-min-height;
	 }
	 @media (max-width: @screen-topbar-down) {
		.navbar-fixed-top:not(.navbar-collapse) + .main-container .sidebar-fixed {
			top: (@navbar-min-height * 2);
		}
	 }
	 //also when .navbar is fixed, .responsive sidebar becomes automatically fixed
	 @media (max-width: @grid-float-breakpoint-max) {
		.navbar-fixed-top + .main-container .sidebar.responsive {
			top: @navbar-min-height;
		}
	 }
	 @media (max-width: @screen-topbar-down) {
		.navbar-fixed-top + .main-container .sidebar.responsive {
			top: (@navbar-min-height * 2);
		}
	 }
 }

/**
//http://updates.html5rocks.com/2012/09/Stacking-Changes-Coming-to-position-fixed-elements
//webkit & Chrome22+ special case
//webkit is not following the standard specs as of Chrome22+
@media screen and (-webkit-min-device-pixel-ratio:0) {
	//like it happens in Firefox&IE, we expect when we set "z-index:auto" for fixed position .sidebar,
	//the child .submenu elements "z-index" is independent
	//and for example a "z-index:1031" .submenu appears on top of a fixed .navbar with "z-index:1030"
	//and a "z-index:1010" .popover appears on top of ".sidebar" but below ".submenu"
	//but webkit defines a new stacking context on "fixed" position elements(.sidebar here)
	//and the above doesn't happen, in fact .submenu inside fixed .sidebar with "z-index:auto" will appear below everything
	//so we set a good(?) "z-index" for .sidebar, but still it's not as good as standard specs (such as in Firefox)
	//and we may need other workarounds!
	//and you may change it based on your needs

	//it's possible have standard functionality in Chrome by going to:
	//chrome://flags/#fixed-position-creates-stacking-context
	//changing "Fixed position elements create stacking contexts" to "Disabled"
	//and removing the following rules
	//and assignning a higher "@submenu-zindex"

	.sidebar.sidebar-fixed {
		z-index: @zindex-sidebar-fixed;//???!
		
		&::before {
			height: 5000px;
			top: auto;
			bottom: auto;
		}
    }
}
*/




//************************************************************************************
//remove the following to disable fixed sidebar (style1 - default) on smaller devices
//if you also want to disable fixed breadcrumbs on smalelr devices, refer to breadcrumbs.less

@media only screen and (max-width: @grid-float-breakpoint-max) {
 .responsive.sidebar-fixed {
	left: auto;
	margin-left: auto;
 }

 //if `.menu-toggler` button is inside `fixed .navbar` let sidebar become fixed as well
 .navbar-fixed-top + .main-container > .responsive {
	position: fixed;
	left: auto;
	margin-left: auto;
	-moz-backface-visibility: hidden;
 }
 //but if `.menu-toggler` button is inside .main-container, then `fixed .navbar` should have no effect
 .navbar-fixed-top + .main-container > .menu-toggler + .responsive {
	position: absolute;
	left: (@sidebar-width);
	margin-left: -(@sidebar-width);
	-moz-backface-visibility: visible;
 }
 //unless specified as fixed
 .navbar-fixed-top + .main-container > .menu-toggler + .responsive.sidebar-fixed {
 	position: fixed;
	left: auto;
	margin-left: auto;
	-moz-backface-visibility: hidden;
 }
}

@media only screen and (max-width: @grid-float-breakpoint-max) {
 .sidebar.responsive.sidebar-fixed {
 		position: fixed;
		left: auto;
		margin-left: auto;
 }
 .main-container .menu-toggler.fixed {
	position: fixed;
	left: auto;
	z-index: @zindex-sidebar-fixed - 1;
	-moz-backface-visibility: hidden;
 }
 
 //for responsive style # 2
 //becuase ".sidebar.responsive-max" is "position: relative" & "margin-left: -190px"
 .sidebar.sidebar-fixed.responsive-max {
	position: fixed;
	left: auto;
	margin-left: auto;
 }
}