![]() ![]() I made this very mistake in the Sample Interactive Grids app. Or you can override the row height for the grid using CSS. If you add markup to a column you need to make sure it isn’t taller than what the default IG CSS rules allow for. So keeping the row heights in sync is a shared responsibility. The browser’s table rules seem to care more about showing what is in a cell than any rules about cell or row height or overflow settings. When there are frozen columns there are separate tables for the frozen and not frozen columns so if the heights of rows in the two tables don’t match the rows get out of sync and it looks terrible and becomes unusable. I know this is supposed to be about column widths but permit me to go on a row height tangent for a moment. We hope to have an option in the future for variable height rows. We choose a fixed row height because it is often what you want, especially for editing, but also because it made many of the fancy things that IG does, such as frozen columns and scroll paging, easier to implement and more efficient. The consistent fixed row height is often very nice when looking over many rows but it can be annoying if some cells have lots of data you want to see. It also fixes the row height of all rows. It uses fixed table layout and lets the user adjust column widths. Some people wanted control over the width of Interactive Reports columns and if you search you can find lots of advice on this some better than others.īut Interactive Grid (IG) is a different beast. When paging through a report I think the changing widths are distracting. This means that the column widths are different depending on which rows you are looking at. It gives more width to columns with lots of text and less width to columns with less text and tries to fit as best it can before giving up and adding a horizontal scroll bar (by being wider than its container). For the most part people seemed pretty happy with how the browser did things. It is also a little less efficient since the browser has to see the whole table markup before it can settle on the column widths. ![]() The algorithm isn’t standardized so it is possible that different browsers do it differently. This means that the browser decides how wide each column is and it generally takes into consideration the data that is in all the rows and all the columns. It used a table with CSS table-layout: auto. This article has been updated to reflect patch release 5.1.1įirst lets review how Interactive Reports handled the column width. You can let me know in the comments after reading this. Still, I’m not 100% sure that in implementing Interactive Grid we got it all exactly right. I hope to explain here everything you need to know about column widths in Interactive Grids. ![]() I think the complaints may be based on misunderstandings of how things work. Since the first Early Adopter release of APEX 5.1 I have seen a number of questions or complaints about how column widths are handled in Interactive Grid. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |