...

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

Workflow Concerns

1. History Management
2. Bookmarking
3. zero footprint or contractual requirements