Return to Question

##Background On mobile precise positioning of the cursor is extremely difficult. When entering a spelling mistake I will usually delete the entire word and retype rather than trying to select the mistake itself. Sometimes deleting an entire sentence and retyping is easier than repositioning the cursor.

##The Bug When entering a comment on the mobile version of the site if the line is exactly a line long then the space (between words) is not recognised.

For example if I type (as a comment on a question, answer comments are a different length)

This seems like a good sentence to test the irritating system[SPACE]

Then the space is not recognised (how ever many spaces I add) and so the first word of the next line is run together with the last word of the first line, so

This seems like a good sentence to test the irritating systemwhich

After the word has fallen onto the next line I can go back and reinsert the space as a work around. However; as I say precise positioning on a phone is extremely difficult

Reproducing this bug seems very sensitive to the line being exactly one line long. I had to experiment with long letters (like 'w') and short letters (like 'f') to get it exactly right. My test sentence quoted above is likely to be dependant on my screen size.

Results so far:

ANDROID
Galaxy s3
Standard Android Browser: exhibits bug - reported by R Tingle & Rory Alsop
Dolphine browser: exhibits bug
Chrome: no bug

Galaxy S2
Standard Android Browser: exhibits bug*

Galaxy S1
Standard Android Browser: exhibits bug - reported by yuvi

*In the case of the Galaxy S2 the space appears to "hold", ending up at the end of the line. But on starting the next word the space disappears

WINDOWS PHONE
Lumia 800
Standard Windows Phone browser: no bug

APPLE
Ipad
Recent Model: exhibits bug - reported by Rory Alsop

Background

On mobile precise positioning of the cursor is extremely difficult. When entering a spelling mistake I will usually delete the entire word and retype rather than trying to select the mistake itself. Sometimes deleting an entire sentence and retyping is easier than repositioning the cursor.

The Bug

When entering a comment on the mobile version of the site if the line is exactly a line long then the space (between words) is not recognised.

For example if I type (as a comment on a question, answer comments are a different length)

This seems like a good sentence to test the irritating system[SPACE]

Then the space is not recognised (how ever many spaces I add) and so the first word of the next line is run together with the last word of the first line, so

This seems like a good sentence to test the irritating systemwhich

After the word has fallen onto the next line I can go back and reinsert the space as a work around. However; as I say precise positioning on a phone is extremely difficult

Reproducing this bug seems very sensitive to the line being exactly one line long. I had to experiment with long letters (like 'w') and short letters (like 'f') to get it exactly right. My test sentence quoted above is likely to be dependant on my screen size.

Results so far:

ANDROID
Galaxy s3
Standard Android Browser: exhibits bug - reported by R Tingle & Rory Alsop
Dolphine browser: exhibits bug
Chrome: no bug

Galaxy S2
Standard Android Browser: exhibits bug*

Galaxy S1
Standard Android Browser: exhibits bug - reported by yuvi

*In the case of the Galaxy S2 the space appears to "hold", ending up at the end of the line. But on starting the next word the space disappears

WINDOWS PHONE
Lumia 800
Standard Windows Phone browser: no bug

APPLE
Ipad
Recent Model: exhibits bug - reported by Rory Alsop

When entering a comment on the mobile version of the site if the line is exactly a line long then the space (between words) is not recognised.

For example if I type (as a comment on a question, answer comments are a different length)

This seems like a good sentence to test the irritating system[SPACE]

Then the space is not recognised (how ever many spaces I add) and so the first word of the next line is run together with the last word of the first line, so

This seems like a good sentence to test the irritating systemwhich

After the word has fallen onto the next line I can go back and reinsert the space as a work around. This is more irritating than you'd imagine on a mobile browser where precisely selecting a letter is very difficult.

Reproducing this bug seems very sensitive to the line being exactly one line long. I had to experiment with long letters (like 'w') and short letters (like 'f') to get it exactly right. My test sentence quoted above is likely to be dependant on my screen size.

Results so far:

ANDROID
Galaxy s3
Standard Android Browser: exhibits bug - reported by R Tingle & Rory Alsop
Dolphine browser: exhibits bug
Chrome: no bug

Galaxy S2
Standard Android Browser: exhibits bug*

Galaxy S1
Standard Android Browser: exhibits bug - reported by yuvi

*with example sentence "This is an example sentence on the galaxy s2. Abcffrr[SPACE]" In this case the space appears to "hold", ending up at the end of the line. But on starting the next word the space disappears

WINDOWS PHONE
Lumia 800
Standard Windows Phone browser: no bug

APPLE
Ipad
Recent Model: exhibits bug - reported by Rory Alsop

##Background On mobile precise positioning of the cursor is extremely difficult. When entering a spelling mistake I will usually delete the entire word and retype rather than trying to select the mistake itself. Sometimes deleting an entire sentence and retyping is easier than repositioning the cursor.

##The Bug When entering a comment on the mobile version of the site if the line is exactly a line long then the space (between words) is not recognised.

For example if I type (as a comment on a question, answer comments are a different length)

This seems like a good sentence to test the irritating system[SPACE]

Then the space is not recognised (how ever many spaces I add) and so the first word of the next line is run together with the last word of the first line, so

This seems like a good sentence to test the irritating systemwhich

After the word has fallen onto the next line I can go back and reinsert the space as a work around. However; as I say precise positioning on a phone is extremely difficult

Reproducing this bug seems very sensitive to the line being exactly one line long. I had to experiment with long letters (like 'w') and short letters (like 'f') to get it exactly right. My test sentence quoted above is likely to be dependant on my screen size.

Results so far:

ANDROID
Galaxy s3
Standard Android Browser: exhibits bug - reported by R Tingle & Rory Alsop
Dolphine browser: exhibits bug
Chrome: no bug

Galaxy S2
Standard Android Browser: exhibits bug*

Galaxy S1
Standard Android Browser: exhibits bug - reported by yuvi

*In the case of the Galaxy S2 the space appears to "hold", ending up at the end of the line. But on starting the next word the space disappears

WINDOWS PHONE
Lumia 800
Standard Windows Phone browser: no bug

APPLE
Ipad
Recent Model: exhibits bug - reported by Rory Alsop

When entering a comment on the mobile version of the site if the line is exactly a line long then the space (between words) is not recognised.

For example if I type (as a comment on a question, answer comments are a different length)

This seems like a good sentence to test the irritating system[SPACE]

Then the space is not recognised (how ever many spaces I add) and so the first word of the next line is run together with the last word of the first line, so

This seems like a good sentence to test the irritating systemwhich

After the word has fallen onto the next line I can go back and reinsert the space as a work around. This is more irritating than you'd imagine on a mobile browser where precisely selecting a letter is very difficult.

Reproducing this bug seems very sensitive to the line being exactly one line long. I had to experiment with long letters (like 'w') and short letters (like 'f') to get it exactly right. My test sentence quoted above is likely to be dependant on my screen size.

Results so far:

ANDROID
Galaxy s3
Standard Android Browser: exhibits bug - reported by R Tingle & Rory Alsop
Dolphine browser: exhibits bug
Chrome: no bug

Galaxy S2
Standard Android Browser: exhibits bug*

*with example sentence "This is an example sentence on the galaxy s2. Abcffrr[SPACE]" In this case the space appears to "hold", ending up at the end of the line. But on starting the next word the space disappears

WINDOWS PHONE
Lumia 800
Standard Windows Phone browser: no bug

APPLE
Ipad
Recent Model: exhibits bug - reported by Rory Alsop

When entering a comment on the mobile version of the site if the line is exactly a line long then the space (between words) is not recognised.

For example if I type (as a comment on a question, answer comments are a different length)

This seems like a good sentence to test the irritating system[SPACE]

Then the space is not recognised (how ever many spaces I add) and so the first word of the next line is run together with the last word of the first line, so

This seems like a good sentence to test the irritating systemwhich

After the word has fallen onto the next line I can go back and reinsert the space as a work around. This is more irritating than you'd imagine on a mobile browser where precisely selecting a letter is very difficult.

Reproducing this bug seems very sensitive to the line being exactly one line long. I had to experiment with long letters (like 'w') and short letters (like 'f') to get it exactly right. My test sentence quoted above is likely to be dependant on my screen size.

Results so far:

ANDROID
Galaxy s3
Standard Android Browser: exhibits bug - reported by R Tingle & Rory Alsop
Dolphine browser: exhibits bug
Chrome: no bug

Galaxy S2
Standard Android Browser: exhibits bug*

Galaxy S1
Standard Android Browser: exhibits bug - reported by yuvi

*with example sentence "This is an example sentence on the galaxy s2. Abcffrr[SPACE]" In this case the space appears to "hold", ending up at the end of the line. But on starting the next word the space disappears

WINDOWS PHONE
Lumia 800
Standard Windows Phone browser: no bug

APPLE
Ipad
Recent Model: exhibits bug - reported by Rory Alsop