Hi, Rudy! It looks like react-next has this bug too. https://github.com/massiveinteractive/haxe-react/issues/131