Closed NumerousHats closed 3 years ago
After poking around on some scalar books at other institutions, I see that paragraphs seem to be defined by being enclosed in <div class="paragraph_wrapper">
elements. So, what do I need to do in the WYSIWYG in order to tell scalar that a section of text needs to be enclosed in a new "paragraph_wrapper"?
Okay. I guess I figured it out. Pressing "Enter" twice miraculously causes a new "paragraph_wrapper" <div>
to appear in the final rendered page as it appears in the browser, while also leaving behind a stray <br>
at the end of the preceding <div>
.
To me, that seems like a truly -- errr -- interesting design decision, but I guess there must have been some good reason for it. I guess it is what it is...
This is really more of a question rather than an issue.
When creating brand new page content in the WYSIWYG editor, typing seems to create bare text and hitting "enter" produces a
<br>
(which has been noted before in #94, though I can't say I actually understand @craigdietrich's comment there).If I look at that newly-created text in the front end using "view source", I see it within a
<span property="sioc:content">
element, but if I look at it using dev tools "inspect", I see it in a<div class="body_copy">
element (in both cases with a<br>
). What's going on here? Some sort of rewriting by javascript? And why the design choice to not enclose text in<p>
tags? Or is something wrong with our install?We're using Scalar 2.5.14, and here is a public test book on our site: https://scalar.ukrhec.org/test-book/. Thanks in advance for any clarifications or explanations!