Page jumps... can't get them to work!...

Dec 1st, 2009 at 08:50 AM
User 1948478 Photo

Per
Senior Advisor
1,850 posts

David,

Our posts may be crossing here so I assume that what you tried was just to add the anchor closing tag?
If you can place the HTML code for the anchor just after the body tag, as I suggested in my more recent post, I think you'll find that everything will work as you intended for all browsers.
I have never used VSD so I don't know how you actually would do this, but I assume there is an "HTML Tool", or something like that, available.
I am in the process of trying to wean myself from MS products and recently switched to Chrome as my default browser. It is not "simplistic" and certainly not "a load of crap" ;) Some browsers, apparently, are just more forgiving of questionable, or borderline, coding. Thus their different behavior in some situations.
Per
www.mingas.com
Dec 1st, 2009 at 09:00 AM
User 1948478 Photo

Per
Senior Advisor
1,850 posts

David Dupuy wrote:
</head>
<body >
<A NAME= "top"></a>

Do I enter this exactly as it looks into the HTML black box?
Sorry for these dopey questions but I don't understand HTML at all so I just want to make sure I'm doing it right?


Yes, now our posts really are crossing :)
I included the </head> and <body> tags above just to show where to put the anchor tag. The only "new" thing is the anchor tag: <a name="top"></a>
I also removed the CSS line which originally defined the anchor location, to avoid potentially confusing double definitions...
I am very hesitant about advising how you should go about even these very minor changes in VSD, since I have never used the program myself. I trust there will be VSD experts out there who reads this and can tell you what to do.
Per
www.mingas.com
Dec 1st, 2009 at 09:34 AM
User 1948478 Photo

Per
Senior Advisor
1,850 posts

Chad Spillars wrote:
Take out the slash before the anchor.
For example, instead of "http://www.irishvaluations.com/#top"
It would look like this
"http://www.irishvaluations.com#top"
Let me know if that fixes your problem.


Chad,
I don't understand this suggestion.
Where would the line: "http://www.irishvaluations.com/#top" appear anyway?
Per
www.mingas.com
Dec 1st, 2009 at 10:26 AM
User 1948478 Photo

Per
Senior Advisor
1,850 posts

David,
All the crossing posts may have caused confusion, so here are the only two small changes I made, in summary:

Added line, just after <body> tag: <a name="top"></a>
Removed line: <div class="Object198"><A NAME= "top"></div> (this was line number 279, but may have changed if you've made other changes)

With these small changes, it now works in all browsers I've tried it on (IE8, FF3.5, Chrome3.0, Safari, Opera10).
It seems to me that the original coding - although with the addition of the anchor closing tag - should have worked. If you were to just put the above changes into the VSD HTML Tool, I'm just afraid it may put it in the same way as it was originally, and nothing much would be gained. It would of course be easy to edit the HTML directly, as I did, but that would not be a good idea, since the changes would not be included in your .vnu file and you would lose the VSD continuity!
Per
www.mingas.com
Dec 1st, 2009 at 12:11 PM
User 510759 Photo

David Dupuy
Registered User
8 posts

Thanks Per. What I'll do is save the VSD website under a different name so if when I edit the HTML it stops working I still have a copy of the original (with its faults) to upload.
Dec 4th, 2009 at 12:15 AM
User 414501 Photo

Chad Spillars
Registered User
564 posts

Chad: to me this really is a VSD issue, since it is related to the 'black box-type' auto-generation of code. Just an opinion...


VSD did not generate the code that we are looking at here. The software has no built in option to create anchor text, so David would have to have added it himself using the HTML tool which just takes the HTML and incorporates it into the site verbatim.

David I assumed that you had used the HTML tool in VSD to create a box and then pasted the HTML code for your anchor script into that box, You would change it by clicking on the box and finding the code that you want to change.

I am in the process of trying to wean myself from MS products and recently switched to Chrome as my default browser. It is not "simplistic" and certainly not "a load of crap" ;) Some browsers, apparently, are just more forgiving of questionable, or borderline, coding. Thus their different behavior in some situations.


I have over a decade of web design experience and am also fluent in Adobe InDesign/Photoshop etc. When it comes to computers I am not and idiot, yet I have yet to even get Chrome to WORK on my computer. I have tried to install it twice and the software is so glitchy that I have yet to download a single website successfully using Chrome. I don't take it seriously and don't optimize my sites for it. I realize, however, that since it is Google there likely will be quite a few ppl using it, I'm just not sure how. Maybe Chrome just doesn't like 64 bit....
Chad Spillars
"Look I finally made myself a signature!"
Dec 4th, 2009 at 03:24 AM
User 1948478 Photo

Per
Senior Advisor
1,850 posts

Chad,
I, of course, take your word for most of that, since my experience with VSD (none) and with web design in general (very little) is no match for you or indeed for most people in these forums. I also very much appreciate your past posts on a variety of subjects, that I have learned much from.

As for the current matters, I suppose all I can say is that "it works for me", both with regard to Chrome and the fix for David's jumping problem... (Having said that, for a variety of reasons I'll probably end up going with Firefox instead of Chrome in the future anyway!) :)
Per
www.mingas.com
Dec 5th, 2009 at 05:45 PM
User 2733 Photo

David Sellers
Ambassador
426 posts

<a name="anchor" id="anchor"></a>


That code should work in all browsers. Please advise.
Let's not get all hurt.
Dec 5th, 2009 at 10:35 PM
User 1948478 Photo

Per
Senior Advisor
1,850 posts

David Sellers wrote:
<a name="anchor" id="anchor"></a>


That code should work in all browsers. Please advise.

I'm not sure quite where you're going with the "Please advise", but I'll give it a shot anyway:
Yes, for all I know that code should work (but there again, what do I know...?)
Since some of the problems in this case remained after adding the originally missing closing tag for the anchor definition, it seemed to me that the problem was some kind of ambiguity with regard to the positioning of the anchor, rather than the anchor definition itself.
This is from the original coding:

HTML anchor definition: <div class="Object198"><A NAME= "top"></a></div>

CSS positioning: div.Object198 { position:absolute; top:1px; left:3px; width: 153px; z-index:27; }
div.Object198 table { width: auto; }

This seemed to me a rather cumbersome way of defining and positioning an anchor, and that was why I opined that it was a 'VSD-issue' rather than an 'HTML-issue'. I was mildly rebuked for this opinion, possibly justifiably so...
Per
www.mingas.com

Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.