Bug 971197

Summary: Live preview renders <step> of <stepalternatives> at same level as parent <step>
Product: [Community] PressGang CCMS Reporter: mmurray
Component: Web-UIAssignee: pressgang-ccms-dev
Status: CLOSED CURRENTRELEASE QA Contact: mmurray
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.1CC: lnewson, mcaspers
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-29 07:43:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
steps of stepalternatives rendered at same level as parent step none

Description mmurray 2013-06-06 01:07:31 UTC
Created attachment 757450 [details]
steps of stepalternatives rendered at same level as parent step

Description of problem:
<stepalternatives> are a subcomponent of <step> and rendered as A, B, etc.

So for example:
<step>
  <para>Do one of these options:</para>
  <stepalternatives>
    <step><para>Option 1 is</para></step>
    <step><para>Option 2 is</para></step>
  </stepalternatives>
</step>

would render as:
3. Do one of these options:
  A. Option 1 is
  B. Option 2 is

But live preview (preview pane below editor pane) simple renders the stepalternatives as steps, so (screen capture attached):
3. Do one of these options:
4. Option 1 is
5. Option 2 is


Version-Release number of selected component (if applicable):
Build 201305221423


Actual results:
Live preview renders <steps> of <stepalternatives> at same level as parent <step> 


Expected results:
Live preview renders <steps> of <stepalternatives> at sublevel to parent <step>

Comment 1 Matthew Casperson 2013-06-28 02:36:33 UTC
Fixed in 201306281223

Rendering is now done with the publican XSL stylesheets, which fixes this issue.

NOTE:
When QAing bug fixes, please make sure the build you are using is equal to or higher than the build identified above. Be aware that this fix may have only been applied in PressGang Next at this time, or it may not be currently applied in any production system, in which case it can only be verified at a later date.

Comment 3 mmurray 2013-07-29 07:31:19 UTC
Verified in build 201307291543