You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Newlines between spans is rendered as a whitespace:
a
b
rendered as "a b".
So i am not sure if the spans should be forced to multilines because you really HAVE to do something like:
a<span *ngIf="">b to be rendered as ab... Maybe we are able to workarround this by using ng-containers despite of spans, but... its awfull and not correct.
Activity
kunajs commentedon Jul 20, 2018
I agree. For example this:
My name is <span class="font-green">Jesus</span>.is formatted as:
which creates unwanted HTML space between "Jesus" and "."
Using ng-container instead of span does the same.
It is very common scenario that you need to have no space after some tag.
stringham commentedon Jul 21, 2018
I'm happy to accept a pull request for this issue, if someone wants to try to fix it.
montella1507 commentedon Aug 1, 2018
I am willing to do that in next weeks, when not so busy