Html formatting on Content Area toggle text?

[md1088]

Hi,
I’ve noticed something odd recently when trying to make a few content area modals. I need to have more than 2 lines of information on the toggles themselves, but given there’s only “Primary Text” and “Secondary Text” on the toggle, I figured I’d put a few html line breaks ( < br > without the extra spaces since the forum picks up on html too ) in there for the primary and secondary text fields and that will solve the problem. While it looks okay in the preview when working in Pro, it doesn’t actually work in any web browsers (chrome, firefox, ie), but rather the < br > is written out instead of interpreted as html.

Interestingly, for a ‘button’, using < br > and other html snippets works fine. So, my question is if it works for buttons, why not for content area toggles too?

See screenshots for a visualization of what I mean:

I’ll leave the example page up for a bit too – https://eoas.rutgers.edu/sandbox/

Thanks!

[christian]

Hey Matthew,

Thanks for reporting. I have replicated what you described in my test site. I will post this in our issue tracker so that this will be queued up for investigation by our developers.

We could not say if this is a bug yet as our developers might not allow HTML in both elements. If that is the case though, the behavior should be the same for both elements.

I discovered a workaround. But, please note that this is not recommended as this might break in the future. The workaround is instead of using <br>, insert a Gap shortcode with no quotes around the value like this: [gap size=1px].

• 

Hope that helps.