|
|||||||
| Feature request: Use CSS+<div> instead of HTML <table> for styling output | ||||
|---|---|---|---|---|
| osTicket should not use HTML <table> for styling output | ||||
Category Unknown |
Affected Version 1.6 rc5 |
Priority 6 |
||
Status Unconfirmed |
Fixed Version (none) |
|||
Submitted 01-16-2010 |
||||
|
||||
|
|
|
|
|
|
Feature request: Use CSS+<div> instead of HTML <table> for styling output
osTicket should not use HTML <table> for styling output
I know that there are pros & cons for tables vs. div, see e.g. http://stackoverflow.com/questions/8...layout-in-html for a good discussion.
My main reason for suggesting this change for osTicket are the drawbacks when dealing with its output: Browsers tend to need more resources and slow down to render <table> based layout, and printing of large tables (such as in <div id="ticketthread"> causes all sorts of troubles in current browsers. IMHO, eliminating the tables in <div id="ticketthread"> and <div id="ticketnotes"> is not much effort but would have a large positive impact. |
![]() |
| Issue Tools |
|---|
Subscribe to this issue |