-
Notifications
You must be signed in to change notification settings - Fork 8
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
Odd fail on 52.2.1; left click disabled...but works in new window #134
Comments
Same issue here, with an exception - Left click won't work in ANY (ie. ALL) of my tabs. In other words, this renders my Firefox unusable :) |
Same issue here, but (unlike OP) if I open a new window that one doesn't work either. I have noted three things:
So this really seems like a tab positioning issue? Something conflicts with the tabs and click detection or something? Win10 Pro, FF ESR 52.2.1 64-bit |
Out of curiosity, do you guys have Firefox Sync set to sync add-ons? My FF is working again but I did a lot of things in a short period so I'm not sure which resolved it (or if it will return). One change I made was turning off the sync. So do you have it set? |
1--I don't use FF Sync. 2--Double-clicking does nothing for me once the app "freezes." 3--I'm seeing indications the malfunction may relate to the # of open tabs. I tend to have lots of tabs open...presently 200. I find that if I save my session, close FF, reopen with just a few tabs, then load the main session, everything works fine. But if I close & reopen with the full session, all the tabs are locked up as described above & FF is unusable. Hoping there's a fix for this soon... |
1. I do have FF Sync - not for Add-Ons 'though (FF Sync Add-Ons unchecked).
2. Double clicking maximises the screen.
3. I just have a bunch of open tabs (certainly less than 10).
…_________________________________________
blog: http://www.pwrusr.com
linkedin: http://www.linkedin.com/in/andreamatesi
On Sat, Jul 22, 2017 at 2:24 PM, conquerist ***@***.***> wrote:
@RC-3 <https://github.com/rc-3>
Have you tried TabKit 0.12.17 with Classic Theme Restorer configured as
described here
<https://github.com/tabkit/tabkit2#classic-theme-restorer-since-firefox-290>
?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#134 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APpmf9qTWxEo8xTGc2e7y7wYMhQNH6Zwks5sQYBogaJpZM4OR7UF>
.
|
I have tested 0.12.27 on firefox portable 52.2.1 (32-bit) from portableapps.com left single click on tab bar - worked (select the tab) in addition I noticed when the mouse pointer hover on a link the pointer is still arrow shape. hope this would any help |
Well said hiyokogit - I'm experiencing the same (mis)behaviour as
hiyokogit. Thanks, Regards, Andrea.
…_________________________________________
blog: http://www.pwrusr.com
linkedin: http://www.linkedin.com/in/andreamatesi
On Sun, Jul 23, 2017 at 3:37 AM, hiyokogit ***@***.***> wrote:
I have tested 0.12.27 on firefox portable 52.2.1 (32-bit) from
portableapps.com
FirefoxPortableESR_52.2.1_English.paf.exe
I extracted the archived file then I only installed Tab Kit 2nd Edition
firefox built-in options are untouched.
left single click on tab bar - worked (select the tab)
left double click on tab bar - worked (open/collapse tree)
left single click on menu bar - worked (show dropdown menu)
left single click on a link - does nothing
left double click on blank space - maximize window(toggle)
left double click on a link - maximize window and open the link
wheel click on a link - worked (open the link in a new tab)
in addition I noticed when the mouse pointer hover on a link the pointer
is still arrow shape.
hope this would any help
sorry for bad english
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#134 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APpmf0UESHV-d34Oie-zgUsPyGZPJeJKks5sQjpOgaJpZM4OR7UF>
.
|
Following @conquerist's advice fixed this problem for me. Install Classic Theme Restorer and apply the config:
|
Hey Ben, you suggestion worked wonders - I've unchecked "Use Firefox
titlebar instead of OS titlebar" and now I can use Firefox again (left
click now works).
[image: Inline image 1]
# Uncheck "Use Firefox titlebar instead of OS titlebar" to fix this issue.
…_________________________________________
blog: http://www.pwrusr.com
linkedin: http://www.linkedin.com/in/andreamatesi
On Mon, Aug 7, 2017 at 11:52 AM, Ben Barsdell ***@***.***> wrote:
Following @conquerist <https://github.com/conquerist>'s advice fixed this
problem for me.
Install Classic Theme Restorer and apply the config:
- Uncheck Use Firefox titlebar instead of OS titlebar in Firefix
button page: fix the totally unusable layout and strange click behaviour
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#134 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APpmfyUqZU_8XXREdAwllp0OCpe4qKwWks5sVnTPgaJpZM4OR7UF>
.
|
I appreciate the suggestions, but have had "Use FF titlebar instead of OS titlebar" disabled** since before reporting the 52.2.1 FF upgrade problem. I continue to experience the same issues originally reported with this version, & am postponing upgrades on my other PCs. ** (I love the extra screen space the titlebar substitution yields, but found that it caused problems with prior FF versions, & have kept disabled since.) |
Allowed 1 of my systems to upgrade to FF 52.3.0 esr Nothing's worse, but nothing's fixed, either. Any help or ideas?? |
@PikachuEXE Sorry, realized I never replied to this. I blame FF Sync. |
FF Sync? The built-in feature? |
Immediately on installing the ESR 52.2.1 update, FF loaded & appeared fine...but left-clicking had no effect on tabs, or anywhere else.
In a 2nd FF window--with the 1st window remaining open--everything is normal, & remains so if 1st window closed. It stays that way until I reboot.
I'm still experimenting & will post any other symptoms/patterns that appear, but this has now been replicated on 2 PCs.
Anyone have similar experience, or ideas on fixing?
The text was updated successfully, but these errors were encountered: