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

Merge latest mozilla code to fork #216

Merged
merged 73 commits into from Oct 11, 2020

Conversation

abhijitvalluri
Copy link
Collaborator

The latest mozilla code has added a "grid tab tray" layout taking code from my work here. I had to get rid of most of it as it duplicates our feature and does it in a different way, and the layout is in my opinion not as great.

Pull Request checklist

  • Tests: This PR includes thorough tests or an explanation of why it does not
  • Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not
  • Accessibility: The code in this PR follows accessibility best practices or does not include any user facing features. In addition, it includes a screenshot of a successful accessibility scan to ensure no new defects are added to the product.

To download an APK when reviewing a PR:

The PR runs an Android build check (run-build) that builds a forkRelease variant of the app. If it succeeds, then we upload the apks (signed with debug keys) via Github actions. We also generate a comment with some instructions and a link to help you find the downloads. You can also follow the instructions below:

  1. Click Details next to "run-build (pull_request_target)" after it finishes with a green checkmark.
  2. Click the "Artifacts" drop-down near the top right of the page.
  3. The apk links should be present in the drop-down menu. You can click on the suitable CPU architecture to download a zipped apk file.
  4. Unzip the file and install the apk.

mcarare and others added 30 commits October 2, 2020 20:46
…llection button.

Check now considers selected tab tray mode.
…n until something has been changed

set save button state by calling invalidateOptionsMenu, causing onPrepareOptionsMenu to be called which will enable/disable the save button depending on if changes have been made or not
This is more correct, faster, and results in less copy-paste duplication
than the current behavior:
  homeScreen { }.dismissOnboarding()

Which opens settings to dismiss onboarding.
Before it used to output the violations all one one line. Now it looks
like:
```
MozillaStrictModeSuppression:
    'import mozilla.components.support.ktx.android.os.resetAfter' at
(17,1) in /StrictModeManager.kt
    Please use `components.strictMode.resetAfter` instead because it has
performance improvements and additional code to monitor for performance
regressions.

MozillaStrictModeSuppression:
    'setThreadPolicy(threadPolicy.build())' at (56,24) in
/StrictModeManager.kt
    Please use `components.strictMode.resetAfter` instead because it has
performance improvements and additional code to monitor for performance
regressions.

MozillaStrictModeSuppression:
    'setVmPolicy(builder.build())' at (71,24) in /StrictModeManager.kt
    NOT YET IMPLEMENTED: please consult the perf team about
implementing`StrictModeManager.resetAfter`: we want to understand the
performance implications of suppressing setVmPolicy before allowing it.
```
Running locally, I get the same error: I think that there legitimately
was an reduction in the number of StrictMode suppressions on start up.
This changes the error highlighting from being the entire contents of
<Button ...> to just the first line of <Button>.
gabrielluong and others added 26 commits October 8, 2020 12:50
… Desktop Bookmarks folder (mozilla-mobile#15649)

For mozilla-mobile#15497: Remove and disable the three dot menu button
…le (mozilla-mobile#15667)

For mozilla-mobile#15402: Hide ETP pop-up when top or bottom toolbar is not visible
Margins were also adjusted to maintain relative placements.
…logic of startup time for cold, warm, and hot startup types.
@github-actions
Copy link

Download the built apks

You can download the apks built by Github actions after the CI checks pass.
Please go to the checks page for this PR to find the zipped apk files under the artifacts drop-down, as seen in the example screenshot below.

Note that you will have to click on the "Android build PR" tab on the left side to see the artifacts.

@abhijitvalluri
Copy link
Collaborator Author

The failing build is just signing that is failing. Which is concerning, as it may mean our CI signing process is flaky or is not working again! The code itself is fine, so I will merge.

@abhijitvalluri abhijitvalluri merged commit dca8a2f into fork-maintainers:fork Oct 11, 2020
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.

None yet