You will notice that anywhere I wanted a carriage return I had to actual do two returns and I still did not really get a paragraph break when viewed in the browser as shown below.
We had a similar problem in the v1 text editor, is this just something that has not been fixed or am I missing something.
In it’s current form this component is not viable for longform text in the true sense of the word. Don’t get me wrong it is a lot close than v1 but there are still issues.
The other problem I have run into is with the specifying of custom typography in the Theme Studio. It is fantastic that you can setup all of this stuff in the first place. But there appear to be some problems. In my case I’m trying to setup the typography for the BODY using a custom font family I had setup. I select this custom font but it is not applied through the custom typography element. It is still displaying the font in the default font and not my custom font. I can select the text and change it to my custom font, but that defeats the whole reason for this custom element.
I’ve tested this and it seems to working here just fine Can you make sure you’re running the latest beta (Version b18, 23018) as we did put in some fixes for this.
If it still doesn’t work, can you share the project file so we can take a look and find out what’s going on?
Yes, I am running b18 and I have just tried it again and it does not use my font selection. I can by pass the problem by selecting the text and setting it inline, but that defeats the whole purpose.
Here is the link to the project.
elementsapp://downloadDocument/Qyr4Wi9wXD9B
Sorry I forgot to add. Go to the Details page and look in the FEATURES section and you will see some Typography (man that is a hard word to type) components in my temporary cards.
I have a case where multi-line text copy-pasted from BBEdit (or from the v1 text) does not result in multiple paragraph tags, but typing return in the inline editor does work as expected.
(running b18)
sample project: elementsapp://downloadDocument/llnQ01em9eir
Hey @handshaper, Okay, we’ve located (and fixed) the problem! The Typography component was showing it had a style selected, but it wasn’t actually selected — the value was null.
Anyway, beta 19 fixes this issue, and I’ve recorded a quick video walking you through the changes and showing how it now works!
Thanks for the report… right now, copying and pasting text into the editor often doesn’t work as expected as it strips out all styles. We’ll take a look at this and see what we can do!
I just wanted to add that I discovered that the typography component is sensitive to where the text comes from if it is copied and pasted into the component. The example I gave at the top of this post was copied from a Stack in Classic and pasted into the component. When I took that same text and first pasted into TextEdit and formatted it before pasting it the result was much cleaner and as expected.
I also discovered that to get better separation between my paragraphs I had to tweak the margins in my custom typography. Then I got much better looking text in the browser.
Can you make sure you’re running the latest beta (Version b18, 23018) as we did put in some fixes for this.