(bug 38158) maxLength issue in jquery.byteLimit.js

As reported in the bug and at http://de.wikipedia.org?oldid=107992278,
FF13 and IE8 refuse any input when a custom modifier function is given
and $el.removeProp("maxLength") is called.
A test of this behaviour is available at http://jsfiddle.net/Rtnj6/
Removing the attribute works, so I've changed this and some minor tweaks.

This partially reverts 39cb0c19d58

Change-Id: I70d09aaecd14aa01b7a305e39a5d512cda3d3fd2
Clean up: Declare variables with public instead of var

Variables in classes should be declared using public $foo
instead of var $foo for various reasons. As we require PHP 5.3
we don't have to take care about that PHP4 left over, but can
get rid of it in favour of the more clear and better readable
public.
See also: http://php.net/manual/en/language.oop5.visibility.php
(Divided into several commits to keep reviewable)

Change-Id: Ic723d0347ab2e3c78bc0097345c68bbee3dc035a
(bug 29898) Set cookie to force HTTPS from HTTP

Sets a cookie on user login (removed on logout) if wpStickHTTPS
was checked, which causes the browser to get a redirect if they
visit the HTTP version of the site.

Change-Id: I60f44a1062a93d15198edae6674bb3310a148b2d
Adding wildcard support to $wgCopyUploadsDomains

Change-Id: I06bff1c626d847e4e28dca0772a931f6d6925736
Added protocol option to Linker and OutputPage::addReturnTo.

Added new argument to the Linker options array to allow
the forcing of an HTTP or HTTPS protocol. In order to facilitate
this, a protocol argument was added to Title::getLinkURL.

Also, an options argument was added to OutputPage::addReturnTo
so that options can be passed to the linker and so that the
returnto URL can be forced to a certain protocol.

Change-Id: Ia9cc11e310ad6ef23c221bdba3a4834e7c5556e7
(bug 40541) Fixed $wgSecureLogin functionality.

* Added parameter to login link so that wpStickHTTPS
  is set to true by default when the user is coming
  from HTTPS.
* Added redirect in Special:Userlogin so that when
  $wgSecureLogin is enabled it automatically redirects
  to HTTPS.
* Adjusted User::setCookies() to add a parameter for
  forcing secure/insecure cookies, and then added the
  appropriate argument to Special:Userlogin so that
  cookies are set appropriately.

Change-Id: I17ac68014840daa47bfd4768e978e9ff2edb00db
Add RELEASE-NOTES for g25605

Change-Id: Ibd09a52e98ea2e8fcdf0291b4a586870cb128007
Bring in 1.19 history, update 1.17 and 1.18 history too

Change-Id: I098fdb5610011cbdd91012b8ed4d29e61ca80408
Merge "Bring in 1.19 history, update 1.17 and 1.18 history too"
Updates for MW 1.21

Change-Id: I582c1bcc50d694705b560fea893d0b2984072c08
Merge "(bug 29898) Set cookie to force HTTPS from HTTP"
Localisation updates from http://translatewiki.net.

Change-Id: I300d5f11d881b764b80695b745bff5e9c7d3c404
Merge "Added protocol option to Linker and OutputPage::addReturnTo."
Merge "(bug 40541) Fixed $wgSecureLogin functionality."
Merge "Clean up: Declare variables with public instead of var"
Merge "Adding wildcard support to $wgCopyUploadsDomains"
Wrap long lines

Also remove default setting of $p done in else statement at end

Change-Id: I5024c1fc1748ad1add145d0696b33a6d7ef3223b
Removed unnecessary whitespace in tpl name/arg class tests.

Change-Id: Id0346d16fcecd0d44d85f29a45923c8401f47a9c
Merge "Wrap long lines"
Release notes: Maintain 1.20 notes in master, revert history.

* The one in history isn't final yet, which makes maintenance
  harder as it would have to be synced between 2 different file
  names across 2 different branches.

* For backport commits its easier if the 1.20 file is still in
  master so that they can be written together with the commit
  (and so that the history is in master as well), as opposed to
  merging it in master without notes and then adding them later
  on in the (amended) merge version.

Change-Id: I3fa4b88a5845a51e83221d78facaba1ddb3b1acb