Project

General

Profile

Bug #10515

Cannot go back to the previous page on node details

Added by Raphael GAUTHIER about 2 years ago. Updated about 2 years ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Priority:
43

Description

Nothing happens when we try to go back to the previous page if we are on node details.

Associated revisions

Revision 6d3d6076 (diff)
Added by Raphaël Gauthier about 2 years ago

Fixes #10515: Cannot go back to the previous page on node details

Revision a530072d (diff)
Added by Raphaël Gauthier about 2 years ago

Fixes #10515: Cannot go back to the previous page on node details

History

#1

Updated by Raphael GAUTHIER about 2 years ago

  • Status changed from New to In progress
#2

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 4.1.0 to 4.1.1
  • Priority set to 0
#3

Updated by François ARMAND about 2 years ago

  • Target version changed from 4.1.1 to 4.0.4

So, the problem is that there is two "Rudder - search nodes" in the history. In 3.1, that was the case, but clicking two times on back was working. Since 4.0, clicking one time to bach trigger again the function that stack a second identical page in the back history, and so you can't go out of the loop. Well, actually, going back further in the history (righ click on back to have the list of recent places) works.

#4

Updated by Benoît PECCATTE about 2 years ago

  • User visibility changed from First impressions of Rudder to Getting started - demo | first install | level 1 Techniques
  • Priority changed from 0 to 43
#5

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 4.0.4 to 4.0.5
#6

Updated by Raphael GAUTHIER about 2 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1635
#7

Updated by Jonathan CLARKE about 2 years ago

  • Status changed from Pending technical review to New
  • Assignee deleted (Vincent MEMBRÉ)
#8

Updated by Jonathan CLARKE about 2 years ago

  • Status changed from New to Pending technical review
  • Assignee set to Vincent MEMBRÉ
#9

Updated by Anonymous about 2 years ago

  • Status changed from Pending technical review to Pending release
#10

Updated by Vincent MEMBRÉ about 2 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.0.5 and 4.1.2 which were released today.

Also available in: Atom PDF