I created a blank MVC 5 app - changed nothing.
After publishing everthy works fine - except that I get no "navigation icon" on my WP8 device.
I get a (small font) full navigation bar on a WP7 device.
I get the icon on a galaxy tab.
But on my WP8 device (tested with mobile as well as with desktop setting in IE) I get nothing.
If I switch to landscape I see the "About" and "Contact" links but not "Register / Login".
When I turn back to portrait - "About" and "Contact" are visible till I refresh the page.
Then they are gone again.
The device I tested with is a Lumia 1020 WP8 (8.0.10517.150) German (768 x 1280).
I got some screenshots with the results:
As you can see - no "Menu box" on the right.
I also checked it with a Lumia 920 (WP8) - same results.
I finally found a working solution.
After finding this link http://timkadlec.com/2013/01/windows-phone-8-and-device-width/ I checked other the (there linked)article at http://mattstow.com/responsive-design-in-ie10-on-windows-phone-8.html
Adding (found at "Update: January 15 2013) the script
(function() {
if ("-ms-user-select" in document.documentElement.style && navigator.userAgent.match(/IEMobile\/10\.0/)) {
var msViewportStyle = document.createElement("style");
msViewportStyle.appendChild(
document.createTextNode("#-ms-viewport{width:auto!important}")
);
document.getElementsByTagName("head")[0].appendChild(msViewportStyle);
}
})();
fixed the problem for me.
Related
Please help me if you have iphone 12 pro ...
My boos (and some of his customers) has an iPhone 12 pro (ios 14.3) and I don't and yu can't install any apps in iphone simulator so debugging this becomes a nightmare.
This problem is specific to Google's app on iphone and does not happen anywhere else!
copy this link and open it in the google's app https://intaker.co/debug.html, tap on one of the links. The site won't load property, it seems that the screen size is not correct (it's very small)!! the loading widget is displayed on the corner and then everything is squished in the corner ... But now if you refresh the same page or rotate the phone the page renders properly!!!
Has anyone seen anything slimier to this? Do you have a solution?
UPDATE 1 : I put a fixed 100% width/height div in the page hopping to force it to grow but no luck
UPDATE 2 : If link comes from the same domain this problem does not happen!!! try the links in here https://intakerclientqa1.azurewebsites.net/debug.html they point to the same domain
UPDATE 3 : This is only happening when using this app https://apps.apple.com/us/app/google/id284815942
UPDATE 4 : Even after updating the device to 14.4 this is still happening, this is how the site is being rendered :
This happens only the first time and only when arrived from a external link, it works fine if :
link is typed/pasted in the browser
page is refreshed
device orientation is changed
I'm building a web app using the create-react-app toolkit. I'm trying to make my website as mobile friendly as possible. I'm initially designing for an iPhone 5 because that is one of the smallest phones around and because it's the phone I have. When I render my website using Chrome or Safari developer tools, the page renders very much different than when I open the page directly on my iPhone. Both Chrome and Safari developer tools have iPhone5 viewpoint defined as 320x568 however that doesn't account for the bar at the top and bottom of the page. In Safari the ACTUAL viewpoint size for my iPhone5 is 320x460 when the page first loads, and after you start scrolling down it expands to 320x529. I figured this out using:
window.addEventListener('resize', function(event){
console.log('width: ' + window.innerWidth);
console.log('height: ' + window.innerHeight);
});
HOWEVER, even when I change the size of the viewport in my developer tools to those values (both Chrome and Safari), it still looks different than the actual iPhone.
I've been unable to find similar problems/solutions to this problem on stack or anywhere else and I want to know if there's a way to make sure the page is viewed correctly on all devices?
Thank you in advance
iPhone 5 Web Design Specs
We have been developing a mobile site using Zurb Foundation 5. It works almost perfectly, except for some unknown reason Windows Phone 8 phones sometimes fail to render the site in full screen. I say sometimes as in maybe 75% of the cases the site is shown correctly but about every fourth time it's not.
Here's a screenshot from Lumia 920 which shows the problem:
The problem gets fixed if the phone is rotated to landscape (and back to portrait).
We're using the following meta info on our site:
<meta http-equiv="X-UA-Compatible" content="IE=edge, chrome=1" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no" />
Also included is the following script in the header:
<script type="text/javascript">
if (navigator.userAgent.match(/IEMobile\/10\.0/)) {
var msViewportStyle = document.createElement("style");
var mq = "##-ms-viewport{width:auto!important}";
msViewportStyle.appendChild(document.createTextNode(mq));
document.getElementsByTagName("head")[0].appendChild(msViewportStyle);
}
</script>
It feels like that the phone sometimes starts rendering the site too early. We have a splash screen with a centered progress ring and from that we can see that progress ring is at first usually on the left side of the screen (not full width) but it then gets centered (site goes full width). But sometimes the progress ring stays of the left and in these cases the site isn't rendered full screen. We haven't experienced this problem with Android or iPhone, only with Mobile IE.
Any ideas?
I have faced same problem and and yet not solved in windows Phone 8 App. But when I upgraded same app to Windows Phone 8.1 the problem is solved. NO CSS and any JavaScript code is working like those link. Reason is in Windows Phone 8 WebBrowser Control is using IE 10 and in IE 10 there is a BUG. Microsoft tells that bug is fixed but it is not. This is bug in IE 10. In Windows Phone 8.1 Webview for Store App and WebBrowser for SilverLight App which use IE 11. Bug is fixed in IE 11 not in IE 10.
Another Link for your Help
I have searched more than a week for same problem but I did not get any solution.
If you got solution Please post here
Thank You,
Background: The application is an iPad app running in Landscape only. When upgrading the app to Xcode 5 and running in the IOS7 simulator, I noticed that some buttons on the right side of the screen were not fully active. i.e. only a fraction of the left side of the button was clickable.
Observation: Running the same source code in IOS6 and IOS7 simulators, and viewing the view hierarchy using the REVEAL tool, I can see that the dimensions of the UIViewControllerWrapperView (the parent of my top level view controller) are landscape for IOS6 (1024x768), but portrait for IOS7.
I am trying to find a way to set the frame of the UIViewControllerWrapperView to the correct dimensions. In the view controller's viewDidLoad method, I tried to get a reference to self.view.superview, but it returns nil.
Can anybody explain; a) why the UIViewControllerWrapperView's frame is in the wrong orientation when running in IOS7 and not IOS6, and more importantly b) how to make it right?
Are you using a UITabBarController? We were having exactly the same issue and got it working by adding this on the UITabBarController:
- (void)viewDidLayoutSubviews
{
// fix for iOS7 bug in UITabBarController
self.selectedViewController.view.superview.frame = self.view.bounds;
}
Why? check this answer
In my demo web app at http://dtmp.vm-dg.de/ori/app.html#view-location/locid-1/catid-0 I have a problem: When running the app in Web App mode from the home screen instead of inside Safari and then click on one of the categories, then the umlaut dots from the Ü in the title will "stay" there on iOS 6. (I don't have an iOS7 device and actually don't intend on upgrading)
I have put the two screenshots showing the bug at https://www.dropbox.com/s/forfzxfqm1i1295/bug1.jpg (menu screen) and www.dropbox.com/s/fiym7qwz6i9xo5x/bug2.jpg.
I have not managed it so far to nail it down to a testcase, though. Anyone ever experienced a similar problem?