I created a repeatable with just one editable in it - a nicedit since richtext is not supported in a repeatable. However I'm having a problem with it compressing out spaces. In source mode, I enter:

Code: Select all

This is a test:<p style="text-shadow: 0px 0px 10px #ff0000;">This should be highlighted text.</p>

And after saving it becomes:

Code: Select all

This is a test:<p style="text-shadow:0px0px10px#ff0000;">This should be highlighted text.</p>

[KK]

Yes, I noticed that behavior, @wysocki.

I think it'd be best to avoid inputting raw HTML into nicedit directly and stick to using only the buttons it provides for formatting. It is a lightweight editor but is not without its flaws (actually several of them).

@KK, Nicedit is indeed a very disappointing editor. Lightweight is fine, but I find it nearly unusable, even for it's express purpose in repeatable regions. Will the upcoming Redactor editor by any chance be available in repeatable regions?

@wysocki, It might not work, but you could try html-encoding the spaces.

Code: Select all

<p style="text-shadow: 0px &nbsp; 0px &nbsp; 10px &nbsp; #ff0000;">

Another option would be to use a CSS class instead.

Code: Select all

<p class="my-class">

[trendoman]

I tested this also and found no issues. Of course, spaces are being eaten by nicedit, but the effect is applied anyways. So, what's the hassle? Seems, I missed the point, guys.

...the effect is applied anyways.

Really? What browser are you using? Even in when I view the page and view the source it shows style="text-shadow:0px0px10px#ff0000;" and the effect is NOT applied since it's a css syntax error.

[KK]

@trendoman, as far as I could see, the effect (red colored text) is visible only at the initial data input - as soon as you save the page, the style as mangled by nicedit takes effect and the red color disappears. I think you did not try saving the page, hence the confusion.

@Tim, I totally share your sentiments about nicedit. I think it is time now to say goodbye to our old friend now. However, I'm not placing this on my todo list of things to do immediately. Please wait for the initial release of v2.0 and then we'll address this.