You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem? 1. Install a vanilla Textpattern 4.5.2
2. Leave a comment on article #1
3. View the comment in the admin backend What is the expected output? What do you see instead? - The default system-created comment (000001) has no leading tab stop before the
The user-created comment (000002) has a leading tab stop before the
What version of the product are you using? On what operating system? - Textpattern 4.5.2 on OS X 10.7 and CentOS 5. Please provide any additional information below. - This is a minor presentational glitch. It affects admin-side operations only and I haven't yet found any impact on front-of-house proceedings.
From gaek...@gmail.com on October 30, 2012 13:03:59
What steps will reproduce the problem? 1. Install a vanilla Textpattern 4.5.2
2. Leave a comment on article #1
3. View the comment in the admin backend What is the expected output? What do you see instead? - The default system-created comment (000001) has no leading tab stop before the
What version of the product are you using? On what operating system? - Textpattern 4.5.2 on OS X 10.7 and CentOS 5. Please provide any additional information below. - This is a minor presentational glitch. It affects admin-side operations only and I haven't yet found any impact on front-of-house proceedings.
Screencast: http://youtu.be/rnjSXRISRuY
Original issue: http://code.google.com/p/textpattern/issues/detail?id=303
The text was updated successfully, but these errors were encountered: