-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[$500] DEV: Logo Display Issue on Small Screens #26330
Comments
Triggered auto assignment to @tjferriss ( |
Bug0 Triage Checklist (Main S/O)
|
Proposalby @ahmdshrif Please re-state the problem that we are trying to solve in this issue.The logo on the splash screen is not being displayed correctly on small screens. Only around 1/4 of the logo is visible, indicating that the logo is being cropped. What is the root cause of that problem?The root cause of the problem is that the SVG image of the logo does not have a viewBox attribute. The viewBox attribute defines the coordinate space of the SVG image. When you resize the image, the viewBox attribute is used to scale the image proportionally. Without a viewBox attribute, the image is simply cropped to fit the new size. What changes do you think we should make in order to solve the problem?To fix the problem, we need to add a viewBox attribute to the SVG image. The viewBox attribute should be set to the same dimensions as the image. For example, if the image is 80 pixels wide and 80 pixels high, the viewBox attribute would be set to:
This will ensure that the image is resized proportionally when it is resized. What alternative solutions did you explore? (Optional)We could also use CSS to scale the image proportionally. However, this would be less efficient than using a viewBox attribute. |
Please fetch latest main. It was fixed already. |
@c3024 yes looks like you fixed it in this PR but I can also reproduce it in ad-hoc Here is how to reproduce it:-
Screen.Recording.2023-09-03.at.11.25.15.PM.movand to fix that we will add viewBox="0 0 80 80" to new-expensify-adhoc.svg Screen.Recording.2023-09-03.at.11.34.02.PM.movcc: @tjferriss |
@tjferriss Huh... This is 4 days overdue. Who can take care of this? |
I don't have a dev environment to test. I'm asking for clarification on whether we'd fix this. |
Job added to Upwork: https://www.upwork.com/jobs/~01229788941fa6e972 |
Current assignee @tjferriss is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 ( |
@abdulrahuman5196 can you reproduce this one on dev? |
@tjferriss, @abdulrahuman5196 Eep! 4 days overdue now. Issues have feelings too... |
@tjferriss, @abdulrahuman5196 Eep! 4 days overdue now. Issues have feelings too... |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@abdulrahuman5196 friendly bump... is this reproducible on dev? |
@tjferriss @abdulrahuman5196 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Testing on dev now |
@tjferriss I am not able to repro the issue in Dev as well as adhoc builds. |
@abdulrahuman5196 can you share the ad-hoc build that you can't repro on it? Screen.Recording.2023-09-15.at.11.25.48.PM.mov |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
1- Open the web app in development mode.
2- Access the app using a device or browser with a small screen size (mobile size).
3- Observe the logo display on the splash screen.
Expected Result:
The logo on the splash screen should be fully displayed, without any cropping or misalignment, regardless of the screen size.
Actual Result:
Only around 1/4 of the logo is visible on the splash screen, indicating that the logo is not being displayed correctly on small screens.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number:
Reproducible in staging?: dev
Reproducible in production?: dev
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screen.Recording.2023-08-21.at.10.01.02.AM.mov
Expensify/Expensify Issue URL:
Issue reported by: @ahmdshrif
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692601767190289
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: