From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Yuchen Pei <hi@ypei.me>, 50500@debbugs.gnu.org
Subject: bug#50500: Add ways to copy id bookmark link in eww
Date: Sat, 11 Sep 2021 22:06:04 +0300 [thread overview]
Message-ID: <87ee9vx78j.fsf@mail.linkov.net> (raw)
In-Reply-To: <874karnvo1.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 11 Sep 2021 14:28:30 +0200")
>> 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.
>
> I'm not sure I understand -- do you want eww to have a visual indicator
> on all HTML elements that have an id? That would be ... weird and ugly,
> I think? Github doesn't display anything in particular on elements with
> ids per se -- they do display a link icon on sections, and the sections
> have ids, but that's because they generated the HTML that way.
That's why I said "*IF* eww will support some visual indication" :-)
But I don't think such visual distraction would be appreciated by users.
next prev parent reply other threads:[~2021-09-11 19:06 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
2021-09-11 12:28 ` Lars Ingebrigtsen
2021-09-11 19:06 ` Juri Linkov [this message]
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=87ee9vx78j.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).