Xpider_MX
New member
Well, then WPCentral is wrong because I read it here, in a WPCentral article.
Sent from my RM-820_nam_canada_246 using Tapatalk
Sent from my RM-820_nam_canada_246 using Tapatalk
IE 11 improves a lot but still not as good as Chrome in Android.
Today I was comparing IE 11 with by brothers Android phone.
I am not going to talk about speed here but the things IE can't do but Chrome can do.
1. IE 11 still can't open sites which open with pop ups.
It's quite annoying that WP IE 11 can only open sites which doesn't have pop's just like old JAVA or S40 phones.
Come on MS, it's 2014 a smartphone era and IE 11 still sames level as old phones now.
2. IE in WP8.1 still crashes like WP 8 when we open heavy sites. I notice IE 11 very often crashes and struggle to open sites like Phonearena.com but Chrome easily open and very fluidly works without any crashes.
If anyone of you have Android phone you can confirm it your self.
I don't know if IE for WP8.1 is still a beta or a stable version but it still needs lots of improvement.
I thought MS is going to fix this in next update but they didn't.
I think these are pretty basic thing that a good browser must do.
What you guys think?
I tried loading phonearena.com. I don't have any issues either. I haven't seen any crash so far with ie11. I also would like to know which site with pop ups not working?IE 11 has NEVER crashed on my 1020, so I'm not sure but it seems like you're having some other kind of issues. Also, phonearena.com opens very fast and I can browse it very fluidly.
In regards to the popup thing, can you provide a link to test? I have yet to visit a site that won't open because of popups.
Alsoo, IE is very fluid when scrolling and zooming and Chrome on Android is slow and unnatural. (I have a quad-core Nexus 4 at home as well) I personally think IE11 may not have some of the advanced features of Chrome, and that has always been the case, but speed is probably the biggest advantage of IE. Windows Phone's browser is very very fast. You should also try sunspider browser test on a Galaxy S4/S5 and watch how the benchmark is barely faster than a 2 year old Snapdragon S4 in a WP running IE11.
Just be certain what device do you have? Sounds like you must have a budget phone if you're having performance issues
Guys windows phone is a developing OS
What do you need to do to get this update? (I'm guessing you may not be aware having posted from an android device but that's just a assumption). You need to register as a developer. Only then will you get the update to any devices linked to that developer account (its been a while for me so the specifics you can read about elsewhere). When MS made it free, the exact thing they were probably hoping to avoid happened which is that lots of non-developers signed up for the program just to get the latest shiny bits early. So yes, it is a preview...No it is not all final code...Yes it's reasonable to assume they are going to update the browser between now and the actual OS release date, Its also fairly reasonable to assume that we're running a debug build with extra junk in it to report issues back to MS in more detail than a final release would have, and hence it being a bit slower (although I don't see it personally). These are the things most devs would expect from a developer/preview/beta/whatever the latest marketing term is that isn't final... release.Then why is a beta being so easily downloaded my so many? Usually betas are more inclusive. No, this is the final software without minor tweaks that will be available when it goes OTA. But for all intents and purposes this is how it will be. Minor stuff like the IE issue will be fixed but this is not a beta.
Posted via the WPC App for Android!
When MS made it free, the exact thing they were probably hoping to avoid happened which is that lots of non-developers signed up for the program just to get the latest shiny bits early.
There is no indication that MS hoped to avoid this. They made this Dev program extremely easy to sign up to, and publicized it and made it unlimited.
Are you using 512MB RAM device?
Has to be among the worse ideas since the McRib. Take a released version of a browser and pit it against a browser that isn't even beta, its a developers preview for crying out loud. Then go on to proclaim this is a fair challenge and encourage others to come to the same conclusion using the same set of parameters. Not science.
When are you people going to learn? It's not a beta, and it's certainly not pre-beta. It's the final build that's sent to OEMs.
Of course, there will be overall performance improvements when the OEMs come up with firmware updates specific to their devices, but IE is not going to change unless MS releases an update. I hope they do, but that doesn't mean the current version is a beta.
ROTFLMAO
Final build. Keep believing that.
The ?final build? from last week, combined with the more recent Final Adaptation Kit, will form the ?real? gold code for the OS ? referred to as the snappily named ?Windows Phone 8.1 QFE1 Final Adaptation Kit Build? ? which Microsoft will seed to its OEM partners. This code should be in the hands of manufacturers on April 14, before its rollout to existing users begins later this month through the Windows Phone Developer Preview.
I have iOS, android and windows phones. None of what you said is even remotely true. You do sound more like an iCultist though, so not surprised by the comments.hahaha ... android users are also very annoyed by the slow and sluggish google chrome , it even lags on galaxy s4 .... ie11 is way better
Say you load a very long article, and start reading it. In the middle, you want to do something else, so you press the Start button and get to a different app, leaving IE behind. Once that's done, you get back to IE.
In WP 8, the long article you were reading would be waiting for you exactly where you stopped reading, no matter how long you spend outside.
But in WP 8.1, if you spend even 15 minutes with the phone locked on the start screen without opening any other apps, as soon as you get back to IE, the page will reload. Now this itself is okay, but the problem is that when this happens, most of the time, the page will go back to top, and you will lose the point where you were last, which is a great annoyance for some of us who read large texts on the phone's browser.
And if reading mode were to be on when switched to the start screen, chances are that the page won't load at all when you get back, leaving you with a blank screen, forcing you to exit reading mode and refresh manually.