fenix
fenix copied to clipboard
Closes #26116: use new viewholders on history screen
Using all fancy new viewholders.
Main features: filtering of remote/local items inside HistoryDataSource
, calculating headers to remove when items are being removed inside HistoryAdapter
, tracking of the empty state in HistoryAdapter
.
Comments on tests are especially welcomed.
Pull Request checklist
- [x] 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.
QA
- [x] QA Needed
To download an APK when reviewing a PR (after all CI tasks finished running):
- Click on
Checks
at the top of the PR page. - Click on the
firefoxci-taskcluster
group on the left to expand all tasks. - Click on the
build-debug
task. - Click on
View task in Taskcluster
in the newDETAILS
section. - The APK links should be on the right side of the screen, named for each CPU architecture.
GitHub Automation
Fixes #26116
This pull request has conflicts when rebasing. Could you fix it @mavduevskiy? 🙏
@MozillaNoah Hey, thank you for taking your time! As a non native English speaker, really appreciate help with grammar/styling. Fixed!
@rocketsroger Thanks for the review! I followed your comments, had question just about one thing.
Played around with strings and html tags, smth like
<string name="history_sign_in_create_account"><u>Or create a Firefox account to start syncing</u></string>
would be displayed as. But multiple translations already used the CDATA
tag. Should I leave it as it is? Remove the tag from the default language only or also adjust the existing translations?
As discussed let's try:
- passing around headers to remove to HistoryView
- simplify the function
calculateTimeGroupsToRemove
... Should I leave it as it is? Remove the tag from the default language only or also adjust the existing translations?
In this case I think we should update it. (by creating a new _2 string) Since we know a good solution that will avoid a function call every time.
This pull request has conflicts when rebasing. Could you fix it @mavduevskiy? 🙏
Leaving this for time being. Redesign is still planned, but priorities are different for now.