Posts by MidiMagic

You haven't given public read permission for your pages. Only you can see them.

In both cases you are trying to put a box object pair (table, and anything else that takes a border) inside an inline tag pair (anchor). This does not work. There are very few things you can put inside an anchor tag pair.

There are a few ways to solve this:

1. Put an onhover and onclick calls on a box object to call JavaScript routines that change the background color or border color, and/or call the link.

2. Use an image of the box and text. You CAN put an image inside the anchor tag pair.

3. Use a button (form object) with your text in it. The entire button (and its styles) is active.

4. Be content with just the text being sensitive.

You have not yet given public permission to view the files. This means that only you can see them. You need to change the permission settings for them in your ISP.

This may be a manifestation of the fluid nature of div tags. If you absolutely need a rigid structure, use a table.

This can also be caused by the IE incompatibility. This happens when you put nonzero surrounding styles (margin, border, padding) in the same tags that contain size styles (width, height).

IE puts the surrounding styles inside the size styles. Other browsers follow the standard, putting the surrounding styles outside the defined sizes.

The fix is to not put them in the same tag or defined style. Instead, nest two pairs of tags, one with the sizes, and the other with the surrounding styles. Then all browsers render the page nearly identically.

Percent does work in padding. I use it all the time.

The problem is the main incompatibility between IE and the other browsers:

Putting size styles (width, height, or the size of an image) and nonzero surrounding styles (margin, border, padding) in the same tag or defined style causes the trouble.

IE puts the surrounding styles INSIDE the defined sizes.

All other browsers follow the standard and put the surrounding styles OUTSIDE the size styles.

The cure is to nest two tag pairs, one with the defined sizes, and the other with the surrounding styles. Use a div pair for the extra tag pair. Now you can control the order of nesting.

This will fix the problem. It also fixes IE object positioning problems.

I usually set up styles as I need them. And I design the big parts of the page first, and then add the little details.

And no lorem ipsum in the final product.:icon_mrgreen:

Here's what I use:

<style type="text/css">
.cenx {text-align: center;}
.bxfix {margin: 0; border: none; padding: 0;}
.ceni {clear: both;}
img {padding: 4pt;) /* set to what you want */
</style>

....

<div class="cenx bxfix">
   <img src="im.jpg alt="Imagetocenter" class="ceni" />
</div>

The page is huge, compared to the window size. You got all that to fit on one screen?

The property "selectd" is spelled wrong, and should be selected="selected" .

Can it handle the Independent Voting System, or is it restricted to the faulty Plurality Voting System?

I don't understand the limit on searches applying when I go BACK, from the first search item I looked at, to see the results list again to look at another found item.

It should not perform the search again, but it tries to, and replaces the results list I want to use with the error message.

Why I need more than 30 minutes:

If you navigate to get a link or an object, when you return, the post text is GONE from the editing box. You must post it, and then edit it after you get the item into the clipboard.

With the torpidity of the Internet, you can get only two or three items before the time limit is reached.

Are you applying it to the body, or to the objects within the body. It must be applied to all of the objects you want to see the background through.

Note that it doesn't work with form text boxes.

The real reason is that you can't have cross-browser compatibility if you place nonzero surrounding styles (margin,. border, padding) in the same tag that has size styles (width, height).

IE crams the surrounding styles INSIDE the size styles.

Other browsers put surrounding styles OUTSIDE the size styles, as the W3C standard states.

Positioning with respect to the browser window is not cross-browser compatible.

Since I don't have Opera, I can't see the trouble. But you do have several common troubles:

- Nonzero surrounding styles (margin, border, padding) in the same style definitions and tags that have size styles (width, height) causes cross-browser incompatibility.

- You have a typo: w\idth

- The location of an object placed by absolute or relative positioning is not cross-browser compatible. Position objects relative to the immediately containing tags, not to the browser window.

- Negative surrounding style values are not consistent.

Float tells the browser whether to make the text flow to the left or the right of an object.

>There are settings in browsers that disable the ability to change link
>colors on web pages. So some people get cute with the links, and
>the link disappears entirely on a browser with link color disabled,
>because it matches the background.

That made absolutely no sense at all. If the browser doesn't allow you to change the color of the links, what makes you think that trying to change it will in fact, change it? :icon_rolleyes:

Not to mention that the very site you're posting on uses custom link colors (and most modern sites these days, if you bother to take a look at the CSS), I'd say that your last point is worth a little less than garbage.

Wrong!

There are accessibility settings in many popular browsers that disable the changing of link colors as an aid to the handicapped.

Changing the link colors usually doesn't cause trouble, but if the site has the background color set to blue, and the link color set to white, the link totally disappears on a browser with the link colors disabled. So the handicapped person using the site can't see the links.

I found this out the hard way, when I put white links on a rainbow-colored background. I got an email complaining that the user could not see some of the links.

Another case is where the link color chosen is not displayable on a screen with a small number of colors set for …

His page is xhtml. It requires the self-closing form of br: <br /> The problem is the use of the br tag to insert breaks in the text. The correct way to display this is to use p tags to surround the paragraphs. This is not the intent of the br tag. The br tag is for forcing a single new line in the middle of text, without inserting a blank line.

Wrong:
<div>
  text
  <br><br>text
  <br><br>text
  <br><br>text
</div>

Right:
<p>text</p>
<p>text</p>
<p>text</p>
<p>text</p>

The problem is in the fluid nature of div. It doesn't always obey the height and width properties, unless forced to by surrounding objects. It "thinks" displaying the content is more important than the defined size.

Several problems:

- The <!-- --> tag pair does not work in xhtml to hide scripts and styles. Styles work in xhtml without those tags, and scripts should be external.

- Absolute and relative positioning are NOT browser-independent. Don't use them. Instead, place a container around the menu area, and let the menu items fit against each other inside it.

- Remember putting that nonzero surrounding styles (margin, border, padding) in the same tag or style definition that contains size styles (width, height) causes browser incompatibilities. IE nests them in the wrong order. Nest two tags, and apply one kind of these styles to each tag.

- Stuff appearing on top of other stuff doesn't always work right. The technology is not yet universally defined.

I'm here! But I can show up only 2 or 3 times a week.

You can't have more than one pair of inline style tags. You have two. And style tags must be in the head. One of your pairs is between the head and the body.

You also have the IE/FF compatibility bug.

Actually, IE is the troublemaker here. Since you adjusted things to work in IE, they don't work in the other browsers.

But you can fix it.

The real problem is that you have nonzero surrounding styles (padding, border, margin) in the same tags and defined styles containing size styles (height, width). The problem is that IE handles this situation in a different nesting order:

- IE crams the surrounding styles INSIDE the measured sizes.

- The other browsers put the surrounding styles OUTSIDE the defined sizes, as defined in the W3C standard.

The remedy is to not apply nonzero surrounding styles to the same tags that have size styles. Nest two tag pairs, applying surrounding styles to one pair, and size styles to the other. Now you can control which is inside the other.

Div is a good tag to use for the inserted tag for the nesting.

The table prevents the browser from resizing. The td tags size to the image. It causes scrollbars to appear instead.

xhtml does not allow empty tag pairs.

You can put something between the tags (such as an nbsp), and then overwrite it with the script.

I don't want to pay extra for fancy looks.

I have sets of styles I use.

- A basic set that includes styles for centering text, images, and objects.
- A palette of colors for backgrounds.
- Styles for div columns.
- Table styles.

I start with the basic styles, and add others as I need them. I build the site top down, as one would build an outline in English class.

Right.

Visibility also has a "collapse" property.

I thought you didn't want the structure to change.

Administrator policies can be used on company owned computers to disable this key.

The problem you really have is that this key is part of Windows and the browser, not part of your program. To make this modification, you have to alter the software the user has on his computer. This can cause numerous problems, including a violation of the user agreement with Microsoft. And it is considered to be illegal hacking.

It is also a web security violation.

IE has a nonstandard extension to JavaScript that redirects keys on the current page. Other browsers do not have this. But it does not redirect the refresh button (if that is the reason you want to disable f5).

This is a legal matter. The year doesn't matter. Our property rights should be the same in any year. You do not have any right to modify the behavior of any computer you do not own. That includes any web user who accidentally lands on your page. The key legal point is obtaining the permission of the owner of the computer.

If you find a way to disable f5 on someone's computer without their permission, then someone else can use what you find to disable a key on my computer without my permission. This is depriving me of my property rights.

If the users want to create redirections of f5 on their OWN computers, that's another matter. That can be done with available software that redefines keyboard keys. And if the company owns the computers, the company can modify them individually. Or you could provide software the user can download and then voluntarily run to effect the changes.

Alternately, if your application is a server-side application, you can modify it on the server so it does not respond to the f5 key, or write a filter that looks for the command from the browser and eats it.

If the script is embedded in the web page, it might be finding and matching itself.

Replace the manager with one who can write code.:icon_cheesygrin:

The only real way to set page properties is to put them into a stylesheet used by all files. But that means that each page must use the stylesheet in the same way.

You may end up with the job of implementing the manager's wishes.

It must be a server-side script. It can't be done in JavaScript.

SQL usually does not do that. It wants to keep the same ID for the same record in perpetuity.

The easiest way would be to delete the numbered column, then add it again as an autonumbering field. But it must not be the field the data is sorted on, and it must not be a primary key.

You don't send an email with a button.

You send the temporary file to the manager as an attachment. Then the manager does the appending.

If they can see the image, the file is already on their computer. All they have to do is retrieve it.

Don't specify the image size in the html code. This causes the browser (as opposed to the graphics editor) to change the size of the image. It is not well adapted at doing this.

It's possible with a .bmp image, since each byte corresponds to a specific point in the image. It makes a speckled part of a horizontal line in the file.

Because data compression is used in other image file types, it is not possible to put such info into other kinds of image files.

Note that anyone who has seen the image in the royalty-free pages will recognize it when he looks at your page.

He means those things where you have to type in the letters visible in an image to validate the submission.

This requires a server-side script.

The problem is that the market for people able to do this is oversaturated. For every job, there are 100 applicants.

The problem is in your style.

....{width: 78px;
     height: 112px;
     margin: 0px 5px 0px 5px;}

You have size styles and nonzero surrounding styles in the same style. This causes IE to behave differently than other browsers.

The other browsers put those 5px margins outside the 78px width, for a total width ofg 88px.

IE puts those 5px margins INSIDE the 78px width. This means the picture won't fit in the
space reserved for it. The browser drops into quirks mode, and tries to fit the pictures any way it can.

Display the title of the page instead of the link. Or do something like this:

<p><a href="this.is.the/really/long/url.htm">this.is.the/</a>
<br />really/long/url.htm</p>

Or even this:

<p><a href="this.string.is.the/really/long/url.htm">this.string.is.the/</a>
<br /><a href="this.is.the/really/long/url.htm">really/long/url.htm</a></p>

The last one makes both pieces of the link text active.

There is no way to place an object at the bottom of the screen and have it work for every screen resolution.

The Internet does not work on the basis of a screen the size of your monitor, but on a downward-expanding page that grows until everything fits. Do not expect your material to fit exactly on one screen. It won't.

background-color: transparent;

Since each browser has its own way of rendering text, you need to do the following:

- Don't expect your page to look exactly the same in all browsers. This is impossible.

- Don't use either absolute or relative positioning. Use containers to position the text and the graphics.

- Place the image, using the location of the img tag within the text, and use the float style to position it left or right.

- Don't expect to center an image within text, because it is impossible to make the text equally wide on both sides. If you need to center an image, make the spaces on both sides clear.

- To keep the layout from falling apart, you might need to use table tags.

Excel has a "Save as web page" option in the File menu. Do all of your calculations with ranges, so you can insert a column and they still work. Be sure to use the correct cell addressing modes, so inserting a row doesn't change your references. Then, just replace the old page with the new one when another game is played.

I used this function to produced updated statistics for time sheets on a job. If it worked for that, it works for sports stats.

What about distributing the changes at night?

How about using a network server for one shared file?

Export the data to an Excel spreadsheet.

Or better, open the file into Excel (use the file type dropdown in the Open window), then save it as an Excel spreadsheet.

You need two tables. One is for the temporary file sent to the manager. The other is the permanent table, under the control of the manager. The manager then merges the record into the main table.

Are you constantly repainting them? If so, you need to not repaint them until an object changes color. Then repaint it only once.

This depends on what is in the object module at the time the script loads. Scripts can not see dynamic changes made to web pages, unless the script is keeping track of the changes it makes itself.

Whether a script can see the style depends on when the script starts.

JavaScript can't access the file system of a computer.

Webpage components: yes.

Files: no.