We’ve completed our API Workflow for FWM_Super. We’ve just completed our SEP26 financials, so will be using SEP26 values are our basis.
As for UX and design, we’ve initially decided to use the bullet chart format with line markers, but the UI for the line markers turned out to be harder to create due to its width and scaling limitations on the HTML layout. AI hallucinated more than once during our testing. Instead, we’ve decided to use the horizontal bar with multi-colored segments. Creating this in chart.js isn’t necessary as the horizontal bar with muti-colored segments work well visually. In addition, we’ve embedded the TMV$ value in the horizontal bar itself. As for TC$ and Tar$, due to its variable change on their amount and calculated based on TMV$, we’ve decided to use mouse hovering tooltip showing its labeling and values for UX purposes.
As we’ve deployed several versions during our testing, we’re currently low on our credits so our model will remain private until the next cycle when the deployment credits reset. In the meantime, we’ll continue to work and test to see if the UI or UX needs to be changed.
This FWM_Super Widget will have it’s own API URL in the main deployment.
We’ve snipped these three Funds as each UI has different views.
WBC (FWM_Super)(SEP26) / ROBO (FWM_Super)(SEP26) /
// UX Updates as of 7-OCT-26 //
Summary Overview
Goal: Replace custom, absolute‑positioned dropdowns with native <select> elements while preserving HUD panel styling and all non‑dropdown code.
Outcome: Native selects implemented for Fund and Period; custom dropdown HTML/CSS/JS removed; HUD visuals and chart logic preserved.
What we used from your existing CSS/HTML
HUD panel layout and visual styles — card backgrounds, borders, shadows, spacing, typography.
Header structure and labels — placement and wording for Fund and Period.
Chart SVG and tooltip — all SVG elements, filters, and tooltip logic left intact.
API fetch and data parsing — the existing data source and parsing logic remain unchanged.
General utility CSS — body, dashboard, card, chart wrapper, and tooltip styling retained.
What we replaced or removed (dropdown‑specific)
Removed custom dropdown HTML — all .hud-select wrapper elements and their inline SVG chevrons.
Removed custom dropdown containers — .hud-dropdown elements used for absolute‑positioned menus.
Removed absolute positioning rules — CSS that positioned dropdowns with position: absolute and fixed offsets.
Removed custom toggle JS — click handlers that showed/hidden .hud-dropdown and the global document click close handler.
Removed dynamic DIV menu building — code that created menu items as <div> elements inside custom containers.
Removed icon anchoring logic — any reliance on a chevron wrapper for anchoring the menu.
What we added or introduced (dropdown‑specific)
Native select elements for Fund and Period using the existing header placement.
A single HUD‑matching select style class to visually integrate native selects with the HUD aesthetic.
Select population function that fills <option> elements from the fetched data.
Select change handler that reads both selects and calls the existing updatePanel logic to refresh the chart.
No new absolute positioning or custom menu containers — browser handles menu rendering and placement.
UX and accessibility impact (concise)
Stability: Eliminates layout drift and misalignment caused by flex spacing and inline SVGs.
Consistency: Native dropdowns render and behave consistently across browsers and platforms.
Accessibility: Keyboard navigation, screen‑reader support, and native focus behavior are preserved.
Maintenance: Less custom code to maintain and fewer edge cases to debug.
What was intentionally preserved unchanged
All HUD visual styling outside dropdown rules.
Bullet chart SVG, glow filters, and tooltip behavior.
API endpoint, data parsing, and update math.
Overall page structure and non‑dropdown JavaScript.