-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
re-open tab in other container: no longer effective #38
Comments
this is true if tab moving is enabled in taborama which basically implements the functionality of "Context Plus". If tab moving is disabled, "Context Plus" works as expected. |
Sorry, there's some misunderstanding. Please reopen this issue. With Taborama alone:
Reproducible with 0.0.38 on (unsupported) Firefox 55.0.3. I'll retest with 57.x. The mention of the side-effect, on Context Plus, was to maybe help understand a cause of this issue. |
Reproduced with Taborama 0.0.38 alone on Firefox Nightly 57.0a1 (2017-09-16) (64-bit) on Kubuntu. |
mmm ... it works here with Nightly. What exactly is the problem? Changing from a container to the default container? |
When a container is clicked, it appears to be selected, then nothing more happens. Here's a screen recording of the symptom with 55.0.3 on FreeBSD-CURRENT. The symptom is the same with Nightly on Kubuntu. |
ha ... thanks a lot for your efforts -- even a movie. |
just released v0.0.39 which should fix the problem ... thanks again |
Fix confirmed. Tested: Taborama 0.0.44 with Firefox 55.0.3 on FreeBSD-CURRENT. |
Issue observed with 0.0.32, 0.0.33 and 0.0.34.
Also (echoes of recently closed reopen tab in other … default: does not work for contained tabs · Issue #36 · kesselborn/taborama):
The text was updated successfully, but these errors were encountered: