all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62574@debbugs.gnu.org
Subject: bug#62574: [PATCH] Preserve peer information for web page in eww-readable
Date: Sat, 01 Apr 2023 11:58:52 +0300	[thread overview]
Message-ID: <m15yagrnar.fsf@eshelyaron.com> (raw)
In-Reply-To: <83jzywyp4i.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Apr 2023 11:37:33 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Fri, 31 Mar 2023 21:55:09 +0300
>> From:  Eshel Yaron via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>> 
>> Here's a small patch that addresses a slight annoyance in EWW.
>
> Thanks, but can you please post a recipe for showing the effect of
> this change?

Sure:

1. Start emacs -Q
2. Type M-x eww RET https://gnu.org RET
   (any HTTPS site with a valid certificate will do)
3. Notice the green color of the page's title in the header line that
   indicates that the peer's certificate is valid
   (You can also check C-h v header-line-format RET to validate that the
   eww-valid-certificate face is applied to the title portion of the
   header line)
4. Now type R to execute eww-readable
5. Note that the color of page's title in the header line changed (it is no longer green)






  reply	other threads:[~2023-04-01  8:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 18:55 bug#62574: [PATCH] Preserve peer information for web page in eww-readable Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-01  8:37 ` Eli Zaretskii
2023-04-01  8:58   ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-04-02  7:40     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m15yagrnar.fsf@eshelyaron.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=62574@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=me@eshelyaron.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.