Mobile experience, what changed? (Read 591 times)

I have an android phone (through verizon).

It used to be that when I'd try to post with browsers on my phone, it would pop up a rudimentary text box w/ html-ish.  I couldn't do anything fancy, but I could enter the witty text I wanted to post and it would post.

With today's upgrade, it seems to be forcing me into the same editor experience I have on my laptop.  This seems problematic.

Using the basic browser that ships with the verizon android, the text editor does not interface with the keyboard application properly.  The user experience is that I touch the text window (which should bring up the keyboard), and nothing happens.

Using firefox for android (version current), it DOES bring up the keyboard application... but word-wrapping barely works.  And if I try to re-edit an existing post, navigation within the text editor was so strange that it is hard to articulate what it did.  I couldn't get to the end of the line easily, and when I did, it would NOT let me see what I was typing.

I had a slightly different change in my mobile experience. I use Android (jelly bean) on at&t and Opera browser. I used to be able to post, albeit with none of the control buttons and no formatting unless I typed html code manually.

Now (post upgrade) when I try to post I get a big blank area where the editor should be.  And yes I cleared the cache.

In order to post this message I am using the stock browser and it actually is working great:  all editor buttons are visible and I'll assume for niw rhat paragraph formatting works.

For now I'll use this browser, but I actually got kind of hooked on Opera.  I hope it works eventually.

Ah the joys of web development.  In addition to test against IE, FF, Chrome, and Safari, now there's the added complexity of iPhone, iPad and Android... 

The new release switched the mobile devices to use the wysiwyg editor because I finally got it to work.  Given some people are having trouble from their mobile devices, I can switch the mobile devices back to a plain text box.  Is that ok?

As is I have found that the update works better on my iPhone.

Ah the joys of web development.  In addition to test against IE, FF, Chrome, and Safari, now there's the added complexity of iPhone, iPad and Android... 

 

 

The new release switched the mobile devices to use the wysiwyg editor because I finally got it to work.  Given some people are having trouble from their mobile devices, I can switch the mobile devices back to a plain text box.  Is that ok?

 

Well, now that I found a browser that works with the wysiwyg I really like it.  Paragraphs are a Good Thing.

Would it be a horrendously impossible task to make that a user-settable option ?

Oh, and BTW : having avatars visible is awesome!

This works way better on my iPhone as well.  

I get paragraphs now!  (Hard returns didn't work the old way)

eric, not only do you have iPhones (several different models), androids (severl different brands), but I'm using a different browser on my iPhone because I don't like safari.  I'm using mercury.

I can't imagine having to test to make sure things worked on all the options available for people to use to browse the Internet now!

I can even modify my post and use smileys!  (But I can't see avatars)

ok on firefox on android, no good on opera. no avatars on either.

I tried it with a very old Android emulator and sort of experienced the problem.  However, if I wait for the editor to finish loading and click in the middle of the text area, then it works.  If I click anywhere near the icons, then weird things happen.  Not sure what to think of it at this point.