René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Revise frame access API in the context of {N} 4.0","articleBody":"### Which platform(s) does your issue occur on?\r\nBoth\r\n\r\n### Please provide the following version numbers that your issue occurs with:\r\n- Cross-platform modules: 4.0.0\r\n\r\nframe.topmost() API is the most obvious \"static\" API to access navigation frame that is very popular among customers. The fact that it just works (until now) is related to {N} apps mostly having a single internally created frame up to {N} 4.0. With {N} 4.0 we expose the ability to the developer to create multiple frames in different scenarios and there are scenarios where frame.topmost() is not really applicable. Generally frame.topmost() returns the last frame that performed navigation but that is not entirely obvious either from its name, or from the documentation -- with {N} 4.0 the following scenario will be possible that renders frame.topmost() meaningless:\r\n\r\n- Root tabview with two tab items\r\n- Each tab item contains frame as a root element (with defaultPage property set to module name)\r\n\r\nWhen you load the app:\r\n- First tab item is processed thus its frame is processed and navigation occurs to the page set as frame.defaultPage (implicitly this adds frame1 to the top of the frame stack)\r\n- Second tab item is processed (nevertheless it is not visible) thus its frame is processed and its navigation entry is added to the navigation queue (but at the same time this implicitly adds frame2 to the top of the frame stack)\r\n\r\nSo if while playing with the visible first tab, you try to reference its frame via frame.topmost() you will actually get a reference to the invisible frame from the second tab.\r\n\r\nConsider:\r\n- Updating frame.topmost() documentation to explain that it returns the frame that performed navigation last\r\n- Extend frame access API besides frame.topmost() to support scenarios like the one above (possible use frame.id and provide API for the user to lookup frames by id)\r\n- Do we need the frame stack at all? Is it a stack or something else?\r\n","author":{"url":"https://github.com/manoldonev","@type":"Person","name":"manoldonev"},"datePublished":"2018-02-09T15:44:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/5407/NativeScript/issues/5407"}