| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
Can you just use oval_surface_0.xml?
android:layout_gravity="start|top"Would you have more sane margins if this was bottom|right?
updateSparkVisibility();Why do you need to call this here?
boolean showSpark = item != null && item.isActorVisit() && !item.wasBlockedVisit();Why? What?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
android:layout_gravity="start|top"Would you have more sane margins if this was bottom|right?
bottom end would act weird on screen resizing, especially width wise, by using start|top, I'm hoping the spark is more consistently pinned to the favicon regardless of screen width.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
boolean showSpark = item != null && item.isActorVisit() && !item.wasBlockedVisit();Why? What?
wasBlockedVisit displays a blocked visit drawable which is different from the normal icon, at least in code. So when the visit is blocked, hide the spark for safety.
boolean showSpark = item != null && item.isActorVisit() && !item.wasBlockedVisit();Hailey WangWhy? What?
wasBlockedVisit displays a blocked visit drawable which is different from the normal icon, at least in code. So when the visit is blocked, hide the spark for safety.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Can you please
<FrameLayoutThis is odd... HistoryItemView is extending a LinearLayout. If you declare a new member as its child, would it get added before / after other children views?
(I see you are calling #bringToFront in Java code, so follow up question there)
mSparkContainer = findViewById(R.id.spark_container);Can you please add a test case in chrome/android/junit/src/org/chromium/chrome/browser/history/HistoryUiTest.java
mSparkContainer.bringToFront();Does this makes the item to be the first child view of parent, or just change the Z-axis?
updateSparkVisibility();Why do you need to call this here?
+1 I was thinking following `updateChipView` pattern is sufficient
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Can you please
I can
Can you just use oval_surface_0.xml?
oh yeah totally LOL, I did not notice this, thanks!
This is odd... HistoryItemView is extending a LinearLayout. If you declare a new member as its child, would it get added before / after other children views?
(I see you are calling #bringToFront in Java code, so follow up question there)
According to Gemini; seems like the content of xml is added first, then the content from code is added next, which is why there's a call to bring to front later.
Hailey WangWould you have more sane margins if this was bottom|right?
bottom end would act weird on screen resizing, especially width wise, by using start|top, I'm hoping the spark is more consistently pinned to the favicon regardless of screen width.
Acknowledged
Can you please add a test case in chrome/android/junit/src/org/chromium/chrome/browser/history/HistoryUiTest.java
Gemini says yes to your request 😂
Does this makes the item to be the first child view of parent, or just change the Z-axis?
This moves the spark container to the end of the child list, to ensure it is drawn last (on top of everything else).
Wenyu FuWhy do you need to call this here?
+1 I was thinking following `updateChipView` pattern is sufficient
Because we want the spark to disappear when the checkmark appears when an item is selected, we need to keep this in updateView().
boolean showSpark = item != null && item.isActorVisit() && !item.wasBlockedVisit();Hailey WangWhy? What?
Sky MalicewasBlockedVisit displays a blocked visit drawable which is different from the normal icon, at least in code. So when the visit is blocked, hide the spark for safety.
Code comment explaining this?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
<FrameLayoutHailey WangThis is odd... HistoryItemView is extending a LinearLayout. If you declare a new member as its child, would it get added before / after other children views?
(I see you are calling #bringToFront in Java code, so follow up question there)
According to Gemini; seems like the content of xml is added first, then the content from code is added next, which is why there's a call to bring to front later.
TIL!
the content of xml is added first, then the content from code is added next
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
<FrameLayoutHailey WangThis is odd... HistoryItemView is extending a LinearLayout. If you declare a new member as its child, would it get added before / after other children views?
(I see you are calling #bringToFront in Java code, so follow up question there)
Wenyu FuAccording to Gemini; seems like the content of xml is added first, then the content from code is added next, which is why there's a call to bring to front later.
TIL!
the content of xml is added first, then the content from code is added next
optional: add this as comment
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
3 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: chrome/android/java/src/org/chromium/chrome/browser/history/HistoryItemView.java
Insertions: 3, Deletions: 1.
@@ -91,7 +91,9 @@
mChipView.getPrimaryTextView().setEllipsize(TextUtils.TruncateAt.END);
mSparkContainer = findViewById(R.id.spark_container);
- // Ensure the spark is drawn on top of the favicon and its background.
+ // Ensure the spark is drawn on top of the favicon and its background. This is needed
+ // because the content of xml is added first, then the content from code is added next (on
+ // top of the xml children).
mSparkContainer.bringToFront();
}
```
[Glic] Add spark display on history page
https://screenshot.googleplex.com/4xQcGDgy6sNSkds
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |