4 ms·
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 browse
by euroclydon 9y ago
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.
- abritinthebay 9y agoTeah, it’s a clever (if not new) hack but there already exists a sane way of doing this
- kimjongman 9y agoI will block react with ublock
- dymk 9y agoOk
- caffed 9y agoYeah, 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.
- hellofunk 9y agoI suppose the newer BroadcastChannel would be an option too, for high performance multi-window usage.