You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Joe Bowser (Created) (JIRA)" <ji...@apache.org> on 2012/03/22 22:52:22 UTC

[jira] [Created] (CB-371) Move History Management out of DroidGap

Move History Management out of DroidGap
---------------------------------------

                 Key: CB-371
                 URL: https://issues.apache.org/jira/browse/CB-371
             Project: Apache Callback
          Issue Type: Sub-task
          Components: Android
    Affects Versions: 1.5.0
            Reporter: Joe Bowser
            Assignee: Joe Bowser
             Fix For: 1.7.0


We maintain history currently so that we can get jQuery mobile to work.  This is a mititgation technique that causes a lot of other bugs, but we should get this out of DroidGap and put it in its own class.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CB-371) Move History Management out of DroidGap

Posted by "Joe Bowser (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CB-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Bowser updated CB-371:
--------------------------

    Assignee:     (was: Joe Bowser)
    
> Move History Management out of DroidGap
> ---------------------------------------
>
>                 Key: CB-371
>                 URL: https://issues.apache.org/jira/browse/CB-371
>             Project: Apache Callback
>          Issue Type: Sub-task
>          Components: Android
>    Affects Versions: 1.5.0
>            Reporter: Joe Bowser
>              Labels: cordovawebview
>             Fix For: 1.7.0
>
>
> We maintain history currently so that we can get jQuery mobile to work.  This is a mititgation technique that causes a lot of other bugs, but we should get this out of DroidGap and put it in its own class.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (CB-371) Move History Management out of DroidGap

Posted by "Joe Bowser (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CB-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Bowser reassigned CB-371:
-----------------------------

    Assignee: Joe Bowser
    
> Move History Management out of DroidGap
> ---------------------------------------
>
>                 Key: CB-371
>                 URL: https://issues.apache.org/jira/browse/CB-371
>             Project: Apache Callback
>          Issue Type: Sub-task
>          Components: Android
>    Affects Versions: 1.5.0
>            Reporter: Joe Bowser
>            Assignee: Joe Bowser
>              Labels: cordovawebview
>             Fix For: 1.7.0
>
>
> We maintain history currently so that we can get jQuery mobile to work.  This is a mititgation technique that causes a lot of other bugs, but we should get this out of DroidGap and put it in its own class.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CB-371) Move History Management out of DroidGap

Posted by "Joe Bowser (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CB-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Bowser updated CB-371:
--------------------------

    Fix Version/s:     (was: 1.7.0)
                   1.8.0
    
> Move History Management out of DroidGap
> ---------------------------------------
>
>                 Key: CB-371
>                 URL: https://issues.apache.org/jira/browse/CB-371
>             Project: Apache Callback
>          Issue Type: Sub-task
>          Components: Android
>    Affects Versions: 1.5.0
>            Reporter: Joe Bowser
>            Assignee: Joe Bowser
>              Labels: cordovawebview
>             Fix For: 1.8.0
>
>
> We maintain history currently so that we can get jQuery mobile to work.  This is a mititgation technique that causes a lot of other bugs, but we should get this out of DroidGap and put it in its own class.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (CB-371) Move History Management out of DroidGap

Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CB-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Bowser resolved CB-371.
---------------------------

    Resolution: Fixed

This is moved into the view.  w00t!
                
> Move History Management out of DroidGap
> ---------------------------------------
>
>                 Key: CB-371
>                 URL: https://issues.apache.org/jira/browse/CB-371
>             Project: Apache Callback
>          Issue Type: Sub-task
>          Components: Android
>    Affects Versions: 1.5.0
>            Reporter: Joe Bowser
>            Assignee: Joe Bowser
>              Labels: cordovawebview
>             Fix For: 1.8.0
>
>
> We maintain history currently so that we can get jQuery mobile to work.  This is a mititgation technique that causes a lot of other bugs, but we should get this out of DroidGap and put it in its own class.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira