[Android] Fix the order for SiteSettingsCategory
The order for `IntDef` doesn't matter for functionality, but logically and for better code readability it should follow enum's order.
This commit is contained in:
+5
-6
@@ -1,17 +1,16 @@
|
||||
diff --git a/components/browser_ui/site_settings/android/java/src/org/chromium/components/browser_ui/site_settings/SiteSettingsCategory.java b/components/browser_ui/site_settings/android/java/src/org/chromium/components/browser_ui/site_settings/SiteSettingsCategory.java
|
||||
index 9215e06fe9f1475607047127c17ee96f34caba68..2b22f4833dfda9914451e4909be811f16112f63a 100644
|
||||
index 9215e06fe9f1475607047127c17ee96f34caba68..219899ca0f3f0070fce7203348d77e89a38eb22b 100644
|
||||
--- a/components/browser_ui/site_settings/android/java/src/org/chromium/components/browser_ui/site_settings/SiteSettingsCategory.java
|
||||
+++ b/components/browser_ui/site_settings/android/java/src/org/chromium/components/browser_ui/site_settings/SiteSettingsCategory.java
|
||||
@@ -75,7 +75,7 @@ public class SiteSettingsCategory {
|
||||
@@ -75,6 +75,7 @@ public class SiteSettingsCategory {
|
||||
Type.TRACKING_PROTECTION,
|
||||
Type.FILE_EDITING,
|
||||
Type.JAVASCRIPT_OPTIMIZER,
|
||||
- Type.NUM_ENTRIES
|
||||
+ Type.NUM_ENTRIES, Type.AUTOPLAY, Type.BRAVE_GOOGLE_SIGN_IN, Type.BRAVE_LOCALHOST_ACCESS
|
||||
+ Type.AUTOPLAY, Type.BRAVE_GOOGLE_SIGN_IN, Type.BRAVE_LOCALHOST_ACCESS,
|
||||
Type.NUM_ENTRIES
|
||||
})
|
||||
@Retention(RetentionPolicy.SOURCE)
|
||||
public @interface Type {
|
||||
@@ -115,9 +115,10 @@ public class SiteSettingsCategory {
|
||||
@@ -115,9 +116,10 @@ public class SiteSettingsCategory {
|
||||
int HAND_TRACKING = 31;
|
||||
int FILE_EDITING = 32;
|
||||
int JAVASCRIPT_OPTIMIZER = 33;
|
||||
|
||||
Reference in New Issue
Block a user