ICEmobile
  1. ICEmobile
  2. MOBI-194

Carousel ill-behaved after first upload

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0 Final
    • Fix Version/s: 1.1 Final
    • Component/s: None
    • Labels:
      None
    • Environment:
      Android/ICEmobile

      Description

      After the very first upload in mediacast, the carousel botton to view the media does not navigate to the viewer page.

      This can easily be recreated as follows:

      1) Restart mediacast
      2) Reload page from container
      3) capture a photo, video or audio
      4) upload it
      5) try to access it from carousel

      The problem seems to only occur for the first uploader. If you push a photo to the client, and then capture media, the carousel behaves as expected.

        Activity

        Hide
        Steve Maryka added a comment -

        This attachment contains the wireshark capture of the described behaviour. It starts just before the upload button is pressed. It contains the upload, first carousel button press (incorrect response), and second carousel button press (correct response).

        Show
        Steve Maryka added a comment - This attachment contains the wireshark capture of the described behaviour. It starts just before the upload button is pressed. It contains the upload, first carousel button press (incorrect response), and second carousel button press (correct response).
        Hide
        Ted Goddard added a comment -

        javax.faces.ViewState is missing from the carousel post that does not work, resulting in a full page update.

        Show
        Ted Goddard added a comment - javax.faces.ViewState is missing from the carousel post that does not work, resulting in a full page update.
        Hide
        Ted Goddard added a comment -

        This appears to be caused by :

        r28296 | judy.guglielmin | 2012-03-13 12:31:12 -0600 (Tue, 13 Mar 2012) | 1 line

        MOBI-120. all components which require js now using same method to load javascript resources to allow for full page non-ajax submit

        Show
        Ted Goddard added a comment - This appears to be caused by : r28296 | judy.guglielmin | 2012-03-13 12:31:12 -0600 (Tue, 13 Mar 2012) | 1 line MOBI-120. all components which require js now using same method to load javascript resources to allow for full page non-ajax submit
        Hide
        Ted Goddard added a comment -

        The carousel issue is fixed, but other components may have the same problem:

        writeJavascriptFile() is being called and optionally rendering the script and the outer span. If the script is not rendered, writeJavascriptFile decides also not to render the outer span, resulting in a large DOM update.

        If many components already manage an outer span with writeJavascriptFile() inside it, then this should be left as-is and components should be modified to ensure that the span is always rendered. However, if the component renderers do not generally manage this span or do not have multiple JavaScript files together, writeJavascriptFile() should be modified to always render the span and then test whether to render the script or not.

        Show
        Ted Goddard added a comment - The carousel issue is fixed, but other components may have the same problem: writeJavascriptFile() is being called and optionally rendering the script and the outer span. If the script is not rendered, writeJavascriptFile decides also not to render the outer span, resulting in a large DOM update. If many components already manage an outer span with writeJavascriptFile() inside it, then this should be left as-is and components should be modified to ensure that the span is always rendered. However, if the component renderers do not generally manage this span or do not have multiple JavaScript files together, writeJavascriptFile() should be modified to always render the span and then test whether to render the script or not.
        Hide
        Ted Goddard added a comment -

        This specific issue is no longer observed. If a different JavaScript technique is chosen for various components, this should be done under new JIRAs for a future release.

        Show
        Ted Goddard added a comment - This specific issue is no longer observed. If a different JavaScript technique is chosen for various components, this should be done under new JIRAs for a future release.

          People

          • Assignee:
            Judy Guglielmin
            Reporter:
            Steve Maryka
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: