Forum Moderators: travelin cat

Message Too Old, No Replies

Having trouble with a Website on a pc vs mac

questions about a Website on a pc vs mac

         

colorspots

6:37 pm on Jun 2, 2003 (gmt 0)

10+ Year Member



I am a webmaster who created a new site for a resort. For some reason when I use div tags it doesn't position it correctly on some of the mac browsers. Specifically IE 2, IE3, IE 4. It places the layer 250 px below the intended position and makes links on the first layer not clickable even if they aren't covered by the layer. I use this code

<div id="Layer1" style="position:absolute; width:208px; height:254px; z-index:1; left: 263px; top: 142px;" class="list">
<p><br>
&nbsp;&nbsp;&nbsp;<span class="mediumheader">Take a <font color="#3366cc">Workshop</font></span><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&raquo; <a href="art_center_classes_painting.htm">Drawing</a>&nbsp; &raquo; <a href="art_center_classes_jewelry.htm">Jewelry</a>&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&raquo; <a href="art_center_classes_painting.htm">Painting</a>&nbsp; &raquo; <a href="art_center_classes_photo.htm">Photography</a>&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&raquo; <a href="art_center_classes_pottery.htm">Pottery</a><br>
<br>
<span class="mediumheader">&nbsp;&nbsp;Meet the <font color="#3366CC">Artists</font> </span><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &raquo; <a href="art_center_artists.htm">Resident Artists</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &raquo; <a href="art_center_glass.htm">Guest Artists</a></p>
<p><span class="mediumheader">&nbsp;&nbsp;View the <font color="#3366cc">Work</font></span><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &raquo; <a href="art_center_glass.htm">Glass Blowers</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &raquo; <a href="art_center_glass.htm">Guest Artists</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &raquo; <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]

Macguru

11:33 am on Jun 3, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hi colorspots,

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

colorspots

3:31 pm on Jun 3, 2003 (gmt 0)

10+ Year Member



Sorry for posting my url. I forgot that examples of problems are strictly forbidden. The URL is now in my profile.

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)

colorspots

10:29 pm on Jun 11, 2003 (gmt 0)

10+ Year Member



Any one?

ShawnR

11:31 pm on Jun 11, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



"...tried the validator but it doesn't recognize my pages..."

What do you mean by that?

colorspots

2:35 pm on Jun 12, 2003 (gmt 0)

10+ Year Member



i receive this message.

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.

ShawnR

3:49 pm on Jun 12, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Add the following line somewhere in the <head> section (i.e somewhere between <head> and </head> ), and try validate again:
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" />

Shawn

colorspots

5:14 pm on Jun 12, 2003 (gmt 0)

10+ Year Member



shawn that worked great.

new problem with the validator. it doesn't portions of the perl code and attributes that flash creates. Another issue is it shows tags i supposedly didn't close but i can't find a single one. Any suggustions?

ShawnR

10:37 pm on Jun 12, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



The way CGI (in this case perl) works is that it is run on the server and generates code the bowser can understand (e.g. HTML). So the browser never sees any perl code; it sees what the perl produces. You want to validate what the browser sees. i.e. Give the validator the the url of the live website.

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

colorspots

12:06 am on Jun 13, 2003 (gmt 0)

10+ Year Member



It makes total sense. I just can't figure out why it says there are problems with the code when there isn't. It tells me the head tag isn't closed and it is. It tells me that there are several <strong> tags not closed but they are. The really funny thing is the perl code creates the top and bottom navigation and the center section is a tpl file. So head code is identical to for all the pages but if I check other pages in the site the same errors don't appear. Its really wierd. I have been coding html professionally since 97. I know my code isn't always perfect but the simple errors it is reporting just aren't there.

Macguru

1:01 am on Jun 13, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Do go by URI?

Did you try to save your page from your browser and use the upload option when you validate the code?

ShawnR

7:31 am on Jun 13, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Excuse my ignorance; what is a tpl file? If that is the difference between the files that validate and those taht don't, then that narrows down the problem a bit, and you can assume the perl code is not causing the problem.

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?

colorspots

5:00 pm on Jun 13, 2003 (gmt 0)

10+ Year Member



Shawn I believe you are correct and that the problem isn't related to the perl. I am not a perl programmer. It was built by a friend of mine.

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]

colorspots

5:02 pm on Jun 13, 2003 (gmt 0)

10+ Year Member



Mac guru I have tried that also. It gives the same errors. I have the page in perl and in static html.

Thanks for all the help. I really do appreciate it.

ShawnR

11:24 pm on Jun 13, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



The problem is not the </head>, it is because some of your html above line 12 is confusing the validator. My guess is it is things like: type=text/javascript in line 11. Change it to type="text/javascript". Also, make lines 7, 8, 9 one line with no carriage returns.

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

KA_Curtis

5:54 pm on Jun 20, 2003 (gmt 0)

10+ Year Member



Hi, I just thought I throw in a comment since I'm a Mac person. Using layers has always given strange results on the Mac, especially NS 4.7.

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

stace

6:03 pm on Jun 20, 2003 (gmt 0)

10+ Year Member



One thing to keep in mind is that less than 10% of surfers are using a Mac (my stats have Mac users at only 3%, and my sites are educational). Not that it isn't good to have a site optimized for both Mac and PC but it's a lot more important that the site look perfect for PC if you have to choose between the two.

colorspots

6:11 pm on Jun 20, 2003 (gmt 0)

10+ Year Member



well that gives me some ideas because I am using layers only 1 and I am using borders in css.

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.

KA_Curtis

7:41 pm on Jun 20, 2003 (gmt 0)

10+ Year Member



I have to agree, the PC visitors are much more important. Having said that though I really don't run into any problems between the two platforms that isn't easily fixed, but I don't use layers at all.

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. :)

colorspots

7:49 pm on Jun 20, 2003 (gmt 0)

10+ Year Member



I wish there were no os 8 users. I get the most hate mail from them. I will spend some time checking out the fesability of removing the layer. I created the layer as a extra unique in page navigation system that could be moved around based on how much text I had. It seemed like a good idea at the time. Ooops. Not having a mac to test on really is difficult. I have to decrypt messages of Dear webmaster your site sucks! Mac users are people too! signed mac os 8 user. A few times i have actually spoken with mac users to try and find the problem. I even got screen shots from a board poster. It didn't help with the not being able to click issue.