Loading skins.vector.search.codex.scripts pulls down Vue.js as
its a script-only module. It is not needed to display the appearance
menu so its presence here seems accidental.
Bug: T381030
Change-Id: I42be70b900340c4a3f10e5d31d1827ad9edd5e7a
Why:
- After migrating to the regular build of Vue 3, the compatConfig
settings in component definitions will be ignored.
What:
- Remove compatConfig declarations from all Vue components in this extension.
Bug: T289105
Bug: T363351
Change-Id: I0f4aefd767145dbba8801c6f4111c64918756e8a
Fixes the separator bar used in the sticky navbar being a light gray
color on dark mode to be a dark gray instead. The light gray is changed
from #c8c8c8 to #c8ccd1 to match an existing Codex color.
Change-Id: I1638fb268dc7a1bbbe80d46b1f2678aa69ba7679
It is always provided by web2017-polyfills in core.
Also remove checks for requestAnimationFrame, which core now
assumes to exist.
Change-Id: Ia9dd0330b45c945cf4aca1ea0d4edadc7308e1fc
In situations where anon account creation is disabled or when
combined login link would be used, the usermenu array contains
single element (for 'login' or 'login/create') instead of two
elements ('login' and 'create account' items separately)
If $wgWikimediaMessagesAnonDonateLink is enabled through the
WikimediaMessages extension, the third element 'sitesupport'
exists, making the number of anon items either 1 or 2 or 3.
This patch fixes $isDefaultAnonUserLinks variable to account
for all the cases
Additionally, if even login is disabled, the element count can be
zero and in such case we need to hide the dropdown in all cases
(not only on large viewports) because it would always be empty.
This patch passes the userlinks count to ::getDropdown() and adds
CSS class when appropriate to hide the drowpdown completely.
Bug: T332743
Change-Id: I1ce5e1ea30917a6e80ef00f3c1703cbd0ecb6968
Move CdxTypeaheadSearch out of render blocking module - it is not
needed - only CdxSearchInput is rendered by default.
Bug: T378636
Change-Id: Id4feb26f73413826cf04ec200d0d501c6b057bfc
To make sure this is code-ified I have added the rule selector-max-specificity
to check specificity and error if we ever attempt to change this and to also
prevent us from writing overly complicated selectors (for now the default is
based on the status quo)
Additional change is required to skinStyle file to accomodate the new rule.
Bug: T373989
Change-Id: I3921d1fb3a098faae8f5a8bdc895783f1b298daa
Add `cursor: inherit;` to the class `mw-selflink` to get back
the expected behaviour of these 'links'.
Bug: T375876
Change-Id: I52d54dc1265fd1a64bc461892e69475a3b3d50b2
Going forward these styles will be provided where needed by
the mediawiki.legacy.messageBox module.
Bug: T360668
Change-Id: I58d9e41f0c98adbd816240b161b5145a667436cd
Due to T343838, we need to adjust the Echo icon after clicking
so it renders consistently with Codex. This is a longstanding bug
and a slight adjustment to how we approach the icon now that Codex
and Vector 2022 use mask-image for their icons.
Bug: T373936
Change-Id: Icdb9cc49c157cb5cbf13fe1f7d5e91b7e986e92e
This was introduced in I16411a7ea47, which only documented the
changes to the colors used. An unintended side effect was inheriting
the standard border-radius, but that should be applied in a
more targetted manner to avoid conflicting with existing
UI components (e.g. OOUI toolbars).
Bug: T373989
Change-Id: I0615ce1594d66cb5207cd119597ae4d0765e94af
Visual changes are subtle, but impact 43 scenarios. The color
and positioning is slightly modified to match Codex.
Bug: T363920
Change-Id: Ie5c88e0aa243f73f2dc9f310d18fd59b831edc64
Follow-up to badd229bab. Moving
`position: sticky` to the same element as `contain: paint` defeated
the workaround. Move it to the parent elements again to make it work.
Bug: T373066
Change-Id: Ic942bfd599661a29cf7b2dbb6c6cc2ec521b8c82
