Feature #11300
Update issue - form position
| Status: | Resolved | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Jean-Philippe Lang | % Done: | 0% | |
| Category: | Issues | |||
| Target version: | - | |||
| Resolution: |
Description
I personally use "Reverse chronological order", so latest updates are top located. It is very inconvenient to get a update form at bottom, while latest update in top.
Is this issue but or feature?
form_position.patch 
(1.3 KB)
Related issues
History
#2 Updated by # And 10 months ago
I resolve it myself. Add, please, code to repository:
<script type="text/javascript">
(function(){
var reverseOrder = <%= User.current.wants_comments_in_reverse_order? %>,
historyElement = $('history'),
updateElement = $('update');
if (reverseOrder && historyElement) {
// Add br-element at bottom of update for to simulate some margin from journals
updateElement.insert({ bottom: new Element('br') });
// Inject before journals
historyElement.insert({ before: updateElement });
}
})();
</script>
#3 Updated by # And 10 months ago
Here it code update.
<script type="text/javascript">
(function(){
var reverseOrder = <%= User.current.wants_comments_in_reverse_order? %>,
historyElement = $('history'),
updateElement = $('update');
if (reverseOrder && historyElement) {
// Add br-element at bottom of update for to simulate some margin from journals
// and apply css-clear-property to break some long commit lists
updateElement.insert({ bottom: new Element('br') }).setStyle({ clear: 'both' });
// Inject before journals
historyElement.insert({ before: updateElement });
}
})();
</script>