That's a myth. Screenreaders aren't confused by tables, they just read them in a specific way. Weird markup order and other 'unusual' div constructs can confuse screenreaders just as much, sometimes more.
It's the users of the screenreaders who get confused. they are blind.
Not really. Removing the "px" changes nothing. And 0px really doesn't make sense to you? How else should you remove a border inherited from lower down in the cascade?
It's not me that does the complaining. it's the browser. Firefox will throw away any style that contains 0 with a unit of measure attached (such as 0px, 0% 0pt). You have to put just the 0, with no unit of measure:
.mystyle [margin: 0;]
Border prefers the "none" attribute, rather than 0, if there is to be no border at all.
But margin and padding do not know the "none" attribute. You have to use 0 with them.
Originally Posted by MidiMagic I'm talking about using div to make a page that doesn't fall apart if someone (or the browser) looks at it wrong.
Yes, so am I.
How is this achieved? When you shrink the browser window, or use a different screen resolution, the divs won't stay put.
I'm talking about divs that don't go crazy when you put a list or a table inside.
Me, too.
How is this achieved? Whenever I try it, the list won't stay together, or the table pokes outside the div.
I'm talking about divs that can be made to expand to fill their containers without using absolute measures.
If you use absolute measures they cannot expand.
They certainly do not respond to the width and height styles correctly. I had divs inside of table cells to further format the contents. They never would expand beyond the size of the text they contained.
I had to use absolute measures {height: .75in; width: 1.5in;} to get the div to expand to the size of the containing table cell. 100% height and width did not work.
The table cells were of fixed height because one cell in each row contained an image.
I'm talking about structures that don't take several hours of tweaking to make them work.
Agreed: <DIV>
It won't work. Every time I try to make what seems to be a straightforward structure from div tags, something goes blooey in the browser. and it falls apart: Either stuff leaks …
The reason the W3C wants tables kept to tabular data is that web readers for the blind announce the row and column of every table cell.
So is there a way to put a style in to get the web reader to shut up about the rows and columns when the table is used to keep a layout from falling apart?
Alternately, we need dtr and dtd tags that behave like the tr and td tags of a table, to get the div ducks all in a row (or column).
The relative size of the h1 font-size style is referenced to the base font size, not the large font size used for h1 by default. So I was actually asking for the font size h1 normally uses when I asked for a double size with 200%. The result was no visible change.
Sorry, but.....I have the right indeed....it's my website... If it where like you say, I would hve to let the visitors to change every aspect of my website...everything.
Suggestion, do not reply posts If you're not helping...that's the idea of the forum...
You do NOT have that right. You are effectively saying that the user can't leave your website, by taking away his controls. This is committing a wrong against the user by taking control away from him and taking over his computer.
I am totally SICK of web page designers who design pages the user can't leave without using the task manager. It should be illegal, with jail time. I have seen this trick used on eBay too often. They fix it so you can't do any comparison shopping once you get to the page. You have to bid to leave it.
Don't play sounds when people open your home page. This can be extremely annoying, especially if someone reaches your site while searching for something else, while sitting in the middle of a cubicle farm. It generates excessive prairie-dogging.
If you want a sound, put a link to the sound on the page, so the unsuspecting search engine user can avoid it.
- Are you out of disk space? - Are you out of RAM (project got too big for the workspace)? - Is the file damaged (try another project file)? - Did you take a disk or flash stick out of the drive before the project was fully saved? - Are you trying to open a project with one or more components on a read-only CD? - Is a file write-protected? - Is a component of the project on a removable disk that is not now in the drive? - Does the computer need rebooting after a power glitch or a thunderstorm?
<a name="overhere"></a>
<h2>Overhere</h2>
<p>something about overhere...</p>
I think your code and styles are confusing it. You have several things that each can force the top of the line off the page:
- The A tag is empty. That makes it render very small at the bottom of the line of text, if it renders at all. Put the a tags inside the h2 tags and the contents between the a tags. I think this is it.
<h2><a name="overhere">Overhere</a></h2>
<p>something about overhere...</p>
Empty tag pairs cause all kinds of rendering trouble--never leave tag pairs empty. If you absolutely must have an empty tag pair, put a nonbreaking space between them.
- I often have trouble getting IE to correctly render h# tags when relative font size (em) measures are used.
- The font size of 1.7em and the height of 40px may be placing two different constraints on the same item that different browsers react to in different ways, especially under different screen resolutions.
- Negative surrounding styles are also not defined by the W3C, and can make quite a mess. Never use them.
- Try defining your padding in units other than px (try em instead).
If none of these work, one thought is to attach the anchor tag to something small in a line above the title (maybe an hr tag, a nonbreaking space, or a line of ----- …
I can't tell from your text whether you are trying to match the height of another div, or trying to fit the browser window.
It is very hard to make a div the same height as a div to its side. The fluid nature of a div makes it impossible to force it to a specified height, except in the dreaded absolute terms. This is one of the cases where table works better.
You can't make a page fit the browser window, because you can't know what size the user's browser window is.
Different browsers, versions, screen resolutions, installed plugins, security settings, and window sizes make this practically impossible.
This is not an intended use of the Internet at the moment.
The two are synonymous. Surfing the web IS downloading material.
What you could block instead is INSTALLING anything. Check your firewall settings.
Another way is to make sure that only a system administrator has an administrator account. Normal user accounts are usually prevented from installing anything.
Once you have user accounts, you can also remove all of the players and player plugins that are needed for some of the bandwidth wasters. This can be a problem if QuickTime is installed. It installs itself in a way that it can't be removed, so a system rebuild is needed to get rid of it.
