MyStore3 software is compliant with JavaScript 1.1 code and the HTML 3.2 standard.
This means that there should be no problems encountered when using
Netscape Navigator 3.x+, Microsoft Internet Explorer 4.x+, or the
Opera 3.5+ browser versions.....right!
So here goes:
Netscape 3.x does not support background images in tables. This is
expected. Just remember that the header row and left column gifs that
you worked so hard on will not show up in N3.x.
Netscape 3.x does not do a good job of cleaning up the stack....or for
all we know any job at all. Because of this, if you are repeatedly
calling pages during setup, you may start to encounter strange behavior.
Also the browser may act funny! Close the browser and start again.
There is a problem with double imaging of the header image in at least
some of the Netscape 4.x versions. We are trying to come up with a work
around. It has to do with nested tables. As of 01-07-99 we think a work
around has solved this problem. Please let us know if you encounter it.
Some early versions of IE4.x were broken. They, among other things,
would not open a pop up window. Get a newer version.
Changing an image in setup and then reloading (or in IE, refreshing)
to view the new look can often result in getting the old image back.
The general rule during a setup is to set the browser to reload a page
each time it is viewed. Don't count on this working to reload your
new image though. You may have to empty the cache. In IE, don't count
on this working either. We've tried everything short of deleting the
computer and still gotten the old image back. It wobbles the mind! No
the image is not in the windows temporary internet files. Sometimes
reloading by using Ctrl-R will work.
Do not expect MyStore to work with AOL 3.x users. AOL uses
their own model of IE3.x for this version which does not run JS1.1. AOL
4.x should work OK.
We can't get OPERA 3.6 to work properly with MyStore3.x. They claim JS1.1
compliance, but to date they do not fully support certain methods.
Large database files (50 items or more) in one category may experience
delays of several seconds in loading. This is highly dependent on
your computer clock speed. It is a result of using nested loops to
read the db and give an ordered presentation; and, it is a result of the
way the latest browsers read JavaScript. If you want fast, use
Netscape3.x.
Large database files may render with missing quantity form fields.
This is a computer/browser memory problem resulting from having
several hungry applications open at the same time. We do not think
this will be a problem for store customers. If you have concerns,
try breaking your category up into more than one table.
The netscape browser does not automatically "escape"
spaces in a URL. This means that if the path to your image
is a category that has spaces such as:
<img src="Specials This Week/Images/thegif.gif">
Netscape will not
find the image. There are two ways to work around this:
1) Try to avoid using spaces where possible in your category
names by using the underscore character (_). (We don't like this.)
2) Use the hex value for a space in the src, "%20" so that your
URL looks like this:
<img src="Specials%20This%20Week/Images/thegif.gif">
Note that this is only for images in the description field of a
table. We can and have used JavaScript everywhere else to
automatically escape spaces.