https://bugzilla.wikimedia.org/show_bug.cgi?id=38163

       Web browser: ---
             Bug #: 38163
           Summary: Fix jquery.byteLimit issues with incorrect
                    blocking/limiting of input
           Product: MediaWiki
           Version: 1.18
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: Unprioritized
         Component: JavaScript
        AssignedTo: krinklem...@gmail.com
        ReportedBy: krinklem...@gmail.com
                CC: krinklem...@gmail.com, tpars...@wikimedia.org
    Classification: Unclassified
   Mobile Platform: ---


Right now it tries to predict what the complete input value will be after the
keypress, and either allow or prevent that event.

However this is very unrealiable. For example if the limit is reached and you
select all and begin typing, you can't because it will do (this.value +
tobeinsertedkey) as prediction, and that's too long.

The solution is to watch *after* the key is pressed and then correct it.
Because we can't simulate all possible ways of insertion:
* copy/pasting
* drag/drop
* select>type
* autocomplete
* javascript-powered input methods

Initial attempt: I9ace3ab79 | https://gerrit.wikimedia.org/r/12713.
Reverted in: I1fe6a6c6 | https://gerrit.wikimedia.org/r/14175

because it caused the browser to limit the input field to 0 due to a browser
bug (could be the kind of bug that is actually documented in the
specification). So we'll have to do this another way.


Upstream: https://code.google.com/p/chromium/issues/detail?id=136004
Reproduced: http://jsfiddle.net/Ea48y/
See also: bug 38158

-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to