because the user's input toggle for airplane mode is both a reflection of user intent & the state of the backend....and the backend is unfortunately variable & lengthy to change (anywhere from 1 to ~10+ seconds sometimes) we need to have an intermediate/transition state....e.g. toggle to airplane mode on....then animate somehow that there's a transition happening, until it either fails/succeeds
comment from dizzypaty
Between the user’s action of toggling the airplane switcher on and/or off and the backend updating the state, the indicator icon displayed on the statusbar should be the following: network-idle.svg
spawned from efforts in bug 1336715
because the user's input toggle for airplane mode is both a reflection of user intent & the state of the backend....and the backend is unfortunately variable & lengthy to change (anywhere from 1 to ~10+ seconds sometimes) we need to have an intermediate/ transition state....e.g. toggle to airplane mode on....then animate somehow that there's a transition happening, until it either fails/succeeds
comment from dizzypaty
Between the user’s action of toggling the airplane switcher on and/or off and the backend updating the state, the indicator icon displayed on the statusbar should be the following: network-idle.svg
(https:/ /drive. google. com/drive/ #folders/ 0BzbnWoHmYF3aZT A4WHNPYW1jeUE/ 0BzbnWoHmYF3aS2 pVejVicktrdm8/ 0BzbnWoHmYF3abl BITVByRnpzdEk).