First Last Prev Next    No search results available
Details
: Support Postbox 5.52 (new platform)
Bug#: 26470
: QuickFolders
: General
Status: RESOLVED
Resolution: WONTFIX
: PC
: Windows NT
: unspecified
: P2
: major
: ---

:
:
:
:
:
  Show dependency tree - Show dependency graph
People
Reporter: Axel Grude <axel.grude@gmail.com>
Assigned To: Axel Grude <axel.grude@gmail.com>
:

Attachments
4.9 prerelease 1 (711.88 KB, application/x-xpinstall)
2018-01-12 16:31, Axel Grude
no flags Details
4.9 prerelease 5 (711.93 KB, application/x-xpinstall)
2018-01-12 17:15, Axel Grude
no flags Details
4.9 prerelease 6 (711.94 KB, application/x-xpinstall)
2018-01-12 17:33, Axel Grude
no flags Details
4.9 prerelease 13 (712.12 KB, application/x-xpinstall)
2018-01-13 15:00, Axel Grude
no flags Details
4.9 prerelease 16 (backwards compatible) (712.07 KB, application/x-xpinstall)
2018-01-15 02:18, Axel Grude
no flags Details


Note

You need to log in before you can comment on or make changes to this bug.

Related actions


Description:   Opened: 2018-01-12 16:27
QuickFOlders Pro Licenses do not validate in the latest Postbox beta 5.52 beta
3

Instead there is an error "myAccounts is undefined" in the error console.
------- Comment #1 From Axel Grude 2018-01-12 16:31:02 -------
Created an attachment (id=8358) [details]
4.9 prerelease 1

Here is a quick patch. Apparently Postbox is trying out a build with a much
newer code base (Gecko 52) so some of the workarounds which were meant for its
currently outdated JS engine have to be modified / avoided.

Generally there are a lot of places in the code that refer to Postbox and
probably need to be fixed (legacy CSS, avoiding for..of etc.)

There are some more modern "Shim Code" methods which need to be made available
to the new version of Postbox while maintaining backward compatibility, so this
by no means completely fixed just yet. Anyway this version should at least
validate QF Pro licenses so that users can keep testing the latest Postbox
beta.
------- Comment #2 From Axel Grude 2018-01-12 17:15:54 -------
Created an attachment (id=8359) [details]
4.9 prerelease 5

Restoring more basic functionality for Postbox beta. Needs to be tested against
legacy Postbox (5.0) as well!
------- Comment #3 From Axel Grude 2018-01-12 17:33:38 -------
Created an attachment (id=8360) [details]
4.9 prerelease 6

fixed Account switching when  selecting a QuickFolder from another account.
------- Comment #4 From Axel Grude 2018-01-13 12:32:47 -------
Changing title as this is a general change to update the Javascript of the
modern Mozilla builds.
------- Comment #5 From Axel Grude 2018-01-13 15:00:24 -------
Created an attachment (id=8361) [details]
4.9 prerelease 13

Fixed:

# drag to new subfolder
# loading and saving bookmarks / reading list items
# fixed advanced folder tab (custom CSS background & color) - apparently
Postbox still requires -moz-linear-gradient and !important. So it seems like
the CSS engine is still outdated
------- Comment #6 From Axel Grude 2018-01-15 02:18:57 -------
Created an attachment (id=8362) [details]
4.9 prerelease 16 (backwards compatible)

Did some backwards compatibility testing. This version works both on new and
old postbox builds.

I had to use the first shim path modifier without the platformversion
conditional as the old platform had problems with it. For the modern versions,
the path is simply overwritten by the next line:

content shimQF chrome://quickfolders/content/shim3/
application=postbox@postbox-inc.com 
content shimQF chrome://quickfolders/content/shim12/
application=postbox@postbox-inc.com platformversion>51
------- Comment #7 From Axel Grude 2018-02-18 02:51:06 -------
The latest version of Postbox 5.52 beta 7 was  released last Friday, with a big
surprise of removing all Addons support. This means all efforts to be
compatible with the next version of Postbox are pointless as of now. Setting
the bug to WONTFIX until further notice.

I have reached out to Postbox management asking about methods of helping our
users to maintain functionality. One possible solution (other than returning to
Addons) would be collaboration and including some of the functionality in the
main product. I am awaiting their reply.

First Last Prev Next    No search results available