A bug report for what? The existing wireframes at the time had a nested element in the attachment representation, and contentEditable wants to put the cursor in that block element; the iframe is a sane way to isolate that. While we aren't having/needing nested content as of now, no sense pulling that away (the UX team also requested keeping that open for future use).