- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Today
Tue, Apr 16
Jul 6 2023
Jun 30 2023
Jun 28 2023
@Sneha Shall we move this back to the backlog or close this and create a new one?
Jun 23 2023
hi @Sneha,
As highlighted by Elena above, the current Title on all our headings and some of the links is somewhat minimal.
Jun 22 2023
Jun 21 2023
Jun 16 2023
As part of Mobile quick view - Show the expanded search result snippet, me and Sneha discussed possible solutions that would allow us to reduce the "layout shift" on mobile.
Jun 14 2023
Jun 13 2023
Jun 12 2023
Jun 9 2023
Jun 8 2023
Jun 6 2023
@Sneha unfortunately this is not possible with the current way of fetching information...
Jun 2 2023
Jun 1 2023
May 31 2023
Further testing has alighted a new issue with the arrow, being introduced by the "expansion" of the snippets, that was moving the arrow.
May 30 2023
I have fixed the top heading issue in the latest patch
May 29 2023
After spending some time researching the issue, I have found out that "container query" even if supported by all major browsers, is NOT supported by our internal LESS implementation. This means that currently to solve this issue we would have to update Wikimedia LESS which is currently a few major versions behind.
Am I correct to assume that this is ok to move forward or would you like me to do any followup action on this task?
May 26 2023
May 19 2023
May 18 2023
I have done some investigation and it seems like this may actually use too many resources and changes for the very low implication it may have.
May 17 2023
May 16 2023
May 10 2023
May 9 2023
May 8 2023
Apr 28 2023
Apr 21 2023
Apr 20 2023
Apr 19 2023
Apr 18 2023
I have added the package in core and tested it locally.
All warning issues in the above Patch expect the following 2 that are coming from Core:
Apr 17 2023
Apr 13 2023
Apr 12 2023
Apr 11 2023
Patch opened.
Yes, I can see the issue there! :)
Not yet, that acceptance criteria is in a different extension and not that straight forward to fix. Shall we split it into two tickets? They are completely unrelated coding-wise..