https://bugs.kde.org/show_bug.cgi?id=467850
--- Comment #4 from Stefano Crocco <stefano.cro...@alice.it> --- (In reply to avlas from comment #3) > 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. According to their answer, GitHub uses the History API (https://developer.mozilla.org/en-US/docs/Web/API/History_API), in particular the pushState and/or replaceState methods. They allow the web page to simulate navigating to a new URL without actually doing so. According to the Chromium documentation (on which QtWebEngine is based), this isn't treated as navigating to a new page (https://chromium.googlesource.com/chromium/src/+/main/docs/navigation_concepts.md#Same_Document-and-Cross_Document-Navigations). This is treated the same way navigating to another fragment (the part after the # of an URL) of the current document is. Unfortunately, from the user's point of view this is rather unintuitive (unlike the fragment case, where it's clear that we're still in the same page). By the way, when clicking on the pull requests link from https://github.com/KDE/konqueror I don't see the progress bar in Konqueror (the one on the bottom right of the status bar), but only a thin progress bar at the top of the page which is provided by the GitHub page itself. -- You are receiving this mail because: You are watching all bug changes.
