Forum Moderators: travelin cat
<div id="Layer1" style="position:absolute; width:208px; height:254px; z-index:1; left: 263px; top: 142px;" class="list">
<p><br>
<span class="mediumheader">Take a <font color="#3366cc">Workshop</font></span><br>
» <a href="art_center_classes_painting.htm">Drawing</a> » <a href="art_center_classes_jewelry.htm">Jewelry</a> <br>
» <a href="art_center_classes_painting.htm">Painting</a> » <a href="art_center_classes_photo.htm">Photography</a> <br>
» <a href="art_center_classes_pottery.htm">Pottery</a><br>
<br>
<span class="mediumheader"> Meet the <font color="#3366CC">Artists</font> </span><br>
» <a href="art_center_artists.htm">Resident Artists</a><br>
» <a href="art_center_glass.htm">Guest Artists</a></p>
<p><span class="mediumheader"> View the <font color="#3366cc">Work</font></span><br>
» <a href="art_center_glass.htm">Glass Blowers</a><br>
» <a href="art_center_glass.htm">Guest Artists</a><br>
» <a href="exhibits_chapungu.htm">Visiting Exhibits</a> </p>
</div> url <snipped> I works fine in all IE NN and Opera for PC but IE & Safari on the mac cause trouble. I would appreciate any help mac experts could give me.
thanks
[edited by: Macguru at 9:43 pm (utc) on June 2, 2003]
[edit reason] URL snipped no site reviews and no specifics please [/edit]
I dont know if it will welp with your layer position but a lot of closing tags need some attention. The extra space in it are breaking those tags, making them impossible to render.
Do you have a doctype declaration on top of your page?
Such as
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
If so please, give it a try here :
[validator.w3.org...]
Then you can check it on other browsers.
By the way, do you really check your pages on IE 2, IE 3, IE 4 for Mac? It has been a long time since I saw those dinosaurs in my logs... ;)
I am not sure if layer is rendered in earlier versions of some browsers. This appears to be conditional on the exact content of the layer. If you get a problem, check the CSS declarations relating to the content elements (for example <p> - not < p> - )
Hope this helps
I have tried the validator but it doesn't recognize my pages. I am not sure if it has to do with the fact that the back end is written in perl. I seriously doubt it since it didn't recognize my straight html version either. I am checking with my perl guy. I added the doc type but it didn't help. My mac traffic is less than 5% but it is a very vocal group. They send me hate mail daily. Unfortunately I am in a completely PC environment with no access to a mac to see why they are having troubles with the site.
I don't usually check my sites in ancient browsers some one from another board sent me screen captures from a mac in 12 different flavors of IE NN and apples new browser.
Thanks for the help but I am still trying to narrow down the problem. The two I am aware of is the layer is lower and the dhtml navigation moves in some of the browsers. (Meaning that it is positioned differently)
I was not able to extract a character encoding labeling from any of the valid sources for such information. Without encoding information it is impossible to validate the document. The sources I tried are:
The HTTP Content-Type field.
The XML Declaration.
The HTML "META" element.
And I even tried to autodetect it using the algorithm defined in Appendix F of the XML 1.0 Recommendation.
Since none of these sources yielded any usable information, I will not be able to validate this document. Sorry. Please make sure you specify the character encoding in use.
IANA maintains the list of official names for character sets.
I have this in the doc. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> I have even tried different versions of it.
If that is what you did and it is complaining of html code you don't have, it might be code that the perl script generated. To see what the browser sees, you could use 'show source' in your browser.
Does that make sense?
Shawn
Of course; this is just to get it through the validator, so you can see if that gives you any clues as to the 'real' problem. But since your msg # 1 didn't have any references to tpl, I assume the 'real' problem is somewhere else? Yes?
Essentially each page use the same code for top and bottom. So in perl a page is created that uses the same code. In the middle where content is different it pulls in a tpl file which contains the middle portion of the page.
Here is a link to the w3.org output. I hope this is legal on this board. If not I am sorry. <snip again, no. >
Error #1
Line 12, column 6: end tag for element "HEAD" which is not open (explain...).
</head>
^
Here is my head code
<head>
<title>Sundance Resort Utah Skiing Mountain Biking Theater Fine Dining Film Festival</title>
<LINK REL=stylesheet HREF="css/spring1.css" TYPE="text/css">
<META name="description" content="Robert Redfords Sundance Utah is a four season community in the mountains of Utah that offers everything from skiing, mountain biking and theater to fine dining and the Sundance Film Festival.">
<META name="keywords" content="sundance Sundance sundanceresort sundance resort Sundance Resort sundance ski resort sundance utah ski skiing robert redford redford utah resort lodging hotel wasatch mountain biking sundance channel sundance catalog sundance film festival snowboarding hiking vacation summer theater sundance institute horseback riding fly fishing park city recreation powder snow winter olympics salt lake city alpine nordic cross country 2002 Olympics 2002 park city mountain resort ark city ski resort park city resort ">
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" />
<SCRIPT language=JavaScript src="/js/forms.js" type=text/javascript></SCRIPT>
</head> [edited by: Macguru at 3:51 pm (utc) on June 14, 2003]
[edit reason] URL snipped no site reviews and no specifics please [/edit]
I know the validator is the most authoratitive, but gee wiz it is an awful piece of software. Its 'explain' button gives new meaning to 'oxymoron'. The authors should be ashamed of themselves. And they are the callibre of software developers who should know better. ;)
Shawn
The only real workaround to using layers is in my opinion is to redirect the visitor to different versions of the same page corrected for the respective browser. I realize that you may not want to do it, but over the past 6 years that I've been building sites I really haven't seen a good solution.
Even though many people would disagree with me, I believe the best way to make sure your pages and site work on all browsers (at least when it comes to positioning) is to use tables.
One other thing, you mentioned that even if a link isn't covered up you can't click on it, IE doesn't do some margins, so if you've assigned a certain margin it might not be working. In other words your link may not be where you think it should be.
HTH
My stats show that less than 7% of my visitors are using macs. The mac users seem to be very vocal about the problems. The ones who complain the most are mac users using os 8. I would like to fix it if possible with out huge headaches.
I think that most Mac users have gotten used to visiting sites that won't work right or crash their browser, especially those who are running 8.1. But to be honest, I didn't think any of them were left. :)