[
https://issues.apache.org/jira/browse/WICKET-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218059#comment-13218059
]
Christoph Grothaus commented on WICKET-4428:
--------------------------------------------
@Martin: you are right regarding that the proposed value for z-index may be too
low in specific cases. But taking that as an argument for not adding some
z-index value to wicket-debugbar.css at all -- I don't know...
Many web designers out there and many web frameworks use z-index values in the
hundreds or lower thousands. I stumbled over this issue when using the Wicket
debug bar in my HTML page together with the popular Twitter Bootstrap CSS
framework (which uses a z-index of 1030 for the top navigation). I wondered
where that funny debug bar might be...
Of course you can get around it by supplying your own CSS -- which is what I
did --, but I think we can help other wicket developers by choosing a
reasonable default z-index value, so they don't have to wonder about this.
The only question IMHO is what that reasonable default value should be. My
first proposal of 4096 was a fully random choice. But maybe we can agree on
100000? That should solve 98% of all cases where the debug bar does not show up
initially.
> 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
