<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body><a class="email" href="mailto:gtimur@gmail.com" title="Timur <gtimur@gmail.com>"> Timur</a> changed <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Editing: Numbering restarts from 1 where it should continue from previous list" href="https://bugs.documentfoundation.org/show_bug.cgi?id=117233">bug 117233</a> <table border="1" cellspacing="0" cellpadding="8"> <tr> <th>What</th> <th>Removed</th> <th>Added</th> </tr> <tr> <td style="text-align:right;">Keywords</td> <td> </td> <td>needsUXEval </td> </tr> <tr> <td style="text-align:right;">Version</td> <td>6.0.2.1 release </td> <td>Inherited From OOo </td> </tr></table> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Editing: Numbering restarts from 1 where it should continue from previous list" href="https://bugs.documentfoundation.org/show_bug.cgi?id=117233#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Editing: Numbering restarts from 1 where it should continue from previous list" href="https://bugs.documentfoundation.org/show_bug.cgi?id=117233">bug 117233</a> from <a class="email" href="mailto:gtimur@gmail.com" title="Timur <gtimur@gmail.com>"> Timur</a> <pre>OK, let's clear this out here and open a documentation bug separately. > There are two things for us to consider: > 1. When you select top-down, is it correct that numbering restarts at 1 > *without* the Restart numbering property of the fourth paragraph being set? > Apparently, there is another, hidden property of the fourth paragraph that > makes the numbering restart. To get a better overview, after step 2. change Numbering type. It's not just restart at 1, it's another, different list. So that may explain Step 4. >And the behavior in my Step 6 is also not right in my opinion. Makes sense. Looks it's again the same problem of different lists. > Is this the only place in LO where selection direction makes a difference? Can't give a list. But yes, like for deleting a text and writing new with track changes. > Should we make this difference? At least for me it led to unexpected > behavior. I agree, it is kind of neat when you know the difference, when you > are a heavy user. But I would venture to say that most users won't and even > a tool tip won't change that significantly. Let's hear others. > Maybe someone has an idea how we could make the behavior simpler and > more obvious, maybe some nice visual cue. For example, there could be a > handle at the end of the previous numbered set that could be pulled down > across the following paras to create consecutive numbers. Adding needsUXEval here. What's reported here looks intuitive without additional options and it's MS style. LO had current behavior all the way from OO and it gives more options. Like, continue previous numbering just for selected paras and keep others as they were. This change would be substantial, even if accepted.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>