Re: WWWAnchor as a WWWAnchor's child. Clarification needed.

James Waldrop (sulam@construct.net)
Wed, 22 Nov 1995 21:42:46 -0800

>Is the browser's behaviour defined in cases where WWWAnchor
>is a child of WWWAnchor ? Take this for example :
>
> WWWAnchor {
> name "http://blah.blah/~blah"
> DEF ClickMe Cube {}
> WWWAnchor {
> name "http://bu.bu/~bu"
> DEF ClickMeToo Cone {}
> }
> }
>
>What would happen if I clicked on the cone ? Will it take me to
>http://blah.blah/~blah or to http://bu.bu/~bu ? I don't think
>this is clear in the VRML 1.0 spec, and some modelers (Fountain)
>generate files with cases where WWWAnchor has a WWWAnchor child.
>Maybe this should be clarified for 1.1 spec ?

Good question. This came up at one point and got locally clarified,
but I don't know if it got into 1.1 (either Bernie's list or the one
the VAG produced).

The general upshot, if I remember correctly, is that the first object
in the hierarchy wins. Of course, I might be wrong about this.

I suggsst you try it out on WebSpace, WebFX, Scout, and WorldView.
That'll give you a rough consensus on what the supposed behavior is.

James

--
James Waldrop                          /          Technical Director
sulam@construct.net                /              Construct Internet Design
sulam@well.com                 /                  http://www.construct.net

  • Next message: James Waldrop: "Re: Textures"
  • Previous message: James Waldrop: "Re: WWWAnchor as a WWWAnchor's child. Clarification needed."
  • In reply to: Mario Juric - XV Gimnazija: "WWWAnchor as a WWWAnchor's child. Clarification needed."
  • Next in thesad: Michael Pichler: "Re: WWWAnchor as a WWWAnchor's child. Clarification needed."