There is actually a magic word and a parser function. This checks
if all links are excluded (*).
Bug: T186590
Change-Id: Iaf860683f6e3bc9b00d5e8f19b8be7c0f1b20f5b
* Change the language icon color to gray and optimize
* Simplify key press event handlers
Bug: T175769
Change-Id: I05cfaf699ed5ddccc781344143886831929cbb72
* language-data update: Add Western Armenian to known languages
* Stop rendering languages twice on initial display
* Style adjustments for no-results
* package.json: maintenance updates
* Localisation updates
In addition to the jquery.uls update, this patch contains local
style customization for no-results view as specified in T175235.
Bug: T175235
Bug: T185086
Change-Id: I51645554413dbaa80e02fec8f9115f4de409fb06
I was getting the following warning message:
npm WARN grunt-stylelint@0.8.0 requires a peer of stylelint@^7.8.0 but none was installed.
Change-Id: I5e671c5d89d315c3ee691dacda4c85ff3ff710a2
* Do not group search results by region
* Replace ULS trigger icon with monochromatic one
* Custom no-results message support
* Upgrade jquery in the example to 3.2.1
* Use .siblings to locate the suggestions, clear elements for efficiency
* Removing assigned ids to elements that are not guaranteed to be unique
* Use eslint and stylelint, fix all errors
Update the language icon in ext.uls.pt module with new monochromatic one
Also use custom style for monobook skin.
Bug: T182539
Bug: T175769
Change-Id: I7341064cd0de367d933048c4800f951568747d11
If the language settings window is not visible, all calculations
will go wrong and page will scroll to 0 position.
So call scrollIntoView only when the element is visible.
The $.fn.scrollIntoView defined in jquery.uls core may be unnecessary
now since it is available natively on DOM elements.
Bug: T178188
Change-Id: I461fa9eb7c51cd277bebd3a04cfcc0eed9793c4e
Changes:
* Localisation updates.
* Update language data:
** Make Spanish available under the Oceania region
** Add the Kumyk language
Change-Id: I53a27dcd3a9ef57a4a7b7b989df6c2bb556c0d2c
* Not updated from upstream; last release is buggy as per upstream.
* Punjabi language has good font support in all modern operating
systems.
Bug: T180422
Change-Id: I323953b4c6293df89034f05e0c2e13a96b42dc34
Moving “Language settings” dialog headline up to put on a
virtual line with ToggleButton and apply `#000` to it as
dialog titles elsewhere.
Bug: T175295
Change-Id: Id2d7a7b90996ec7be96e8bafd7bbe78eb8f0e1c9
1. Do string comparison for equality early in the method so that we can
do early return if it passes.
2. Move the zero length check for string up for early return. This may
not have any significant change in performance though.
Change-Id: I86bdd612a4a31c5ebfac6bcd7687b829acc69cda
In the process of updating BetaFeatures logo it got
identified that the logo is better marked up as one
`<path>` element.
Follows up I57f2f4890e980992db2c25506bbdc330530d67b1
Bug: T180427
Change-Id: I3bd8eb032943e00c93975db2911a9f7d26c0bcb2
Unifying BetaFeatures SVG screenshot markup by:
- changing `id`s for better readability,
- sorting attributes,
- using full pixel values where applicable and
- generalizing attributes on `g` where applicable
Also fixing a visual glitch in the RTL version.
Follows up Idace90e945a2bd5efa869ee717224274fd94e91a.
Bug: T180427
Change-Id: I57f2f4890e980992db2c25506bbdc330530d67b1
* Store prefixes and infixes separately in the data
* First match language code, then prefixes, then infixes
* Try to use suggestion either in user language or autonym first
* use formatversion=2 to avoid escaping Unicode
Using Language::fetchLanguageName might can have a small
performance impact. On the other hand there is now check
to skip languages we already found, avoiding some fuzzy
matching.
This is in a preparation for a change in jquery.uls to use
the search API more, while trying to reduce the amount of
weird autocompletion suggestions we show to the user.
Bug: T73891
Change-Id: Id94c5352d9a591969bf90144d1d2d5e758d08301
