| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Just 3 lines fixes ;)
Also clean up in the dir structure...
|
|
|
|
| |
Preparing repo to merge rekonq2 code...
|
| |
|
|
|
|
|
|
|
|
|
| |
& Search also for favicon.ico files
This seems to be the unique method to surely workaround this bug
rekonq encounters when tries to load an unextant favicon with KIO (see
BUG:289029
)
|
|
|
|
|
|
|
|
| |
This patch implements session management. Most of the ideas are taken
from Konsole, which is also a KUniqueApplication but manages session
restoring correctly.
REVIEW: 103658
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit, while does not perfectly fix the issue, "workaround" it
a lot to fix crashes on private mode enter/exit
- improve session store/restore
- improve session manager code
- calm down kDebug messages
- applies code style
CCBUG: 268328
|
|
|
|
|
| |
I think we need to consider the two cases (normal restore vs restore
from crash) in different ways.
|
|
|
|
|
|
|
|
| |
We finally have it :D
CCMAIL: akreuzkamp@web.de
REVIEW: 100604
REVIEWED-BY: adjam, elproxy
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Shows the about:closedTabs page in the background.
Task: https://bugs.kde.org/show_bug.cgi?id=249228
|
| |
|
|
|
|
|
|
|
|
|
| |
This let me think about the need of reimplementing it and all History
to support more infos (eg: zoom)
closing one bug and opening another :)
BUG:228480
|
|
|
|
| |
Speed up compilation & linking on Win, Lin & Mac. Step 1
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This fix some issues, about some "stupid" sites whose js
sends strange "about:blank" requests (just found 2!!)
|
|
|
|
|
|
| |
- moved from DataStream to TextStream (we use strings..)
- implemented a semaphore (m_safe)
- closing every time file
|
|
This is HEAVILY based on code from Lionel and Yoram branches.
But this code behaves differently: it restores rekonq tabs (just) on crash.
Thanks to Lionel suggestions, it seems "better" than my initial idea :)
It is quite extensible. We need just to fix it better as possible and then
manage its behaviour in newInstance code.. ;)
|