Is there a good reason that all blocks are set:

.block {
  position: relative;
}

You can run into overlay problems if you do that globally.

Example:

Float the #logo left and then float some stuff inside the .region-header to the left too (in my case i did that with the search fields).
As a result the .region-header area will overlap the #logo and so clicking on the (logo not click able) tag will no longer work.

I wanted to mention that because its not abnormal that people float stuff inside their header. But maybe there is a special reason for position:relative, just curious.

I set .block back to, static, problem fixed, no other problems.

Comments

Jeff Burnz’s picture

Jeff Burnz commented

By memory the only reason this was set was to ease RTL in some browsers. Then I just left it there, however I see no immediate reason why we cannot take this out apart from maintaining backwards compatibility (some might be relying on this).

I know it causes issues, it was always a trade off between actually getting RTL to work properly in IE without out including an IE conditional stylesheet. The issues were always minor and easily worked around.

I have to think about it and test some, I will keep it in mind however I do not see this as a major problem, given the theme has 20 thousand users and I get complaints about this almost never.

Jeff Burnz’s picture

Jeff Burnz commented
Title: Block class relative » Remove position relative on blocks
Version: 7.x-2.1 » 7.x-2.x-dev

Gonna update the title so I remember what this is actually about :)

BTW, thanks for the issues e-anima, its very good to have someone posting ideas and constructive feedback.

Jeff Burnz’s picture

Jeff Burnz commented
Component: Miscellaneous » CSS/HTML

Revamping my categories.

marcoka’s picture

marcoka commented

some additional note on what i discovered. somehow after setting position:relative to position:static...the contextual links are broken and will only appear on the top right corner (only for contextual links for blocks).

Jeff Burnz’s picture

Jeff Burnz commented

That is because you are explicitly declaring position static and overriding contextual links module which needs it.

marcoka’s picture

marcoka commented
Status: Active » Closed (won't fix)

i dont have problems anymore/since then. so i would say fixed. reopen it you disagree.