Overall I like the new theme. Feels much fresher.
A couple of things I'd like to mention:
status-completed Adding images to posts doesn't seem to be working for me now. The transparent gray overlay appears on top of the modal. Trying to click the dialog instead causes a click on the transparent layer, which dismisses the dialog. This is Chrome 41, Windows 7....
I use Arch Linux, and have instaled ttf-google-fonts-git. Roboto has always been a part of the package. But the site still looks awful on my computer. When I was typing this as a comment, I couldn't see what I'm typing well enough. Though I can see this just fine when typing in the Answer section.
If you must use Roboto, please use Roboto-Medium or Roboto-...
Not a real answer to this, but I've experienced this font issue in at least 3 of my Windows 10 laptops/PCs.
Things common to all those PCs, if I remember correctly, were:
Windows 10, drivers, Chrome, and all software up to date.
Copy of Roboto font family (downloaded directly from Google) installed locally.
Font issue was noticeable not just on Android SE,...
From your screenshot, it looks like you've hit the font selection problem with the Roboto font. If you install Roboto under Linux, then when a site or program asks for Roboto, it gets "Roboto Medium" (which is quite heavyweight) instead of "Roboto Regular" (which looks normal). This is a problem with how the weights are set in the font files.
This site has ...
While we're waiting for official response from SE designers team, I decided to create a userstyle for main chat room.
It looks like this
You need to install Stylish extension on your browser:
Here's the CSS rules
box-shadow: 0 1px 2px rgba(0, 0, 0, 0.2);
This is a visual issue effecting an unsupported browser (12.17 was released in April 2014, over a year ago - only to fix the heartbleed issue, so the actual rendering engine has not been updated for longer than that).
As such, we will not be fixing it - we need to dedicate our time to items of high impact. This issue effects a very small number of users who ...
This is great, looks really nice, except:
Since when's Android blue?
You should use the "Android green" for header and/or logo (CC-BY) listed on http://developer.android.com/distribute/tools/promote/brand.html#android-robot.
When you're saying
fix SE network CSS bugs globally
it assumes that other sites have the same design, but they don't, when will ...
Two things I'd mention:
The primary top-left android logo is too similar in colour to the background
The Ask Question button could be highlighted, à la a floating action button, in a different colour and slightly raised.
The first thing to understand was that this Stack Exchange site graduated from beta to a full site two and a half years ago. The design was set up at that time, and at that time Android v3.x aka Honeycomb was the newest version of the Android OS. You can see the thoughts from Jin, Stack Exchange's designer in this post: Design ideas for Android.se Site. (...
almost white background with hardly visible Honeycomb-ish pattern (come on, almost same color as the input box?)
It's a background, it's not supposed to pop out.
the green-ish question title and other texts may hardly point to Android, otherwise rendering the pages almost unreadable. In fact, it hurt my eyes when I checked out the newsletter in my ...
It's a bug with as @Jin said, the Roboto font. I can't uninstall it as the Android SDK requires it, so I used user style-sheets to solve the problem.
Chrome doesn't support native user style-sheets, I used this extension called Stylist and here's what I did:
This works fine for me on both Android.SE and Meta.Android.SE. Really does a favor on my eyes. Hope ...
After the new design was launched, I noticed that the badge spacing is off.
It looks like it was optimized for circle badges, but since the Android head is longer then a circle, there isn't a margin between the badge icon and the badge.
Here's a screenshot of the issue.
(In particular, notice how close the silver badge icon is to the "2".)
This issue is ...
I use the Web Override extension for Chrome to fix this.
Then just add the following to the CSS tab:
font-family: Arial !important;
p.s. I cannot believe this has not been fixed...