.collapsible{
  font-size: 16px !important;
  display: inline!important;
  width: auto!important;
  margin:0px!important;
  padding:0px!important;
  font-size: 100% !important;
  line-height: inherit !important;
  min-height: 20px !important;
  text-transform: none !important;
  vertical-align: bottom !important;
  font-weight:600;
}
.collapsible-section{
  display:inline !important;
}
.collapsible-section .content {
    display: none;
}
.collapsible + .content {
    display: none;
}

button.collapsible{
  position: relative;
  padding-right: 18px !important;
}

button.collapsible::after{
  content: "";
  display: inline-block;
  width: 14px;
  height: 14px;
  margin-left: 6px;
  vertical-align: middle;

  background-repeat: no-repeat;
  background-position: center;
  background-size: contain;

  /* the arrow picture and the link's two colours follow the settings (simple-collapse.php, awt_collapse_inline_css) */

  transform: rotate(0deg);
  transition: transform .2s ease;
}

/* rotate up when expanded */
button.collapsible.active::after{
  transform: rotate(180deg);
}

/* Read More right after the text, on the same line when it fits.
   collapser.js already makes the paragraph before the box inline, but a page-speed plugin may delay that script until the
   visitor's first mouse move or scroll, so on first view (and for a search engine) Read More started a new line and then
   jumped up. A <p> that wpautop puts around a hand-written <button class="collapsible"> (product short descriptions) was
   never handled. These two rules give the same result from the first paint. The <br> wpautop sometimes leaves right
   before the box is removed in PHP (ella_collapse_drop_br_before_box).
   Where: the pages that carry the body class awt-collapse-inline (the setting "Read More on the text's own line"). */
body.awt-collapse-inline p:has(+ .collapsible-section){display:inline}
body.awt-collapse-inline .collapsible-section > p:has(> button.collapsible){display:inline}
