NativeScript / NativeScript/plugins
[@nativescript/camera] IOS Camera stays behind page content if opened in nested page-router-outlet
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 206
- Forks
- 123
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 1
Description
let me paste the bug from the previous version
unfortunately still not fixed, hence the request for help
https://github.com/NativeScript/nativescript-camera/issues/234
"
I have a nested page-router-outlet configuration in my app. Root component template has a page-router-outlet. Child page has the following template:
<grid-layout rows="*, auto">
<page-router-outlet row="0"></page-router-outlet>
<stack-layout row="1" style="height:50;background-color:red;"></stack-layout>
</grid-layout>
I load a child page inside the page-router-outlet shown inside the template above. If I open the camera inside that child component, stack-layout component in the template above stays above the camera and blocks the camera buttons.
If I use a router-outlet inside the template above, I still have the same problem.
"
is there any chance to fix this or adjust the patch?
iOS 7.1.0, device
is there any chance to fix this or adjust the patch?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the camera behavior with the nested page-router-outlet configuration described in the issue on an iOS device, and compare it with the earlier issue linked there. Trace the camera plugin's iOS presentation and outlet layering behavior; done means the camera controls are not blocked by the surrounding stack-layout or page content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, typescript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100