Open/close arrows stop working randomly

[mtravers]

Every so often, for no apparent reason, the open/close widgets in the app-db browser just stop working completely. When this happens, none of them will respond at all (aside from the top-level one -- but any opener on a green background is completely nonfunctional. Same behavior with 0.4.1 0.4.3.

Driving me crazy, because it makes this otherwise extremely valuable tool kind of useless.

[mike-thompson-day8]

This is a duplicate of #209 but we thought it was fixed with v0.4.3 (I'm assuming you are using 0.8.x and React 16.8.6)

BTW, I assume you are aware of the workaround:
https://github.com/Day8/re-frame-10x#the-expansion-triangles-in-the-data-browsers-dont-work-any-more-but-they-used-to

[mtravers]

I'm using Reagent 0.8.1, which is the latest available AFAIK, which brings in [cljsjs/react "16.3.2-0"]. Wasn't aware of the workaround, thanks for pointing it out (but completely resetting Chrome isn't something I want to do very often).

…

On Tue, Oct 8, 2019 at 5:18 PM Mike Thompson ***@***.***> wrote: This is a duplicate of #209 <#209> but we thought it was fixed with v0.4.3 (I'm assuming you are using 0.8.x and React 16.8.6) BTW, I assume you are aware of the workaround: https://github.com/Day8/re-frame-10x#the-expansion-triangles-in-the-data-browsers-dont-work-any-more-but-they-used-to — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#251>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAEUUZE7C3RA5FEYED744LQNUPNBANCNFSM4I6YOZNQ> .

[mike-thompson-day8]

No need for a complete reset, just local storage for your app.

While running your app), in Chrome, go to devtools (F12), choose the Application Tab and then select (on the left) Local Storage and clear out what's there. Restart your app. Fixed? (Warning this removes your re-frame-10x settings)

[superstructor]

@mtravers Firstly apologies for this issue. We know its annoying and we want to get this fixed.

Is there any additional information you can provide to help me find reliable reproduction steps ?

Roughly how frequently do you experience the issue ?

Does this only occur when using re-frame-10x in an external window or does it also occur as the default internal panel on the right ?

[mtravers]

Thanks for the reply! I can't really give reproducible steps, sorry. It happens infrequently, and I *think* it only happens when using the external window (however, once it gets in stuck mode the problem appears on the internal panel as well).

…

On Tue, Oct 15, 2019 at 8:19 PM Isaac Johnston ***@***.***> wrote: @mtravers <https://github.com/mtravers> Firstly apologies for this issue. We know its annoying and we want to get this fixed. Is there any additional information you can provide to help me find reliable reproduction steps ? Roughly how frequently do you experience the issue ? Does this only occur when using re-frame-10x in an external window or does it also occur as the default internal panel on the right ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#251?email_source=notifications&email_token=AAAEUU3SKMZ5TXG54YU32UTQO2B3XA5CNFSM4I6YOZN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBK4QHQ#issuecomment-542492702>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAEUU5CBHEBJY7WDJDYWJLQO2B3XANCNFSM4I6YOZNQ> .

[superstructor]

[hipitihop]

I believe the core issue is caused by the re-frame application tab in the browser losing focus. When you switch to another tab in the same Chrome window, all 10x interactions stop responding, top tabs and including the expand arrows. When you switch tab back to your re-frame application, 10x catches up and responds to the last interaction.

NOTE 1: Effects all interactions, not just the arrows.

NOTE 2: Only happens when switching tabs within the same Chrome window. General focus change, e.g. if you have another Chrome window open and you switch to that while you re-frame application tab is still the current tab in the other Chrome window, then 10x continues to function as expected.

[kimo-k]

Closing for now.

Can't reproduce the original bug. @mtravers, please let us know if you're still affected.

Added some documentation for the behavior described above by @hipitihop. This is technically fixable, but the fix seems high-effort and could have browser compatibility & legacy issues.

More importantly, the concern is out of scope, IMO. If there's a critical use-case for switching tabs in the browser window where your app is running, please let us know. Otherwise, you can always just use a different window.