Known issues.
What we know is wrong, inconsistent or unfinished in Sprout — in the components, the documentation and the MCP server. If you hit something on this list, it is not you. If you hit something that is not on it, tell us.
Open
Confirmed. The fix is agreed but has not shipped.
The parseNordic example accepts input the real component rejects
DocumentationOpenThe parsing example on the Numeric input page turns "1.234,56" into 1.234 and "12abc" into 12. The shipped AceveNumericInput rejects both. The example should use the component's own parseNumeric. Related: the component does not accept a pasted "1 234,56" with a grouping space, which the page says it should. Open the page →
Danish thousands separator is described wrongly
DocumentationOpenThe Data grid page says Swedish, Danish and Norwegian all group thousands with a space. Danish uses a full stop (4.218,00). The currency example next to it also reads as if changing locale converts the currency, which it does not. Open the page →
Read-only grid cells are specified in a colour that fails contrast
AccessibilityOpenRead-only cells use the disabled text colour, about 2.2:1 in both themes. The page justifies it with the WCAG exception for inactive controls, but a read-only cell can be focused and copied, so the exception does not apply. This is a specification issue only — no grid component ships. Open the page →
Success and danger hover colours on the Color page differ from the tokens
TokensOpenThe Color page shows #0e7c45 and #b94730 for the hovered states. The token package has #0b6739 and #993a28. The page should read the values from the tokens instead of repeating them by hand. Open the page →
Toggle button guidance combines aria-pressed with a changing label
DocumentationOpenThe Buttons page shows aria-pressed together with a Mute / Unmute label. A toggle should use one or the other: a fixed label with aria-pressed, or a label that changes and no aria-pressed. Open the page →
WCAG AA is worded as a verified fact rather than a requirement
AccessibilityOpenOne rule says every Aceve product meets AA, no exceptions. That is the floor we require, not something that has been measured for every product. The wording should be "must meet". Open the page →
The Contribute page gives an outdated icon count
DocumentationOpenIt says 297 icons. The set has 566 (338 outlined, 228 solid). Open the page →
Copying a primitive needs more than the file, and that is not written down
DocumentationOpenThe React primitives rely on CSS variables defined in this site's stylesheet (such as --canvas), on the .aceve-btn classes, and on the site's Icon component. A team that copies only the .jsx file gets an unstyled component. The dependencies should be listed on the Connect page. Open the page →
Icon search has no synonyms
MCPOpenSearching for "settings" returns nothing; the icon is called gear-1. Tags are just the icon name split into words, so any search by meaning fails. Synonyms need to come from the token package or from an alias map in the MCP server. Open the page →
MCP tools report invalid input as a successful reply
MCPOpenA tool that cannot resolve its input returns a normal result containing an error field, without marking the call as failed. A "no match, here are suggestions" reply is fine that way; genuinely invalid input should be flagged as an error. Open the page →
Control heights do not line up across components
TokensOpenInputs are 24 / 32 / 40px, buttons are 28 / 38 / 48px, and the Data grid page says its 44px row matches the button height, which is 38px. An input and a button on the same row do not share a height. Open the page →
Some specified outline colours are too faint
AccessibilityOpenThe #cccccc field outline on white is about 1.6:1, below the 3:1 that a control boundary needs. Dark-theme values have not been measured yet. Open the page →
Focus rules contradict each other between pages
AccessibilityOpenThe Accessibility page says nothing traps keyboard focus, while a modal dialog is expected to keep focus inside it. The two rules need to be stated so they do not contradict each other. Open the page →
The MCP description of the AI disclosure label drops the page's caveats
MCPOpenThe MCP server calls it a legal mark without the reservations the docs page carries about when and how it applies. Open the page →
Needs a decision
Confirmed, but there is more than one reasonable fix and someone has to choose.
Checkbox is listed with an indeterminate state it does not have
ComponentsNeeds a decisionThe component list says "with indeterminate state". AceveCheckbox only has checked, onChange, label and disabled. Either build the state or correct the description. Open the page →
AceveButton sets no default type
ComponentsNeeds a decisionWithout a type, a button inside a form submits it. Nothing on this site is affected, but a team that copied the component may rely on that. Changing the default to type="button" is safer for new code and could change behaviour for existing copies. Open the page →
Floating tabs announce themselves as tabs without behaving like them
AccessibilityNeeds a decisionThe buttons have role="tab", but there is no arrow-key navigation, every tab is a separate Tab stop, and no tab panel is linked. The accessible name is hard-coded to "View". Either complete the tabs pattern, which needs panel ids from the caller, or use different semantics for a view switcher. Open the page →
There are no automated tests
TestingNeeds a decisionCI runs lint and a production build. No story has an interaction test, and the Storybook accessibility check is set to report, not to fail. Turning it on needs a test runner with a browser and a new CI job. Open the page →
The product list is derived from the logo set
MCPNeeds a decisionProducts without a logo set here (Craftnote, Next Project, Rekyl, Accurator, KlarPris) are missing from get_product, and the Entré description may be wrong. Every reply carries a caveat, but the list needs an owner and a source of its own. Open the page →
The home page starts an animation after 30 seconds of inactivity
SiteNeeds a decisionIntentional, and switched off when reduced motion is requested. Reported as distracting for someone reading the page slowly. Keep, change the delay, or remove. Open the page →
Not yet checked
Reported to us. We have not verified it ourselves.
Numeric input page shows mock-ups rather than the shipped component
ComponentsNot yet checkedReported: parts of the Numeric input page illustrate behaviour the shipped primitive does not have. Open the page →
Token naming inconsistencies
TokensNot yet checkedReported: token names are not consistent across the docs and the package. Open the page →
The icon set loads as one large chunk
SiteNot yet checkedReported: the icon data is shipped as a single large JavaScript file. Open the page →
Pattern guidance gaps
DocumentationNot yet checkedReported: some composite patterns lack guidance. Open the page →
The Figma-to-code chain has not been verified end to end
ProcessNot yet checkedWhat is deployed matches the repository and CI is green. The Figma publish step, the package registry and how consuming teams pick up a release have not been checked. Open the page →
By design
Reported as a problem. It is a documented choice, explained here.
There is no versioned React package
ComponentsBy designSprout publishes tokens as a package and components as documented reference code. That is a stated decision, described on the Connect page. Its consequence is listed above as S08. Open the page →
MCP tools return text, not structured output
MCPBy designThe server returns JSON as text and declares no output schema. That is a documented choice for client compatibility. The version is available through get_version. Open the page →
Fixed
Shipped. The version is the receipt.
The unchecked checkbox box could be invisible
ComponentsFixed · v3.36.0The border colour was cleared on the client and fell back to white, so an unchecked box had no visible edge in Storybook and after the first on–off on the docs page. The border is now one computed value. Open the page →
Checkbox had no visible keyboard focus
AccessibilityFixed · v3.36.0Focus landed on the hidden native input. The painted box now shows the same focus ring as Radio. Open the page →
Input and Numeric input showed no focus ring
AccessibilityFixed · v3.36.0An inline outline: none overrode the site's focus style, although the documentation promised a ring. It is removed from both components. Open the page →
AceveInput ignored native input attributes
ComponentsFixed · v3.36.0type, name, disabled, readOnly, required, autoComplete and the rest never reached the input, and there was no ref. They are now passed through. onChange still receives the string. Open the page →
Storybook Docs rendered stray form controls
StorybookFixed · v3.36.0HTML tags written in component descriptions were rendered as real elements. They are now marked as code. Open the page →
The contrast tool ignored transparency
MCPFixed · v3.36.0check_contrast reported a fully transparent black on white as 21:1. A translucent colour now returns an explanation instead of a ratio. Open the page →
MCP described an old version of the Button
MCPFixed · v3.36.0get_component_source gave the old height, radius and variant names. It now matches the component: three sizes, four types, three styles. Open the page →
MCP did not know that Radio ships as a React component
MCPFixed · v3.36.0AceveRadio was missing from the component source list, so it was reported as documentation only. It is added, and the build prompt now separates "documented" from "ships as code". Open the page →
The build prompt rejected valid persona ids
MCPFixed · v3.36.0build_ui and review_ux only knew four generic roles and stopped on a real id such as ingo-installer. They now look the persona up in the catalog. Open the page →
A role name silently picked a persona from another product
MCPFixed · v3.36.0Asking for "installer" always resolved to one product's persona. The prompts now narrow by product and ask when a role fits several people or none on that product. Open the page →
How to read this
Where the list comes from and what it leaves out.
Where it comes from
The list was seeded by an external review of Sprout in November 2026. We checked each finding against the code before listing it; the ones we have not got to yet are marked as not yet checked rather than repeated as fact. The reference on each entry is the review's own finding number.
What it leaves out
Security findings are not listed here. They are handled privately and appear in the changelog once they are closed. A fixed issue stays on this page with the version it was fixed in, so the list is also a record of what changed.