Leading UI Standardization efforts.
- User Since
- May 7 2015, 3:20 PM (145 w, 6 d)
- IRC Nick
- LDAP User
- MediaWiki User
- Volker E. (WMF)
@Dzahn Any updates on above? Accomplishing this task is part of end of Q goals and is dependent on the current's discussion outcome on moving forward.
So the affected browsers of the PNG fallback in the SVG hack are currently IE <= 9, Firefox <= 3.5 and Android 2.
Tue, Feb 20
Mon, Feb 19
Tue, Feb 13
@santhosh There's also discussion around T179361: Move MobileFrontend/Minerva's svg_check.sh script into a reusable, separate library, which would target your request on our side.
@Capt_Swing @Jan_Dittrich No, currently there's no static site generator in place for RLP. We've been discussing possible usage at T164449: Consider a static site generator for WikimediaUI Style Guide, but we didn't yet settle on a conclusion.
Mon, Feb 12
@Dispenser And how to you make the OS tell the browser that it's in high contrast mode and the browser exposes that to the client? I think that's more complicated than just a rewrite of a CSS property :/
Sun, Feb 11
@Hanna_Petruschat_WMDE Thanks for this proposal!
I've updated the corresponding task T127405 to make the various current applications and success criteria easier to understand. With the updated information, a few remarks:
Sat, Feb 10
Fri, Feb 9
Thu, Feb 8
Recapping conversation with @Prtksxna, we are both in favor of open standards, with our current path leveraging GitHub as a contributor multiplier, we are also aware, that a proprietary metadata addition like OpenGraph might be considered under an implementation time cap.
Microformats seem like another interesting option, my personal concern is, in contrast to schema.org or OpenGraph it doesn't seem to provide a strong consumer benefit.
Let's start with the schema.org and OpenGraph additions…
Wed, Feb 7
@Prtksxna You've wrote above “Google accepts microdata, but prefers JSON-LD”. Where did you get that information from?
I leaned towards microdata as it is a more obvious form of support and simplifies maintainability as it's not as easily forgotten left behind type of metadata, that an JSON-LD file in root folder would probably be.
@Prtksxna I like the summary! Given the scope of the project, I think both, following schema.org and OpenGraph makes sense. Maybe we can aim for time-boxing it to 2-4 hours of research & implementation investment?
@Etonkovidova Your sign-off.
Tue, Feb 6
@Mooeypoo Heads-up, this will go into OOUI v0.25.2.
With padding: 0:
@DarTar As it's sometimes unnecessary hard to imagine, this would be a preview with figcaption issue resolved:
Mon, Feb 5
@DarTar Non-margins are a design feature from Style Guide. ;) But there's a connected bug of the figcaption not being put back on horizontal alignment of main contents text. We were discussing the imagery and on smartphones in portrait mode it turned out to work better for our imagery there. Take a moment and give it a try with several images (ignoring the figcaption alignment) before deciding for one or the other.
After conversation with @matmarex, given that this wouldn't gain us a lot together with the time investment needed, putting this to “Lowest”.
@DarTar One thing to consider is, you've set all project taglines, but on the “Projects” overview page, you're currently going with only a normal paragraph.
Proposal to change this (and probably shorten it slightly) to:
@bmansurov The footer issue is captured in https://github.com/wikimedia/WikimediaUI-Style-Guide/pull/62 upstream. As soon as this gets reviewed, I'll update it here too.
Thanks @Liuxinyu970226, updated!
@DarTar The class is already there, I've updated the code slightly to provide better markup:
- Recommended way <figure> and <figcaption>:
Put the image into a figure element like this, I've updated events.html accordingly:
<a target="_blank" href="https://www.mediawiki.org/wiki/Wikimedia_Research/Showcase"><img src="img/screenshots/Research Showcase.png" title="Wikimedia Research Showcase" alt="screenshot of videos from the monthly Wikimedia Research Showcase" /></a>
<a target="_blank" href="https://www.mediawiki.org/wiki/Wikimedia_Research/Showcase"> <figure> <img src="img/screenshots/Research Showcase.png" title="Wikimedia Research Showcase" alt="screenshot of videos from the monthly Wikimedia Research Showcase"> <figcaption class="figure__caption">Screenshot of videos from the monthly Wikimedia Research Showcase</figcaption> </figure> </a>
Just for completion, I haven't heard back from the company for the last two weeks on the email request.
And in the end of the task description I put the proposal to “to stay with the current caret indicator as special case”. Basically to put the plan to remove them and only use movement icons on hold due to the insufficient, disruptive application of movement icon as dropdown indicator replacement. No immediate action required here from my POV.
The whole task is meant for transparent documentation.
@Prtksxna Get rid of what?
Sun, Feb 4
As minor note, one of the learnings from RLP page was to set images to 2px border-radius as well. Should we set this as general rule?
Sat, Feb 3
@bmansurov I couldn't reproduce the scaling issue – not on Win10/Fx57 nor on OS X/Fx58…
Fri, Feb 2
@Rammanojpotla For now there's a Gerrit patch with the overhauled icons at https://gerrit.wikimedia.org/r/#/c/400091/
We're also planning on making the icons downloadable as SVGs in the https://wikimedia.github.io/WikimediaUI-Style-Guide/ in near future after the patch got merged.