From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Link the IPFire logo to ipfire.org
Date: Tue, 09 Jun 2015 14:13:55 +0200 [thread overview]
Message-ID: <1433852035.25208.164.camel@ipfire.org> (raw)
In-Reply-To: <op.xzyms4dqcahio0@atl-uetersen.atlantisgmbh.local>
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
On Tue, 2015-06-09 at 13:13 +0200, Larsen wrote:
> On Tue, 09 Jun 2015 13:02:15 +0200, Michael Tremer
> <michael.tremer(a)ipfire.org> wrote:
>
> >> I do know that some have JS deactivated and don´t like it, but in this
> >> case there is nothing lost.
> >
> > If someone disables JS they will already have issues with other parts of
> > the web user interface and of course most of the "web 2.0".
> >
> >> Is there anything else wrong with using JS?
> >
> > Not in general. I just find it a rather complex solution for a simple
> > problem. The plain HTML approach would be much better and work for those
> > who disable JS, too.
>
> But then you loose CSS, don´t you?
What do you mean by loose? That should be changed then, yes.
The final HTML code would look something like this:
<div id="logo">
<a href="http://www.ipfire.org">
<img src="logo.png" ...>
</a>
</div>
The CSS properties should be changed that the background image is
removed and the content is centered. The final result should like the
same in the end.
> And if someone has actually disabled JS, they will notice other problems
> as you mentioned before, so it´s unlikely they will even noticed that they
> cannot click on the IPFire logo to get to the homepage.
>
>
> Lars
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-09 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 20:50 Larsen
2015-06-09 10:53 ` Michael Tremer
2015-06-09 10:59 ` Larsen
2015-06-09 11:02 ` Michael Tremer
2015-06-09 11:13 ` Larsen
2015-06-09 12:13 ` Michael Tremer [this message]
2015-06-09 12:35 ` Larsen
2015-06-09 20:00 Larsen
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=1433852035.25208.164.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox