When scrolling, I noticed a rendering issue after updating Google Chrome. It seems like it is rendering the page too slow.
My version of Chrome is 49 and my operating system is Windows 10. (This did not happen in Linux, Mac or Windows 7). It is using the CSS property: display flex.
Has anyone else encountered this issue as well?
Windows 10 hates Chrome. It seems like Microsoft is intentionally attempting to make others use their browser, "Edge", because of how slow they have made Chrome run. On any other operating system, it runs flawlessly on an even 4gb of RAM. On Windows 10, you'll be waiting every bit of 5-10 minutes just for the "about:blank" page to load, not even trying to get the internet yet.
With this in mind, I'm almost sure that this is something to do with Windows 10 being itself. I've had multiple rendering issues on Chrome myself on the operating system.
I'm also with Michael_B on this, the comment above. It looks like it could be a bug in Chrome but I wouldn't be surprised if Microsoft didn't contribute to this somehow.
I hope this helps.
Related
I have to run the Testsuites across Windows (Chrome, Firefox, and IE) and macOS (Safari and Chrome).
Wanted to implement best strategies to Synchronize AUT with Robot test scripts while testing around Cross browser and Cross platform.
Somehow felt handling Safari browser on macOS is bit challenging. How best I try add some wait but still fail for each run with some 'ElementNotVisibleException'.
However Chrome on Mac OS is quite okay when the same is tested on Windows machine.
Any thoughts would be highly appreciated on best handling mechanisms for Safari on Mac OS.
Thanking in advance!!!
you can use Wait Until Element is Visible Keyword from selenium2Librray from robot framework. the best way is to do it on safari is try executing the scenario manually first and note the maximum time it takes to load the webElement. Once you note down the time, put this time as you max timeout. Below is one example
Wait Until Element Is Visible ${mention_locator_here} timeout=${element_timeout_in_seconds}
You can explore those options Here
Hello Stackoverflow community.
Since the release of Windows 8 and thus, Internet Explorer 10, FCKEditor refuses to function with IE10. With the latest patches, Firefox 17 and Chrome work just fine with it.
I know FCKEditor is old, so I was thinking of moving to CKeditor but it seems, its implementation for classic asp webpages doesnt work with IE10 as well.
Any suggestions, on how to fix the problem, or any other editors (with the functionality of the above two editors) would be appreciated(classic asp only).
CKEditor should work with IE10.
Maybe there are some problems with it at the moment (I tested it briefly some time ago), but given that it's a supported version (opposed to the status of FCKeditor), if you file bugs reporting the problems they should be fixed eventually.
So recently Microsoft threw the joke that was IE6 into the recycling bin, and said that users should automatically be upgraded to the latest version of IE, if they hadn't already. Unfortunately for web designers, this means that some people (running XP) will be stuck with IE8.
I recently started redesigning a clients website to bring it up to date, and in order to make loading times quicker, save on disk usage, and on bandwidth, I have implemented the use of CSS3 code and then a big but... IE8 Doesn't support CSS3... :(
Is there a significant amount of users on XP / Vista / 7 who still use IE8, or have they moved to alternative, more up to date browsers such as Chrome, Firefox, Safari etc?
Should I worry about trying to find a way to keep the website looking correct in all browsers? or is there a way for me to encourage visitors using IE8, to swap it for another browser?
I imagine this depends on how the website is used. Is it an intranet website, a public website, or an web application that the owner dictates the version. IMO the best way to figure this out is to have Google Analytics plugged into the web app.
I can tell you that the project I am currently on doesnt have the luxuary to rule out IE8. 70% of our users that use the web app I work on use IE8. It seems to still be the most used browser in the business world. (at least from my experience) Heck we still need to support IE7.
However if you can guarantee the web users are using an up to date browser, then thats a different story. Or of course you can say, this app doesnt support IE 8 or lower.
Thats my 2 cents.
IE8 is the default browser in Windows 7, so expect it to hang around forever, just as IE6 has because it was the default in Windows XP.
Use http://code.google.com/p/html5shiv/ or http://code.google.com/p/ie7-js/ to ease the pain.
Yes, but according to WC3 the percentage of usage is now only ~8% for IE8.
Thats still a pretty big number to turn your back on however.
I'd be very interested to hear what professional developers think about this, particularly frontend developers.
How do you go about testing your designs in multiple browsers? Do you use virtual machines, each with a different version of Internet Explorer installed? What is your setup/workflow?
So, what's the most efficient and reliable way to test a design in several legacy web browsers?
Thank you.
I mostly use Spoon virtualization. They removed IE from the service aftyer Microsoft told them to however it's still a good service for testing other browsers/versions.
For IE I tend to use the Microsoft provided IE VMs.
If you need virtualization product then VirtualBox is pretty good and free.
I've also just discovered Browserling which does something similar to Spoon virtualization and has support for multiple IE versions.
Oracle's VirtualBox is free. I have the following VMs set-up:
Windows XP - IE6, Firefox 3
Windows XP - IE7, Firefox 4
Windows Vista - IE8
Really, I don't test older versions of Firefox, Chrome, or Safari. All three of those browsers are on quick update cycles now and the push their updates almost immediately. The chance that users are still using an older version of those is much less than those using Internet Explorer.
Even now, I don't really test in IE6 anymore (thank god), but I know this is different depending on the audience of your website.
Really, if you can get away with it, do your basic testing in IE 7, 8, 9 and the latest versions of Firefox, Chrome, and Safari. Don't go completely out of your way to fix layout issues in older IEs; If you can get the information you want from the site, then the site is functioning. If someone complains about the site not looking exactly right, recommend they upgrade or switch browsers. "I can't upgrade from IE6 because my company uses it" is not really a valid excuse anymore with Chrome and Firefox being as light weight as they are, unless their computer admins have things completely locked down.
IE Tester allows to see web from ie5 till ie9.
http://www.my-debugbar.com/wiki/IETester/HomePage
It depends how legacy you wonna go but there is also Adobe browser lab.
I build a webpage and in IE8 + FF3 it goes well, but a friend opens it in ie7 and it's terrible.
How can I emulate IE7 / other things / FF2 in my Windows 7 envoirement?
You need to run in in a virtual machine as you can't have multiple versions of IE installed on the same machine the same time.
Downlaod Virtual PC 2007
Download the IE7 Virtual PC image from Microsoft. There's also an IE6 image there.
You can also install FF2 on the virtual machines safely.
IE8 has a Developer Tools utility under Toos->Developer Tools. You can change Compatibility Mode to view how the page would look in IE7. As for FF2, the only way I know of is to actually have FF2 installed. Maybe you can find an older download package?
Once the utility opens there is a Browser Mode: box on the top menu. Change that to IE7, and it will render the page as IE7 would.
I've used the 'Superpreview' feature that comes with Expression Web 3, it has help me to get a page working with IE8,7 and even 6, along with FireFox. You can get a free trail if you can't get the full version.
You can use IETester for IE 5.5 to 8 for emulation. You can add on DebugBar (by the same developer) into IETester for Firebug-like debugging.
However Firefox I'm not sure. The only thing I can think of is to download a clean FF 2 and install it on another computer.
As for Firefox, you can use a portable version.
Various options locally:
Run multiple virtual machines hosting different browsers (or combinations of browsers)
The latest version of expression has a fairly comprehensive browser comparison tool
There are some clever IE hacks out there too.
Also online
Browsercam (and similar sites)
Adobe Browserlab possibly - not sure how "live" it is yet.
There are a number of simulators, one at least from MS to let you view in different IE browser versions. However they are simulators so may not accurately reflect the actual browser. Another way, but it might be over the top for your purposes is to install VM's and put the real browser in each VM to do the testing.
I'm currently using Internet Explorer Collection which gives me over a dozen versions of IE, not that I test that many but it's interesting to look back at occasionally.