}Since there is no else clause, mSupportedProfileType may still be uninitialized.
Just want to make sure this is intended.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Since there is no else clause, mSupportedProfileType may still be uninitialized.
Just want to make sure this is intended.
I think we probably want the profile type to always be initialized.....what should be the fallback here? When might the multi-instance manager be null?
Maybe we should add a fallback and also emit a histogram to keep tabs on how common (or rare) this is?
Charles HagerSince there is no else clause, mSupportedProfileType may still be uninitialized.
Just want to make sure this is intended.
I think we probably want the profile type to always be initialized.....what should be the fallback here? When might the multi-instance manager be null?
Maybe we should add a fallback and also emit a histogram to keep tabs on how common (or rare) this is?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
public static @SupportedProfileType int readProfileType(int instanceId) {Nit: JavaDocs
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
mSupportedProfileType = SupportedProfileType.MIXED;From non-owner perspective:
Comparing with the original CL:
https://chromium-review.googlesource.com/c/chromium/src/+/7208039/10/chrome/android/java/src/org/chromium/chrome/browser/ChromeTabbedActivity.java
The else clause used to has mWindowId == 0, which is a valid window id.
And we used to follow the normal procedure to determine mSupportedProfileType (based on FF/intent/ChromeSharedPreferences). Now we force it to SupportedProfileType.MIXED, which might be a behavior change.
But whether this is Okay depends on when we will get into the else clause.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
From non-owner perspective:
Comparing with the original CL:
https://chromium-review.googlesource.com/c/chromium/src/+/7208039/10/chrome/android/java/src/org/chromium/chrome/browser/ChromeTabbedActivity.java
The else clause used to has mWindowId == 0, which is a valid window id.
And we used to follow the normal procedure to determine mSupportedProfileType (based on FF/intent/ChromeSharedPreferences). Now we force it to SupportedProfileType.MIXED, which might be a behavior change.
But whether this is Okay depends on when we will get into the else clause.
Since we don't know when the else clause occurs, using the normal procedure to determine supportedProfileType makes sense to me.
public static @SupportedProfileType int readProfileType(int instanceId) {Michael WuNit: JavaDocs
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |