Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. Site Bugs / Suggestions
  4. Annoying Sentence Structures (ASS)

Annoying Sentence Structures (ASS)

Scheduled Pinned Locked Moved Site Bugs / Suggestions
pythonperllinuxhelp
26 Posts 4 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Bassam Abdul Baki

    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.

    C Offline
    C Offline
    Chris Maunder
    wrote on last edited by
    #21

    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

    B 1 Reply Last reply
    0
    • C Chris Maunder

      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

      B Offline
      B Offline
      Bassam Abdul Baki
      wrote on last edited by
      #22

      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; }

      C 1 Reply Last reply
      0
      • B Bassam Abdul Baki

        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; }

        C Offline
        C Offline
        Chris Maunder
        wrote on last edited by
        #23

        Yep - this also helps, but causes problems in other browsers.

        cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP

        B 1 Reply Last reply
        0
        • C Chris Maunder

          Yep - this also helps, but causes problems in other browsers.

          cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP

          B Offline
          B Offline
          Bassam Abdul Baki
          wrote on last edited by
          #24

          Well done! What was the issue? Looks like you deleted an entire stylesheet.

          C 1 Reply Last reply
          0
          • B Bassam Abdul Baki

            Well done! What was the issue? Looks like you deleted an entire stylesheet.

            C Offline
            C Offline
            Chris Maunder
            wrote on last edited by
            #25

            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

            B 1 Reply Last reply
            0
            • C Chris Maunder

              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

              B Offline
              B Offline
              Bassam Abdul Baki
              wrote on last edited by
              #26

              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.

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups