You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Andrew Grieve <ag...@google.com> on 2012/10/09 21:33:35 UTC
Android's History Object
What's the deal with this?
<preference name="useBrowserHistory" value="true" />
I know that this has been the answer to fixing some people's issues...
Should we make the browser history the default and delete this preference?
Are there any JIRA issues related to having multiple history impls on
Android?
Re: Android's History Object
Posted by Andrew Grieve <ag...@chromium.org>.
Nice work!
On Wed, Oct 10, 2012 at 12:50 PM, Joe Bowser <bo...@gmail.com> wrote:
> OK, I did the switch.
>
> So, we still have two histories, but instead of the shim that we did,
> we now use the browser history as default. This means that the
> following will work again:
>
> - iFrames
> - Browser history with anchors and params (Fix for the 3.x to 4.0.x
> bug was submitted months ago, but we didn't switch until today)
>
> If you want to switch back to the old method, the parameter
> "useBrowserHistory" must be set to false. This should be good for old
> legacy apps who use a different style of history.
> navigator.app.backHistory and history.back should both work now.
>
> Joe
>
> On Tue, Oct 9, 2012 at 12:52 PM, Joe Bowser <bo...@gmail.com> wrote:
> > Hey
> >
> > I created a new ticket for this. I can look into this later today.
> >
> > https://issues.apache.org/jira/browse/CB-1611
> >
> >
> > On Tue, Oct 9, 2012 at 12:45 PM, Joe Bowser <bo...@gmail.com> wrote:
> >> Hey
> >>
> >> I think there's a few JIRA tickets and a few discussions here for
> >> this. We were talking about switching to using the browser history by
> >> default instead of our shim for a while. There was a bug with the
> >> browser history that caused us to be stuck on the first page twice.
> >>
> >> https://issues.apache.org/jira/browse/CB-1504
> >>
> >> I'm happy with us switching to the browser history instead of our
> >> current default. That being said, I think we need to follow our six
> >> month deprecation policy. I know that the policy sucks, but it's
> >> there for a reason.
> >>
> >> Joe
> >>
> >> On Tue, Oct 9, 2012 at 12:33 PM, Andrew Grieve <ag...@google.com>
> wrote:
> >>> What's the deal with this?
> >>>
> >>> <preference name="useBrowserHistory" value="true" />
> >>>
> >>> I know that this has been the answer to fixing some people's issues...
> >>> Should we make the browser history the default and delete this
> preference?
> >>> Are there any JIRA issues related to having multiple history impls on
> >>> Android?
>
Re: Android's History Object
Posted by Joe Bowser <bo...@gmail.com>.
OK, I did the switch.
So, we still have two histories, but instead of the shim that we did,
we now use the browser history as default. This means that the
following will work again:
- iFrames
- Browser history with anchors and params (Fix for the 3.x to 4.0.x
bug was submitted months ago, but we didn't switch until today)
If you want to switch back to the old method, the parameter
"useBrowserHistory" must be set to false. This should be good for old
legacy apps who use a different style of history.
navigator.app.backHistory and history.back should both work now.
Joe
On Tue, Oct 9, 2012 at 12:52 PM, Joe Bowser <bo...@gmail.com> wrote:
> Hey
>
> I created a new ticket for this. I can look into this later today.
>
> https://issues.apache.org/jira/browse/CB-1611
>
>
> On Tue, Oct 9, 2012 at 12:45 PM, Joe Bowser <bo...@gmail.com> wrote:
>> Hey
>>
>> I think there's a few JIRA tickets and a few discussions here for
>> this. We were talking about switching to using the browser history by
>> default instead of our shim for a while. There was a bug with the
>> browser history that caused us to be stuck on the first page twice.
>>
>> https://issues.apache.org/jira/browse/CB-1504
>>
>> I'm happy with us switching to the browser history instead of our
>> current default. That being said, I think we need to follow our six
>> month deprecation policy. I know that the policy sucks, but it's
>> there for a reason.
>>
>> Joe
>>
>> On Tue, Oct 9, 2012 at 12:33 PM, Andrew Grieve <ag...@google.com> wrote:
>>> What's the deal with this?
>>>
>>> <preference name="useBrowserHistory" value="true" />
>>>
>>> I know that this has been the answer to fixing some people's issues...
>>> Should we make the browser history the default and delete this preference?
>>> Are there any JIRA issues related to having multiple history impls on
>>> Android?
Re: Android's History Object
Posted by Joe Bowser <bo...@gmail.com>.
Hey
I created a new ticket for this. I can look into this later today.
https://issues.apache.org/jira/browse/CB-1611
On Tue, Oct 9, 2012 at 12:45 PM, Joe Bowser <bo...@gmail.com> wrote:
> Hey
>
> I think there's a few JIRA tickets and a few discussions here for
> this. We were talking about switching to using the browser history by
> default instead of our shim for a while. There was a bug with the
> browser history that caused us to be stuck on the first page twice.
>
> https://issues.apache.org/jira/browse/CB-1504
>
> I'm happy with us switching to the browser history instead of our
> current default. That being said, I think we need to follow our six
> month deprecation policy. I know that the policy sucks, but it's
> there for a reason.
>
> Joe
>
> On Tue, Oct 9, 2012 at 12:33 PM, Andrew Grieve <ag...@google.com> wrote:
>> What's the deal with this?
>>
>> <preference name="useBrowserHistory" value="true" />
>>
>> I know that this has been the answer to fixing some people's issues...
>> Should we make the browser history the default and delete this preference?
>> Are there any JIRA issues related to having multiple history impls on
>> Android?
Re: Android's History Object
Posted by Joe Bowser <bo...@gmail.com>.
Hey
I think there's a few JIRA tickets and a few discussions here for
this. We were talking about switching to using the browser history by
default instead of our shim for a while. There was a bug with the
browser history that caused us to be stuck on the first page twice.
https://issues.apache.org/jira/browse/CB-1504
I'm happy with us switching to the browser history instead of our
current default. That being said, I think we need to follow our six
month deprecation policy. I know that the policy sucks, but it's
there for a reason.
Joe
On Tue, Oct 9, 2012 at 12:33 PM, Andrew Grieve <ag...@google.com> wrote:
> What's the deal with this?
>
> <preference name="useBrowserHistory" value="true" />
>
> I know that this has been the answer to fixing some people's issues...
> Should we make the browser history the default and delete this preference?
> Are there any JIRA issues related to having multiple history impls on
> Android?