@capacitor/screen-orientation: iOS: orientation() and screenOrientationChange event report orientation change although orientation is locked
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- ios, swift, typescript
- 领域
- mobile
调研方向
使用 @capacitor/[email protected] 在 iOS 上复现该问题，从此处描述的 ScreenOrientation.lock()、orientation() 和 screenOrientationChange 入口开始。将锁定为 portrait-primary 并旋转设备后的报告值进行比较；当 listener 和 orientation() 反映锁定的屏幕方向，且不改变文档所述的 Android 行为时，即表示完成。
由索引模型根据 Issue 内容生成。
描述
Bug Report
Plugin(s)
@capacitor/[email protected]
Capacitor Version
💊 Capacitor Doctor 💊
Latest Dependencies:
@capacitor/cli: 4.7.0
@capacitor/core: 4.7.0
@capacitor/android: 4.7.0
@capacitor/ios: 4.7.0
Installed Dependencies:
@capacitor/core: 4.7.0
@capacitor/cli: 4.7.0
@capacitor/ios: 4.7.0
@capacitor/android: 4.7.0
[success] iOS looking great! 👌
Platform(s)
- iOS
Current Behavior
After locking the orientation
await ScreenOrientation.lock({orientation: "portrait-primary"})
the screenOrientationChange listener still reports changed orientations when the device is rotated as if the orientation was not locked. Calling
const {type} = await ScreenOrientation.orientation()
also returns the orientation as if the screen orientation was not locked.
The document orientation itself is locked correctly though, no matter how the device is rotated.
Expected Behavior
The screenOrientationChange listener should only report changes when the screen orientation is actually changed, not when the device is rotated while the screen orientation is locked. Likewise ScreenOrientation.orientation() should return the correct screen orientation when it is locked, no matter how the device is rotated.
This does not seem to be an issue on Android. There the screenOrientationChange listener gets only called after ScreenOrientation.lock() if it actually changed the screen orientation. ScreenOrientation.orientation() also returns the correct screen orientation after ScreenOrientation.lock() was called.
Code Reproduction
Other Technical Details
Additional Context
- 主要语言
- Java
- 星标
- 682
- 派生
- 689
- 平均合并
- 6 天 20 小时
- 30 天内合并 PR
- 4
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ionic-team/capacitor-plugins 的其他 Issue
-
[@capacitor/app] iOS: 'Expression implicitly coerced from String? to Any' warning in getAppLanguage未关闭triage
难度 1/5 1 小时以内 新手友好度 88/100
ionic-team/capacitor-plugins#2604 ·
-
platform: android
难度 3/5 1-2 天 新手友好度 78/100
ionic-team/capacitor-plugins#2605 ·
-
platform: ios
难度 4/5 3-5 天 新手友好度 58/100
ionic-team/capacitor-plugins#2603 · 1 条评论 ·
-
platform: android
难度 3/5 1-2 天 新手友好度 76/100
ionic-team/capacitor-plugins#2599 ·
-
platform: ios
难度 3/5 1-2 天 新手友好度 68/100
ionic-team/capacitor-plugins#2595 · 2 个 reaction ·
查看 ionic-team/capacitor-plugins 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
apache/rocketmq-dashboard#5358 ·
维护者通常 3 天内回复
-
area:cpan-port area:database bug
难度 2/5 1-3 小时 新手友好度 84/100
fglock/PerlOnJava#1605 ·
维护者通常 1 天内回复
-
1.0.0-rc2
难度 2/5 1-3 小时 新手友好度 68/100
wso2/dpdp-accelerator#377 ·
维护者通常 1 天内回复
-
area/dependencies backport/26.4 kind/cve severity/high source/scan-dependencies status/triage
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复