body { color:#222; font-family: 'Montserrat', sans-serif; font-size:14px; line-height: 1.5; overflow-x: hidden; background:#fff   }

/* line-height:1.5 above + the input/button/select/textarea rule below, added
   2026-09-23 - same root cause as the a{text-decoration:none} and h1-h6
   rules already restored in this file: deleting bootstrap.css in the
   2026-08-11 cleanup dropped Bootstrap's OWN global resets along with its
   grid, and these two were missed until now. (1) `body{line-height:1.5}` -
   bootstrap.css set this directly on body; without it, body's computed
   line-height is the bare browser default (~1.15), not 1.5, for every piece
   of text site-wide that doesn't carry its own explicit Tailwind `leading-*`
   class. The `.cms-content{line-height:1.5}` patch in legacy-grid.css
   (2026-08-11) fixed only the ONE symptom reported at the time (CMS
   rich-text spacing) without catching that the underlying body rule itself
   was gone - removed now that this fixes it at the actual source. (2) form
   controls (`input`/`button`/`select`/`textarea`) do NOT inherit
   font-family/font-size/line-height from their parent by default in any
   browser's UA stylesheet - Bootstrap's reboot.css explicitly resets this
   (`font-family:inherit` etc.) so form fields match the page's type instead
   of falling back to the browser's native control font (Arial, ~13px).
   Surfaced live on the footer newsletter input: reported as visibly
   shorter/narrower than the real site ("visina elemenata ne odgovara,
   sužen") - measured live, computed style was font-family:Arial,
   font-size:13.33px, line-height:normal (height 36.4px) vs the real
   www.msu.hr's Montserrat/14px/21px (height 42.8px) on the exact same
   element. Every OTHER form control site-wide was masked from this because
   it already carries its own explicit Tailwind text-size class (ContactForm,
   SearchBox, admin inputs) - this footer form is one of the few ported with
   literal legacy values and no Tailwind type classes of its own, so it was
   the one to expose the gap. */
input, button, select, optgroup, textarea {
	margin: 0;
	font-family: inherit;
	font-size: inherit;
	line-height: inherit;
}

/* table{border-collapse:collapse} added 2026-09-23 - same dropped-Bootstrap-
   reset pattern (bootstrap-reboot.css's own `table{border-collapse:collapse}`),
   found while auditing "ostale tablice" after the documents-table fix above.
   Queried the DB directly rather than guessing: 18 mod_clanci/mod_dogadanja/
   mod_stranice rows have a raw <table> pasted straight into their rich-text
   content (mod_sadrzaj) by an editor - e.g. mod_stranice #101's accessibility-
   statement criteria table (`<table border="1" width="869">`, no class at
   all). These aren't Documents.tsx's table (that one sets its own
   border-collapse directly, unaffected by this) - they're raw HTML sitting in
   the database with no component to attach a Tailwind class to, so this has
   to be a global CSS reset to reach them, exactly like the row/col-md-12 CMS
   grid compat rules in legacy-grid.css. Confirmed against the real
   www.msu.hr/stranice/digitalna-pristupacnost/101.html: its table's border
   color/padding need NO extra CSS at all (border-color defaults to
   `currentColor` = body's #222, padding is genuinely 0 on a classless table,
   both true automatically) - `border-collapse` was the one actual gap,
   without it these tables render with `separate` (the browser default),
   doubled-up borders instead of the clean single-line grid legacy shows. */
table {
	border-collapse: collapse;
}

/* a{text-decoration:none} added 2026-08-12 - not in the original master.css,
   which only ever had the :hover rule below. Legacy's actual base-state
   underline removal came from Bootstrap's own reset (`a{text-decoration:none}`
   in bootstrap.css), deleted from this project during the 2026-08-11 cleanup
   pass as "confirmed dead" (true for its .container/.row grid rules, false
   for this one line - nothing else in the migration replaced it). Every
   plain <a> site-wide was silently falling back to the raw browser default
   (underlined) until reported live on the slider's prev/next arrows -
   restoring it here, in the same file, right next to the hover rule it was
   always meant to pair with, rather than only patching the one component
   that happened to surface it.
   color:#007bff/#0056b3 added 2026-09-23 - same dropped-Bootstrap-reset
   pattern (`a{color:#007bff}` / `a:hover{color:#0056b3}`, bootstrap.css:190-
   198): every plain link that isn't given its own explicit Tailwind text
   color (raw CMS-content links, the documents table's title links) was
   falling back to the bare browser default blue/visited-purple instead of
   Bootstrap's blue - reported live with an old-vs-new screenshot comparison
   on a "pravo na pristup informacijama" page. `a:hover` here keeps its
   original text-decoration:none (a real MSU-authored rule, predates
   Bootstrap removal entirely - not touched), just gains the matching hover
   color. */
a { color: #007bff; text-decoration: none;}
a:hover { color: #0056b3; text-decoration: none;}

/* h1-h6 base sizing added 2026-08-12 - same root cause as the a{text-decoration:none}
   bug above: deleting bootstrap.css in the 2026-08-11 cleanup pass dropped its global
   `h1..h6{font-weight:500;line-height:1.2;...}` + per-level font-size rule, which every
   legacy heading depended on since master.css itself never restyles h1-h6 except the
   slider's own explicit override (see #slider-container .row h1 below). Surfaced live
   on the slider's podnaslov: legacy's LOOP::indexSlider() (LOOP.class.php:39) renders
   raw `<h5>{mod_podnaslov}</h5>` with NO class at all, so it always relied entirely on
   this base rule - without it, the browser's bare UA default took over (0.83em/700
   weight) instead of Bootstrap's 1.25rem/500 weight, reading as noticeably smaller AND
   bolder than the real site. Restoring the exact Bootstrap values here (not just for
   h5) since the same raw-HTML-heading pattern (cms-content, dangerouslySetInnerHTML)
   is used for mod_sadrzaj/mod_podnaslov site-wide, not only on the slider - any h1-h6
   a CMS editor put in that rich text depended on this same base rule. Components that
   need a different look already set explicit Tailwind text-size/font-weight classes,
   which win regardless (this file loads into the lowest-priority `legacy` layer - see
   tailwind.css).
   line-height corrected 1.1 -> 1.2 on 2026-09-23: originally read off the LOCAL,
   unminified `bootstrap.css` in the legacy source tree, assuming it matched what's
   actually served. It doesn't always - MSU's real production `bootstrap.min.css` has
   its own hand-edits in places (see the `.table`/link-color fix in Documents.tsx, same
   day, found via the same mistake). Re-verified this one specific value by fetching
   the live www.msu.hr/tpl/stil/css/bootstrap.min.css directly: its combined
   `.h1,.h2,...,h1,h2,...{font-weight:500;line-height:1.2;...}` rule is unminified-
   Bootstrap's stock value here (1.2, not 1.1) - this file's own copy just had the
   wrong number, not a real MSU customization. Everything else in this block was
   cross-checked against the same live file and does match. */
h1, h2, h3, h4, h5, h6 {
	margin: 0 0 0.5rem 0;
	font-family: inherit;
	font-weight: 500;
	line-height: 1.2;
	color: inherit;
}
h1 { font-size: 2.5rem; }
h2 { font-size: 2rem; }
h3 { font-size: 1.75rem; }
h4 { font-size: 1.5rem; }
h5 { font-size: 1.25rem; }
h6 { font-size: 1rem; }

a.opsirnije {background:#fff; border:1px solid #111; font-size:12px;  display:inline-block; padding-right:10px; color:#111;  margin:10px 0px }
a.opsirnije i {display:inline-block; padding:10px; font-size:16px; border-right:1px solid #111; color:#111}
a.opsirnije:hover {background:#111; border:1px solid #111; font-size:12px;  display:inline-block; padding-right:10px; color:#fff;  }
a.opsirnije:hover i {display:inline-block; padding:10px; font-size:16px; border-right:1px solid #fff; color:#fff; -moz-animation: bounceRight 1s infinite;
	-webkit-animation: bounceRight 1s infinite;
	animation: bounceRight 1s infinite;}

a.opsirnije2 {background:#fff; border:1px solid #111; padding:20px; font-size:12px;  display:inline-block;   color:#111;  margin:10px 0px ; font-weight:bold;}
a.opsirnije2:hover {background:#111; border:1px solid #111; font-size:12px;  display:inline-block;   color:#fff;  }

button.opsirnije2 {background:#fff; border:1px solid #111; padding:20px; font-size:12px;  display:inline-block;   color:#111;  margin:10px 0px ; font-weight:bold;}
button.opsirnije2:hover {background:#111; border:1px solid #111; font-size:12px;  display:inline-block;   color:#fff;  }


/* .arrowRight removed 2026-08-11 - ported to real Tailwind directly on
   Slider.tsx's arrow span (group-hover:w-[60px] etc.) as part of fixing the
   span/`a.arrowRight` tag-mismatch bug that made this rule never actually
   match anything - see that file's own comment. */
a.arrowDown  {width:100% ; height:30px; background:url(../img/arrowDown.png) bottom center no-repeat; display:block; margin:10px 0px; -webkit-transition: width .35s ease-in-out;
  transition: height .35s ease-in-out;}
a.arrowDown:hover {height:60px;}

a.arrowDown.ffffff {width:100% ; height:30px; background:url(../img/arrowDownWhite.png) bottom center no-repeat; display:block; margin:10px 0px; -webkit-transition: width .35s ease-in-out;
  transition: height .35s ease-in-out;}
a.arrowDown.ffffff:hover {height:60px;}

/* #search-box/#search-results/.search-title (base tier) removed 2026-08-11
   - ported to real Tailwind directly in Header.tsx/SearchBox.tsx (including
   the mobile-breakpoint tier further down this file) - see those files' own
   comments. */


/* .sk-folding-cube/.sk-cube* + @keyframes sk-foldCubeAngle removed
   2026-08-11 - a loading-spinner animation confirmed dead, zero matches
   anywhere in the codebase (no component ever renders a `.sk-folding-cube`
   element). */

/* Bare `svg{}`/`path{}` element selectors (+ `.open`/`path#top,#bottom`/
   `path#middle`/`.cross path#*`) removed 2026-08-11 - this was the same
   dangerous unscoped-selector landmine OmoWidget.tsx already had to
   defensively work around for its own icons (every plain <svg>/<path>
   anywhere on the page matched these, size/stroke included, regardless of
   what it actually was). Header.tsx was the only real dependent (its
   hamburger icon) and now sets its own explicit size + computes the
   open/closed stroke animation directly per path via React state instead -
   see that file's own comment. OmoWidget.tsx's defensive override
   (`.omo-widget-container svg{width:auto;height:auto}` etc.) stays as a
   harmless no-op now that the rule it was countering is gone, rather than
   removing it and adding a new implicit assumption about master.css's
   contents. */
/* .prev-next/.nextItem/.gallery .col-md-6 removed 2026-08-11 - confirmed
   dead (repo-wide grep, zero matches). .prevItem stays - DogadanjePage.tsx
   uses it for both its prev/next links. */
.prevItem {padding:10px; color:#111; border:1px solid #111; }
	.prevItem span {display:none; }
.prevItem:hover { background:#111; color:#fff;  transition: 1s; left: 0;}
	.prevItem:hover span {transition: 1s; display:inline-block;  }

/* #navigation-container/#header-container (base tier) removed 2026-08-11 -
   ported to real Tailwind in Header.tsx, including the mobile-breakpoint
   overrides further down this file - see that component's own comment.
   `.col-md-7`/`a#showMenu`/`a#hideMenu` sub-rules were already dead before
   this (no matching elements anywhere), removed alongside rather than left
   behind. */

/* #header-page-container removed 2026-08-11 - confirmed dead, no matching id anywhere in the codebase. */
#slider-container {margin:0; padding:0; position:relative; z-index:5000;  }
	 #sliderNav { position:absolute; z-index:0; margin-top:470px; z-index:8000;}
	 	#sliderNav a {color:#111; font-size:44px;}
		#sliderNav a:hover {color:#fff; font-size:44px;}
		
/* Footer chrome (border/menu/social/copyright) removed 2026-08-11 - ported
   to real Tailwind classes directly in Footer.tsx (see that file's own
   comment). Was previously scoped to a literal `id="footer-container"`
   duplicated across 3 DOM elements - a bug inherited from the original PHP
   template's own unclosed <div>, not something worth keeping a CSS hook
   for. */
		
#page-main-image-container { margin:0; padding:0; margin-top:100px;}
/* .container/h1/p span/i sub-rules removed 2026-08-11 - .container/p
	   span/i confirmed dead (no matching markup), h1 was fully redundant
	   (PageHero.tsx already applies identical font-black text-[54px]
	   directly). `a` stays - real conditional fallback color when a
	   breadcrumb link has no mod_boja-derived inline color, see
	   PageHero.tsx's own comment. */
	#page-main-image-container a {color:#111;   }
	
/* #page-subnav-container removed 2026-08-11 - SubNav.tsx already applies
   the identical border-t/border-b directly via Tailwind (this rule was
   fully redundant, not just unused); `.sublink`/`.eventMenu` sub-rules were
   already dead (SubNav.tsx uses its own Tailwind classes throughout, never
   these classnames). id dropped from SubNav.tsx alongside this. */
/* .content-container/.titleWrap removed 2026-08-11 - confirmed dead, zero matches anywhere (the *.cms-content-scoped* .container-fluid/.content-container in legacy-grid.css is a separate, unrelated rule - not this one). */
/* #page-image-container removed 2026-08-11 - ported to real Tailwind
   (bg-fixed etc.) at all 5 call sites (ClanakPage/ZbirkaPage/DogadanjePage/
   KontaktStranica/StaticnaStranica) - see those files' own comments. */

/* .fotorsama removed 2026-08-11 - a typo of .fotorama that never matched anything, confirmed by audit. */
/* #share-container/.ttop restored 2026-08-12 - the 2026-08-11 "confirmed dead"
   removal was wrong: "no matching markup in this codebase" meant this legacy
   feature (tpl/bottom.php, included on every non-homepage page) had simply never
   been PORTED at all, not that it was unused on the real site - it's real, visible
   chrome at the bottom of every detail/listing page (share-to-friend/Facebook/
   Twitter links + a back-to-top arrow), caught live via a real msu.hr screenshot.
   Now rendered by ShareBar.tsx, restoring the exact original values here. */
#share-container {padding-bottom:60px;}
	#share-container #share a {background:#fff; border:1px solid #111; font-size:12px;  display:inline-block; padding-right:10px; color:#111; margin:0px 5px; }
		#share-container #share a i {display:inline-block; padding:10px; font-size:16px; border-right:1px solid #111; color:#111}
	#share-container #share a:hover {background:#111; border:1px solid #111; font-size:12px;  display:inline-block; padding-right:10px; color:#fff; margin:0px 5px;}
		#share-container #share a:hover i {display:inline-block; padding:10px; font-size:16px; border-right:1px solid #ccc; color:#fff}
	#share-container a.ttop {padding:5px 8px; font-size:22px; border:1px solid #111; color:#111}
	#share-container a.ttop:hover {padding:5px 8px; font-size:22px; border:1px solid #111; color:#fff; background:#111}
/* #map-container/#map-event-container removed 2026-08-11 - real Google Maps embed never ported (KakoDoNas.tsx's own comment confirms), confirmed dead. */
/* #calendar/#calendar-days/.eventItem removed 2026-08-11 - real month-grid calendar widget never ported (KalendarDogadanja.tsx's own comment: ships a plain list instead), confirmed dead. */
/* .paralax/.desktopContent/.mobileContent removed 2026-08-11 - .paralax was
   already fully shadowed by inline height:600 on every real call site
   (inline always wins), see StaticnaStranica.tsx's own comment.
   .desktopContent/.mobileContent were never used by any real element at
   all - MediaBlok.tsx's own comment documents replacing this legacy
   wrapper pattern with a `desktopOnly` prop + Tailwind `hidden md:block`
   instead, confirmed via repo-wide grep (only comment references remain). */


/* the `screen and (-webkit-min-device-pixel-ratio:0)` block that used to
   live here only ever contained #calendar-days/.eventItem overrides -
   both already confirmed dead and removed above, so the whole block is
   gone too rather than left empty. */


@media (min-width: 768px) and (max-width: 1280px) {
	#slider-container {margin:0; padding:0; position:relative; z-index:5000;  }
	 #sliderNav { position:absolute; z-index:0; margin-top:400px; z-index:8000;}
	 	#sliderNav a {color:#111; font-size:44px;}
		#sliderNav a:hover {color:#fff; font-size:44px;}
}
	
@media (max-width:768px) {


	#slider-container {margin:0; padding:0; position:relative; z-index:10}
		#slider-container .row {position: absolute; left:20px; bottom:150px; width:100%; right:20px;}
			#slider-container .row h1 {font-size:34px; font-weight:900; letter-spacing:-3px;}
			
	#slider-container .row {position: absolute; left:50px; right:160px; top:200px; width:350px; font-size:11px;  }

	 #slider-container {margin:0; padding:0; position:relative; z-index:5000;  }
	 #sliderNav { position:absolute; z-index:0; margin-top:300px; z-index:8000;}
	 	#sliderNav a {color:#111; font-size:44px;}
		#sliderNav a:hover {color:#fff; font-size:44px;}
		
		#prevFrame {margin-left:-30px;}
		#nextFrame {margin-right:-30px;}

}