https://bugs.kde.org/show_bug.cgi?id=467850

--- Comment #3 from avlas <jsar...@gmail.com> ---
(In reply to Stefano Crocco from comment #2)
> (In reply to Stefano Crocco from comment #1)
> > (In reply to avlas from comment #0)
> > > SUMMARY
> > > 
> > > History fails to remember internal browsing in some sites such as GitHub. 
> > > It
> > > works fine in other browsers such as Firefox
> > > 
> > > STEPS TO REPRODUCE
> > > 1. open a new tab
> > > 2. go to https://github.com/KDE/konqueror
> > > 3. click on pull requests (it moves to
> > > https://github.com/KDE/konqueror/pulls)
> > > 4. go back (button or alt+left)
> > > 
> > > OBSERVED RESULT
> > > 
> > > it comes back to new tab
> > > 
> > > EXPECTED RESULT
> > > 
> > > it should go back to https://github.com/KDE/konqueror instead
> > 
> > This is caused by the underlying web engine (QtWebEngine) not informing
> > Konqueror that a new page has been loaded. I  created a bug report for
> > QtWebEngine (https://bugreports.qt.io/browse/QTBUG-115589), because I think
> > this is not supposed to happen: let's see if it gets some answers.
> > 
> > Unfortunately, working around this issue would either require heavy changes
> > in the way Konqueror manages history or using different ways to detect that
> > a different page has been loaded, which could have unwanted side effects.
> > I'll wait for some answers to my bug report before trying any of these
> > workarounds.
> 
> According to Qt, this is not a bug because even if the URL changes, the page
> actually
> remains the same. This means that I'll have to find out how to change how
> WebEnginePart
> handles history to account for situations like this. I fear it won't be
> easy: I already tried the
> most obvious approach (reacting to the change in the URL rather than to the
> loading of a
> new page) but it doesn't work.

Hmm, what do they mean by the page remains the same? I don't get it. The URL is
different and the content is too. I can see how konqueror loads the new content
with the progress bar.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to