2 Platform-specific setTextFormat bugs

[Solid Gold Robot]

I see there's been some discussion about setTextFormat on cpp targets in the past, but I think what I'm experiencing now is a little different.

I've discovered that using setTextFormat without specifying start and end indexes (which is supposed to be allowed) causes a hard crash on iOS. But simply adding the start and end indexes fixes it. 

However, if you include start and end indexes, TextFields will no longer center on HTML target (despite using TextFormatAlign.CENTER). 

So, possibly 2 different bugs in setTextFormat? 

I'm working around with target-specific code now, but would like to avoid that.