https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422014-07-01T16:53:07ZArvadosArvados - Idea #3138: [Workbench] UI improvements: Persistent top nav between pageshttps://dev.arvados.org/issues/3138?journal_id=117952014-07-01T16:53:07ZRadhika Chippadaradhika@curoverse.com
<ul><li><strong>Assigned To</strong> set to <i>Radhika Chippada</i></li></ul> Arvados - Idea #3138: [Workbench] UI improvements: Persistent top nav between pageshttps://dev.arvados.org/issues/3138?journal_id=118222014-07-02T13:07:37ZTom Cleggtom@curii.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/11822/diff?detail_id=10140">diff</a>)</li></ul> Arvados - Idea #3138: [Workbench] UI improvements: Persistent top nav between pageshttps://dev.arvados.org/issues/3138?journal_id=118332014-07-02T16:13:37ZTom Cleggtom@curii.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/11833/diff?detail_id=10152">diff</a>)</li></ul> Arvados - Idea #3138: [Workbench] UI improvements: Persistent top nav between pageshttps://dev.arvados.org/issues/3138?journal_id=119162014-07-04T09:04:52ZRadhika Chippadaradhika@curoverse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> Arvados - Idea #3138: [Workbench] UI improvements: Persistent top nav between pageshttps://dev.arvados.org/issues/3138?journal_id=122032014-07-09T09:37:15ZRadhika Chippadaradhika@curoverse.com
<ul><li><strong>Story points</strong> changed from <i>1.0</i> to <i>2.0</i></li></ul><p>Adding one more story point for learning wiselinks and how to use it.</p> Arvados - Idea #3138: [Workbench] UI improvements: Persistent top nav between pageshttps://dev.arvados.org/issues/3138?journal_id=123512014-07-16T15:26:05ZRadhika Chippadaradhika@curoverse.com
<ul><li><strong>Target version</strong> changed from <i>2014-07-16 Sprint</i> to <i>2014-08-06 Sprint</i></li></ul> Arvados - Idea #3138: [Workbench] UI improvements: Persistent top nav between pageshttps://dev.arvados.org/issues/3138?journal_id=123942014-07-16T15:54:49ZWard Vandewegeward@curii.com
<ul><li><strong>Subject</strong> changed from <i>Workbench UI improvements: Persistent top nav between pages</i> to <i>[Workbench] UI improvements: Persistent top nav between pages</i></li></ul> Arvados - Idea #3138: [Workbench] UI improvements: Persistent top nav between pageshttps://dev.arvados.org/issues/3138?journal_id=126502014-07-23T18:05:05ZBrett Smithbrett.smith@curii.com
<ul></ul><p>Reviewing <a class="changeset" title="Merge branch 'master' into 3138-wiselinks" href="https://dev.arvados.org/projects/arvados/repository/arvados/revisions/c3d4b399c57e711f0cd87c2178f873a688323967">c3d4b39</a></p>
<ul>
<li>The loading animation does not work intended on my Firefox 30. When a wiselink is clicked, the old content is wiped out and then immediately fades back in. The new content renders whenever it arrives in the browser. One idea: would it maybe help if you fade out on a page:loading event, and fade in on page:always or page:done?</li>
<li>The <a href="https://github.com/igor-alexandrov/wiselinks" class="external">documentation</a> indicates that wiselink event handlers must manually fill in analytics details. I wonder if the same is true in our case as well—especially since the branch moves <code>piwik_tracking_tag</code> to the page head, where it won't be reloaded when wiselinks are followed. Is there any way for us to be sure that this branch doesn't interfere with analytics?</li>
</ul>
<p>Thanks.</p> Arvados - Idea #3138: [Workbench] UI improvements: Persistent top nav between pageshttps://dev.arvados.org/issues/3138?journal_id=127612014-07-25T21:46:58ZRadhika Chippadaradhika@curoverse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>When wiselinks is initialized, selection.js is not working. Tom and I discussed this. According to Tom, we want to stop using selection.js very soon. Hence, we do not want to invest time now to make selection.js to work when wiselinks is on. Hence, for the time being, I commented out wiselinks object initialization. We will turn it on when we resolve the selection.js issue.</p>