Compare commits
No commits in common. "47058d2b2710ad1b82c1f70357b263e96ca90107" and "3cd491eaf69d3415e9fd070fec7ff08bc4a458d5" have entirely different histories.
47058d2b27
...
3cd491eaf6
@ -1 +1 @@
|
|||||||
v20260112-16-runchecks-popup-objects-no-overlap
|
v20260112-15-vspc-scroll-partial-approve-objects
|
||||||
|
|||||||
@ -144,22 +144,9 @@
|
|||||||
overflow: auto;
|
overflow: auto;
|
||||||
}
|
}
|
||||||
|
|
||||||
#runChecksModal #rcm_body_iframe {
|
#runChecksModal #rcm_body_iframe { height: 100%; }
|
||||||
flex: 1 1 auto;
|
#runChecksModal .rcm-mail-panel { flex: 1 1 auto; min-height: 0; }
|
||||||
min-height: 0;
|
#runChecksModal .rcm-objects-scroll { max-height: 25vh; overflow: auto; }
|
||||||
height: auto;
|
|
||||||
}
|
|
||||||
#runChecksModal .rcm-mail-panel {
|
|
||||||
display: flex;
|
|
||||||
flex-direction: column;
|
|
||||||
flex: 1 1 auto;
|
|
||||||
min-height: 0;
|
|
||||||
}
|
|
||||||
#runChecksModal .rcm-objects-scroll {
|
|
||||||
max-height: 25vh;
|
|
||||||
overflow: auto;
|
|
||||||
margin-top: 0.5rem;
|
|
||||||
}
|
|
||||||
</style>
|
</style>
|
||||||
|
|
||||||
<div class="modal fade" id="runChecksModal" tabindex="-1" aria-labelledby="runChecksModalLabel" aria-hidden="true">
|
<div class="modal fade" id="runChecksModal" tabindex="-1" aria-labelledby="runChecksModalLabel" aria-hidden="true">
|
||||||
@ -1180,4 +1167,4 @@ if (tStatus) tStatus.textContent = '';
|
|||||||
updateButtons();
|
updateButtons();
|
||||||
})();
|
})();
|
||||||
</script>
|
</script>
|
||||||
{% endblock %}
|
{% endblock %}
|
||||||
|
|||||||
@ -229,13 +229,6 @@
|
|||||||
- Improved VSPC error detection by treating both “Error” and “Failed” states as errors for the run status.
|
- Improved VSPC error detection by treating both “Error” and “Failed” states as errors for the run status.
|
||||||
- Enhanced VSPC parsing to use the “Alarm Details” column so object rows (e.g., HV01, USB Disk) persist with their full alarm messages and become visible in the customer job view.
|
- Enhanced VSPC parsing to use the “Alarm Details” column so object rows (e.g., HV01, USB Disk) persist with their full alarm messages and become visible in the customer job view.
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v20260112-16-runchecks-popup-objects-no-overlap
|
|
||||||
|
|
||||||
- Fixed layout issue in the Run Checks popup where the Objects table could overlap the mail content.
|
|
||||||
- Adjusted container sizing and overflow handling to ensure the Objects table stays within its designated area.
|
|
||||||
- Ensured the mail content and Objects table are visually separated and cannot overlap regardless of content length.
|
|
||||||
================================================================================================================================================
|
================================================================================================================================================
|
||||||
## v0.1.19
|
## v0.1.19
|
||||||
This release delivers a broad set of improvements focused on reliability, transparency, and operational control across mail processing, administrative auditing, and Run Checks workflows. The changes aim to make message handling more robust, provide better insight for administrators, and give operators clearer and more flexible control when reviewing backup runs.
|
This release delivers a broad set of improvements focused on reliability, transparency, and operational control across mail processing, administrative auditing, and Run Checks workflows. The changes aim to make message handling more robust, provide better insight for administrators, and give operators clearer and more flexible control when reviewing backup runs.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user