image969
May 14, 2026, 8:09pm
1
Does anyone have an idea if these two cards are still managed and if so, is an update in the works?
2026.5 killed the text fields, and I’m really wondering if I have to deep dive in the JavaScript to fix a bunch of my cards or if I should wait it out if it’s actually being worked on
Custom Text Row hasn't been actively managed for a few years and there is already a PR for Mini Media Player to switch to native text input:
dev ← bluedragon456:fix-tts-input-rendering
opened 06:26AM - 09 May 26 UTC
## Summary
Replaces the TTS `ha-textfield` with a native text input so the TT… S message field renders reliably in newer Home Assistant frontend/mobile app environments.
## Problem
Some users see the TTS Send button but no text entry field. The TTS configuration is valid, but the `ha-textfield` component does not always render correctly in the card.
## Changes
- Replaced `<ha-textfield>` in `src/components/tts.js` with a native `<input type="text">`
- Preserved existing input id/class behavior
- Preserved existing `this.input.value`, `this.message`, and `reset()` flow
- Preserved click/key event propagation handling
- Added local CSS so the native input uses Home Assistant theme variables
## Validation
- `npm ci`
- `npm run build`
Build passed. Existing warnings only:
- outdated Browserslist data
- circular dependency warning in `@vibrant/core`
image969
May 18, 2026, 1:35pm
4
Is there a way I can use whatever is on this link or do I have to wait until I see an update available in hacked