 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 17 Jul 2002 07:52:10 +1000, Chris Cason wrote:
>
> "Chris Cason" <new### [at] delete thispovrayorg> wrote in message
news:3d345e3f@news.povray.org...
>>
>> "Warp" <war### [at] tagpovrayorg> 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.
>
> http://www.povray.org/resources/newsgroups/old-oetut.html
>
> For the effect to be visible, you need to have a style that applies an underline
> (or whatever) for a 'hover' action. I'd presume that Mozilla is doing this all
> the time, but it only ever becomes visible in cases like this.
>
> I have deliberately added a </a> after the word 'this' in the first paragraph to
> make it clear that the effect does indeed end when a </a> is found.
The effect can also be seen on the bottom half of this page this page (not a
POV page):
http://abcnews.go.com/sections/GMA/GoodMorningAmerica/GMA020709Breast_feeding_at_eight.html
--
%HAV-A-NICEDAY email mailto:ste### [at] zeroppsuklinuxnet
Steve web http://www.zeropps.uklinux.net/
or http://start.at/zero-pps
11:24pm up 19 days, 9:43, 1 user, load average: 1.26, 1.18, 1.12
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <new### [at] deletethispovrayorg> wrote:
> http://www.povray.org/resources/newsgroups/old-oetut.html
Hmm... What's the main difference between my example and that? I don't
understand.
--
#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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 16 Jul 2002 18:38:29 -0400, Warp wrote:
> Chris Cason <new### [at] deletethispovrayorg> wrote:
>> http://www.povray.org/resources/newsgroups/old-oetut.html
>
> Hmm... What's the main difference between my example and that? I don't
> understand.
I think it's the hover thingie in the CSS that's doing it as much as
anything else.
--
sphere{z*5,1pigment{rgb.5}finish{reflection.3specular.5}}box{<-50,-3,-50>
<50,-2,50>pigment{checker/*\__\\__/ * \_\\__*/scale 2}finish{ambient.7}}
light_source/*__\\__\\__\\__\\__\( ~ )\__\\__\\__\\__\\*/{<2,5,1>*4,1}
/*\\__\\__\\__\\__\\__\\__\\__\\__\~ -/__\\__\\__\\__\\__\\*//* Steve */
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3d342fad@news.povray.org>, new### [at] deletethispovrayorg
says...
> > the </a> tag. Leaving the </a> tag out is a syntax error. What should the
>
> Not really. Browsers are expected to have the ability to infer a closing
> tag when one should obviously be there. A good example would be the sequence
> <tr><td>Some Text</tr>. I have left out a </td>, but any browser will infer
> its presence and act as if it were supplied.
You should really look at the specs (even if Thorsten for some
strange reasons doesn't like them).
There are elements wich need a closing tag (<div> for example), elements
where it is optional (<td>, <li>), ones where it isn't allowed (<img>,
<br>).
Lutz-Peter
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3d348b44@news.povray.org>, tho### [at] trfde says...
> Nope, the stylesheet is correct.
It is. But its meaning is not the one you think it is.
> Mozilla is broken, or as they call it, it
> has this "feature".
With "a:hover { text-decoration: underline ; color: #ff0000 }"
you say, that you want the content of the element "a" to be underlined if
the mouse is hovering above it.
Thats EXACTLY what Mozilla does.
Hint: The pseudo-class :hover is NOT restricted to links.
Lutz-Peter
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Lutz-Peter Hooge <lpv### [at] gmxde> wrote:
> With "a:hover { text-decoration: underline ; color: #ff0000 }"
> you say, that you want the content of the element "a" to be underlined if
> the mouse is hovering above it.
> Thats EXACTLY what Mozilla does.
So this means that it's all the other browsers which are broken because
they don't do what the CSS is telling them to do?-)
--
#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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3d34c5e8@news.povray.org>, war### [at] tagpovrayorg says...
> So this means that it's all the other browsers which are broken because
> they don't do what the CSS is telling them to do?-)
How do you come to that conclusion?
Povray doesn't implement subsurface scattering - does that mean that it's
"broken"?
There is no need to implement everything in every browser -
but if a web author uses a specific feature he should be aware of the
fact that thare could be a browser that actually implements this feature
to its full extend.
Lutz-Peter
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <MPG.179ed89c4035df85989712@news.povray.org> , Lutz-Peter Hooge
<lpv### [at] gmxde> wrote:
> With "a:hover { text-decoration: underline ; color: #ff0000 }"
> you say, that you want the content of the element "a" to be underlined if
> the mouse is hovering above it.
> Thats EXACTLY what Mozilla does.
No, it is still a bug in Mozilla. They just follow the standard in a "take
every letter in the standard no matter how ambiguous and wrong it is" way.
obviously this is just asking for trouble. But hey, they are the gods who
have to teach the world proper standard HTML, right.
This is like a spellchecker correcting every word it doesn't know. After
all, it knows all words, and there cannot be new ones and it in unfailable.
What is being forgotten here is that blind enforcing of something by a
program is the worst of all implementations.
The consequence of this is that Mozilla's render engine is a badly broken
mess because of the developers' failure to understand something as simple as
"compatibility" (not that it ever was their strength when developing
Netscape 1-4). I had really hoped after so many years they had learned
their lesson and would have come up with something that does a good job
rendering HTML :-(
> Hint: The pseudo-class :hover is NOT restricted to links.
This was only introduced in CSS2 which apparently the people who introduced
this nonsense even failed to notice that it will break every a-name tag
variant out there. Or they failed to put this exception in a obvious
location. But hey, with the bloat of their standards, that is a mistake
easy to make :-(
The specification in CSS1 is correct and makes it explicit:
>>All 'A' elements with an 'HREF' attribute will be put into one and only one of
these groups (i.e. target anchors are not affected). <<
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3d34c5e8@news.povray.org> , Warp <war### [at] tagpovrayorg> wrote:
> So this means that it's all the other browsers which are broken because
> they don't do what the CSS is telling them to do?-)
To the contrary, all other browsers behave like specified by CSS1. As I
just pointed out in my other reply to him the bug might even be in the CSS2
spec and the Mozilla developers simply failed to notice that :-( Of course,
that means it is still a bug in Mozilla.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 17 Jul 2002 12:01:23 +0200, Thorsten Froehlich wrote:
> This is like a spellchecker correcting every word it doesn't know. After
> all, it knows all words, and there cannot be new ones and it in unfailable.
> What is being forgotten here is that blind enforcing of something by a
> program is the worst of all implementations.
You mean like enforcing that mail and web be on the same ISP connection?
--
#local i=.1;#local I=(i/i)/i;#local l=(i+i)/i;#local ll=(I/i)/l;box{<-ll,
-((I/I)+l),-ll><ll,-l,ll>pigment{checker scale l}finish{ambient((I/l)/I)+
(l/I)}}sphere{<i-i,l-l,(I/l)>l/l pigment{rgb((I/l)/I)}finish{reflection((
I/l)/I)-(l/I)specular(I/l)/I}}light_source{<I-l,I+I,(I-l)/l>l/l} // Steve
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
