You are classifying website feedback within the top-level category: Functionality/Bugs. Goal: Assign exactly ONE subcategory per item using the list below. Use the exact names. SUBCATEGORIES (use exact names): - Broken or Incorrect Links: Links that 404, redirect to the wrong place, are missing, or point to an unintended destination (e.g., homepage instead of target). - Display & Rendering Issues: Elements not rendering correctly (cut off, duplicated, missing, overflowing, wrong sizes), unexpected banners/overlays, or visibility problems. - Interactive Element Malfunctions: Buttons/menus/forms/carousels not working as intended (unclickable, inconsistent behavior, hover anomalies). - Data & Logic Errors: Wrong values/types, incorrect sorting/filtering, duplicated items from logic flaws, validation bypasses. - Mobile-Specific Bugs: Issues that occur only on mobile (menu glitches, overlays, mobile-only layout problems). Examples: - "This link goes to home page" → Broken or Incorrect Links - "attend the next imcas links to china page" → Broken or Incorrect Links - "Last row is cut off; can’t see details" → Display & Rendering Issues - "Duplicate image; first product appears twice" → Display & Rendering Issues - "Send button not clickable in chat" → Interactive Element Malfunctions - "Sort dropdown sometimes works, sometimes not" → Interactive Element Malfunctions - "Filter by grant status doesn’t work" → Data & Logic Errors - "Rent check should be a dollar value" → Data & Logic Errors - "Mobile menu stutters/disappears" → Mobile-Specific Bugs - "Number overlaps photo on mobile" → Mobile-Specific Bugs - "Audio/video does not play or player fails to render" → Display & Rendering Issues - "Incorrect media asset renders/plays" → Data & Logic Errors - "Control is present but click has no effect" → Interactive Element Malfunctions - "Control is missing or not visible" → Display & Rendering Issues Guidelines: - Choose the dominant intent. If multiple apply, prefer the most specific. - Do NOT invent new subcategory names. Use only the list provided. - If none apply, use No Match. Aim for 90–95% non-no-match. - Reasoning must be concise (<= 12 words). Tie-breakers and boundary rules: - Navigation target wrong, missing link, or 404 → Broken or Incorrect Links (even if the clickable element exists). - Visibility/cutoff/duplication/missing element → Display & Rendering Issues; unclickable/unstable behavior of a control → Interactive Element Malfunctions. - Wrong values/types, bad sorting/filtering, duplicates from logic → Data & Logic Errors (not Display). - If the problem is mobile-only and clearly stated as such, use Mobile-Specific Bugs; otherwise classify by the underlying issue. - Accessibility-related issues (e.g., screen reader labels) classify by affected function: non-functional control → Interactive; hidden/visible content problems → Display. - Status/inquiry without a concrete malfunction (e.g., "is reCAPTCHA disabled until go-live?") → use the No Match bucket. Additional general rules for consistency at scale: - Element presence vs behavior: If a control (button, link, menu item, input) is entirely missing or not visible → Display & Rendering Issues. Use Interactive Element Malfunctions only when the element is present but non-responsive, requires multiple attempts, or behaves inconsistently. - Media handling: No playback or player fails to render → Display & Rendering Issues; wrong media asset renders/plays → Data & Logic Errors; player controls exist but interactions (clicks/keyboard) do not work → Interactive Element Malfunctions. - Accessibility and operability: Incorrect accessible names/labels/roles → Data & Logic Errors; a control that exists but is not operable via keyboard/assistive tech → Interactive Element Malfunctions; content visually hidden/duplicated or unreadable due to styling/DOM/visibility → Display & Rendering Issues.\n Return JSON only in the exact format shown.