Skip to content

android: Remove usage of Fragments - #46317

Merged
mrobinson merged 2 commits into
servo:mainfrom
veyndan:rm-Fragments
Jul 7, 2026
Merged

mrobinson merged 2 commits into
servo:mainfrom
veyndan:rm-Fragments

Conversation

@veyndan

@veyndan veyndan commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Per the docs (emphasis mine):

For Compose-only apps, do not use Fragments and instead use the recommended Compose-only architecture with a single Activity and latest navigation libraries, like Navigation 3.

The latter two points are end goals, but can be done separately.

Testing: There are no automated tests for Android.
Fixes: Part of #45715.

@servo-highfive servo-highfive added the S-awaiting-review There is new code that needs to be reviewed. label Jul 6, 2026
@servo-highfive servo-highfive removed the S-awaiting-review There is new code that needs to be reviewed. label Jul 7, 2026
@mrobinson
mrobinson added this pull request to the merge queue Jul 7, 2026
@servo-highfive servo-highfive added the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Jul 7, 2026
Merged via the queue into servo:main with commit 3eb9998 Jul 7, 2026
34 checks passed
@servo-highfive servo-highfive removed the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Jul 7, 2026
@veyndan
veyndan deleted the rm-Fragments branch July 7, 2026 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants