Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better Clear Recent History Dialog #2272

Closed
wants to merge 1 commit into from
Closed

Conversation

gunir
Copy link
Contributor

@gunir gunir commented Oct 22, 2024

Better Clear Recent History Dialog

image

Clearing Offline Website Data is useful, because Zen will get slower as it accumulates more Offline Website Data (localStorage and indexedDB), clearing this returns back good performance, and there's websites that spam Offline Website Data to GBs, causing slows down to Zen so this is good for maintaining Zen for performance.

Summary by CodeRabbit

  • New Features
    • Introduced an option to enable the old clear history dialog for improved privacy management.
    • Added experimental support for the Kyber encryption algorithm in TLS and HTTP/3 protocols, enhancing security features.

Better Clear Recent History Dialog

Signed-off-by: Gunir <[email protected]>
@gunir gunir requested a review from mr-cheff as a code owner October 22, 2024 06:11
Copy link

coderabbitai bot commented Oct 22, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request involve modifications to the configuration settings within the zen-browser.js file. It introduces three new preferences: one for enabling the old clear history dialog and two related to the experimental implementation of the Kyber encryption algorithm in TLS and HTTP/3 protocols. The existing preferences remain unchanged, maintaining the overall structure of the configuration.

Changes

File Path Change Summary
src/browser/app/profile/zen-browser.js - Added preference: privacy.sanitize.useOldClearHistoryDialog (true)
- Added preference: security.tls.enable_kyber (true)
- Added preference: network.http.http3.enable_kyber (true)

Possibly related PRs

Suggested reviewers

  • mauro-balades

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range comments (1)
src/browser/app/profile/zen-browser.js (1)

Line range hint 243-249: Update PR description to include all changes.

While the change to the Clear Recent History Dialog aligns with the PR objectives, the addition of Kyber-related experimental features was not mentioned in the PR description. Consider updating the PR description to include:

  1. The rationale for enabling the old Clear Recent History Dialog.
  2. An explanation of the Kyber-related changes, their potential benefits, and their experimental nature.
  3. Any known risks or considerations for enabling these experimental features.

This will provide better context for reviewers and future reference.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between 065e825 and 9fa346f.

📒 Files selected for processing (1)
  • src/browser/app/profile/zen-browser.js (1 hunks)
🧰 Additional context used
🔇 Additional comments (2)
src/browser/app/profile/zen-browser.js (2)

Line range hint 249-249: Group Kyber-related preferences and provide context.

This preference is closely related to the previous Kyber TLS preference. Consider grouping them together and adding a comment explaining the relationship between Kyber in TLS and HTTP/3.

Please address the following:

  1. Are there any interdependencies between the TLS and HTTP/3 Kyber implementations?
  2. Has this been tested in conjunction with the TLS implementation?
  3. Are there any known issues or limitations when enabling Kyber for both TLS and HTTP/3?
#!/bin/bash
# Check for any existing HTTP/3 Kyber-related code or comments
rg -i "http.?3.*kyber" --type js

248-248: Verify the implications of enabling Kyber in TLS.

While enabling Kyber, a post-quantum cryptography algorithm, could enhance future security, it's important to ensure this experimental feature has been thoroughly tested and is ready for general use.

Please provide more information on:

  1. The current state of Kyber implementation in TLS.
  2. Any performance implications or compatibility issues.
  3. Whether this should be enabled by default or made configurable by users.

src/browser/app/profile/zen-browser.js Show resolved Hide resolved
@mr-cheff mr-cheff closed this Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants