If EnabledTop is set as 1st group in OfflineIndicator, we got the following test failures:

chrome_public_test_apk on Android device Nexus 5 (with patch) Run on OS: 'Android'
org.chromium.chrome.browser.payments.PaymentRequestPaymentMethodIdentifierTest#testSupportedTypesMustMatchForCanMakePayment
org.chromium.chrome.browser.payments.PaymentRequestPaymentAppCanMakePaymentQueryTest#testNoBobPayInstalled
org.chromium.chrome.browser.payments.PaymentRequestPaymentMethodIdentifierTest#testSupportedNetworksMustMatchForCanMakePayment
org.chromium.chrome.browser.payments.PaymentRequestPaymentAppCanMakePaymentQueryTest#testPayViaFastBobPay
org.chromium.chrome.browser.fullscreen.FullscreenManagerTest#testHidingBrowserControlsRemovesSurfaceFlingerOverlay
org.chromium.chrome.browser.payments.PaymentRequestPaymentAppCanMakePaymentQueryTest#testNoInstrumentsInFastBobPay
org.chromium.chrome.browser.payments.PaymentRequestPaymentMethodIdentifierTest#testPayWithBasicCard
org.chromium.chrome.browser.payments.PaymentRequestPaymentAppCanMakePaymentQueryTest#testPayViaSlowBobPay
org.chromium.chrome.browser.payments.PaymentRequestPaymentAppCanMakePaymentQueryTest#testNoInstrumentsInSlowBobPay

These errors occur because the test device ran in airplane mode and thus the appearance of top offline indicator caused those tests who relied on checking the existence or clicking the UI elements at the top of the content area to fail.

For now, I worked around this by moving EnabledBottom to 1st group. On the long run, we need to figure out how to solve this problem.