Actions
Bug #24405
closed
Node tabs have onclick event handlers assigned on unrendered elements
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
It bothers me each time
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Priority:
97
Name check:
To do
Fix check:
To do
Regression:
No
Description
Some event handlers for buttons like Show logs buttons in compliance and system status tabs are not assigned correctly :
They are assigned before the HTML tree for the tab is even rendered, so the button will not have the additional onclick handlers we assigned to them.
Updated by Clark ANDRIANASOLO about 2 months ago
- Related to Bug #24383: Show logs button in node compliance tab does nothing added
- Related to Bug #24015: Use Content-Security-Policy strict headers added
Updated by Clark ANDRIANASOLO about 2 months ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO about 2 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder/pull/5463
Updated by François ARMAND about 2 months ago
- Related to Bug #24430: Visible lag when changing tab of node details added
Updated by Clark ANDRIANASOLO about 2 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|793a058b463c202c43b7c25c17637be2231412da.
Updated by Vincent MEMBRÉ about 2 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.1.0~beta2 which was released today.
Actions