search

ericmckean / wave-protocol

Automatically exported from code.google.com/p/wave-protocol
0 stars 0 forks source link

cannot Enter or edit text in a blip on iPad or iPhone (web client) #237

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Connect to a wave server's webclient with socket.io
2. Load or create a wave
3. Try to edit the text of any blip, new or old

What is the expected output? What do you see instead?
Expect a cursor to appear and the text entry panel to pop up. Instead, it tries 
to select the text entry area as an object like an image

What changeset or version are you using? On what operating system?
2011/02/08 17:00. Federation disabled, Sun Solaris 10/Sparc64. Issue verified 
by hosting on Mac OS X 10.6.6/Intel64. Client OS on iPad/iPhone tested with 
iPhone OS 3.2, iOS 4.2(phone), iOS 4.2(pad). Other client used it test, Macbook 
previously mentioned with Safari and Firefox, both tested ok.

Please provide any additional information below.
Not a major issue by any definition, but given the popularity of this class of 
device, well worth being logged as a bug. On the plus side, current versions 
with socket.io work perfectly apart from this, and I can watch blips being 
edited etc, just can't create them

Original issue reported on code.google.com by GeekChiq...@gmail.com on 6 Mar 2011 at 11:50

GoogleCodeExporter commented 9 years ago 
Just a note - you can use an alternative Data API based client to access WIAB. 
I have modified the micro-wave app created by antimatter15 to support WIAB. You 
can try it at micro-box.appspot.com (it works with waveinabox.net:9898).

Original comment by vega113 on 13 Mar 2011 at 4:15

GoogleCodeExporter commented 9 years ago 
The result is identical to the waveinabox client - site works perfectly, waves 
can be created, read, watched, users added - but the iPad's web browser doesn't 
support the element used for entering text so it's not possible to input or 
edit anything as the on screen keyboard does not appear, nor the cursor.

Does anyone have an Android phone or tablet who could test this in mobile 
Chome? I've only had access to MobileSafari.

Original comment by GeekChiq...@gmail.com on 13 Mar 2011 at 10:47

GoogleCodeExporter commented 9 years ago 
This is a known issue with both Android and iDevices. The problem lies in the 
fact that both use browser versions that are cut down copies of the desktop 
versions. Until they are brought up to speed, the best way to access WIAB from 
these devices would be with a custom client.

Original comment by JamesRPu...@gmail.com on 13 Mar 2011 at 10:51

GoogleCodeExporter commented 9 years ago 
Well, I think we can safely adsume that neither the Apple or Android mogile 
webkit teams are likely to change this any time soon, since it's not a widely 
used feature.. What would anyone suggest as a replacement element for the 
current text input method in a mobile web client? Or woukd you suggest an 
entirely native app?

Original comment by GeekChiq...@gmail.com on 13 Mar 2011 at 11:17

GoogleCodeExporter commented 9 years ago 
I am using micro-box on my iPhone - have no problem to edit/create blips.

Original comment by vega113 on 14 Mar 2011 at 9:14