So I'm testing out a site on my Nexus 4, the layout when you browse to the page on mobile looks like so:
It turns out on my phone, I can scroll or move the scroll bar down, by tapping the very edge of a screen. When I try to tap the right arrow, sometimes it will think that this is an attempt to scroll and move me down the page.
My question is, is this limited to the Nexus 4 device, Android or is it the Chrome Browser? I've tried it on both a HTC and even the Nexus 10 and it isn't possible so it seems to be localised to the Nexus 4 device. More importantly, is it possible to disable this?
Although the scrollbar is not always visible in Chrome for Android, it is always present (when the page extends past the end of the screen) and will intercept touches on the edge of the screen.
As you scroll vertically on the Nexus, look for a gray bar on the right side. It is hidden when you are not scrolling, but it is still there and will still receive touches. The color of the scroll bar can also make it hard to see on certain backgrounds (such as the gray I see in your screenshot).
When I'm not touching the screen:
When I'm scrolling:
Related
I've received a bug report from a user that's quite confusing. The user reports that two lists in the app are broken. Firstly, the lists appear out of place with both a vertical and horizontal offset, with the vertical offset being greater (see picture) and secondly, when they tap on an item in the list, it opens a different item to the one they clicked. Drag-to-reorder also captures a list item further down than where they pressed. As the lists are appearing lower down than they should, my theory is that some sort of graphical glitch is showing the list out of place, but still registering and acting upon touch events as though the list were in the correct place -- resulting in the 'wrong item' part of the problem. However I'm at a loss as to what could cause a bug like this -- it's more than a layout issue because the system seems to be confused about where the list is as well! Photo below (note that cirular blob in bottom corner is just a Facebook Messenger chat head)
The bug appears on a Sony F3311 and Blu Diamond M, both running Android 6.0 / API 23, but not a Nexus 7 running Android 6.0.1. We've not encountered it on any other emulators or devices, right up to a Pixel 4a.
Update: the issue seems to be caused by using a fading edge on the lists (a ListView in one case, a RecyclerView in the other.) Removing this fixes this, but I can't work out why exactly it's happening, or even what devices attributes cause it.
I don't know if this is the right place to ask for a solution.
I have a weird bug on Samsung S9 Android 8.0:
The area for the 3 Buttons (Menu, Home, Back) is blocked for some apps, so their UI ends on the top border of this area although I set these buttons to not fixed so that I have to swipe up to see them. One of these apps is Instagram.
Also, there is the problem that the outline of some UI is shining through the current UI of each app, no matter which app is currently running. This UI is always the same. I removed all UI elements from an app I'm working on so that I have a completely white screen. Then I made a video because on screenshots the UI fragments are not visible:
https://der-magere-student.com/public/media/WIN_20210115_02_29_04_Pro.mp4
On the bottom you can see:
In more or less black: the android menu buttons (BUT NOT THE REAL ONES, the real ones are hidden until I swipe up)
In more or less white: 4 of the five toolbar button of Instagram (home (house icon), the magnifying glass, the Plus (inside the android home button), and the heart) The fifth is not visible
On the top you can see:
The right side of the WhatsApp toolbar: From right to left. The more icon, the call icon, and the video call icon
horizontally centered with a bit offset from the top display border you maybe can see a little bar. I don't know where this comes from
There is a lot more but it's not visible on the video and also not identifiable for me. But I can see something.
Does anyone know where this bug comes from? Is it known? How to fix it?
You're looking at OLED screen burn-in. It's not a software problem; it's actually wear on the screen that happens slowly over time.
The UI you're seeing at the bottom of the screen is Android's navigation buttons, which are particularly notorious for getting burned into the screen (see, for instance, this image from this article), because they're always in about the same spot. Newer versions of Android take measures to reduce the burn-in from them, but there's only so much that it's possible to do.
Try opening something that shows a white screen with the navigation buttons hidden: you'll see the same thing.
A few points to get started;
Handset: Nexus 4 (Android 4.4.4)
Browser: Chrome 36.0 (the latest update)
I am struggling to find a single article online which relates to it! Is there anybody else experiencing the same issue?
The issue; pretty much any swipe enabled horizontal slider prevents vertical scrolling. It happens on just about every website that I have tried so far.
Take, for example, the JD Sports website;
http://m.jdsports.co.uk/products/nike-air-huarache/120445
This is one of the biggest sport retailers in the UK. When I view a product page, the swipe gallery fills my entire viewport making it very difficult to scroll down to the buy button, which is hidden below the fold.
If I take a look at my favourite slider site, I can't vertically scroll when touching over a gallery;
http://kenwheeler.github.io/slick/
Is this a bug? Or do I have something wrong with my handset/browser?
I'm trying to make a textField that accepts input. My problem is, that when a user taps a textField, the input field is maximized so that it covers half the background image (the keyboard covering the other half).
The picture below shows what the background image looks like before the user taps one of the five textFields (the grey bars).
The image below and to the left shows what currently happens when I tap a textField: the input field is enlarged and completely covers the background image. What I WANT to happen, however, is what I've tried to show below and to the right: the textField is focused and the user can start writing while the background is still visible.
The app works fine on my Samsung Galaxy tablet, but for some reason I have this issue on my Nexus 5 phone only. The phone has plenty of other apps where the example to the right is what happens, so I at least know that it's possible. How do you do it?
(Was unable to find a tag for the Nexus 5)
This is a common problem. See http://forums.coronalabs.com/topic/36320-keyboard-covers-my-textfield-when-placed-on-botton-of-the-screen/ for some ideas. Some devs create their own virtual kb, see eg https://developer.coronalabs.com/category/tags/keyboard for some libs to help with this.
This is the ExtractEditText UI; you just need to add a flag to disable it. On your EditText, set the attribute:
android:imeOptions="flagNoExtractUi"
I am using this link! for cropping an image and after getting the cropped image somehow whole layout moves about 20dp upwards and hides behind the status bar (this is random behaviour i.e happens sometimes) I tried many things to fix this problem but couldn't get to the solution, mainly because I dont know what is causing the problem.
This is a device specific problem, occurs occasionally in galaxy s and htc desire but frequently on samsung Ace. I tested app on samsung note and htc desire HD it works fine no such problem in these devices.
There is one more thing I should mention here that is: when layout hides under the status bar if I popup the keyboard by clicking on textfield layout gets back to normal i.e hidden area gets visible again. I cannot attach the image but found similar question Android - Status bar hides part of view sometimes exactly this is the behaviour of my layout.
Note:Recently i found out that camera activity is causing the layout to move upwards. To verify this start camera in samsung Galaxy Ace and just press back and note the layout movement in icons of home screen.
I have fixed the problem by using crop method inside the camera activity check this Set Camera Size - Parameters vs Intent? last answer of the post helped me to solve the issue.