evan-king / drag-scroll Goto Github PK

In order to gain familiarity and make the project more maintainable, the core module needs to be refactored using a (pragmatically) functional approach with separation into independent components where practical.

Particular focus will be given to isolating use of legacy APIs to adapter components, which should ease the introduction of broader compatibility.

In recent versions of Pale Moon, rocker gesture (right to left) from Fire Gesture set to close tab results in an erroneous click on the tab left in focus after tab closure. (Grab and Drag is set to support scrolling on right click.)

This may be a bad interaction with Grab and Drag or caused by a common browser bug/behavior change, independently affecting both addons (see #2). Need to run basic troubleshooting procedures to isolate this issue, and then depending on results implement any fix possible from within this project.

Not sure what if anything is feasible here, but options should be explored and at the very least internal logic should be unit tested and test driven.

Will be using Mocha and Chai.expect, borrowing approach/CI from other personal projects.

Current plans are for the implementation to support Pale Moon first and Firefox secondarily (only for versions retaining support for legacy addons, for now at least).

Publishing will likely only target Pale Moon by self-hosting the addon and getting it indexed in Pale Moon. (No current plans to submit to AMO at all.)

Broader compatibility and publishing may be supported if contributors can be found willing to spearhead that effort (post-refactoring).

First step is to automate local XPI builds, followed by setting up a CI workflow around it using TravisCI (also see #5). Then once a stable baseline addon is established, see if a CI-generated artifact can be the source for release candidates.

Second, establish and document a release process. We should validate coherent version tagging (i.e. version in code must exclusively match tagged version), and need to generate additional artifacts to support self-hosting the addon. Static hosting setup details need not be generated, but should be documented (possibly anonymizing some details).

Not to be done until working local builds are available, or unless parallel efforts are discovered.

Not experiencing this personally but I've heard reports of it for current Grab and Drag users on recent Firefox versions (particularly on it's Mozilla addon page).

If you are encountering this issue, please share any details you can here.

Occurring in Pale Moon Version: 27.4.1 (64-bit) on Windows 10. Appears to only occur on drag clicks that begin and end outside content areas (away from text/images) but not limited to any discernable high-level DOM scopes.