We are starting side by side testing IOS vs droid

[stevec]

First issue we have is that if a textbox is disabled on android then the context menu is also disabled and cannot be clicked on. This works find on IOS (can click on it). We use this in many places for popping up a map where we do not allow the change of address (or GEO) in some situations so it is disabled, but we still want the user to be able to click on context menu and use it.

[stevec]

Hmm ...

Why did you delete your response? Thinking IOS wrong and not droid ...

I was told here on another issue (or maybe an email, not positive) to go with disabled to remove the box when not editable. At that time I was leaning toward appearance Plain and they said no to use disabled true instead. Anyway for now I went with my original idea of appearance plain (when not editable) rather than disabled true, and that works on both.

But it does need fixed, but one which OS ... lol

[MarkDuignan]

I deleted it because I had read the table referenced in the URL back to front - which made me think my response was actually wrong information.

[MarkDuignan]

This was the table - http://www.longrangemobile.com/docs/LRP ... areena.htm

ie: There is some subtlety as to when disabled elements are responsive or unresponsive.

However - I'm not yet sure how that relates to context menus.