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

Partial display of the table dedicated to the “Settings” option of the search page in “Mobile site” display mode #4265

Closed
Ricky-Tigg opened this issue Mar 7, 2024 · 4 comments

Comments

@Ricky-Tigg
Copy link

Describe the bug

v.: 5.192.2 | screen resolution: 1920 x 1200 | screen size (mm): 218 x 136

Hello. While the Mobile site display mode option is selected, and the search page is viewed along the vertical axis of the screen, the display of the table dedicated to the Settings option of the search page is partial.

duckduckgo_android_vertical_axis_view

How to Reproduce

  1. Select the Mobile site option.
  2. Display the search page along the vertical axis of the screen by rotating the screen accordingly; this requires Android's Auto-rotate option to be selected.
  3. Click the Settings option which is found in the search page.

Expected behavior

The table dedicated to the Settings option that is found in the search page must be displayed in its entirety. See the case illustrated in this image, which was taken while the search page was viewed along the horizontal axis of the screen.

duckduckgo_android_horizontal_axis_view

Environment

No response

Copy link
Contributor

github-actions bot commented Mar 7, 2024

Thank you for opening an Issue in our Repository.
The issue has been forwarded to the team and we'll follow up as soon as we have time to investigate.
As stated in our Contribution Guidelines, requests for feedback should be addressed via the Feedback section in the Android app.

@CDRussell
Copy link
Member

Hi @Ricky-Tigg, thanks for taking the time to report.

I think I need a little more information to fully understand this; I couldn't reproduce the issue but there's also a few terms you've used where I might not be understanding them correctly.

To give me more clarity on the problem and steps to reproduce:

  1. which device are you using?
  2. when you say "Mobile Site", do you mean the setting in the app itself? (the one in the overflow menu)
  3. when you say "Display the search page along the vertical axis of the screen", do you mean to hold it in portrait mode?

I think the ultimate answer here is likely that if there's an issue it's with the search results page itself and not the Android app. If that's the case, I can pass that feedback on internally once I understand it more.

@Ricky-Tigg
Copy link
Author

Vocabulary

  • portrait | No geometric description deriving from it can be found anywhere.
  • overflow menu | No clue to guess you.

Fortunately there are references that leave no room for ambiguity, unlike ours.

  • Let us therefore consider the letter l, in lower-case, as being representative of the device presented from the front, which is therefore where the screen is located. The longest side is oriented in the vertical direction. That is all.
  • The Mobile site and Desktop site options alternate with each other. Which options are part of the panel of this application, which when manually invoked via the symbol with the three superimposed dots, appears on the right border of the window.

Having since tested the behaviour of the said search page in the Firefox for Android 124 beta browser, I was able to observe the said phenomenon, which allows us to conclude that this is not an issue specific to Duckduckgo for Android.

At last, my tests are conducted while the Font size option that is as an Android setting, is left at its default value, which is normal. It could have be meant to have global effect since it affects the size of text and web elements in Duckduckgo for Android.

P.S. From the above, we can deduce that the information that follows will be of no use as to the issue; device: Huawei Mediapad T5.

@CDRussell
Copy link
Member

Thanks @Ricky-Tigg.

conclude that this is not an issue specific to Duckduckgo for Android

Agreed. I will close this task on that basis, and share the feedback internally with the right team. Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants