[
https://issues.apache.org/jira/browse/AMBARI-9942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk resolved AMBARI-9942.
-------------------------------------
Resolution: Duplicate
> Improve view URL interaction with ambari-web's location bar
> -----------------------------------------------------------
>
> Key: AMBARI-9942
> URL: https://issues.apache.org/jira/browse/AMBARI-9942
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.1.0
>
>
> Currently views are embedded inside ambari-web via an IFrame. Though this
> provides a clean separation of ambari-web and view-ui, it raises the issue
> that the view-ui URLs are completely disconnected from ambari-web's URLs.
> So if user wanted to bookmark a particular page inside the view, it is not
> possible as the location bar is completely owned by ambari-web. Some of the
> interactions that have to work are
> 1. As user interacts within a view, ambari-web location-bar should be
> updated (bottom-up) so that user can copy location from location-bar and send
> it to someone.
> 2. When another user gets URL and pastes into location-bar, it should
> propagate down to the view and show correct UI (top-down)
> 3. When user right-clicks on any link inside the view and copies its
> location, that location should be accessible to any other user. Another user
> should get login screen if need be, following which they should be redirected
> to correct UI
> Ambari-web uses EmberJS which relies heavily on the URL's hash. The views
> however are free to choose whatever relative paths they want. Trying to merge
> EmberJS hash and view relative paths is problematic in some cases:
> 1. '=' onwards is chopped off in Firefox
> 2. Having two '#' hashes in the URL is not standard
> Ambari-web needs to provide some help/guidance in better managing view URLs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
