sorry, I already said yes on email. I think removing "last" is fine.

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.

perhaps we could look into how translatewiki does their main page (e.g. en extension that restyles a single page)

No, @Jdlrobson means a beta feature Illustration, like the other beta features. Please ping @violetto to see if Michelle or Gus has some cycles to create one.

This looks good everyone, I had concerns but seeing the images all looks well.

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

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?

@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.

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.

https://www.mediawiki.org/w/index.php?title=Topic:Sepl7rfwqf81uh29&fromnotif=1

New topic

@Ricordisamoa that is not correct and should be removed from the patch.

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

@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.

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.

@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.

@Nirzar & @violetto we decided to make the default state quiet, you have to throw on a primary label to get a button bound?

@Prtksxna I don't think this needs to support Intentions…

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?

https://en.wikipedia.org/wiki/Emu_War?source=app
http://stats.grok.se/en/latest/Emu_War
https://twitter.com/JaredZimmerman/status/568117159227834368

Found this library which seems to allow for this https://github.com/inuyaksa/jquery.nicescroll might be overkill but seeing how its done here could be insightful

Just to expand on what @werdna already said, this is what we'd use in the top of process dialogs, toolbars, including floating toolbars, and any tightly bounded use of buttons or other controls types, @KHammerstein or @Nirzar can add an image to clarify further.

I don't think anyone suggested a warn button, so I not sure why we're still talking about this.

@Ricordisamoa, This is the current text, these designs aren't actually changing the copy, just the design and layout.

You don't want to investigate a reusable fix that would work on all scrolling views that exist on pages that scroll? Seems like this has been coming up more and more frequently.

@Deskana, thats what I said…?

@violetto I think its very different than most stepper controls I've seen, but also its is good because we can use the design much more easily on multiple platforms. I think its good.

@Nirzar I think this is a good iterative step, but I'd recommend that we start thinking about a (very) special page for the OAuth permissions that is minimal, has our branding, does not have the normal site chrome and doesn't use a lightbox at all. I think what you have here is a great next step.

@Aklapper & @Qgil, you two are total phabricator pros, I think this would be useful to a wide array of people less skilled than yourself. perhaps you'd reconsider upstreaming this, based on designing for your users rather than yourselves?