Hello.
I'm running into this problem and I just downloaded Greensock today. A lot of the examples are a little outdated, but I'm using the main example on the site as a basis: https://codepen.io/GreenSock/pen/mvhak
I feel like I'm following everything to the tee. But when I run it, SplitText is not honoring my <br> tag on my string. However, I call .revert() after everything is done via "onComplete" and, after revert takes place, the <br> tag immediately becomes recognized.
This is essentially my code. I create my string, set it to the "topicDetail" item of my html, make sure the opacity is fully on, then set up my animation. Again, when it runs, the <br> tag is ignored, but as soon as revert() is called, the <br> kicks in and the text snaps instantly to splitting properly.
var topicDetail = "This is a test to see<br>if my Break Tag is honored.";
// Set the topic detail.
$('#topicdetail').html(topicDetail);
// First make sure it's set to full opacity, just in case.
TweenLite.set('#topicdetail', {opacity: 1});
// Set the animation for the detail text.
var tl = gsap.timeline({onComplete: revert});
var mySplitText = new SplitText("#topicdetail");
var chars = mySplitText.chars;
tl.from(chars, {duration: 0.5, opacity:0, scale:3, y:40, ease:Back.eastOut, stagger: 0.02});
When I replicate this on the codepen sample page from above, it works just fine.
Now, I AM running the web page not via a browser, but inside XSplit, an application designed for streaming for sites like Twitch.tv. However, that shouldn't be the problem, I don't think. But you never know. Better to give all the info possible. Everything else has been running properly on XSplit thus far.
Edited to add: Messing with the sample page above, revert() also causes a snap on the text above even if the only thing I change is adding "revert()" as an onComplete. That's not really the bug I'm here to tackle, but it does seem to be a bug in general that the text that gets produced doesn't match, exactly, the text after being reverted. Obviously I'm okay with not calling revert() at all if that bug remains, but I still would like my <br> to be properly processed.