<itemvalue="Window flag: hide all screen decorations (such as the status bar) while this window is displayed. This allows the window to use the entire display space for itself -- the status bar will be hidden when an app window with this flag set is on the top layer. A fullscreen window will ignore a value of SOFT_INPUT_ADJUST_RESIZE for the window's softInputMode field; the window will stay fullscreen and will not resize. This flag can be controlled in your theme through the android. R. attr. windowFullscreen attribute; this attribute is automatically set for you in the standard fullscreen themes such as android. R. style. Theme_NoTitleBar_Fullscreen, android. R. style. Theme_Black_NoTitleBar_Fullscreen, android. R. style. Theme_Light_NoTitleBar_Fullscreen, android. R. style. Theme_Holo_NoActionBar_Fullscreen, android. R. style. Theme_Holo_Light_NoActionBar_Fullscreen, android. R. style. Theme_DeviceDefault_NoActionBar_Fullscreen, and android. R. style. Theme_DeviceDefault_Light_NoActionBar_Fullscreen. Deprecated Use WindowInsetsController. hide(int) with WindowInsets. Type. statusBars() instead."/>
<itemvalue="Window flag: hide all screen decorations (such as the status bar) while this window is displayed. This allows the window to use the entire display space for itself -- the status bar will be hidden when an app window with this flag set is on the top layer. A fullscreen window will ignore a value of SOFT_INPUT_ADJUST_RESIZE for the window's softInputMode field; the window will stay fullscreen and will not resize. This flag can be controlled in your theme through the android. R. attr. windowFullscreen attribute; this attribute is automatically set for you in the standard fullscreen themes such as android. R. style. Theme_NoTitleBar_Fullscreen, android. R. style. Theme_Black_NoTitleBar_Fullscreen, android. R. style. Theme_Light_NoTitleBar_Fullscreen, android. R. style. Theme_Holo_NoActionBar_Fullscreen, android. R. style. Theme_Holo_Light_NoActionBar_Fullscreen, android. R. style. Theme_DeviceDefault_NoActionBar_Fullscreen, and android. R. style. Theme_DeviceDefault_Light_NoActionBar_Fullscreen. Deprecated Use WindowInsetsController. hide(int) with WindowInsets. Type. statusBars() instead."/>
<itemvalue="Gets the headers associated with the request. These are represented as a mapping of header name to header value. Returns: the headers associated with the request."/>
<itemvalue="Gets the headers associated with the request. These are represented as a mapping of header name to header value. Returns: the headers associated with the request."/>
<itemvalue="Greeting"/>
<itemvalue="Greeting"/>
@ -61,13 +62,12 @@
<itemvalue="minus"/>
<itemvalue="minus"/>
<itemvalue="BRITISH"/>
<itemvalue="BRITISH"/>
<itemvalue="Called whenever the widget configuration changes. If the parent widget rebuilds and requests that this location in the tree update to display a new widget with the same [runtimeType] and [Widget.key], the framework will update the [widget] property of this [State] object to refer to the new widget and then call this method with the previous widget as an argument. Override this method to respond when the [widget] changes (e.g., to start implicit animations). The framework always calls [build] after calling [didUpdateWidget], which means any calls to [setState] in [didUpdateWidget] are redundant. {@macro flutter.widgets.State.initState} Implementations of this method should start with a call to the inherited method, as in `super.didUpdateWidget(oldWidget)`. _See the discussion at [Element.rebuild] for more information on when this method is called._"/>
<itemvalue="Called whenever the widget configuration changes. If the parent widget rebuilds and requests that this location in the tree update to display a new widget with the same [runtimeType] and [Widget.key], the framework will update the [widget] property of this [State] object to refer to the new widget and then call this method with the previous widget as an argument. Override this method to respond when the [widget] changes (e.g., to start implicit animations). The framework always calls [build] after calling [didUpdateWidget], which means any calls to [setState] in [didUpdateWidget] are redundant. {@macro flutter.widgets.State.initState} Implementations of this method should start with a call to the inherited method, as in `super.didUpdateWidget(oldWidget)`. _See the discussion at [Element.rebuild] for more information on when this method is called._"/>
<itemvalue="Called when a dependency of this [State] object changes. For example, if the previous call to [build] referenced an [InheritedWidget] that later changed, the framework would call this method to notify this object about the change. This method is also called immediately after [initState]. It is safe to call [BuildContext.dependOnInheritedWidgetOfExactType] from this method. Subclasses rarely override this method because the framework always calls [build] after a dependency changes. Some subclasses do override this method because they need to do some expensive work (e.g., network fetches) when their dependencies change, and that work would be too expensive to do for every build."/>