Notification custom layouts: spacing of the timestamp.

chrome/android/java/res/layout/web_notification_big.xml

Index: chrome/android/java/res/layout/web_notification_big.xml
diff --git a/chrome/android/java/res/layout/web_notification_big.xml b/chrome/android/java/res/layout/web_notification_big.xml
index 2b9251011a1fb3db6ed4ca8897c67c9c36138db1..23408aa22673e6c88cf6dfebab29ca656077d3c0 100644
--- a/chrome/android/java/res/layout/web_notification_big.xml
+++ b/chrome/android/java/res/layout/web_notification_big.xml
@@ -57,12 +57,16 @@
 
             <TextView
                 android:id="@+id/time"
-                style="@style/WebNotificationTime"
-                android:layout_width="wrap_content"
-                android:layout_height="wrap_content"
+                android:layout_alignBaseline="@id/title"
                 android:layout_alignParentEnd="true"
                 android:layout_alignParentTop="true"
-                android:singleLine="true"/>
+                android:layout_height="wrap_content"

[newt (away), 2015/10/29 20:38:19]

Since we're talking about it, the attribute order that we use more or less
throughout Chrome is:

  id
  layout_width
  layout_height
  other layout_* attributes (alphabetized, or just "logically" arranged)
  other attributes (usually alphabetized)

Rationale:
width and height come first after id, since they're mandatory unlike other
attributes. layout_* attributes are grouped together because they are
instructions for the parent ViewGroup rather than for the view itself.

[Michael van Ouwerkerk, 2015/10/30 09:58:39]

Thanks! That seems reasonable, I'll converge on this pattern as I make changes
then. Done for the parts touched by this CL.

+                android:layout_width="wrap_content"
+                android:layout_marginEnd="8dp"
+                android:layout_marginStart="8dp"
+                android:layout_marginTop="8dp"
+                android:singleLine="true"
+                style="@style/WebNotificationTime"/>
 
         </RelativeLayout>