XUL Tree cells lack multirow text in cell usability feature like "Wrap text" in OpenOffice and Excel

NEW
Unassigned

Status

()

Core
XUL
10 years ago
6 years ago

People

(Reporter: Sergey Zh, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8) Gecko/20071015 SUSE/2.0.0.8-1.1 Firefox/2.0.0.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8) Gecko/20071015 Firefox/2.0.0.8

In XUL Tree there is no ability to setup multirow text in cells. This is very important lacking feature, when trying to provide OpenOffice/Excel-like functionality for table data in XUL Tree.

Currently, when there is lots of text data in cells, little percent of text is shown in a cell, it is cut short. Length of text may easily be over the entire screen width, so the cells with it's width have no chance to show all text. It should be optionable to make text in some cells multirow, thus all text in some chosen cells (or row's cells or column's cells) would be visible.


Reproducible: Always

Steps to Reproduce:
How it looks where it works:
1. Open OpenOffice Calc/Excel file with lots of text in cells.
2. Select some columns or rows.
3. Right mouse button -> Format Cell  -> Alignment tab -> Wrap text automatically  ,press OK.
Height of rows with selectes cells is adjusted, text in selected cells become multirow, all data is visible.  Meanwhile other, non selected cells may contain cut text(like XUL tree cells now), not wasting screen space with some other less importent cell data.
Actual Results:  
XUL tree lacks critical usability feature allowing application developer to develop table data user interaction with XUL instead of some completely different technology.

Expected Results:  
XUL Tree feature-rich cell data manipulation.

Updated

10 years ago
Component: XP Toolkit/Widgets: Trees → XUL
QA Contact: xptoolkit.trees → xptoolkit.widgets
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.