lp:~osomon/oxide/clearCache

Branch merges

Propose for merging

No branches dependent on this one.

On hold for merging into lp:~oxide-developers/oxide/oxide.trunk

Chris Coulson: Pending requested 2015-03-09

Diff: 425 lines (+224/-10)

11 files modified

qt/core/browser/oxide_qt_web_context.cc (+9/-1)
qt/core/browser/oxide_qt_web_context.h (+3/-1)
qt/core/glue/oxide_qt_web_context_adapter.cc (+5/-1)
qt/core/glue/oxide_qt_web_context_adapter.h (+3/-1)
qt/qmlplugin/oxide_qml_plugin.cc (+3/-1)
qt/quick/api/oxideqquickwebcontext.cc (+7/-1)
qt/quick/api/oxideqquickwebcontext_p.h (+4/-1)
qt/tests/qmltests/api/tst_WebContext_clearCache.py (+17/-0)
qt/tests/qmltests/api/tst_WebContext_clearCache.qml (+55/-0)
shared/browser/oxide_browser_context.cc (+97/-2)
shared/browser/oxide_browser_context.h (+21/-1)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1260014: Add an API to manage local data (cookies, local storage, app cache, indexed DB and web DB)

Medium

Triaged

Link a bug report

Related blueprints

1009. By Olivier Tilloy on 2015-03-09

Add a unit test for the new clearCache() method.

1008. By Olivier Tilloy on 2015-03-09

Add a clearCache() method on the WebContext.

1007. By Chris Coulson on 2015-03-06

Bump Chromium rev to 42.0.2311.22

1006. By Chris Coulson on 2015-03-05

r1005 should not be applied to component builds

1005. By Chris Coulson on 2015-03-05

Disable webcore debug symbols and link with --no-keep-files-mapped on native x86 builds because of linker OOM

1004. By Chris Coulson on 2015-03-05

Tidy up the linker settings a bit:
- Now we depend on GCC 4.8, we can use -fuse-ld=gold.
- Don't remove -Wl,--reduce-memory-overheads from ldflags - it doesn't appear to be added by Chromium now.
- Don't use -Wl,--no-map-whole-files when the host is arm - gold defaults to this on 32-bit architectures anyway.
- Don't use -Wl,--no-keep-memory - this is BFD specific

1003. By Chris Coulson on 2015-03-05

Be careful when posting tasks to the UI thread as they may not run, in which case the pending tasks will be deleted at shutdown. This causes shutdown crashes when those tasks reference classes that assume that Chromium is running

1002. By Chris Coulson on 2015-03-04

Explicitly disallow calls to CompositorUtils::CreateGLFrameHandle once shutdown has begun

1001. By Chris Coulson on 2015-03-04

Bump Chromium rev to 42.0.2311.15

1000. By Olivier Tilloy on 2015-03-04

Add a unit test to verify that restoring the state of a navigation that had triggered an error triggers the error again.
Also update an existing test to verify that reloading a page that had triggered an error generates the same sequence of load events.