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

Menu Option Disappears Completely On Certain Screen Size #3880

Merged
merged 12 commits into from
Dec 8, 2024

Conversation

ericji1326
Copy link
Contributor

Fixes #3850

Copy link

netlify bot commented Nov 23, 2024

Deploy Preview for actualbudget ready!

Name Link
🔨 Latest commit ce4aed4
🔍 Latest deploy log https://app.netlify.com/sites/actualbudget/deploys/67549abcca35e100089d171a
😎 Deploy Preview https://deploy-preview-3880.demo.actualbudget.org
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

github-actions bot commented Nov 23, 2024

Bundle Stats — desktop-client

Hey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle.

As this PR is updated, I'll keep you updated on how the bundle size is impacted.

Total

Files count Total bundle size % Changed
10 5.45 MB → 5.45 MB (+237 B) +0.00%
Changeset
File Δ Size
src/components/accounts/Header.tsx 📈 +237 B (+1.26%) 18.34 kB → 18.58 kB
View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

Asset File Size % Changed
static/js/wide.js 241.3 kB → 241.53 kB (+237 B) +0.10%

Smaller

No assets were smaller

Unchanged

Asset File Size % Changed
static/js/indexeddb-main-thread-worker-e59fee74.js 13.5 kB 0%
static/js/useAccountPreviewTransactions.js 1.63 kB 0%
static/js/AppliedFilters.js 21.32 kB 0%
static/js/workbox-window.prod.es5.js 5.69 kB 0%
static/js/resize-observer.js 18.37 kB 0%
static/js/narrow.js 82.96 kB 0%
static/js/BackgroundImage.js 122.29 kB 0%
static/js/ReportRouter.js 1.52 MB 0%
static/js/index.js 3.44 MB 0%

Copy link
Contributor

github-actions bot commented Nov 23, 2024

Bundle Stats — loot-core

Hey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle.

As this PR is updated, I'll keep you updated on how the bundle size is impacted.

Total

Files count Total bundle size % Changed
1 1.32 MB 0%

Changeset

No files were changed

View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

No assets were bigger

Smaller

No assets were smaller

Unchanged

Asset File Size % Changed
kcab.worker.js 1.32 MB 0%

@ericji1326 ericji1326 changed the title [WIP] Menu Option Disappears Completely On Certain Screen Size Menu Option Disappears Completely On Certain Screen Size Nov 25, 2024
Copy link
Contributor

coderabbitai bot commented Nov 25, 2024

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/desktop-client/src/components/accounts/Header.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-eslint-plugin".

(The package "eslint-plugin-eslint-plugin" was not found when loaded as a Node module from the directory "/packages/eslint-plugin-actual".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-eslint-plugin@latest --save-dev

The plugin "eslint-plugin-eslint-plugin" was referenced from the config file in "packages/eslint-plugin-actual/.eslintrc.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

Walkthrough

The pull request introduces changes to the AccountHeader component within the Header.tsx file. The primary modification involves adjusting the styling of several <View> components by applying the flex: '0 0 auto' property. This change is intended to influence the layout behavior of these components in relation to their parent containers. Importantly, the logic governing button rendering and user interactions remains intact, with no modifications made to the functionality concerning reconciliation, transaction management, or filtering. The component continues to utilize hooks for state management and hotkey handling without any changes to its props or core logic. Overall, the updates focus solely on layout adjustments without adding new features or significantly altering existing behaviors.

Assessment against linked issues

Objective Addressed Explanation
Fix the menu option disappearance on certain screen sizes (Issue #3850) It is unclear if the layout changes resolve the issue.

Possibly related PRs

Suggested labels

:sparkles: Merged

Suggested reviewers

  • matt-fidd
  • youngcw

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between c30f251 and a138b6f.

📒 Files selected for processing (1)
  • packages/desktop-client/src/components/accounts/Header.tsx (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/desktop-client/src/components/accounts/Header.tsx

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
Contributor

@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: 0

🧹 Outside diff range and nitpick comments (1)
packages/desktop-client/index.html (1)

112-114: Consider a more targeted CSS reset approach.

While all: unset will solve the immediate issue, it might be more maintainable to identify and reset only the specific properties causing the menu visibility problem (e.g., opacity, visibility, display, etc.).

 .view-reset {
-  all: unset;
+  /* Reset only specific properties */
+  opacity: 1 !important;
+  visibility: visible !important;
+  display: flex !important;
+  position: static !important;
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between c25e3d4 and f3d4255.

⛔ Files ignored due to path filters (1)
  • upcoming-release-notes/3880.md is excluded by !**/*.md
📒 Files selected for processing (2)
  • packages/desktop-client/index.html (1 hunks)
  • packages/desktop-client/src/components/accounts/Header.tsx (3 hunks)
✅ Files skipped from review due to trivial changes (1)
  • packages/desktop-client/src/components/accounts/Header.tsx
🔇 Additional comments (1)
packages/desktop-client/index.html (1)

112-114: LGTM! Verify across all affected screen sizes.

The addition of .view-reset with all: unset should help resolve the menu visibility issue by removing inherited styles that may be causing the problem.

✅ Verification successful

The view-reset class is appropriately used to fix menu visibility

The verification shows that the view-reset class is correctly implemented in Header.tsx specifically around the MenuButton components, which aligns with fixing the menu dropdown visibility issue. The class is applied in three menu-related contexts within the account header, making it a targeted solution rather than an overly aggressive reset.

  • Applied to account menu view containers in packages/desktop-client/src/components/accounts/Header.tsx
  • Properly defined in packages/desktop-client/index.html with all: unset
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Find all components using the new view-reset class to ensure proper application
rg -l "view-reset" --type tsx --type jsx

Length of output: 68


Script:

#!/bin/bash
# Search for view-reset class usage in all files, including HTML, CSS, and JavaScript/TypeScript
rg "view-reset" -l

# Also check for any CSS files specifically
fd -e css -e scss

Length of output: 232


Script:

#!/bin/bash
# Let's see how the view-reset class is being used in Header.tsx
rg "view-reset" packages/desktop-client/src/components/accounts/Header.tsx -B 2 -A 2

# Also check the context in index.html to understand the full implementation
rg "view-reset" packages/desktop-client/index.html -B 2 -A 2

Length of output: 618

Copy link
Contributor

@jfdoming jfdoming left a comment

Choose a reason for hiding this comment

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

Thanks for the PR! We generally don't use raw CSS where possible. Instead, View has a style prop that works similarly.

@ericji1326
Copy link
Contributor Author

Thanks for the PR! We generally don't use raw CSS where possible. Instead, View has a style prop that works similarly.

I'll get a fix up ASAP

@ericji1326 ericji1326 requested a review from jfdoming December 7, 2024 00:05
@ericji1326
Copy link
Contributor Author

Hey @jfdoming, I have made the change as you requested! Let me know what you think! 😄

Copy link
Contributor

@jfdoming jfdoming left a comment

Choose a reason for hiding this comment

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

Thanks! Looks good. If you have time, would be nice to add a screenshot test for this—you can follow this template. Otherwise happy to merge as is

@ericji1326
Copy link
Contributor Author

Thanks! Looks good. If you have time, would be nice to add a screenshot test for this—you can follow this template. Otherwise happy to merge as is

Hey @jfdoming! Thanks for the PR approval! I think I'm pretty low on time due to exams. May I get this just merged as is?

Thanks!

@jfdoming jfdoming merged commit e4b40fb into actualbudget:master Dec 8, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Menu Option Disappears Completely On Certain Screen Size
2 participants