Project

General

Profile

Actions

Feature #11300

closed

Update issue - form position

Added by # And over 12 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
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?


Files

form_position.patch (1.3 KB) form_position.patch # And, 2012-09-30 22:57

Related issues

Copied to Redmine - Patch #12524: Update issue - form positionClosed

Actions
Actions #1

Updated by # And over 12 years ago

  • Assignee set to Jean-Philippe Lang

Hey, anyone? =)

Actions #2

Updated by # And over 12 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>

Actions #3

Updated by # And over 12 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>
Actions #4

Updated by # And about 12 years ago

Added patch to Redmine 2.1.0.

Actions #5

Updated by # And almost 12 years ago

  • Status changed from New to Resolved

Moved to #12524

Actions #6

Updated by Etienne Massip about 11 years ago

  • Status changed from Resolved to New
  • Assignee deleted (Jean-Philippe Lang)

I don't think this should be done using JavaScript?

Actions #7

Updated by # And about 11 years ago

Actually, yes. I just don't know Ruby syntax, that's why I used JS.

Actions #8

Updated by Go MAEDA over 8 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Closing as a duplicate of #12524.

Actions

Also available in: Atom PDF