I'd also caution against thinking of a component as a portion of the DOM, but rather a compartmentalized bit of your application. There can be and often are components which do not render anything - it's not as tightly coupled to the DOM as it seems.
A component could be responsible for making AJAX requests, and dispensing the response to a number of child components that do render, for example. There is nothing to view for the parent, it's just making requests to the server, but each child will depend on the data it provides. That way you can separate your concerns - the components responsible for displaying the data don't need to know about AJAX at all, they just get the data they need as props.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'd also caution against thinking of a component as a portion of the DOM, but rather a compartmentalized bit of your application. There can be and often are components which do not render anything - it's not as tightly coupled to the DOM as it seems.
Check out Presentational and Container Components for some talk about the pattern.
Oh I didn't know that. But how can there be a component without a view?
A component could be responsible for making AJAX requests, and dispensing the response to a number of child components that do render, for example. There is nothing to view for the parent, it's just making requests to the server, but each child will depend on the data it provides. That way you can separate your concerns - the components responsible for displaying the data don't need to know about AJAX at all, they just get the data they need as props.