| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
http://www.gnu.org/licenses/rms-why-gplv3.html
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
For a better future. Apologies when your 'git blame' resolves to this.
I'm actually really impressed how well uncrustify works. This required
only a little one-time manual work to avoid extra space in 'else {'.
This breaks function prototype alignment, but we should get rid of most
of those anyway.
We decided to start aligning function parameters, like other GNOME
applications. It looks nicer this way, and I couldn't teach uncrustify
the previous Epiphany style.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We used to do this:
* HTTP pages -> no security indicator
* HTTPS pages with mixed content -> insecure warning icon
* HTTPS pages with no mixed content -> secure lock icon
Now we do this:
* HTTP pages and HTTPS pages with mixed content -> insecure warning icon
* HTTPS pages with no mixed content -> secure lock icon
https://bugzilla.gnome.org/show_bug.cgi?id=744064
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Instead of bringing up the certificate details dialog when clicking on
the lock icon in the address bar, instead bring up a popover that
displays information about the security status of this site, including a
button to open the certificate dialog.
https://bugzilla.gnome.org/show_bug.cgi?id=666808
|
|
|
Since an attacker can modify some contents of these pages, we should
display a warning icon instead of a secure lock, following the convention
of major browsers.
https://bugzilla.gnome.org/show_bug.cgi?id=666808
|
