Is anyone working on support for Firefox 36?

[Hal Wine]

Firefox 36 is scheduled to be released on February 24[1], and it looks like Pentadactyl would need some significant work to support 36. The usual "bump the max version" trick won't work this time.

Unfortunately, I don't see signs of any such work in the repository at https://code.google.com/p/dactyl

If anyone is working on support, I'd love to help in any way I can (test, doc, minor tweaks). Let me know.

--Hal

[1] https://www.google.com/calendar/embed?src=mozilla.com_2d37383433353432352d3939%40resource.calendar.google.com

[wsha...@gmail.com]

Yes, if you look at the commit log for the past couple days, you will see some new commits trying to address the breakage.

[n.t.g...@gmail.com]

Not working on FF 36 :(

[Mrrob]

The nightly works fine for me:

:version
Pentadactyl hg7157-default (2015-02-25 12:45 -0800) running on:
Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0

I'm bloody happy about it! <praise bow>

---
mrrob
---

> <https://www.google.com/calendar/embed?src=mozilla.com_2d37383433353432352d3939%40resource.calendar.google.com>
>
> --
>
> ---
> You received this message because you are subscribed to the Google
> Groups "Pentadactyl" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to pentadactyl...@googlegroups.com
> <mailto:pentadactyl...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

[google]

Yes, nightly working well! Thanks! Did not saw they appeared again.

I tried 'hg pull', 'make -C pentadactyl xpi' and it did not worked for me.

[gt]

On 26 February 2015 14:29:16 GMT+05:30, google <n.t.g...@gmail.com> wrote:
>Yes, nightly working well! Thanks! Did not saw they appeared again.
>
>I tried 'hg pull', 'make -C pentadactyl xpi' and it did not worked for
>me.

You need to do:

hg pull -u

[ant...@gmail.com]

Did the latest nightly break "gg" for anyone? I also can't use <number>% navigation, or navigate to lines with <number>G. I can, however, get to the end of the page with G. Maybe multi-key commands are broken in general?

[Raghavendra Prabhu]

Hi all,

On Sat, Feb 28, 2015 at 1:22 AM, <ant...@gmail.com> wrote:

Did the latest nightly break "gg" for anyone? I also can't use <number>% navigation, or navigate to lines with <number>G. I can, however, get to the end of the page with G. Maybe multi-key commands are broken in general?

Is :tabclose broken for anyone on latest hg tip?  It seems to be failing for me. 

-----

Raghavendra

 

On Thursday, February 26, 2015 at 8:27:45 AM UTC-5, gt wrote:

On 26 February 2015 14:29:16 GMT+05:30, google <n.t.g...@gmail.com> wrote:
>Yes, nightly working well! Thanks! Did not saw they appeared again.
>
>I tried 'hg pull', 'make -C pentadactyl xpi' and it did not worked for
>me.

You need to do:

hg pull -u

--

---
You received this message because you are subscribed to the Google Groups "Pentadactyl" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pentadactyl...@googlegroups.com.

[gt]

On 28 February 2015 11:12:45 GMT+05:30, Raghavendra Prabhu <raghu.p...@gmail.com> wrote:
>Hi all,
>
>On Sat, Feb 28, 2015 at 1:22 AM, <ant...@gmail.com> wrote:
>
>> Did the latest nightly break "gg" for anyone? I also can't use
><number>%
>> navigation, or navigate to lines with <number>G. I can, however, get
>to the
>> end of the page with G. Maybe multi-key commands are broken in
>general?
>>
>
>
>Is :tabclose broken for anyone on latest hg tip? It seems to be
>failing
>for me.

:tabclose is working fine for me with hg7157.

@antijr, all the things you mentioned are working fine in my case.

[zemat...@gmail.com]

Any shortcut that takes two characters is broken for me.  go, gn, gg, ZZ... I see that the first character disappears after the second character is input.  Anyone else seeing this?

[Alex Goins]

Yeah, that's what I was seeing before. I installed the latest nightly (2/28) and it seems to be fixed, although I'm not sure if that's what fixed it.

--

---
You received this message because you are subscribed to a topic in the Google Groups "Pentadactyl" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pentadactyl/1AbaOmajc2E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pentadactyl...@googlegroups.com.

[Roland G]

Is :tabclose broken for anyone on latest hg tip?  It seems to be failing for me.

It was also broken for me. I figured out that the tab-options plugin was the problem. I only commented out the reasoning function (around line 71 in tab-options-dev.js ) because I don't need it.

[Nate OMD]

Roland,

Thanks for the advice.  I, too, have had zero luck, trying both hg from "tip" and the Feb 28 nightly, as well as the March 2 & 3 nightlies.

If there are 2 add-ons I cannot live without, there are pentadactyl & Tab Mix Plus.  Given others' reports of success, I had an unjustified suspicion of some interaction issue between PD & TMP.

You say "tab-options" -- I guess you mean "New Tab Options"?   No big deal for here, but it may be of consequence for the PD devs.

In case anyone else is reading this, here are the specific symptoms I was getting as of 01:00 Eastern (US) time this morning:

• firefox generally came up ok.  ("generally":  well, only 1 tab row until I restarted it, and some other small issues in window framing.)
• 'gT' and 'gt' seemed to work OK.
• when I hit 'f' or 'F',
• I got the prompt to enter the link letters I wanted to go to.  (apologies, as I forget the proper name for this feature.)
• the link highlights did not display
• As I recall, FF would freeze up shortly after attempting this.
• when I hit ':' (to get command prompt), FF would freeze each & every time.
• I'm not sure on this point, but I feel like -- even if I did not hit ':'/'F'/'f' -- sometime FF would lock up.
• Maybe this is personal anxiety on my part, or leftover apprehension having seen this symptom at previous FF upgrades, but I feel like when PD+FF have this vulnerability, then I have only a limited time to try what I can before FF freezes up.
• "FF Freezing" means:  I'd get a "busy" spinner that just would not go away.  I'd have to "force quit" FF.

Wondering if anyone knows:  is there a difference between uninstalling PD before installing a new version, versus simply updating to a new version?

During my trials, I tried both ways without seeing a difference.

Thanks to all who help!

[Roland G]

sorry if I'm wrong here.. Ive got no idea how to select the post to answer to...

@Nate OMD

You say "tab-options" -- I guess you mean "New Tab Options"?   No big deal for here, but it may be of consequence for the PD devs.

No I mend the tab-options PD - plugin.
Looks like a different issue.
For me none of your problems appears.
I use the latest nightly with firefox 36 on arch linux..

[Nate OMD]

Roland,

OK.  Thanks for the info.  

I'm using FF 36.0 on OS X Yesemite (10.10.2)

I don't know how it could be, but I wonder if the issue is mac-specific.  (The entire extension is in javascript, isn't it?  JS ought to be agnostic to OS, I would think.)

The only thing I can imagine is if I need to convert the (javascript & css) text files from their default unix line endings (<LF> at ends of lines) to mac line endings (<CR> at ends of lines.)

Anyway, I'm glad one of us is having good fortune!

[wsha...@gmail.com]

Answering your earlier question -- it shouldn't make a difference whether or not you uninstall Pentadactyl before installing a new version.

Regarding the issues you see, I don't know what could be going on but I did see some similar complaints from another OS X user on IRC. Like Roland, I am using Firefox 36 on Arch and Pentadactyl seems to be working fine for that configuration.

As a sanity check, I recommend installing Pentadactyl into a new Firefox profile and see how it behaves there. That removes most of the possible confounding factors. I also recommend moving your .pentadactylrc and .pentadactyl folders to a different location temporarily in case you have a setting or plugin that is problematic.

Here are some links on working with Firefox profiles in case you haven't done so before:

https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
http://kb.mozillazine.org/Profile_Manager

[Nate OMD]

wsha... ~

Thanks for the guidance.  It was a worthwhile pursuit:  In summary:

• in the new profile, pentadactyl seemed to work fine.  Tho I didn't do more that a cursory check with link shortcuts & some other keystrokes, everything seemed normal.
• I noticed starting up this way created a great spewage of log data.  (Perhaps this normally goes into a file somewhere?  I don't know.)  So I restarted Firefox with the usual profile & this time piped the spewage into a file, which I'll have to review later.  At this point, I'll say I saw only 2 statements obviously about PD, and neither obviously related to any major problem.
• JavaScript warning: resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///Users/... .../extensions/penta...@dactyl.googlecode.com.xpi!/bootstrap.js, line 392: JavaScript 1.7's let expressions are deprecated
  
• addons.xpi DEBUG removeTemporaryFile: file:///Users/nschley/dactyl/pentadactyl-latest.xpi does not own temp file
  
• Strangey, FF did not freeze when I started it this way with PD active.
• I wonder if the "freeze" may be related to this JS warning that issued for a few other add-ons & scripts:
• mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create
  
• Interestingly, I got no log errors or warnings when I tried PD keystrokes.  Wondering if this suggests the keystroke config -- however that works -- was unable to get config'd correctly, or is blocked by some other package somehow.

I likely won't be able to get into what I logged today, but will advise anything I find when I get to it.

Thanks again!

Nate

[Nate OMD]

wsha... ~

Well, never mind the backstory, but here is some log data.  I've removed the relatively few lines that are not PD-related, and I cut short the 21 identical follow-on instances of line #124.

Otherwise, I hope the attached file contains enough info to give some savvy individual some idea as to the issue.

Thanks yet again, & Holler if I can do anything to help!

Nate

[Nate OMD]

Just to complete the thread:  the issues I raised last month concerning Pentadactyl on Mac seem to have dispersed.

I installed the latest PD & enabled it in the current FF (37.0.1.)