Posts by MidiMagic

Firefox 2 issue when posting and reading threads.

Whenever I post today, I get a perpetual "loading" animation. I have to refresh the screen to see the post.

I cannot edit a post, I get the perpetual "loading" animation. Using refresh brings back the original page, not the edit screen.

When I looked at the image in the post "Internet Explorer issue when reading posts" (maybe not exact title, because I can't navigate away without losing the text), I could not click on it to return to the post.

It can't be done.

The web is NOT designed to fill a screen. You provide content, and it expands downward to fill whatever area is needed, running off the screen downward if necessary.

Remember that different computers have different resolutions. Combine that with different browsers, and it is quite impossible to make a web page that fits into a screen.

IE has nonstandard extensions to do this, but nobody else implements them.

In order to make IE behave the same as other browsers, you can NOT have nonzero surrounding styles (margin, border, padding) and size styles (width, height) applied to the same tag.

You need to nest two divs, one with the surrounding styles, and the other with the size styles. Nest them in the order you want the styles to appear in. Then both browsers will behave the same way.

The previous solution does not work, because the styles have both size and surrounding styles.

Do this:

Styles:

.boxfix {margin: 0; border: none; padding: 0;}
.boxsiz {width: 300px;}
.boxbor {margin: 10px; border: none; padding: 0;}

HTML:

<div>
  <div class="boxbor">
    <div class="boxsiz, boxfix" id="img1">
      <img src="myimage1.gf" alt="my first image" />
    </div>
  </div>
  <div class="boxbor">
    <div class="boxsiz, boxfix" id="img2">
      <img src="myimage2.gf" alt="my second image" />
    </div>
  </div>
</div>

Use the ids to do the javascript settings.

I found two the validation service won't find:

1. You have an 0px style value in your p tag style. This is invalid in Firefox, and causes the entire p tag style to be thrown away. There may be more of these.

2. You have size styles (width, height), and nonzero surrounding styles (margin, border, padding) in the same style or on the same tag. This causes size and placement errors, because IE wrongly nests them in the wrong order. FF and other browsers place the surrounding styles outside the defined size styles, as the W3C specifies. IE crams them inside the size styles.

The trick is to not use nonzero surrounding styles and size styles in the same tag. Nest two tags, with one style in each.

I am using Windows XP and Firefox 2.

I'm getting stuff not only from websites, but also from files on my hard drive. I AM using tabs, and also Windows Explorer. But when I return to the window with the post, the ad plays again. The ad often takes me to the top of the page, and when I scroll down again, the text is gone.

Could this be a cache problem?

This is a common problem with web pages. Different computer screens have different resolutions.

One trick is to place things in such a way that the space between them expands with a larger screen.

You can place the files in a folder on your hard disk, and play with it offline. That's how I develop. Point the browser at the file to be tested.

You have improperly nested tags.

The form tag can't be nested inside the table tag, but with the tr tag inside it. The tr tag must be the immediate child of the table tag.

Put the form tag outside the table tag. Input tags can then be put inside the td tags. border width: 2; 2 what?

Check for an anomaly in an image. It might have one extra vertical pixel.

I went bonkers trying to eliminate such a space, and found that one of the images had an extra row of pixels, all white, at the bottom. This made the browser make that row one pixel higher, displaying a white background below the other images in the row.

The problem is that the nesting order of size styles (width, height), and surrounding styles (margin, border, padding) is different with different browsers.

FF puts the surrounding styles OUTSIDE the size styles, where the W3C says they belong.

IE crams the surrounding styles INSIDE the size styles.

The problem you are having is that your code is making the styles add up to more than the width of the available space, once you add in the surrounding styles. When this happens, the div drops down under the others.

Input is a self-closing empty tag, not a tag pair. It has no closing tag.

<form>
    <input type="text" />
</form>

Who does What?

"Why! I Don't Know! He's on third, and I don't give a darn!" (from the Abbot & Costello radio short "Who's on First")

I use XHTML 1.0 Strict with CSS1. Almost all browsers in use today can handle it.

I do use tables a bit more liberally than some people want me to. There are some structures that can't be easily converted to a div structure without falling apart.

I have learned to write browser-independent code.

I would suggest that you just display the image. That's what most advertising banners are.

Some of them are motion picture images (which I don't like, because they steal control, preventing me from navigating quickly until they stop moving). The motion is contained inside the .gif or .flv file itself. If the file contains motion, it will move when displayed without further coding from you.

I still hate how I can't navigate the site while the ads are moving.

How do I compose the post before I post it? If I leave the page to go get something to insert in the post, when I get back, the posting window is empty. Everything I had already put in the window is GONE!

So I can't include more than one link or object in the post, because the clipboard can hold only one thing at a time.

This is a setting on the browser.

When you first download a file on most browsers after installing the browser, a dialog box opens to ask what you want to do with the file. There is a checkbox saying "open all files of this type in this way" in the dialog box. If you check the checkbox, you will never see that dialog box again for that kind of file.

Hiding urls is usually a sign of criminal activity or malware threats.

The web is supposed to be public, not private.

You have them in different divs. In order for text to wrap around an image, both have to be in the same container.

Yes. Then apply a style to the td tag that aligns the text to the right.

<style type="text/css">
.rt {text-align: right;}
</style>
.....
<table>
  <tr>
    <td>Protein</td>
    <td class="rt">8g</td>
    <td class="rt">25%</td>
  </tr>
  <tr>
    <td>Fiber</td>
    <td class="rt">1g</td>
    <td class="rt">3%</td>
  </tr>
</table>

Checkboxes have the values of true or false in the attribute "checked".

The what?????

I would suggest reinstalling your browser. It works fine for me.

He's thinking of tunneling his way into the principal's office, or jail.

I am a teacher. I have software that lets me look at the screen of any student's computer in my classroom. I can even put that screen up on the projector, so the whole class can see it.

The school's computers are there for education, not for the internet timewasters and nasties most students want to see.

These computers are paid for with tax money (in public schools). Internet access is NOT free. So when you are using the computers for non-school purposes, you are stealing money from the taxpayers.

Your approach is wrong. You don't put stuff on top of other stuff if you want them to stay together. You put stuff INSIDE other stuff.

You need to think of web objects as containers. They contain other objects.

Use a div as a container, and then put your stuff between the div tags.

This looks like a copyright infringement issue. I see logos and other things that are obviously faked versions of real copyrighted material.

Someone probably reported the copyright infringement, and asked that your site be blocked, or reported your site to one of the copyright enforcement organizations.

Note that ISPs can be held liable for "aiding and abetting" copyright infringement if they display infringing materials.

Obama scares me, not because of what he promises, but that he believes that he can use Keynesian Economics to achieve it. It hasn't worked right even once.

There is also a problem using width or height in the same style as nonzero margin, border, and/or padding. IE nests them in a different order, putting the surrounding styles inside the width, instead of outside as the standard requires.

The trick is to nest containers, separating the following into different containers:

1. width and height, or images of defined size.

2. margins, borders, and padding.

3. floats and clears.

Be more specific. I can think of 5 different things that could be.

WRONG!

Table is not blasphemous, except with some idiots who don't understand what the W3C really wants people to avoid.

The things the W3C wants to remove are:

1. The use of tables to create margins, borders, and padding effects. Before CSS, table was the only way to make them.

2. The use of tables where the row and column announcements made by accessibility page readers for the blind do not make any sense in the page context.

There is a real problem: Div can't do what table can do in respect to keeping a structure together. Div is fluid in nature, and falls apart when things don't fit.

My rule on this is:

- Use table to create structures where it is important that the parts stay together in a gridlike pattern.

- Use div in other cases.

You have invalid code that causes FF to throw out the style it is in.

Zero values in styles must NOT have units of measures. Your 0px entries cause the style it is in to be thrown away by the browser:

Yes: 0
No: 0px, 0pt, 0in, 0%, 0em, etc

Do they teach spelling?

Two possibilities:

- You didn't use the proper procedure to eject the flash drive when you put the images on it.

- The flash drive is designed for a Vista computer, and the other computer is XP or earlier.

Wouldn't that be a violation of copyright?

Use the style text-align: right; .

This is a good place to put in a table with no borders.

W3C and Firefox don't accept styles with units of measure attached to 0 values. So instead of 0px, just put 0. This causes some of your styles to be thrown away.

There is no way to center content vertically on the screen that works on all browsers and screen resolutions.

Go to the W3C site and validate your code.

Center the container containing the ol or ul tags, or add such a container.

I make a Word document with the formula in it, and take a screenshot.

Before you do anything else, validate your code with W3C:

http://validator.w3.org/

Firefox is a lot more likely to object to bad code.

This is not quite right.

The purpose of tbody is to go with thead and tfoot to make a table that has a header and footer that are always visible when the table is larger than a page.

If you use tbody, you also need to use thead and tfoot, and they must be placed in the following order:

<table>
  <thead>
    <tr>
      <th>stuff 1</th><th>stuff 2</th>
    </tr>
  </thead>
  <tfoot>
    <tr>
      <th>stuff 1</th><th>stuff 2</th>
    </tr>
  </tfoot>
  <tbody>
    <tr>
      <td>stuff 1</td><td>stuff 2</td>
    </tr>
  </tbody>
</table>

I had the same trouble, and recycled Spybot.

Browsers have accessibility settings to disable changing the colors of links. Check your settings.

Link color metastyles are global in nature.

Using size styles (width, height) and nonzero surround styles (margin, border, padding) in the same tag or stylesheet style guarantees an incompatibility between IE rendering and FF rendering, because IE nests them in the wrong order.

The problem is the order that IE displays size styles and surrounding styles.

Other browsers display the sizes INSIDE the surrounding styles (margin, border, padding).

IE crams the surrounding styles inside the sizes. So the sizes must be made larger, to make room for the surrounding styles (unless the surrounding styles are 0).

First of all, table is NOT deprecated in xhtml. There is no reason to avoid using a table where a table is needed. This sounds like tabular data.

What is discouraged is the use of tables to simulate margins and padding. This was done before styles were invented. Using tables to delineate sections of a document is also discouraged.

It is impossible to center something vertically on a web page and have it work on all browsers and screen resolutions.

The internet is not designed to exactly fill a screen, and is not intended to be used in the way you are trying to use it. Web page rendering is designed to start at the top, and expand downward until content is exhausted.

It should not be considered a "vs" situation. Some sites need both.

The only thing "wrong" with using a table is that a reading program for the blind will report table positions.

If divs can't do the job, go back to a table.

The use of tables that the W3C says should really not be used is the use of tables to simulate margins and padding.

Don't put size styles (width, height) and nonzero surrounding styles (margin, border, padding) in the same tag and/or stylesheet style.

A ul tag cannot be the direct child of another ul tag. The browser goes into quirks mode if it finds this.

When styles conflict, styles lower in the stylesheet are given priority over styles above them.

I saw it, but it disappeared before I knew to get a screenshot. It was an ad that launched popups when the mouse rolled over it.

First of all, don't put text on top of a bright colorful background, or people with certain vision problems or dyslexia can't read it at all. Use a pastel background.

Second, use the background style on the body or a div. If Frontpage doesn't offer this, change to writing pure xhtml code.

A few tips:

1. Never put size styles (width. height) in the same tag or stylesheet style with nonzero surrounding styles (margin, border, padding). This is guaranteed to create a compatibility problem between IE and Firefox (IE nests them in the wrong order). Instead, nest two tags, and apply the size styles to one, the surrounding styles to the other.

2. Don't use absolute positioning. IE and FF differ on how to interpret the positions. And different display resolutions mess up the positioning.

3. Rollover menus belong in the recycling bin. They are a stupid fad, and make navigation much harder for dyslexic people. It should be illegal to make something happen when the mouse just points at something.