In scope:
- Implement styling for "Your Events" table; organizer view
| ldelench_wmf | |
| May 17 2022, 8:58 PM |
| F35309910: build.png | |
| Jul 6 2022, 6:01 PM |
| F35309908: build.png | |
| Jul 6 2022, 6:01 PM |
| F35149786: Screen Shot 2022-05-13 at 10.59.38 AM.png | |
| May 19 2022, 3:38 PM |
In scope:
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| Add styling for the events table | Daimona Eaytoy | mediawiki/extensions/CampaignEvents | master | +67 -3 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Daimona | T308279 Display list of registrations (organizer side) | |||
| Resolved | Daimona | T308609 Styling for "Your Events" table |
Change 793521 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):
[mediawiki/extensions/CampaignEvents@master] Add styling for the events table
Change 793521 merged by Cmelo:
[mediawiki/extensions/CampaignEvents@master] Add styling for the events table
Adding a few notes here as per our previous discussion, with things that differ from the prototype:
tagging in @gonyeahialam and @ifried about this third bullet point above - does every row in the Participants column need to have an icon?
I'm neutral on the question above. I agree that the icon may not be necessary since the row title is "Number of participants." So we will await response from @gonyeahialam to see what he thinks and learns more about the background on the icons.
@Daimona a few minor notes about the table header:
comp:
build:
also noting here that the kebab/"three dots" menu is rotated 90 degrees from the the icon in the comp and this change was as an intentional change as noted in T308607#7957847
MW core puts the arrow before the text, so I'm not sure why it's different in the comp... For consistency with the rest of the interface and given how the icon positioning works internally, I'd rather not change that if possible.
- In the comp, the text is No. of Participants, but in the build it is Number of Participants.
This is an intentional change I made; I think the interface messages should be as clear as possible, and according to the manual we should avoid jargon, slang, etc. I didn't see a compelling reason to use an abbreviation here, and so I just used the full word.
The styling has been implemented, with some changes to the styling based on comments shared above. For this reason, I'm marking this ticket as Done.