Using React 16 to open new window with shared state

Re:Using React 16 to open new window with shared state by euroclydon on Thursday November 09, 2017 @11:07AM (#15663515)

This is a bad idea for any serious app. I inherited a framework that did this, and it performed terribly. Not to mention, it’s an exercise in discovering browser edge cases you would have otherwise never had to worry about. Use postMessage or localStorage to communicate between windows. Don’t use window handles.

[ Parent | on HN ]

Re:Using React 16 to open new window with shared state by hellofunk on Monday November 13, 2017 @09:58PM (#15692252)

I suppose the newer BroadcastChannel would be an option too, for high performance multi-window usage.

[ Parent | on HN ]

Re:Using React 16 to open new window with shared state by caffed on Thursday November 09, 2017 @12:39PM (#15664243)

Yeah, I use MessageChannel ports whenever communicating across domains: extensions, Workers, etc.

That was I can abstract it into convenience classes for connecting, event listening, etc.

[ Parent | on HN ]

Re:Using React 16 to open new window with shared state by abritinthebay on Thursday November 09, 2017 @12:06PM (#15664003)

Teah, it’s a clever (if not new) hack but there already exists a sane way of doing this

[ Parent | on HN ]

Re:Using React 16 to open new window with shared state by kimjongman on Thursday November 09, 2017 @12:08PM (#15664022)

I will block react with ublock

[ Parent | on HN ]

Re:Using React 16 to open new window with shared state by dymk on Thursday November 09, 2017 @03:00PM (#15665391)

[ Parent | on HN ]