Issue Coverage

Issue coverage

3.0 works through the issues accumulated during the 2.x era one by one; the table below lists how each of them is handled in 3.0.

Issue	How 3.0 handles it
187 / 172 / 178 / 203 jumping on content resize	Anchor positioning + LayoutParams.gravity mapping; no layout at zero size
206 not snapping by gravity after collapsing	The anchor does not change with the size
240 app-level drag gets clipped	Layer container with clipChildren=false; movement only writes translation
195 no-op when called in onCreate / 192 Service	Command queue; system windows may request permission from any context
150 / 205 / 180 disappears across pages, recreate, rotation	desiredVisible + onHostLost / onHostReady
201 child views destroyed on page change / 189 already has parent	The content view belongs to the engine; safeAdd
218 long-press timing / 222 drag after long press / 243 & 108 pass-through / 165 drag region / 209 & 124 & 137 scroll conflicts / 207 & 37 disable drag	Composable FxGesture
194 / 220 / 241 / 235 / 155 / 211 LayoutParams	systemHost { layoutParams {} } + FxOverflow
204 asymmetric half hide / 117 & 157 four-way adsorption / 148 which edge	FxAdsorb / FxHalfHide(start, end) / onPositionChanged(anchor)
242 / 90 RTL	Layout direction participates in anchor resolution
92 portrait/landscape position / 184 storage not triggered	FxStorage keys include the orientation; a single write point
210 / 239 Compose disappears, owner crash	FxComposeOwner belongs to the control
212 / 151 block outside touches, dismiss on outside touch / 154 & 198 above a Dialog	modal(); above a Dialog use viewGroupHost(dialog.window.decorView)
221 blacklist by superclass	blacklist(Class) includes subclasses + filter(AppActivityFilter)
244 not shown inside a Fragment	FragmentHost waits for the view to be created
183 offset differs after downgrade / 188 cannot drag to the bottom	Unified safe area; host swap keeps the config
133 iterate every window / 200 system window coordinates	FloatingX.controls() / FxControl.position
140 / 38 leaks	Listeners belong to the control; the Activity tracker clears references
167 / 238 dependency leakage	Module dependency boundary + a CI assertion
129 multi-process	Out of scope, see FAQ

The per-API mapping for upgrading from 2.x lives in Migration from 2.x; #187 / #210 / #221 / #240 / #244 above each have a regression page named after the issue in the demo, see Demo.

---

Back to Home · See also: Migration from 2.x Demo FAQ