Content Type TABLE does not allow 0 cellspacing
When setting up content type TABLE it does not allow for a cellspacing of 0. It automatically unckecks the selection and does not render this in html.
MSIE uses a default cellspacing other than 0 when rendering the tables. Therefore, there does not appear to be a way to create a table with no spacing between cells.
(issue imported from #M93)
Updated by Ingmar Schlecht about 17 years ago
This is about the TCA configuration of the field tt_content.table_cellspacing which is currently like this:
This would obviously have to be changed in some way, I think.
Anyone with more knowledge on what could be changed without causing any sideeffects please comment!
Updated by Robert Lemke about 17 years ago
What value would you like to put into that field?
I admit that it is quite confusing that the zero (0) disappears as soon as you leave the field. But this is the correct behaviour, because 0 is the default value, better: the "checkbox value" (see: http://typo3.org/documentation/document-library/doc_core_api/columns_fieldnam-1/)
This means that if the cellspacing or cellpadding field is empty, in reality "0" is set, because the table_cellspacing and table_cellpadding fields in MySQL are of the type integer with default to zero.
As long as you don't want to put something else than an integer value here, I wouldn't consider it a bug. But maybe it would be nicer to display the "0" when the checkbox is checked.
Updated by Ernesto Baschny over 15 years ago
Both fields should allow an int value OR an empty value ("", i.e. NULL). So TYPO3 could be differenciated if the user doesn't want to set the field (NULL), which should render a TABLE without any "cellspacing" (or "cellpadding") attribute or if he wants to set the field with a value of "0" (which would render cellpadding/spacing="0").
As far as I can see there is no TCA-way of having an input field that has "eval=int" but still allows a NULL value. So I guess this would require the new possibility in the CORE first. But maybe I just cannot see how it could be acomplished (http://typo3.org/documentation/document-library/doc_core_api/columns_fieldnam-1/).
Updated by Benni Mack over 11 years ago
we could change the DB field to be varchar and then we do the int-evaluation on TCA basis, having finally two values to differentiate ("" and 0) in the DB.
Of course, the cleanest way would be that TYPO3 finally learns to understand the difference between 0 and NULL.
Updated by Riccardo De Contardi about 8 years ago
- Target version deleted (
Tthe bug is still present in TYPO3 CMS 6.1.0
Said that, AFAIK table attributes like cellspacing and cellpadding are deprecated in HTML5
Honeslty, I think they should be removed.
The field "Additional CSS Class" trims white spaces, so you can't add more than one CSS class... please, fix it!
Updated by Riccardo De Contardi over 4 years ago
- on 7.6.16 has no more the fields "border", "cellpadding", "cellspacing" if you use Fluid Styled Content. They are still present if you use CSS Styled Content.
- on latest master (8.7.1) the TABLE CE has no more the fields "border", "cellpadding", "cellspacing" as far as I can see (both CSS Styled Content and Fluid Styled Content - I have not tested with Compatibility7 loaded, though).
- The issue about the distinction between 0 and NULL is still present AFAIK.