[ACE-4085] Layout issues with PubSub log dialog from Share Created: 27-Jul-15  Updated: 18-Feb-20  Resolved: 18-Feb-20

Status: Closed
Project: Alfresco One Platform
Component/s: Web Scripts and Surf
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Kevin Roast [X] (Inactive) Assignee: Closed Issues
Resolution: Won't Fix Votes: 0
Labels: Share, triaged
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Share


Attachments: File AKU-453.ogv     File AKU-463 - reproduced.ogv    
Issue Links:
Duplicate
is duplicated by AKU-444 Long dialogs do not centre correctly ... Closed
Related
is related to by AKU-444 Long dialogs do not centre correctly ... Closed
Story Points: 5
Sprint: Sprint 27

 Description   

1. First display of pubsub dialog will render in the wrong location - normally much wider than the browser window size with the top left corner of the dialog at the centre of the screen. Touching the browser horizontal scrollbar will cure this as will closing and reopening the dialog.

2. The dialog is modal - this makes it pretty useless to see what is happening in real-time - please make the dialog modeless. Suggest docked to the bottom of the screen like the Chrome inspector etc. See AKU-486 for this feature request



 Comments   
Comment by David Draper [X] (Inactive) [ 31-Jul-15 ]

I've not been able to reproduce the first issue (see attached video trying this out in both Firefox and Chrome in different window sizes).

The second issue isn't a bug, but a feature request. Also, since it's actually the Share header that requests to create a dialog containing the debug log there isn't anything that we can do in Aikau alone to address this issue. I'll create a feature request (AKU-486) for this improvement to the rendering the debug log and link it to this issue

Comment by David Draper [X] (Inactive) [ 31-Jul-15 ]

I'm not able to reproduce this issue on Share 5.0.2 using the the latest snapshots of the 1.0.29 development branch (see attached video). Please re-open if there is specific environmental or other steps required to reproduce.

Comment by David Draper [X] (Inactive) [ 31-Jul-15 ]

Martin Doyle [X] Can you double-check this for me and close the issue if you can't reproduce please.

Comment by Martin Doyle [X] (Inactive) [ 03-Aug-15 ]

Can confirm unable to reproduce.

Also, have discovered that we hook into the ALF_SHOW_PUBSUB_LOG topic inside Aikau, so once the feature request mentioned (AKU-486) has been done, we ought to be able to make the PubSub log appear inside the new "dockable" widget.

Comment by Kevin Roast [X] (Inactive) [ 03-Aug-15 ]

Added video of reproducing issue

Comment by David Draper [X] (Inactive) [ 07-Aug-15 ]

Martin Doyle [X] has done some extension research into this issue. We have not been able to reproduce the problem on my machine (Linux), Martin Doyle [X]'s machine (Mac) or Richard Smith [X]'s machine (Windows). Richard has also uses CMM so it isn't related to that specific module. We have been able to detect the cause of the problem on Kevin Roast [X]'s machine which is that the dojo/cldr/nls/gregorian.properties dependency is not being detected by Surf so is not included in the pre-built cache. We have been able to show that where the issue does not reproduce that this module is included in the pre-built cache. We've also been able to demonstrate that my adding the dependency in another way will resolve the issue. However, Surf should be able to correctly analyse all AMD dependencies so that they are included - we don't want to be patching each module, we want to fix the problem at source.

There has to be some kind of environmental issue at play here... although we have explored Java versions (both 7 and 8), OSes and browser locales. However, since we need to make changes to Surf then this issue needs to be re-assigned to the appropriate project so that Surf can be fixed.

Comment by Kevin Roast [X] (Inactive) [ 07-Aug-15 ]

dojo/cldr/nls/gregorian.js to be specific, but otherwise yes. and yes adding it to the module fixes the problem for me.

Generated at Mon Jul 13 20:27:42 BST 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.