* Optimizing by selecting the ID seperately (very fast) and doing a find() within that context (also caching pCactions ).
* while at it:
- caching selector
- aliasing $ to jQuery locally
- Shorthand dom-ready
(Follow-up r86861)
--This line, and those behind, will be ignored--
M phase3/skins/Vector.php
M phase3/skins/vector/images/arrow-down-icon.png
M phase3/skins/vector/screen.css
AM phase3/skins/vector/vector.js
M phase3/resources/Resources.php
Hope I did this in an ok fashion. svn merge --re-integrate was giving me issues
so I just essentially over-wrote my working copy with the version at img_metadata.
I'm not sure what the intent was, but this rule will make something like:
<span class="small">fo<b>o</b></span>
have the second o in foo be smaller then the first. Even without this rule, nested instances
of class="small" will still be smaller than a single instance, so it only causes weirdness.
Fixes Bug 8028, Bug 8115, Bug 15406, Bug 17141, Bug 8732
1. Sites can specify custom collations.
The script accepts an object "tableSorterCollation" which contains a lookup
table, how specific characters should be treated.
For example, after setting "tableSorterCollation={'ä':'ae', 'ß':'ss'};" in the
site's common.js any string containing an ä or Ä will be sorted as if it were a
'ae'.
2. Table rows can be forced to use a specific data type.
By setting class="sort-{Parsername}", the row will be parsed with the specified
algorithm. class="sort-date" would force date sorting etc.
The following parsers are available: text, IPAddress, number, url, currency,
date, isoDate, usLongDate, time
3. Execution time is reduced by half or more.
Sorting a 935 row * 8 columns table:
Browser Before After
-------- ------ -----
Chrome 10 90ms 42ms
Safari 5 115ms 48ms
Firefox 4 412ms 87ms
IE8 720ms 115ms
4. Based on the content language and the mdy vs dmy preference, the parser can
understand dates such as "17. März '11". wgMonthNames=[] and
wgMonthNamesShort=[]
in the content language and the mdy vs dmy preference are exported to js; A
table containing the following dates would be sorted correctly:
17. Jan. 01
23 Feb 1992
9.02.05
13 November 2001
14 Oktober '76
Was tested in ie6-8, chrome, safari 5, ff3 & ff4
* Remove color:black from table {} in skins (bug 28422)
* Add color:black to .wikitable (since it has a background-color)
* Update comment about CSS3 'word-wrap:break-word' support in Gecko
* Remove line-break in mediawiki.js (it's ~ 90 chars, acceptable)
# the digitClass join versions were inverted: for a maxLength > 1 it should be
(|||), not []
# the regexp escape for digits in the ts_number_transform_table was a bit, er,
strange. Although it worked, I think my version is more common.
# most important: As recommended in http://en.wikipedia.org/wiki/Percent_sign,
there may be some whitespaces between the number and the
"%". See also Bug #15422 for that, I'm not sure wheter it's
included there.
I didn't include the “non-breaking space is part of \s” bit since I didn't want to mess up browser bug work-arounds
I'm not bored enough to actually port these IE styles into the main Chick stylesheet. So better to re-enable them until someone else is bored enough to try.
* Simple skin support multiple sidebar items
* Standard (a.k.a. Classic) likes to add "my watchlist" and "my contributions"
links at the bottom of the first sidebar box. It also has no titles for boxes.
* Cologne blue supports multiple sidebar boxes with titles.
* Allow field validators to return multiple errors
* Allow field validators to return Message objects
* Add a class for fields for invalid input
* Style invalid <input> fields with red border color
Done with http://www.mediawiki.org/wiki/StyleGuide/Forms in mind
