Skip to content

Gesturefy v4 (Port to manifest v3)#715

Draft
Robbendebiene wants to merge 83 commits into
masterfrom
port-to-manifest-v3
Draft

Gesturefy v4 (Port to manifest v3)#715
Robbendebiene wants to merge 83 commits into
masterfrom
port-to-manifest-v3

Conversation

@Robbendebiene

@Robbendebiene Robbendebiene commented May 15, 2024

Copy link
Copy Markdown
Owner

Requirements:

Firefox will provide global user controls for site access per add-on.

See:
-  https://bugzilla.mozilla.org/show_bug.cgi?id=1497075
- https://bugzilla.mozilla.org/show_bug.cgi?id=1711787

Removing this option from Gesturefy reduces the amount of code that needs to be maintained. It's also more performant to exclude the entire content script from running than doing content script side checks.
Last but not least exclusions have always been a power feature that never really fit into Gesturefy from a design/UI standpoint.
Also resolves #542
The reason behind this change is that content scripts no longer get access to extension files unless they are declared as a web_accessible_resource. I'm against doing so for privacy reasons. At least in theory websites could use web_accessible_resource for fingerprinting.

Some additional information can be found here: https://bugzilla.mozilla.org/show_bug.cgi?id=1578405
Previously all unmatching gestures were hidden including the "new gesture button".
This could lead to confusion that gestures are missing/disappeared and no new gestures can be added.
The new concept only unhighlights unmatching gestures which still provides an overview over all gestures, indicates that some sort of filtering is active and allows adding new gestures. The only downside is that users have to scan the screen (on smaller screens even need to scroll) in order to find the results.
Historical moment. I hope you're all proud of me,
that these actions finally leave the "about" page.
Also add the ability to backup/restore the config to/from the cloud
It now works with urls instead of tabs and globs instead of regex
The latter ensures backwards compatibility and allows a potential change to the dynamic content script API in the future
So far there is now way to do this via browser functionality, or dynamic content script registration.
See also w3c/webextensions#653
@Robbendebiene Robbendebiene linked an issue May 5, 2026 that may be closed by this pull request
- reduces parsing and memory cost
- prevents Flash of Unstyled Content (FOUC)
- Remove obsolete config manager
- Split defaults.json into settings and gestures
- Also drops the legacy gesture reversal in code
- Reverse default gestures
- Migration code should reverse user gestures
- remove the custom search engine URL setting
- Reasoning: more easily compensate the removal of the openEmptySearch setting
- Introduce a new "target" setting where users can select where to open the content
- Show other settings depending on the selected target (conditional settings)
- Add new label property to commands allowing them to adjust their label based on their settings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant