Description of problem:
When you use the new templates editor, trying to edit and preview template changes is quite unergonomic.
Version-Release number of selected component (if applicable):
Sat 6.7 Snap 5
Steps to Reproduce:
1. Have a host registered to the Satellite server, and set as managed in All Hosts -> <host> -> Edit
2. Create a clone of a template in Hosts -> Provisioning Templates. I used the "Kickstart Default" template.
3. Open the template. The new template editor will open.
4. Scroll to the end of the template. Note the number of the last line. The "Kickstart Default" template has 295 lines as of today.
5. Switch to the Preview tab. You will see a preview of the kickstart file generated from the template for the host registered in the step 1. As the resulting file is usually shorter than the template, the number of lines in the kickstart file will be lower than number of lines in the template. In my case, it was 219.
6. Now switch back to the editor tab. You are not at the end of the file (line 295) anymore, but at the line with the same number as the last line in the kickstart file preview (219).
7. When you scroll to any line in the editor or preview tab, when you switch tabs, the other tab will be scrolled to the same line (or to the end of the file, if there is not enough lines).
The editor and preview areas keep "in sync" regarding the line number currently displayed. That means user editing the template has to scroll all the time to get back to the line he actually wants to edit, and then scroll again to the line displaying the generated text. This makes editing and checking the output preview at the same time virtually impossible.
Editor and preview areas can be scrolled independently of each other, and each remembers its last displayed line.
Created redmine issue https://projects.theforeman.org/issues/28624 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28624 has been resolved.
the tabs are no longer synced and remember their own pointer positions.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.