.theme-background {
	background-repeat: no-repeat;
	min-height: 700px;
	padding: 40px 0;
	background-position: center center;
	background-attachment: fixed;
	-webkit-background-size: 100% auto;
	-moz-background-size: 100% auto;
	-o-background-size: 100% auto;
	/*background-size: cover;*/
}

@media (min-width: 1200px) {
	.theme-background {
		min-height: 100vh !important;
	}
}

@media (max-width:600px) {
.theme-background {
    -webkit-background-size: auto;
  -moz-background-size: auto;
  -o-background-size: auto;
  background-size: auto;
}
}

/*colour picker*/
input.colour-picker {
	vertical-align: top;
	width: 20%;
}
.form-horizontal .controls input[type="text"].colour-picker {
	width: 20%;
}
.colour-swatch {
	width: 24px;
	height: 24px;
	border: 1px solid #ccc;
	display: inline-block;
	margin: 2px;
	cursor: pointer;
}
span.colour-hash {
	vertical-align: top;
	padding: 5px 2px 0 0;
	display: inline-block;
}

/*uploaded images*/
.uploaded-image{
	border: 2px dashed #666;
	padding: 10px;
}

/*maps*/
.map-container {
	border: 8px solid #fff;
	background-color:#fff;
    width:100%;
    box-shadow: 0px 0px 3px #ccc;
}
	.map-container span{
		left: 25%;
		top: 42%;
		display: block;
		position: relative;
	}
	.map-container span.right {
		left: -25%;		
	}
/*dates*/
.date 
{
	float: left;
	color: black;
	border-top-style: solid;
	text-align: center;	
	padding: 4px 10px;
	border-top-width: 8px;
}
	.date .day {
		font-size: 28px;
		line-height: 28px;
		display: block;
		clear: both;
		font-weight: bold;
	}
	.date .month {
		font-size: 12px;
		line-height: normal;
		display: block;
		clear: both;
		font-weight: bold;
	}
.date .year {
	font-size: 10px;
	line-height: normal;
	display: block;
	clear: both;
	font-weight: bold;
	color: #9B9B9B;
}
/*headline text*/
.headline{ font-size: 46px;font-weight: bold;line-height: normal;padding: 4px 10px; /*background: black;color: white;*/ display: inline-block;}
.headline.smaller { font-size: 40px;}

/*subheadline text*/
.subhead{ font-size: 24px;font-weight: bold;line-height: normal;padding: 4px 10px;background: black;color: white;display: inline-block;}

/*event title*/
.event-title h1 {
	float: left;
}
.event-title span{
	display: inline-block;
	float: left;
	clear: left;
	font-size: 25px;
	line-height: 25px;
}

/*header*/
.header {
	min-height: 95px;
	padding: 0 0px;
}
header .logo {
	padding: 50px 0 10px 0; /*10px 0;*/
	max-width: 320px;
	text-align: center;
	margin: 0 auto;
}

@media (min-width:768px) {
   header .logo {
    float:left;
    margin:0px 0 10px 0;
    }

    .top-nav {
    margin-bottom:-55px;
    }
}


.venue {
	/*background: #ff0;
	color: #000;*/
	font-weight: bold;
	padding: 4px 10px;
	font-weight: bold;
	display: inline-block;
}
	.venue a {
		color: #000;
	}

    .lt-ie8 .venue a {
        margin:0px 0px 0px -25px;
    }

/*featured event*/
.featured-event .date{
	/* background: white; */
	float: left;
	color: black;
	padding: 6px 15px 5px 15px;
	border-top-width: 14px;
	border-top-style: solid;
	text-align: center;
    z-index:2; 
    box-shadow: 0px 0px 3px #333;
    -webkit-box-shadow:  0px 0px 3px #333;
    -moz-box-shadow:  0px 0px 3px #333;
    position:relative;
}

.featured-event .date-classic-template {
	background-color: #fff;
}

    .featured-event .date.expired {
        color:#ccc;
        position:relative;
       
    }

     .expired-sash {
        /* background:transparent url(../images/past.png) no-repeat top right; */
        z-index:2;
        width: 70%;
		background: #FF0100;
		color: #ffffff;
		text-align: center;
		border-radius: 5px;
		font-size: 14px;
		margin-left: 8px;
		padding: 1px 3px;
    }
	@media only screen and (max-width: 769px) {
		.expired-sash {
			left: 100%;
			margin-left: 5px;
			font-size: 12px;
		}
	}

.lt-ie9 .featured-event .date{
    padding: 7px 15px 6px 15px;
}

.featured-event.mini .date
{
	padding: 4px 10px;
	border-top-width: 8px;
}
	.featured-event .day {
		font-size: 60px;
		line-height: 53px;
		display: block;
		clear: both;
		font-weight: bold;
	}
	.featured-event.mini .day {
		font-size: 28px;
		line-height: 28px;
	}
	.featured-event.compact .day {
		font-size: 55px;
		line-height: 50px;
	}
	.featured-event .month {
		font-size: 22px;
		line-height: normal;
		display: block; clear: both; font-weight: bold;
	}
	.featured-event.mini .month {
		font-size: 12px;
	}	
	.featured-event.compact .month {
		font-size: 20px;
	}
	.featured-event .year {
		font-size: 14px;
		line-height: normal;
		display: block; clear: both; font-weight: bold;
		color: #9B9B9B;
	}

	.featured-event.mini .year {
		font-size: 10px;
	}		
	.featured-event.compact .year {
		font-size: 13px;
	}
.featured-event .details {
	float: left;
	padding-left: 0px;
    z-index:1; 
    position:relative;
}
.featured-event.compact .details {
	padding-left: 0;
}
	.featured-event  h2 
	{
		float: left;
		margin-bottom: 0;
		margin-top: 0;
	}
		.featured-event  h2 a {
			color: white;
		}
	.featured-event .venue{
		float: left;
		clear: left;
		font-size: 22px;
		line-height: normal;
	}
	.featured-event .availability {
		background: #fffccb;
		color: #000;
		float: left;
		clear: left;
		padding: 4px 10px;
		font-size: 14px;
	}
	.featured-event .tickets {
		color: #f45000;
		font-weight: bold;
	}

.first-header-row{
	background-color: #004774;
	color: #fff;
}
.header-row{
	background-color: #d7efff;
	color: #000;
}

.event-questions {
    float:left;
    width:100%;
    }

    .event-questions fieldset {
        float:left;
        width:98%;
        padding:0px 1%;
        margin-bottom:20px;
        }

.question-block {
    float:left; 
    padding:10px 0px;
    width:100%;
    }

    .event-questions ol {
    margin:0px;
    padding:0px 0px 0px 20px;
    }

        .event-questions ol li {
            float: left;
            width:100%;
        }

        .lt-ie8 .event-questions ol , .lt-ie8 .event-questions ol li {
       float: none;
         }


#add-question-popup {
    /* margin: 10px 0px 0px 0px; */
    display:none;
}

.question-block dd {
margin:0px 0px 2px 0px;    
}

.edit-line {float:left; width:100%; margin:5px 0px 10px 0px;}
span.edit-line {font-size:14px; padding:0px 0px 0px 5px; width:auto; float:none; }

.question-block dd .edit-line a{ font-weight:normal; padding:0px 5px 0px 0px;  }

#current-event-questions {
    background-color:#D7EFFF;
    padding:2% 3% 0% 3%; width:94%;
    margin:0px 0px 20px 0%;
    }

.add-question {
    float:left;
    width:92%;
    background-color:#FFFCB7;
    margin:10px 0px 0px 0px;
    padding:1% 4%;
    border:1px solid #ece77f
}

    .add-question .control-group {
    float:left; 
    width:100%;
    margin-bottom:5px;
    }

        .add-question .control-group label {
        float:left;
        font-weight:bold;
        margin:0px 0px 4px 0px;
        width:100%;
        }

        .add-question .control-group input[type="text"] {
        width:94%;
        }
/* ---------------------------------------------------------------- survey answers
 *
 * Shared by both survey renderers - the host form on .sw-form-vertical and the guest
 * form on the older <ol> branch - because the markup they emit for an answer is now
 * the same. Colour, spacing and type come from tokens.css; the button role comes from
 * Bootstrap and styles.css, and nothing here redeclares it.
 *
 * Every rule is keyed on a survey-only class (.sw-survey-answer, .sw-scale,
 * .feedback-question-text ...), never on a bar class alone. .sw-form-controls is the
 * SW-4047 horizontal form's control column, so a rule on it here would restyle the
 * radios and checkboxes of every settings form in the app.
 */

/* A numeric scale: a row of chips, one per point.
 *
 * Its own class rather than .btn-check + .btn.btn-secondary, which is where this
 * started. Borrowing the button role meant anything styling buttons on a tenant-themed
 * guest page reached the answers - one tenant rendered the whole row as filled blocks,
 * so every option looked chosen. Answers are not actions and do not share a role.
 *
 * The chip sits on the card border weight, not the control border weight, so a row of
 * ten does not compete with the textarea above it. */
.sw-scale {
    display: flex;
    flex-wrap: wrap;
    gap: var(--sw-space-2);
    /* the group starts on the question's left edge, whatever the surrounding sheet
       does to lists and inputs on the older guest survey */
    margin: 0;
    padding: 0;
}

/* Hidden, not removed: still focusable, still in the tab order, still announced.
 * Not display:none, which would take it out of both. */
.sw-scale__input {
    position: absolute;
    width: 1px;
    height: 1px;
    margin: 0;
    padding: 0;
    opacity: 0;
    pointer-events: none;
}

/* Type is set, not inherited. Both surveys sit under sheets that colour loose text -
 * the numbers were picking up a link colour - and the tenant theme sets the family on
 * body, so only size, weight and colour are named here and the family still cascades. */
.sw-scale__option {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    min-width: 48px;
    min-height: 44px;                    /* WCAG 2.5.5 */
    margin: 0;
    padding: 0 var(--sw-space-3);
    border: 1px solid var(--sw-border);
    border-radius: var(--sw-radius-sm);
    background: var(--sw-surface);
    color: var(--sw-text);
    font-size: var(--sw-font-size);
    font-weight: normal;
    line-height: 1;
    text-align: center;
    font-variant-numeric: tabular-nums;  /* 1 and 10 sit on the same rhythm */
    cursor: pointer;
}

.sw-scale__option:hover {
    background: var(--sw-surface-hover);
}

/* Selected takes the tenant's navigation pair, falling back to the neutral.
 *
 * This read "selected is a neutral, not a brand fill" until SW-3946, on the strength of
 * a failure that was real but is not this one. The old markup was
 * .btn-check + .btn.btn-secondary, so tenant BUTTON styling landed on every option at
 * once and a whole row looked chosen. Painting only :checked cannot do that - exactly
 * one chip in the group is filled, which is the entire signal.
 *
 * The pair is the navigation bar's, published as custom properties by Theme.cshtml:
 * the active link colour on the bar it sits on. Two reasons it is that pair and not
 * LinkColour or MenuLinkColour. It is company-level and on the company theme screen,
 * where MenuLinkColour is a CATEGORY field that defaults to white and is a menu TEXT
 * colour, not a fill - a chip built from it comes out white on white. And contrast is
 * symmetric, so inverting a pairing the customer already approved on their own nav
 * gives the chip exactly the ratio their navigation has. LinkColour has no partner at
 * all, so white on it would be a guess.
 *
 * The fallback is the token, so a tenant who has not themed their nav is unchanged:
 * --sw-text on --sw-text-inverse, 15.8:1. The fallback lives here rather than in
 * tokens.css because these names are the theme's, not the platform's - same as
 * --TableHeaderColour.
 *
 * Weight is the safety net for a pale nav colour, where a filled chip is otherwise
 * hard to tell from an empty one. Selection is also carried by :checked on a real
 * radio in a role="radiogroup", so colour is never the only signal - general rule 9. */
.sw-scale__input:checked + .sw-scale__option {
    background: var(--GuestButtonBackgroundColour, var(--NavigationActiveLinkColour, var(--sw-text)));
    border-color: var(--GuestButtonBackgroundColour, var(--NavigationActiveLinkColour, var(--sw-text)));
    color: var(--GuestButtonTextColour, var(--NavigationBackgroundColour, var(--sw-text-inverse)));
    font-weight: var(--sw-font-weight-medium);
}

.sw-scale__input:focus-visible + .sw-scale__option {
    outline: none;
    border-color: var(--sw-border-focus);
    box-shadow: var(--sw-focus-ring);
}

/* The free-text answer fills its column.
 *
 * responsive.css:666-670 puts `width: 82%; max-width: 500px` on a bare `textarea`
 * selector inside @media (min-width: 481px) - comma-joined to a
 * `.form-horizontal .controls input[type="text"]` rule it was presumably meant to be
 * scoped by, so it caps every textarea in the app. Width alone does not beat it; the
 * cap has to be lifted too.
 *
 * Here rather than in the survey's page sheet, which is linked by four host views and
 * not by the guest layout - so the fix reached the internal form and left the public
 * one stopping at 500px inside a 640px card. Keyed on the survey's own textarea class:
 * the cap is app-wide, but lifting it everywhere is a design-system change, not this
 * ticket's. */
textarea.form-control.feedback-question-text {
    width: 100%;
    max-width: 100%;
}

/* The select is sized by its content - styles.css forces `select { width: auto }` -
 * so a long option can push it past the card on a phone. Cap it, and keep a floor so
 * "Please select..." does not collapse to a stub. No width: the !important above owns
 * that, and auto is what is wanted anyway. */
.feedback-question-dropdown {
    min-width: 220px;
    max-width: 100%;
}

/* Section header.
 *
 * It was a bare <h4>, so its size depended on which wrapper the survey sat in.
 * On the host form styles.css's `.new-layout-wrapper h4 { font-size: 1.3rem }` quietly
 * cut it back and it looked right; the guest form is not inside a .new-layout-wrapper,
 * so it fell through to Bootstrap's own h4 - calc(1.275rem + 0.3vw), 1.5rem past
 * 1200px - and outsized the survey's own title.
 *
 * Sized here instead, so it is the same header on both. Typed as h4.sw-survey-section
 * to match the specificity of that wrapper rule; this sheet loads after styles.css, so
 * it wins the tie. More space above than below: a header belongs to what follows it. */
h4.sw-survey-section {
    font-size: var(--sw-font-size-xl);
    font-weight: var(--sw-font-weight-bold);
    margin: var(--sw-space-6) 0 var(--sw-space-2);
}

/* One selected state for the whole survey.
 *
 * A scale chip fills with --sw-text, but a radio's dot is painted by the browser and
 * defaults to its own blue, which no tenant theme reaches - so a form could show a
 * black chip and a blue dot in the same column, two answers to the same question of
 * "what does chosen look like here". accent-color settles it in one declaration and
 * leaves the native control otherwise alone.
 *
 * It tracks the chip above, fallback and all: whatever :checked fills with, this takes.
 * They are one decision, and moving only one of them is the bug this rule exists to
 * stop - a branded 1-10 row beside a dark Yes/No dot on the same form. */
.sw-survey-answer input[type="radio"],
.sw-survey-answer input[type="checkbox"] {
    accent-color: var(--GuestButtonBackgroundColour, var(--NavigationActiveLinkColour, var(--sw-text)));
}

/* Bootstrap indents .form-check by 1.5em and floats .form-check-input back into that
 * gutter with a negative margin. Shared/FormControl undoes both, but only inside
 * .sw-form-vertical - so on the guest survey, which is not in one, the float stayed:
 * the radio hung above-left of its own label and the text dropped to the next line.
 *
 * Undone here too, scoped to a survey answer group, with the same values FormControl
 * uses so a question inside .sw-form-vertical is unchanged. Display is left alone
 * deliberately: .form-check-inline must stay inline-level or the row stops being a row. */
.sw-survey-answer .form-check {
    padding-left: 0;
    margin-bottom: 0;
    flex-wrap: nowrap;
}

.sw-survey-answer .form-check-input {
    float: none;
    margin: 0 var(--sw-space-2) 0 0;
}

/* Named options - Yes / No, or a question's own option list.
 * The label is the target, not the 13px input beside it.
 *
 * The 44px comes from the row, and the label stretches to fill it. It used to be
 * min-height on the label itself, which was the bug behind the dropped text: the label
 * is inline-level, so a tall inline box next to an inline input is laid out on a line
 * and wrapped whenever the two could not share one. A flex row cannot wrap like that,
 * and align-self keeps the whole 44px clickable rather than just the text inside it. */
/* The .sw-form-vertical copies are not redundant. Shared/FormControl styles
 * `.sw-form-vertical .form-check` at the same specificity as the plain selectors
 * below and loads after this sheet on _Layout, so without the longer selector the
 * host and guest surveys lay their options out differently. Same rule, both. */
.sw-form-vertical .sw-survey-answer .form-check,
.sw-form-vertical .sw-survey-answer .FeedbackQuestionRadioButton,
.sw-survey-answer .form-check,
.sw-survey-answer .FeedbackQuestionRadioButton {
    display: flex;
    align-items: center;
}

/* An inline option must stay inline-level or the row stops being a row.
 * After the block rule above, so it wins the tie. */
.sw-form-vertical .sw-survey-answer .form-check-inline,
.sw-form-vertical .sw-survey-answer .FeedbackQuestionRadioButton,
.sw-survey-answer .form-check-inline,
.sw-survey-answer .FeedbackQuestionRadioButton {
    display: inline-flex;
}

/* The target is grown with padding on the label, not a fixed height on the row.
 *
 * It was min-height: 44px, in two places in turn. On the label it was the bug behind
 * the dropped text - a label is inline-level, so a tall inline box beside an inline
 * input gets laid out on a line and wraps when the two cannot share one. Moved to the
 * row it stopped wrapping, but inflated a 20px line to 44 on every option, which reads
 * as a gap in the form rather than as a control.
 *
 * 44px is WCAG 2.5.5, which is AAA. The AA requirement is 2.5.8 at 24x24, and padding
 * clears that while the row still sizes to its own text. The scale chips keep the full
 * 44: there the height is the control itself, not space around it.
 *
 * align-self makes the label fill the row, so the padded area is all clickable. */
.sw-survey-answer .FeedbackQuestionRadioButton label,
.sw-survey-answer .form-check-label {
    display: flex;
    align-items: center;
    align-self: stretch;
    padding-block: var(--sw-space-1);
    gap: var(--sw-space-2);
    margin: 0;
    cursor: pointer;
}

/* Inline wrapping turns "Coach provided by the host" into a ragged line that reads as
 * two options. Past three, or one longer than a few words, they stack. */
.sw-choices--stacked {
    display: flex;
    flex-direction: column;
    align-items: flex-start;
    gap: var(--sw-space-1);
}

.sw-choices--stacked .form-check-inline {
    margin-right: 0;
}

/* The answer's own error. Shared/FormControl already forces this visible inside
 * .sw-form-vertical; the guest form is not in one, so it needs saying here too. */
.sw-feedback-error {
    display: block;
    margin-top: var(--sw-space-1);
}

/* Guest Management filter row: the event picker and the selects beside it share one width, so a
   tab's filters read as a set and a long event name does not stretch the row. */
.gm-filter-select {
    width: 24rem;
    max-width: 100%;
}

/* A filter that only applies once another is chosen starts hidden; the legacy filter-row rules
   would otherwise override the hidden attribute with their own display. */
.gm-filter-select[hidden] {
    display: none !important;
}

/* The allocation filter lists chips for what is picked, so it gets the grouped picker's full width. */
.gm-filter-select--allocations {
    width: var(--sw-form-control-max-width, 500px);
}

/* Each allocation row's counts in the grouped picker. The icons are the e-ticket document icons,
   whose stroke rules live with the document icon styles, so the few that matter are repeated here
   for tabs that do not load those. */
.sw-allocation-counts {
    display: inline-flex;
    gap: 10px;
    flex-shrink: 0;
    margin-left: auto;
    color: var(--sw-form-placeholder-color, #767676);
    font-size: 13px;
    font-variant-numeric: tabular-nums;
    white-space: nowrap;
}

.sw-allocation-counts--short {
    color: var(--bs-danger, #dc3545);
}

.sw-allocation-counts__count {
    display: inline-flex;
    align-items: center;
    gap: 3px;
}

.sw-allocation-counts .sw-doc-line {
    fill: none;
    stroke: currentColor;
    stroke-width: 1.35;
    stroke-linecap: round;
    stroke-linejoin: round;
}

.sw-allocation-counts .sw-doc-fill {
    display: none;
}

/* SingleSelect hides the select and draws its own box beside it, so ng-hide on the select alone
   would leave that box showing while a tab is still loading its events. */
.gm-filter-select select.ng-hide + .select2-container {
    display: none !important;
}

/* A Number order field over the quantity requested. The request forms predate FormControl,
 * so Bootstrap only reddens .form-control.is-invalid; these inputs carry no .form-control.
 * [type="number"] lifts this above the request pages' own `.reqSubmissionDiv input[type=number]`
 * border, which otherwise wins on load order. The message takes the same token, as FormControl's
 * does, rather than Bootstrap's slightly different red. */
input[type="number"][data-quantity-limit].is-invalid {
    border-color: var(--sw-danger);
}

input[data-quantity-limit] ~ .invalid-feedback {
    color: var(--sw-danger);
}
