Ingvar Stepanyan

> children in props is React's design artifact and I for example do not want it, so I do not use React specific output. This is happening only in optimizer...

> PS. This belongs in React as @sebmarkbage believes whitespace rules are best left outside of the spec. Ah, if we leave this outside the spec, then fine. Because for...

> I think the fact that it is easily gzipped is irrelevant, it shouldn't be there I thought it was the reasoning why you didn't want to see it there....

> Pretty much every single project I've ever worked on has used a post-process for stripping white-space out, it's has worked fantastically to get consistently pixel-perfect layouts, across all browsers....

> See #6 for why white-space behavior is unspecified. Oh, didn't find it on my own. Sorry for that. > It's kind of inconvenient that this is underspecified because this...

@syranide Sorry, I might not remember details of topic being discussed ~2 months ago but didn't we discuss trimming whitespaces on ends of content and not whitespaces in between?

> Babel doesn't support this correctly either: Hmm, it definitely did earlier, and from the error: > repl: Property value of JSXAttribute expected node to be of a type ["JSXElement","StringLiteral","JSXExpressionContainer"]...

> we didn't realize the spec had been changed In fact, this feature here from the very beginning. > And nobody spotted it. Well, from > because we had gotten...

> It was very clearly added to the spec with PR #15 which happened after the JSX spec was first public. @ RyanCavanaugh Sorry for the confusion - I mean...

@spicyj That's weird, I remember actively using it way before Babel.