Page 1 of 1

Tile tabs incompatible with v25.02

Posted: 2014-11-03, 18:03
by MrToad
When I upgraded from V24.71 to 25.02, clicking a link to open it in a new tab, produced a duplicate of that link in both tabs. I switched back to crashfox but after 4 crashes came back to palemoon..since duplicate tabs with the problem, I disabled tile tabs on one pc and removed it on another. Palemoon worked fine after that. Since I don't use tile tabs much and I can always use in in FF or waterfox, I won't miss it. I post this in case others are having a similar problem and to give a heads up to MC in case there's an easy fix.

Re: Tile tabs incompatible with v25.02

Posted: 2014-11-04, 22:20
by astewart
Tile Tabs version 11.13 is available under Version Information -> See Complete Version History. It has been fixed for Pale Moon 25. Works for me.

Alan

Re: Tile tabs incompatible with v25.02

Posted: 2014-11-17, 05:25
by Aelius81
Tile Tabs, even the most recent version, still has at least one problem: shift+drag should create a new tile in the direction you let go of the drag. However, in Pale Moon, it assigns (i.e. replaces) the dragged tab onto the active tile. Additionally, this problem does not occur when using the "Tile Tab" functionality from the context/drop-down menus (i.e. activate Tile Tabs so the screen is split into tiles; right-click a tab; select Tile Tab and choose a direction.) That works, but shift+drag (which is supposed to do the same thing) does not work as expected. Shift+drag will assign (i.e. replace) rather than tile (i.e. create new tile.)

I have confirmed that this problem exists:
  • in PM 25.02, and 25.1
  • with no other extensions enabled
  • with default about:config settings.
  • with default Tile Tabs settings
I have also determined that this problem does not exist in Firefox.

Re: Tile tabs incompatible with v25.02

Posted: 2015-01-12, 05:17
by astewart
The fix in Tile Tabs 11.13 was for a key assignment error, but the problems with drag functions as well as with "Tile Link in New Tab" menu item still occur because Tile Tabs uses a browser api "Task.spawn()" defined in the Task.jsm module, in those functions for browser versions 25.0 to 31.0.

As written, that generates a error "Task is not defined" in PM. I added

Code: Select all

Cu.import("resource://gre/modules/Task.jsm");
to the Tile Tabs code and that got rid of the error, but the functions still don't work.

I added a couple lines to force the browser version to 24.9 in Tile Tabs for the PM guid

Code: Select all

var palemoon_ID = "{8de7fcbb-c55c-4fbe-bfc5-fc555c87dbc4}";
if (tileTabs.appInfo.ID == palemoon_ID) tileTabs.ffVersion = "24.9";
so the lines with Task.spawn aren't executed, and that seems to work correctly, although I haven't tried everything. I'm guessing there is some efficiency disadvantage in not using Task.jsm.

Task.jsm exists in PM, Task.spawn is defined there, and the .jsm code comments are virtually identical to the docs at MDN. Have there been any changes or differences to Task.jsm between Firefox 25 and PM 25? Is Task.jsm imported somewhere already in Firefox, so the extension didn't need to do the import?

Alan