Addressing issue #207
Such language codes were not listed in ULS language list.
Root cause was $.uls.data.getLanguagesByScriptGroup was returning
a map of script groups, which contained only resolved language codes.
And later in append method of jquery.uls.lcd.js, there is a check if
that language code is part of languages list passed as option to uls()
call. This test fails and the language code does not get added to display.
Change-Id: Iec914a9694a46eef5750ef3af7346d66e052ab77
To ensure these work locally over the file:/// protocol, simply
use https instead.
Straighten out inconsistencies in the markup (closing slash). Made
to match the test/index.html file.
Also:
* index-mobile.html: Re-use jQuery object instead of executing
the same query three times.
* test: Remove unused qunit-fixture element.
Protocol-relative urls don't work when using the file from the
file system directly in a browser (they require the file being
served from a http web server).
This is why the Grunt run has been broken since 426ccf0131, as
can be seen on https://travis-ci.org/wikimedia/jquery.uls/builds.
utils.getLanguagesByScriptGroup() runs on the object's languages
property and not on all the langdb languages. This caused
the redirects to be counted as languages. I fixed this,
and added a test to prevent it.
Also update JS langdb, because it went out of sync in of
the previous commits.
This is supposed to allow adding special languages.
This region's section is hidden by default and can be enabled by
passing different options to the lcd object.
