/* PVT3 Sign & Send — Phase A styles. Scoped entirely to .p3-sign-* / .p3-mg-* /
   .p3-signsend-* so nothing here touches the plain viewer's existing rules. */

/* ── Header toolbar buttons (added to the existing viewer header) ───── */
/* SECTION A / A3 FIX (2026-08-24, Button Color Law): this rule used to force
   PDF Prepare & Send to the app's stock blue the moment it was active,
   overriding record-document-viewer.css's .p3-act-prepare.active (its own,
   correct, deeper-pink "active" tint) purely on specificity — a class+element+
   attribute+class selector (0,3,2) beats a two-class one (0,2,0) regardless of
   load order. Removed: PDF Prepare & Send is the ONE colored button, active or
   not, and .p3-act-prepare.active already carries its own active-state shade. */

/* ══ THE WHITE HAND LAW (CLAUDE.md 5.21, David's ruling, 2026-08-21) ══
   "The hand/pointer cursor is BANNED from Sign & Send... now and forever."
   Round 6 claimed this done; it wasn't — killing the floating move-arrow
   icon left every real BUTTON (header actions, rail tiles, toolbar, mini-
   toolbar, month-grid, fax modal) still showing cursor:pointer/grab,
   confirmed live by hovering every element type on the deployed site, not
   by reading the CSS. THE GUARD: `cursor` is an inherited CSS property —
   setting it ONCE here, on the sign layer's root, means any descendant
   that does NOT explicitly set its own cursor shows the plain arrow by
   default. Reintroducing the hand now requires a conscious, visible line
   of CSS (most of the rest of PVT3 uses cursor:pointer on buttons by
   habit — that habit is exactly how it kept creeping back in). The two
   deliberate exceptions, both set explicitly below: a mark = `move`
   (.p3-sign-stamp), actively-editing text/date = `text` (.editing). The
   fax modal and month-grid render as SIBLINGS of this modal, not
   descendants (documentHtml() appends them after `</section>`), so they
   get their own copy of the same guard further down this file. */
.p3-record-viewer-modal.p3-sign-expanded{cursor:default}
.p3-record-viewer-modal.p3-sign-expanded .p3-record-viewer-actions button{cursor:default}

/* ── WORKSPACE SIZE (David's ruling, 2026-08-20) — the plain viewer keeps
   its own modest width/height (record-document-viewer.css, untouched);
   Sign & Send mode expands the SAME modal to a near-full-screen working
   size. !important is deliberate, not lazy: record-document-viewer.css
   already carries an equal-specificity `:has(.email-open)` rule for a
   DIFFERENT case, and this session already found one real bug from two
   rules of matching specificity fighting silently (the resize-handle
   collision, ROUND 1) — this guarantees which one wins regardless of
   load order or a future rule added beside it. */
.p3-record-viewer-modal.p3-sign-expanded{width:min(97vw,1680px)!important;height:94vh!important;max-height:none!important}

/* ── THE PALETTE RAIL (ROUND 3) — a real <aside>, which the plain viewer's
   OWN CSS hides by default (`.p3-record-viewer-layout>aside{display:none}`,
   the old page-thumbnail rail law) since PVT2 has no rail, AND separately
   styles ANY <aside> child (`>aside{padding:16px 12px;overflow:auto;...}`,
   `>aside>div{display:grid;gap:12px}`) left over from that same removed
   rail — both would otherwise silently apply to this NEW, unrelated rail's
   own divs (the exact class of bug ROUND 1 already found once with the
   resize handle: a bare `.p3-sign-rail-item` at one class loses to
   `.p3-record-viewer-layout>aside>div` at a class+2 tags). Every rail rule
   below is deliberately over-qualified with the SAME
   `.p3-record-viewer-layout.sign-rail-open>aside.p3-sign-rail` prefix so it
   always outranks those old rules, not by relying on source order. */
.p3-record-viewer-layout.sign-rail-open{grid-template-columns:104px minmax(0,1fr)}
.p3-record-viewer-layout.sign-rail-open.email-open{grid-template-columns:104px minmax(0,1fr) minmax(420px,540px)}
.p3-record-viewer-layout.sign-rail-open>aside.p3-sign-rail{display:flex;flex-direction:column;gap:10px;padding:14px 8px;background:#f8fafc;border-right:1px solid #dbe3ee;overflow-y:auto;overflow-x:hidden;align-items:stretch}
.p3-record-viewer-layout.sign-rail-open>aside.p3-sign-rail>.p3-sign-rail-item{display:flex;flex-direction:column;align-items:center;gap:4px;padding:8px 4px;border-radius:10px;border:1.5px solid transparent;background:#fff;box-shadow:0 1px 4px rgba(15,23,42,.08);cursor:default;user-select:none}
.p3-record-viewer-layout.sign-rail-open>aside.p3-sign-rail>.p3-sign-rail-item.active{border-color:#2f72e5;background:#eef4ff}
.p3-record-viewer-layout.sign-rail-open>aside.p3-sign-rail>.p3-sign-rail-item svg{width:30px;height:30px}
.p3-record-viewer-layout.sign-rail-open>aside.p3-sign-rail>.p3-sign-rail-item img{width:100%;max-width:82px;height:auto;pointer-events:none}
.p3-sign-rail-date{font-size:13px;font-weight:750;color:#000;white-space:nowrap}
.p3-sign-rail-text{font-size:14px;font-weight:750;color:#000;font-family:'Segoe UI',Arial,sans-serif}
.p3-sign-rail-label{font-size:9px;color:#8491a6;text-transform:uppercase;letter-spacing:.04em}

/* ── Secondary toolbar row, shown only while Sign & Send mode is open ── */
.p3-sign-toolbar{display:flex;align-items:center;gap:8px;flex-wrap:wrap;padding:7px 16px;background:#eef4ff;border-bottom:1px solid #cfe0fb;flex:none}
.p3-sign-toolbar .p3-sign-tool{border:1px solid #b9cdf2;background:#fff;color:#25406f;border-radius:8px;padding:7px 12px;font-weight:750;cursor:default}
.p3-sign-toolbar .p3-sign-tool.active{background:#2f72e5;color:#fff;border-color:#2f72e5}
.p3-sign-toolbar-spacer{flex:1}
.p3-sign-toolbar-hint{font-size:12px;color:#4a5b7c}
/* SECTION A / A3 FIX (2026-08-24, Button Color Law): was solid blue via a
   redundant "primary" class (styles.css's button.primary, 0,1,1, was outranking
   this rule's own 0,1,0 background regardless of load order) — Save & File is
   neutral like every other action here except PDF Prepare & Send. */
.p3-sign-save{border:1px solid #dbe3ee;background:#f8fafc;color:#3e4d67;border-radius:8px;padding:8px 16px;font-weight:750;cursor:default}
.p3-sign-save:disabled{opacity:.6;cursor:not-allowed}
/* #462 — Save & File's in-place patient ask (the tabletop finder's shape) */
.p3-sign-file-ask{display:flex;flex-wrap:wrap;align-items:center;gap:8px;padding:9px 16px;background:#fff8e6;border-bottom:1px solid #f1d58a;flex:none;cursor:default}
.p3-sign-file-ask strong{font-size:13px;color:#5b4410;margin-right:4px}
.p3-sign-file-ask input{flex:1 1 240px;min-width:200px;border:1px solid #d8c07c;border-radius:8px;padding:7px 10px;font:inherit}
.p3-sign-file-ask .pe-finder-hits{flex-basis:100%;display:flex;flex-wrap:wrap;gap:6px}
.p3-sign-file-ask .pe-finder-hits button{border:1px solid #d9e2ef;background:#fff;border-radius:8px;padding:6px 10px;cursor:default;font:inherit}
.p3-sign-file-ask .pe-finder-hits small{color:#6b7689}
.p3-sign-file-ask .ghost{cursor:default}
:root[data-theme="dark"] .p3-sign-file-ask{background:#2e2818;border-color:#5a4a20}
:root[data-theme="dark"] .p3-sign-file-ask strong{color:#f2d68a}
:root[data-theme="dark"] .p3-sign-file-ask input,:root[data-theme="dark"] .p3-sign-file-ask .pe-finder-hits button{background:#1c2230;color:#e6ebf3;border-color:#3b4557}
/* ROUND 5 (David): a VISIBLE Undo button — THE BECKER RULE (CLAUDE.md 5.20),
   Ctrl+Z is the shortcut layered on top, never the only way in. */
.p3-sign-undo{display:inline-flex;align-items:center;gap:6px;border:1px solid #d7e0eb;background:#fff;color:#25406f;border-radius:8px;padding:5px 12px;font-weight:750;font-size:12.5px;cursor:default}
.p3-sign-undo:disabled{opacity:.4;cursor:not-allowed}

/* ── The stamp overlay — sits directly on top of the page canvas, exactly
   matching its box because the article's only in-flow child is the canvas
   (the page-number caption is position:absolute and does not affect it). ── */
.p3-sign-overlay{position:absolute;inset:0;z-index:2}
/* ROUND 6 (David): the floating grey move-arrow (Round 5) still read as
   "the hand" — a floating icon standing in for a cursor. Killed outright;
   the mark itself now carries the OS-level four-way MOVE cursor directly
   (no icon element at all), everywhere else in Sign & Send stays the
   normal arrow. The body still drags on press either way — only the
   CURSOR changed. */
.p3-sign-stamp{position:absolute;cursor:move;touch-action:none;user-select:none}
/* ROUND 6 — "the instant a drag starts, ALL chrome vanishes... just the
   mark gliding under the cursor; chrome returns only after release."
   `.dragging` is toggled by startBodyDrag() only after real pointer
   movement clears a small threshold (so a plain click-to-select never
   flickers), and !important guarantees it beats `.selected`'s outline
   regardless of rule order — same reasoning as the workspace-size rule
   above. */
.p3-sign-stamp.dragging{outline:none!important}
/* SELECTION STYLE (David's ROUND 5 ruling): "a THIN outline hugging the
   mark — never filled or shaded. Ink 100% visible while selected." Offset
   trimmed from Round 4's 2px to 1px so it hugs rather than floats around
   the mark; the old selected-text background tint is gone entirely — no
   fill, ever, selected or not. Hover (below) gives a fainter, separate hint
   before a click commits to selecting. */
.p3-sign-stamp.selected{outline:1px solid rgba(47,114,229,.6);outline-offset:1px}
.p3-sign-stamp:hover:not(.selected){outline:1px solid rgba(47,114,229,.22);outline-offset:1px}
.p3-sign-stamp.p3-sign-check,.p3-sign-stamp.p3-sign-x,.p3-sign-stamp.p3-sign-signature{min-width:6px;min-height:6px}
.p3-sign-stamp.p3-sign-check svg,.p3-sign-stamp.p3-sign-x svg{width:100%;height:100%;display:block}
.p3-sign-stamp.p3-sign-signature img{width:100%;height:100%;display:block;pointer-events:none}
.p3-sign-stamp.p3-sign-text,.p3-sign-stamp.p3-sign-date{min-width:24px;min-height:1.3em}
/* BLACK, always — David's rework 2026-08-20: "same ink look as the
   signature." */
.p3-sign-text{outline:none;white-space:pre-wrap;word-break:break-word;color:#000;font-family:'Segoe UI',Arial,sans-serif;line-height:1.25;min-width:14px}
/* Not-editing = drags like every other stamp, grabbed anywhere including
   the text itself (same move cursor as every other mark — ROUND 6).
   Editing = a real text cursor, like typing anywhere. */
.p3-sign-stamp.p3-sign-text.editing,.p3-sign-stamp.p3-sign-date.editing{cursor:text}
.p3-sign-stamp.p3-sign-text.editing .p3-sign-text,.p3-sign-stamp.p3-sign-date.editing .p3-sign-text{cursor:text}
/* "A clean text box appears at that spot" — the dashed box shows ONLY while
   actively typing; at rest a placed mark reads like ink on the page, same
   as Check/X/Signature, with only the shared .selected outline (below) as
   its resting-state affordance. */
.p3-sign-stamp.editing .p3-sign-text{outline:1px dashed #7c93b8;outline-offset:3px;background:rgba(255,255,255,.7);padding:1px 3px}
/* Hidden until hovered or selected — David's rework 2026-08-20: the icon
   was permanently rendered, crowding the date at rest ("glued to it").
   ROUND 5: 30% bigger (22px/12px -> 29px/16px) per David's order. */
.p3-sign-date-open{position:absolute;right:-34px;top:0;border:1px solid #b9cdf2;background:#fff;border-radius:6px;width:29px;height:29px;font-size:16px;line-height:1;cursor:default;padding:0;opacity:0;pointer-events:none;transition:opacity .12s}
.p3-sign-stamp.p3-sign-date:hover .p3-sign-date-open,.p3-sign-stamp.p3-sign-date.selected .p3-sign-date-open,.p3-sign-stamp.p3-sign-date.editing .p3-sign-date-open{opacity:1;pointer-events:auto}
/* ROUND 6 (David): "SELECTED-AT-REST — remove ALL badges from around the
   mark; a selected mark shows ONLY the thin 1px outline." The corner resize
   handle, the delete badge, the "stamp again" badge, and the floating
   move-arrow (all previously children of the mark's own DOM node) are gone
   — replaced by ONE fixed mini-toolbar (below), always in the same place
   near the top of the page area, never hugging the mark. Resize is now
   keyboard +/- (RESIZE_STEP_RATIO, unchanged since Round 5) or the
   toolbar's own -/+ buttons — both call the identical resizeSelectedBy(),
   satisfying THE BECKER RULE (CLAUDE.md 5.20): a visible, clickable
   control, not a keyboard-only capability. */
/* ROUND 6 REGRESSION FIX (David's hand check, 2026-08-21): the toolbar's
   container had `pointer-events:auto` across its WHOLE rectangle while
   visible — not just its buttons — and that rectangle sits INSIDE real page
   content (main starts ~10px above it). Confirmed live: a tap aimed at a
   spot the toolbar happened to occupy hit the toolbar (`elementFromPoint`
   returned it) and silently placed nothing — the mechanism behind all
   three reported symptoms (Stamp Again taps swallowed mid-column, a
   "dead zone" re-grabbing a mark under it, the "lag" of a press that did
   nothing until retried elsewhere). The container itself now NEVER
   captures pointer events — only its buttons do — so gaps/padding/
   background are pass-through to whatever is underneath, exactly like the
   page's own overlay. */
.p3-sign-minitb{position:fixed;z-index:12000;display:flex;align-items:center;gap:6px;background:#17233b;color:#fff;border-radius:10px;padding:6px 8px;box-shadow:0 8px 24px rgba(15,23,42,.4);opacity:0;pointer-events:none;transform:translate(-50%,0);transition:opacity .12s;font-size:12px}
.p3-sign-minitb.visible{opacity:1}
.p3-sign-minitb button{border:none;background:rgba(255,255,255,.14);color:#fff;border-radius:7px;padding:6px 10px;font-weight:700;font-size:11px;cursor:default;display:flex;align-items:center;gap:4px;white-space:nowrap;pointer-events:none}
.p3-sign-minitb.visible button{pointer-events:auto}
.p3-sign-minitb button:hover{background:rgba(255,255,255,.26)}
.p3-sign-minitb-size{display:flex;align-items:center;gap:2px;background:rgba(255,255,255,.1);border-radius:7px;padding:2px}
.p3-sign-minitb-size button{padding:4px 9px;font-size:14px;font-weight:800;line-height:1}
.p3-sign-minitb-size b{min-width:40px;text-align:center;font-weight:750;font-size:11px}
.p3-sign-minitb [data-p3-mtb-delete]{background:rgba(192,49,26,.85)}
.p3-sign-minitb [data-p3-mtb-delete]:hover{background:#c0311a}

/* ── The month-grid date picker — ROUND 4 (David): "so tiny it's unusable...
   must open at the app's NORMAL STANDARD SIZE, never a miniature." No
   reusable "create form" date-grid component exists anywhere in PVT3 to
   literally call instead (checked: the calendar's monthGrid() is the whole
   month VIEW, tightly coupled to live calendar state, and every real
   "create form" date field in the app is a plain native <input type=date>)
   — so this is the same custom popup, substantially enlarged to read as a
   real, comfortable picker rather than a miniature. ─────────────────── */
/* THE WHITE HAND LAW (CLAUDE.md 5.21) — the month-grid renders as a SIBLING
   of the sign-expanded modal (documentHtml() appends it after the modal's
   own closing tag), so it needs its own copy of the inheritance guard. */
.p3-month-grid{position:fixed;z-index:12600;width:340px;background:#fff;border:1px solid #d7e0eb;border-radius:14px;box-shadow:0 16px 44px rgba(15,23,42,.28);padding:18px;cursor:default}
.p3-month-grid header{display:flex;align-items:center;justify-content:space-between;margin-bottom:12px}
.p3-month-grid header button{border:none;background:#eef4ff;color:#25406f;border-radius:8px;width:38px;height:38px;font-size:20px;cursor:default}
.p3-month-grid header strong{font-size:18px;color:#17233b}
.p3-mg-weekdays,.p3-mg-days{display:grid;grid-template-columns:repeat(7,1fr);gap:4px;text-align:center}
.p3-mg-weekdays span{font-size:13px;font-weight:700;color:#8491a6;padding:6px 0}
.p3-mg-days button{border:none;background:transparent;border-radius:8px;padding:12px 0;font-size:16px;color:#25406f;cursor:default}
.p3-mg-days button:hover{background:#eef4ff}
.p3-mg-days button.p3-mg-selected{background:#2f72e5;color:#fff;font-weight:750}
.p3-month-grid footer{margin-top:12px;text-align:right}
.p3-month-grid footer button{border:none;background:transparent;color:#4a5b7c;font-size:14px;cursor:default;padding:8px 10px}

/* ── The left-nav standalone door ─────────────────────────────────────── */
/* #418 — the standalone page's stage: the whole page is the drop target; the stage is where the eye lands.
   No hand cursor anywhere here (law 5.21) — the drop zone is a surface, the buttons are real buttons. */
.p3-signsend-stage{display:grid;place-items:center;gap:8px;border:2px dashed #b9cdf2;border-radius:16px;padding:64px 24px;text-align:center;background:#f8fafc;min-height:52vh;cursor:default;transition:background .15s,border-color .15s}
.p3-signsend-stage.dragging{background:#eef4ff;border-color:#2f72e5;box-shadow:inset 0 0 0 3px rgba(47,114,229,.25)}
.p3-signsend-stage-art{font-size:44px;line-height:1;color:#b9cdf2}
.p3-signsend-stage strong{font-size:18px;color:#17233b}
.p3-signsend-stage>span{color:#718096;font-size:13px;max-width:520px}
.p3-signsend-stage-actions{display:flex;gap:10px;margin-top:14px}
.p3-signsend-stage .p3-combine-add-btn{cursor:default}
.p3-signsend-add input{display:none}
.p3-signsend-error{background:#fff1f2;color:#9f5261;border-radius:8px;padding:8px 10px;font-size:13px;margin-bottom:10px}
.p3-signsend-standalone-active{display:grid;gap:10px;justify-items:start}

/* ── #469 (David, 2026-09-17) — placed marks stay editable ─────────────────
   PART A. "The active mark is obvious on screen — David must be able to see
   WHICH one he has hold of." ROUND 6's hairline outline was right for a mark
   sitting alone; it says nothing when three X marks are stacked in a corner.
   A selected mark now carries a real outline plus a soft halo, and ONE corner
   grip. Everything vanishes again the moment the drag starts (.dragging),
   which keeps ROUND 6's "dragging = ink only" rule intact. */
.p3-sign-stamp.selected{outline:2px solid rgba(47,114,229,.9);outline-offset:2px;box-shadow:0 0 0 4px rgba(47,114,229,.14)}
.p3-sign-stamp.dragging{outline:none!important;box-shadow:none!important}
.p3-sign-stamp.dragging .p3-sign-resize{display:none}
.p3-sign-resize{position:absolute;right:-7px;bottom:-7px;width:13px;height:13px;border-radius:50%;background:#2f72e5;border:2px solid #fff;box-shadow:0 1px 4px rgba(15,23,42,.45);cursor:nwse-resize;touch-action:none;z-index:3}
.p3-sign-minitb-what{display:flex;flex-direction:column;line-height:1.1;padding:0 8px 0 2px;font-weight:750;font-size:11px;white-space:nowrap}
.p3-sign-minitb-what small{font-weight:500;font-size:9.5px;opacity:.72}
/* PART B — the three answers at Save. */
.p3-sign-save-choice{max-width:420px}
.p3-sign-save-choice-sub{margin:0;font-size:12px;color:#64748b}
.p3-sign-choice{display:flex;flex-direction:column;gap:2px;text-align:left;padding:10px 12px;border-radius:10px;border:1.5px solid #cbd5e1;background:#fff;cursor:default}
.p3-sign-choice b{font-size:13px;color:#17233b}
.p3-sign-choice small,.p3-sign-choice span{font-size:11.5px;color:#64748b;font-weight:500}
.p3-sign-choice:hover{border-color:#2f72e5;background:#f6f9ff}
.p3-sign-choice-name input{margin-top:6px;padding:7px 9px;border-radius:7px;border:1px solid #cbd5e1;font-size:13px;width:100%}
.p3-sign-save-choice-row{display:flex;gap:8px;justify-content:flex-end;align-items:center}
/* PART C — the review bar over the finished document. */
.p3-sign-review-what{font-size:12.5px;color:#334155}
.p3-sign-review-what b{color:#17233b}
:root[data-theme="dark"] .p3-sign-save-choice-sub,:root[data-theme="dark"] .p3-sign-choice small,:root[data-theme="dark"] .p3-sign-choice span{color:#9fb0c8}
:root[data-theme="dark"] .p3-sign-choice{background:#1c2230;border-color:#3b4557}
:root[data-theme="dark"] .p3-sign-choice b{color:#e6ebf3}
:root[data-theme="dark"] .p3-sign-choice:hover{background:#243046;border-color:#5b8cf0}
:root[data-theme="dark"] .p3-sign-choice-name input{background:#151b27;color:#e6ebf3;border-color:#3b4557}
:root[data-theme="dark"] .p3-sign-review-what{color:#c7d2e2}
:root[data-theme="dark"] .p3-sign-review-what b{color:#f1f5f9}
:root[data-theme="dark"] .p3-sign-resize{border-color:#0f1520}

/* ── #470 PART C (David) — "the dashed drop area and the empty canvas below
   it take the whole screen and look ridiculous." It was min-height:52vh with
   64px of padding, stretched the full width of the page. A normal drop target
   now: capped width, centred, sized to its own content. Dropping anywhere on
   the page still works — that listener is on `document`, untouched. */
.p3-signsend-stage{padding:26px 24px 22px!important;min-height:0!important;max-width:720px;margin:4px auto 0}
.p3-signsend-stage-art{font-size:30px!important}
.p3-signsend-stage strong{font-size:16px!important}
.p3-signsend-stage-actions{margin-top:10px!important}
.p3-signsend-stage .p3-combine-add-btn{flex-direction:row;align-items:center;gap:7px}
.p3-signsend-stage .p3-combine-add-btn small{display:block;font-weight:500;font-size:10.5px;color:#64748b}
:root[data-theme="dark"] .p3-signsend-stage .p3-combine-add-btn small{color:#94a3b8}
/* #470 PART B — LOOKED AT, not just asserted (law 5.15): the first build put the subtitle BESIDE the label, so
   "From Chart" wrapped to two lines while "Add Files" stayed on one and the pair read as broken. Both doors are now
   built the same way — a column inside the button — and both are given the same width so they sit as a matched pair. */
.p3-signsend-stage-actions{align-items:stretch}
.p3-signsend-stage .p3-combine-add-btn{flex:0 0 240px;justify-content:flex-start;text-align:left;padding:9px 12px}
.p3-signsend-stage .p3-combine-add-btn>span{display:flex;flex-direction:column;align-items:flex-start;line-height:1.2;white-space:nowrap}
.p3-signsend-stage .p3-combine-add-btn>span small{font-weight:500;font-size:10.5px;color:#64748b;white-space:nowrap}
:root[data-theme="dark"] .p3-signsend-stage .p3-combine-add-btn>span small{color:#94a3b8}

/* #469 PART B — LOOKED AT (law 5.15), and the first build was wrong on screen: the save chooser reuses the
   .p3-sign-file-ask shell, whose `input{flex:1 1 240px}` is a WIDTH basis in that row-flex panel and became a
   240px-tall HEIGHT inside my column, so "Type a filename" rendered as an enormous empty box. The chooser is an
   explicit column with an explicit field height; nothing is left to inherit. (Law 5.26 — a mechanism that works is
   not a finished UI.) */
.p3-sign-save-choice{display:flex;flex-direction:column;align-items:stretch;gap:9px;max-width:440px}
.p3-sign-save-choice .p3-sign-choice{flex:0 0 auto}
.p3-sign-save-choice .p3-sign-choice-name input{flex:0 0 auto;height:34px;min-width:0;width:100%;box-sizing:border-box;margin-top:6px}
.p3-sign-save-choice .p3-sign-save-choice-row{flex:0 0 auto}
.p3-sign-save-choice .p3-sign-save-choice-row button{cursor:default}
