Topic: smash the mac (Page 1 of 1) Pages that link to <a href="https://ozoneasylum.com/backlink?for=9546" title="Pages that link to Topic: smash the mac (Page 1 of 1)" rel="nofollow" >Topic: smash the mac <span class="small">(Page 1 of 1)</span>\

 
mikey milker
Paranoid (IV) Mad Scientist

From:
Insane since: Apr 2000

posted posted 10-21-2002 19:58

okay so i thought i recoded my pages correctly enough that they would render fine in just about everything... on the pc things were good to go, but when i checked it on multiple macs running ie this morning the page would do nothing but freeze. oddly enough mozilla on the mac worked fine....

but yeah, so if you're good with coding for mac.ie check out http://three.zerominuszero.net and give me a heads up on what exactly is going on in my code that'd make the first page not render. whenever i'd try to access it things would be loading down in the status bar but it'd get hung up on loading the last image and just sit there... 15 minutes later still nothing so i gave up.

please help, i'd like to finish this project sooner than later.

<3 mm!!

mikey milker
Paranoid (IV) Mad Scientist

From:
Insane since: Apr 2000

posted posted 10-21-2002 20:05

i mean for the love of god... it even validates perfectly, argh.

HZR
Bipolar (III) Inmate

From: Cold Sweden
Insane since: Jul 2002

posted posted 10-21-2002 21:04

Hmm, weird, could it have something to do with the doctype maybe.

Slime
Lunatic (VI) Mad Scientist

From: Massachusetts, USA
Insane since: Mar 2000

posted posted 10-21-2002 21:33

Hmm, no scripts even? Weird. Not the first time I've seen IE 5/mac die on a standards compliant page, though.

BTW: do you *mean* for your design to look like a PDF?

mikey milker
Paranoid (IV) Mad Scientist

From:
Insane since: Apr 2000

posted posted 10-21-2002 21:38

OH MY GOD MY PAGE LOOKS LIKE PDF FILES?!?!

yeah... we'll save that for the site review section once the technical aspects somewhat work.

i never thought of the doctype causing the error... i'll try changing it before i go to the mac labs tomorrow so i can see whether or not that makes a difference. i seriously need to figure out how to get my ibook to connect to msn.dsl here at my place, argh.

has anyone with a mac tried the page yet? maybe it had something to do with the school's proprietary network security system...

Slime
Lunatic (VI) Mad Scientist

From: Massachusetts, USA
Insane since: Mar 2000

posted posted 10-21-2002 22:14

Haha, sorry. =)

I don't have a mac, but haven't you considered putting it on a CD so that you can test it and make changes on a mac itself?

mikey milker
Paranoid (IV) Mad Scientist

From:
Insane since: Apr 2000

posted posted 10-21-2002 22:34

yeah that's a good idea, i'll just use the cd burner in the ibook and.... shit.

i've got a zip drive i can move stuff back and forth with, but i quit doing that a while ago because i thought pages weren't rendering correctly because they couldn't download the referenced doctype.

Emperor
Maniac (V) Mad Scientist with Finglongers

From: Cell 53, East Wing
Insane since: Jul 2001

posted posted 10-22-2002 16:14

mm: Tell me about it - I have had all sorts of problems with IE/Mac and Jeni and Steve have been great help in getting to the bottom of things. I'm not sure about the freezing business - I knwo it can struggle to close complex nested DIVs and that adding this (before the final closing DIV) can kick things into gear:

<br clear="all" />

[edit: or better:

<br style="clear:both;" />

well its worth a try]

Just a couple of things to try (I basically can't see anything wrong so I'm just guessing):

1. Try the styles without the @import (worth a go).

2. As much fun as your metatags are try removing the space and hard returns:

quote:
<meta name="keywords" content="mikey,milker,zerominuszero,zero,minus,photography,pretentious,asshole,and,one,hell,of,a,guy,red,leaf,lettuce,supercalafragalisticsadomasochism

" />



3. Have a go at stripping out those metatags and see if that works.

Basically I can't see why those changes would make a difference but it would be what I'd try if it were me.

If all else fails we could smash up the Macs (or get MS to release a version of IE/Mac that wasn't so bad).

___________________
Emps

FAQs: Emperor

Slime
Lunatic (VI) Mad Scientist

From: Massachusetts, USA
Insane since: Mar 2000

posted posted 10-22-2002 20:05
quote:
...they couldn't download the referenced doctype.



Browsers don't actually download the DOCTYPE that you specify. They just compare it against an internal list of known doctypes.

Dracusis
Maniac (V) Inmate

From: Brisbane, Australia
Insane since: Apr 2001

posted posted 10-22-2002 21:19

You could also just keep a local copy of the DTD's and copy them onto the zipdisk/CD. Although you'd need to change the doctype's to reflect the new location of those DTD's. Just to be sure.

mobrul
Bipolar (III) Inmate

From:
Insane since: Aug 2000

posted posted 10-22-2002 21:20

Really?
Hmmm...
Not that I doubt you, but why, then, do DOCTYPES contain something like:

code:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"[b]"http://www.w3.org/TR/html4/strict.dtd"[/b]>


(Bolded for emphasis)
?
[edit]Damn it Drac! You got in my way!
Question for Slime.[/edit]

[This message has been edited by mobrul (edited 10-22-2002).]

Slime
Lunatic (VI) Mad Scientist

From: Massachusetts, USA
Insane since: Mar 2000

posted posted 10-22-2002 21:37

To tell the browser that that's where the DTD for your page is. That doesn't mean the browser has to download it. If it did mean that, then that particular URL would get millions of hits per day, putting the w3c site down entirely.

Browsers are made to recognize common DTDs at the time of their creation. If they see a URL for a DTD they understand, then they know what sort of document to expect.

The fact that the presence of a DOCTYPE definition makes a browser behave differently has less to do with what's behind the URL in the DOCTYPE, and more to do with the fact that the user specified it at all. The presence of a DOCTYPE switching the browser into "standards" mode doesn't rely on the contents of the URL. The URL simply has to be one that the browser understands, and then the browser assumes that the author knew what they were doing, so it renders the page correctly instead of following old, non-standard "quirks."

In any case, the point is, you don't need to be able to connect to the URL, or even to the internet at all, for a DOCTYPE to take effect.

[edit: by the way, this means that if you make a copy of the DTD at that URL, put it up on your own web site, and then use *that* URL for the DTD, the browser will *not* enter standards-compliant mode. It will assume it's either not a valid DTD, or not one that it knows about.]

[This message has been edited by Slime (edited 10-22-2002).]

mikey milker
Paranoid (IV) Mad Scientist

From:
Insane since: Apr 2000

posted posted 10-23-2002 06:25

thanks for the ideas emp... all good things i hadn't thought of tinkering with yet. didn't get any results yet, but i'm sure i'll get there... eventually.

why the fuck am i trying to make my code standard-compliant again? so it won't work in any of the browsers i used to code for just fine..... agh.

and now that i know i don't have to worry about the doctype needing web access to render correctly i've moved everything over to my laptop. so far no luck though. it's weird because while the first page won't render, the other three do just fine in mac.ie ... so i'm thinking the hangup might be related to the <span class> being nested in a <p class>.

got sketches and more enjoyable projects to work on right now though so i'll try the coding game some more tomorrow. thanks for all the input everyone.

mikey milker
Paranoid (IV) Mad Scientist

From:
Insane since: Apr 2000

posted posted 10-23-2002 07:40

okay i think i figured out and fixed the problem. it seems like ie.mac was having a bitch mother of a time trying to render a class within a class. i'm not sure if that's the proper terminology but whatever... anyway it seemed to throw it in some sort of infinite loop, ugly.

what i ended up doing was defining the width for the class located within the parent class. for some odd reason telling it what size it needed to render as fixed the hiccup and even helped me do some positional layout i was unable to figure out earlier.

of course once i got it back on the peecee i edited the css files to change some other stuff so for all i know i've completely rebroken it for macs... but i'll just wait until i'm on campus tomorrow morning so i'll have a good reason to scream in the middle of class.

and i still have to integrate movable type into this bad boy...

InI
Paranoid (IV) Mad Scientist

From: Somewhere over the rainbow
Insane since: Mar 2001

posted posted 10-23-2002 11:17

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

Dracusis
Maniac (V) Inmate

From: Brisbane, Australia
Insane since: Apr 2001

posted posted 10-23-2002 11:24

InI: I've seen that happening a lot on several CSS driven sites. Maybe it's a CSS2/IE thing.

InI
Paranoid (IV) Mad Scientist

From: Somewhere over the rainbow
Insane since: Mar 2001

posted posted 10-23-2002 11:30

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

mobrul
Bipolar (III) Inmate

From:
Insane since: Aug 2000

posted posted 10-23-2002 14:34

I've read about that effect too.
Zeldman, or, no...uno momento, porfavor (sp?)...
Not Zeldman but bluerobot.
Read that article. Is that what you're talking about?




Post Reply
 
Your User Name:
Your Password:
Login Options:
 
Your Text:
Loading...
Options:


« BackwardsOnwards »

Show Forum Drop Down Menu