/** * Navigates to the given page inside the SplitContainer. * The navigation is done inside the master area if the page has been added, * otherwise, it tries to do the page navigation in the detail area. * * @param {string} sPageId * The screen to which we are navigating to. The ID or the control itself can be given. * @param {string} [transitionName=slide] * The type of the transition/animation to apply. Options are "slide" (horizontal movement from the right), "baseSlide", "fade", "flip", and "show" * and the names of any registered custom transitions. * * None of the standard transitions is currently making use of any given transition parameters. * @param {object} oData * This optional object can carry any payload data which should be made available to the target page. The BeforeShow event on the target page will contain this data object as data property. * * Use case: in scenarios where the entity triggering the navigation can or should not directly initialize the target page, it can fill this object and the target page itself (or a listener on it) can take over the initialization, using the given data. * * When the transitionParameters object is used, this "data" object must also be given (either as object or as null) in order to have a proper parameter order. * @param {object} oTransitionParameters * This optional object can contain additional information for the transition function, like the DOM element which triggered the transition or the desired transition duration. * * For a proper parameter order, the "data" parameter must be given when the transitionParameters parameter is used (it can be given as "null"). * * NOTE: It depends on the transition function how the object should be structured and which parameters are actually used to influence the transition. * The "show", "slide" and "fade" transitions do not use any parameter. * @type this * @public * @since 1.10.0 * @ui5-metamodel This method also will be described in the UI5 (legacy) designtime metamodel */
