https://bugzilla.wikimedia.org/show_bug.cgi?id=65824

--- Comment #6 from Kunal Mehta (Legoktm) <legoktm.wikipe...@gmail.com> ---
(In reply to Vibha Bamba from comment #4)
> Kunal, You make a reasonable point here, We are actually using black
> backgrounds fairly conservatively. it is meant to clearly distinguish
> selection areas from content screens.

Is that necessary? Or at the very least, can it not be black<-->white?

Looking through a few of the iOS apps I have installed:

Facebook uses a grayish back-background (I don't know what the right word is)
with white foreground for content, and gray separators with white background in
the settings menu

Twitter uses a white background throughout with gray separators.

Foursquare uses a white background for content has a lighter-black (not as
solid black as the Wikipedia app) menu which goes to a white backgrounded
settings.

Gmail does the same thing as Foursquare.

I'd note that both Foursquare and Gmail don't cover the entire screen in black,
just part of it, and it's not a solid black, it's a bit lighter. Also they use
a menu slider rather than an overlay so it's less sudden.

Personally I'd prefer not even having black at all, but a compromise might be
to do something like Foursquare/Gmail do.


(In reply to Vibha Bamba from comment #5)
> In the final design which comes out in the next build, Save is punted to the
> default IOS Share sheet. The Edit History is at the very bottom of the
> article.
> See Language and Edit History designs on this card -
> https://trello.com/c/rwpQuBAF/81-main-navigation-design-for-sprint-31

This build already came out :)

I noticed the language selector (bug 65825), but it looks very out of place
with a solid black box compared to everything else on a white background.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to