GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Page component properties are missing in page-router-outlet · Issue #2385 · NativeScript/nativescript-angular

Page component properties are missing in page-router-outlet #2385

New issue
Copy link
New issue
Copy link
Open
Open
Page component properties are missing in page-router-outlet#2385
Copy link

Description

@mohammadrafigh
mohammadrafigh
opened on Jul 31, 2025
Issue body actions

If I understand correctly, page-router-outlet creates Frame and Pages. Is there any way to set the Page properties in the template?
For example, androidStatusBarBackground or statusBarStyle as stated here.
I don't know if there are other ways to set these properties when using Angular, So I created this feature request to allow setting these properties through page-router-outlet or maybe using a built-in service.

Activity

  1. lostation commented on Aug 1, 2025

    @lostation
    lostation
    on Aug 1, 2025
    More actions

    Forget about it...You'd better go away from NS and try another tech stack...if it's an option...

    Reacted by Mohammad Rafigh, Johan Ljungdahl and EmaGht
  2. edusperoni commented on Aug 1, 2025

    @edusperoni
    edusperoni
    on Aug 1, 2025
    Collaborator
    More actions

    @mohammadrafigh you can inject(Page) in any component and it'll give you the nearest page. Then you can set the styling as you see fit. Same for frame.

  3. mohammadrafigh commented on Aug 2, 2025

    @mohammadrafigh
    mohammadrafigh
    on Aug 2, 2025
    Author
    More actions

    @edusperoni Thanks for your suggestion, I've already thought about that but it doesn't make sense if I want to set a property for all Pages rendered using page-router-outlet. Consider I want to set a property globally. It's not a big deal to inject it as a workaround but it would be a bad practice if I want to do it on all page container components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.