-
Notifications
You must be signed in to change notification settings - Fork 10
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
Suspended tabs sometimes return as e10s tabs #30
Comments
Im not the dev but in the meantime I think i can lend you a hand and save you and the dev some time Can you list the steps to reproduce it? Also try the dev version to see if it's solved there. piro.sakura.ne.jp/xul/xpi/nightly/ |
Just tried it with a VM vanilla install of beta 33 and the dev version you mention and it can be reproduced fairly easily:
|
Have you tested if this happens on a clean profile with just this extension installed? |
As I said, I tried it with a vanilla (fresh) installation in a virtual machine (Windows XP) with just the development version of the extension installed. You are welcome to try yourself |
I tested it and on firefox 33b8 even though the tabs are underlined instead of being greyed out I'm able to swich between them when they get suspended but I noticed that the right click menu gets disabled for me and i cant open new tabs or close existent tabs or close firefox at all and if there are tabs with flash content like youtube if you load that tab make it unload then try to lad it again firefox will skip that tab and jump to the next one (maybe this is what happened to you?). So yeah the add-on it's not compatible with firefox 33. |
Thanks, I didn't know the method is renamed on Firefox 33... |
Tested in VM and I can confirm rayman89's findings |
Seems to be expired. |
I updated to Firefox Beta v. 33 and now some tabs' titles are randomly underlined. Those tabs cannot be closed anymore. Sometimes the tab can't even be accessed anymore but that too is random.
I read on various sites that underlining means e10s is enabled but I checked about:config and both browser.tabs.remote and browser.tabs.remote.autostart are set to false.
After someone told me it might be related to this extension, I disabled it and the problem went away, so I think it's a bug in this extension
The text was updated successfully, but these errors were encountered: