I do not have a copy of the notebook image for your latest code. Your new size is 608x460 and it has the name: 0337820501_2prevstill.jpg Could you please post a copy of that image in this topic?
yes of course here it is:
Do you know how it came to be messed up? Do you know what happened that broke the tables in the row with the ?
i think what it was really messed up is this table code that i do not why i delete it it was on the original page this code lines:
A few messages ago you said that you had never seen one of your pages pass the HTML validator test before. Now you can say that you have written one that does! Thatās progress.
thanks
I assume that you have tested the page. What do you think you should do next?
i think to place the buttons where i want and the text field make the width equal like the last text field i think do on it css
To do that reliably, you cannot use nested tables. Nested tables are isolated from one another and cannot be arranged in related columns.Are you willing to use one table instead of nested tables?
Why i can not use nested tables You can not arranged in what is in columns tabs as you want?
and why it is not reliably is it a rule to nested table?
Nested tables imply that a single entry within a set of tabular data is itself tabular data - this is extremely rare. I doubt that anyone has come up with a situation yet when creating a web page where nesting tables would be semantically correct and the purpose of HTML is to semantically identify what the content is. Using even a single table is reasonably rate - should occur on less than 1% of pages on a typical web site.
Did you try zooming the text in the valid code that you last posted?
This is your code that you last posted. I added outlines around the table-cells. RED are the outer table-cells, BLUE are the nested table-cells. As you can see, the nested table-cells do not have any relationship to one another. They are not vertically aligned. How could someone tell the buttons to align beneath the ends of the textarea? They do not know anything about each otherā¦ and the buttons are not in a nested table-cell, they are in the outer table.
.
If you use one table, then the columns will align vertically. That is the rule of tables. That is how they work.
or with the width of the text fields unrestricted (notice the buttons follow the edges of the textarea the way you like).
Nested tables do not work the way you wish they worked.
Did you try zooming the text in the valid code that you last posted?
no i didnāt but i try it now and you right it is like in your image
This is your code that you last posted. I added outlines around the table-cells. RED are the outer table-cells, BLUE are the nested table-cells. As you can see, the nested table-cells do not have any relationship to one another. They are not vertically aligned. How could someone tell the buttons to align beneath the ends of the textarea? They do not know anything about each otherā¦ and the buttons are not in a nested table-cell, they are in the outer table.
or with the width of the text fields unrestricted (notice the buttons follow the edges of the textarea the way you like).
Nested tables do not work the way you wish they worked.
so i have a some questions:
is it in that way is the easy way to do with one table?
can i force the nested columns table to do what i want? is there a way to do it with nested tables?
and if i was having nested columns around the buttons what will happen?
Anthing can be done with nested tables but NOTHING should be done that way.The need for using tables for anything except tabular data is long gone and I have yet to find an example of where any of the content of tabular data is itself tabular data and where the information is still simple enough to display on a single page.
Nested tables is a 20th Century approach and is inappropriate in the 21st Century.
Note that there are also some browsers where table borders canāt be turned off.
NOā¦ for the reasons already stated above and demonstrated in the image showing how your code with nested tables renders in a browser. Nested tables are isolated from one another (third time).
No, not reliably (as already stated). It will work unreliably like the image using your code shows above.
No improvement. Nested tables are isolated from one another. They cannot form natually related columns. The button row already does not know about the first 4 rows. Nesting the button row will not reduce the isolation of the buttons.
Whether it is easy or not depends on you. The layout is reliable as shown above in two images. Plus, Dreamweaver does not lose a button.
Before I decide which table to make i was looking on the Handbook that gave me on the a course on what you were talking about the table i was not found but there is a part that talks about building a absolute and rltibi grid to a site with tables and they where talking that is highly recommended to place a table inside a table to get maximum control on the site.
on that i want to know what is your opinion,what you think or whatever?
I do not know what you are describing. I do not know what a ārltibi gridā is. And I cannot imagine anyone ā¦
ā¦in the last 12 plus years. You are reading something that is very old.
What is the date on that handbook and the information that it contains? When was it written? Who published it?
In my opinion, your struggle to prove that outdated technology is the way to go today is a waste of time.
If you understood how these HTML tables and CSS properties worked, you would understand why nested tables cannot accomplish what you wish to do easily, if ever. You are fighting the wrong battle. You should be fighting to learn new things that work instead of fighting to hang onto outdated things that do not work the way you wish they worked.
I will urge you to build one table using Dreamweaver with 5 rows and no attributes. With that and some CSS, you can create your form and place the buttons where you want them. It is not pushbutton easy, but it is not as hard as you fear.
I do not know what you are describing. I do not know what a ārltibi gridā is
.
i meant when you do relative/absolute grid to a site in tables i think in table in general it is highly recommended to place a table inside a table to get maximum control on a site. absolute if you do table that has a total width in pixels and relative a table with a percentage relative width no matter what resolution is displayed it will take up the same relative width across the screen.
And I cannot imagine anyone ā¦
what you mean about that?
you would understand why nested tables cannot accomplish what you wish to do easily
tell me if i am right when you say that you can do it with nested tables but it will me not easy but it can be done
,I will urge you to build one table using Dreamweaver with 5 rows and no attributes. With that and some CSS, you can create your form and place the buttons where you want them. It is not pushbutton easy, but it is not as hard as you fear.
where do you want me to do that?
What is the date on that handbook and the information that it contains? When was it written? Who published it?
about the handbook i do not know what year it is published but it is on write on the first dreamweaver i think dreamweaver cs3 i have cs6 and i think a teacher that was taught in the college write this book.
Tables were originally intended to display tabular data - which is still their purpose today. In the early days of the Internet, there was no real way to control the layout of a page, and tables started to be used for that purpose, because there was no other way. Then CSS was introduced, to provide a way to style pages and control layout that was separate from the HTML markup. Using CSS, there is no need to use tables purely for layout - ever. Is CSS something new? No - it was first introduced in 1996. So if the course you are taking is still recommending the use of tables for layout, it is teaching extremely outdated techniques which have not been used for many years, and which will not stand you in good stead, should you wish to pursue Web design after college.
Yes - you can use nested tables to lay out your page. Should you? No - there are better ways to do it, which will give you more control. (You can use an axe to chop a cabbage. Would you? No - because there are better ways to do it, which will give you more control.)
Wow, youāve been doing a lot of studying. Just a few messages ago you insisted on using pixels because you did not learn percentages and now percentages and positioned tables in a grid are the answer that you seek that will let you use nested tables. Thatās very impressive! I am amazed by the amount of energy you expend and work you will do to use outdated nested tables where they should not be used today.
We have long ago discussed the demerits of absolutely positioning content on a page.
Please show us your page when you are finished. Iām very curious to see how it works out.
PS: Donāt forget to zoom the font-size a modest amount while testing to simulate users who may be visually impaired or who use a different platform with different fonts than yours and see if the layout remains satisfactory.
Funny, I do not remember saying that. I said that you can do it with nested tables but the layout would not be reliable because nested tables are isolated from one another. That has already been demonstrated.
We were doing OK using either <div>s, one table, or your preferred nested tables - the layout was not completely reliable but it was close enough to be acceptable across a modest range of font sizes - UNTIL you insisted that the buttons must be aligned beneath and a specific number of pixels from the edges of the textarea field. That requirement is too specific for your nested table layout. <div>s or a single table can do it nicely, but not nested tables. Why? Because the <textarea> field and the buttons are not related to one another. You will not accept allowing the buttons to center themselves across the last row. That is very easy and looks good, but it would not be your designā¦ a design requirement that you did not impose initially, BTW. Your earlier drawings and layout examples showed asymmetrically positioned small buttons in the bottom row.
If you want the buttons to be laid out with pixel accuracy beneath the <textarea> field, then the columns must relate to one another. AND, in your case, we canāt just design for real browsers, both buttons must be visible in Dreamweaver Design View or they are not acceptable to you.
One table with 3 columns and 5 rows will fill that order. The only thing to quibble about is whether to use outdated table attributes or go with CSS where possible.
:sigh:
The following files contain one table with 5 rows of 3 columns each.
The first file retains as many old HTML table attributes as I could leave behind. The new CSS is minimal.
You need to turn on borders around all of your table cells. If that doesnāt look right then you shouldnāt be using a table. Some browsers donāt allow borders to be turned off and you canāt define exact positioning with table content - since for content that belongs in a table the exact position shouldnāt matter.
The code that I posted assigns an outline around the table cells instead of turning on the borders since the latter affects the layout a little.
Youāve mentioned before that some browsers do not allow borders to be turned off. Would you mind mentioning which browsers these are? I seem to have forgotten. AFAIAC, thatās another good argument for avoiding tables for layout.
I am not sure exactly which one it was but I remember one student in one of my classes had it on their mobile phone - that mobile browser always placed a border around all table cells to make it easier to read the table content.
.
