Jan 15 2020
Jul 4 2019
Jan 11 2019
Nov 11 2018
Feb 28 2018
Feb 23 2018
Sep 15 2017
Aug 10 2017
May 28 2017
Mar 6 2017
Jan 4 2017
Aug 5 2016
Jul 5 2016
Apr 28 2016
Mar 26 2016
Mar 12 2016
Mar 9 2016
Dec 15 2015
Oct 31 2015
Aug 13 2015
Jul 16 2015
Jul 9 2015
Jun 23 2015
Apr 21 2015
sorry, I already said yes on email. I think removing "last" is fine.
Apr 17 2015
Based on talking to @ori today, the decision has been made to roll out to catalan wikipedia and greek wikipedia, due to their user bases, and watch carefully the technical performance of the feature (server/api load) as well as its effect on EventLogging.
Apr 16 2015
perhaps we could look into how translatewiki does their main page (e.g. en extension that restyles a single page)
Apr 12 2015
This looks good everyone, I had concerns but seeing the images all looks well.
Apr 11 2015
I'd rather not work to hard on updating the current state of things and spend energy fixing the compact personal bar, @MZMcBride want to log some configuration option bugs against that project? @mattflaschen is picking up the torch and starting to resolve some of the blocker issues to CPB
Apr 8 2015
Sorry to clarify, for users who have made the decision for themselves OR for users that we've made the decision that visualeditor is the default editor, in the cases where one tab is visible that tab should be "edit" -> Visualeditor. Does that make it clearer?
Apr 7 2015
@Qgil, for all intents and purpose the design team is on phabricator now, however some teams they work with are not. If those teams (mobile web) fully migrate to phab, the designers will migrate as well.
Apr 6 2015
This was specifically around the in-app alerts that an update is ready. do we have those? if not I'd prefer keeping this task.
Apr 5 2015
Apr 3 2015
Apr 2 2015
Apr 1 2015
@Ricordisamoa that is not correct and should be removed from the patch.
Mar 31 2015
I'm just trying to make sure that the static version of the images shows the most possible image, esp. since we're dealing with images that are already on the verge of too low res for the phone, its ok if its stretched during the transition, but we don't want to omit images or have articles without images because the zoomed size won't be high enough resolution. Once you've changed the zoom direction, the total zoom factor, and maybe slowed it down just a bit can you send me the APK?
I'd like to fix this, but I'm not going to consider it a blocker for the test.
@Ricordisamoa what is the question?
Also its great to see more UI being converted. Thanks all!
A few notes…
If images are within 20% of the screen size we might be able to salvage them with a very subtle blur, I don't know if this will greatly increase the number of fair use images that show up in the app.
I think this might be related to fair use images which will appear at low resolution due to commons policy. In the short term I'd recommend that we make sure that images that are equal to or less than the width of the device (or twice the width in the case of HiDPI devices) not be shown
Mar 30 2015
@matmarex this task is referring to the change in the OVERALL size of the control, not the size of the graphics WITHIN the control.
Sorry to clarify, the margins portions of the patches are probably fine, but need to be broken out from the sizing changes which need to be reverted .
This needs to be reverted, after this change form elements no longer align.
Mar 29 2015
Mar 27 2015
not quite, all internal design (and design research) projects (like UI standardization, Reflex) are now handled in phab, teams that designers work with on a regular basis may not have migrated to phab, causing those tasks to be tracked elsewhere.
We need to removed Chinese from the inital test. Due to fundraising having a banner campaign at the same time as our planned test. We should resolve this for a possible later incremental launch but, due to the need to remove Chinese Wikipedia from the test. It doesn't block the test rollout.
Mar 26 2015
@APerson thank you for the feedback, it is appreciated, there are two reasons that we changed the focus state for the input fields,
@Jdforrester-WMF I'd argue that very few people have any idea what the yellow field background means, and autofill ≠ yellow in most users minds, e.g. they see autofill and type ahead in more contexts where there is no yellow background than ones where the background is yellow
@Nikerabbit see the blocking task T93279: Scrolling within in-page regions transfers scroll action to page at end of list (tracking) for one example, the other thing to take a look at is if you have a pinterest account the "you" tab of the notification flyout has the correct behaviour if you want to inspect their implementation.
We're not removing the Autofill predictions, only the yellow background which causes inconsistency between field elements. So to increase UI consistency yes, we'll need to make this change.
Mar 25 2015
Mar 24 2015
@Prtksxna I don't think this needs to support Intentions…
Mar 23 2015
Mar 20 2015
Thanks for writing that up Danny, one suggestion and one question.
Version 42.0.2311.50 beta (64-bit) OS X 10.10.2
@Whatamidoing-WMF i don't think we should have anything pre-edit based on the work that the Growth team did.
@Qgil we have to be careful about setting up expectations that we can't fulfil, additionally we don't want to create a firehose of inputs we can't manage. While I'm generally a fan of starting small and simple, getting this wrong could actually be worse than not doing it at all.
@Aklapper there is not project for research requests to help the annual planning process. Analytics team would be doing the work, but its a tenuous relationship
Just to clarify my idea was for a future enhancement, not an actual plan on
the roadmap or something that anyone agreed to. I could also see it an an
option or extension that gets toggled on on sites/project where it is
wanted/needed but not a default part of the skin.
@Amire80 that all sounds reasonable, but i do worry about the maintaining a history of display names and showing them attached to historic posts, this could be complicated and VERY confusing, it would allow a user to change then name mid-conversation and and appear as each within a thread. This isn't how most (any?) systems with display names work that I'm aware of, so I'd be very wary of diverging from what users expect.
copied from dupe…
Status : Abandoned… Design Research needs this to keep on track in Q4, @KLans_WMF thoughts on when this will get some focus?