nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TS 6.1 Issues

cemman01

I am currently on a TS6.1 environment. While its good to note that several of our 6.0L issues have been fixed, some minor ones have cropped up. I was hoping IW or someone from Devnet could address or provide an explanation for these:

1) Clicking on links within the 6.1 GUI to open a new TS window no longer works, as in 6.0L and 6.0 versions. In the new window, only the right hand side of the GUI is displayed and the left hand side containing the folder structure is not.

Was this done intentionally?

2) 'Compare To' options for large areas still causes a timeout and an error as described below appears after 5 minutes or so. This was the behavior in 6.0L and below and we were told that this was one of the fixed bugs in 6.1.

"Please select an item to view differences for."

3) While selecting the target area for the 'Compare To' options, the browse field expands out of view of the GUI screen. The 'OK' and 'Close' buttons are not visible and no scrollbar to reach them. We were told that the visibility of elements within the 6.1 GUI would not be an issue since the JS logic behind it was re-written.

Any idea why we are still seeing these type of visibility issues?

(FYI : The 'OK and 'Save' buttons while viewing File Properties looks like it has been fixed. Why is this issue handled in some places and not others?)

4) Reverting from the 'List Modified' view to the normal view of looking at all contents under a folder no longer behaves as in TS6.0L and below versions. Now, if you were in the 'List Modified' view and select a folder from the left hand navigation side, the right hand pane displaying sub-folders\files, should refresh to show all files present under the folder and not just the modified files as in 6.1.

Again, was this change intentional?

I would appreciate if someone could respond to these issues.

Thanks,
Carolyn.

Edited by cemman01 on 04/05/04 01:01 PM (server time).

Find more posts tagged with

Comments

abackenr

>1) Clicking on links within the 6.1 GUI to open a new TS window no longer works, as in 6.0L and 6.0 versions.
> In the new window, only the right hand side of the GUI is displayed and the left hand side containing the folder structure is not.

> Was this done intentionally?

sounds like a bug. i've never experienced it, but there should not have been a change in behavior.

> 2) 'Compare To' options for large areas still causes a timeout and an error as described below appears after
> 5 minutes or so. This was the behavior in 6.0L and below and we were told that this was one of the fixed bugs in 6.1.

well, maybe not completely fixed... compare now begins rendering results a lot sooner. however, it seems like you are talking about really really large workareas, since a five minute compare is rather absurd. i believe we are looking into fixing this better for 6.5 (showing progress bars, and optimizing it).

> 3) While selecting the target area for the 'Compare To' options, the browse field expands out of view of the GUI screen.
> The 'OK' and 'Close' buttons are not visible and no scrollbar to reach them. We were told that the visibility of elements
> within the 6.1 GUI would not be an issue since the JS logic behind it was re-written.

i don't know what they mean by JS logic being rewritten. this sounds like another bug, and i believe i have it assigned to me for 6.5.

> Any idea why we are still seeing these type of visibility issues?

because scrollbars in browsers are an absolute pain and never work as you'd expect them to.

> (FYI : The 'OK and 'Save' buttons while viewing File Properties looks like it has been fixed. Why is this issue handled in some places and not others)

because it's a lot of code and we didn't want to create instability. it'll be addressed for 6.5. file properties was the most urgent for 6.1.

> 4) Reverting from the 'List Modified' view to the normal view of looking at all contents under a folder no longer behaves
> as in TS6.0L and below versions. Now, if you were in the 'List Modified' view and select a folder from the left hand navigation
> side, the right hand pane displaying sub-folders\files, would refresh to show all files present under the folder and not just modified files as in 6.1.

i'm not sure what you mean. what do you mean by reverting?

the behavior you should have is that the tree becomes sticky to the current view you are in. therefore, while in list modified, if you select a folder in the tree, you should be shown modified contents within that folder. so yes, there was a change in behavior for 6.1 that was intentional. hope this answers your question.

staff engineer @ interwoven

cemman01

Thanks for the quick feedback. Item 4 is what would annoy most of our clients since it adds an extra step to the process they were used to. I understand the "sticky view" process but this was not the behavior for 6.0L and 5.x versions. Now a user has to intentionally change the view from Modified Files to All files from view menu.

I'll go through Support to open cases for those items you have pointed as bugs.

Thanks.

nipper

>Thanks for the quick feedback. Item 4 is what would annoy most of our clients since it adds an extra step to the process they were used to.
> I understand the "sticky view" process but this was not the behavior for 6.0L and 5.x versions. Now a user has to intentionally change the
>view from Modified Files to All files from view menu.

I, one, am happy for this change.

I have had too many times, seen my users have browsers time out while WD builds the list of modified. It is even worse when you view my modified
(since it has to look through thousands of modifieds for the few I modified, BTW we are down to 1300 modified in our shared WA)
Since this is persistant, logging out (if you can) or killing the browser does not help. I have had to delete the user with iwuser & recreate
to fix this.

Andy