| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This reverts commit 962d9dd1fc5fe530dc9a7e29c95a0a2c1e7aa885.
|
|
|
|
|
|
|
|
|
|
|
| |
Conflicts:
src/adblock/adblockwidget.h
src/application.h
src/history/historymanager.h
src/tabpreviewpopup.cpp
Backported from master branch
|
| |
|
|
|
|
|
|
|
| |
- QL1S/QL1C
- single-char QString efficiency
- explicit ctors
- normalized signals & slots
|
|
|
|
| |
CCMAIL: aspotashev@gmail.com
|
| |
|
|
|
|
|
|
| |
This was the crash (probably) occurred during ds2011 presentation.
Check if a list is empty before pulling something (with QList::first()
method).
|
|
|
|
|
|
| |
- QL1S
- one stupid kDebug less
- codingstyle
|
|
|
|
|
|
| |
- strings
- bool WebPage::hasSslValid() const
- check all the certificate chain
|
|
|
|
|
|
|
|
|
|
| |
I hope I addressed here a number of fixes in my first implementation:
- working hasSSLValid() function (checking cert validity and chain errors)
- escaping certificate strings
- typos (Sha256/Md5, supportedCipherBits/usedCipherBits)
- encryption check (at least I hope so)
CCMAIL: rich@kde.org
|
|
|
|
|
|
| |
Hopefully addressed the problems against our (new) SSL code.
CCMAIL:timb@nth-dimension.org.uk
|
| |
|
|
|
|
| |
Now we are ready for the fight...
|
|
|
|
|
|
|
| |
These are last changes to clean up and improve SSL rekonq
communications.
It is yet missing a proper SSL errors API integration. You just need
to wait for the next commit...
|
|
|
|
|
|
|
| |
This commit changes rekonq history data struct to manage also the
first time you visited a site.
This way we can "expose" this new info in the SSL widget.
(We can obviously do a lot more with it...)
|
|
|
|
|
|
| |
Now they really seem "similar" to the ones provided by Google Chrome
and Firefox.
They all need further improvements, anyway...
|
|
|
|
|
|
|
|
| |
While the widget "copies" and "rethink" Google Chrome actual one,
the dialog has been implemented starting from the comparison
between the ones we have in KDE, Google Chrome's and Firefox's.
I have to start from somewhere...
|
|
|
|
|
|
|
| |
This new (initial) implementation follows the guidelines
found "looking" at Google Chrome and Mozilla Firefox SSL
info windows.
More improvements coming...
|
|
|