Bug #36697

Table Layout in TER Manuals

Added by Den Denyer about 1 year ago. Updated 7 months ago.

Status:Closed Start date:2012-04-29
Priority:Must have Due date:
Assignee:Boris Hinzer % Done:

0%
Category:[Team] Server
Target version:- Estimated time:0.00 hour
Votes: 0

Description

I believe the table layout in the TER manual rendering is broken. I use Opera, but checked in FF and Chrome and saw the same issues.

On large pages such as : http://typo3.org/documentation/document-library/core-documentation/doc_core_tsref/4.7.0/view/1/6/

You can see that as you scroll down, the table content is cropped. There should be 4 columns but often in large tables you can see only 3. This is because the table is fixed with and the column contents exceed this width.

A quick fix is to add:

table-layout: fixed;

To the .d table {} selector in the CSS.

For me this was in: http://typo3.org/typo3temp/js_css_optimizer/js_css_optimizer_ea47919fc3ab30b1fc4fbb9204a0fad3_bundled_cssFiles.1335201861.css

But obviously that's the optimised CSS link, I don't know the root resource. Needless to say you can find it easily by inspecting any of the TER manual/document tables.

If you want any more information, find me in #typo3 on IRC, I am almost always there.

Capture.PNG - Issue when table layout is fixed. (26 kB) Den Denyer, 2012-04-29 03:10

Capture2.PNG - Original issue, no fixed layout means 4th column can't be seen. (21.3 kB) Den Denyer, 2012-04-29 03:10

Related issues

duplicates The typo3.org project - Bug #35664: Documentation rendering not correct Closed 2012-04-04

History

#1
Updated by Den Denyer about 1 year ago

BTW I tried to search for similar issues, but could find no search functionality in Forge. I read through the first 50 or so issues and didn't find anything specifically addressing this issue, but I'd LOVE to know where the search feature lives!!

Also, fixing the table layout will break entries in any column that will not word-wrap, and alas the word-wrap property is poorly supported. I've attached an example screenshot of such a problem.

#2
Updated by Den Denyer about 1 year ago

Attaching some screen captures.

The TS Ref tables are pretty heavy on information, they really need more horizontal room than is provided by the current layout.

Capture2.PNG shows the current problem.
Capture1.PNG shows the "Fix" and its associated issue.

#3
Updated by Steffen Gebert about 1 year ago

Thanks for your report, Den. You find the search in the upper right corner.

#4
Updated by Den Denyer about 1 year ago

You mean that stupidly obvious large white box with SEARCH written next to it?

Sigh

I'll be right back, just going to try and flatten out my desk with my head. Many thanks :)

#5
Updated by Chris topher about 1 year ago

Hi guys,

we are already discussing this problem in #35664. Please go on there!

#6
Updated by Boris Hinzer about 1 year ago

  • Status changed from New to Needs Feedback

Could it be that the news main.css is yet not loaded because of the compression?
Otherwise this issue should have also been fixed like in #35664

#7
Updated by Boris Hinzer about 1 year ago

  • Assignee set to Joern Bock

Hi Joern,
since I don't know to whom to address my last comment, I assign this ticket to you.
I hope you don't mind ;) It seems that the compressed css still has the old main.css as base. Otherwise this issue should have been fixed IMHO.

Regards,

Boris

#8
Updated by Boris Hinzer 11 months ago

  • Assignee changed from Joern Bock to Christian Zenker

Hi Christian,
afaik you setup the compression of the css/js. Could you please take a closer look why the main.css from the site is not linked in?

Thanks a lot.
Regards,

Boris

#9
Updated by Christian Zenker 11 months ago

  • Category changed from [FOR] Markup to [Team] Server
  • Assignee changed from Christian Zenker to Tolleiv Nietsch

Boris Hinzer wrote:

afaik you setup the compression of the css/js.

No I didn't. We just talked about it, but did not do anything. ;)

Could you please take a closer look why the main.css from the site is not linked in?

According to the documentation of js_css_optimizer the crushed files in typo3temp/js_css_optimizer/* are never updated. I think there is the problem. Deleting the files in this folder could solve this issue.

I asked Tolleiv to have a look at it and he plans to do it this weekend.

#10
Updated by Tolleiv Nietsch 11 months ago

  • Assignee changed from Tolleiv Nietsch to Christian Zenker

Does it work on the latest system? (the compression is refreshed with every deployment)

#11
Updated by Christian Zenker 10 months ago

  • Assignee changed from Christian Zenker to Boris Hinzer

Boris, I'd like to give this back to you. I'm not sure what CSS style should have changed and what to look for to see if the css files got rebuild. Can you help?

#12
Updated by Ben van 't Ende 7 months ago

  • Status changed from Needs Feedback to Closed

Documentation rendering will be fully overhauled.

Also available in: Atom PDF