========
https://hg.mozilla.org/integration/gaia-central/rev/2cc6e0988688
Author: Mihai Cîrlănaru <mihai@cirlanaru.com>
Desc: Merge pull request #14236 from mihai/bug_937499
Bug 937499 - [Settings] Update input type and trigger showing keyboard ... r=@crh0716
========
https://hg.mozilla.org/integration/gaia-central/rev/74c6bf0e73b7
Author: Mihai Cirlanaru <mihai@cirlanaru.com>
Desc: Bug 937499 - [Settings] Update input type and trigger showing keyboard for certain subpanels. r=arthurcc
Use correct type and inputmode for input fields from the following panels:
- Wi-Fi->Connect with WPS
- Cellular & Data->Data settings
- Cellular & Data->Message settings
- Cellular & Data->A-GPS settings
Trigger showing the keyboard for the following subpanels:
- Call Settings->Voicemail
- Bluetooth->Rename my device
TI check. (r=bz)Bug 951517 - Fix broken DOM TI check. (r=bz)Bug 951517 - OnlyFix
broken DOM TI check. (r=bz)Bug 951517 - Only Fix broken DOM TI check. (r=bz)Bug
951517 - Fix broken DOM TI check. (r=bz)Bug 951517 - Only Fix broken DOM
objectTI check. (r=bz)Bug 951517 - Fix broken DOM TI check. (r=bz)Bug 951517 -
Fix broken DOM TI check. (r=bz)
The bounds of the scroll port match what will actually be drawn on the screen.
The bounds of the contained content (sized to the display port) are still accessible via mList.GetBounds, and similarly the visible rect of the contained content is mList.GetVisibleRect. The external bounds/visible rect are GetBounds and GetVisibleRect on the nsDisplayScrollLayer object itself.
We implement nsDisplayScrollInfoLayer::GetBounds solely so that it continues to return an empty rect because we expect active empty layers to have empty visible rects.
We no longer have to set our mVisibleRect in nsDisplayScrollLayer::ComputeVisibility because nsDisplayList::ComputeVisibilityForSublist now does it correctly for us (like other items).
We also have to teach ContainerState::ProcessDisplayItems to not set the visible region for scroll layers because it has the external visible region, not the larger internal display port sized visible region. We instead let BuildContainerLayer set the visible region of the layer.
Add a MediaShutdownManager and have that as the only xpcom-shutdown
observer. This then shutsdown the MediaDecoders, and blocks waiting for
the media state machine's shared thread to complete shutdown before
exiting from the xpcom-shutdown observer. This ensures that the
MediaDecoder infrastructure does not use XPCOM on any thread after XPCOM
has shutdown, which is a logical error.
Due to graph mutation during an incremental cycle collection, objects in the CC graph
may end up with more things pointing to them than they have a ref count. However, these
objects should never become garbage.
Any object that has been stored away somewhere in the middle of incremental graph
building must be treated as live, because we can't trust that the CC graph has
accurate information about it. If such an object is truly garbage, we'll unlink it
in the next cycle collection instead.
ICC uses this to track objects that have been AddRef'd during ICC graph building.
For those objects, we may not have the proper information for them, so treat them
as live.
