Uploaded image for project: 'Fluid Engage'
  1. Fluid Engage
  2. ENGAGE-342 Performance of 0.3 is slow even when hitting from an iPhone on wifi
  3. ENGAGE-482

Ensure all components are amenable to being displayed within the Screen Navigator

    XMLWordPrintable

Details

    • Sub-issue
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 0.3b
    • 0.3b
    • None
    • None

    Description

      At the moment, there are a number of hard-baked assumptions about how URLs are handled on the client side that cause our components to break when hosted within the ScreenNavigator. We need to place a layer of indirection between components and the URL space, including how they access query parameters and get/set window.location.

      Attachments

        1. ENGAGE-482-css.patch
          6 kB
          Antranig Basman

        Issue Links

          Activity

            People

              colin Colin Clark
              colin Colin Clark
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: