Oct 15 2020
Oct 13 2020
Aug 20 2020
Patch merged to 1.35 in T250851
Aug 12 2020
Aug 11 2020
@Legoktm I cherry-picked the patches required and merged them into a single one.
I am not sure if it is the right way to do it so please let me know if any changes needed to be made.
Relevant discussion and cherry-picked patch are in T250851,
Aug 9 2020
Can this be backported to 1.35? T233677 removed the ability to stop mediawiki.searchSuggest from being loaded and there is no alternatives to do so in 1.35.
Aug 6 2020
Jun 30 2020
Jun 19 2020
Jun 18 2020
Jun 16 2020
Jun 12 2020
@abi_ Thanks for adding the project!
I added the project information to Translatewiki, and commit access is granted too.
Please let me know if there's anything I can do to help.
Apr 13 2020
@Isarra the portal implementation could theoretically replace the current jQuery autocomplete in the core as a drop-in replacement. One of the major benefit of the new search suggestions (OOUI, Portal, etc.) is that it has rich suggestions with images and descriptions. With both PageImage and TextExtract as default extensions, it might be a decent starting point to replace the jQuery solution.
Feb 15 2020
Seems to be a misconfiguration issue on my end.
The issue was resolved after a reinstall of Parsoid, now everything works fine.
Feb 14 2020
The Parsoid output is as follow:
madmin@scw-u18lts:/home/www-data/public_html$ grep -C5 parsoid LocalSettings.php # 'redisServer' => '127.0.0.1:6379',
Feb 7 2020
I have to learn about those performance measurements. Could you give some links?
As @Volker_E mentioned, WMF decided to not provide web fonts for large scale projects for now as the trade off on performance and UX is not worth the investment. When a website uses a webfont, the client needs to make a HTTP request then download the font, it is an additional delay on the critical rendering path. Take Roboto as an example, the WOFF2 (most compressed format) for Roboto Regular (400) with basic latin is 16KB. Plus the latency introduced in the HTTP request, it could easily be 2-3 seconds load delay on a slow 3G network. Page load time can be solved with font-display:swap or lazyload, but that will introduce other UX issues such as font popping when web font is loaded. For a site like Wikipedia that serves a lot of people with slower and capped connections, the negative performance impact is significant.
Feb 6 2020
@Volker_E if web fonts are out of the picture for now, I suggest that we should focus on updating the hierarchy on the current Vector skin first to match with the style guide to improve readability. However, it might introduce a lot of problems with existing templates or layout hack uses on WMF sites.
@AronManning The typography that the style guide suggested is not adopted at all by Vector, I suggest that instead of focusing on font choices first, we need to focus on adopting the hierarchy (size, styles, weight, etc.) defined in the style guide as it is more suited for modern day screens. Adopting the hierarchy first will improve the readability issues across different platforms, and also builds a foundation for studying other font choices.
Just curious, is there a particular reason to deviate from the fonts used in the style guide? It would make more sense to adopt the Wikimedia styles that is also used on Minerva and native apps instead of picking other fonts for UI standardizations and many reasons.
Feb 5 2020
@matmarex thanks for looking into it and the praise! Not sure if the following information helps but we don't have RESTBase on the wiki.
Also another weird behavior is that templates placed inside the <tabber> tags (from Extension:Tabber) seems to be not affected.
Feb 4 2020
@Ryasmeen instead of inserting a template, it was simply visual editing a page that already has a template in there.
@Ryasmeen it is on a non-WMF wiki, here's an example page containing templates using TemplateStyles: https://scwdev.czen.me/Defender
Since it is a dev site, registration is locked and edits are permission only. However, I hope that the following screenshot would help:
Jan 30 2020
@Ryasmeen templates with TemplateStyles transclusion means using a template that uses TemplateStyles, aka having <templatestyles src="Template:Foo/style.css">.
Jan 8 2020
@Tgr Agreed. A lot of Mediawiki installations outside of WMF are infested with spam bots. The recommended solution nowadays for third party wiki is to use Questy Captcha, but it is easily beatable. An implementation that will also works on other MW installations will benefit the ecosystem. Maybe an implementation to core or continue on the ConfirmEdit extension?
As mentioned in T176589, the concept of strength (T179635, T189546) should also be considered to better separate human and bots. From what I recalled, AICaptcha is working towards that and also that's what ReCaptcha V3 is using.
Jan 5 2020
Dec 29 2019
Dec 20 2019
Dec 14 2019
Dec 12 2019
@Oznogon The OOUI search uses a different search widget as I remembered, so it is not affected.
@Jdlrobson I ended up implementing WMTypeAhead with success but I don't know how or where to make a patch, I have given the code to @Isarra and see what he will do with it.
Dec 11 2019
@Jdlrobson do you have a pointer on where can I look up the repo for the discovery portal?
@Jdlrobson It wasn't a problem in the older MW build like 1.27 so my best guess is that it could be related to the jQuery update to 3.X. Anyways thanks for the pointer, I'll share the result if I can find a solution that would help to migrate this issue.
To add onto my comment before, the issue seems to be very widespread. Apart from the WMF wikis, I'm also able to replicate the same bug on RuneScape Wiki (without MF) and PCGamingWiki, in which both of them use a custom skin.
Dec 4 2019
@Jdlrobson I am able to replicate the same issue on MW 1.31.3 with a custom skin that I have been developing from scratch without using MobileFrontend. This is clearly not a skin-specific issue.
To add onto what @Wess mentioned, the dropdown only worked when:
- Through a desktop browser.
- Through a desktop browser with mobile emulation
- Through the mobile browser when remote connected to a desktop using Chrome DevTools, but only works when interact through the desktop not the mobile.
Related to the issue I mentioned above, the style transcluded in the template only appear in Visual Edit when it is inside of the <includeonly> tags or when no <includeonly> tags are present in the template. However, in both scenario, the above not parsed bug still present. Not sure if it is the intended behavior.