@media screen {
body.modal-open {
    overflow: auto;
}

/* Clears the fixed bar: MEASURED in a static harness (real header markup + the real stylesheet chain,
   Chrome, rendered at 1646px viewport width) at 58px content + a 3px border-bottom = 61px - matching
   --idt-chrome-h and the border-bottom declared on .idt-appbar in idt-ui.css, so the number holds at
   any width; the bar's own min-height doesn't shrink on mobile, only the nav below it collapses. The
   harness measured the rendered rect at 60.857px because the display's 175% OS scaling rounds a 3px
   CSS border to a whole device pixel (5px at that scale = 2.857px back in CSS px) - a sub-pixel
   rendering artifact, not a real 61px vs 60.857px difference, so the comment below uses the exact 61.
   The 18px above that is --idt-gap, the app's own block-separation rhythm (idt-ui.css), used here so
   the gap under the bar reads as deliberate rather than a leftover number. 61 + 18 = 79.

   The bottom value is now the same 79px, arrived at from the other end: the footer band is 58px plus
   its own 3px top rule, and `body { margin-bottom: 61px }` (idt-ui.css, beside the band it reserves for)
   already holds page content clear of it, so all this padding still owes the page is the --idt-gap
   between the last block and the band - 18 + 61 = 79 again. It was 90px, which reserved space for a
   footer that was never 90px tall and left the page bottom-heavy by a number nothing explained. */
body>.container {
	padding: 79px 0 18px;
}

.row{
	margin-right: 0px;
	margin-left: 0px;
}

.modal-header{
	padding: 6px 6px 6px 12px;
}

button.disabled{
	opacity: 0.65;
	cursor: not-allowed;
}
/* button.disabled:hover went on 2026-10-07. It gave a disabled button display:block, 10px padding,
   white text on #e5e5e5 and a 20px bottom margin - at (0,2,1) it beat the kit button outright, so the
   order and fill dialogs' Save, which carries .disabled while its request is out, turned into a
   full-width grey bar under the cursor. The rule above, the dimmed look and the no-entry cursor, stays. */

/* Rules that lived inside the old header block, kept when the header modernisation deleted the rest of
   it (the header itself now lives in idt-ui.css's .idt-appbar-* rules). Two are left, and neither
   styles the navigation bar itself:
     - .nav-tabs and .nav-tabs>li>a style the in-page tab strips - Account Management's page tabs and
       the Members and Organisations edit dialogs' tabs.
     - Two more lived here: #confirmSave .btn-default, deleted on 2026-09-03 with the five private
       copies of the confirm dialog it served, and the sign-in links' Bootstrap blue, 2026-10-07. */
.nav-tabs{
	border-bottom: none;
}

.nav-tabs>li>a{
	font-size: 15px;
}

/* --- The sign-up form, and the organisation shuttle tree (.organisations, on sign-up, Account
   Management, Members and Organisations) --- */

#sign-up-form label{
	text-align: left;
}

.organisations {
	text-align: left;
}

/* #termsContainer label { margin-left: 5px } was deleted on 2026-09-03. It was the last core.css rule
   reaching /signup's rebuilt form, and it beat entry.css on specificity without needing load order to
   help it: an id plus a type selector is (1,0,1) against .entry-check's (0,1,0), which is exactly the
   trap CLAUDE.md names - an id selector in core.css out-specifies any number of kit classes. The
   symptom was quiet: the Accept-terms checkbox row sat 5px right of the left edge of every other field
   on the page, so the one row that has to read as part of the same column was the one visibly out of
   line. #termsContainer itself stays in the markup - signup.html's own comment says why, it is the
   block the validator's terms message belongs to - so getting out of the rule's way by renaming was
   not available, and nothing else wanted the rule. */

/* ---- End sign-up form and shuttle tree ------------*/

/* ---------- Grids, form error text, tab panes, and the Dealing fill dialog ----------------------- */

.ui-th-column,.ui-jqgrid .ui-jqgrid-htable th.ui-th-column
{overflow:hidden;white-space:nowrap;text-align:center;vertical-align: middle !important;}

.ui-jqgrid .ui-jqgrid-hbox,
.ui-jqgrid .ui-jqgrid-btable tbody tr.jqgrow td{
	font-size: 12px;
}

.error{
	color: red;
}

.tab-content>.active{
	border-top: 1px solid silver
}

.grid-panel{
	margin-top:0px;
}

/* `.jqgrow button` - transparent, borderless, no outline for every button in a grid row - went on
   2026-10-07; it outranked the kit's button weights in every table. RetiredCoreCssRulesTest keeps it
   out of every stylesheet, and idt-ui.css says what it cost where the --xs rules fighting it were. */

/* #addNewOrder was absolutely positioned into the corner of a jqGrid title bar, because that is where
   dashboard.js used to inject it. "New order" is a real button in its card header now (styled by
   .idt-btn in idt-ui.css) - on /trading since the 2026-08-12 split, not the Dashboard any more - and
   nothing else in the app used these rules. */

.control-label{
	text-align: left;
}

@media (min-width: 768px){
	.modal-dialog {
		width: 730px;
	}
}

#selected-offer{
	float: left;
	width: 47%;
	
	
	 
}

#fill-body{
	padding: 29px;
}

#fill-order-inputs{
	float:right;
	width: 50%;
	border-left: 1px solid #e5e5e5;
	padding-left: 10px;
}
#form-fill-order{
/* 	height: 245px; */
	height: auto;
	display:block;
	overflow-y:auto;
	overflow-x:hidden;
	width:100%;
}
#form-fill-order .form-group .control-label{
	text-align: left;
	padding-top: 8px;
}

#fill_order_type{
	font-weight: normal;
}

#selected-offer .form-group{
	margin-right: -15px;
    margin-left: -15px;
    margin-bottom: 15px;
}
#selected-offer .form-group>.col-sm-5:nth-child(odd){
	font-weight: bold;
	padding-right: 9px;

	    padding-top: 7px;
    margin-bottom: 0;
    text-align: left;
}
#selected-offer .form-group>.col-sm-6{
	font-weight: normal;
	text-align: left;
	width: 52%;
	display: block;
    
    height: 34px;
    padding: 6px 12px;
    font-size: 14px;
    line-height: 1.42857143;
    color: #555;

}

/* ---------- End grids and the fill dialog -------------------- */

/* ------ Trade History ------ */

#payments{
	width: 100%;
}

/* ------- End Trade History ----- */

/* ----- Account Management ---- */

#organisations-form{
	width: 100%;
}

#j2_1{
	display: none;
}

#member-form, #reset-form{
	width: 100%;
}

/* --- End Account Management ---- */

/* ------ Members ---- */

/* .members-filter, #member-reports and #export-button-members styled the old three-box filter panel and
   the Reports panel this rebuild removed outright (see membermanagement.html's own comment on what used
   to sit above the masthead). Confirmed by grep across views/ and resources/js/ that none of the three
   names survive anywhere in the application - not merely unused on this page, matching nothing at all -
   so, unlike the #status .form-group rule below, these are deleted rather than kept. */

/* Five rules keyed to the Edit member dialog's own id used to sit in this block (a silver fieldset
   border, the two tab panes forced to min-height:419px, and three more keyed through
   #authoritiesMemberTree, which that dialog no longer has at all). They are gone, not overridden: the
   Edit member dialog's id names nothing else in this codebase but membermanagement.html and
   membermanagement.js, and that dialog is kit-native now, so nothing left consumed them. This is a
   DIFFERENT call from the bare #authoritiesMemberTree rules that used to sit directly below, which were
   kept at the time because they still served Organisation Management's Edit organisation dialog - a different
   id, belonging to a dialog that was still the legacy markup. Same-looking id-scoped rules, opposite
   fates, because only one of the two dialogs had moved.

   Both dialogs have moved now. Organisation Management went onto the kit on 2026-09-03 and its shuttle is
   .idt-shuttle, so #authoritiesMemberTree, .panel-auth, .tree-panel, .button-auth, #tree-member-buttons
   and #container-buttons match nothing anywhere in the application and have gone the same way. The
   opposite fates were temporary, which is the thing worth knowing: an id-scoped rule kept alive for one
   remaining consumer is a rule with a scheduled deletion date, and this is what it looks like when the
   date arrives. (KitPromotionTest pins the id itself gone from this file, which is why this comment
   spells it differently than a plain grep would expect - see that test for why.) */
/* #filterButtonsMembers styled the old Filter button, which is also gone outright (grep confirms the id
   matches nothing anywhere), so it is deleted alongside the three rules above rather than left behind.

   Two #status .form-group rules used to be argued for HERE and kept, on the grounds that #status was not
   a name this page owned alone: organisationmanagement.html and usermanagement.html each declared their own
   #status pane wrapping .form-group rows, core.css loads on both, and an id selector matches whichever
   page renders one - it has no idea which page meant to keep using it. That was the right call for as
   long as it was true. On 2026-09-03 both of those pages moved onto the kit, renaming their panes
   #auth-pane-info and #user-info precisely to get out of these rules' way, and #limits went with them.
   The only #status left in the application is this page's own tab pane, which has carried no .form-group
   since its rebuild - so both rules now match nothing at all and both are deleted, by the same test that
   deleted the four above. The pair is worth recording rather than just removing: the reason the rules
   survived their own page's rebuild was a second consumer, and the reason they are gone is that the
   second consumer left. */
/* ------ End Members ----*/

/* ------ Organisations --- --*/

/* A rule painting every disabled text box #dddddd stood here until 2026-10-07. It made a box the reader
   may not edit the darkest thing in its dialog; idt-ui.css's .idt-input:disabled is the quiet version. */


/* ----- End Organisations --- */

/* ----- Trades and Fees --- */

.full-part{
	width:100%;
	float:left;
}

#trades{
	margin-top: 10px;
}

/* ----- End Trades and Fees ---*/

/* ----- User management and Settings ----
   Nothing left. The Users page's #addNewUser rule (it hid the New user button) and the #userInfo /
   #settingInfo fieldset boxes in the two edit dialogs went on 2026-10-07; RetiredCoreCssRulesTest
   keeps them out of every stylesheet. */
/*----- JQGrid ----------- */

.ui-jqgrid .ui-jqgrid-bdiv {
  position: relative; 
  margin: 0em; 
  padding:0; 
  overflow: auto; 
  overflow-x:hidden; 
  overflow-y:auto; 
  text-align:left;
}

 .ui-jqgrid .ui-jqgrid-hbox, .ui-jqgrid .ui-jqgrid-btable tbody tr.jqgrow td{
        word-wrap: break-word; /* IE 5.5+ and CSS3 */
        white-space: pre-wrap; /* CSS3 */
        white-space: -moz-pre-wrap; /* Mozilla, since 1999 */
        white-space: -pre-wrap; /* Opera 4-6 */
        white-space: -o-pre-wrap; /* Opera 7 */
        overflow: hidden;
        height: auto;
        vertical-align: middle;
        padding-top: 3px;
        padding-bottom: 3px
    }

th.ui-th-column div {
	word-wrap: break-word; /* IE 5.5+ and CSS3 */
	white-space: pre-wrap; /* CSS3 */
	white-space: -moz-pre-wrap; /* Mozilla, since 1999 */
	white-space: -pre-wrap; /* Opera 4-6 */
	white-space: -o-pre-wrap; /* Opera 7 */
	overflow: hidden;
	height: auto;
	vertical-align: middle;

}

.ui-jqgrid .ui-grid-ico-sort{
	position: initial;
	right: initial;
}

.ui-jqgrid .ui-jqgrid-htable .ui-th-div{
	margin-top:0px;
}
.table>thead>tr>th, .table>tbody>tr>td {
	padding: 2px;
}

/* ---- End JQGrid ---- */

/* The footer moved to idt-ui.css, under .idt-footer, the same way the header moved to .idt-appbar: it is
   application chrome, and this file is the one page modernisation is steadily deleting. What stood here
   was a solid #991B1E band with #f7dfd9 links and two `float: left; width: 49.5%` columns that never
   responded to anything. Nothing loads jumbotron-narrow.css, which also carries `.footer` rules, so
   there is no competitor left for the class name. */

/* Sticky footer styles
-------------------------------------------------- */
/* Still here, and still load-bearing: .idt-footer is position:absolute, and these two declarations are
   what make bottom:0 mean the bottom of the PAGE rather than the bottom of the viewport. The band's own
   clearance - what `margin-bottom: 60px` used to do here, 2px short of the band it was reserving for and
   with nothing recording which number it tracked - now sits in idt-ui.css beside the height it has to
   match. */
html {
	position: relative;
	min-height: 100%;
}

body {
	background-color: #ffffff;
}

#banner{
	width:100%;
	height: 69px;
	background-color: #991B1E;
}
}

/* The 2013 bordered risk-metric table's last rule, a.basic, its bold first-column headings and the red
   "changed by this upload" text colour went on 2026-10-07 with 70 more rules here that no page, dialog
   or script still produced markup for - checked by loading every page with each dialog and tab open,
   then by searching every script for the names. upload.js marks a changed cell with the kit's
   .rm-changed instead. p.error went the same day, being .error again with a type selector in front. */