dperez schrieb:
> This is a very easy task. I can do it in the next days
>
>
OK, go ahead.
Best Fabian
> Fabian Jakobs-2 wrote:
>
>> I think this is a good idea. We are pretty busy right now so it wont be
>> fixed right now. Could you open a bug for this issue so it doesn't get
>> lo
This is a very easy task. I can do it in the next days
Fabian Jakobs-2 wrote:
>
> I think this is a good idea. We are pretty busy right now so it wont be
> fixed right now. Could you open a bug for this issue so it doesn't get
> lost?
>
--
View this message in context:
http://www.nabb
dperez schrieb:
> Hi,
>
> Thanks for your answer.
> It could do nothing (and possibly log a warning) if it detects is inside a
> frame.
>
>
> Fabian Jakobs-2 wrote:
>
>> since no browser has a API for browser history, every implementation of
>> browser history consists of a bunch of hacks :-(.
Hi,
Thanks for your answer.
It could do nothing (and possibly log a warning) if it detects is inside a
frame.
Fabian Jakobs-2 wrote:
>
> since no browser has a API for browser history, every implementation of
> browser history consists of a bunch of hacks :-(. So does our and with
> the pre
dperez schrieb:
> Hi,
>
> I use successfully the facilities in class qx.client.History.
> It's really easy to use. But when I load my page inside a frame
> (window.parent != window), it stops working ok. Any intent to update the
> history, produces a change in the current URL.
>
> I consider this
Hi,
I use successfully the facilities in class qx.client.History.
It's really easy to use. But when I load my page inside a frame
(window.parent != window), it stops working ok. Any intent to update the
history, produces a change in the current URL.
I consider this a bug.
The workaround I'm u
