Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Story Points:
      2
    • Sprint:
      Fall 6 Nov 30 - Dec 11, Fall 7 Dec 14 - Dec 23, Winter 1 Dec 28 - Jan 8, Winter 2 Jan 11 - Jan 22, Winter 3 Jan 25 - Feb 5

      Description

      If a user visits App Store using the Safari Web browser and then attempts to install an App, nothing happens.

      Safari does not allow javascript code that was loaded via https to connect to other web sites via http unless a new window is opened. In this case, the "other web site" is IGB itself running on the localhost.

      For this task, determine if users can install apps into IGB using app store and safari.

      If this cannot be done, then implement some kind of warning or failsafe to alert the user to the fact that they cannot use the Safari browser to install an App from App Store.

      Before beginning work, please review the linked issue for detailed descriptions of the problem.

      Also, consult with Karthik Raveendran on how BioViz Connect has handled this issue from both a technical and user interface perspective.

        Attachments

          Issue Links

            Activity

            Hide
            pbadzuh Philip Badzuh added a comment - - edited

            I am still seeing the issue of the menu bar not loading properly on the bioviz connect page - it is either rendered after a 3+ second delay or not at all...This is also present when using google chrome. I'm not sure what commit is responsible, but this is present on the production site - bioviz.org, so it may have also been the result of a change introduced before those made in this ticket. Maybe a new bug ticket should be made to fix the issue.

            The other styling issue is fixed, however, and the safari warning/notification banner works as expected.

            Show
            pbadzuh Philip Badzuh added a comment - - edited I am still seeing the issue of the menu bar not loading properly on the bioviz connect page - it is either rendered after a 3+ second delay or not at all...This is also present when using google chrome. I'm not sure what commit is responsible, but this is present on the production site - bioviz.org, so it may have also been the result of a change introduced before those made in this ticket. Maybe a new bug ticket should be made to fix the issue. The other styling issue is fixed, however, and the safari warning/notification banner works as expected.
            Hide
            ssegu Sai Supreeth Segu added a comment -

            Yes that issue still exists and it's in production. So, the issue might be with the code in bioviz.org. Please create a new ticket for that issue and please kindly check whether this issue is fixed or not.
            cc: Philip Badzuh

            Show
            ssegu Sai Supreeth Segu added a comment - Yes that issue still exists and it's in production. So, the issue might be with the code in bioviz.org. Please create a new ticket for that issue and please kindly check whether this issue is fixed or not. cc: Philip Badzuh
            Hide
            pbadzuh Philip Badzuh added a comment -

            I'll make that ticket. Moving this to done.

            Show
            pbadzuh Philip Badzuh added a comment - I'll make that ticket. Moving this to done.
            Hide
            chirag24 Chirag Chandrahas Shetty added a comment -

            Philip Badzuh I'm not sure but the delay might be because the application is not able to load https://www.bioviz.org/js/lightbox.min.map file.

            Show
            chirag24 Chirag Chandrahas Shetty added a comment - Philip Badzuh I'm not sure but the delay might be because the application is not able to load https://www.bioviz.org/js/lightbox.min.map file.
            Hide
            pbadzuh Philip Badzuh added a comment -

            Yeah, I saw that in the console, but checking out at an earlier commit, that error is logged, but the delay isn't present, so that must be a separate problem.

            Show
            pbadzuh Philip Badzuh added a comment - Yeah, I saw that in the console, but checking out at an earlier commit, that error is logged, but the delay isn't present, so that must be a separate problem.

              People

              • Assignee:
                ssegu Sai Supreeth Segu
                Reporter:
                aloraine Ann Loraine
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: