sceneStyle ignored.

[FrankSalad]

Version

• react-native-router-flux v3.2.6
• react-native v0.22.2

Routes defined like this

      <Router>
        <Scene key="root" sceneStyle={{paddingTop: 50}}>
          <Scene key="one" component={One} />
          <Scene key="other"
                 component={Other}/>
        </Scene>
      </Router>

Also tried

      <Router sceneStyle={{paddingTop: 50}}>
        <Scene key="root"2>
          <Scene key="one" component={One} />
          <Scene key="other"
                 component={Other}/>
        </Scene>
      </Router>

Expected behaviour

Padding is added to the top of both scenes.

Actual behaviour

No padding is added to the top of either scene.

[jeroenbourgois]

I am not so sure sceneStyle is still used in the 3.0 Version? @aksonov

[aksonov]

It is not used in v3. You may pass any attribute but should use it inside your component accordingly. So 'style' may work.

[domchristie]

You may pass any attribute but should use it inside your component accordingly

I feel it’d be good if sceneStyle was brought back. Wrapping every scene component in <View style={props.style}> isn’t ideal.

I could look into creating a PR if you’re interested?

[aksonov]

Yes, feel free to create PR.

[domchristie]

I had a look into this and unfortunately it’s not as easy as I had hoped.

DefaultRenderer can either render a navigationState component or an NavigationAnimatedView. In the case of rendering a navigationState component there’s no way to apply styles directly without wrapping it in another component (perhaps a NavigationCard?)

[aksonov]

Should be done for 3.2.7

[mmazzarolo]

Hello there, sorry but I don't get it, does sceneStyle work now?
The example of the first post is still not working for me on 3.2.7.

[aksonov]

Check latest master

On 07 Apr 2016, at 15:24, Matteo Mazzarolo notifications@github.com wrote:

Hello there, sorry but I don't get it, does sceneStyle work now?

The example of the first post is still not working for me on 3.2.7.

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub #452 (comment)

[amitbobade2007]

Not working for me also in 3.2.8.

[aksonov]

@domchristie Does it work for you?