I created a website for a customer: https://marie-gon.com
As always I tested it for various screen sizes using Firefox, Safari and Chrome inbuild responsive design tools.
I own a macbook 11inch, and ipad and iPhone 5/SE so for those devices I can check if the tests are the same in real live.
My customer has a macbook 16 inch retina, her partner a macbook 13inch and her graphic designer an iMac 5k retina. All 3 see sent me screen shots and none of them reflect the test results. I am trying to figure out for weeks now what's wrong and I can't solve the problem.
Can anyone help me?
It appears all is well, except for the customer.
Probably something to do with settings of the device.
Related
Why does my emulator screen look like gibberish?
The emulator works fine, but when I try to visit any webpage on chrome using the emulator, it crashes as you can see.
I don't know where else to look, and I need to get this up and running soon, so I can contribute to my companies repository.
I'm hoping somebody with more experience may have had issues with this and experience handling it.
Note: I had to enable SVM and IOMMU in my BIOS to even get the emulator to start on windows. All because I'm using a Ryzen 5 processor.
Also there are no windows options to enable hyper-v.
Thanks in advance!
-Allen
While developing app with codename one with Netbeans IDE, I was running into this issue where the simulators were not usable except iphone 3. If I choose the simulator to be iPhone 5 or 6 or 6 plus, the simulator is so huge and only part of it appears on the screen and I couldn't even scroll.
Is there anyway to make the simulator to fit within the window sizes? I tried on Mac and Windows and I experienced the same result.
Please advise.
Uncheck the Scrollable option under the Simulalator menu. It's on by default since some artifacts might appear during scaling but for large skins there is no alternative.
IDE: Eclipse
Desktop OS: Mac
Device : Android 4.0.4
Hi,
last week i sent a new android build to the server, and it updated the jar files i have on my Mac, then i installed the app on LG android 4.0.4 device that i tested before, and was surprised to find some pages display all black.
After investigating a little, i discovered that when i use tabs on any form the form will be displayed black only on android, no problem on simulator nor IOS iPhone 6S.
I looked at the forum and i found similar problem happened a year ago , and the solution was to use "android.asyncPaint=false" temporarily . now this removed the black, but messed all the rendering while navigating between tabs.
So my question is why this happened now? the past three months i was developing and deploying on android without any problem. Did the newest update corrupt something?
Thanks
Sam
Using the android.asyncPaint flag is discouraged as it will fallback into a relatively slow compatibility mode. We are currently investigating some regressions in some rendering optimizations that affect some devices and are in the process of deploying a solution for that.
Please let us know if the issues persist.
I have a hobby website:
http://www.chartmygolf.com/Programs/Program.aspx
and for the first time (in six years) someone has said the circle/percentage thing that appears when the program is loading is not appearing, and consequently the program does not load. What could be causing this?
He has installed Silverlight 5.
He is in the USA so I have a bit of time to prepare some ideas. The things I have thought of so far are:
A 32/64 bit mismatch between Internet Explorer and Silverlight versions. If it is this how do I check what 32bbit or 64bit versions they have of each?
Whether they have Silverlight not Enabled in Internet Explorer. (I think this might be low odds because he tried to load it on firefox and chrome with the exactly the same problem).
Does anyone know another Silverlight website page which requires program loading, so I can check if the problem he is having is specific to my page or to Silverlight programs in general?
Jon
EDIT:
Some more info.
He is operating on Windows 7.
He went to the sample Silverlight page (Silverlight SDK Sample Browser) and it loaded most of the way. What doesn't load is the top section and the sidebar which both have spinning circles around them with 100% in the middle.
He is using IE11.
In the add-on section the Silverlight is enabled for both 32-bit and 64-bit versions.
I hope this can be resolved.
So I have a website and I mean to make 2 version of it, the desktop version (with full features) and mobile version (simplification of the desktop version). I'm using media query in CSS to adjust the style. It works well in native browser. When I open my web using native browser it will show the mobile version style. But somehow when I open my web using Opera Mini, it keeps showing the desktop version instead.
I have googled it and didn't found any clue. Any idea how does it happen?
Thanks!
I finally found what's wrong with it. Turns out I was stupidly using #media screen only and Opera Mini doesn't seem handle it well. I've googled it for hours. Someone said actually Opera Mini supports #media screen but other people said that the right media property for Opera Mini is #media handheld. Well, I tried to play safe by simply changing it to #media all. And it works!
There are a number of reasons why Opera Mini is showing the desktop version of the site. The most likely is that your website is not properly detecting Opera Mini as a mobile site and is not returning the correct content. If you're using some plugin or other piece of software that is automatically handling the routing of desktop vs. mobile for you, that might be the culprit. Also, it's possible that this is happening by design, because of how Opera Mini works.
Opera Mini runs web content through Opera's own proxy servers and attempts to 'optimize' the content before delivering it to the user. That is, content is rendered first on the proxy server and then delivered to the device. This of course creates all kinds of complications for someone who is trying to deliver a consistent mobile web experience to their users. Fortunately, Opera provides a development guide to help give you a better sense of what's going on and how to cope with it.
Opera Mini is, in my experience, a very difficult browser to work with. At the Wikimedia Foundation, we server a very limited Wikipedia (and sibling project) experience when we detect someone's using Opera Mini.
You should definitely read through the opera mini development guide and make sure that any device detection you're doing is correctly recognizing opera mini as a mobile browser. If you're just using media queries, you may either want to reconsider a more robust approach to mobile detection, or adjust your design accordingly to work for opera mini. Good luck!