Community
Participate
Working Groups
I'm not sure when this broke, but we used to store the user's preference for table or tree view to the preferences, and index.html would direct to the appropriate place. Now it seems that index.html always goes to the table view regardless of your last view. Not sure if the problem is that storing it broke, or that reading it broke.
(In reply to comment #0) > I'm not sure when this broke, but we used to store the user's preference for > table or tree view to the preferences, and index.html would direct to the > appropriate place. Now it seems that index.html always goes to the table view > regardless of your last view. Not sure if the problem is that storing it > broke, or that reading it broke. I changed index.html to always go to the table view. This was to fix the "double login dialog" problem - we brought up the login dialog (first instance) and concurrently started looking at the preference for whether to go to tree or table. In the not-logged-in case, this caused an error response, which in turn caused us to go to the table page. On this page, the user was still not logged in (unless they were really fast in filling the first login dialog), so we opened another login dialog (second instance). The proper solution would be to wait on index.html until the user was successfully logged in, then accessing the preference, and then going to the table or tree page.
Who still uses the tree page? ;-)
(In reply to comment #2) > Who still uses the tree page? ;-) ;-) I do, but only to make sure it still mostly works. It's also our answer to "table tree is not fully keyboard enabled or accessible." It also helps me ensure the command framework can deal with very different rendering of commands that have been declared in a common place. But I agree, maybe having a dynamic view switch and exposing all that to the user is not very interesting.
for M6 I've removed the "switch view" command on nav-table. We can revisit this later.
The tree view is gone so this is not an issue anymore.
