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

Implement Find in Page #947

Merged
merged 1 commit into from
Sep 5, 2023
Merged

Implement Find in Page #947

merged 1 commit into from
Sep 5, 2023

Conversation

HollowMan6
Copy link
Collaborator

Resolve #929

Translations are copied from Chromium. https://github.com/chromium/chromium/blob/main/components/strings/components_strings_en-GB.xtb

translation id: 3495081129428749620

com igalia wolvic-20230904-003810

com igalia wolvic-20230904-003832

Copy link
Member

@svillar svillar left a comment

Choose a reason for hiding this comment

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

This is excellent!

There is some more work to be done though so that we could eventually use it also with the Chromium backend though. We cannot break the engine agnostic approach of wolvic's architecture.

Copy link
Member

@javifernandez javifernandez left a comment

Choose a reason for hiding this comment

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

Awesome !

Copy link
Member

@svillar svillar left a comment

Choose a reason for hiding this comment

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

Looking great, just some minor comments

Copy link
Member

@svillar svillar left a comment

Choose a reason for hiding this comment

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

BTW I forgot to mention, please add some placeholders or empty implementations for the chromium backend, otherwise this patch would break the chromium build

@svillar
Copy link
Member

svillar commented Sep 5, 2023

Another comment, this is kind of a request that you could ignore if it involves a lot of work. I thought it'd be nice to show the prev/next buttons as inactive/hidden whenever either there is no result or there is no text to search yet. I guess this can be done in the xml by adding a condition on the number of results...

Signed-off-by: Songlin Jiang <sjiang@igalia.com>
@HollowMan6
Copy link
Collaborator Author

BTW I forgot to mention, please add some placeholders or empty implementations for the chromium backend, otherwise this patch would break the chromium build

Add the getSessionFinder method override in chromium SessionImpl, hopefully, that will make the chromium backend build. But I don't have a test environment for that so I'm not 100% sure.

Another comment, this is kind of a request that you could ignore if it involves a lot of work. I thought it'd be nice to show the prev/next buttons as inactive/hidden whenever either there is no result or there is no text to search yet. I guess this can be done in the xml by adding a condition on the number of results...

This should be done on the Mozilla Android component side (UI-related), maybe we can open an issue for feature requests there. https://github.com/mozilla-mobile/firefox-android/tree/main/android-components/components/feature/findinpage

@svillar svillar merged commit 5a1234d into main Sep 5, 2023
7 checks passed
@svillar svillar deleted the findInPage branch September 5, 2023 13:39
@HollowMan6
Copy link
Collaborator Author

Another comment, this is kind of a request that you could ignore if it involves a lot of work. I thought it'd be nice to show the prev/next buttons as inactive/hidden whenever either there is no result or there is no text to search yet. I guess this can be done in the xml by adding a condition on the number of results...

This should be done on the Mozilla Android component side (UI-related), maybe we can open an issue for feature requests there. https://github.com/mozilla-mobile/firefox-android/tree/main/android-components/components/feature/findinpage

Submitted a feature request at: https://connect.mozilla.org/t5/ideas/find-in-page-for-firefox-android-hide-inactivate-previous-amp/idi-p/38778

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.

Search in page
3 participants