Tickets :: Comment on [#12802] Limit max width of compose textarea in dynamic view

* Your Email Address
* Spam protection	Enter the letters below: .__ . ..___..___.._. [ __\|\/\| _/ _/ \| [_./\| \|./__../__._\|_
Comment	>> Rather unnecessarily combative response there Michael, if I may say >> so. I'll admit (and duly apologise for) my knowledge of email being >> somewhat superficial. I've used it for a bit more than 15 years, but >> I haven't been as deeply involved in its implementation as I >> currently necessarily find myself. That obviously makes me at times >> reliant on my observations of how things are usually done, which I >> call conventions (nobody mentioned standards). > > I wasn't being combative. I was trying to explain the difference, as > I understand it, between transport and presentation. To make my > point, I tend to use a lot of emphasis (must be my teaching > background). > > Apologies if that was too direct of a response. Unfortunately, as > the time goes on, I have less and less time to devote to the project, > so I find that being direct and clear in responses saves a lot of > time on the back end. It also is a more useful response to those who > later view the ticket and might have the same issues. > > So what I get out of this is that this is a UI issue. I'm not > convinced that any sort of action is necessary on our end. Locally, > you can always use CSS to size the window as you see fit. Just > remember that what you see on the screen is not necessarily what will > be seen on the receiving end, so that should not be the focus of any > UI change.
Attachment
Watch this ticket

Saved Queries