User Story
- As a member of the Design System Team, in preparation for our upcoming "Gap Analysis" meeting with Web+Design System, I'd like to better understand where we on Web have needed to make workarounds for functionality that is not currently provided via Codex, so that I can better understand how to help and better be aware when these workarounds might cause breakages in the future.
Tasks to be included in gap analysis
Context
As a few examples, from @Catrope :
One of the icon issues [we saw last week] seems to be caused by the Web team using the icon sub-mixins and then providing their own background-image rule on top, which is a workaround for Codex not supporting loading icons by URL (as opposed to embedding them).
Another example: https://phabricator.wikimedia.org/T358068 is caused by Minerva working around the fact that Codex provides no (documented) way to use custom icons as CSS-only icons, by passing in custom icons in the most intuitive-seeming way which turns out not to work correctly
Also from @Catrope :
I think it would be useful for us to broaden this beyond icons, so we can try to identify more of these cases. I feel like there have to be other places where you all are working around gaps in Codex or using it in a way we didn't intend or document, not just these icon-related issues we found yesterday
From @Jdlrobson :
Also related: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/MobileFrontend/+/1005804 seems MobileFrontend also has the concept of a button block from the MediaWiki UI days in the editor
Testing Environment for QA
- N/A - either the list is written or not!
Acceptance Criteria
- We have made up a spreadsheet of the following format: Description of workaround || Missing functionality in codex that might help || associated phab tickets for related issues/breakages (where applicable) - the last column is for issues that this workaround caused
- We have shared this list with the Design System Team at least one day prior to our upcoming Gap Analysis sync with them