Firefox suddenly began to display the Wall Street Journal web page (www.wsj.com) in much smaller magnification.This behavior corresponds to some sort of recent Windows 10 automatic update. Explorer and Chrome behavior were not affected.
Related
I cannot make Google Chrome tile correctly in Awesome WM (version 4.3 in Debian 10 & 11). Chrome's window stops responding, or goes blank, if it is resized (a new tile is added next to it, or a tile is closed/minimized), or when it's open in floating mode.
This weird behavior started with the recent version of Chrome (probably, 86). Only Chrome is affected, Firefox and all other applications I use work without problems.
I tried running Chrome with debug log, but there is nothing helpful there. No error messages appear, neither in journalctl nor in ~/.xsession-errors.
Did anyone experience anything like this before?
The problem was resolved after disabling "hardware acceleration" in Chrome. Seems like this feature didn't work well on my system (intel hd graphics 4400 and Awesome WM).
I have a Windows Phone (a Nokia Lumia) from which I recently encountered an issue. I can't zoom (pinch zoom) or navigate (scrolling with the finger) using Google Maps. It was possible I believe last week or the week before that, but now it's not working anymore.
I can't recall any updates issued in between last working date and now, nor have I fiddled with any options.
I saw in a thread that one could use the options in the browser in order to enable zooming. But this option is not present for me. I use Internet Explorer.
Based from this thread, if it was determined that you are on a desktop version or IE, it will allow zooming to be controlled by mouse. Touch won't work at all. I also found this blog which states that:
The mobile Web version of Google Maps is optimized for WebKit browsers such as Chrome and Safari. However, since Internet Explorer is not a WebKit browser, Windows Phone devices are not able to access Google Maps for the mobile Web.
The desktop version of Google Maps works just fine in these browsers. It's one thing for Google to say the mobile site isn't tested or supported in the mobile browsers, but the desktop version, at least, shouldn't be off-limits. The desktop version may not be ideal in a mobile browser, but it does work.
I just checked my web app in a first-generation iPad with Safari 4.0.4. I
noticed a lot of styles were not working properly:
border-radius
opacity
image height & width (if only one property is declared in the css)
etc...
I am thinking whether to make necessary css adjustments to make my web app render properly on Safari 4.0.4. While the global usage for IE6 and 7 are quite moderate. At the moment we are fine with not showing full support for these browser versions, due to their lack of css support.
Could this same consensus apply for Safari 4.0.4?
IE7's last release was on 2007 (http://en.wikipedia.org/wiki/Internet_Explorer_7). Safari 4 was on 2010 (http://en.wikipedia.org/wiki/Safari_version_history)
If any other frontend developers faced a similar scenario. Would appreciate to hear from you.
I think iOS can be considered sufficiently deprecated at this point to ignore it. The iPhone 4 came with iOS 4 and the iPhone 3GS has had several updates available for it for so long that an incredibly small percentage of users would be expected to still use iOS 3.x. Further, since most mobile platforms push you to update as soon as a new version is released, there is even less of a chance anyone is using anything but the most recent 2 or 3 versions.
You can see a breakdown of iOS version usage here: http://david-smith.org/iosversionstats/
Also, your link goes to information about safari desktop versions. For iOS, go here: http://en.wikipedia.org/wiki/IOS_version_history
As a general rule, our company uses the 2 versions back rule, 3 for IE, unless there is a specific need for further backward compatibility per the client.
I'm designing a mobile website but am having some issues with the compatibility. After testing the website on my Android phone (Rezound) and my brother's iPhone 4, the website looked okay. But when I asked a friend to test it on his Galaxy Nexus, he says he just gets a black screen.
Are there any known website compatibility issues with the Galaxy Nexus? The only thing I know about that phone is that it uses Ice Cream Sandwich, but aren't all Android o/s phones going to render the website in a similar, if not identical fashion?
This is the link to the website in question: http://m.studiosimplicit.com.
I just tested this on a Galaxy Nexus running Android 4.0.2 in the default browser, the latest Opera Mobile and Firefox, and Chrome Beta. All of the aforementioned browsers handled your site fairly well except for the default Android browser, which produced the black screen you described on first load, and the menu elements below a large black square on a subsequent load.
If I had to guess, I'd say that this has something to do with the fixed positioning of your img.bg. Support for fixed positioning was just recently introduced in Mobile Webkit, and its implementation is still a little rough around the edges. Mobile browsers that don't support position: fixed will simply ignore the styling rule and render the element with its inherited positioning while ICS' default browser, which claims to support fixed positioning, will botch the rendering of the element producing the weird behavior we're seeing.
I may be wrong, but I believe the only non-constant thing in the default Android web browser is screen resolution. Although the hardware may be different, the OS it's running and the software the OS is running are the same. It should render identically on the same OS.
The only explanation I can come up with is that Ice Cream Sandwich has flaws in its browser. Though that doesn't seem to make sense either, considering that web page is simple enough. To be honest, I'm as confused as you are right now...
I'm downloading the SDK to test your website in an emulator. Let's see what happens.
Edit: someone else seems to have taken over. I'll just leave it to him/her.
So added gears functionality into my Mobi Engine, but there is a wierd behavior when viewing the site in Chrome. The HTML gets shifted down by about 15px. All other browsers tested so far does not show the same problem. Also doesn't seem to affect any mobile browsers.
Check here for the symptom. http://cibr8.itell.mobi
I only need gears to post back the user's location (if allowed by the user).
I don't know what is causing this, but you could drop Gears for the Chrome browser. What Gears used to provide (location & local storage) is now part of HTML 5. Google have "end of life'd" Gears. Chrome supports HTML5 (up to date versions anyway)
http://gearsblog.blogspot.com/2010/02/hello-html5.html