4661: Email notification always restarts numbered lists in comments at 1

vsitaram 
What version are you running?


2.5.13.1


What's the URL of the page containing the problem?


N/A, internal review board link


What steps will reproduce the problem?


    

  1. Publish a new review, and then create a review comment with multiple unconnected numbered lists
    2. 

  2. For the numbered lists, start some of them at later numbers like 2, 3, 10, etc. Anything other than 1
    3. 

  3. Put someone on notification for the review (if you haven't already) and publish the comment
    4. 





What is the expected output? What do you see instead?


The email notification you receive will show the comment, including the numbered lists. But each list in the email will always start with number 1, regardless of what the actual text of the review comment shows on RB as the starting number.


What operating system are you using? What browser?


Windows 10 64-bit, Firefox 58.0.2, MS Outlook 2016




Please provide any additional information below.


Screenshot attached
#1 vsitaram 
Another example of the issue. These are also unconnected list (being manually numbered, couldn't continue from previous lists and keep the nice formatting with line breaks I needed). The RB update which shows what changed in that field displays everything as "1." to start.
david
#2 david 
Unfortunately, this is an Outlook problem. We're including the "start" parameter in the HTML to do the right thing, but Outlook (at least 2016) doesn't use it correctly.
  • -New
    +ThirdParty
#3 vsitaram 
Thanks for the response, David. I would say we can close this as third-party, but my reply #1 above shows an issue directly in RB related to review changes (and unrelated to email sent out). If you make an update to your notes (such as Testing or Notes to Reviewers sections) and publish the update, the diff shown in the review in your browser also has this issue, at least in Firefox. Seems like this kind of issue shows up in more than one place, then, and maybe it's a problem in both Outlook AND Firefox?