Changed cap default to fix ux issue on js toggle

Editor assessment

The subject depends on unexplained jargon: 'cap' and 'cap default' mean little to a reader who has not seen the toggle's internals, so understanding requires effort or the diff. The fix type fits a UX glitch, and the body's squashed bullets do add specifics, a hard check on capSide hiding and always showing capSide for dynamic capType, which partially reconstructs the problem. Still, no one states what the UX issue actually was or why the default changed. No scope is present, past tense dominates, and the fragmented bullets leave this merely decodable rather than instructive.