[TYPO3-content-rendering] working on accessible_tables - questions

Sebastian Kurfuerst sebastian at garbage-group.de
Wed Dec 14 17:41:29 CET 2005


Hi,
I currently work on integrating some extensions into the core, at the
moment I do accessible_tables. Thanks again to the German TYPO3 partner
network for funding this.

Some questions:
      * I removed the CSH, because it only worked flawlessly when
        extending tt_content with one more field - but it didn't have
        too much information in it anyways.
      * the german and italian translation is currently lost, because
        the translators have to translate it and then it gets inserted
        into the csh_packages.
      * table headers are _switched off_ by default to get full
        backwards compliancy. Does this make sense to you?
      * the hard-coded p-tag was removed, but inserted in innerStdWrap
        again to reach backwards compliancy.
      * the <thead> tag IMO only makes sense when headerPos is set to
        "top" - is this correct? it was inserted all the time before.
      * the <th> tag is only set when headerPos is set to top. I think
        this makes sense as well?
      * tbody is currently only outputted when headerPos set to "top" -
        does it make sense to output it all the time? Problems with
        backwards compliancy when tbody is outputted around _all_
        tables? (That was the reason for me not to do this.)

Please give some comments about it.

Thanks and greets, Sebastian




More information about the TYPO3-project-content-rendering mailing list