From: Juri Linkov <juri@linkov.net>
To: Yuchen Pei <hi@ypei.me>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 50500@debbugs.gnu.org
Subject: bug#50500: Add ways to copy id bookmark link in eww
Date: Fri, 10 Sep 2021 19:08:44 +0300 [thread overview]
Message-ID: <87v938ijxf.fsf@mail.linkov.net> (raw)
In-Reply-To: <87sfycwpjl.fsf@ypei.me> (Yuchen Pei's message of "Fri, 10 Sep 2021 23:03:42 +1000")
>> Well, people put ids on all kinds of elements, but they're not generally
>> meant to be used for navigation. (I mean, sometimes they are, but
>> statistically speaking, they're not.)
>>
>> So I'm not sure that `w' in general should be doing this in eww.
>> Anybody else got an opinion?
>
> Makes sense. How about adding it as a customization variable, so that one
> can customize whether `w` also includes the id bookmark part and by default
> it does not. It is often useful to save more precise positions in web
> page documents.
The problem is that "id" from such HTML:
<h5 id="section13">13. Use with the GNU Affero General Public License.</h5>
is not rendered on UI, so the user doesn't know that here is some "id"
available for bookmarking. But, for example, github.com for the sections
of the README.org file with ids displays visual indication that looks like
a chain icon on the left. If eww will support some visual indication about
ids used on the page like github does, then it will make sense also to
include the displayed id to the copied link.
next prev parent reply other threads:[~2021-09-10 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 6:43 bug#50500: Add ways to copy id bookmark link in eww Yuchen Pei
2021-09-10 11:15 ` Lars Ingebrigtsen
2021-09-10 13:03 ` Yuchen Pei
2021-09-10 16:08 ` Juri Linkov [this message]
2021-09-11 12:28 ` Lars Ingebrigtsen
2021-09-11 19:06 ` Juri Linkov
2022-08-25 14:49 ` Lars Ingebrigtsen
2021-09-11 12:34 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v938ijxf.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=50500@debbugs.gnu.org \
--cc=hi@ypei.me \
--cc=larsi@gnus.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).