Annoying Sentence Structures (ASS)
-
4. I did say the spelling was not the issue. :) It just says LINQ (All Flavours), not questions or discussions. 5. That one is annoying. Is each cell in its own table per chance?
Bassam Abdul-Baki wrote:
That one is annoying. Is each cell in its own table per chance?
:| <- That's me giving you a very flat look.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
3. No, C++/CLI means "C++ on the CLI", not "C++ and/or CLI". 4. Yes, LINQ has various flavours. Want me to write flava instead? Word. 5. I hate CSS and rendering engines. Seriously. How on earth can a table cell be shorter than it's row?? I will ponder.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
4. I did say the spelling was not the issue. :) It just says LINQ (All Flavours), not questions or discussions. 5. That one is annoying. Is each cell in its own table per chance?
-
Bassam Abdul-Baki wrote:
That one is annoying. Is each cell in its own table per chance?
:| <- That's me giving you a very flat look.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Better flat than C#.
-
Bassam Abdul-Baki wrote:
That one is annoying. Is each cell in its own table per chance?
:| <- That's me giving you a very flat look.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
For the cell height, the only difference I see is that the Description column has a .hover-container CSS attribute that the other columns do not have. Deleting ".hover-container" should fix it since you have the .hover-row attribute.
-
For the cell height, the only difference I see is that the Description column has a .hover-container CSS attribute that the other columns do not have. Deleting ".hover-container" should fix it since you have the .hover-row attribute.
hover-container defines the element containing the button-group that holds the buttons. hover-row defines the entire row to be highlighted on mouse over.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
hover-container defines the element containing the button-group that holds the buttons. hover-row defines the entire row to be highlighted on mouse over.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Interesting. Commenting out hover-container worked for me. However, commenting out display:block also worked. Couldn't see any direct side-effects from either of these actions. .hover-container { position:relative; //display:block; margin-right:1em; }
-
Interesting. Commenting out hover-container worked for me. However, commenting out display:block also worked. Couldn't see any direct side-effects from either of these actions. .hover-container { position:relative; //display:block; margin-right:1em; }
Yep - this also helps, but causes problems in other browsers.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Yep - this also helps, but causes problems in other browsers.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Well done! What was the issue? Looks like you deleted an entire stylesheet.
-
Well done! What was the issue? Looks like you deleted an entire stylesheet.
a) It's gratifying that you noticed b) The issue was a weird one. In Gecko and WebKit, if you specify that a table cell is to be displayed as a block then the boundaries of that cell (at least the boundary where a border will be drawn) can be shorter than the height of the row. I have a set of buttons that appear when you hover over a row (class=hover-row). The buttons are wrapped in a SPAN that is displayed when you hover over the row, and their position is constrained by the immediate container they are within (class=hover-container). To position the buttons correctly, the container needs to have position:relative and display:block, and the buttons themselves are position:absolute. If the hover-container element (the table cell, in this case) doesn't have relative/block then the bottons appear at the top right of the page. If they do have relative/block then the border of the cell is screwed up since the cell can now be shorter than the row. It dawned on me around 1am that all I was trying to do was constrain the buttons to be within the table cell, so I wrapped everything in the table cell within a div, gave it the hover-container class, and bingo, everything worked.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
a) It's gratifying that you noticed b) The issue was a weird one. In Gecko and WebKit, if you specify that a table cell is to be displayed as a block then the boundaries of that cell (at least the boundary where a border will be drawn) can be shorter than the height of the row. I have a set of buttons that appear when you hover over a row (class=hover-row). The buttons are wrapped in a SPAN that is displayed when you hover over the row, and their position is constrained by the immediate container they are within (class=hover-container). To position the buttons correctly, the container needs to have position:relative and display:block, and the buttons themselves are position:absolute. If the hover-container element (the table cell, in this case) doesn't have relative/block then the bottons appear at the top right of the page. If they do have relative/block then the border of the cell is screwed up since the cell can now be shorter than the row. It dawned on me around 1am that all I was trying to do was constrain the buttons to be within the table cell, so I wrapped everything in the table cell within a div, gave it the hover-container class, and bingo, everything worked.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
a. I've been in QA far too long. And my Math background makes me quite anal(ytical). :) b. Nothing like working at dawn for things to dawn. That's the problem with adding CSS attributes to every minutia these days, everything requires a DIV tag around it. Glad you got it fixed.