Releases: Privacy-Managers/Privacy-Manager
Manifest V3
Chrome is deprecating Manifest v2 in favor of Manifest V3. Current release ensures the Privacy Manager compatibility with the new Browser Extensions standard.
Changes
- #96 - Load single background script.
- #102 - Manifest v3 compatibility:
- Updated manifest.json to v3.
- Stop using DOM API in the service worker.
- Store network requests in the local storage and clear on browser start over storing in background page, which is no more option with Manifest V3.
- Use declarativeNetRequest API over WebRequest for UA blocking.
- #100 - Updated outdated packages.
- Fixed flaky e2e tests caused by changes above.
- 8ea5909 - Few translation updates.
German translations
Thanks to Andy K. Privacy Manager is now also available in German.
Bug fixes release
Thanks to @alexdevero another annoying bug has been identified which caused removed cookies to get whitelisted. Current release fixes that bug and adds title attribute to whitelisting buttons.
Bug fixes release
@alexdevero noticed an annoying regression bug, which tests failed to fetch. Current release fixes that bug and makes extension versioning in sync with npm package.
Bug fixes release
A followup bug fixes release after big rewrite.
this release contains only changes in pm-components repository:
- Added polyfill for constructing stylesheets to support Web Components on the browser that don't yet support constructing stylesheets
- Fixed constant opening information dialog of pm-toggle when dialog is closed using enter on close button
- Fixed pm-tab-panel is being hidden when clicked outside of the tab
Complete rewrite
Main changes
- Moved repository into Privacy Managers organization.
- Switched to using web components instead of old monolith.
- Replaced old codebase with modern JavaScript features.
- Replace Chrome.* API with Browser.* API Polyfill (First step towards Firefox browser support).
- Use webpack as build tool.
- Modularization of JS files.
- Automated puppeteer tests for web components and Privacy Manager.
- and more...
Related Issues
#2 - Switch to ES6
#40 - Start using web components
#43 - Implement tests
#45 - Promisify the Chrome extensions API
#48 - Create a separate github organization for Privacy Manager
#49 - turnSwitchesOff and checkSettingState
#50 - Stop using addSettingItem callback as a listener
#51 - Create test for collectHeaders, Block user agent and ActiveTab toggles
#52 - Start using pm-tab-panel web component
#53 - Replace Cookie table with pm-table component
#54 - Create tests for cookie table component
#55 - When deleting cookies and domains handle whitelisting in storage
#57 - Use pm-dialog for adding cookies
#58 - Use pm-dialog instead of prompt window for the settings list descriptions
#59 - Updating a cookie with an expired expiration date throws an error
#60 - Add tests for Adding and setting cookies using pm-dialog
#61 - Use Add instead of Update in Cookie dialog
#62 - Remove delete button from the Add cookie dialog
#63 - Session cookies are not supported
#67 - Use pm-dialog for Cookie deletion
#68 - Use pm-table instead of requests table in the networks tab
#69 - Create test for pm-table in network tab
#70 - "Cookie is updated using 'edit cookies' dialog" test keep failing
#71 - Open in incognito button doesn't work
#72 - Download JSON formatted network data
#73 - Move storage listener into addStorageToggle
#74 - Subitem whitelist title is not being added
#75 - Use Message passing instead of getBackgroundPage()
#77 - Add test for data removal
#78 - Error in the background page
Whitelist cookies from clearing up
Updated the design
Fixed Broken Build for Chrome Dev on Windows
- #24 - Wrap storage API in function, instead of assigning setters and getters to the variable