Feature #11300
Update issue - form position
Status: | Closed | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Issues | |||
Target version: | - | |||
Resolution: | Duplicate |
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?
Related issues
History
#2
Updated by # And over 10 years 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 over 10 years 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>
#6
Updated by Etienne Massip over 9 years ago
- Status changed from Resolved to New
- Assignee deleted (
Jean-Philippe Lang)
I don't think this should be done using JavaScript?
#7
Updated by # And over 9 years ago
Actually, yes. I just don't know Ruby syntax, that's why I used JS.
#8
Updated by Go MAEDA over 6 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Closing as a duplicate of #12524.