Splitting this off from #1545952: [META] UI for updating an issue in D7.
If we go the route of using the core edit form (option A) or a modal popup (option B) for updating the issue, sometimes it'd be nice to also see the full comment history while you're composing your update. However, we don't necessarily want to *always* do that, since that adds a lot of extra data to the page load (which is especially problematic on a mobile device, both for bandwidth and UI clutter reasons).
So, it might be nice to have a magic button that uses AJAX to load the whole comment stream and current summary into a div at the bottom of the edit form so that if you want to see the current values (and you didn't just open the edit UI in a new browser tab, as nature intended), you still can.
This issue is postponed since we might not use a UI that needs this at all, and even if we do, this is a totally optional add-on that could be rolled out in phase 2 instead of something that's required for 7.x-1.0 and the initial launch.
Comments
Comment #1
iamcarrico commentedI will take a look at this today/tomorrow see what I can pull out of a hat.
Comment #2
dww@ChinggizKhan: Please don't. ;) We're not even sure we want this UI yet. That's why the status is "postponed". It was just a place-holder for a discussion I had yesterday and wanted to make sure I had a place to track it in case we actually want it.
Thanks,
-Derek
Comment #3
drummUntagging Drupal.org D7 since this isn't a release blocker. It is not a regression from D6 and we can always add this later.
(And focusing the title a bit. The comments could be included in the regular page, maybe toggled with JS, unless they take significant extra time to load & render.)
Comment #4
dwwIt kind of is a regression from D6. In D6, since the comment form is on the page with all the comments, you can see the whole history while you're composing your reply. In D7, that's all gone, and all you can see while editing the issue is the node itself. But, I agree this isn't a launch blocker (unless the UX team says so) so we can untag for now.
Comment #4.0
dwwClarifying the postponement.
Comment #5
webchickComment #6
dwwAdding this as another child of the meta issue on fixing the issue queue workflow problems.
Comment #7
mgiffordThis is fixed now from what I can tell. There's no problem updating the issue summary & scrolling back/forth between the comments...