- Ya
- 20 Agosti 2026, 22:42 UTC
- Mwandishi
- kamo
- Ahadi ya
- 2e91cfd
Eight more screens had the defect found in the marketing visitor drawer. The app is served under img-src 'self' data: blob: https://theme.kamocrm.com https://*.kamocrm.com so an <img> at flagcdn.com, or react-country-flag's `svg` mode (really an <img> at cdn.jsdelivr.net), is refused before the request leaves the browser. It survived this long because it was almost invisible: every one of these call sites carried an onError that hid the broken image, so the flag simply never appeared and the row looked like it was never meant to have one. Only the tracking drawer, which had no such handler, showed the broken glyph. CountryFlag is now the one implementation — a Unicode flag emoji, text rather than a picture, so nothing is fetched, nothing can be blocked, and a visitor's country is no longer disclosed to a third party on every render. It carries the emoji font stack NavTop has always used; without it Windows renders the letters "US" instead of a flag. Converted: LanguageSelect, CountrySelect, PostForm, EmojiSelector, EditableLeadComponents and the lead detail page, whose country and language flags were broken too. The tracking drawer's FlagBadge is now a thin alias over it rather than a second copy. US STATES had no emoji to swap to, so SubdivisionField and MortgageFieldsComponent render a SubdivisionBadge — the two-letter code in a brand-tinted chip. That is better than the flag it replaces, not merely cheaper: at 16x12 a state flag is unidentifiable, most being a blue field with a seal, while "CA" is read instantly and is what people actually say. react-country-flag is removed from package.json AND package-lock.json — dropping it from only one would fail `npm ci` in the Docker build, which is the gate that matters. The guard's grandfather list is now empty.