my website (www.primapaginaonline.it) has a problem when browsed from a smartphone (at least from android, on a Nokia Lumia with Internet Explorer looks fine). It has big empty space at right and at bottom of the page. I can't understand why it looks like that.
Any help?
Thanks
Your website have some css issues
in following elements listed below:
document.getElementById("footerwrapper1") --> Responsible for Horizontal Scroll
document.getElementsByClassName('secondary') --> Responsible for Vertical Scroll
by changing css property display:none to both of them,
Unnecessary scroll is removed.
Related
I have had feedback from Pixel 3/4 users that the bottom of the screen on this app is cut off, obscuring buttons and possibly other controls that the user requires.
This has only started happening on Android 10. The app contains both Xamarin.Android axml and Xamarin.Forms xaml layouts for the views (the particular page that you are viewing below is Xamarin.Forms).
I don't want to set margins, paddings, gravity or such like on the entire app as obviously that would impact non Android 10/Pixel users. I don't really want to check the operating system version and programatically change those properties as that seems quite hacky and will quickly become unmanageable.
I've looked for something similar to a UseSafeArea property for navigation bars rather than notches but there doesn't seem to be any. Is using WindowInsets the only way to this or has someone else had/solved this issue?
How it looks (controls at bottom are obscured):
How it should look (and does on every other device, the data is different here but it's the view that matters):
I had a similar issue which I solved by removing a few lines of code that were there to fix a bug that has since been fixed in Xamarin Forms.
It directly relates to this forum topic: https://forums.xamarin.com/discussion/87176/windowsoftinputmode-doesnt-work-in-xamarin-forms-android
If these lines exist in your MainActivity.cs, try removing them and see if that works:
Window.SetSoftInputMode(Android.Views.SoftInput.AdjustResize);
Window.SetSoftInputMode(SoftInput.StateHidden);
AndroidBug5497WorkaroundForXamarinAndroid.assistActivity(this);
I got a weird problem with bootstrap 3 and the glyphicons!
The problem appears on my android mobile phone with Chrome (latest).
Problem description: If the font-face-statement exists in the bootstrap.css to load the glyphicon font file(s), the layout of the page gets a little bit broken.
On a windows phone, it's fine. It's fine # Firefox on a Desktop machine too and also in Chrome Desktop.
If I load the page the first time, the layout is OK! If i reload the page or change the page: The weird problem appears and keep! (-> Cache?)
E.g., screenshots from Android Mobile Chrome (latest):
Button group vertical with glypihcons. Icons are moved to the right. (Padding problem?)
Buttons with text # footer. (Padding problem at right side?)
Label for an input field. (It just breaks)
A self styled Checkbox + Label after it. (Unwanted new line break after the checkbox because the parent container is a lil' bit too small (width)...)
I don't know whats going on! If I remove the font-family for the Glyphicon Icons from bootstrap.css, everything is and keeps okay (insteat the missing glyphicon icons off course). If I let the font-face statement in the file, the problem occurs # android mobile phone.
Does someone already have had this problemand how can I fix this and what is the problem?
Fixed it for my self. It don't know what Chrome did, but clearing all the Chrome App Cache worked for me. The Problem was App related.
Im using Ratchet Framework for andriod app development.
I have some scrolling problems in some android phones and also in bluestack.
when scrolled, a toomany blank spaces occurs and it affects the smooth scrolling. also affects the forms in the page. attached the image related
scrolling on some other devices is good , No extra space.
1) make sure you are using the meta tags provided by ratchet.
2) make sure you are inserting the bar-tab navigation at the top right after the body
From the ratchet getting started guide:
1. Fixed bars come first
All fixed bars (.bar) should always be the first thing in the of the page. This is really important!
2. Everything else goes in .content
Anything that's not a .bar should be put in a div with the class .content. Put this div after the bars in the tag. The .content div is what actually scrolls in a Ratchet prototype.
3. Don't forget your meta tags
They're included in the template.html page included in the download, but make sure they stay in the page. They are important to Ratchet working just right.
If that doesn't help post some code and let us take a look at it
I have a very simple Android app that's just a WebView. Everything works fine (complex Javascript etc.). However, all of the HTML select controls seem to be disabled. They display with default values, but nothing happens when I click on them, and they don't get the orange highlight when I arrow through the controls.
Other inputs (text, radios, submit) work fine, so I don't think it's a focus issue.
Configuration:
Eclipse IDE
SDK Version 8 (2.2)
Testing in the Emulator
I had the same problem. My problem was fixed by changing overflow:hidden to overflow:visible on a containing element.
I had the same problem.
In my case I had elements on the page that had the style position:fixed;
Although the bounding boxes of the select element and the fixed positioned elements did NOT overlap, I wasn't able to open the select dialog.
By removing a couple of fixed positioned elements I got it to work. Seems to be a bug in webview.
Same Problem, fixed it by setting position:relative on the li's containing the select fields
2 years after the fact, but in case someone pulls this up again:
If it's android 2.3, put in every empty child element of a fixed position parent. I found that this fixed the problem for me.
I have added the webview within scrollview in the layout. So data in webview is not fully displayed. Only in android sdk1.6 WVGA resolution, It is not working properly.
This bug is filed in android bug tracker also. For your reference, http://groups.google.com/group/android-developers/browse_thread/thread/d66d908993d51d65
Can anyone knows how to solve this very big high priority issue.
the webview scroll bars appears automatically so you don't need to nest into a ScrollView!
You should not put scrollable items
(e.g., WebView) in a ScrollView.
-- Mark Murphy (a Commons Guy)