Re:React 16
by danield9tqh on Tuesday September 26, 2017 @11:45PM
(#15344770)
This does worry me a bit though. There is probably a reason they are difficult to test, because they go against the React DOM pattern of a component only having control over the DOM nodes inside it. Call me a purist but this seems like a deviation from React's functional roots and going against the very problem React was trying to solve in the first place.
Re:React 16
by danabramov on Wednesday September 27, 2017 @06:25AM
(#15346371)
The feature is mostly intended for rendering into nodes not managed by React. Such as a document child that is sibling to the application root.
Portals are helpful when using content overflow in modals. For example, we have a modal which contains a form and that form has an autocomplete text box. When we render the autocomplete part, we need to render it outside of the modal, otherwise the overflow policy blocks the contents and does not allow the autocomplete are to appear over / outside of the modal.
The use of portals also make it easier to support screen readers through the aria tags by allowing the application to quickly block the background of the application and allow the screen reader to focus on the content presented to the user.