Results 1 to 17 of 17
Like Tree1Likes
  • 1 Post By Ordeith
  1. KorJax's Avatar
    Member

    Posts
    54 Posts
       #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.
  2. ninjaap's Avatar
    Member

    Posts
    2,454 Posts
    Global Posts
    2,466 Global Posts
    #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.
  3. KorJax's Avatar
    Member

    Posts
    54 Posts
       #3  
    Guess I just need to get tapatalk or something. I prefer using web interface though because it shows everything in the formatting that the forum is designed for with all the features the forum has.
  4. Ordeith's Avatar
    Member

    Posts
    185 Posts
    #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.
    HeyCori likes this.
  5. stmav's Avatar
    Retired Moderator

    Posts
    3,685 Posts
    Global Posts
    3,767 Global Posts
    #5  
    Not sure about other sites. But if I do the spread fingers zoom on the reply area, the cursor is in the box and keyboard stays. And I can reply with no problem. Same on my Surface RT.
  6. KorJax's Avatar
    Member

    Posts
    54 Posts
       #6  
    Quote Originally Posted by stmav View Post
    Not sure about other sites. But if I do the spread fingers zoom on the reply area, the cursor is in the box and keyboard stays. And I can reply with no problem. Same on my Surface RT.
    Doesn't do anything for me. If I select it and then picnh zoom I get the cursor in the box, but not keyboard.
  7. FinancialP's Avatar
    Member

    Posts
    433 Posts
    Global Posts
    467 Global Posts
    #7  
    Quote Originally Posted by Ordeith View Post
    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.
    Don't spread such a lie, please.

    It's the way the OS handles touch based events. Nothing to do with WebKit
  8. stmav's Avatar
    Retired Moderator

    Posts
    3,685 Posts
    Global Posts
    3,767 Global Posts
    #8  
    Quote Originally Posted by KorJax View Post
    Doesn't do anything for me. If I select it and then picnh zoom I get the cursor in the box, but not keyboard.
    Works fine for me. Replying right now that way.
  9. Ordeith's Avatar
    Member

    Posts
    185 Posts
    #9  
    Quote Originally Posted by FinancialP View Post
    Don't spread such a lie, please.

    It's the way the OS handles touch based events. Nothing to do with WebKit
    it is no lie, do your research.


    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.

    Tl;dr:
    Pointer events, open standard, used by IE.
    Touch events, proprietary webkit unlicensed and inferior, used by webkit and far too many developers.
  10. FinancialP's Avatar
    Member

    Posts
    433 Posts
    Global Posts
    467 Global Posts
    #10  
    Quote Originally Posted by Ordeith View Post
    it is no lie, do your research.


    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.
    Hmmm ok. Still has nothing to do with WebKit or Google or Apple.

    But hey, whatever you believe.
  11. Ordeith's Avatar
    Member

    Posts
    185 Posts
    #11  
    maybe you should re-read, looks like you missed several somethings there.
  12. realwarder's Avatar
    Member

    Posts
    822 Posts
    #12  
    Whatever the cause its pretty sad that the phone these forums are promoting has issues posting here. The forum needs an update to fix this.
  13. Ed Boland's Avatar
    Member

    Posts
    559 Posts
    #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.
    Thanked by:
    KorJax 
  14. KorJax's Avatar
    Member

    Posts
    54 Posts
       #14  
    Quote Originally Posted by Ed Boland View Post
    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.
    Wow thanks that dies the trick! Still annoying but at least my forums are now usable.
  15. Ed Boland's Avatar
    Member

    Posts
    559 Posts
    #15  
    You're welcome!

    Yes, very annoying... especially on a Windows Phone forum!
  16. KorJax's Avatar
    Member

    Posts
    54 Posts
       #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.
  17. Ed Boland's Avatar
    Member

    Posts
    559 Posts
    #17  
    Cool! Thanks for the heads up.. just tried that and it does indeed work like you say.

Similar Threads

  1. Go back in Internet Explorer, how?
    By mb-dape in forum Windows Phone 7
    Replies: 17
    Last Post: 02-28-2012, 10:35 AM
  2. How to browse in Internet Explorer? Back button?
    By sloppy standard in forum Windows Phone 7
    Replies: 10
    Last Post: 11-19-2011, 04:16 PM
  3. Go forward in Internet Explorer?
    By lopes in forum Windows Phone 7
    Replies: 13
    Last Post: 10-06-2011, 10:42 PM
  4. Replies: 8
    Last Post: 07-11-2011, 01:42 AM

Posting Permissions

B