Last modified: 2011-04-14 15:11:38 UTC
These are in fact two different bugs on the same code: a) Deletion summary was prefilled with up to 150 characters from the page content, leaving space for the sysop to add his reason. r27170 changed it to the maximun available (allowed by the language), eating that content. Rationale was "In the deletion default reasons, calculate how much text to get from the article text, rather than getting 150 characters (which may be too much)". I don't know why max(150, $maxLength) wasn't used. (Regression was complained onm ML). b) With r27832 (bug 9633) the calculated length isn't accurate any more. The delete reason from the list is prepended and mysql trims the reason field (see URL). Either change the <input maxlength to 255 - max(strlen(deletereasons)) or perform some black magic with javascript when changing the combo value (hard to get right).
> b) With r27832 (bug 9633) the calculated length isn't accurate any more. Selecting from the dropdown of reasons should probably override (and if JS is avaiable, blank) the 'reason' field.
(In reply to comment #1) > > b) With r27832 (bug 9633) the calculated length isn't accurate any more. > > Selecting from the dropdown of reasons should probably override (and if JS is > avaiable, blank) the 'reason' field. > No, using both is a common use case.
