| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
also, a tiny fix for some visual glitches...
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- inline spell highlighter. This requires WebKit 2.3 to work.
- Addition of a suggested replacement word list to the context menu,
for the word right clicked on
- A standard modeless spell check dialog that works on the current
editable text (or selection).
Heavily cribbed from Dawit's work on kdewebkitpart.
oops... also a codingstyle script round here... :)
|
|
|
|
|
| |
Just 3 lines fixes ;)
Also clean up in the dir structure...
|
|
|
|
| |
Preparing repo to merge rekonq2 code...
|
|
|
|
|
|
|
| |
Check if the URL of the current tab is even valid before checking its
protocol.
REVIEW: 106561
|
|
|
|
| |
BUG: 283178
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Create a local function to get rid of code repetition.
I know this is a bit hackish (at least the way I did it)
but it works well in my tests against the three situations:
- restore crashed sessions
- restore saved sessions
- restore from private sessions
- restore user sessions (restarting KDE)
|
|
|
|
| |
BUG:292773
|
|
|
|
|
|
| |
Commit 5b07ae28 introduced a bug here because no tab is now created by
default in the restoring window
BUG: 292586
|
| |
|
| |
|
|
|
|
|
|
|
| |
Factor out all code that loads the DOM Document, and use proper calls
in each method.
REVIEW: 103722
|
|
|
|
|
|
|
|
|
| |
& 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
|
|
|
|
| |
PS: ignore about urls in the session manager
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
First, I'm really sorry for this bad commit ('git' talking..).
The fact is that the 3 bugs fixed here were found chained playing
with close code. Here it is the report:
- fix close window (it now really appears on multiple window closing)
- fix saveSession (saving one call for each site loaded and storing
better information): saveSession is now called on loadFinished
- clean up some compilation warnings
|
| |
|
|
|
|
|
|
|
|
| |
We finally have it :D
CCMAIL: akreuzkamp@web.de
REVIEW: 100604
REVIEWED-BY: adjam, elproxy
|
|
|
|
|
|
| |
- QL1S
- one stupid kDebug less
- codingstyle
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
an rApp shortcut for Application::instance,
clean up code switching to use the new shortcut
Reviewed by: adjam
|
|
|
|
|
|
| |
Shows the about:closedTabs page in the background.
Task: https://bugs.kde.org/show_bug.cgi?id=249228
|
| |
|
| |
|
|
|
|
| |
BUG:246268
|
|
|
|
|
| |
SettingOpenTab --> NewTab (according to settings)
NewCurrentTab --> NewFocusedTab
|
|
|
|
| |
BUG:241495
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Now rekonq tries just 1 time to recover from crash. In Italy
we say "Perseverare e' diabolico"...
|
| |
|
| |
|
|
|
|
|
| |
* it basically represents a tab in rekonq
* everything that happens within one tab should go here (wallet bar, find bar?)
|
|
|
|
| |
BUG: 211913
|
|
|
|
|
|
| |
- 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.. ;)
|