/*
 * Two things: the honeypot, and the administrator notice for markup that
 * does not match its definition. Nothing that styles your form.
 *
 * The honeypot first. A separate stylesheet rather than an inline style, because a Content
 * Security Policy blocks inline styles - and a honeypot that becomes
 * visible inverts: real visitors fill it in, get flagged as spam, and
 * their messages arrive without a notification.
 *
 * Off-screen positioning rather than display:none, the hidden attribute
 * or type="hidden". Two reasons:
 *
 *   Bots. Parsers recognise "hidden" and "none" and skip those fields,
 *   so the trap catches nothing. An off-screen field is, to anything but
 *   a full layout engine, indistinguishable from a real one.
 *
 *   Themes. Author CSS always beats the UA stylesheet, so a plain
 *   input { display: block } disables the hidden attribute entirely.
 *   Off-screen positioning does not touch display, so that same rule
 *   leaves it alone.
 *
 * !important because theme styles on form fields are common and this one
 * must not lose.
 */
.kiss-form-hp {
	position: absolute !important;
	left: -9999px !important;
	top: auto !important;
	width: 1px !important;
	height: 1px !important;
	overflow: hidden !important;
}

/*
 * The administrator notice shown when markup and definition disagree.
 * Enough to stand out from the page, nothing more - the page is the
 * theme's, not ours.
 */
.kiss-form-notice {
	margin: 1em 0;
	padding: 1em;
	border-left: 4px solid #996800;
	background: #fcf9e8;
	color: #1d2327;
	font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;
	font-size: 14px;
	line-height: 1.5;
}

.kiss-form-notice p {
	margin: 0 0 .5em;
}

.kiss-form-notice p:last-child {
	margin-bottom: 0;
}

.kiss-form-notice ul {
	margin: 0 0 .5em 1.5em;
	list-style: disc;
}