MidiMagic

It's part of the Cisco router firmware.

Absolute positioning is a great way to cause browser incompatibilities, because they don't agree on where the absolute positioning starts. Don't use either pixels or absolute positioning if you want browser compatibility.

Why not just open a new page? The BACK button returns you to the menu page.

This is the thing I hate most about websites! Those things are extremely annoying. I want a way to make the browser ignore them. They drive dyslexic people crazy. That is a good way to make a lot of people click their back buttons.

Negative margin values are nonstandard, and can fail. The capital letters in the color definition may be causing Firefox to throw out the style.

This is the IE browser incompatibility bug. It happens even with the correct doctype. Firefox and other browsers render the surrounding and size elements nested as follows (outside to inside), following the W3C box definition: margin, border, padding, width/height IE wrongly renders them in this order (outside to inside): width/height, …

[QUOTE=kanaku;810719]You're most welcome. =) (I'm still hoping someone will clear up the issue with [icode]clear: right[/icode] though)[/QUOTE] Doesn't this allow other items (such as text) to flow on the left side?

First, NEVER use absolute positioning. It guarantees that your site will mess up in different browsers. Remember that the browser screen is not a fixed size. You must design flexibly, to work on different browsers, screen resolutions, and window sizes.

If you are trying to exactly fill a browser window, note that it can't be done in a way that works in all browsers, screen resolutions, and window sizes.

The [icode]<!-- -->[/icode] tags should be removed. They cause troubles with new browsers.

0px is an invalid style. It causes Firefox to throw away the entire style. When a value is 0, do not attach a unit of measurement. Just put 0.

Please do NOT do this. Many of us have trouble reading text when it is on top of an image. It is an accessibility problem.

The height attribute, applied to html and body, is rendered in different ways on different browsers, if it is rendered at all. It is usually NOT the size of the window, but the height of the entire document after rendering. There is no reliable way to make the document render …

This is one of the things that really bugs me about most commercial software. When I try to do a simple task, the software does other things "for me" that I didn't want. Examples: - Office changing the color scheme of all of the products, not just one. - A …

Is there a way to do it which is browser independent and does not open another window? I just want a momentary sound like the windows navigation sounds.

0px is an invalid style. Place units of measure on nonzero values that need them. Do not place units of measure on zero values. It causes some browsers to throw the entire style away.

My area is so oversaturated that nobody is hiring them.

I thought it was "ipsum before doler, except after lorem." The real problem is nesting of features. The standard calls for the following nesting order, outside to inside: - margin - border - padding - width IE orders them in the wrong order: - width - margin - border - …

This is a setting in the browser, not your code. Each user has to turn off the caching of pages and/or enable checking for changed files.

I'm sick of these rules that dictate when you can post on what thread. WHO originally decided that this should be a rule - some government bureaucrat? Or was it a webmaster trying to conserve disk space? The usual case of a post to an old thread occurs in this …

Height and width parameters are deprecated. When you don't yet have the image, use a blank image the same size. Put some text on it, like "Bob lost the picture." Many browsers refuse to render space for objects they can't find.

First of all, stop using pixels. Pixels freeze your page to work for only one screen resolution. Use percent, and use points for font sizes. Put 0 margins, borders, and padding on the divs that are using percents. Text can not be placed directly inside a div. It must be …

Why does it matter?

The problem is that a new install of IE has to be taught what to do with a .gif file.

It is impossible to do some of these. i want a loading screen before my site fully loaded. it can be 1. loading screen before the home page fully loaded. - In order for the page to load, the browser must be displaying it, so the browser can render things. …

First of all, hiding scripts and styles in comment tags is deprecated. It doesn't work anymore. Remove the [icode]<!--[/icode] and [icode]-->[/icode]. They now keep your browser from using the scripts and styles. Scripts should be in external files, not inline in the code.

I see several errors. 1. Stop using pixels for measurement. This locks the design to one screen resolution. It fails on other screen sizes. 2. Don't put dimensions on 0 values (e.g. 0px). If Firefox finds one of these, it throws away the entire style. 3. Don't put nonzero surrounding …

I use notepad and write my own code. The problems between the nonstandard IE and the standards-obeying browsers like Firefox are not easily fixed by using conditional styles. They are easily fixed by not using size styles (width, height) in the same tags or styles with nonzero surrounding styles (margin, …

Just design it to be browser-independent. Never use anything that is browser-dependent. This is basically not putting size styles (width, height) on the same tags that contain nonzero surrounding styles (margin, border, padding). If you need both, nest two sets of tags.

Div is a block tag. A is an inline tag. You can't put block tags inside inline tags.

Several points: Height can't see the browser window size in most browsers. Most browsers correctly put the surrounding styles (margin, border, padding) OUTSIDE the size styles (width, height). Internet Explorer crams them INSIDE instead. The cure for this is to not use nonzero surrounding styles with size styles in the …

Using px replaces one trouble with another. The page now becomes monitor-resolution-sensitive. Use pt instead.

Create your own.

If the boundary is NOT a border or the edge of a content box, but is just a visible edge of the top layer, it is generated in the human eye. To make that go away, the pixel colors at the edges of the top layer must match the pixel …

Now we just have to teach the beginners the meaning of that lorem ipsum stuff. :icon_cheesygrin:

The main thing to remember is that it looks at TEXT content in the html in your web page file. It can't see stuff in css files, scripts, dynamic content, image files, database files or auxillary files. And it ignores meta tags. The order the websites are listed is determined …

Embed is a nonstandard IE extension. It is deprecated.

What the bots look for: Plain text in the HTML file. It's not going to look for the following: - Stuff in scripts - Dynamic content - Images - Other objects - Auxiliary files - Any html created during rendering

Don't put stuff on top of other stuff. It causes all kinds of trouble.

This is what happens when you design for a specific screen resolution. There is more room on the screen when the scrollbar isn't there.

target= is deprecated.

This is one place where absolute positioning and pixel sizing fail miserably. If you use size styles (width, height) in the same tag or style that contains nonzero surrounding styles (margin, border, padding), it causes Internet Explorer to do this kind of thing, with a different result in Firefox.

The li tag is not allowed to be alone. It must be directly inside a ul or ol pair.

I need to see more than a photo and one style. I need to see the other styles and html surrounding it. The trouble might be in a different element. Note that the Firefox error console might be useful here. It tells you if an error occurs, and the line …

[code] div#trans7 { background: #400000; width: 10px; height: 842px; position: absolute; top: 0px; left: 51px; } .... div#trans7 { background: #400000; width: 10px; height: 842px; position: absolute; top: 0px; left: 51px; } .... div#hder { background: white; width: 660px; height: 98px; position: absolute; top: 0px; left: 202px; font-family: Comic Sans …

Use relative measures, not absolute ones. - Use percent to arrange objects across the width of the page, and to set the sizes of box objects. - Use points for items related to text size.

But there is nothing wrong with using tables for actual table content (anything that looks like a spreadsheet). It is not deprecated.

Add what? I'm not sure what you wnat.

You have to write your web page code to use the styles that are there.

0px is not a valid style. You must not put units of measures on zero values. Just put 0 for a zero value. Some browsers throw the entire style away if it contains a 0 with a unit of measure. Note that the ad code may be using nonstandard IE …