![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Thorsten Froehlich <tho### [at] trf de> wrote:
> They should have been two distinct tags, but unfortunately aren't the
> end tags for the "name" variant of the a tag does absolutely nothing useful
> and only adds clutter. Plus it would be no problem to handle it correctly.
> So why add user inconvenience.
As I wrote in the other article, I just tested the <a name="..."> behaviour
with Mozilla, and see no misbehaviour (ie. Mozilla does not need the </a> as
reported). I don't understand.
--
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <3d342fad@news.povray.org>,
"Chris Cason" <new### [at] delete this povray org> wrote:
>In that case, the presence of a "</a>" is implied immediately after the <a
>...>,
>simply because it can't be any other way. This is the way browsers have worked
>since the start, to my knowledge, and one that doesn't work that way is IMO
>broken (and I don't care what the standards say, it's broken).
No, this is not the way things have worked from the start, nor is it the
way things should work now. Anchoring was originally expected to anchor
text: the original GUI browser (Mosaic) would crash if a page tried to
anchor nothing.
If you look in O'Reilly's HTML Definitive Guide, you'll see that their
anchor examples enclose text. (see p. 197, section 6.3, of the fourth
edition).
Anchoring around something is more useful for computer-oriented browsing
than anchoring around nothing. I have used this in my own scripts in the
past, and suspect other people have as well.
As we move away from anchoring with <a name="...">text</a> and towards
anchoring via IDs in existing tags, most anchors will once again enclose
text.
An anchor needs a closing tag in the same way as <em> and <strong> need
closing tags. There isn't any "implied ending" except perhaps at the end
of a paragraph-level tag.
Jerry
--
http://www.hoboes.com/jerry/
"Give a man a fish and you feed him for a day. Teach him to fish, and you've
depleted the lake."--It Isn't Murder If They're Yankees
(http://www.hoboes.com/jerry/Murder/)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <3d3433e0@news.povray.org> , Warp <war### [at] tag povray org> wrote:
> With Mozilla I don't see any odd behaviour. None of the text is underlined
> or anything else. Everything seems to work as it should.
Not surprising as you alway place it at the end of a structure element.
Even Mozilla isn't _that_ stupid!
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trf de
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <jer### [at] netplex aussie org> , Jerry
<jer### [at] acusd edu> wrote:
> An anchor needs a closing tag in the same way as <em> and <strong> need
> closing tags. There isn't any "implied ending" except perhaps at the end
> of a paragraph-level tag.
But then, why does Mozilla turn it into a *link*, inferring that it has a
"href" attribute while it does not? That is a bug!!! The standard is very
precise about the difference between "href" and "name" type a tags. The
"name" variant does behave like a destination, not an origin...
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trf de
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Thorsten Froehlich <tho### [at] trf de> wrote:
>> With Mozilla I don't see any odd behaviour. None of the text is underlined
>> or anything else. Everything seems to work as it should.
> Not surprising as you alway place it at the end of a structure element.
> Even Mozilla isn't _that_ stupid!
I didn't understand. A short example would have been more clear.
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Warp" <war### [at] tag povray org> wrote in message news:3d3433e0@news.povray.org...
> Could someone give me a (small) example where the reported misbehaviour
> happens?
I'll see if I can restore a copy of the page where this was happening.
-- Chris
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Tue, 16 Jul 2002 18:21:57 +0200, Thorsten Froehlich <tho### [at] trf de> wrote:
> In article <jer### [at] netplex aussie org> , Jerry
><jer### [at] acusd edu> wrote:
>> An anchor needs a closing tag in the same way as <em> and <strong> need
>> closing tags. There isn't any "implied ending" except perhaps at the end
>> of a paragraph-level tag.
>
> But then, why does Mozilla turn it into a *link*, inferring that it has a
> "href" attribute while it does not? That is a bug!!!
But it doesn't - I'm willing to bet all this whining is
because the attached CSS has "a { whatever-style: }"
instead of "a:link { whatever-style; }". At least that causes
the described behavior in 0.9.9.
Everyone, please stop whining about how the web, html
specs and browsers are broken; they have been that way
as long as they've existed and there will never be
a change to that. It sucks, but there's nothing anyone
can (or will) do about it - standard compliance or
unambiguous specifications just don't thrive in the
electronic world.
--
Antti Arola, edistyksenvastainen retropaskiainen
This message written by a complete asshole.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Antti Arola" <aea### [at] iobox fi> wrote in message
news:slr### [at] skavara ese...
<snip>
Who is this Antti? How dare a sane person contribute to the discussion...
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Tue, 16 Jul 2002 20:46:31 +0100, Tom Melly <tom### [at] tomandlu co uk> wrote:
> "Antti Arola" <aea### [at] iobox fi> wrote in message
> news:slr### [at] skavara ese...
>
><snip>
>
> Who is this Antti?
I thought my sig said it all. I fully mean it. Dead serious.
That is also why I rather lurk.
> How dare a sane person contribute to the discussion...
Dunno. Maybe one of the sane participants would care to
comment?
--
Antti Arola, edistyksenvastainen retropaskiainen
This message written by a complete asshole.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <slr### [at] skavara ese> , Antti Arola <aea### [at] iobox fi>
wrote:
> But it doesn't - I'm willing to bet all this whining is
> because the attached CSS has "a { whatever-style: }"
> instead of "a:link { whatever-style; }". At least that causes
> the described behavior in 0.9.9.
Nope, the stylesheet is correct. Mozilla is broken, or as they call it, it
has this "feature".
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trf de
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |