Community
Participate
Working Groups
In reviewing bug 372262 I noticed that we pass "null" as the selections when we render commands to the "More" menu in the user list page. If no selections or item are passed in to the command service on render, then the selection service will be consulted. The navigator uses this same technique with the more menu. However, the navigator is setting up a selection service in the command service. That allows the "null" behavior to work properly. The glue code for the user list is not doing so, so there will never be any commands rendered on that first call to updateNavTools. Compare users.ui/web/profile/user-list.js line 25, 27 (wrong way) to client.core/web/navigate/table.js line 26, 33 (right way) What this means is that the page will never render selection based commands until the selections change in some way. So behavior like "remembering previously selected items when you page back in history" will not work.
(In reply to comment #0) > What this means is that the page will never render selection based commands > until the selections change in some way. So behavior like "remembering > previously selected items when you page back in history" will not work. Well, it's more specific than that. "remembering previously selected items" may not be implemented on this page, would have to investigate this further. This bug as stated simply means that the first time you render commands (not because of a selection service notification), you won't get the selection based command such as "Delete User" even if there were a selection known by the service. Only when the selection changes would the toolbar be updated. But the reality is that you probably always get a notification from the service, because even persisted selections trigger callbacks.
This bug refers to a coding error I noticed, but I'm not sure there's even a symptom. It's just about properly instantiating the services for a page. Not a 2.0 RC2 issue. Removing milestone.
I think we don't have this page any more.
