From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Philip Kaludercic <philipk@posteo.net>, 69132@debbugs.gnu.org
Subject: bug#69132: [ELPA] Remove jQuery from elpa.gnu.org
Date: Sat, 17 Feb 2024 23:05:13 -0500 [thread overview]
Message-ID: <jwv5xymxw1n.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <b77a0e94-cb3a-4325-8fd7-dbbee6b52068@gutov.dev> (Dmitry Gutov's message of "Sun, 18 Feb 2024 00:49:56 +0200")
>> But is there a reason we want it to look identical in all browsers?
> The end goal of a graphical design is usually a particular look.
> A handful of minor deviations would work against that.
The thing I hate most about the WWW is that it's running on *my*
computer but it's completely under the control of the web site.
So I don't see why we should consider obtaining "a particular look" to
be a good reason for doing a reset.
A good reason would be if without a reset the page can sometimes be
illegible, or something like that.
Stefan
next prev parent reply other threads:[~2024-02-18 4:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 19:41 bug#69132: [ELPA] Remove jQuery from elpa.gnu.org Philip Kaludercic
2024-02-14 23:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-15 8:12 ` Philip Kaludercic
2024-02-15 11:07 ` Philip Kaludercic
2024-02-15 15:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-17 18:25 ` Stefan Kangas
2024-02-17 20:57 ` Dmitry Gutov
2024-02-17 21:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-17 22:26 ` Dmitry Gutov
2024-02-17 22:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-17 22:49 ` Dmitry Gutov
2024-02-18 4:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-02-18 12:14 ` Dmitry Gutov
2024-02-18 14:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-18 14:24 ` Dmitry Gutov
2024-02-18 14:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-18 14:38 ` Dmitry Gutov
2024-02-18 3:28 ` Richard Stallman
2024-02-18 4:07 ` Corwin Brust
2024-02-18 4:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 2:56 ` Richard Stallman
2024-02-22 12:00 ` Philip Kaludercic
2024-02-25 3:13 ` Richard Stallman
2024-02-25 10:55 ` Philip Kaludercic
2024-02-25 15:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-18 15:07 ` Philip Kaludercic
2024-02-18 18:19 ` Corwin Brust
2024-02-24 10:03 ` Philip Kaludercic
2024-02-25 10:06 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-25 10:44 ` Philip Kaludercic
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=jwv5xymxw1n.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=69132@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
/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).