Posts by MidiMagic

This is a place where the browsers are not the same. The divs are inheriting the center attribute from the outside div in FF, but not IE.

The second div is also too large, since it is wrapping. FF decided to give it maximum width by placing it below the other div. This is part of the fluid nature of div.

Also, you are mixing css with the deprecated align attributes. This can cause unpredictable results.

Since you are already in a table, use the table to place the two parts where you want them. Tables always stick together in the correct order if all of the tags are present.

This is a place where you should use a query. With it, you can display data from different tables in the same screen.

You can also use a query.

That's to keep you from accidentally deleting an unsaved feature.

You are making a copy of the array with your function declaration. Then, when you return from the function, the copy is not copied back to the original.

Either address the array globally (don't use it as a paramet4er, but just use it inside the function), or return it in the return statement.

Did your hard disk get fuller?

Why the sudden interest in zip files? Some of us can't open them.

It depends on whether your browser image rendering setting is set to "shrink to fit" or "scroll large images."

If it is shrinking to fit, text on a saved image may shrink too small for the display resolution on the screen you have.

This is a very difficult problem, because you are trying to create transparency on top of a moving image. Remember that text has either a colored background, or has a transparent background that shows what is behind it. But it becomes a huge task of working out for each pixel whether or not it should be test pixels, or part of a movie. This doubles the processor time needed to show the movie.

This is a case that needs a table. It is extremely difficult to do it with divs and css. But you can certainly use css to format the table.

If the sides are empty, just use padding on the body tag.

There is a misconception on removing tables from websites:

The original problem was the misuse of tables, because there were no margin, border, or padding attributes available without tables. So web programmers started using tables to create these styles.

Tables should be removed if they are used to create margins, borders, or padding on otherwise plain sites.

Tables should be retained if a strict layout is needed, because they are the only web objects that always hold the positions of the contents the same, relative to each other. Pure div/css designs fall apart if the contents don't fit.

For example, my home page is designed with two div columns, but it collapses to one column with a low-resolution browser, a small browser window, or on Web TV.

A few points:

- 0px is an invalid style. It causes browser errors. Use 0 for values that are zero.

- Convert all size and alignment tag attributes to styles.

- Use classes, so each set of styles can be used on all tags needing it.

- Use relative sizes, as percentages of the width of the containing element.

- Don't place nonzero surrounding styles (margin. border, padding) and size styles (width, height) in the same tag or style. Putting them together causes browser incompatibilities, because IE nests them in the wrong order.

- Convert one property type at a time. Then test the changes.

- Use tables if you need a structure to hang together when the window size changes. Use divs if you want to allow the content to slide around for maximum visibility without horizontal scrolling.

- Don't use absolute positioning or styles, except for image sizes.

- Test the page with different browsers and screen resolutions. Also play with the browser window size (in restore down), to see what happens when the resolution or window size becomes small.

- Use the W3C validator page.

You ought to check that span method on other browsers and screen resolutions. The text positioning might change drastically.

If they send the files to you, you could edit them before putting them online.

If your ad is a banner across the top, everything else will move down.

Absolute positioning in a web page will mess up any attempt to add an ad.

Note that this site requires all ads for each position to be the same size.

You must put things on the left before things on the right.

0px is an invalid style. Use 0 for any zero value, without units.

Are you talking about the missing green lines in the borders?

You have empty div pairs. Nothing is placed between the tags. This is a nonstandard use (a no-no in web page design). There is no guarantee that an empty pair of tags will be rendered. If there is room, it will render, but if it is squeezed for space, it will be skipped.

Why don't you just enclose the text in a div with a border style?

Another possibility is that the line of pixels containing the border is not rendering because the display unit decided to skip that line.

It's better to write code that works in all browsers.

Don't assume that everyone had the capability to open a compressed file. This ability is purposely banned from the computers I use.

Your scripts are putting other things on top of the video.

Try to build pages with objects INSIDE other objects, not ON TOP of them. Layering is not yet fully implemented so it works well.

You need a for or while loop to repeat all of the records.

But why don't you just use the export function under File.

I come here only once a week.

Check to see if they have Microsoft Excel export and import in common.

That sounds like a job that would never be done, because while you are writing the huge amount of code to do that, the services will change their pages, so you would have to start over.

Use a regular button with the word RESET on the face. Use it to call a function to put default values in the ones you want to reset. I wrote several of these.

Keepvid works too.

You can disagree all you want, but I have this problem myself. It normally doesn't bother me, unless there is moving content.

The problem is that the moving content clears the equivalent of a text buffer in the minds of some dyslexics. They then have to READ THE PAGE AGAIN, after the item moves or expands.

I would rather wait for a page to load than have to read the page multiple times. Or better yet, I would rather scroll through the larger images.

Some people are just TOO impatient. They should be required to turn a crank 100 times before the image appears.

Make sure the styles for the top, middle, and bottom have widths of 100 percent in them, and margins and paddings of 0. If you want margins or paddings on any of these, nest more divs inside them with the padding and margin styles wanted.

<div id="wrapper">
  <div id="top">
    Top content.
  </div>
  <div id="middle">
    <img src="fid.jpg" />
  </div>
  <table>
    <tr>
      <td>
        Left content.
      </td>
      <td>
        Right content.
      <td>
    </tr>
  </table>
  <div id="bottom">
    Bottom content.
  </div>
</div>

They put the page into a frame, with the ads in another frame.

But it also makes any page that was so carefully crafted to validate on W3c fail to validate when displayed on the combined page. This makes web page makers mad.

Alternately, you could require that the page author provide an img tag with a link to the ad.

Please, no moving ads. They make me click Back faster than anything else.

I can think of several reasons:

- Different browser communications settings.

- Different methods for the way the browser assembles the page.

- Different handshaking orders.

- Different methods of resizing images to fit.

- Different methods of displaying (maybe one waits until the entire image is downloaded before displaying any of it)

- Different internet cache settings.

- Fragmented internet cache on one browser.

- If both are installed on the same computer, the second one might get a less optimum cache space. It's even worse if both programs are open.

- Different virus checker settings or methods.

It's the same (and working) in both browsers for me.

No, because all images are really rectangles. The rest of that image is transparent. But the browser has no idea where the content is within the rectangular image.

I have some ideas:

1. Cut the image in two. But placement is tricky.

2. If the image is really solid green like that, you could make it with table components.

3. Put the text in a larger image containing both.

I really don't see how any company that annoys you to death (or freezes your scrollbar) expects to gain customers.

Just like Microsoft, who also can't seem to leave stuff alone.

I don't want a different browser.

The color of the scrollbar is now defined by Microsoft, not the browser.

This is the only website with the problem.

Don't design to an absolute size.

From computer to computer, you are going to find:

- Different screen resolutions

- Different color sets

- Different browser software

- Different window sizes

- Different monitor dot sizes

You have to make things flexible if you are going to have approximately the same look across a variety of computers.

You must accept the following facts:

- Different computers have different numbers of pixels for the vertical and horizontal sizes of the screen.

- People with vision problems use lower screen resolutions.

- Your page is going to look different on different display sizes.

- If stuff is too wide for the display, it scrolls.

- There is no way to make a page exactly fill the screen vertically.

- The same image will fill a larger part of a low-resolution monitor, and a smaller part of a high-resolution monitor.

- Many flat-panel monitors have lower resolutions.

- Layers don't work on many computers. This feature is too new.

- Absolute positioning does not work on different screen resolutions.

- Web TV browsers have a very low resolution (320 X 200).

What does work:

- Use percentages of the screen width to position things.

- Position things in zones, with enough space between objects to allow for shrinkage when the resolution is lower.

- Don't even think about trying to make …

Remember that some people are totally sick of hover effects. They are cute little tricks that are quickly becoming annoying, and they are accessibility problems for people with dyslexia. They will flee your page with the back button.

It's never going to work with absolute settings. Different browsers will render it differently. Different screen resolutions and window sizes also cause trouble with absolute settings. Use percentage of page settings instead.

You may also be seeing the IE/FF incompatibility. Placing both size styles (width, height) and surrounding styles (margin, border, padding) in the same tag or style causes all kinds of strange fit problems.

It is the nature of a div structure to fall apart if it won't fit. You will never create a div structure that holds its shape under all conditions. The reason it doesn't work is that there is no equivalent to the tr tag in div structures. Browsers float div tags wherever they will fit.

If you absolutely need the same structure to hold together for all window sizes and screen resolutions, use a table. It is not deprecated. There is a misconception about what is good web practice and what is not.

What is discouraged is using table tags to create borders, margins, and padding around website objects. At one time, this was the only way to put margins around pages.

The reason some people don't want tables used for page structuring is that it is confusing to people using a speaking reader for the blind. But if the table is used for just the two parallel columns, and not the rest of the page, it works well, and is not too confusing, since it is a table of …

You don't have anything between the opening and closing span tags. This causes the tag to fail to render at all.

I am building pages that work the same (or very nearly the same) on both.

Tips:

1. Don't put surrounding styles (margin, border, padding) in the same styles or tags as size styles (height, width), other than to set the other ones to 0.

Internet explorer renders these in the wrong nesting order, causing most of the incompatibilities. The fix is to nest two box objects, one with the surrounding styles, and one with the sizes.

2. Don't use tags wrong. If the browser finds an error in the code (or no doctype), it goes into quirks mode. FF and IE have very different quirks modes.

3. Be aware that IE makes fonts one pixel wider than FF does.

4. Define horizontal and vertical text alignment for tables in styles. IE and FF have different defaults.

Do you in fact have a CD burner?

Is the burner program in simulation mode?

Are you going for some kind of award for the hardest to create webpage in history?

And I suppose you don't want the curves to change shape if the button stretches the image.

The only way I can think of to do this is to have a series of images for different lengths, and pick the one that works for the length of the text.

By the way, I am totally sick of rounded corners. They remind me of early 1950s roller rinks.

I had changed the color of the scrollbar to fix this,

Microsoft's latest upgrade removed the ability to set the color of the scrollbar, so I am back where I was again. I can't see the edge of the scrollbar on the right side of the screen, because it matches the background.

Some browsers do not allow certain styles on form items.

Your background color is overriding the background image, because it is later in the stylesheet.

Use the percentage styles to get the browser window width into styles.

.classname1 {width: 100%;}
.classname2 {width: 50%;}

Maybe that is because IE displays fonts one pixel wider than FF does, for the same font size. You are not doing anything wrong. The browser makers can't agree on standards.

Check the settings of the browsers too. A user can tell the browser to increase or decrease the font size from that specified in the page. This will stay that way until canceled.

Don't try to cram too much text into a space.

The problem is that not all monitors have the same screen resolution. If you design a page to fit a certain screen resolution with absolute sizes, the following happen to the page:

- On monitors with lower resolutions, scrollbars will appear.

- On monitors with higher resolutions, the page will be in the upper left corner.

To make the pages more flexible for resolution changes, do the following:

- Use relative sizes and positioning. Usually this is a percentage of the width of the page.

- Don't use a page creator such as DW.

- It is impossible to exactly fit a page vertically for all monitors. Don't waste time trying. If you don't want scrollbars, don't put stuff near the bottom.

Put the visited styles at the top of the stylesheet, with the hover ones under them.

If there is a conflict between styles, the lowest one listed in the stylesheet prevails. So the visited ones are prevailing over the hover ones because they are under them.

You are mixing styles and tag attributes. The tag attributes will override the styles.

You can not mix size attributes (width, height) with surrounding styles (margin, border, padding) on the same tag. It causes incompatibilities between IE and Firefox.

Your font size might be smaller than the smallest the font is defined, since fonts are not usually defined in pixels.

You have illegal values in the styles. They deactivate the entire style they are in.

The value 0 must NOT have a dimension suffixed to it (such as 0px).

If an object will not fit in the space allocated, the space will expand to let it fit.

Use the Error Console in the Firefox Tools menu to detect bad styles. It will list the errors after you open the page.
.

What you need is one table with a list of all of the products, and more fields for the different kinds of products to link to the original tables you have.

Did you use the name of the field the query produced?

I got it to work, using the name of the field produced by the summary data function.. But you can't use data from both a table and from a query based on that table in the same form.

Make two different forms, one for each purpose.