Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example does not work on Android 2.2.1 #25

Open
akuckartz opened this issue Dec 17, 2012 · 5 comments
Open

Example does not work on Android 2.2.1 #25

akuckartz opened this issue Dec 17, 2012 · 5 comments

Comments

@akuckartz
Copy link
Contributor

The example http://szabyg.github.com/annotate.js/ does not work either in the Android browser which is part of Android 2.2.1 nor in Firefox 17 nor in Firefox 18 beta.

The page loads but When I click on "Enhance" nothing seems to happen. The button label is not even changing to "in progress...".

Can it have anything to do with small bandwidth? Any other ideas or suggestions?

@akuckartz
Copy link
Contributor Author

It also does not work in the most recent versions of Opera Mini and Opera Mobile.

There does not seem to exist any browser for Android 2.2.1 (on Samsung Galaxy) in which the annotate.js example works :-(

Researching that issue I noticed that underscore.js is calledby the annotate.js example) also has problems in these browsers:
jashkenas/underscore#908

My guess is that these problems with underscore.js might also be the cause of the annotate.js issue. That library is used in "_.defer()" which is called in the example. But that currently seems to be the "only" use of underscore.js.

@akuckartz
Copy link
Contributor Author

I got it to run on Android 2.2.1 :-)

I will report details later. Hint: browser settings.

@akuckartz
Copy link
Contributor Author

I changed the text encoding setting in the browser from Latin-1 (ISO-8859-1) to Unicode (UTF-8). Automatic might also work.

And I switched off the popup blocker.

I did not try to find out if both are necessary.

The first sign that something is difference is that clicking on one of the two "Enhance" buttons changes both labels to "In progress...".

Clicking (touching) on one of the enhanced terms marked with a colored backgrund results in the disambiguation dialog to be shown and that also works properly.

One problem still exists. So far only the short second paragraph was enhanced but not the far longer first one. Maybe it is just slow and needs more minutes.

@szabyg
Copy link
Owner

szabyg commented Dec 19, 2012

I admit, annotate so far is not optimized for smart phones. I just tried on
Android 2.3.3 (Galaxy S) with the following result:
Verily slowly, but works.
Editing is not possible due to HTML5 contentEditable incompatibility of the
built-in browser.
Mouse-over functionality doesn't exist on a touch device. Best practice to
solve this?
On Dec 17, 2012 1:37 PM, "Andreas Kuckartz" [email protected]
wrote:

The example http://szabyg.github.com/annotate.js/ does not work either in
the Android browser which is part of Android 2.2.1 nor in Firefox 17 nor in
Firefox 18 beta.

The page loads but When I click on "Enhance" nothing seems to happen. The
button label is not even changing to "in progress...".

Can it have anything to do with small bandwidth? Any other ideas or
suggestions?


Reply to this email directly or view it on GitHubhttps://github.com//issues/25.

@akuckartz
Copy link
Contributor Author

@szabyg I am really happy that I finally had noticed that the popup blocker of the Android browser was active and annotate.js is working for me now :-)

The speed is no problem as far as I am concerned.

A popup blocker also was one cause of the problem when using annotate.js in the mobile versions of Firefox (17 and 18 Beta). Unfortunately they do not provide a comfortable user interface to switch it off - not user friendly :-(

But at least I found this:
"Type about:config in the address bar. Use the filter to find dom.disable_open_during_load and set it to false."
https://support.mozilla.org/en-US/questions/860610

And yes, it was switched on... After switching it off there is an improvement: the labels of the "Enhance"-buttons now change to "in progress..." when one of them is touched. That did not happen when the popup-blocker was active.


For my use case the best practice when contentEditable is not working seems to be these steps:

  1. enter text in textarea
  2. copy text to div container (textarea can then be removed)
  3. enhance

I have no good idea what should be done when one needs to edit existing RDFa code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants