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

Fix Lock Screen UI issues #399

Merged
merged 2 commits into from
Jan 17, 2022
Merged

Fix Lock Screen UI issues #399

merged 2 commits into from
Jan 17, 2022

Conversation

samsymons
Copy link
Collaborator

Accent Color Task/Issue URL: https://app.asana.com/0/1199178362774117/1201574532063637/f
Font Weight Task/Issue URL: https://app.asana.com/0/0/1201528988008230/f
CC: @brindy

Description:

This PR attempts to fix two issues reported with the lock screen: the font weight was too thin for some people, and occasionally the continue button would not have the system accent colour. I haven't been able to reproduce either of these issues, so I've attempted to speculatively fix them with the following:

  • For the accent color, the key equivalent is now being set in viewDidLoad as a backup. I don't know what would cause this to get lost from the Storyboard, but I don't have any other ideas here at the moment.
  • For the font weight, I realized that I had use the custom font option to SFPro, instead of using the System options. This worked fine for me, but I can see how it would trip the system up. This has been changed to use the default font options, customizing weight and size as appropriate.

Steps to test this PR:

  1. Run through onboarding, check that the title fonts are bold and that the Continue button has an accent color

Testing checklist:

  • Test with Release configuration

Internal references:

Software Engineering Expectations
Technical Design Template
When ready for review, remember to post the PR in MM

Comment on lines -163 to -165
<string key="keyEquivalent" base64-UTF8="YES">
DQ
</string>
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Not sure why this got removed, it's still set in the Storyboard.

@mallexxx mallexxx self-assigned this Jan 17, 2022
Copy link
Collaborator

@mallexxx mallexxx left a comment

Choose a reason for hiding this comment

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

Looks good to me, confirming font issues fixed; the button is highlighted
There's still a way to get the button not highlighted: after minimizing browser window and restoring it the button will be unhighlighted

@mallexxx mallexxx assigned samsymons and unassigned mallexxx Jan 17, 2022
@brindy brindy merged commit fc143da into develop Jan 17, 2022
@brindy brindy deleted the sam/fix-lock-screen-ui-issues branch January 17, 2022 11:16
samsymons added a commit that referenced this pull request Feb 18, 2022
# By Alexey Martemyanov (20) and others
# Via Tomas Strba (2) and others
* develop: (63 commits)
  Tweaks of suggestions and autocomplete (#403)
  Bump privacy dashboard to latest version (#409)
  Point to the latest BrowserServicesKit branch. (#414)
  Move embedded TDS from BSK to platform repo (#412)
  Image of shield with dot replaced (#410)
  Expand Fireproofing to include Local Storage and IndexedDB (#408)
  Version 0.18.5
  support privacy config for clickToLoad (#407)
  Automatically select available login (#405)
  initial FB Click to Load (WIP) (#329)
  onboarding updates (#398)
  Version 0.18.4
  Configuration of Sparkle - Setting SUAllowsAutomaticUpdates to NO (#404)
  Hide downloads button if the popover is opened/closed manually (#397)
  Textfield of the homepage is empty and unfocused right after switching to the homepage (#400)
  Remove navigatorCredentials (#392)
  Remove GPC header if it exists when not needed (#366)
  Version 0.18.3
  Fireproofing encrypted storage (#332)
  Fix Lock Screen UI issues (#399)
  ...

# Conflicts:
#	DuckDuckGo.xcodeproj/project.pbxproj
#	DuckDuckGo/Crash Reports/Model/CrashReportSender.swift
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.

3 participants