Open karneaud opened 7 months ago
Hi @karneaud Thanks for bringing this to our attention. The scenario you tried implementing is indeed not supported; instead we suggest to provide the content of your second screen via another endpoint and refer to it via a URL. I've updated the docs in #795 to remove the ambiguous statements, let me know if the docs makes more sense now!
Been trying to use document fragments to switch between
<screen>
but kept gettingThen I came across this...
In the "document fragment" format,
href
is an element id prepended by a#
. The id must refer to an element in the current document.For example, assume the following doc is loaded from
https://mysite.com/home
:When the user presses "Hello", the content for the next screen will be loaded from the doc:
I'm trying to understand what is being said here. Is it that document fragments cannot work in
<Navgiation/>
scenarios? If so how does this work? How can this work?