Bug 65619
Summary: | [Qt] QWebSettings::DeveloperExtrasEnabled requires persistent storage | ||
---|---|---|---|
Product: | WebKit | Reporter: | Holger Freyther <zecke> |
Component: | WebKit Qt | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | ademar |
Priority: | P2 | Keywords: | Qt, QtTriaged |
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Holger Freyther
With r92082 (e76e2f263222bb347f719cc876b05ba7de754ade) only enabling the DeveloperExtras on the QWebSettings will lead to the inspector being shown but no content/icons being displayed, only after QWebSettings::enablePersistentStorage is used the inspector starts to work.
The easiest way to find that out would be to remove enablePersistentStorage from the Tools/QtTestBrowser/main.cpp:LauncherApplication::applyDefaultSettings.
I don't know if this applies to the latest trunk, I don't know if it applies to QtWebKit. I can't update WebKit due the lack of the bandwidth (and also in terms of processing power).
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Ademar Reis
It's indeed broken on trunk (r92298), but OK in the QtWebKit-2.2 branch.
Jocelyn Turcotte
=== Bulk closing of Qt bugs ===
If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary.
If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.