- 02-17-2013, 11:21 AM #1
I.E. for this fourm or the other fourm I frequent very much - Facepunch
As soon as I select a text field, the keyboard comes up and then immediatly goes away and deselects the text field. I've -never- had this issue with any other browser on any other device. Text fields such as login/password (stuff that is only one line long) are fine, but any text fields like "REPLY" or whatever supports more than just plain text it immediately does what I described above.
I tried the top rated free browser in the market - I like its UI much more (then again, I probably didn't fully learn how to use the IE browser yet... new phone!), but it has the same exact issue, which tells me that it simply uses the IE browser as a base and just is a simple UI change for it.
Anyone have any solutions to this, or alternate browsers that don't have this issue? This is a pretty huge deal breaker for me since I frequent the above forum and several others (that are based on the similar posting systems) and being able to only browse using my phone would be a huge bummer.
- 02-17-2013, 11:48 AM #2
Yes, I occasionally have this problem with this site on WP8 and my Surface RT. I don't know what it is and am surprised there hasn't been more complaints about it. Perhaps its because many went with the wpcentral app to access these forums.
- 02-17-2013, 12:39 PM #4
The problem is two fold.
1. Webkit uses a non-standard somewhat hacked together touch API, Internet Explorer adheres to web standards in this instance.
2. The web programmers on those sites are coding to work with the proprietary webkit API and not coding to the standards like they should.
And Google seems perfectly happy with making webkit the new IE6, and those web programmers seem perfectly content to play along and let Google control the web. So who knows if this will ever change.
- 02-18-2013, 12:06 AM #9
Edit: here I will do some for you.
Pointer Events is a draft specification that provides a unified event model for multi-touch, pen, and mouse input. It's the World Wide Web Consortium's (W3C) second attempt at a standard for handling touch input. The first specification, Touch Events, has been essentially abandoned. Touch Events were modeled on the proprietary touch API that Apple added to Safari for the iPhone. However, the specification was written without Apple's involvement, and the Cupertino company refuses to commit to disclosure and royalty-free licensing of any patented technology that might cover the Touch Events spec.
The contribution comes not long after Redmond encouraged Web developers to remember Internet Explorer and not assume that WebKit is the only rendering engine that's used on the mobile, touch-oriented Web. At the moment, touch-driven Web content is leaving Internet Explorer 10 (and hence Windows 8 and Windows Phone 8) behind, because it is being written for WebKit and Touch Events, and WebKit and Touch Events alone.
Pointer events, open standard, used by IE.
Touch events, proprietary webkit unlicensed and inferior, used by webkit and far too many developers.
- 02-18-2013, 09:06 AM #13
Here's what i have to do sometimes:
Click on "go advanced" and click on the title field to bring the keyboard up, then press and hold on the body/reply field until the cursor appears and the keyboard should stay up.
Some say the mobile vs desktop option in the IE settings makes a difference, but I've found it happens either way.
- 02-19-2013, 07:35 PM #16
Also, I found an alternate fix for fourms that don't have a title area to trick the keyboard up.
Using UC Browser (which is free, and works just like IE except with more functionality) you can enable "Speed Mode" which turns the web page into a text only/simple environment. What you do then is go into "Go Advanced" when making a reply, turn on speed mode, and then you should be able to select and enter in your reply without any issues. Submit reply, then switch speed mode off to view full web pages again. Downside is, because its a simple text box you make your reply in while you are in "Speed Mode", typing suggestions, auto-correct (i.e. capitilzation) etc doesn't happen while you type.
It's annoying you have to take these steps but AFAIK this will work for any website no matter what, making WP8 usable to make replies on web forums.
Hopefully they just fix this in the future though.
- By mb-dape in forum Windows Phone 7Replies: 17Last Post: 02-28-2012, 10:35 AM
- By sloppy standard in forum Windows Phone 7Replies: 10Last Post: 11-19-2011, 04:16 PM
- By Lopes in forum Windows Phone 7Replies: 13Last Post: 10-06-2011, 10:42 PM
- By HeyCori in forum Windows Phone 7Replies: 8Last Post: 07-11-2011, 01:42 AM