You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/28 11:23:48 UTC

[jira] [Resolved] (WICKET-4428) Wicket DebugBar: add CSS property "z-index" so it will show above other elements that use z-index

     [ https://issues.apache.org/jira/browse/WICKET-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-4428.
-------------------------------------

    Resolution: Won't Fix

Adding this zIndex wont solve the problem completely. There always be an application which has an element with higher value of its zIndex and then someone else will report the same problem with even higher value for DebugBar's zIndex...
The simplicity of CSS is that you can target any element and manipulate its properties. So, I think it is better the user's application to tweak the zIndex in their own .css file depending on their own needs.
                
> Wicket DebugBar: add CSS property "z-index" so it will show above other elements that use z-index
> -------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-4428
>                 URL: https://issues.apache.org/jira/browse/WICKET-4428
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-devutils
>    Affects Versions: 1.5.4
>            Reporter: Christoph Grothaus
>            Priority: Trivial
>         Attachments: fix-WICKET-4428.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> The wicket debugbar may fail to display if the webpage has a <div> element or any other component at the top that uses the CSS property "z-index". As the debug bar <div> element has no z-index, it will be under that other element, hence not visible.
> Solution: add a line "	z-index: 4096;" to wicket-debugbar.css.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira