Home: the sign-in screen should keep app windows open instead of dropping them

未关闭
#497 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust

调研方向

Start by locating Home's sign-in and lock flows and how they clear app contexts and desktop frames; the issue does not name files or tests. Trace session expiry and authentication-error handling, then review how frame authority is refreshed for the same person and how a different-person sign-in prompts before teardown. Done means open apps retain state through sign-in and lock, with the requested identity-specific behavior and security semantics reviewed.

由索引模型根据 Issue 内容生成。

描述

When a Home session expires (12 hours) or an authentication error sends Home back to sign-in, Home clears every app context and blanks the desktop frame, so open apps lose their state. With Documents' Autosave off (the 0.8.0 default), unsaved edits are lost this way. A computer's lock screen keeps apps running underneath; Home's sign-in and lock should do the same: show sign-in over the desktop, refresh the frames' authority after the same person signs in, and only tear windows down (after asking) when a different person signs in.

Found while testing 0.8.0-alpha.27 (28 Oct). Planned for 0.8.1. Needs a security review of the lock semantics.

主要语言
Rust
星标
6
派生
2
平均合并
1 天 3 小时
30 天内合并 PR
42

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

elastos/elastos-runtime 的其他 Issue

查看 elastos/elastos-runtime 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。