<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - TABLES text in cells behaves wrong when rotated (Shift Enter needed for line - see comment#3)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=34436#c34">Comment # 34</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - TABLES text in cells behaves wrong when rotated (Shift Enter needed for line - see comment#3)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=34436">bug 34436</a> from <a class="email" href="mailto:foberle@enteract.com" title="Frank <foberle@enteract.com>"> Frank</a> <pre>Re: "I think this is not a bug although it is confusing" Seriously? If some feature is confusing to users, particularly those experienced enough to participate in the user forums, and is recognized as confusing by a developer, that is by any reasonable definition a BUG. It's likely that the issue might not be one of coding inadequacies, but rather a lack of clear definition of what needs to happen during text entry or editing within a cell. As pointed out earlier, the specs for such a FUNDAMENTAL editing process should encompass all conditions, including the use of multiple script directions and so forth - just like normal use. HINT: ask the question: why should the process/technique of editing text within a cell be any different [from a user's perspective] from editing in the document as a whole? If the answer is developer-centric (e.g. such behaviour is harder to code within a cell) rather than user-centric, this can be considered a CLUE. Of course the excuse ("who uses that feature anyway?") can (as usual) be used to obfuscate the issue. If the feature is considered not to be useful, why not simply remove it? And I think we all know the answers (yes, plural) to that.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>