Bug 1009192 - RFE: Content Spec switching between tabs should keep the scroll position
Summary: RFE: Content Spec switching between tabs should keep the scroll position
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.2
Assignee: Lee Newson
QA Contact: Julie
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-18 00:02 UTC by Lee Newson
Modified: 2013-10-17 23:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1008797
Environment:
Last Closed: 2013-10-17 23:49:15 UTC
Embargoed:


Attachments (Terms of Use)

Description Lee Newson 2013-09-18 00:02:49 UTC
+++ This bug was initially created as a clone of Bug #1008797 +++

Splitting this since the original bug had three problems in one report.

Description of problem:

In the content spec file, clicking on other tabs and then switching back to the 'content spec' tab should take the user to the line of the content spec file the user was viewing and not to the start of the file.

Comment 1 Lee Newson 2013-09-18 01:56:06 UTC
Added in Build 201309181144.

When switching tabs in the Content Spec editor, the first visible row will be saved and then when switching back to the editor tab, it will scroll down to that line.

Note: This build is currently live on the test/dev server.

Comment 2 Julie 2013-09-19 01:17:48 UTC
(In reply to Lee Newson from comment #1)
> Added in Build 201309181144.
> 
> When switching tabs in the Content Spec editor, the first visible row will
> be saved and then when switching back to the editor tab, it will scroll down
> to that line.
> 
> Note: This build is currently live on the test/dev server.

Hey Lee,
   Can you give me the URL for the test/dev server. I checked it on 'next' but couldn't verify the fix.  Thanks

Comment 4 Lee Newson 2013-09-19 01:26:20 UTC
See the private comment above for the link (it's internal so the comment has to be private).

Comment 6 Lee Newson 2013-09-24 05:52:09 UTC
This is now live on the PressGang Next instance as well.


Note You need to log in before you can comment on or make changes to this bug.