public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
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 13:02:15 +0200	[thread overview]
Message-ID: <1433847735.25208.154.camel@ipfire.org> (raw)
In-Reply-To: <op.xzyl5jsgcahio0@atl-uetersen.atlantisgmbh.local>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

On Tue, 2015-06-09 at 12:59 +0200, Larsen wrote:
> On Tue, 09 Jun 2015 12:53:08 +0200, Michael Tremer  
> <michael.tremer(a)ipfire.org> wrote:
> 
> > Is there a certain reason why this is done by using Javascript? An <a>
> > tag would have worked fine as well I think. That would require to embed
> > the image by using the <img> tag, but that is probably the cleaner
> > solution any way...
> 
> I used this as a starting point:
> http://stackoverflow.com/questions/4465923/a-href-link-for-entire-div-in-html-css
> 
> The <a>-tag didn´t work when I wrapped it around the <div>-tag (and it  
> would only be allowed for HTML5).
> I didn´t think about using an <img>-tag as I thought that it was cleaner  
> as it is by using CSS.
> 
> 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.

-Michael

> 
> 
> Lars

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-06-09 11:02 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 [this message]
2015-06-09 11:13       ` Larsen
2015-06-09 12:13         ` Michael Tremer
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=1433847735.25208.154.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