You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Match editor toolbar colours to Cacti themes and keep pickers visible - #290
The editor toolbar used fixed blue colours and could have unreadable text when styled by Cacti’s theme. Use the theme’s title-row background with readable toolbar text, borders and hover states. Allow the toolbar height to follow its content.
Append autocomplete results to the active editor dialog so interface and graph pickers remain visible above the dialog. Keep enabled dialog actions readable.
Validation: all 225 plugin tests passed on PHP 8.3 in an isolated fixture installation; syntax and whitespace checks passed. The combined local Chrome audit checked the toolbar and picker layering across seven installed themes and both current/legacy dialog CSS paths. Full installation and cross-browser integration remain unverified for this branch.
Latest review follow-up
Removed the forced button text colour so native theme rules apply. Added a real jQuery UI regression invoking show_dialog() and checking autocomplete menu ownership on opening/reopening. Latest local validation: 225 PHP tests (5414 assertions), existing editor workflow and new picker-layering JavaScript checks, plus headless Chrome checks of native button text colours and menu ownership across ten isolated theme fixtures.
These follow-up checks use isolated local fixtures, not a running Cacti installation. PHP 8.3 syntax, whitespace, manifest and translation-template checks passed. GitHub CI must still confirm the revised commits.
Further review follow-up
Addressed in 1a9dc4d. Changed the toolbar to sticky positioning in normal page flow, contained its floated list with display: flow-root, and cleared the theme title-row float. Removed the fixed body/form offsets. Isolated Chrome fixtures using the actual editor toolbar markup/CSS and ten installed theme stylesheets passed at 320, 760 and 1400px widths: the form remains below the toolbar initially and after expanded help text, and the toolbar stays at the top when scrolling (90 checks). All 225 plugin tests pass (5414 assertions). This is fixture validation, not a full running-installation browser audit.
Additional review validation
Addressed the concerns in the latest Copilot review summary in 3547134. Added a scoped wm-editor-dialog class when the editor opens a dialog and overflow: visible on that wrapper. Autocomplete menus remain in the wrapper for stacking but can extend beyond its edges. The real jQuery UI ownership/reopen test passes, as do all 225 plugin tests (5414 assertions). In isolated Chrome, actual jQuery UI menus were tested across ten installed themes: a hidden-overflow rule reproduced clipping before the fix, while the fixed hidden-overflow and native-theme cases allowed hit-testing below the wrapper (30 fixtures). Menus were held open in these layout fixtures to avoid cross-frame focus closing them. This is not a complete live-installation browser audit.
Toolbar collapses because floated menu is not contained
css/editor.css:47
height: auto does not make the toolbar follow its controls because its only child, #toolbar ul, remains floated. The toolbar therefore collapses to zero content height, so the theme background applied by cactiTableTitleRow is painted only behind the border instead of behind the transparent menu items. Establish a new block formatting context so the floated list contributes to the toolbar height.
I checked the toolbar-collapse concern from the latest review summary in isolated headless Chrome fixtures using the actual editor CSS and all ten installed Cacti theme stylesheets. The existing fixed-position toolbar already contains its floated list: its measured height is 40px for dark/modern and 52px for the other eight themes, with the list fully contained in every case. Adding display: flow-root produced identical geometry in all ten fixtures. I therefore left the CSS unchanged rather than adding an unverified fix. This verifies the fixture layout, not a complete running-installation browser/theme audit; if a specific installation still shows collapse, a reproduction would help identify the differing rule.
Appending the 300px autocomplete menu inside .ui-dialog makes it subject to the dialog's clipping. Current Cacti themes such as dark, modern, sunrise, and deepness set .ui-dialog { overflow: hidden; }, so a picker near the bottom of the node/link dialog can have most of its results cut off. The new jsdom test only checks DOM ownership and cannot detect this layout failure. Please either override overflow for these editor dialogs or keep the menu outside the clipped wrapper and raise its stacking order.
Addressed the concerns in the latest Copilot review summary in 3547134. Added a scoped wm-editor-dialog class when the editor opens a dialog and overflow: visible on that wrapper. Autocomplete menus remain in the wrapper for stacking but can extend beyond its edges. The real jQuery UI ownership/reopen test passes, as do all 225 plugin tests (5414 assertions). In isolated Chrome, actual jQuery UI menus were tested across ten installed themes: a hidden-overflow rule reproduced clipping before the fix, while the fixed hidden-overflow and native-theme cases allowed hit-testing below the wrapper (30 fixtures). Menus were held open in these layout fixtures to avoid cross-frame focus closing them. This is not a complete live-installation browser audit.
Resolved the CHANGELOG.md conflict with current develop in 781fe22, retaining one issue#290 entry. The editor theme and picker fixes remain intact. All 229 local PHP tests pass (5438 assertions), along with the real jQuery UI picker reopening regression, editor workflow check, manifest and whitespace checks. These are isolated fixture checks; full-installation cross-browser verification remains outstanding.
Resolved the new CHANGELOG.md conflict after #298 merged into develop. Both changelog entries are preserved; the editor theme and picker changes remain intact. All 230 local tests pass (5461 assertions), and the real jQuery UI picker reopening regression, editor syntax, manifest and whitespace checks pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The editor toolbar used fixed blue colours and could have unreadable text when styled by Cacti’s theme. Use the theme’s title-row background with readable toolbar text, borders and hover states. Allow the toolbar height to follow its content.
Append autocomplete results to the active editor dialog so interface and graph pickers remain visible above the dialog. Keep enabled dialog actions readable.
Validation: all 225 plugin tests passed on PHP 8.3 in an isolated fixture installation; syntax and whitespace checks passed. The combined local Chrome audit checked the toolbar and picker layering across seven installed themes and both current/legacy dialog CSS paths. Full installation and cross-browser integration remain unverified for this branch.
Latest review follow-up
Removed the forced button text colour so native theme rules apply. Added a real jQuery UI regression invoking show_dialog() and checking autocomplete menu ownership on opening/reopening. Latest local validation: 225 PHP tests (5414 assertions), existing editor workflow and new picker-layering JavaScript checks, plus headless Chrome checks of native button text colours and menu ownership across ten isolated theme fixtures.
These follow-up checks use isolated local fixtures, not a running Cacti installation. PHP 8.3 syntax, whitespace, manifest and translation-template checks passed. GitHub CI must still confirm the revised commits.
Further review follow-up
Addressed in 1a9dc4d. Changed the toolbar to sticky positioning in normal page flow, contained its floated list with display: flow-root, and cleared the theme title-row float. Removed the fixed body/form offsets. Isolated Chrome fixtures using the actual editor toolbar markup/CSS and ten installed theme stylesheets passed at 320, 760 and 1400px widths: the form remains below the toolbar initially and after expanded help text, and the toolbar stays at the top when scrolling (90 checks). All 225 plugin tests pass (5414 assertions). This is fixture validation, not a full running-installation browser audit.
Additional review validation
Addressed the concerns in the latest Copilot review summary in 3547134. Added a scoped wm-editor-dialog class when the editor opens a dialog and overflow: visible on that wrapper. Autocomplete menus remain in the wrapper for stacking but can extend beyond its edges. The real jQuery UI ownership/reopen test passes, as do all 225 plugin tests (5414 assertions). In isolated Chrome, actual jQuery UI menus were tested across ten installed themes: a hidden-overflow rule reproduced clipping before the fix, while the fixed hidden-overflow and native-theme cases allowed hit-testing below the wrapper (30 fixtures). Menus were held open in these layout fixtures to avoid cross-frame focus closing them. This is not a complete live-installation browser audit.