Known limitations (browser extension) » History » Version 1
koszko, 09/10/2021 06:18 PM
list Hachette's known limitations
| 1 | 1 | koszko | # Known limitations |
|---|---|---|---|
| 2 | |||
| 3 | We list surprising, non-obvious issues and possible privacy shortcomings in version 0.1 of Hachette. |
||
| 4 | |||
| 5 | * Hachette currently uses short-lived cookies tu smuggle settings to its content scripts. Although partially worked around using outgoing response filtering and unlikely to happen in practice, cookies might leak and website owner could use them to learn that user's browser has Hachette running in it. We are investigating possible solutions. |
||
| 6 | * Currently, user scripts can only be injected to HTML pages. |
||
| 7 | * Currently, user scripts under Mozilla-based browsers may fail to run on pages loaded from `file://` schema. |
||
| 8 | * On some (Mozilla-based) browsers Hachette might disrupt XML preview. |
||
| 9 | * Hachette doesn't have additional features one could expect from a content blocker: |
||
| 10 | * There is currently no option to disable Service Workers while allowing normal scripts to execute. |
||
| 11 | * There is currently no option to disable loading of external/third-party fonts that are used by Google for snooping on internet users. |
||
| 12 | * There is currently no facility to anonimize queries Hachette makes to its script repositories. This means a bad admin of a [Hydrilla](https://hachettebugs.koszko.org/projects/hydrilla/wiki) instance could see the sites for which a Hachette user tried to find custom scripts. |
||
| 13 | * Hachette is still missing: |
||
| 14 | * UI Translations |
||
| 15 | * Accessiblity features |
||
| 16 | * Mobile support |
||
| 17 | * There are likely bugs. |