Yes, by "selective" I meant for highlighted/selected text--retitling to reflect it being in both cases. When you talk of seeing it elsewhere--does that include non-rich text forms (Gmail plain text compose, perhaps)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I type "Eist le mo ghlor" on the first line of a gmail message, plain text, without pressing Enter, and lift, it lifts correctly and puts the cursor at the beginning of the *next* line.
If I do the same thing in Gmail rich text, it lifts correctly and puts the cursor at the beginning of the line, at the "E" in "Eist".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does "selective accentuate" mean accentuation of highlighted/selected text? I've seen this even with the traditional accentuation of the full form.
Yes, by "selective" I meant for highlighted/selected text--retitling to reflect it being in both cases. When you talk of seeing it elsewhere--does that include non-rich text forms (Gmail plain text compose, perhaps)?
If I type "Eist le mo ghlor" on the first line of a gmail message, plain text, without pressing Enter, and lift, it lifts correctly and puts the cursor at the beginning of the *next* line.
If I do the same thing in Gmail rich text, it lifts correctly and puts the cursor at the beginning of the line, at the "E" in "Eist".
Great, thanks for the info. Bumping the priority just a bit since it's a larger UI inconsistency, though keeping targeted at 1.0 for now.