When i implement an embedded style, it refuses to accept my style. I put it inline which worked (but cancels out the whole point of styles). I then found out after hours of mucking around that if I change the style to an id(#blah instead of .blah) and refer to it as an id="blah" it worked, I then then changed it back to a .blah then class="blah" and it accepted it!!!!??? Its almost like changing it to an id tripped the computers memory into realising what it is supposed to be doing?!?! Can anyone explain this cos its making my head hurt!!
thanks...
ps, using editplus and its signifying that the code is correctly laid out...Um. We need to see your code
Originally posted by stunews
Its almost like changing it to an id tripped the computers memory into realising what it is supposed to be doing?!?!
I've experienced this myself and the only thing I can think is that somwhere there is a cache expiration on the browser, and then something else that finally triggers the browser to send another GET to the server.
My experience is that I can make serious changes to the CSS - go to my browser and click refresh - and find that the CSS has not been implemented (like I'm using a cached version of the page or something). Best thing to do is get up and go for a 5min walk and come back and click refresh. I've not been able to understand it because its very sporatic when it happens.the code works now so i would just be showing you a peice of code that works which is purty pointless....
i'm using win98se, is there a OS that is most reliable for programming or is there no real difference??Originally posted by stunews
the code works now so i would just be showing you a peice of code that works which is purty pointless....
i'm using win98se, is there a OS that is most reliable for programming or is there no real difference??
If we can, we set all our testing browsers to never cache any info, never keep a history, etc, because even when you tell some browsers to ditch the cache, they do not. Also, AOL caches stuff on their own servers, and even if you're working with a browser that will refresh it's cache when you tell it to, if it comes through AOL it may not be refreshed.
If you're stuck using a PC to code I'd use Netscape but other folks here with more experience starting on PC may offer some other choices. If you START coding in IE it'll be off in everything else because IE gets some things wrong. Also... did you say Win98?!?! whew... get XP!
If you're on a Mac, like me, start with Safari or Firefox, then tweak for PCIE.yeah, its PC so, i need to upgrade windoze then..ok.
I'll get a copy of netscape on the go as well then...
thanks everyone for your helpyeah, its PC so, i need to upgrade windoze then..ok.
I'll get a copy of netscape on the go as well then...
thanks everyone for your helpFor what it's worth, if you decide to go to XP, format your drive, then start from scratch. Windows OS upgrades aren't recommended, particularly if you are trying to fix a problem. An upgrade might hide a problem, but rarely fixes much.
My 2cts.On the note of caching, some web servers cache static files anyhow. The web server that runs <!-- m --><a class="postlink" href="http://mjw.cmich.edu/">http://mjw.cmich.edu/</a><!-- m --> - a site I recently designed - caches virtually any kind of file, be it an image or text file. It was annoying as heck during development.
If you are developing and uploading to a server before previewing it, you might be running into a server caching problem.
And actually, Windows 98 isn't a big deal. Buy lots of RAM. As much as possible. And develop first in the latest stable build of Mozilla, Firefox, and Opera. If you develop for Netscape, do so only for versions 7.0 and newer. Those versions were based on the initial stable release of the Gecko Runtime Environment, which powers Mozilla, Camino, Firefox, and a few other browsers. Then, as mentioned above, hack the style sheets for IE. But this is a bit off topic.
If you are previewing your pages off of your computer, make sure you have the page loaded directly into the browser, not through web server software running locally on your computer.
If that still doesn't solve the problem, dump the cache in IE - cookies, history and all. I've seen strange caching behavior in IE if the cache hasn't been dumped in a while.Hey, stick with Win98SE unless you've got Gb of HDD and you don't mind being the target for viruses. Seriously in IE if you hold down the Ctrl key and press F5, that should force a refresh which F5 alone doesn't always produce.
Small is sweet - Win98 lover.
thanks...
ps, using editplus and its signifying that the code is correctly laid out...Um. We need to see your code
Originally posted by stunews Its almost like changing it to an id tripped the computers memory into realising what it is supposed to be doing?!?!
I've experienced this myself and the only thing I can think is that somwhere there is a cache expiration on the browser, and then something else that finally triggers the browser to send another GET to the server.
My experience is that I can make serious changes to the CSS - go to my browser and click refresh - and find that the CSS has not been implemented (like I'm using a cached version of the page or something). Best thing to do is get up and go for a 5min walk and come back and click refresh. I've not been able to understand it because its very sporatic when it happens.the code works now so i would just be showing you a peice of code that works which is purty pointless....
i'm using win98se, is there a OS that is most reliable for programming or is there no real difference??Originally posted by stunews
the code works now so i would just be showing you a peice of code that works which is purty pointless....
i'm using win98se, is there a OS that is most reliable for programming or is there no real difference??
If we can, we set all our testing browsers to never cache any info, never keep a history, etc, because even when you tell some browsers to ditch the cache, they do not. Also, AOL caches stuff on their own servers, and even if you're working with a browser that will refresh it's cache when you tell it to, if it comes through AOL it may not be refreshed.
If you're stuck using a PC to code I'd use Netscape but other folks here with more experience starting on PC may offer some other choices. If you START coding in IE it'll be off in everything else because IE gets some things wrong. Also... did you say Win98?!?! whew... get XP!
If you're on a Mac, like me, start with Safari or Firefox, then tweak for PCIE.yeah, its PC so, i need to upgrade windoze then..ok.
I'll get a copy of netscape on the go as well then...
thanks everyone for your helpyeah, its PC so, i need to upgrade windoze then..ok.
I'll get a copy of netscape on the go as well then...
thanks everyone for your helpFor what it's worth, if you decide to go to XP, format your drive, then start from scratch. Windows OS upgrades aren't recommended, particularly if you are trying to fix a problem. An upgrade might hide a problem, but rarely fixes much.
My 2cts.On the note of caching, some web servers cache static files anyhow. The web server that runs <!-- m --><a class="postlink" href="http://mjw.cmich.edu/">http://mjw.cmich.edu/</a><!-- m --> - a site I recently designed - caches virtually any kind of file, be it an image or text file. It was annoying as heck during development.
If you are developing and uploading to a server before previewing it, you might be running into a server caching problem.
And actually, Windows 98 isn't a big deal. Buy lots of RAM. As much as possible. And develop first in the latest stable build of Mozilla, Firefox, and Opera. If you develop for Netscape, do so only for versions 7.0 and newer. Those versions were based on the initial stable release of the Gecko Runtime Environment, which powers Mozilla, Camino, Firefox, and a few other browsers. Then, as mentioned above, hack the style sheets for IE. But this is a bit off topic.
If you are previewing your pages off of your computer, make sure you have the page loaded directly into the browser, not through web server software running locally on your computer.
If that still doesn't solve the problem, dump the cache in IE - cookies, history and all. I've seen strange caching behavior in IE if the cache hasn't been dumped in a while.Hey, stick with Win98SE unless you've got Gb of HDD and you don't mind being the target for viruses. Seriously in IE if you hold down the Ctrl key and press F5, that should force a refresh which F5 alone doesn't always produce.
Small is sweet - Win98 lover.