[pull] androidx-main from androidx:androidx-main#1143
Merged
Conversation
Design doc: go/compose-xr:subspace-semantics-property. Test: added unit tests Fix: 513652972 Bug: 460427288 RelNote: Introduced SubspaceSemanticsPropertyReceiver: a dedicated wrapper that limits 3D layout container properties to valid fields (initially testTag and contentDescription). Change-Id: I5cf5cbf8dd1ca4a2d25b8c4e1fbf2b3a2bad8973
Design doc: go/compose-xr:subspace-semantics-property. Test: Added unit tests Fix: 513653210 Bug: 460427288 RelNote: Introduced SubspaceSemanticsConfiguration. This is a configuration of semantics properties for a Spatial node. This class safely exposes query methods for 3D semantics without leaking foundational 2D semantic capabilities to external consumers. Change-Id: Id025e31885a84d762a1b2d6c493c2892cf2138d6
Neither the g3 code nor the non-Compose for XR code uses these deprecated APIs: https://source.corp.google.com/search?q=s:SpatialConfiguration%2F.request(Home%7CFull)SpaceMode%20%20-f:xr%2Fcompose. * Remove the deprecated APIs before Compose for XR Beta. * Address the Android API Council's LocalSpatialConfiguration runtime exception feedback. The throwing methods (requestHomeSpaceMode/requestFullSpaceMode) are deleted entirely, ContextOnlySpatialConfiguration no longer has any throwing methods. * Decided not to make it nullable to not force devs to add null-checks (such as `?.`). Bug: 458712461 Fix: 478259989 Test: removed obsolete existing unit tests. Relnote: Removed Deprecated Space Mode APIs from SpatialConfiguration. Change-Id: I1ef5cb8200ee2450136d5347b5f07a79bfb0c55e
It is possible for work to have been scheduled between the WorkSpec being marked NOT_SCHEDULED in WorkerWrapper and the execution listener cancelling/rescheduling the work. This would result in the work never being scheduled in the underlying schedulers as they would be cancelled, but the subsequent schedule would not schedule as the WorkSpec would already be marked scheduled. To fix this, we do not cancel the work if it is already rescheduled (i.e. ENQUEUED and has a schedule time). This does not affect non-retry scenarios as the work would not be in the ENQUEUED state. Relnote: Fix bug with retried work failing to schedule with the OS Bug: 504085166 Bug: 517339607 Test: /development/validate_changes.sh HEAD~1 buildOnServer,test,connectedAndroidTest --runOnDependentProjects Change-Id: I452fcda5509083ec0dd8eb6bc1ddb1b1315a6aa6
By using the RemoteText from wear.compose.remote.material3 instead of compose.remote.creation.compose.layout Change-Id: Ie0df57f2e28bf160c093a3a2a267bd632c91a2e2
This reverts commit 6211067. Reason for revert: b/515816892 google3 drop is blocked Test: failing test from b/515816892 passed with this revert Relnote: N/A Change-Id: I6d48c9b9e1014ab8ef135b658d0404805f3e7725
Bug: 439850795 Test: presubmit, ./gradlew appsearch:appsearch-local-storage:connectedCheck Change-Id: Ic198d39a0bb15be50385619b5e34b43bf11c0963
Test: build the app Change-Id: I3f45a6b7d1e936504dbb21895c7a3eb2a55150ae
Previosly, we passed global line index passed from MultiParagraph to Paragraph when calculating isLineEllipsized for lineIndex. This caused ArrayIndexOutOfBoundsException when querying `StaticLayout.getEllipsisCount`. This issue was surfaced when using bullets because their internal configuration forces StaticLayout. Fix: 503397884 Test: new tests Change-Id: I998323a9d8e49d0e74bb47642a37cf960ae643f9
Update the library version for window Bug: 513223805 Test: n/a Change-Id: I8d478380188dddd4cb0dda82738c8971d2897567
…into androidx-main
Auto-generated-cl: translation import OFF_PEAK_PRESUBMIT: true Low-Coverage-Reason: CODE_NOT_TESTABLE Change-Id: Idcc12e47d9e9deb1abcca8798c5747fb04553111
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )