...
- It doesnt make sense when used inside a browser interface - the browser already has controls to do everything the Screen Navigator does.
- It requires
Code Block <a>tags to navigate back and forth between screens of content - It has not been tested in a nested scenario, although it should theoretically work