Unverified50% confidenceDecision RuleExact time
When hoisting TextFieldState to a ViewModel, it should be a direct property of the ViewModel rather than being placed in the UI state of an immutable data class, otherwise the copy method will create a new instance and cause loss of selection, cursor, and history.
1
Sources
50%
Confidence
Long-term
Relevance
10/30/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedFor same-document transitions, an object containing callback and types properties can be passed to document.startViewTransition(); for cross-document transitions, a types descriptor can be added to the @view-transition rule69% similarUnverifiedCompose provides two-way interoperability with the traditional View system: ComposeView allows embedding Compose components in XML layouts, while AndroidView allows using traditional Views within Compose.63% similarUnverifiedA TextFieldState reference never changes after creation; user input changes its internal properties (such as the text field), so a StateFlow cannot perceive changes to its internal text, and StateFlow cannot be relied upon to observe the text.62% similarUnverifiedText-only models cannot view website rendering via screenshots for visual feedback correction, whereas multimodal models can form a closed loop of 'coding → rendering → visual feedback → correction.'60% similarUnverifiedAfter an image is successfully generated, the top-level content of ChatResponse does not contain a DataContent item but instead contains ImageGenerationToolCallContent, ImageGenerationToolResultContent, and TextContent, with the PNG located inside the Outputs of ImageGenerationToolResultContent.59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1117733API
curl https://kongchang.com/api/v1/knowledge/claims/1117733MCP
get_claim(id=1117733)