Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: shr - span elements with title attribute, tooltip?
Date: Wed, 30 Mar 2011 14:02:40 -0500	[thread overview]
Message-ID: <87fwq4bfe7.fsf@lifelogs.com> (raw)
In-Reply-To: <f6d3l820cx.fsf@news.eternal-september.org>

On Wed, 30 Mar 2011 15:39:58 +0200 Richard Riley <rileyrg@googlemail.com> wrote: 

RR> Nightmare times. What was "broken" was the reality level of many CSS
RR> advocates a couple of years ago who somewhat smugly informed everyone to
RR> use CSS rather than tables for "simple" layouts and point blankly
RR> refused any help to those trying to use tables for cross browser layout
RR> "working solutions".

<rant> 

I think 99% of things about HTML, CSS, and web browsers are
either ridiculous or broken.  The good bits (in SGML's domain) are
basically Lisp without `eval'.

Specifically regarding layouts, it's sad that the only layout management
in HTML (without Javascript) is the equivalent of Java's FlowLayout.
Tables are sort of a GridBagLayout, but the idiocy inherent in the
inability (in the early days of HTML) to design and implement a sensible
layout manager for HTML is simply staggering.  Now, of course, it's too
late to make HTML anything but a presentation layer for Javascript.

And then we have CSS, the out-of-band, braindead solution that can
either go inline or separately and which uses selectors and multiple
classes to achieve amazing complexity.  Where HTML is at least a data
language, CSS is a crazy mish-mash of direct instructions, inheritance,
browser hacks, and unmodifiable stylesheets you hope will work but
usually don't.

</rant>

Ted

p.s. Yes, I realize the irony of using SGML tags above.




  reply	other threads:[~2011-03-30 19:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27  7:54 Adam Sjøgren
2011-03-27  8:32 ` [PATCH] Show title attribute of span elements as mouse over text Adam Sjøgren
2011-03-28 18:58 ` shr - span elements with title attribute, tooltip? Ted Zlatanov
2011-03-28 19:17   ` Adam Sjøgren
2011-03-28 19:33     ` Ted Zlatanov
2011-03-28 19:59       ` Adam Sjøgren
2011-03-28 20:14         ` Ted Zlatanov
2011-03-28 20:34           ` Adam Sjøgren
2011-03-28 21:02             ` Adam Sjøgren
2011-03-28 21:07             ` Ted Zlatanov
2011-03-29 17:52   ` Lars Magne Ingebrigtsen
2011-03-29 18:07     ` Ted Zlatanov
2011-03-29 18:23       ` Lars Magne Ingebrigtsen
2011-03-29 18:46         ` Ted Zlatanov
2011-03-29 19:04           ` Lars Magne Ingebrigtsen
2011-03-29 19:16             ` Ted Zlatanov
2011-03-29 19:35               ` Lars Magne Ingebrigtsen
2011-03-29 19:50                 ` Ted Zlatanov
2011-03-29 20:15                   ` Lars Magne Ingebrigtsen
2011-03-29 21:31                     ` Lars Magne Ingebrigtsen
2011-03-30  6:05                       ` Adam Sjøgren
2011-03-30 13:13                       ` Ted Zlatanov
2011-03-30 13:39                         ` Richard Riley
2011-03-30 19:02                           ` Ted Zlatanov [this message]
2011-04-03 12:10                             ` Lars Magne Ingebrigtsen
2011-03-29 21:15             ` Adam Sjøgren
2011-03-29 21:09     ` Adam Sjøgren
2011-03-30  0:58     ` Kevin Ryde

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=87fwq4bfe7.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@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.
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 NNTP newsgroup(s).