Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-01-16 15:23:46 +0200

text editing in browser is crippled

Placing the cursor in a text field on a web page brings up the keyboard, but writing text here is very crippled, because it doesn't go into proper editing mode, just four plain rows of keys. This means: - predictions turned off - no zoom-in cursor placement - no clipboard (copy/paste) I'm guessing this was done because of wanting to keep the page visible while typing instead of covering the whole screen with a text editor, and maybe it's difficult to program the full-featured text editor into the browser? IMO that is too high a price to pay, reverting to vkb from the stone age just for keeping the page visible. Trying to write out a post like this on a web page just makes you want to put yr Jolla away, and so does using webmail. And a workaround like typing in a notes app and then pasting into browser is not possible. no clipboard, remember?

text editing in browser is crippled

Placing the cursor in a text field on a web page brings up the keyboard, but writing text here is very crippled, because it doesn't go into proper editing mode, just four plain rows of keys. This means: - predictions turned off - no zoom-in cursor placement - no clipboard (copy/paste) I'm guessing this was done because of wanting to keep the page visible while typing instead of covering the whole screen with a text editor, and maybe it's difficult to program the full-featured text editor into the browser? IMO that is too high a price to pay, reverting to vkb from the stone age just for keeping the page visible. Trying to write out a post like this on a web page just makes you want to put yr Jolla away, and so does using webmail. And a workaround like typing in a notes app and then pasting into browser is not possible. no clipboard, remember?

text editing in browser is crippled

Placing the cursor in a text field on a web page brings up the keyboard, but writing text here is very crippled, because it doesn't go into proper editing mode, just four plain rows of keys. This means: - predictions turned off - no zoom-in cursor placement - no clipboard (copy/paste) I'm guessing this was done because of wanting to keep the page visible while typing instead of covering the whole screen with a text editor, and maybe it's difficult to program the full-featured text editor into the browser? IMO that is too high a price to pay, reverting to vkb from the stone age just for keeping the page visible. Trying to write out a post like this on a web page just makes you want to put yr Jolla away, and so does using webmail. And a workaround like typing in a notes app and then pasting into browser is not possible. no clipboard, remember?

text editing in browser is crippled

Placing the cursor in a text field on a web page brings up the keyboard, but writing text here is very crippled, because it doesn't go into proper editing mode, just four plain rows of keys. This means: - predictions turned off - no zoom-in cursor placement - no clipboard (copy/paste) I'm guessing this was done because of wanting to keep the page visible while typing instead of covering the whole screen with a text editor, and maybe it's difficult to program the full-featured text editor into the browser? IMO that is too high a price to pay, reverting to vkb from the stone age just for keeping the page visible. Trying to write out a post like this on a web page just makes you want to put yr Jolla away, and so does using webmail. And a workaround like typing in a notes app and then pasting into browser is not possible. no clipboard, remember?

text editing in browser is crippledlacking features

Placing the cursor in a text field on a web page brings up the keyboard, but writing text here is very crippled, because it doesn't go into proper editing mode, just four plain rows of keys. This means: - predictions turned off - no zoom-in cursor placement - no clipboard (copy/paste) I'm guessing this was done because of wanting to keep the page visible while typing instead of covering the whole screen with a text editor, and maybe it's difficult to program the full-featured text editor into the browser? IMO that is too high a price to pay, reverting to vkb from the stone age just for keeping the page visible. Trying to write out a post like this on a web page just makes you want to put yr Jolla away, and so does using webmail. And a workaround like typing in a notes app and then pasting into browser is not possible. no clipboard, remember?

text editing in browser is lacking features

Placing the cursor in a text field on a web page brings up the keyboard, but writing text here is very crippled, because it doesn't go into proper editing mode, just four plain rows of keys. This means: - predictions turned off - no zoom-in cursor placement - no clipboard (copy/paste) I'm guessing this was done because of wanting to keep the page visible while typing instead of covering the whole screen with a text editor, and maybe it's difficult to program the full-featured text editor into the browser? IMO that is too high a price to pay, reverting to vkb from the stone age just for keeping the page visible. Trying to write out a post like this on a web page just makes you want to put yr Jolla away, and so does using webmail. And a workaround like typing in a notes app and then pasting into browser is not possible. possible, because no clipboard, remember?clipboard.

text editing in browser is lacking features

Placing the cursor in a text field on a web page brings up the keyboard, but writing text here is very crippled, because it doesn't go into proper editing mode, just four plain rows of keys. This means: - means:

  • predictions turned off - off
  • no zoom-in cursor placement - placement
  • no clipboard (copy/paste) (copy/paste)

I'm guessing this was done because of wanting to keep the page visible while typing instead of covering the whole screen with a text editor, and maybe it's difficult to program the full-featured text editor into the browser? IMO that is too high a price to pay, reverting to vkb from the stone age just for keeping the page visible. Trying to write out a post like this on a web page just makes you want to put yr Jolla away, and so does using webmail. And a workaround like typing in a notes app and then pasting into browser is not possible, because no clipboard.

text editing in browser is lacking features

Placing the cursor in a text field on a web page brings up the keyboard, but writing text here is very crippled, because it doesn't go into proper editing mode, just four plain rows of keys. This means:

  • predictions turned offoff (fixed in update 10)
  • no zoom-in cursor placement
  • no clipboard (copy/paste)(copy/paste) (paste added in update 10, still no copy)

I'm guessing this was done because of wanting to keep the page visible while typing instead of covering the whole screen with a text editor, and maybe it's difficult to program the full-featured text editor into the browser? IMO that is too high a price to pay, reverting to vkb from the stone age just for keeping the page visible. Trying to write out a post like this on a web page just makes you want to put yr Jolla away, and so does using webmail. And a workaround like typing in a notes app and then pasting into browser is not possible, because no clipboard.

text editing in browser is lacking features

Placing the cursor in a text field on a web page brings up the keyboard, but writing text here is very crippled, because it doesn't go into proper editing mode, just four plain rows of keys. This means:

  • predictions turned off (fixed in update 10)
  • no zoom-in cursor placement
  • no clipboard (copy/paste) (paste added in update 10, still no copy)

I'm guessing this was done because of wanting to keep the page visible while typing instead of covering the whole screen with a text editor, and maybe it's difficult to program the full-featured text editor into the browser? IMO that is too high a price to pay, reverting to vkb from the stone age just for keeping the page visible. Trying to write out a post like this on a web page just makes you want to put yr Jolla away, and so does using webmail. And a workaround like typing in a notes app and then pasting into browser is not possible, because no clipboard.webmail.

text editing in browser is lacking features

Placing the cursor in a text field on a web page brings up the keyboard, but writing text here is very crippled, because it doesn't go into proper editing mode, just four plain rows of keys. This means:

  • predictions turned off (fixed in update 10)
  • no zoom-in cursor placement
  • no clipboard (copy/paste) (paste added in update 10, still no copy)

I'm guessing this was done because of wanting to keep the page visible while typing instead of covering the whole screen with a text editor, and maybe it's difficult to program the full-featured text editor into the browser? IMO that is too high a price to pay, reverting to vkb from the stone age just for keeping the page visible. Trying to write out a post like this on a web page just makes you want to put yr Jolla away, and so does using webmail.

text editing in browser is lacking features

Placing the cursor in a text field on a web page brings up the keyboard, but writing text here is very crippled, because it doesn't go into proper editing mode, just four plain rows of keys. This means:

  • predictions turned off (fixed in update 10)
  • no zoom-in cursor placement
  • no clipboard (copy/paste) (paste added in update 10, still no copy)

I'm guessing this was done because of wanting to keep the page visible while typing instead of covering the whole screen with a text editor, and maybe it's difficult to program the full-featured text editor into the browser? IMO that is too high a price to pay, reverting to vkb from the stone age just for keeping the page visible. Trying to write out a post like this on a web page just makes you want to put yr Jolla away, and so does using webmail.