I'm building a website with an alphabetical list of items, with a HTML bookmark positioned just above the beginning of each letter; A, B, C, etc.

This works just the way I want it to in Firefox, but when I display the page in Google Chrome, clicking on a bookmark's corresponding href link in the selection menu positions the page view well below the placement of the bookmark.

This is a work in progress... the page in question is http://www.earljones.com/eetest/NOTE1.html and I have placed bookmarks (so far) for A, B and C.

Any thoughts? Thanks!

- Earl

Chrome is just focusing the anchor in the center of it's display instead of at the top of the page. You could perform a browser check and make special anchors for chrome users, but I'd personally just get over it and use Firefox.

Thanks for the suggestion, Zac, but really, what browser I choose to use is irrelevant, since I am designing for others, millions of whom (I don't think that is an exaggeration) use Google Chrome.

Is it difficult do do the browser check as you suggest? Does anyone else have a suggestion?

Thanks.

- Earl

Here's browser detection: http://www.w3schools.com/js/js_browser.asp

After checking for chrome, just rewrite the links in that scroll table to the ones you place for chrome. If you're not familiar with javascript, w3schools.com is great for learning, but many here (including me) would be willing to help out.

Instead of using anchors, however, would it not be simpler to send users to a page containing 'A' when they click the A link? Super-long pages are generally reserved for legalese such as http://www.coffeecup.com/legal/website/

Wouldn't it be simpler to just use regular anchor tags instead of scripts for this? Anchor Tags are a whole lot easier and less work to do than this is from what I can see. Looks like what you are doing is partially anchor tags already, but there aren't any anchor tag setups for the actual content, only the alphabetical menu. I think you're making this much more difficult than it really needs to be. Just my opinion of course, but they do work nice and easy in most all the browsers, including google chrome.

Here's a page from a site I did for my brother's band, you can see the links on the left side which are tags to take you to the sections for each person. Work nicely and very easy to setup.
http://rockinwithmainstreet.com/band_bios.html

Anchor tags = KISS.

Exactly!

Chrome has always handled anchor tags just fine when I have used them in the HTML Editor. But I have seen this problem mentioned in the forums a few times in connection with VSD. The landing point is erratic and is not always with the anchor centered on the screen, as Zac suggested. There seems to be something about VSD's absolute positioning of anchors in divs that Chrome doesn't like...(?) And I would agree with you that you can't just ignore Chrome either.

I would seriously consider Zac's suggestion, though, about using a separate page for each letter, rather than anchors on a super-long page, which is likely to become unmanageable in other ways as well. You already have a problem with the floating menu around the letter 'C'. The menu kind of disappears there for a while. I think the concept of KISS would lead you to using separate pages...

I have news for you. The floating menu has issues in the latest IE, FF, Chrome, and Opera. The menu disappears at times and fails to do anything at times. Plenty of sites use a long page for this sort of thing. It is certainly easier to maintain one page then 26 pages. Especially when something changes in the design of the site.

I would have to agree with Tom on this too, is definitely easier to do 1 long page with constant changes than a whole alphabet worth of constant changes. And theme design, well that would be a nightmare at best lol.

Chrome works just fine for anchor tags, it's just that you gotta work on how to get them setup correctly in VSD, which unfortunately I don't use. The tags are not the issue I'm sure, it's just how to get them in VSD to make them work right. Definitely not working the way it is right now at all in Chrome, regardless of what the menu itself does.

Does this code go into an HTML Tool entry? Or does VSD have a built in setup for handling anchor tags? If it's built in, then maybe try the HTML Tool for it instead. IF it's not built in and you're doing the tags using HTML Tool, check to be sure you're using the right code. The code being used on that site is definitely not right for basic anchor tags.