https://bugs.kde.org/show_bug.cgi?id=382587
--- Comment #5 from Laurent Montel <mon...@kde.org> --- (In reply to Patrick from comment #4) > (In reply to Laurent Montel from comment #3) > > (In reply to Patrick from comment #2) > > > I did some debugging and found that the scroll position is remembered by > > > the > > > chromium backend used by Qt. The scroll position restore used by > > > akregator/messagelib isn't working because javascript is disabled. > > > > it's wrong as it's execute in specific environment. > > js is enabled as private => it's execute for sure. > > > Javascript is enabled for external URLs, loaded in a new tab. But javascript > is disabled for article content stored inside the feed, shown next to the > article list (in widescreen view) or below the article list (in normal > view). See the constructor of ArticleViewerWebEnginePage. I know as I implemented it :) but we can call javascript even if it's disabled it as we execute it in specific "room". For sure as it works as it in kmail (coded that I implemented too) > > > > > > > > As > > > enabling javascript might have side effects, a possible solution is > > > loading > > > a blank page before a new article is loaded in the viewer. You could do > > > this > > > in ArticleHtmlWebEngineWriter::begin() by replacing: > > > mWebView->load(QUrl()); > > > with > > > mWebView->load(QUrl(QStringLiteral("about:blank"))); > > > > ???? > > The idea was to clear the page and reset the scroll position to the top, but > it doesn't work well with the rest of the code. -- You are receiving this mail because: You are the assignee for the bug.